Component:	MegaRAID Storage Manager (MSM) v6.81-00 Windows 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
Windows Installer	6.81-00	6.80-00
Product Version                                 	6.81.0000                                           6.80.0000
GUI	2.74	2.74
Framework  	3.1	3.1
Storelib Plugin                 	2.01	2.01
Storelib Plugin JNI      	1.13 Build 01	1.13 Build 01
Storelib IR Plugin                 	2.01	2.01
Storelib IR Plugin JNI      	1.14 	1.14 
Log Service Plugin            	1.03	1.03
NetworkCapability Plugin  	1.10	1.10
Authenticate Plugin         	1.01	1.01
Authenticate Plugin JNI    	1.01	1.01
SystemInfo Plugin	1.04	1.04
CIM Plugin	1.05	1.05
SASKernel	2.56	2.56
Storelib	3.46-03	3.46-03
Storelibir	4.34-04	4.34-04
Storelibir-2	1.17	1.17
MegaMonitor	01-01-49	01-01-48
Popup	1.00-29	1.00-29
Generic SNMP Agent	3.17.0.1	3.17.0.1
SAS Data Collector	1.34.0.6	1.34.0.6
SAS MIB File	1.24-07	1.24-07
SAS-IR Data Collector	1.20.0.4	1.20.0.4
SAS-IR MIB File	1.15-03	1.15-03

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 (C:\Program Files\MegaRAID Storage Manager). Paste the newly extracted docs folder into MSM directory (C:\Program Files\MegaRAID Storage Manager).

Known Limitations:
·	This version of MSM has some known issues with Windows 64 bit OS with IR-1 card due to the underlying component issues
·	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:
StorelibIR version is not showing properly in MSM GUI.

Rational ClearCase Location	
Known Restrictions: 
·	Due to a legacy security setting in Windows 2000(now removed in Windows XP, 2003 etc), Authentication requires the following privilege setting: 
Go to Program --> Administrative Tool --> Local Security Settings and assign the policy "Act as part of operating System" to user (Administrator / Everyone). 
·	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.
·	This MSM release is not integrated with Vista Application Manifest, thus it is not UAC 
(User Account Control) compliant for Windows Vista.
·	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 

·	MSM will be supported starting from Windows 2000 Service Pack 3. Anything lower than this will not be supported.
·	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.

Note: 
1.	Please always read README.txt before installation
2.	SNMP components belong to SNMP installer: 3.17-0181 and SNMP-IR: 3.17-082.

Suggested Additional Areas to Test