MegaRAID Storage Manager(MSM) Installation
==========================================
The kit contains both mode of installation. The interactive and non-interactive.
To, install the product using interactive mode, the user should execute the command "./install.csh" from the installation disk.
To, install the product in a non-interactive or silent mode, the user may use the command "./install.csh [-options] [ -ru popup]" from the installation disk. The options are:
  a, for Complete installation
  c, for Client Component Only
  s, for StandAlone
  l, for Local
  d, for Server
The "-ru popup" will remove popup from installation list.
User may also run non-interactive installation using "RunRPM.sh" command.

The installer provides the user with five types of setup option.
1. Complete - This will install all the features of the product.
2. Client Components Only - The storelib feature of the product will not be installed in this type of installation. As a result, the resident system will only be able to administer and configure all the servers in the subnet, but will not be able to serve as a server.
3. StandAlone - This option will only install components required for local server management. This system will not be discovered automatically by other MSM
   servers in the subnet and it will not discover other MSM servers in the subnet automatically. (multicasting will be disabled) But the system can connect 
   to other MSM servers by providing the ipaddress in the hostview screen and can be connected by the other MSM clients in the subnet.
4. Local - This option will install only components required for local configuration. Will not allow other systems on the network to connect to
   this server and cannot connect to other servers. This MSM installation mode only uses the loopback interface.
5. Server - This option will only install components required for remote server management.

The installation will help the user to select any of the setup type, but if the user directly run "RunRPM.sh", it will install the complete feature.

NOTE:
	1. For RHEL 5, it is necessary to install compat-libstdc++ version 33-3.x before installing rpm.
	2. 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)
	3. For SLES-9 32bit OS, it is necessary to install compat-libstdc++-lsb-4.0.2_20050901-0.4.i586.rpm
	   before installing MSM. This RPM is available in the OS DVD (path is /media/dvd/suse/i586)
	4. For RHEL 3, it is necessary to install the RPM libstdc++34-3.4.0-1.i386 before installing MSM.
	5. It is necessary to enable shadow password in RHEL 6 to login to MSM.
	6. Prerequisites for installing MSM on RHEL6.x x64 operating system 
	   Before installing MSM on RHEL6.x x64 system, Please install the following rpms,
	   Without these files/RPM's MSM may not be install properly or may not work as expected.

		libstdc++-4.4.4-13.el6.i686.rpm
		compat-libstdc++-33-3.2.3-69.i686.rpm
		libXau-1.0.5-1.el6.i686.rpm
		libxcb-1.5-1.el6.i686.rpm
		libX11-1.3-2.el6.i686.rpm
		libXext-1.1-3.el6.i686.rpm
		libXi-1.3-3.el6.i686.rpm
		libXtst-1.0.99.2-3.el6.i686.rpm
		
	    Also note that RHEL6.x complete OS installation is required for MSM to work.
		The above mentioned rpm's come as part of RHEL6 OS DVD. These RPM's may need
	    additional dependent RPM's as well, all the dependent RPM's also must be installed on the target system.

	7. Net-SNMP rpm installation is required before we install agent rpms.
		RHEL 4.8:
			net-snmp-5.1.2-18.el4.x86_64.rpm
			net-snmp-utils-5.1.2-18.el4.x86_64.rpm
		RHEL5.4
			lm_sensors-2.10.7-4.el5.x86_64.rpm 
			net-snmp-utils-5.3.2.2-7.el5.x86_64.rpm
			net-snmp-5.3.2.2-7.el5.x86_64.rpm
		RHEL 5.3
			lm_sensors-2.10.7-4.el5.x86_64.rpm
			net-snmp-5.3.2.2-5.el5.x86_64.rpm
			net-snmp-utils-5.3.2.2-5.el5.x86_64.rpm
		RHEL 5.5
			net-snmp-5.3.2.2-9.el5.x86_64.rpm
			net-snmp-utils-5.3.2.2-9.el5.x86_64.rpm
		RHEL 5.6
			net-snmp-5.3.2.2-9.el5_5.1.x86_64.rpm
			net-snmp-5.3.2.2-9.el5_5.1.x86_64.rpm
		RHEL 5.7
			net-snmp-5.3.2.2-14.el5_5.1.x86_64.rpm
			net-snmp-utils-5.3.2.2-14.el5_5.1.x86_64
		RHEL 5.8
			net-snmp-5.3.2.2-17.el5_5.1.x86_64.rpm
			net-snmp-utils-5.3.2.2-17.el5_5.1.x86_64
		RHEL 6.0
			net-snmp-5.5-27.el6.x86_64.rpm
			net-snmp-utils-5.5-27.el6.x86_64
		RHEL 6.1
			net-snmp-5.5-31.el6.x86_64.rpm
			net-snmp-utils-5.5-31.el6.x86_64.rpm
		RHEL 6.2
			net-snmp-5.5-37.el6.x86_64.rpm
			net-snmp-utils-5.5-37.el6.x86_64.rpm
		RHEL 6.3
			net-snmp-5.5-39.el6.x86_64.rpm
			net-snmp-utils-5.5-39.el6.x86_64.rpm
		SLES 11
			net-snmp-5.4.2.1-8.1.x86_64.rpm
			perl-SNMP-5.4.2.1-8.1.x86_64.rpm
	8. In case you are unable to install lsi snmp agent rpms, use rpm -ivh --force *.rpm and 
	   then you can uninstall the lsi rpms using rpm -e *.rpm. 
	9. In case of problems with installing multiple rpms and get into cyclic redundancy issue,
	   one can install all rpms in one command line.
	   (Example: rpm  -ivh net-snmp-5.4.2.1-8.1.x86_64.rpm perl-SNMP-5.4.2.1-8.1.x86_64.rpm)
	10. For VMware 3.5, it is necessary to install libstdc++34-3.4.0-1.i386.rpm before installing
	   MegaRAID Storage Manager(MSM). The rpm can be downloaded from
	   http://rpm.pbone.net/index.php3/stat/4/idpl/1203252/com/libstdc++34-3.4.0-1.i386.rpm.html.
	11.For VMware 4.1, it is necessary to create a softlink as mentioned below before installing
	   MegaRAID Storage Manager(MSM). Run the below command to create the necessary soft link
	   required for MegaRAID Storage Manager(MSM) to work.
	   "sudo ln -sf /lib/libgcc_s.so.1 /usr/lib/vmware/lib/libgcc_s.so.1"
	12. JRE1.6 differences - In Linux 32/64 bit: MSM is shipped with JRE 1.6 U37 unlike other platforms like Windows/Solaris because of the OS
    	backward compatibility issues with JRE1.7 Here is the link where we can find out the OS support matrix for JRE1.7
		http://www.oracle.com/technetwork/java/javase/config-417990.html
	13. Soft links in Linux 64 bit: For RHEL/SLES on 64 bit platform(s), it is necessary to create the below soft links before installing
    	MegaRAID Storage Manager(MSM) 64 bit package.
	    "ln -sf /usr/lib64/libcrypto.so.xx.xx /lib64/libcrypto.so.4"
        "ln -sf /usr/lib64/libssl.so.xx.xx /lib64/libssl.so.4"

=========
Attention
=========
1) 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.


==================
Known Restrictions
==================
1) Latest LSI 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 LSI MegaRAIDStorageManager MSM GUI, MegaPopup acts as Client and Framework act as Server. 


Prerequisite for MSM installation:
==================================
MSM installation scripts also installs the LSI SNMP agent rpm. 
The LSI SNMP agent application depends upon standard SNMP Utils package. 
Please ensure that the SNMP-Util package is present in the system before
installing MSM. SNMP-Util package includes the rpm.s net-snmp-libs , net-snmp-utils  and
additional dependent RPM.s. Please make sure that these RPM.s are installed from the OS media before
installing the MSM.

Prior to install MSM, check for existence of libstdc++.so.5 and libstdc++.so.6
librareis are present in /usr/lib directory. If not present/ installed, 
then install the Linux software component RPM that provides these libraries.
These RPM's will be available in the OS DVD. 

Prior to executing install.csh, check for existence of /bin/csh. If
not present/ installed, then install the Linux software component RPM
that provides /bin/csh.

Prerequisites to run MSM remote admin
======================================

1. Configure the system with valid IP address. Make sure there is no IP address conflict with in the sub network.

2. Ports such as 3071 and 5571 are open and available for MSM framework communication.

3. Disable all security manager and firewall.

4. Configure the multicasting, make sure class D multicast IP addresses are registered (at least 229.111.112.12 should be register for MSM to work), if not create static route using the following command:

        route add 229.111.112.12 dev eth1.

        Note that this command will not modify the routing table to be persistent across reboots. Please follow the guidelines per operating system to add the above mentioned IP address as a static entry into the routing table to be persistent across reboots.

        You may wish to add the entire range of IP addressess (224.0.0.0 through 239.255.255.255) into the routing table. Please note that this requires procedures that varies between different flavours and versions of operating system and may have security implications.

5. Install MSM, if already installed then restart MSM framework.


CIMPlugin Support
=================
In case of networks that doesn't have DNS configured, the .hosts. file of the systems where MSM is installed must be manually edited to map the IP address & the host name of your CIMOM server.  In addition, it should also have a mapping of its own IP address (not the loop back address) and host name for the indications to be supported.


MSM Uninstallation
==================
The product can be uninstalled using "Uninstall" short-cut created in Program menu. The user may also directly run the script "/usr/local/MegaRAID Storage Manager/uninstaller.sh" to uninstall MSM.


Notes:
  1. MSM upgrade is supported in this release. In other word, this release can be upgraded by future releases.

  2. To shutdown MSM Framework service, run "/etc/init.d/vivaldiframeworkd stop".
  
  3. "Any kernel upgrade requires restart of the MSM Framework and Services"
      for example, 
      RedHat Linux command to reload or restart network (login as root user):
      To start Linux network service:
      # service network start
      Debian Linux command to reload or restart network:
      # /etc/init.d/networking restart

==========================
Supported RAID Controllers
==========================
This download supports the following controllers

LSI MegaRAID: MegaRAID SAS 9240-4i/8i,MegaRAID SAS 9260-4i/8i/16i,MegaRAID SAS 9261-8i,MegaRAID SAS 9280-4i4e,MegaRAID SAS 9280-8e,MegaRAID SAS 9280-16i4e,
MegaRAID SAS 9280-4i4e,MegaRAID SAS 9265-8i,MegaRAID SAS 9285-8e,MegaRAID SAS 8704EM2,MegaRAID SAS 8708EM2,MegaRAID SAS 8880EM2,MegaRAID SAS 8888ELP

LSI HBA: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 SNMP agent for Linux 
********************************************************************

Installation procedure for LSI SNMP Agent(For SUSE and Red Hat Linux)
--------------------------------------------------------------------------

1. LSI SNMP Agent rpm's installs the agents. 

2. rpm will take care of the necessary modification needed in the snmpd.conf
file for running the agent.
[
NB: Before installation please check,there is any pass command 
    starts with 1.3.6.1.4.1.3582 OID in snmpd.conf, if available then delete
all the old pass commands starts with 1.3.6.1.4.1.3582 OID.
(This could be possible if there is any previous LSI SNMP Agent was installed
in the system)
]
3. The snmpd.conf file structure should be same as lsi_mrdsnmpd.conf. For
reference,a sample conf file (lsi_mrdsnmpd.conf) will be there in the
/etc/lsi_mrdsnmp directory. 

4. For running SNMP query from a remote m/c add the ip address of that m/c in
the snmpd.conf file like this..

   com2sec	snmpclient	172.28.136.112		public

   Here ipaddress of the remote m/c is 172.28.136.112

5. For receiving snmp trap to a particular m/c, add the ip address of that m/c
in the com2sec section of snmpd.conf file. For example, to get Trap in
10.0.0.144, then add following line to snmpd.conf.
#       sec.name	source			community
   com2sec	snmpclient	10.0.0.144		public

6. To Run/stop the snmpd daemon.
   	/etc/init.d/snmpd start/stop
 
7. To start/stop the SNMP Agent daemon before issuing any snmp query.
     /etc/init.d/lsi_mrdsnmpd start/stop

8. Status of the SNMP Agent daemon can be checked by issuing the following
command...
   /etc/init.d/lsi_mrdsnmpd status

9. You can issue snmp query like this...

    snmpwalk -v1 -c public localhost .1.3.6.1.4.1.3582

10. You can get the snmp trap from local m/c by issuing the following
command...
    snmptrapd -P -F "%02.2h:%02.2j TRAP%w.%q from %A %v\n" 

11. For SLES-11 platform, please follow the below steps to configure traps.
	Edit /etc/lsi_mrdsnmp/sas/sas_TrapDestination.conf file & add ipaddress as
	shown below.

	#################################################
	# Agent Service needs the IP addresses to sent trap
	# The trap destination may be specified in this file or
	# using snmpd.conf file. Following indicators can be set
	# on "TrapDestInd" to instruct the agent to pick the IPs
	# as the destination.
	# 1 - IPs only from snmpd.conf
	# 2 - IPs from this file only
	# 3 - IPs from both the files
	#################################################
	TrapDestInd 3
	#############Trap Destination IP##################
	127.0.0.1   public
	172.28.157.149 public
	#################################################
	
NOTE:
	For SNMP components to work, it is necessary that linux system should
have snmp-net packages(rpm) to be already present.

	It is assumed that snmpd.conf is located at /etc/snmp for Redhat and
/etc for SuSE. Anyway, user can change the file location from
/etc/init.d/lsi_mrdsnmpd file

	It is neccessary to uninstall all the previous version before
installing a new version. The rpm has not been created to support -U version.
The rpm -U is most likely to fail with this rpm.

SNMP Trap Disable functionality
===============================
User may disable SNMP Trap functionality using "-notrap" as install(install.csh) parameter.

MegaRAID Storage Manager(MSM) Installation on VMware :
======================================================
To, install the MSM on VMWare operating system, the user should execute the
command "./vmware_install.sh" from the installation disk.

The installer provides the user to choose the License agreement,operating system 
and storelib to be used as mentioned below.
1. End user license agreement.
2. Operating system  (VMware 3.5 or VMware 4.0).
3. Select the Storelib (Inbox Storelib or Storelib from MSM package).

Note:
1. LSI SNMP Agent is not a supported configuration on VMware Operating system (VMware 3.5 or VMware 4.0).
2. Ensure that on a 32 bit or on a 64 bit VMware operating system, you install the 32 bit MegaRAID Storage Manager software.
3. Workaround Specific to ESXi Server: 
   a) On some Windows machines it has been seen that the discovery of VMWare ESXi servers fail as a result of a bug in the 3rd party application that
   	  is used for discovery. This is actually caused by one of the windows servers in the network which contains a service called IBM SLP SA, which
      gets installed along with IBM Director If we stop this service on all the windows servers in the network,
      MSM will be able to discover all the ESXi servers.   
   b) Ensure that the thirdparty application services like "slpd and sfcbd-watchdog services are up and running on ESXi
   	  server".(/etc/init.d/slpd status & /etc/init.d/sfcbd-watchdog status).
   c) Ensure that firewall has been disabled on ESXi server.
      (Check Firewall status : "esxcli network firewall get" To Disable Firewall : "esxcli network firewall unload").

MegaRAID Storage Manager(MSM) Uninstallation on VMWare :
======================================================
The MSM can be uninstalled by running the script 
"/usr/local/MegaRAID Storage Manager/uninstaller.sh".

MSM Performance improvement
===========================
For better performance of MSM, when subjected to any heap-intensive (say heavy
IOs) or computational tasks,improve the heap by including the following command
"-Xms1024m -Xmx1024m",where
 1024m           Size of the heap allocated. The specified size is dependent on the machine's Hardware configuration.
 -Xms1024m       Sets the initial size of the Java heap to 1024 Mbytes
 -Xmx1024m       Sets the maximum heap size to 1024 Mbytes

 1. Goto product home folder (/usr/local/MegaRAID Storage Manager).
 2. Open startupui.sh file in editable mode.
 3. Include the command -Xms1024m -Xmx1024m after "./jre/bin/java",
    effectively:
    LD_LIBRARY_PATH=$MSM_HOME/lib ./jre/bin/java -Xms1024m -Xmx1024m -DVENUS=true....

=============
Fixes/Updates
=============
13.01.04.00

MR5.6 
Defects:

1)SCGCQ00362722                           MSM discovery host does not work
2)SCGCQ00353990                           After clear configuration from any of the server,Refresh of device tree is taking more time.
3)SCGCQ00376597                           Server Profile information is not alligned properly in MSM Dashboard for SPARC10
4)SCGCQ00382064                           Invalid entries in MSM resource files

13.01.03.00

Defects
MR5.6:

1)SCGCQ00373530                           Wrong nextlearntime is shown for BBU in snmp util and HP openview.
2)SCGCQ00369533                           Not able to select SAS,SATA PD's after selecting and deselecting SSD's as part of the Drive Group.
3)SCGCQ00360074                           VD informations are not aligned properly in solaris sparc 11.
4)SCGCQ00361118                           MSM: Recon option on Odd numbered drive R0 not allowed.
5)SCGCQ00362722                           MSM discovery host does not work
6)SCGCQ00374135                           CSA-1.5 MSM-"Selected FW version" shows wrongly while updating firmware (7mb rom  file of 2161) from MSM
7)SCGCQ00365138                           SWR: MSM displays incorrect VD creation time.
8)SCGCQ00369158                          Text not displayed properly in advanced properties of BBU page.
9)SCGCQ00374605                          CSA1.5: MSM : Alt+g+c+t is not displaying pop up window for set patrol read properties.

MR6.1:

1)SCGCQ00361161                           MSM is showing junk characters in preserved cache window

13.01.02.00

Defects:
MR5.6:
1)SCGCQ00357654		MR5.6 Linux 32/64 bit MSM is not packaged with JRE1.7
2)SCGCQ00355879		MSM- not displaying the complete serial no. for IBM, toshiba drives and Expander
3)SCGCQ00356237		MSM: when flashing a MR controller, MSM reports it will flash iMR FW in the same package
4)SCGCQ00353922		Windows 2012 is unable to discover VMWare through MSM
5)SCGCQ00361388		MSM Fails to Discover ESXi servers.

MR6.1:
1)SCGCQ00320835 	iMR_Fury_6.1:MSM - MSM framework crashed during Foreign config import

13.01.01.00

Defects:

MR5.6: 

1)SCGCQ00357953                           MR 5.6 Alpha: MSM is unable to create a snapshot view
2)SCGCQ00356079                           MSM still prompt user when trying to Uninstall MSM using the "silent" option
3)SCGCQ00358682                           MSM's BBU Advanced Properties page have text that are truncated
4)SCGCQ00353987                           Host Name and OS Name were not displayed for ESXi servers
5)SCGCQ00354457                           Set virtual drive properties dailog is not closing when we click on Ok button
6)SCGCQ00354069                           RAID 10 not listed for IR2 in MSM
7)SCGCQ00354080                           Host name and Right Click option not visible IR2/IR controller
8)SCGCQ00305171                           MACON:  ssd drive temperature is shown in negative value.
9)SCGCQ00357909                           "Create VD" tab is missing on specific scenario
10)SCGCQ00353922                          Windows 2012 is unable to discover VMWare through MSM
11)SCGCQ00359981                          MSM: MR5.6 is missing the 256 bit encryption US export policy and local_policy jar files in jre1.7
12)SCGCQ00305170                          (RW LSIP200223243) macon: the media error count in pd proerties page dosent change unless we do a manual refresh


HAMR: 

1)SCGCQ00356875                           HAMR: MSM show Domain ID instead of server name when only node exist in cluster
2)SCGCQ00316678                           HAMR: MSM did not have a help file for configure a shared VD

MR6.1:

1)SCGCQ00345771                           iMr_Hamlin_MSM:Prepare for removal option is not coming for DIF/SED drives in MSM
2)SCGCQ00347187                           iMR_Hamlin_MSM:4K drive size not shown proper in MSM profile summary
3)SCGCQ00348477                           MR-MSM: on starting manual learn cycle on supercap, warning message shows that learn cycle takes upto 8 hours.
4)SCGCQ00346252                           iMR_Hamlin_MSM:"Instant secure erase" option is enabled for FDE/SED drives in JBOD state


13.01.00.00
Enhancements:

1)SCGCQ00295261                           MSM Japanese Translation
2)SCGCQ00342901                           Improve MSM response time - early work
3)SCGCQ00342910                           MSM to display entire HA cluster in a a single pane - early work
4)SCGCQ00329012                           MSM: Add support to load CIMPlugin in Linux 64-bit client
5)SCGCQ00295907                           Add MSM StartUI icon
6)SCGCQ00352103                           NMR1.0 HSW merge to MR5.6 HSW
