This release note and the software that accompanies it are copyright (c) 2012, 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 = 13.04.03.01
OS supported = Windows* 2000, Windows* 2003, Windows* XP, Windows* Vista, Windows* 2008, Windows* 7, Windows* 8
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
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 <MSM_HOME>\ 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) 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.
4) 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.
5) 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).
6) 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.
7) Japanese translation issue – In Windows/Solaris: Using JRE1.7 even though the system locale is set to "Japanese (ja)",
JRE 1.7 is returning the system locale as "en", which is not seen in JRE1.6.
Because of this reason even though the user modifies the system locale to "ja", MSM still displays all the text, events in "English" language.
Work Around for over coming this issue:
1)Open "startupui" file located at "$MSM_HOME" directory.
2)Modify the run time argument -Duser.language from en to ja.
Ex: -Duser.language = ja
Note: This issue has been filed against the JRE and has been resolved in JRE1.8
Refer http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7073906
8) sfcb timeout socket error in CIMOM server results in AEN blocked by sfcb-cimom and may lead to duplicate entries in client with incorrect
event description. To get rid of this, user is required to restart sfcb service in VMware ESXi.
Command to restart : /etc/init.d/sfcbd-watchdog restart.
The same has been raised against VMware. Refer to the link further details
[https://www.vmdev.net/tracker/tracking/linkid/prpl1235/remcurreport/true/template/ViewIssue.vm?id=LSDM89&readonly=true]
=======================
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 <Package_Dir>\DISK1\ISSetupPrerequisites\VC Redist Installation.
2.setup.exe /s /v"/qn SETUPTYPE="<setuptype>" [REMOVEUTIL="<util1>[,<util2>]"]" from the installation disk. The <util> can be Popup,SNMP and <setuptype> can be StandAlone. The REMOVEUTIL option will remove the utility from install list. In Future, there will be more options for <util>
3. If vcredist_x86.exe is already installed, run the command mentioned in the step 2.
=========================
Installation Instructions
=========================
See Detailed installation instructions below:
1.Log in to the system as an administrator or as a user with administrative privileges.
Depending on the operating system and security settings, it may be necessary to
install MSM using administrative rights. This may require that, log in as administrator and run the installer,
or open a command prompt as administrator and run the installer via the command line,
or right click on the setup.exe and select “Run As Administrator”.
2. 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.
3. 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=<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
=============
13.04.03.01
Defects:
MR 5.7
1)SCGCQ00414983 SWR - User can login MSM without giving the credentials in SLES 11 SP2 64 bit in THOR_RX300_S7 Server
2)SCGCQ00402226 MSM is not dynamically reporting configuration changes and events when connected to VMWare
13.04.03.00
Defects:
MR 5.7
1)SCGCQ00400298 System logs contains junk characters in event description when system locale is set to Japanese.
2)SCGCQ00402020 MSM 13.04.02.01/Loss of connection occurrs will connected to a server and accidetly put in an IP that does not exist
3)SCGCQ00400381 Update Controller Firmware dialog disappears sometimes.
4)SCGCQ00341934 Invader: MSM is not showing drop down list to change the Cachecade VD properties
5)SCGCQ00399634 MSM not sending emails for events that occur on VMWare host
6)SCGCQ00400146 MSM displays incorrect "Date of Manufacture" for BBU
7)SCGCQ00401437 MSM 13.04.02.01/MSM is not showing the estimated time left during a rebuild under show progress.
8)SCGCQ00400523 MegaRAID CacheVault Unlimited (Unsupported) Factory Installed (Unsupported) on an IBM controller in Advanced Software Options
9)SCGCQ00400407 Incorrect data in view server profile
10)SCGCQ00327336 MSM provides conflicting messages in popups for patrol read possibilities
MR 6.0
1)SCGCQ00398394 MSM:PR property settings windows does not pop up in Win server 2012 OS
HAMR
1)SCGCQ00402871 Latest release MSM_13.04.02.01 flicker way too long during auto refresh
2)SCGCQ00399362 MSM is not response and display NA when pull out multiple drive and put back for rebuild
13.04.02.01
Defects:
MR 5.7
1)SCGCQ00341934 Invader: MSM is not showing drop down list to change the Cachecade VD properties
2)SCGCQ00393485 CC 2.2: MSM shows the tape device type as "Unknown" and device ID as "0"
3)SCGCQ00394764 VD name displayed incorrect in server profile.
4)SCGCQ00369550 MSM Framework hangs on creating more than three globalhotspares in Solaris sparc 10 OS
5)SCGCQ00360810 MSM no longer reports External Port A or B and Position 1 or 2 on the errors
6)SCGCQ00375632 Title missing for popup with text message a test email was sent to selected recipients
MR 6.0
1)SCGCQ00396301 Unable to resume rebuild in MSM
MR 6.1
1)SCGCQ00390580 MSM reports failure to run instant secure erase on a locked FDE drive
HAMR
1)SCGCQ00394979 MSM in peer server is not refreshing After configuration related operations
13.04.02.00
Enhancements:
MR 5.7
1)SCGCQ00348865 NMR1.5 HSW merge to MR5.7 HSW
2)SCGCQ00353469 Nytro XD 1.5 storCLI commands to be merged with MR 5.7
MR 6.1
1)SCGCQ00383877 Removal of VD creation date info in MSM/RWC2
HAMR
1)SCGCQ00323031 Add Support for OEM HA-DAS product
Defects:
MR5.7
1)SCGCQ00362448 MSM - RWC2 Individual event descriptions for MR_Monitor are unclear and out of order
2)SCGCQ00369098 MSM 12.08.03.03 with BGI progress
3)SCGCQ00377449 CC2.2: MSM is showing irrelevant message pop up when trying flash 16MB image
4)SCGCQ00204125 WDMSM: Somtimes wrong Storelib version is displayed under server info for MSM on ESX.
5)SCGCQ00385106 MSM - RWC2 Individual event descriptions for MR_Monitor are unclear and out of order
6)SCGCQ00392547 MSM should not show Elapsed Secs for PD/VD progresses
MR 6.1
1)SCGCQ00380183 Progress bar is not completely updating to 100% in copyback.
2)SCGCQ00373405 PERC9: MSM provides an option to create the virtual drive of strip size 8KB
3)SCGCQ00380064 Wrong spanned drive group size is displayed in MSM
4)SCGCQ00376251 Start patrol read option is missing in a particular scenario
5)SCGCQ00383345 iMR_MSM:Online capacity expansion is not successful after rebuild of global hot spare
13.04.00.00
Enhancements:
MR5.7:
1)SCGCQ00319011 Rebuild time reset
2)SCGCQ00360919 Red Hat Enterprise Linux 5.9 Support
3)SCGCQ00360926 VMware 5.0 Update 2 Support
4)SCGCQ00336441 Need to validate the absolute value on Controller set time
HAMR:
1)SCGCQ00323031 Add Support for OEM HA-DAS product
Defects:
HAMR
1) SCGCQ00353990 After clear configuration from any of the server,Refresh of device tree is taking more time.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.