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. ========================== 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-R spec,9211-8i/4i-R spec =================== Package Information =================== MSM version = 12.01.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. ========= 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 ================== 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). ======================= 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.01.03.00 Defects: 1)LSIP200229837 MSM shows two instances under Windows 2008 Uninstall window 2)LSIP200230158 Required Multilingual User Interface (MUI) support on e-mail functionality 3)LSIP200229835 MSM needs to update the Support Link and Help Link from http://www.LSICorp.com to http://www.LSI.com 4)LSIP200230243 MSM/Two different clients are able to login to the same server at the same time in NAT environment 5)LSIP200230253 MSM cannot configure alerts from Client over NAT 6)LSIP200230250 MSM does not connect to local server 7)LSIP200230247 MSM 12.01.02.02\Unable to send email after putting in SMTP server 8)LSIP200230221 Install MSM 12.01.02.02 and found log with errors 12.01.02.02 Defects 1)LSIP200229458 (RW LSIP200224028) MSM will not install or uninstall correctly without Run as Administrator being selected 2)LSIP200229741 MSM-ESXi Server does not discovery not successful via MSM 12.01.02.01 Defects 1)LSIP200224654 Need to update the readme file appropriately for receiving the SNMP traps in Solaris Sparc 2)LSIP200211685 MSM over NAT incurs major performance hit 3)LSIP200224508 The word "periodically" is misspell in the warning message for "Disable Automatic Learn Cycle" 4)LSIP200225012 MSM Next Learn cycle not showing correct value for DayLightSaving time Zone 5)LSIP200077225 MSM/SSM: Not displaying the power properties in DG page for spanned DG 6)LSIP200223752 SNMP query fails to report the updated adapter task rates(cc rate, recon rate,rebuild rate and bgi rate). 7)LSIP200225022 Defect created for check in the defect LSIP200225012 fix missed files 8)LSIP200224361 Physical tab and controller properties are disappearing from msm After creating VD for IR2 controller 9)LSIP200223341 If you enable security on controller using FOD and create secure VD it goes missing upon reboot 10)LSIP200224318 Enclosure Position number is incorrect in MSM after hotplug enclosure to port 4-7 11)LSIP200224509 MSM does not allow user to disable "Use LDAP Login" 12)LSIP200225104 MSM is causing Memory Leak in javaw.exe 13)LSIP200224971 Pressing OK button in the Manage SSD Caching it brings up the Update Controller Firmware option 14)LSIP200209208 MSM event log shows incomplete onboard "disk device ID" 15)LSIP200223176 (XB096122) MSM issue with email (SMTP) when multiple email recipients are set 16)LSIP200222216 MSM stops refreshing after drives are inserted or removed 17)LSIP200222456 Enclosure information is missing in SNMP walk 18)LSIP200224765 MSM JLogger showing wrong rescheduled time value for the "Periodic Battery Relearn was missed" event 19)LSIP200224772 SNMP queries not getting refreshed once enclosure is connected/removed. 20)LSIP200224166 MSM installer allows to proceed without entering LDAP details when"Do you wish to specify LDAP details" is selected 21)LSIP200224733 Warning message for BBU manual learn cycle contains misspell word 22)LSIP200224923 MSM reports "Battery is not being discharged" when the battery is discharging and "Operational" when in "Relearn" 23)LSIP200224317 JBOD drive creation didn't get update in MSM logical view 24)LSIP200224990 MSM-LSIP200224164-Uinstall MSM is not showing proper message 12.01.02.00 Defects 1)LSIP200222911 BBU next learn cycle did not get detected by MSM 2)LSIP200223761 MSM should not display 65535 minutes estimated recharge time when not charging 3)LSIP200222656 MSM 'Cannot create configuration: 3' 4)LSIP200221457 MSM does not display PD properties and Mouse Right Click not working for SATA PD in SPARC OS 5)LSIP200223621 SNMP for RHEL crashes with lsi_mrdsnmpd Service restart and enclosure push/pull . 6)LSIP200223606 Cannot reconstruct partial degrade R6 to R5 7)LSIP200223247 macon: on changing the rebuild rate the cache flush interval is also getting changed. 8)LSIP200223243 macon: the media error count in pd properties page doesn’t change unless we do a manual refresh 9)LSIP200224233 don’t allow user to set properties for TMMC nontransparent battery. 10)LSIP200224084 MSM fails to discover ESXi server 11)LSIP200224329 Defect created for Re-Scoped PR "LSIP200122939---Real Time Scheduler for Relearn" code check in 12.01.01.00 Defects 1)LSIP200222653 MSM show a PRL11 as a R1 instead of R10 with treatR1EAsR10 enabled. 2)LSIP200221325 Calendar needs to be implement more user friendly in BBU set properties Enable mode. 3)LSIP200221309 Manual and Automatic Panels are scrambling in the BBU Set Properties disable mode. 4)LSIP200222008 MSM allows user to select a PI enabled VD as Snapshot repository for non PI enabled VD 5)LSIP200223133 Resolve the known limitation of MSM on ESXi server - Event logging feature 6)LSIP200223086 Initial events are not logging on MSM - JLogger for ESXi server. 7)LSIP200221616 When Patrol Read is disabled, MSM does not gray out "Start Patrol Read" 8)LSIP200222516 No option to disable data protection on the spanned Drive Group but there is for single Drive Group. 9)LSIP200221462 SNMP shows incorrect Serial Number of Physical Drive 10)LSIP200222244 In MIB file "stripe size" parameter description is not correct which gives user a wrong interpretation for its value 11)LSIP200222251 SCGCQ00238704 - Device interface parameter values are not coming properly in MIB browser 12)LSIP200222255 SCGCQ00238494 - Raid level Qualifier parameter name is not coming correctly in MIB browser description. 13)LSIP200222256 SCGCQ00236725 - SNMP: Operation support description is not proper in MIB browser. 14)LSIP200221867 Unable to set CC, Patrolread ,BGI,Rebuild,Reconstruction Rates during SNMP query. 15)LSIP200222258 Instructions in readme file for receiving traps is inappropriate for SLES11. 16)LSIP200222596 SNMP Memory Leak 17)LSIP200222447 Set Learn Cycle Properties popup will not allow pressing OK to exit message 18)LSIP200149354 MSM Array creation wizard chooses write back always as it's default choice as opposed to write thru 12.01.00.00 Enhancements: 1) LSIP200211305 Request for MSM to display drive Serial number 2) LSIP200186453 add event ID to MSM email alerts 3) LSIP200122939 Real Time Scheduler for Relearn 4) LSIP200210377 SNMP to add missing drive properties 5) LSIP200211369 Change for SNMP agent to be able to send the trap to non default community 6) LSIP200186835 SLES 11 SP2 support for MegaRAID SAS products 7) LSIP200196753 RHEL 6.2 support for MegaRAID SAS products 8) LSIP200211358 OEL & OEL UEK 5.6, 5.7, 6.0 & 6.1 support for MegaRAID SAS products 9) SCGCQ00225872 WD controller specific attributes for SNMP 10) SCGCQ00225876 WD SNMP: Add DFF specific attributes 11) SCGCQ00225881 WD SNMP: Support SNMP Traps for WD events 12) SCGCQ00230455 Report the new Events for DFF temperature and power throttling Defects: 1) LSIP200221224 Delivering all changes done for 11M08_CCoH 2) LSIP200197399 (PR: LSIP200210377) Drive SN & FW information is missing >> PR LSIP200212342 (Amazon) 3) LSIP200212342 (PR: LSIP200211369) SNMP trap for custom community support for LSI MegaRAID controllers >> Subbu asked me to fix it as part of the defect 4) LSIP200212406 Defect to resolve version no conflicts of SNMP DC and Agent >> Used to resolve the version number conflicts with 2011 Q4 SNMP builds