MegaRAID Storage Manager(MSM) Installation ========================================== The kit contains both mode of installation. The interactive and non-interactive. To, install the product using interactive mode, the user should execute the command "./install.csh" from the installation disk. To, install the product in a non-interactive or silent mode, the user may use the command "./install.csh [-options] [ -ru popup]" from the installation disk. The options are: a, for Complete installation c, for Client Component Only s, for StandAlone l, for Local The "-ru popup" will remove popup from installation list. User may also run non-interactive installation using "RunRPM.sh" command. The installer provides the user with five types of setup option. 1. Complete - This will install all the features of the product. 2. Client Components Only - The storelib feature of the product will not be installed in this type of installation. As a result, the resident system will only be able to administer and configure all the servers in the subnet, but will not be able to serve as a server. 3. StandAlone - This option will only install components required for local server management. This system will not be discovered automatically by other MSM servers in the subnet and it will not discover other MSM servers in the subnet automatically. (multicasting will be disabled) But the system can connect to other MSM servers by providing the ipaddress in the hostview screen and can be connected by the other MSM clients in the subnet. 4. Local - This option will install only components required for local configuration. Will not allow other systems on the network to connect to this server and cannot connect to other servers. This MSM installation mode only uses the loopback interface. 5. Server - This option will only install components required for remote server management. The installation will help the user to select any of the setup type, but if the user directly run "RunRPM.sh", it will install the complete feature. NOTE: 1. For RHEL 5, it is necessary to install compat-libstdc++ version 33-3.x before installing rpm. 2. For SLES-10 SP3 64bit OS, it is necessary to install libstdc++33-32bit-3.3.3-7.8.1.x86_64.rpm before installing MSM. This RPM is available in the OS DVD (path is /media/SUSE-Linux-Enterprise-Server_001/suse/x86_64) 3. For SLES-9 32bit OS, it is necessary to install compat-libstdc++-lsb-4.0.2_20050901-0.4.i586.rpm before installing MSM. This RPM is available in the OS DVD (path is /media/dvd/suse/i586) 4. For RHEL 3, it is necessary to install the RPM libstdc++34-3.4.0-1.i386 before installing MSM. 5. It is necessary to enable shadow password in RHEL 6 to login to MSM. 6. Prerequisites for installing MSM on RHEL6.0 x64 operating system Before installing MSM on RHEL6.0 x64 system, Please install the following rpms, Without these files/RPM's MSM may not be install properly or may not work as expected. libstdc++-4.4.4-13.el6.i686.rpm compat-libstdc++-33-3.2.3-69.i686.rpm libXau-1.0.5-1.el6.i686.rpm libxcb-1.5-1.el6.i686.rpm libX11-1.3-2.el6.i686.rpm libXext-1.1-3.el6.i686.rpm libXi-1.3-3.el6.i686.rpm libXtst-1.0.99.2-3.el6.i686.rpm Also note that RHEL6.0 complete OS installation is required for MSM to work. The above mentioned rpm's come as part of RHEL6 OS DVD. These RPM's may need additional dependent RPM's as well, all the dependent RPM's also must be installed on the target system. 7. Net-SNMP rpm installation is required before we install agent rpms. RHEL 4.8: net-snmp-5.1.2-18.el4.x86_64.rpm net-snmp-utils-5.1.2-18.el4.x86_64.rpm RHEL5.4 lm_sensors-2.10.7-4.el5.x86_64.rpm net-snmp-utils-5.3.2.2-7.el5.x86_64.rpm net-snmp-5.3.2.2-7.el5.x86_64.rpm RHEL 5.3 lm_sensors-2.10.7-4.el5.x86_64.rpm net-snmp-5.3.2.2-5.el5.x86_64.rpm net-snmp-utils-5.3.2.2-5.el5.x86_64.rpm RHEL 5.5 net-snmp-5.3.2.2-9.el5.x86_64.rpm net-snmp-utils-5.3.2.2-9.el5.x86_64.rpm SLES 11 net-snmp-5.4.2.1-8.1.x86_64.rpm perl-SNMP-5.4.2.1-8.1.x86_64.rpm 8. In case you are unable to install lsi snmp agent rpms, use rpm -ivh --force *.rpm and then you can uninstall the lsi rpms using rpm -e *.rpm. 9. In case of problems with installing multiple rpms and get into cyclic redundancy issue, one can install all rpms in one command line. (Example: rpm -ivh net-snmp-5.4.2.1-8.1.x86_64.rpm perl-SNMP-5.4.2.1-8.1.x86_64.rpm) 10. For VMware 3.5, it is necessary to install libstdc++34-3.4.0-1.i386.rpm before installing MegaRAID Storage Manager(MSM). The rpm can be downloaded from http://rpm.pbone.net/index.php3/stat/4/idpl/1203252/com/libstdc++34-3.4.0-1.i386.rpm.html. 11.For VMware 4.1, it is necessary to create a softlink as mentioned below before installing MegaRAID Storage Manager(MSM). Run the below command to create the necessary soft link required for MegaRAID Storage Manager(MSM) to work. "sudo ln -sf /lib/libgcc_s.so.1 /usr/lib/vmware/lib/libgcc_s.so.1" ========= Attention ========= 1) From MR5.3 MSM is added with 256 bit encryption and this option is disabled by default from factory. The end user(s) who needs to enable 256 bit encryption is\are expected to perform the below steps 1.Go to \ StrongSSLEncryption.ini 2.Modify the property SSL_STRONG_ENCRYPTION to "ENABLE" 3.Restart the MSM Framework Warning : Please be aware that enabling 256bit encryption would restrict the user from communicating with the previous versions of MSM due to the higher Vs lower bit encryption handshake in the communication channel. ================== Known Restrictions ================== 1) Latest LSI MegaRAID Storage Manager for Windows/Linux/Solaris is using an expired SSL certification (it was expired in Aug 18, 2009). Though MSM is not a Web-based application, MSM uses the Socket connection over SSL to handshakes only with the legitimate clients of its own using the proprietary key files which were generated using java's key tool with the limited life time. Though it has been identified as an issue as the key was expired, this is not a constraint to end-user anymore. The renewal of "vivaldikey" , "server.cert" and "server.key" needs to be done with both client and Framework i.e. if we renew the key in both the client and Framework the latest version of the MSM will not work with earlier versions of the Framework which implies a limitation in the deployment environment.In LSI MegaRAIDStorageManager MSM GUI, MegaPopup acts as Client and Framework act as Server. Prerequisite for MSM installation: ================================== MSM installation scripts also installs the LSI SNMP agent rpm. The LSI SNMP agent application depends upon standard SNMP Utils package. Please ensure that the SNMP-Util package is present in the system before installing MSM. SNMP-Util package includes the rpm.s net-snmp-libs , net-snmp-utils and additional dependent RPM.s. Please make sure that these RPM.s are installed from the OS media before installing the MSM. Prior to install MSM, check for existence of libstdc++.so.5 and libstdc++.so.6 librareis are present in /usr/lib directory. If not present/ installed, then install the Linux software component RPM that provides these libraries. These RPM's will be available in the OS DVD. Prior to executing install.csh, check for existence of /bin/csh. If not present/ installed, then install the Linux software component RPM that provides /bin/csh. Suppose Lib_Utils rpm is already installed on the target system, irrespective of the version of the MSM, uninstall the Lib_Utils rpm and then install MSM. Prerequisites to run MSM remote admin ====================================== 1. Configure the system with valid IP address. Make sure there is no IP address conflict with in the sub network. 2. Ports such as 3071 and 5571 are open and available for MSM framework communication. 3. Disable all security manager and firewall. 4. Configure the multicasting, make sure class D multicast IP addresses are registered (at least 229.111.112.12 should be register for MSM to work), if not create static route using the following command: route add 229.111.112.12 dev eth1. Note that this command will not modify the routing table to be persistent across reboots. Please follow the guidelines per operating system to add the above mentioned IP address as a static entry into the routing table to be persistent across reboots. You may wish to add the entire range of IP addressess (224.0.0.0 through 239.255.255.255) into the routing table. Please note that this requires procedures that varies between different flavours and versions of operating system and may have security implications. 5. Install MSM, if already installed then restart MSM framework. CIMPlugin Support ================= In case of networks that doesn't have DNS configured, the .hosts. file of the systems where MSM is installed must be manually edited to map the IP address & the host name of your CIMOM server. In addition, it should also have a mapping of its own IP address (not the loop back address) and host name for the indications to be supported. MSM Uninstallation ================== The product can be uninstalled using "Uninstall" short-cut created in Program menu. The user may also directly run the script "/usr/local/MegaRAID Storage Manager/uninstaller.sh" to uninstall MSM. Notes: 1. MSM upgrade is supported in this release. In other word, this release can be upgraded by future releases. 2. To shutdown MSM Framework service, run "/etc/init.d/vivaldiframeworkd stop". 3. "Any kernel upgrade requires restart of the MSM Framework and Services" for example, RedHat Linux command to reload or restart network (login as root user): To start Linux network service: # service network start Debian Linux command to reload or restart network: # /etc/init.d/networking restart ========================== Supported RAID Controllers ========================== This download supports the following controllers LSI MegaRAID: MegaRAID SAS 9240-4i/8i,MegaRAID SAS 9260-4i/8i/16i,MegaRAID SAS 9261-8i,MegaRAID SAS 9280-4i4e,MegaRAID SAS 9280-8e,MegaRAID SAS 9280-16i4e, MegaRAID SAS 9280-4i4e,MegaRAID SAS 9265-8i,MegaRAID SAS 9285-8e,MegaRAID SAS 8704EM2,MegaRAID SAS 8708EM2,MegaRAID SAS 8880EM2,MegaRAID SAS 8888ELP LSI HBA:LSI SAS3041E-R,LSI SAS3041X-R,LSI SAS3080X-R,LSI SAS3081E-R,LSI SAS3442E-R,LSI SAS3442X-R,LSI WarpDrive SLP-300,9212 4i4e spec,9211-8i/4i spec ******************************************************************** LSI SNMP agent for Linux ******************************************************************** Installation procedure for LSI SNMP Agent(For SUSE and Red Hat Linux) -------------------------------------------------------------------------- 1. LSI SNMP Agent rpm's installs the agents. 2. rpm will take care of the necessary modification needed in the snmpd.conf file for running the agent. [ NB: Before installation please check,there is any pass command starts with 1.3.6.1.4.1.3582 OID in snmpd.conf, if available then delete all the old pass commands starts with 1.3.6.1.4.1.3582 OID. (This could be possible if there is any previous LSI SNMP Agent was installed in the system) ] 3. The snmpd.conf file structure should be same as lsi_mrdsnmpd.conf. For reference,a sample conf file (lsi_mrdsnmpd.conf) will be there in the /etc/lsi_mrdsnmp directory. 4. For running SNMP query from a remote m/c add the ip address of that m/c in the snmpd.conf file like this.. com2sec snmpclient 172.28.136.112 public Here ipaddress of the remote m/c is 172.28.136.112 5. For receiving snmp trap to a particular m/c, add the ip address of that m/c in the com2sec section of snmpd.conf file. For example, to get Trap in 10.0.0.144, then add following line to snmpd.conf. # sec.name source community com2sec snmpclient 10.0.0.144 public 6. To Run/stop the snmpd daemon. /etc/init.d/snmpd start/stop 7. To start/stop the SNMP Agent daemon before issuing any snmp query. /etc/init.d/lsi_mrdsnmpd start/stop 8. Status of the SNMP Agent daemon can be checked by issuing the following command... /etc/init.d/lsi_mrdsnmpd status 9. You can issue snmp query like this... snmpwalk -v1 -c public localhost .1.3.6.1.4.1.3582 10. You can get the snmp trap from local m/c by issuing the following command... snmptrapd -P -F "%02.2h:%02.2j TRAP%w.%q from %A %v\n" 11. For SLES-11 platform, please follow the below steps to configure traps. Edit /etc/lsi_mrdsnmp/sas/sas_TrapDestination.conf file & add ipaddress as shown below. ################################################# # Agent Service needs the IP addresses to sent trap # The trap destination may be specified in this file or # using snmpd.conf file. Following indicators can be set # on "TrapDestInd" to instruct the agent to pick the IPs # as the destination. # 1 - IPs only from snmpd.conf # 2 - IPs from this file only # 3 - IPs from both the files ################################################# TrapDestInd 3 #############Trap Destination IP################## 127.0.0.1 public 172.28.157.149 public ################################################# NOTE: For SNMP components to work, it is necessary that linux system should have snmp-net packages(rpm) to be already present. It is assumed that snmpd.conf is located at /etc/snmp for Redhat and /etc for SuSE. Anyway, user can change the file location from /etc/init.d/lsi_mrdsnmpd file It is neccessary to uninstall all the previous version before installing a new version. The rpm has not been created to support -U version. The rpm -U is most likely to fail with this rpm. SNMP Trap Disable functionality =============================== User may disable SNMP Trap functionality using "-notrap" as install(install.csh) parameter. MegaRAID Storage Manager(MSM) Installation on VMware : ====================================================== To, install the MSM on VMWare operating system, the user should execute the command "./vmware_install.sh" from the installation disk. The installer provides the user to choose the License agreement,operating system and storelib to be used as mentioned below. 1. End user license agreement. 2. Operating system (VMware 3.5 or VMware 4.0). 3. Select the Storelib (Inbox Storelib or Storelib from MSM package). Note: 1. LSI SNMP Agent is not a supported configuration on VMware Operating system (VMware 3.5 or VMware 4.0). 2. There is a possibility that the MSM Framework that runs on the host from which the GUI is launched misses to discover an ESXi host in the subnet, while some other MSM Framework in the same subnet succeeds to discover it. In that scenario, all the communications to the ESXi hosts happens through the latter MSM Framework. This will result in MSM GUI not receiving events from the ESXi host. 3. On some Windows machines it has been seen that the discovery of VMWare ESXi servers fail as a result of a bug in the 3rd party application that is used for discovery. This is actually caused by one of the windows servers in the network which contains a service called IBM SLP SA, which gets installed along with IBM Director. If we stop this service on all the windows servers in the network, MSM will be able to discover all the ESXi servers. 4. Ensure that on a 32 bit or on a 64 bit VMware operating system, you install the 32 bit MegaRAID Storage Manager software. MegaRAID Storage Manager(MSM) Uninstallation on VMWare : ====================================================== The MSM can be uninstalled by running the script "/usr/local/MegaRAID Storage Manager/uninstaller.sh". Note: ===== When the user runs the MegaRAID Storage Manager(MSM) installation script install.csh, the rpm's and will be installed, These RPM's install the third party libraries and MSM is dependent on these libraries.If you uninstall the libraries installed by these RPM's then other applications that are dependent on these libraries may not function correctly. Hence these RPM's will not be removed when MSM is uninstalled. If you want to remove the RPM, run the command Rpm -e and Rpm -e . If older version of the libutil rpm is installed on the system, please uninstall the older version of the RPM using the command "rpm -e " and then install the latest libutil rpm packaged in this zip file. MSM Performance improvement =========================== For better performance of MSM, when subjected to any heap-intensive (say heavy IOs) or computational tasks,improve the heap by including the following command "-Xms1024m -Xmx1024m",where 1024m Size of the heap allocated. The specified size is dependent on the machine's Hardware configuration. -Xms1024m Sets the initial size of the Java heap to 1024 Mbytes -Xmx1024m Sets the maximum heap size to 1024 Mbytes 1. Goto product home folder (/usr/local/MegaRAID Storage Manager). 2. Open startupui.sh file in editable mode. 3. Include the command -Xms1024m -Xmx1024m after "./jre/bin/java", effectively: LD_LIBRARY_PATH=$MSM_HOME/lib ./jre/bin/java -Xms1024m -Xmx1024m -DVENUS=true.... ============= Fixes/Updates ============= 12.05.03.00 Defects: 1)LSIP200232643 MSM displays Protected CacheCade feature MSM 12.05.02.01 Defects: 1)LSIP200232567 Copy Back Progress String needs to be Modified as a Replace Drive in Progress panels for TB and Invader Cards. 2)LSIP200232427 Wireshark logs says SSLV2 for latest MSM v-12.05.01.00 12.05.02.00 Defects: 1)LSIP200231801 MR5.3 MSM: Flash size in the controller property is shown as NA for WD card 2)LSIP200232283 UG drive shows emergency hotspare status when Emergency Hotspare for UG drives is disabled. 3)LSIP200232196 Dummy Defect - Resolving compilation error due to merge. 4)LSIP200232022 MSM 12.05.01.00 cannot update latest firmware image due to change in package size 5)LSIP200231367 MSM deletes the VD when select to discard cache from the access blocked VD 6)LSIP200231608 MSM allows user to create SSC VD with more than 512GB but does not provide any warning message 7)LSIP200231870 SNMP Services do Not Restart after System Reboot. 8)LSIP200231819 MR5.3 SNMP/MSM: SNMP displays invalid values for some of the WD attributes 9)LSIP200231868 SSL_STRONG_ENCRYPTION enabled by default 10)LSIP200232414 MSM Does not Allow Configuring DS3 when DS1 and DS2 is disabled and DS3 is Enabled 11)LSIP200232223 Serial Number displayed wrong while SNMP query for ThunderBolt Controller 12)LSIP200232058 Unable to start PR with Set PR Properties when one of the VDs is in degraded state. 13)LSIP200232268 LDAP Settings not getting saved When MSM is relaunched. 14)LSIP200232215 mfcdefaults should not be NULL check codition is not required for populating Manage power save settings Menu in MSM 15)LSIP200231800 MR5.3 MSM: NVRAM size is displayed as NA though NVRAM is present 16)LSIP200232469 SSL Security needs to be modify 17)LSIP200230839 OCR becomes disabled when changing controller rates in MSM 18)LSIP200232473 Defect to check-in modified readme file for Linux SNMP-IR agent 19)LSIP200230822 Mib version is showing different from the version mentioned in release note. 20)LSIP200232484 MSM 12.05.01.00/Is displaying copyback in certain areas and should say replace drive. 21)LSIP200232495 MSM is displaying Copyback in events, string to be changed to Replace Drive Operation 12.05.01.00 Defects: 1)LSIP200231260 Prepopulated CacheCade VD Name is using different format between VD0 and VD1. 2)LSIP200231690 Error when loading the lsi_adaptersas MIB 3)LSIP200231557 MR5.3: Misspelling of 'acyivation' in MSM's "Activate MR Advance Software..." Window 4)LSIP200231075 MSM CC2.0 warning message is not valid with RAID0 in WB mode 5)LSIP200231261 Prepopulated CacheCade VD name is larger than 15 characters allowed. 12.05.00.00 Enhancements: 1)LSIP200222486 Integrate CCoH MSM, SL (?SL-IR?), & CLI changes back into mainstream release Defects: 1)LSIP200231073 Full init option is available from MSM when creating a PI enabled R60 VD 2)LSIP200230992 (Defer LSIP200230313) MSM/UG drive shows emergency hotspare status when Emergency Hotspare for UG drives is disabled. 3)LSIP200231259 MSM local mode installation can connec to another system with complete installation 4)LSIP200230941 MSM crashed on Windows 2008 R2 when doing a refresh 5)LSIP200231240 MSM monitor configure alert menu has restore default option which does not function correcly. 6)LSIP200231356 MSM reports "Login failed: Exception while login!" when logging into VMWare ESXi 5.0 server 7)LSIP200231056 5.3 Alpha MSM on Linux fails to set CC schedule: "The requested command has invalid arguments" 8)LSIP200231274 MSM does not allow start PR on optimal VD, while another VD is rebuild state. 9)LSIP200230713 (Defer LSIP200225204) Unable to display CopyRight String in Windows SNMP 10LSIP200231078 MSM displays invalid VD number in the AEN when SSD caching is disable on the VD 11)LSIP200230997 MSM does not sort the events by date/time correctly 12)LSIP200231055 MSM fails to restore SSD Caching back to original "Enabled" state after loading original configuration file. 13)LSIP200229461 (RW LSIP200224318) Enclosure Position number is incorrect in MSM after hotplug enclosure to port 4-7 14)LSIP200231455 Remaining Capacity for SuperCaP in SNMP-MIB is different than in MSM 15)LSIP200231241 Pause for password at boot time cannot be disabled from MSM 16)LSIP200231243 Enabled pause for password at boot time is not reported by MSM without restarting the app 12.02.01.01 Defects: 1)LSIP200230348 SNMPWalk displaying OID's of only one controller and Copyright is not displayed. 2)LSIP200230397 PD serial numbers are showing incorrect. 3)LSIP200230084 MSM error message for medium error is not clear on which port/drive is having the medium error 4)LSIP200230454 Copyright is missing in SNMP walk. 5)LSIP200230615 lsi_mrdsnmd service does not stop . 6)LSIP200230616 SNMP Crashes with querying of CopyRightinfo . 7)LSIP200229662 MSM always displays "0-0-0" for "Diagnostics Complete Date" on DIF drives 12.02.01.00 Enhancements: 1)LSIP200105050 Get rid of dependency on 3rd party libs 2)LSIP200200133 Limit lower boundary of SSL encryption to 128bit 3)LSIP200200134 Use SSLv3 or hire protocols in MSM 4)LSIP200186835 SLES 11 SP2 support for MegaRAID SAS products 5)LSIP200200340 RHEL 5.8 support for MegaRAID SAS products 6)LSIP200222736 MSM Support for Solaris 11 7)LSIP200222728 Port MSM to JRE 7 for Solaris 8)LSIP200200313 MSM Popup Installation in /etc/profile should change for Solaris 11 Defects: 1)LSIP200230174 MSM showing "Battery State" as Operational for Non-Operational battery also