Installation : Installing and Supporting the MegaRAID Storage Manager Software on VMware : Differences in MegaRAID Storage Manager for VMware ESXi

Differences in MegaRAID Storage Manager for VMware ESXi
The following are some of the differences in the MegaRAID Storage Manager software utility when you manage a VMware server.
Full functionality support is available for the VMware ESXi operating system, but it works differently than the normal MegaRAID Storage Manager framework mode. The event logging feature for the MegaRAID Storage Manager Client connected to a VMware ESXi system behaves as follows:
The event descriptions might not be identical to a normal MegaRAID Storage Manager event, (running on a MegaRAID client) because the descriptions come from the firmware through the provider.
Refreshing of the MegaRAID Storage Manager GUI after any updates on the firmware is slower for a client connected to VMWare ESXi hosts, compared to one connected to Windows/Linux/Solaris hosts.
Add an entry to map the VMware host’s IP address with the host name. This is for the discovery to happen correctly. In the absence of this entry, the VMware host would be discovered as 0.0.0.0.
Add an entry to map its own IP address (not the loop back address) with the host name. This is to ensure that the Asynchronous Event Notifications (AENs) are delivered correctly.
In the hosts file of the machine on which the MegaRAID Storage Manager software is installed, add an entry to map its own IP address (not the loop back address) with the host name. This is to ensure that the Asynchronous Event Notifications (AENs) are delivered correctly.
It takes a while to discover the CIMOM servers. If you start the MegaRAID Storage Manager software client immediately after you install the MegaRAID Storage Manager software (or restart Framework service), you will not be able to discover any hosts in the network.