2.91-03_Linux_MSM.txt Driver File Contents (LSI_MSM_Utility_Win_291-05.zip)

****************************************************

LSI Logic MegaRAID Storage Manager Release for Linux

****************************************************

Release Date: 03/05/09
======================


Supported Controllers
==================

MegaRAID SAS 8704ELP
MegaRAID SAS 8704EM2
MegaRAID SAS 8708ELP
MegaRAID SAS 8708EM2 
MegaRAID SAS 8880EM2
MegaRAID SAS 8888ELP


Component:
=========
SAS MegaRAID MSM Linux
Release Date: 03/05/2009


Version Numbers:	MSM
===============		=====	
Current Version		2.91-03
Previous Version	2.90-01


Bug Fixes and Enhancements:
===========================
LSID100101584 	"Concurrent" option of "Scheduled Consistency Check" is invalid
LSID100101108	MSM Framework Service on SLES10 Must Be Restarted to Connect from Remote Windows Machine
LSID100099907 	MSM services fails on every reboot on a standalone server on Solaris OS.
LSID100101109 	Change Security Key Settings Next Button Disabled
LSID100101829 	Upgrading from MSM 2.77 to 2.90 Failure
LSID100091075 	8K and 64k stripe size option in RMU-SWR 
LSID100100491 	MSM CIM plug-in to get loaded on RHEL5 system
LSID100101583 	Scheduled Consistency Check" stops unexpectedly.
LSID100101741 	MSM is not allowing to configure Global Hotspare when more that one VD is present
LSID100095211 	Remove status dots in physical & logical views
LSID100106552	ROOT user is the only user that has FULL access Change Order
LSID100101079	Expander enclosures not visible in MSM
LSID100095891	Java process of MSM occupies CPU resource in Linux RedHat5.1.
LSID100107565	MSM process forced to go down by the IO trafic fragility test(DoS Attack).
LSID100093589	MSM - Use localhost if NO network is found
LSID100101620	Under RHEL 5.1 EM64T doesn't see any RAID controller 
LSID100106622 	(CO) CR_Ref# LSID100101862: SMARTer with SSD 
LSID100107134	Scan for Foreign Config does not  work with a drive in Spun Down State.
LSID100106999	Junk Chars displayed in the warning msg of Foreign config import screen
LSID100106586	MSM max VD exceeded
LSIID100099772	MSM 2.89 failed to create GHS during  rebuild on R1 & raid 6 together.
LSID100106939	Write Through for Failed/Missing Battery Always = No
LSID100108145	Typo in GHS coverage warning dialog box
LSID100107135	Mnemonic ALT+A does not work in Reconst screen
LSID100108025	Read me in MSM version 2.91 gives wrong Information
LSID100101081	Write-Thru for failed/missing battery" setting displayed incorrectly
LSID100108482	MSM causes “Controller Properties corruption” when user changes controller setting.


Component Features: 
==================
1.	Popup application is a client side application.

2.	To start Popup application “popup.exe” and to stop “popup.exe –stop(or stop)” command line is required.

3.	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.   

4.	The key requirements for popup application, is to get the SAS FW event message from storelib through Monitor and Monitor to Popup application.  Popup application displays the message box in the GUI environment in case of any event occurs on server side.


Known Restrictions:
===================
1.	Installation path cannot be changed. It is fixed. The installation directory is /usr/local.

2.	With Firmware version 1.00.00-0050, MSM load configuration does not work properly. 

3.	Framework and Monitor should be loaded before loading the Popup application.

4.	Popup version 1.00-17 or later require Monitor version 01-01-01 or later.


Known Bugs: 
===========
1.	NONE


Installation Notes: 
===============
1.	Refer to readme.txt file in zip file.

Download Driver Pack

How To Update Drivers Manually

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.

server: web2, load: 1.19