**************************************************************** LSI Corp. MegaRAID Storage Manager Release for Solaris10 x86/x64 **************************************************************** Release Date: 05/24/12 ====================== Release Version: 12.05.03.00 ============================ Supported Controllers ===================== 3Gb/s SATA+SAS HBAs: -------------------- LSI SAS 3041E-R LSI SAS 3081E-R LSI SAS 3442E-R LSI SAS 31601E 6Gb/s SATA+SAS -------------- LSI SAS 9207-8i LSI SAS 9207-4i4e LSI SAS 9211-4i LSI SAS 9211-8i LSI SAS 9212-4i4e LSI SAS 9212-4i4e LSI SAS 9217-8i LSI SAS 9217-4i4e This release note and the software that accompanies it are copyright (c) 2011, LSI Corporation or its suppliers, and may only be installed and used in accordance with the license that accompanies the software. This Software is furnished under license and may only be used or copied in accordance with the terms of that license. No license, express or implied, by estoppels or otherwise, to any intellectual property rights is granted by this document. The Software is subject to change without notice, and should not be construed as a commitment by LSI CORPORATION or its suppliers to market, license, sell or support any product or technology. Unless otherwise provided for in the license under which this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, or distributed by any means without the express written consent of LSI CORPORATION. ========= Attention ========= 1)MSM uses 5571 or 3071 as multicast listening ports, please make sure these ports are NOT blocked by firewall utility for MSM remote connection. 2)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 . Go to \ StrongSSLEncryption.ini . Modify the property SSL_STRONG_ENCRYPTION to .ENABLE. . 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) The MSM service,Framework will not start upon reboot if the /opt file system is mounted on a separate partition. This is because these services currently depend only on the network service which starts even before the other file systems are getting mounted. 2) The icons on the start menu will not appear immediately after the installation or upgrade of the package. The user has to logout and then login to use the icons. 3) In Solaris, location of Systemlog will depend upon the configuration available in the /etc/syslog.conf. 4) SNMP Trap integration is not done for this release. Additional steps has to be performed after installing Solaris SAS SNMP Agent, a) Edit LSI_StorSNMP.ini file located under /etc/lsi_mrdsnmp b) Search for the following line and change Y to N at the end of the line. ## Dat File Name ### Trap Dest. File Name## /etc/lsi_mrdsnmp/sas/sas_mib.dat etc/lsi_mrdsnmp/sas/sas_TrapDestination.conf N ======================= Contents on the package ======================= This package includes the Java Runtime Environment files as well as the MegaRaidStorageManager installation files. ========================= Installation Instructions ========================= Summary of Installation Steps: 1. Extract the files from the tar.gz. Note the package also contains the Java Runtime Environment (JRE) files that must be installed. 2. From the unpacked files, run ./install.sh. The installation path cannot be changed. Most files are installed to /opt/MegaRaidStorageManager with additional files added to /var and /etc. WARNING: If the *.sh files in the packages have Windows line breaks. Run the 'tr' command to convert the scripts before you install MSM. $> tr -d '\15\32' < existing_file_name > new_file_name $> chmod a+x new_file_name 3. This package supports only Complete installation mode. ====== 1. While installation the user has to provide the "y" option wherever the installation scripts prompts for the same. 2. To shutdown MSM Framework service, run "svcadm disable -t MSMFramework". 3. To startup the framework service run "svcadm enable MSMFramework". 4.If the service is in "maintenance" state, use "svcadm clear MSMFramework" 5. To check for the status of MSM services execute the command "svcs -a | grep -i 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" 5. Install MSM, if already installed then restart MSM framework. =========================== Uninstallation Instructions =========================== The product can be uninstalled by executing the "uninstaller.sh" file located in /opt/MegaRaidStorageManager directory. While uninstallaion the user has to provide the "y" option wherever the uninstallation scripts prompts for the same. Notes: 1. To shutdown MSM Framework service, run "svcadm disable -t MSMFramework". 2. To startup the framework service run "svcadm enable MSMFramework". 3.If the service is in "maintenance" state, use "svcadm clear MSMFramework" 4. To check for the status of MSM services execute the command "svcs -a | grep -i msm". ============================= SNMP Agent Usage Instructions ============================= 1. SNMP MIB: ------------ After installing SNMP Agent package, the MIB file "LSI-AdapterSAS.mib" is installed under /etc/lsi_mrdsnmp/sas directory. The MIB file for SAS IR "LSI-AdapterSASIR.mib" is installed under /etc/lsi_mrdsnmp/sasir directory. 2. Starting/Stopping/Status of SNMP Agent: ------------------------------------------ 1.) Following commands are used to start/stop the Solaris System Managment Agent(net snmpd) daemon Start : # svcadm enable svc:/application/management/sma:default Stop : # svcadm disable svc:/application/management/sma:default restart : # svcadm restart svc:/application/management/sma:default Status : # svcs svc:/application/management/sma:default NOTE: online indicates the SMA is started. disabled indicates the SMA is stopped. 2.) Following commands are used to start/stop SAS SNMP Agent daemon Start : #/etc/init.d/lsi_mrdsnmpd start Stop : #/etc/init.d/lsi_mrdsnmpd stop restart : #/etc/init.d/lsi_mrdsnmpd restart Status : #/etc/init.d/lsi_mrdsnmpd status 3.Configuring snmpd.conf: ------------------------- By default, snmp queries (walk,get) can be executed from any remote machine without any snmpd.conf file changes. To quickly add a new community and client access , please follow the following steps 1. stop the SMA service,by executing the following command # svcadm disable svc:/application/management/sma:default 2. Adding readonly and readwrite community names, To add readonly community name and client/hostname/ipaddress Under "SECTION: Access Control Setup" in /etc/sma/snmp/snmpd.conf file is shown below. Following is an excerpt from the /etc/sma/snmp/snmpd.conf file ########################################################################### # # SECTION: Access Control Setup # # This section defines who is allowed to talk to your running # snmp agent. # rocommunity: a SNMPv1/SNMPv2c read-only access community name # arguments: community [default|hostname|network/bits] [oid] rwcommunity snmpclient 172.28.157.149 ########################################################################### Similarly, To add readwrite community name and client/hostname/ipaddress Under "SECTION: Access Control Setup" in /etc/sma/snmp/snmpd.conf file is shown below. Following is an excerpt from the /etc/sma/snmp/snmpd.conf file ########################################################################### # # SECTION: Access Control Setup # # This section defines who is allowed to talk to your running # snmp agent. # rocommunity: a SNMPv1/SNMPv2c read-only access community name # arguments: community [default|hostname|network/bits] [oid] rwcommunity snmpclient 172.28.157.149 ########################################################################### 3. start the SMA service, by executing the following command # svcadm enable svc:/application/management/sma:default NOTE: Refer "man snmpd.conf" command for more information on configuring snmpd.conf file. 4.Configuring SNMP Traps: ------------------------- To receive SNMP traps, the following steps needs to be followed, 1.) stop SNMP Agent by executing the following command, #/etc/init.d/lsi_mrdsnmpd stop 2.) 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 2 #############Trap Destination IP################## 127.0.0.1 public 172.28.157.149 public ################################################# 3.) start SNMP Agent by executing the following command, #/etc/init.d/lsi_mrdsnmpd start 5.Configuring SNMP Traps: ------------------------- To receive SNMP traps, the following steps need to be followed 1.) stop IR SNMP Agent by executing the following command, #/etc/init.d/lsi_mrdsnmpd stop 2.) Edit /etc/lsi_mrdsnmp/sasir/sas_ir_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 2 #############Trap Destination IP################## 127.0.0.1 public 172.28.157.149 public ################################################# 3.) start SNMP Agent by executing the following command, #/etc/init.d/lsi_mrdsnmpd start 6.References: ------------- Please visit http://docs.sun.com/app/docs/doc/817-3000/introduction-1?a=view for more information on Solaris System Management Agent. 7. MSM Performance improvement ------------------------------- Symptoms a. MSM slow/hung during large configurations. b. MSM slow while running the TAS tool. c. Out of Memory Error. 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 (/opt/MegaRaidStorageManager). 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.... 8. Logo and Splash Screen Customization(Channel Customers) ----------------------------------------------------------- In order to help system builders redistribute MSM with their own logo and splash screen, user can provide the customized Logo & Splash screen file name by editing the file "msm.properties", present in folder. In the file "msm.properties" there are two key values which have no entry. Following are the keys: CHANNELLOGO= CHANNELSPLASHSCREEN= By default there are no values assigned for both these "Keys" and hence MSM uses the default LSI Logo and Splash screen. When system builders like to customize the Logo and Splash screen, they need to provide the Logo & Splash screen file name against these entries. Following are the steps which need to be followed to provide the filenames: 1) Open the file "msm.properties" in folder. 2) Make the entry for Logo file against the key "CHANNELLOGO" 3) Make the entry for Splash screen file against the key "CHANNELSPLASHSCREEN" 4) Save the file 5) Place the 2 images in folder. 6) Start the application. Notes: 1) File names for both entries should not have any spaces. For eg: valid file name would be: logo_test_1.png or LogoTest1.png or TEST_SPLASH_FILE.jpg 2) Logo image dimensions should not be more than 160 * 85 i.e width * height. 3) Splash screen image dimensions should not be more than 390 * 260 i.e width * height. After making above changes, when user logs into MSM, user should see changes with new splash screen and logo in MSM. ============ Known Issues ============ 1) When changing virtual disk properties, initial values for 'Write Policy' or for 'Write Thru for failed/missing Battery' may be different from the currently set values. Always check that the correct 'Write Policy' setting is selected before clicking 'Go' button. 2) Service management facility is introduced into the Solaris package by which the services will start and stop automatically if the system reboots. 3) 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. ============= 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 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 Enchancements: 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