In the VTMN Communities, William Lam, created a new HealthCheck script that I will be definietely adding to my HealthCheck Arsenal. More information on the script and its usage can be found in the VTMN Communities posting.
The script reports on the following:
- vCenter Build/Release
- ESX/ESXi Build/Release
- Cluster(s) Name/Statistics (Hosts,CPU and MEM availabity, HA,DRS and DPM enabled)
- ESX/ESXi Hardware configuration (NICs/HBAs)
- ESX/ESXi State
- ESX/ESXi Config (WIP)
- ESX/ESXi Datastore summary
- Virtual Machines summary
- VM Storage summary
- VM Network summary
- VM w/Snapshots
- VM w/RDMs
- VM w/NPIV enabled
- VM w/connected CD-ROMs
- VM w/connected Floppys
For more details, please take a look at the sample report located at here. The requirements for this script are: vCenter 2.5, ESX(i) 3.5, VI-Perl Toolkit or VIMA.
Just like Duncan states, this script can be compared to the PowerShell HealthCheck scripts and the Service Console script.
:: February 2, 2009 by Rick Scherer
Posted under ESX 3.5 Tips, ESXi 3.5 Tips, this blog has 2,054 views and 3 responses.
(No Ratings Yet)
Loading ...
7:48 pm on February 4th, 2009
I’ve just updated the script with some fixes/enhancements including the –datacenter option.
7:02 am on February 3rd, 2009
May I make another suggestion. I have used the script in our environment but have noticed you include –cluster as an option, but no –datacenter option. Uniqueness of the cluster name is constrained at the datacenter level. we actually have the same cluster name across multiple datacenters, there for the script just grabs the first one in the view and thats it. It maybe advantageous to add a –datacenter option with a filter on that in the outer most loop.
10:42 pm on February 2nd, 2009
Hi Rick,
Thanks for the post, I also just posted an update of the script. Had to fix a few minor bugs and added some enhancements that Duncan had suggested earlier.