Lenovo ThinkServer RD330 MegaRAID SAS Software User Guide - Page 240

Chapter 6: MegaRAID Storage Manager Overview and Installation | Installing and Configur- ing a CIM Provider MegaRAID SAS Software User Guide 6.6 Installing and Configuring a CIM Provider 6.6.1 Installing a CIM SAS Storage Provider on Linux Add an entry to map its own IP address (not the loop back address) with the Hostname. This is to ensure that the Alert 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 Hostname. 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 MSM client immediately after you install MSM (or restart Framework service), you will not be able to discover any hosts in the network.  This is supported only on a full installation of MSM; standalone, client-only, and server-only modes do not support VMWare ESX3i management.  Supported on the following operating systems: - Windows, RHEL and SLES 10  The following descriptions summarize the status of components related to VMWare ESX3i: - MSM client GUI is supported. - There is no support for Monitor Configurator; you cannot configure the severity of the AENs. - There is no pop-up service support. - There is no e-mail and system log support. - Monitor service support is not available. This section describes the installation and configuration of the MegaRAID Common Information Model (CIM) provider. The Common Information Model offers common definitions of management information for networks, applications, and services, and allows you to exchange management information across systems throughout a network. On a VMWare ESX3i system, management is possible only through a CIM provider and it is performed through MSM installed on a remote machine running a Linux or Windows operating system. VMWare ESX3i comes with the Small Footprint CIM Broker (SFCB) CIM Object Manager (or CIMOM). A CIMOM manages communication between providers, which interact with the hardware, and a CIM client, where the administrator manages the system. 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 procedure documents how to install and un-install the CIM SAS Storage Provider on a system running on the Linux operating system. Page 240