Lenovo ThinkServer RD330 MegaRAID SAS Software User Guide - Page 239
providers, instrumentation to Management Brokers CIM Object Manager. CMPI
View all Lenovo ThinkServer RD330 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 239 highlights
MegaRAID SAS Software User Guide Chapter 6: MegaRAID Storage Manager Overview and Installation | MegaRAID Storage Man- ager Support and Installation on VMWare 6.5.4.2 Differences in MSM for VMware ESXi SFCB supports Common Manageablity Programming Interface (CMPI)-style providers. CMPI defines a common standard used to interface Manageability Instrumentation (providers, instrumentation) to Management Brokers (CIM Object Manager). CMPI standardizes Manageability Instrumentation, which allows you to write and build instrumentation once and run it in different CIM environments (on one platform). 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: - Only the IP address and the Host name display. - The operating system type and the operating system architecture do not appear. - There is no support for the controller health information. 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: 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 does 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. Page 239