New version of the Powershell Healthcheck script released

Version 2.0 of the Healthcheck script is released. The script reports the following:

– VMware ESX server Hardware and version         
– VMware vCenter version    
– Cluster information (Updated)    
– VMware statistics (New)
– Active Snapshots    
– CDROMs connected to VMs   
– Floppy drives connected to VMs  
– Datastores Information such as free space
– RDM information  (New)
– VM information such as VMware tools version,  processor and memory limits     
– VM’s and there datastore (New)
– VMware timesync enabled  
– Percentage disk space used inside the VM (New)    
– VC error logs last 5 days (New)

It is possible to schedule this script and output the content to HTML and e-mail it. 

I uses some of enhancements from the VI Toolkit forum @

http://communities.vmware.com/community/developer/windows_toolkit

If you have suggestions , let me know!

You can download the script here.

 image

[ad#verticaal]

VMware ESX servers unable to manage via VIC, SSH or iLO session

Today i had a nasty problem with a customer. Some VMware ESX servers were disconnected from vCenter. Tried to connect the VMware ESX hosts using the VIC,  but that was not possible. I was unable to login via SSH connection, connect with HP iLO to the HP Blade enclosure and did a remote connection to the console. There where HA errors on the screen. I tried to log in the console, after typing the password and hit the enter button the login prompt re-appears every time i try.  The VMware ESX servers were not manageable anymore, DAMM.

The VMs on the disconnected VMware ESX servers were still running and had RDP enabled. The only solution so far was to log in via RDP and shutdown the VMs.  I did this for one VMware ESX server. After shutting down all VMs, i did a cold reboot of the VMware ESX server. After several minutes the VMware ESX server reappears in vCenter. I went to the log files and found the following error:

fork: Resource temporarily unavailable

clip_image002

After searching the VMware Knowledge base i found the following article:

Defunct cimservera processes seen on VMware ESX 3.5 running hardware management agents

It looks like we have the same symptoms:

  • Unable to login through SSH to VMware ESX host
  • Unable to login on local Service console
  • HA errors.

I did “ps-ef” on the console of other VMware ESX servers that were still working and returned a couple of thousands cimservera defunct processes. Holy shit.

clip_image002[5]

After restarting the pegasus service on the host the cimservera defunct processes are away. Now there are 134 processes active.

It seems that one ISCSI target was offline and that all the VMware ESX servers tried to connect to the ISCSI target every 60 seconds, the failed login attemps results in thousands of cimservera defunct processes. This is a bug and VMware will release a patch for this nasty problem. Watch your patches.

I did a temporarily fix by schedule restarting the pegasus service every day on every VMware ESX server using the plink utility.

Watch your processes frequently on your VMware ESX hosts!

[ad#verticaal]

New VMware Powerpack for PowerGUI

 

On the PowerGUI website is a new version off VMware PowerPack released.

A PowerPack extends the PowerGUI with a set of folders, nodes, links and actions that allow you to manage VMware Infrastructure. With the PowerPack no Powershell knowledge is needed.

The new version has the following new enhancements and supported features:

December 19, 2008 (2.0.0)
– reorganized the PowerPack structure to facilitate easier management of multiple hosts and to allow users to retrieve objects from one or more of the hosts they are managing whether they are already connected or not
– added support for browsing the VMware Inventory hierarchy (includes Hosts and Clusters, Virtual Machines and Templates, Networks and Datastores), including being able to browse directly into the file system on the datastores
– added many new links and actions
– exposed many more VMware Infrastructure objects through topological views and through integration in the hierarchy
– improved the performance of many nodes, links and actions
– added single sign-on support (note that connecting to multiple hosts using the same username but different passwords is currently not supported, but we are working on that and will provide support for this soon)
– tested management against Virtual Center 2.0, ESX 3.0x and 3.5, ESXi 3.5 and Virtual Server 2.0 (note: management of Virtual Center 2.0 requires version 1.0 of the VMware VI Toolkit)
– and more!

Supported features:
• Management of multiple VMware Virtual Center, ESX, ESXi and VMware Server hosts when using the VMware VI Toolkit 1.0 release
• Management of multiple VMware Virtual Center, ESX and ESXi hosts when using the VMware VI Toolkit 1.5 release
• Single sign-on to multiple hosts using the same credentials
• Ability to browse through inventory hierarchies on Virtual Center
• Ability to view topological data for any managed server
• Management of datacenters, clusters, resource pools, hosts, folders, virtual machines, templates, snapshots, networks, datastores, files, tasks and log files

 

Some screenshots:

 

image

 

image

More information can be found on the PowerGUI site.