Also when you install additional components e.g. Every environment is different and you may use more or less alarms than I have mentioned.ĭon’t forget that depending on which vSphere licenses you have might see extra default alarms for items such as FT. Naturally, this isn’t a complete list of alarms, however it is the default alarms that I would configure in most, if not all environments. Insufficient vSphere HA Failover Resources Hopefully these alarms shouldn’t need any explanation, as they should ALWAYS be enabled.
If you have this set to high for all servers then it can cause alarms when backup software rolls back snapshots depending on how big the VM is. I tend to leave VM Monitoring Only and Medium and then change individual VM’s monitoring to High if required. VSphere HA Virtual Machine Monitoring Error this alarm works in conjunction with Virtual Machine Monitoring. If for some reason none of your other alarms work then at least you know that a VM has been restarted by HA. VSphere HA Failover In Progress this resides on the nice to have. With this in mind, I set the Warning to 90% and Critical to 95% so I have some room to either more VM’s around either by Storage vMotion or Cold Migration. Then when the Datastore is provisioned only use 1TB so you have room for expansion quickly and easily if needed. if you need 1TB for a Datastore, ask for an extra 25%. I recommend always asking for slightly more than need e.g. From the presented LUN how much space has been provisioned as a Datastore. Well it also manages ‘lost storage path redundancy’ and ‘degraded storage path redundancy’ so if you have an if your ESXi host has multiple connections to it’s storage, you will be notified if one of these is lost.ĭatastore Usage On Disk quite an important one. Big deal you say, I can see that in vCentre. If the host loses connection to the storage then the VM’s will be restarted using HA. We are now going to run through some of the default alarms, with some suggested thresholds.Ĭannot Connect To Storage why would we want to configure this? Well essentially this is a per host setting. Enable the alarm so the proper alert status is visible. This issue may occur if you have disabled the action for this alarm. This is a pre-configured alarm and it triggers automatically when problems are detected. To change the default swapfile location for the host select the host, click the Configuration tab and Virtual Machine Swapfile Location.In the previous post setting up and configuring alarms in vCenter 5 Part 1 we looked at the initial configuration. A: The Storage Status is reported by the Datastore usage on disk alarm, which monitors datastore disk usage. It may be likely that your host is configured to use a different datastore for all VMs by default and it is just taken up by swap files at this point. As far as cleaning up that datastore, you can right-click it and Browse and poke around to see what kind of files are taking up the space.
Select one of the other options ("Always store with the virtual machine" is recommended and will probably work for you since that datastore has a lot of free space). At first this seemed to work until I made a modification to the default alarm and now it. Right-click the VM and go to Edit Settings > Options tab > Swapfile location. vCenter level has the default Datastore usage on Disk alarm set for 85 and 95, but I have one datastore cluser with 4TB datastores, so I set an individual alarm at the datastore cluster level that is also for datastore usage on disk set at 94 and 97.
Are any of the datastores full or very close to it? The swap file may be located on a full datastore even if the VM is on another datastore and if the host cannot create the swap file, the VM will not boot. Take a look at all of the datastores visible to the host (in vSphere, select the host > Configuration tab > Storage).