Component:	MegaRAID Storage Manager (MSM) v6.81-00 Linux Installer	
Engineering Release Date:		February 1, 2010
Engineer:				Raghu H B
MegaRAID Products Supported:	MegaRAID SAS
Released To: 				Fremont UT Group
 
Version Numbers:
Component			Current Version		Previous Version
1.	Linux Installer	6.81-00	6.80-00
2.	GUI	2.74	2.74
3.	Framework  	3.1	3.1
4.	Storelib Plugin                 	2.01	2.01
5.	Storelib Plugin JNI      	1.13 Build 01	1.13 Build 01
6.	Storelib IR Plugin                 	2.01	2.01
7.	Storelib IR Plugin JNI      	1.14	1.14
8.	Log Service Plugin            	1.03	1.03
9.	NetworkCapability Plugin  	1.10	1.10
10.	Authenticate Plugin         	1.01	1.01
11.	Authenticate Plugin JNI    	1.02	1.02
12.	SystemInfo Plugin	1.04	1.04
13.	SASKernel	2.56	2.56
14.	Storelib	3.50-03	3.46-03
15.	Storelibir	4.37-04	4.35-04
16.	Storelibir-2	1.20	1.18
17.	MegaMonitor	01-01-49	01-01-47
18.	SNMP Installer	3.17-1081	3.17-1080
19.	SNMP IR Installer	3.17-1082	3.17-1081
20.	Generic SNMP Agent	3.17.0.1	3.17.0.0
21.	SAS Data Collector	1.27-4	1.27-4
22.	SAS MIB File	1.24-07	1.24-07
23.	SAS-IR Data Collector	1.20-2	1.20-2
24.	SAS-IR MIB File	1.15-03	1.15-03
25.	CIMPlugin	1.05	1.05

Reason for Release

Defect fixes:

1.		LSIP200044850	10M02:Not able to create Raid volume through "Simple" config in MSM for IR card.	
2.		LSIP200044851	In SASIR card i am not able to create RAID 1ME.	
3.		LSIP200018806	The test email feature is not working on SSM	
4.		LSIP200043285	Patrol Read cannot be started using MSM when media errors are created.	
5.		LSIP200049842	multiple login possible with the ip 127.0.0.1	
6.		LSIP200018763	Mismatch in the fanspeed rpm values for ebbets/camden enclosures in serial console and MSM.	
7.		LSIP200043528	MSM screen did not got update when create VD from partial disk	
8.		LSIP200044831	Host Configure Dialog needs to be updated for SSM.	
9.		LSIP200044980	Configure Host setting is not saved	
10.		LSIP200049520	MSM 6.80-00 does not show the progress of Reconstruction from R5 to R0	
11.		LSIP200049530	The Progress Bar tab does not disappear after init is finished.	
12.		LSIP200049194	Couldn't Select Any Date From January (2010) To Run Schedule Patrol Read On SSM 6.70.04	

Known Issues:

1.	This build is limited to support the warning and Information alerts as a pop-up. This will be taken care in the next build
2.	This build is limited to support the help documents as explained below.  This will be taken care in the next build.
Extract the help files from docs.zip file available in inbanesg.
Delete the docs folder present in the MSM directory (/usr/local/MegaRAID Storage Manager). Paste the newly extracted docs folder into MSM directory (/usr/local/MegaRAID Storage Manager).

Known Limitations:
•	Scan/Import Foreign Configuration (SAS IR ): Not working (SCGCQ00055411:R0 VD becomes OFFLINE if R1 is created using remaining drives. && SCGCQ00057106 - No clear configuration option in MSM) 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. 
•	All the limitations applicable to Storelib and the respective side effects will also applicable to MSM.
Ex: If get partition info fails in storelib, VD related operation might fail.

Note:
1. Defect Reference: Vivaldi 2.07 Startup fails in DSA installed RHEL5 32 bit Snap7 (1/12)
The environment variable of "XMODIFERS" is set to "SCIM" in DBCS Linux OS 
(DBCS SLES10 and RHEL5 (Japanese, Korean, Traditional Chinese, Simplified Chinese). 
This variable is set to "none" in US Linux OS.When the environment variable 
of "XMODIFERS" is set to "SCIM", we cannot input Pass Phrase.  
To work around this problem, the description of "XMODIFERS=@im=none" should be 
added in the “startupui.sh".

Currently this variable is provided in startupui.sh and disabled (commented), whenever the 
users encounter this issues it is required to uncomment this and restart, 
which resolves this issue.

2. StorelibIR and StorelibIR-2 versions are not showing properly in MSM GUI (help-> about -> Server   info), this will be fixed in the next build.This build is generated from the Integration branch (Single branch for all programs).

3. If MSM is installed on the Vmware operating system Storelib and StorelibIR versions will be different than the versions mentioned above. The storelib and storelibIR versions will be depending on the user selection as mentioned below.

* If user selects the inbox storelib versions then inbox storelib versions will be loaded and displayed on the MSM GUI.

* If user selects the Storelib packaged in MSM below versions will be loaded and displayed in the MSM GUI
                
Storelib                                 3.30-03                                     
Storelibir                              4.27-04

 
4. When the user runs the MegaRAID Storage Manager(MSM) installation script
install.sh, the rpm's <Lib_Utils-1.xx-xx.noarch.rpm> and <Lib_Utils2-1.xx-xx.noarch.rpm>
will be installed, These RPM's install the third party libraries and MSM is dependent on these
libraries. If you uninstall the libraries installed by these RPM's then other
applications that are dependent on these libraries may not function correctly. Hence these RPM's
will not be removed when MSM is uninstalled. If you want to remove the RPM,
run the command Rpm -e <Lib_Utils-1.xx-xx.noarch.rpm> and Rpm -e <Lib_Utils2-1.xx-xx.noarch.rpm>.

If older version of the libutil rpm <Lib_Utils-1.xx-xx.noarch.rpm> is installed on the system,
please uninstall the older version of the RPM using the command "rpm -e <Lib_Utils-1.xx-xx>" and then install the latest libutil rpm <Lib_Utils-1.xx-xx.noarch.rpm> packaged in this zip file.

4.     For RHEL 5, it is necessary to install compat-libstdc++ version 33-3.x before installing rpm.
        For SLES-10 SP3 64bit OS, it is necessary to install libstdc++33-32bit-3.3.3-7.8.1.x86_64.rpm
        before installing MSM. This RPM is available in the OS DVD
        (path is /media/SUSE-Linux-Enterprise-Server_001/suse/x86_64)

Rational ClearCase Location
Known Restrictions: 
•	Installation path cannot be changed. It is fixed. The installation directory is /usr/local.
•	With Firmware version 1.00.00-0050, MSM load configuration does not work properly. 
•	Framework and Monitor should be loaded before loading the Popup application.
•	Popup version 1.00-17 or later require Monitor version 01-01-01 or later.
•	Upgradation of Blackrock(2.70-00) to Estatoah Falls(2.80-00) or higher is not supported.
(because Storelib version for Blackrock is 3.0.0.0 and Estatoah Falls is 2.51.0.0 , since the major version of Blackrock Storelib is higher, an upgradation is not possible) 
•	Messages for clear configuration and delete virtual disk are not in sync with UX document.
•	Selecting arrays of different encryption types in virtual disk creation dialog is not prevented. This has to be prevented as we do for other conditions in spanning.
•	Please see as below for CIM plug-in limitation,
o	Multiple Login Modes (ie, View Only/ Full Access) will not be supported. All the logins will be in Full Access mode only. This will be a limitation for this feature. (The GUI, however has not been updated; need UX approval for the same.) 
o	SystemInfo plug-in is not supported - The HostView panel (one that lists the frameworks in the network) will not list the properties “OS” and “Health” for the entries that correspond to VMWare system. Also, the server properties in the tree view will list only the System Name & IP. 
o	The VMWare hosts are discovered only when the Framework service starts on the host where MSM is installed. The exception handling for a CIMOM going out the network anytime later has not been implemented yet. 
o	It takes a while to discover the CIMOM servers. So, if you start the MSM client immediately after you install MSM (or restart Framework service for some reason), you will not be able to discover any hosts in the network. 
o	Refreshing of the MSM GUI after any updates on the firmware will be slower for a client connected to VMWare ESX3i hosts in comparison to one which is connected to Windows /Linux /Solaris hosts. 
o	The error level for all events have been hard coded to [Information, 0] in the logger for this release. For subsequent releases, this issue will be addressed & appropriate error levels would be displayed for each event. 
o	Event logging feature for MSM client connected to a VMWare system behaves as follows
•	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. 
•	“Save log” feature will not be supported. However, the “Save Log as Text” will continue to be supported.
•	“View Log” option will allow the user to view the logs saved in a text file on the event logger dialog.
•	Localization is not supported and will be handled as part of the future enhancements
•	The event descriptions may not be identical to a normal MSM client since we display whatever comes from the firmware.

•	Known limitation in Monitor Configurator GUI:
Key navigation on the severity column (i.e. containing combo box in Events table on the “Change Individual Event” dialog) is not supported currently. This requires more research and analysis on Java’s support. 

For now, only mouse can be used for selecting any item from the combo box.Currently, combo box on row selection is not visible. While particularly selecting any of the cells in third column using mouse, combo box becomes visible. Investigating ways to make it visible on row selection.

Features
•	Popup application is a client side application.
•	To start Popup application “popup.exe” and to stop “popup.exe –stop (or stop)” command line is required.
•	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.  
•	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.
•	Forward code merging from Unicoi to Estatoah is completed, so please verify all the defects from the Unicoi program.

Known Bugs
Note: Please always read README.txt before installation
Suggested Additional Areas to Test