Failed to manage the IBM RAID Controller with MSM with an ESXi 5.x host server - IBM BladeCenter, System x and Flex System



Source

RETAIN tip: H21152

Symptom

Users may not be able to connect to the host when attempting to remote manage an IBM ServeRAID controller using IBM MegaRAID Storage Manager (MSM) in a Microsoft Windows Virtual Machine (VM) with a ESX 5.x host.

Typically users may see only the Windows VM, and not the host server, which is what users will need to see in order to manage the ServeRAID controller to which the VMs are connected.

Affected configurations

The system may be any of the following IBM servers:

  • BladeCenter HS12, type 8014, any model
  • BladeCenter HS12, type 8028, any model
  • BladeCenter HS22, type 7870, any model
  • BladeCenter HS22V, type 7871, any model
  • BladeCenter HS23, type 7875, any model
  • BladeCenter HS23E, type 8038, any model
  • BladeCenter HX5, type 7873, any model
  • Flex System x220 Compute Node, type 7906, any model
  • Flex System x240 Compute Node, type 7863, any model
  • Flex System x240 Compute Node, type 8737, any model
  • Flex System x440 Compute Node, type 7917, any model
  • System x3100 M4, type 2582, any model
  • System x3200 M2, type 4367, any model
  • System x3200 M2, type 4368, any model
  • System x3200 M3, type 7327, any model
  • System x3200 M3, type 7328, any model
  • System x3300 M4, type 7382, any model
  • System x3400 M2, type 7836, any model
  • System x3400 M2, type 7837, any model
  • System x3400 M3, type 7378, any model
  • System x3400 M3, type 7379, any model
  • System x3500 M2, type 7839, any model
  • System x3500 M3, type 7380, any model
  • System x3500 M4, type 7383, any model
  • System x3530 M4, type 7160, any model
  • System x3550 M2, type 7946, any model
  • System x3550 M3, type 4254, any model
  • System x3550 M3, type 7944, any model
  • System x3550 M4, type 7914, any model
  • System x3620 M3, type 7376, any model
  • System x3630 M3, type 7377, any model
  • System x3650 M2, type 7947, any model
  • System x3650 M3, type 4255, any model
  • System x3650 M3, type 7945, any model
  • System x3650 M4, type 7915, any model
  • System x3690 X5, type 7147, any model
  • System x3690 X5, type 7148, any model
  • System x3750 M4, type 8722, any model
  • System x3750 M4, type 8733, any model
  • System x3755 M3, type 7164, any model
  • System x3850 M2, type 7233, any model
  • System x3850 X5, type 7143, any model
  • System x3850 X5, type 7145, any model
  • System x3950 M2, type 7233, any model
  • iDataPlex dx360 M2 Server, type 7323, any model
  • iDataPlex dx360 M3 Server, type 6391, any model
  • iDataPlex dx360 M4 server, type 7912, any model

The system is configured with at least one of the following:

  • MegaRAID Storage Manager, any version

The system is configured with one or more of the following IBM Options :

  • ServeRAID M5014 SAS/SATA Controller, Option part number 46M0916, any Replacement part number (CRU)
  • ServeRAID M5015 SAS/SATA Controller, Option part number 46M0829, any Replacement part number (CRU)
  • ServeRAID M5025 SAS/SATA Controller, Option part number 46M0830, any Replacement part number (CRU)
  • ServeRAID M5110 SAS/SATA Controller Card, Option part number 81Y4481, any Replacement part number (CRU)
  • ServeRAID M5110 SAS/SATA Controller for IBM System x (CTO), any replacement part number
  • ServeRAID M5110e SAS/SATA Controller for IBM System x, onboard, any embedded
  • ServeRAID M5115 SAS/SATA Controller, Option part number 90Y4390, any Replacement part number (CRU)
  • ServeRAID M5120 SAS/SATA Controller for IBM System x, Option part number 81Y4478, any Replacement part number (CRU)

Note: This does not imply that the network operating system will work under all combinations of hardware and software.

Please see the compatibility page for more information: http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/

Solution

Follow this procedure to configure properly MegaRAID Storage Manager (MSM) in a Windows VM in ESXi 5.x:

VMware ESXi 5.0 IBM Customized Release MSM 12.05.03.00 For Windows or Linux
  1. Execute the following command from the ESXi shell:

      esxcli network firewall unload export LD Library Path=/usr/lib/CIM
    Network communication is a key element for a proper communication between the ESXi Common Information Model (CIM) provider and the LSI management software.

  2. Ensure that the network settings are correct by making the following changes:
    1. Provide a proper hostname and Internet Protocol (IP) address while doing the initial configurations for the ESXi host.
    2. Update the hosts file on the client to include the server information:

        For Windows:
      /Windows/system32/drivers/etc/hosts
      (For example: 192.168.70.10 esxi5.asasupport.com)

      For Linux:
      /etc/hosts
      (For example: 192.168.70.10 esxi5.asasupport.com)
  3. For networks that do not have Domain Name System (DNS) (or Dynamic Host Configuration Protocol (DHCP)) configured, the 'hosts' file in the machine on which the MSM is installed must be edited as follows:
    1. Add an entry to map the VMware host's IP address with the host name. This is for the discovery process to proceed correctly. In the absence of this entry, the VMware host would be discovered as 0.0.0.0.
    2. Add an entry to map the actual IP address of the localhost with its hostname (an entry for the loopback address would be present by default in the hosts file and it should not be removed). This is to ensure that the Asynchronous Event Notifications (AENs) are delivered correctly.

       

      For example, if 135.24.228.136 is the IP of the VMware host and 135.24.228.137 is the IP of the Linux host, the following entries must be added in the hosts file:

      1. 24.228.136 DHCP-135-24-228-136.lsi.com DHCP-135-24-228-136 #vmware
      2. 24.228.136 DHCP-135-24-228-136.lsi.com DHCP-135-24-228-136 #Linux
      c. After setting up the network settings execute the following on the ESXi shell:

        /etc/init.d/slpd restart /etc/init.d.sfcbd-watchdog restart
      d. Install MSM on your remote Windows or Linux computer.
      e. Start the MSM from a remote Windows/Linux machine that has the MSM installed in Complete mode.
      f. On the Host View window that appears, click the Configure Hosts button.
      g. Select Display all the systems in the network of the local server.
      h. Click Save Settings.
      i. A confirmation dialog appears asking users to confirm the settings. Click OK in the confirmation dialog to start the discovery process. The ESXi server appears in the list of found hosts as shown in the following figure:

        cogent_28095.esxi5.gif
      j. Apply Yes, and let it discover the host for 1 or 2 minutes. Once found, users will see the IP address and the host name in the list.

      Note: In the 'IPAddress' field of the Host View screen, users should provide the IP address of the local machine (can be the actual IP or loopback address) or the IP of any Windows/Linux machine that has MSM installed. Users should not provide the VMware ESXi host's IP here.
      k. Enter the root account name and password of the ESXi host in the 'User Name' and 'Password' fields respectively. Log in as root. It may take up to 4 minutes to log in to the host server.

The following are some of the differences in the MSM utility when managing a VMware ESXi server. These limitations apply to the system information exposed through the application:

  • Only the IP address and the host name are displayed. No support is available for the controller health information.
  • The MSM allows Common Information Model Object Manager (CIMOM) server authentication with the user ID and the password for VMware.
  • Access to VMware ESXi hosts is controlled based on user privileges. Only root users can have 'Full Access' while the non-root users can have only 'View Only' access.
  • Multiple root users can log in simultaneously using 'Full Access' mode to access the VMware ESXi server. Event logging support is available for the VMware ESXi operating system, but it works differently than the normal MSM framework mode.
  • The support for retrieving initial logs is limited to 30 events. Only those events that occur after a user logs in for the first time to an ESXi server appear in the event logger dialog.
  • System logs are not displayed.
  • The Save log feature is not supported; however, the 'Save Log as Text' is supported.
  • The View Log option allows users to view the logs saved in a text file on the event logger dialog.
  • Refreshing of the MSM Graphical User Interface (GUI) after any updates on the firmware is slower for a client connected to VMware ESXi hosts, compared to one (1) connected to a Windows/Linux/Solaris host.
  • It takes some time to discover the CIMOM servers. If users start the MSM client immediately after installing the MSM software (or restart the Framework service), they will not be able to discover any hosts in the network.
  • VMware ESXi is supported only in a complete installation of the MSM software; stand-alone, client-only, and server-only modes do not support VMware ESXi management.
  • VMware ESXi is supported on Windows Server, Red Hat Enterprise Linux (RHEL), and SUSE Linux.

Additional information

This information will be added to the MegaRAID Storage Manager User's Guide by 4Q13.

Applicable countries and regions

 


Document id:  MIGR-5092858
Last modified:  2013-04-29
Copyright © 2014 IBM Corporation