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

LSI Logic MegaRAID Storage Manager Release 

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

Release Date: 06/30/06
===================

Supported Controllers
==================
MegaRAID SAS 8408E
MegaRAID SAS 8480E
MegaRAID SAS 8308ELP
MegaRAID SAS 8344ELP
MegaRAID SAS 8300XLP
MegaRAID SATA 300-8ELP
MegaRAID SATA 300-4ELP


Component:
=========
SAS MegaRAID MSM Windows
Release Date: 06/30/2006


Version Numbers:	MSM
===============		=====	
Current Version		1.13-07
Previous Version	1.08.01

Bug Fixes and Enhancements:
===========================
1.	MSM does not read FW MFC data when create new configuration

2.	Fake and Invalid Options are appearing on right mouse button clicking on "Port"

3.	"About" GUI under Help do not showing Product name and version properly

4.	Uninstalling MSM fails to remove corresponding files and directories.

5.	Still display "1.13 Build 02" even using "1.13-04".

6.	MSM:To create Ded HSP, it only allows the HDD which is bigger than or equal to the max capacity drive of the array.

7.	Monitor Configurator version in GUI not matching with MSM 1.13 Build 05 Release Note

8.	Parameter of ID99 message is incorrect.

9.	Error : Unknown exception when click on Tool-Mail configurator with Win2003 Japanese version

10.	Not able to make Mail alert feature to work

11.	Error severity reporting and thread synchronization issues have been improved in this release of Monitor.

12.	Event Notification application now un-register with FW when application exit.

13.	Event Notification Application replies back to FW once it gets from FW with the same message to let FW know that app rec’d the message.

14.	New server.pem file which does not require password to comply with new monitor.

15.	Monitor Configurator has been introduced in this release.

16. 	Popup function is added from MSM1.02, however this Popup is not function properly.

17.	The only one log is registered with event log, when you reboot server without operating in MSM.

18.	Installer complete upgrade process while MSM is running but actually failed to upgrade the components.

19.	MSM can't be started on Linux by local user

20.	WB without battery should be allowed

21.	Can not create R6 using 3 drive

22.	MSM return error when a unconfigured bad  perform a prepare for removal.

23.	MSM display wrong bbu even a bbu is installed in ZCR controller.

24.	Infrastructure support for Vivaldi Configurator.

25.	MSM has been made FHS (File Hierarchy Standard) compliance. FHS for Linux sets the standard for installing the third-party solutions, in other words, it directs the third-party solution providers to locate their files at certain locations.

26.	During Rebuild operation, try to save the controller configuration in a file. On trying to import that saved file encounters err

27.	Guided and "Auto" Config fails to create redundant array with more than 2 free PDs available.

28.	MSM Fails to start Installation process when no "C:\" drive present in the system

29.	Configuration wizard fixes

30.	All the PDs are highlighted in Reconstruction Wizard when any one PD is to be removed from an array.

31. 	Elapsed & Estimated Time in all Progress window displays wrong information.

32.	Prepare for Removal should not be available for internal drive

33.	The OS level RMU does not change to Enable Alarm in the Operations Pull Down menu when alarm is set to disabled

34.	The rebuilding disks are not indicated on Graphical View of Enclosure

35.	The Disk Status is not renewed on Graphical View

36.	Multiple VDs cannot be reclaimed in one shot though they are allowed to get selected all at once.

37.	Should replace "LD" with "VD" in Volume name while creating virtual disk using Auto config and Guided config.

38.	The reclaim button should be greyed out when an invalid object is highlighted

39.	Attempt to start Patrol Read from MSM GUI fails with error code 39

40.	MSM can not flash SAS ZCR image

41.	MSM log is some what misleading to the user when BBU is not used in the card.

42.	Remove hotspare button, Accept button should be greyed out until useable

43.	Incorporation of new command SL_EXIT_LIB in Storelib Plugin JNI.

44.	Checkword support for 1078 firmware on flash.

45.	Assigning long VD name is not displying the VD size unless rescan is performed

46.	Attempt to create Config encounters error "Command failed by Operating System" and AEN updation stops

47.	Upgrading MSM from ver 1.08-00 to 1.08-01 fails to start Popup service in Windows env.

48.	The number of Fans and Power Supplies is different from Log

49.	MSM shows incorrect detail messages.

50.	MSM could not display Graphical View, Correctly.

51.	MSM: when making Dedicated HS, it shows max 10 arrays even if we have more than 10 arrays.

52.	'Locate VD' & 'Stop Locating VD' options available against VD with PD outside an enclosure.

53.	When SRL_03 RAID capability of an adapter is not present, the number of Virtual disk created per spanned arrays is 1 that will use the entire spanned array. For such a situation, spanning has been prohibited using holes.


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, for all informational/Warning events.  User can optionally add Popup in the actionList of the alertdb.xml file which is released by Monitor.
  
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.	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). 

2.	Framework version Beta 2.7 and above is not compatible with its earlier versions.

3.	User authentication (Authenticate version 3.1) will not be compatible to its earlier version.

4.	Logger Service (Log Service version 3.1) will not be compatible to its earlier version.

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

6.	Upgrade from last release (Beta 3.1) is not supported.

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


Known Bugs: 
===========

1.	NONE

Installation Notes: 
===============

1.	Refer to readme.txt file in zip file.

