I just wanted to throw out some tips that I run into from time to time in customer environments. These are just meant to be a quick reminder of the things that I find are missed during installations. If you have any to add to the list please leave a comment below, Thanks!
- vSphere needs to know about your mail server or it wont be able to send you alerts. Go to Administration -> vCenter Server Settings and then find the mail section in the list. FIll in your SMTP server as well as the sender email address. This will make sure that when an alert is triggered it will be able to send an email if the action is to do so.
- Alerts also need to be configured…. In fact vCenter will do nothing more than trigger the alarm by default. So if you want email alerts, make sure to go into each alert you want emailed to you and set it up to do so. click on your vCenter server in the left tree, and then select the alarms tab. Next click on Definitions and right click each alarm you want to send an email for, then go to the Actions tab and click add to add an email alert action. Lastly you need to specify where that email needs to go.
If the idea of setting every one of these alarms seems like too much work your not alone. I blogged about using powershell to automate the process a while back over here…. and Lauren Malhoit blogged about it over here.
- Remember to Update your hosts! OK how many of you used to brag about your windows or linux server up-time ? Well this isnt the old days so remember to update your ESXi servers and reboot them to apply those updates when needed. Your windows and linux servers will still report no downtime if you use vMotion to move the VM’s and this will help to avoid bugs and other problems in the future. To update your hosts go to the “Update Manager” tab and run a scan after attaching the critical and non critical baselines to the host or cluster.
- Make sure your hosts are placed properly. I have seen customers create a datacenter object in vCenter, as well as a Cluster Object. However when they add their hosts in to vCenter they will accidentally put them under the datacenter instead of the cluster. So when things go south and they lose a host, they expect HA to kick in… but since the hosts arent in a cluster HA does nothing.
- Multipathing is a must for both iSCSI and Fiber Channel, but is yours working right ? The easiest way to check is to go into one of your hosts and go to the storage adapters area under the Configuration tab. Here you will see a list of hba’s or the VMware Software iSCSI adapter. Irregardless some simple multiplication can tell us what we need to know. If the number of paths you have is not a multiple of the number of targets times the number of devices then you have a problem.
- Make sure you use Round Robin path selection if possible… check with your vendor to see if Round Robin is an acceptable PSP, if it is make sure to set it (on every host, and every lun). Note that ESXi 5.1 can automatically detect and set Round robin for VNX arrays. Note the picture below is a VNXe which will not have non-optimal paths, but most arrays will show two “Active (I/O)” paths and two “Active” Paths