RAID Monitoring and Configuration with an Intel or LSI RAID Card
Intel and LSI RAID cards provide tools for RAID system monitoring and configuration. There are various CLI and GUI tools which can be used when an operating system is running, as well as RAID BIOS tools which can only be used when the operating system is not running.
The most useful GUI tool is the Intel RAID Web Console 2 (or, LSI MegaRAID Storage Manager (MSM), which is in essence the same product). This tool can be installed on a Windows based system and provide health reporting, alerting and configuration functionality for the local system as well as remote systems.
VMWare ESXi does not support the installation of GUI utilities directly on the host, or into the VMWare VCenter server or VSphere client. However, the Windows RAID Web Console 2 (RWC) installed onto a separate physical Windows system, or running on a Windows Guest operating system inside the VMWare ESXi host, can connect to management agents installed inside ESXi.
Downloads - you will need:
You should now have the following links or shortcuts, or similar, on your Windows desktop:
(You may have links to the VMWare web client or VSpere client on this guest or physical machine, but these can be located on a different machine).
esxcli software vib install -v /tmp/vmware-esx-provider-lsiprovider.vib --no-sig-check
esxcli software vib list
To disable the firewall
esxcli network firewall set --enabled false
esxcli network firewall set --enabled true
The Intel RWC 2 / LSI MSM software prefers to use multicast requests, although in RWC2 version 12 and MSM version 5.3 this was apparently fixed. ESXi will only respond to unicast requests.
When you have been able to Discover the Host, you should be able to login. The username and password required are the root username and password of the ESXi Host.
The Intel RWC 2 / LSI MSM connected to an ESXi host allows you to carry out most normal function, including drive rebuilds, hot-spare configuration, and even Firmware updates (although, as with a Windows system, this requires a reboot to take effect). You can also configure email alerting.
Some of the logging options are reduced. For example, controller events that occur before the SMIS provider has loaded inside ESXi are not available.