P1129 - Patch for ESXi ServersApr 29, 2010
Connectors for monitoring servers running ESX4i or ESX3i.
Should you install this patch?
Apply this patch if you are not seeing local physical disk information.
Apply this patch if you are using the ESXi connector to monitor your server (instead of the manufacturer's agent).
This patch replaces Patch P1115.
What does it fix?
Not all ESX servers report the status of their disks via ESX's disks classes. This patch adds support for monitoring ESX disks via their IPMI sensors. If disks are found in ESX's disk classes, the IPMI connector will not be activated. Linux added as supported platform.
ESX3i (Using ESXi Connector):
Adds disk, temperature and voltage information. Provides status of memory modules (generally previously reported as "unknown" on most systems). Linux added as supported platform. The Linux - Network / MIB2Linux connector can now be used to monitor the system's network cards (Remote SSH / SNMP will need to be enabled).
Local monitoring using the ESXi connector is now enabled. The KM will use the manufacturer's agent if available, otherwise will try monitoring via the OS when the Patrol Agent and KM are installed on the ESXi Linux Host OS.
Note: For our purposes, BusyBox host OS = ESX3i, RedHat host OS = ESX3.
How to install the patch?
Copy the following files to the $PATROL_HOME/lib/MS_HW_hdf directory on the managed server:
A new connector will now appear when adding a Blade Chassis / OOB management card - VMWare ESX4i.
To monitor an ESX4i system, setup a remote monitoring of the ESX4i host, select the VMWare ESX4i connector and specify WBEM credentials (these are the same as those used to login to vSphere).
Monitoring of HBAs in ESX4i systems should be done using the SMI-S HBA connector.
Nothing needs to be installed on Console systems.