****************************************************** LSI Corp. MegaRAID Storage Manager Release for Windows ****************************************************** Release Date: 05/23/12 ====================== Release Version: 12.05.03.00 ============================ OS Supported ============ Windows* 2000, Windows* 2003, Windows* XP, Windows* Vista, Windows* 2008, Windows* 7. This package can be installed on all x86 and x64 systems. 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 estoppel 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)MSM does not work on Longhorn Core 3)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) Users have to install Windows Installer 3.0 or above to install MSM on their machines. Here is the link to install Windows installer 3.0. http://www.microsoft.com/downloads/details.aspx?FamilyID=5fbc5470-b259-4733-a914-a956122e08e8&displaylang=en&Hash=XWGQj4dth%2f0C0XawhHybRR1RcAY9BfBRJiYTZWCYM5AMpqnvUT9q9zvYdbEZE0AC0H5guBKp%2biuLGqMH%2f0Xl%2fA%3d%3d 2) MSM will be supported starting from Windows 2000 Service Pack 3. Anything lower than this will not be supported. 3) Event logging feature for MSM client connected to a VMWare system behaves as follows a) There will be no support to retrieve initial logs (ie, the events that happened before a client logs in). Only those events that occur after a client logs in will be displayed in the event logger dialog. b) Save log feature will not be supported. However, the Save Log as Text will continue to be supported. c) View Log option will allow the user to view the logs saved in a text file on the event logger dialog. d) Localization is not supported e) The event descriptions may not be identical to a normal MSM client since we display whatever comes from the firmware. 4) Scan/Import IR RAID Foreign Configuration not working When all the drives are removed clear configuration wont appear. So foreign configuration should be tested removing only one drive without removing all of them. 5) 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. 6) In Windows, MSM upgrade from 11M05 releases (MSM v11.05.xx.xx) to 11M08 releases (MSM v11.08.xx.xx) fails. The work around for this issue are. 1. Uninstall 11M05 MSM (MSM v11.05.xx.xx) and install 11M08 MSM (MSM v11.08.xx.xx). 2. Upgrade 11M05 MSM (MSM v11.05.xx.xx) to 11M06 MSM (MSM v11.06.xx.xx) then upgrade to 11M08 MSM (MSM v11.08.xx.xx). 7) 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. ======================= Contents of the package ======================= This package includes the Java Runtime Environment files as well as the MegaRAID Storage Manager(MSM) installation files. The installer provides the user with five types of setup option apart from custom setup. 1. Complete - This option will install all program features. 2. Client - This option will only install components required to remotely view and configure servers. 3. Server - This option will only install components required for remote server management. 4. 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. 5. 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 does not multicast too to allow remote clients to discover. To, install the product in a non-interactive or silent mode, the user should use the commands. 1.Install the VC Redist Package from command line "vcredist_x86.exe /Q", vcredist_x86.exe is available in \DISK1\ISSetupPrerequisites\VC Redist Installation. 2.setup.exe /s /v"/qn SETUPTYPE="" [REMOVEUTIL="[,]"]" from the installation disk. The can be Popup,SNMP and can be StandAlone. The REMOVEUTIL option will remove the utility from install list. In Future, there will be more options for 3. If vcredist_x86.exe is already installed, run the command mentioned in the step 2. ========================= Installation Instructions ========================= See Detailed installation instructions below: 1. Extract the contents of the ZIP file and run Setup.exe from the Disk1 folder. If JRE is not already installed, the setup program will install the appropriate version and reboot. 2. Choose from four options: - Complete: Installs all features. - Client: Allows the local system to administer and configure all the RAID servers in the network, but not the local system. - Server: Allows the local server to be managed remotely. - StandAlone: Allows the local server to be managed only by itself. This installation can neither manage other servers nor allow other clients to manage this server. If you do not see the choices in #2, the program has determined you have a client only system with no LSI(R) SAS RAID controller installed or MSM was installed over a previous version and kept the same mode. If a security warning about "popup" appears, click "allow" if you wish to receive alerts. By default all Fatal and Critical events will be displayed by Popup. However, user can optionally add Popup for other types of events using Monitor Configurator. Windows 2000 note: Authentication requires the admin privilege setting. To enable, go to Program --> Administrative Tool --> Local Security Settings. Assign the policy "Act as part of operating System" to user (Administrator / Everyone). To start the utility, go to Start>Programs>MegaRAID Storage Manager and choose StartupUI. You will be notified if no supported RAID controllers are found. Silent install is available using the command: Setup.exe /s /v"/qn SETUPTYPE= where setuptype may be StandAlone, Client or Server. =========================== Uninstallation Instructions =========================== The product can be uninstalled using the shortcut "MegaRAID Storage Manager/Uninstall" from Start Menu. The product can also be removed from Add/Remove Program. The product can be uninstalled from command line using the below options. open the command prompt and cd to product home folder (C:\Program Files\MegaRAID Storage Manager). Execute uninstaller.exe as mentioned below Uninstaller.exe (For interactive mode of uninstallation) Uninstaller.exe -silent (for Silent uninstallation) NOTE: MSM does not work on Longhorn Core ======================================== How to configure SNMP Agent in Windows. =========================================== Step 1. Use SNMP Manager to retrieve the data (It is assumed that you have compiled mib files already). The mib files are available at the same location as setup.exe Step 2. Use Trap utility to get the traps. NOTE : Before you install the Agent, Make sure that SNMP Service is already installed in the system. ==================================================================================================== If you do not have SNMP Service installed on your system, Follow the following steps to install SNMP Service for Windows System. Steps to install SNMP Service in Windows 2003: Step 1. Select Add/Remove Programs from Control Panel. Step 2. Select "Add/Remove Windows components" in the left side of the "Add/Remove Programs" window. Step 3. Select "Management and Monitoring Tools". Step 4. Click Next and SNMP service installation will start. In-between the installation you will be prompted to insert Windows 2003 CD, once you provide the CD and click OK the SNMP installation will resume and SNMP Service will be installed on that system. Once Installation is done, it will display a message saying Installation is successful Steps to Configure SNMP Service on Server side Step 1. Select "Administrative Tools" from Control Panel Step 2. Select Services from "Administrative Tools" window. Step 3. Select SNMP Service in the "Services" window. Step 4. Open SNMP Service and go to its properties. Step 5. Goto "Security" tab and make sure that "Accept SNMP Packets from any host" is selected. Add a community with some keyword. Eg-“ public” Step 6. Goto "Traps" tab and the list of host IPs to which you want the traps to be sent with community name. Steps to install SNMP Service on Windows 2008: ============================================== Before you install the LSI Agent, Make sure that SNMP Service is already installed in the system. If you do not have SNMP Service installed on your system, Follow the following steps to install SNMP Service for Windows 2008 System. Step 1. Select Program and Features from Control Panel. Step 2. Click on "Turn windows feature on/off" to select the windows components to install. Step 3. Select Features in the left side menu. Step 4. Click on Add Features. Step 5. Select "SNMP Services". Step 6. Click on Next. Step 6. Click on Install and SNMP installation starts, You will be prompted for the Windows 2008 CD during the installation, Insert the CD and select OK, the installation will resume. Once Installation is done, it will display a message saying Installation is successful. Follow the below Steps to Configure SNMP Service on Server side on Windows 2008. Step 1. Select "Administrative Tools" from Control Panel Step 2. Select Services from "Administrative Tools" window. Step 3. Select SNMP Service in the "Services" window. Step 4. Open SNMP Service and go to its properties. Step 5. Goto "Security" tab and make sure that "Accept SNMP Packets from any host" is selected.Add a community with some keyword. Eg-“ public”. Step 6. Goto "Traps" tab and the list of host IPs to which you want the traps to be sent with community name. SNMP Trap Disable Functionality =============================== The SNMP Trap can be disabled either using custom setup or by using TRAPIND="N" as msiexec parameter. CIM Plugin 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) & host name for the indications to be supported. 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 (C:\Program Files\MegaRAID Storage Manager). 2. Open startupui.bat file in editable mode. 3. Include the command -Xms1024m -Xmx1024m after "JRE\bin\javaw", effectively: start JRE\bin\javaw -Xms1024m -Xmx1024m -Duser.country=US.... Note: -Xms1024m -Xmx1024m can be configured based on the server configuration ============ Known Issues ============ N/A ============= 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 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