This release note and the software that accompanies it are copyright (c) 2012, Avago Technologies 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 AVAGO TECHNOLOGIES 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 AVAGO TECHNOLOGIES. ========================== Supported MegaRAID Controllers ============================== MegaRAID SAS 9362-4i MegaRAID SAS 9362-8i MegaRAID SAS 9361-4i MegaRAID SAS 9361-8i MegaRAID SAS 9363-4i MegaRAID SAS 9380-8e MegaRAID SAS 9381-4i4e MegaRAID SAS 9361-8iCC MegaRAID SAS 9380-8eCC MegaRAID SAS 9364-8i MegaRAID SAS 9340-8i MegaRAID SAS 9341-8i MegaRAID SAS 9341-4i MegaRAID SAS 9270-8i MegaRAID SAS 9271-4i MegaRAID SAS 9271-8i MegaRAID SAS 9271-8iCC MegaRAID SAS 9286-8e MegaRAID SAS 9286CV-8e MegaRAID SAS 9286CV-8eCC MegaRAID SAS 9265-8i MegaRAID SAS 9285-8e MegaRAID SAS 9240-4i MegaRAID SAS 9240-8i MegaRAID SAS 9260-4i MegaRAID SAS 9260CV-4i MegaRAID SAS 9260-8i MegaRAID SAS 9260CV-8i MegaRAID SAS 9260DE-8i MegaRAID SAS 9261-8i MegaRAID SAS 9280-4i4e MegaRAID SAS 9280-8e MegaRAID SAS 9280DE-8e MegaRAID SAS 9280-24i4e MegaRAID SAS 9280-16i4e MegaRAID SAS 9260-16i MegaRAID SAS 9266-4i MegaRAID SAS 9266-8i MegaRAID SAS 9285CV-8e MegaRAID SAS 8704ELP MegaRAID SAS 8704EM2 MegaRAID SAS 8708ELP MegaRAID SAS 8708EM2 MegaRAID SAS 8880EM2 MegaRAID SAS 8888ELP MegaRAID SAS 8308ELP* MegaRAID SAS 8344ELP* MegaRAID SAS 84016E* MegaRAID SAS 8408E* MegaRAID SAS 8480E* MegaRAID SATA 300-8ELP* Supported HBA Controllers ========================= LSI SAS 9211 LSI SAS 9212 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 LSI Nytro WarpDrive WLP4-200 LSI Nytro WarpDrive WLP4-400 LSI Nytro WarpDrive BLP4-400 LSI Nytro WarpDrive BLP4-800 LSI Nytro WarpDrive BLP4-1600 LSI Nytro XD BLP4-400 LSI Nytro XD BLP4-800 LSI SAS 9207-4i4e LSI SAS 9217-4i4e LSI SAS 9207-8i LSI SAS 9217-8i LSI SAS 9207-8e LSI SAS 9201-16e LSI SAS 9200-8e *These older controllers should work but have not been tested. =================== Package Information =================== OS supported = Windows* 2000, Windows* 2003, Windows* XP, Windows* Vista, Windows* Server 2008, Windows Server 2008 R2, Windows* 7, Windows* 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2012 R2 and Windows Server 2016. 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. 4) MSM Framework uses the 3071 port, please make sure this port is not occupied by other application to avoid the issues like Ex: GUI refresh and Monitor Events logging issues. 5) Increase/Decrease strength of Public/Private RSA keys: Windows MSM Installer provides an option to user to select Self signed key size. Upon installation user can still switch the keys and below were the steps to perform the same: - Stop MSMFramework Service. - Make sure service is Stopped - Edit the vivaldikey.properties available in below locations 1) <MSM_HOME> 2) <MSM_HOME>\Framework 3) <MSM_HOME>\MegaPopup - Comment/Uncomment the VIVALDI_KEY_FILE field for Key size selection. - Save the vivaldikey.properties file. - Start the MegaRAID Storage Manager Framework service. - Start the MegaPopup from Command prompt ( <MSM_HOME>\MegaPopup\popup.exe) 6)Alert notifications of users choice: After installation user can switch the alert notifications choices and below were the steps to perform the same: - Stop MSMFramework Service. - Make sure service is Stopped - Edit the eventnotificationchoice.properties available in below location <MSM_HOME>\Framework - Comment/Uncomment the EVENT_NOTIFICATION_CHOICE field for alert notification choice selection. - Save the eventnotificationchoice.properties file. - Start the MegaRAID Storage Manager Framework service. - Start the MegaPopup (<MSM_HOME>\MegaPopup\popup.sh) ================== 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) 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 stop. /etc/init.d/sfcbd-watchdog start. 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] 5) CURL error in CIMOM server results in AEN blocked by CIMOM server to upper layer(CIMProvider-->MSM). This can happen if servers are in differnt subnet or if there is any incomplete AEN subscritions. To get rid of this, user is required to have both client and server in same subnet. Any incomplete AEN subscriptions needs to be removed via CIMClient Either restart of sfcb service or reboot the server is recommended after any change in VMware server. 6) 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). 7) Latest AVAGO 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 AVAGO MegaRAIDStorageManager MSM GUI, MegaPopup acts as Client and Framework act as Server. 8) 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 9) Latest AVAGO MegaRAID Storage Manager for Windows has been packaged with Visual C++ Redistributable for Visual Studio 2012 Update 1. Note that "Visual C++ Redistributable ...
boog3r