HP VMware ESXi 5.0 Customized Image Release Notes for March 2012

Installing ESXi 5.0 Patch ESXi500-201112001 available at http://www.vmware.com/patchmgr/
findPatch.portal fixes the issue.
Missing MP SNMP traps
Fixes the issue where specific HP SNMP traps are not generated even though the conditions
associated with the traps have occurred on HP ProLiant servers running VMware ESXi 5.0 with
SNMP traps enabled with the HP WBEM Providers installed.
The following HP SNMP traps were generated:
• Trap 9003: iLO login attempt threshold reached
• Trap 9005: iLO selftest error
• Trap 9006: server to iLO communication failures are not generated
In this release, these traps are now generated when the condition associated with the traps have
occurred. Reference HP Customer Advisory C03177749 at: http://h20000.www2.hp.com/
bizsupport/TechSupport/Document.jsp?objectID=c03177749.
Missing SNMP traps on HP SIM
SNMP traps monitoring with HP SIM is not supported for the SNMP traps sent by HP WBEM
Providers on VMware ESXi 5.0. But these traps can be received on other SNMP clients like
snmputil, netsnmp and so on.
Invalid SNMP traps are generated under certain conditions
Fixes the issue where HP ProLiant servers running VMware ESXi 5.0 that use SNMP traps enabled
with the HP WBEM Providers installed generates invalid SNMP traps with empty TrapOIDs or
with an HP TrapOID. Also, generates SNMP traps with TrapID of 0 or 0xffffffff under certain
conditions. An empty TrapOID is decoded by the MIB decoders as zeroDotZero.
Invalid traps are generated in the following cases:
• When HP Systems Insight Manager (HP SIM) discovers a server for management for the first
time.
• During the Provider startup, as a result of a boot, reboot, or a manual restart occurring.
• When the Fan state is changed to failed, removed, or OK.
• Server has redundant fan.
• Fan is inserted when the server already has redundant fans.
NOTE: The correct SNMP trap is generated for all Fan state changes and for redundancy
lost or restored.
• When the Power Supply is removed or a State is changed to failed, but the server still has
redundant power supplies.
NOTE: The correct SNMP trap is generated when the Power Supply is failed or removed
and for redundancy lost or restored.
• When the Smart Array Physical Drive State changes to rebuilding.
NOTE: The correct SNMP trap is generated when the rebuild completes.
• When the Smart Array Controller battery charge State changes.
NOTE: The correct SNMP trap is generated if the battery fails.
An example of an invalid trap:
8 Important notes and recommendations