![]() |
MegaRAID Storage Manager Online Help System |
Differences in MSM for VMware ESXi
The following are some of the differences in the MSM utility when you manage a VMware server.
- The following limitations apply to the system information exposed through the application:
- Authentication support:
- MSM allows CIMOM server authentication with the user ID and the password for VMware.
- Access to VMWare ESXi hosts is controlled based on the user privileges. Only root users can have 'Full Access' while the non-root users can have only 'View Only' access.
- Multiple root users can simultaneously login using 'Full Access' mode to access the VMWare ESXi server.
- Event logging:
Full functionality support is available for the VMware ESXi operating system, but it works differently than the normal MSM framework mode. The event logging feature for MSM Client connected to a VMware ESXi system behaves as follows:
- There is no support for retrieving initial logs (the events that occurred before a client logs in). Only those events that occur after a client logs in appear in the event logger dialog.
- System log do not display.
- The “Save log” feature is not supported; however, the “Save Log as Text” is still supported.
- The “View Log” option allows you to view the logs saved in a text file on the event logger dialog.
- The event descriptions might not be identical to a normal MSM Client because the descriptions come from the firmware through the provider.
- There is no filtering of events, unlike Monitor Service.
- Refreshing of the MSM 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.
- Remote discovery:
- For networks that do not have DNS configured, the “hosts” file in the machine on which MSM is installed must be edited as follows:
- Add an entry to map the VMware host’s IP address with the hostname. 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 Hostname. This is to ensure that the Asynchronous Event Notifications (AENs) are delivered correctly.
- For networks that has DNS configured, the “hosts” file in the machine on which MSM is installed must be edited as follows:
- When you do the initial configurations for the VMware host, provide the correct DNS server IP address.
- In the
hosts
file of the machine on which MSM is installed, add an entry to map its own IP address (not the loop back address) with the host name to ensure that the Asynchronous Event Notifications are delivered correctly.- It takes a while to discover the CIMOM servers. If you start the MSM client immediately after you install MSM (or restart Framework service), you will not be able to discover any hosts in the network.
- VMware ESXi is supported only on a full installation of MSM; stand-alone, client-only, and server-only modes do not support VMware ESXi management.
- VMware ESXi is supported on following operating systems:
- The following describes the status of components related to VMware ESXi:
DB09-000202-04 37857-02 Rev. E October 2010 Copyright© 2010 by LSI Corporation. All rights reserved. You can find a list of the LSI U.S. distributors, international distributors, sales offices, and design resource centers on the LSI web site at: http://www.lsi.com/cm/ContactSearch.do |