MegaRAID Storage Manager Application for Linux

Adapters Supported: 
  - N2125 SAS/SATA HBA for IBM System x
  - N2115 SAS/SATA HBA for IBM System x
  - IBM PureFlex System Storage Expansion Node
  - Onboard LSI 2004 SAS/SATA controller
  - Onboard LSI 1064 SAS controller
  - Onboard LSI 1064e SAS controller
  - Onboard LSI 1068e SAS controller
  - Onboard LSI 1078 SAS controller
  - ServeRAID C100 (81Y4475)
  - ServeRAID C105 (90Y4386)
  - ServeRAID H1110 SAS/SATA Controller for IBM System x (81Y4492)
  - ServeRAID H1135 Controller for IBM Flex System and BladeCenter (90Y4750)
  - ServeRAID M1215 SAS/SATA Controller for IBM System x (46C9114)
  - ServeRAID M1210e SAS/SATA Controller for IBM System x
  - ServeRAID M5210e SAS/SATA Controller for  IBM System x
  - ServeRAID M5210e SAS/SATA Controller
  - ServeRAID M5110 SAS/SATA Controller for IBM System x (81Y4481)
  - ServeRAID M5110e SAS/SATA Controller for IBM System x 
  - ServeRAID M5120 SAS/SATA Controller for IBM System x (81Y4478)
  - ServeRAID M5025 SAS/SATA controller (46M0830)
  - ServeRAID M5016 SAS/SATA Controller for IBM System x (90Y4304)
  - ServeRAID M5015 SAS/SATA controller (46M0829)
  - ServeRAID M5014 SAS/SATA controller (46M0916)
  - ServeRAID M1115 SAS/SATA Controller for IBM System X (81Y4448)
  - ServeRAID M1015 SAS/SATA Controller (46M0831)
  - IBM SAS HBA (25R8060)
  - IBM 3Gb SAS HBA v2 (44E8700)
  - IBM SAS Expansion Card (CFFv) for IBM BladeCenter (39Y9190)
  - IBM SAS Connectivity Card (CFFv) for IBM BladeCenter (43W3974)
  - IBM SAS/SATA RAID Kit (42C1312, 42C1313)
  - IBM ServeRAID BR10i SAS controller (44E8688)
  - IBM ServeRAID BR10il SAS controller (44X0411)
  - IBM ServeRAID BR10il v2 SAS controller (49Y4731)
  - IBM ServeRAID MR10il SAS controller (44E8767)
  - IBM ServeRAID MR10is SAS controller (44E8695)
  - IBM ServeRAID MR10ie (CIOv) SAS controller (46C7167)
  - IBM ServeRAID MR10i SAS controller (43W4296)
  - IBM ServeRAID MR10k SAS controller (43W4280)
  - IBM ServeRAID MR10M SAS controller (43W4339)
  - MegaRAID 8480 SAS controller (39R8850)

(C) Copyright International Business Machines Corporation 1999, 2015. All 
rights reserved.  US Government Users Restricted Rights - Use, duplication, 
or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Note: Before using this information and the product it supports, read the 
general information in "Notices and trademarks" in this document.


CONTENTS
________

1.0  Overview
2.0  Installation and setup instructions
3.0  LSI SNMP agent for Linux 
4.0  Usage information 
5.0  Unattended mode
6.0  Web site and support phone number
7.0  Notices and trademarks
8.0  Disclaimer


1.0  Overview
_____________

    1.1    This document describes how to install the MSM storage management 
           application.  MSM is a GUI application that runs in the Linux or 
           VMware environment.  

    1.2    Limitations
           - MegaRAID Storage Manager only supports 1024 bit SSL encryption key length.
           - New or first time installation of MSM must be done manually.  See
             section 2.2 Attended Installation for instructions.
	   - Current installed version of MSMS must be 13.11.01.06 or higher to
             run this update package in unattended mode.

    1.3    Problems fixed:
           - See change history
           
    1.4    Level of Recommendations and Prerequisites for the update:
           - The mpt3base.ko, mpt3sas.ko and mpt3ctl.ko modules, mpt2base.ko, mpt2sas.ko
             and mpt2ctl.ko modules or megaraid-sas.ko module must be installed and loaded
             before MSM will function correctly.
           - 32 bit glibc, libstdc++.so and libncurses.so are required for the update run.
             Example:  RHEL 6 install - libstdc++-4.4.4.13.el6.i686.rpm
				      - ncurses-libs-5.7-3.20090208.el6.i686.rpm
           	       RHEL 7 install - glibc-2.17-55.el7.i686

    1.5    Dependencies:
        -  Soft links in Linux 32 bit: For RHEL/SLES on 32 bit platform(s), it is necessary to create the
            below soft links before installing MegaRAID Storage Manager(MSM) package.
	      "ln -sf /usr/lib/libcrypto.so.xx.xx /lib/libcrypto.so.4"
	      "ln -sf /usr/lib/libssl.so.xx.xx /lib/libssl.so.4"
        -  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"
	-  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)
	-  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)
	-  For RHEL 3, it is necessary to install the RPM libstdc++34-3.4.0-1.i386 before
           installing MSM.
	-  Prerequisites for installing MSM on RHEL6.0 operating system 
	   Before installing MSM on RHEL6.0 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.0 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.
			
        -  Prerequisites for installing MSM on RHEL7 operating system 
           Before installing MSM on RHEL7 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.8.2-16.el7.i686.rpm
				libXau-1.0.8-2.1.el7.i686.rpm
				libxcb-1.9-5.el7.i686.rpm
				libX11-1.6.0-2.1.el7.i686.rpm
				libXext-1.3.2-2.1.el7.i686.rpm
				libXi-1.7.2-2.1.el7.i686.rpm
				libXtst-1.2.2-2.1.el7.i686.rpm
				glib2-2.36.305.el7.i868.rpm 
				nss-softoken-freebl-3.15.4-2.el7.i686.rpm
				libgcc-4.8.2016.el7.i686
		
	    Also note that RHEL7 complete OS installation is required for MSM to work.
            The above mentioned rpm's come as part of RHEL7 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.

	-  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 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
		RHEL 6.4
			net-snmp-5.5-44.el6.x86_64.rpm
			net-snmp-utils-5.5-44.el6.x86_64.rpm
		RHEL 6.5
			net-snmp-5.5-49.el6.x86_64.rpm
   			net-snmp-utils-5.5-49.el6.x86_64.rpm
		RHEL 6.6
			net-snmp-5.5-49.el6_5.3.x86_64.rpm
   			net-snmp-utils-5.5-49.el6_5.3.x86_64.rpm
		RHEL 7.0
			net-snmp-5.7.2-18.el7.x86_64.rpm
			net-snmp-utils-5.7.2-18.el7.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
	-  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. 
	-  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)
     	        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

        - 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 MSM.

        - Prior to install MSM, check for existence of libstdc++.so.5 and libstdc++.so.6
          libraries 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.
	
    1.6	   Update Contents:
           o  ibm_utl_msm_17.05.01.03_linux_32-64.bin
              - Zipped installation package
           o  ibm_utl_msm_17.05.01.03_linux_32-64.chg
              - Change history


2.0  Installation and setup instructions
________________________________________

  This package can be used with several of IBM's update management tools, 
  including IBM UpdateXpress Manager, IBM UpdateXpress System Packs, and 
  IBM Director.

  It can also be used as a standalone package.  

  To use the package with one of IBM's update management tools, follow the 
  instructions that came with your specific management tool.

  2.1 Standalone usage instructions
  ---------------------------------

  ibm_utl_msm_17.05.01.03_linux_32-64.bin <option>

    -x <dirname> - Extracts contents to tor <dirname>
    -s - Silent/unattended install
    -? - Prints help information

   2.2 Attended Installation
   -------------------------
   A. Extract update to a directory using the option above.
   B. Change to the system OS appropriate architecture directory
   C. Follow the instructions below.

	The installer provides the user with four types of setup options.
	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.

    - The package contains two mode of installation, 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
    - The "-ru popup" will remove popup from installation list.
    - User may also run non-interactive installation using "RunRPM.sh" command.
    - Under Linux, this installation kit can be used in either interactive or non-interactive
      mode.  In VMware, only interactive mode is supported. 
      
      Below are the set of commands to be used for update only installation for different setup
      types.
Usage : install.sh [-option]
The options are:

          au - The update only Complete Installation of MSM

          cu - The update only Client components only program of MSM

          su - The update only StandAlone component of MSM

          lu - The update only Local component of MSM

          du - The update only Server component of MSM
  
    - 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.


    2.3 Trouble Shooting Tips
    -------------------------

    RHEL7:
    The snmpd daemon(s) may not start automatically after the installation completes.
    After MSM installation finishes, run the following commands as an elevated user in
    order to start the snmpd services. If the system has been rebooted since the MSM
    install completed, these commands should not be needed.
 

       systemctl start snmpd
       systemctl daemon-reload
       systemctl start lsi_mrdsnmpd


    2.4 Uninstallation
    ------------------
    The application can be uninstalled using the "Uninstall" short-cut which 
    is created in the program menu.  

    A scriptable uninstaller can be found here:
      /usr/local/MegaRAID Storage Manager/uninstaller.sh

    NOTES:
    - This release supports upgrades by future releases.  There is no need to 
      uninstall before upgrading.
    - To shut down the MSM Framework service, first stop the Monitor service 
      by typing:
        /etc/init.d/mrmonitor stop
      then stop the framework service by typing:  
        /etc/init.d/vivaldiframeworkd stop

    - 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


    2.5 Prerequisites to run MSM remote admin
    -----------------------------------------

    - Configure the system with valid IP address. Make sure there is no IP address conflict
      with in the sub network.
    - Ports such as 3071 and 5571 are open and available for MSM framework communication.
    - Security manager and firewall is configured correctly to allow needed ports to be opened.
    - 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 addresses (224.0.0.0 through 
        239.255.255.255) into the routing table. Please note that this requires procedures
        that varies between different flavors and versions of operating system and may have
        security implications.


     2.6 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.


     2.7 MegaRAID Storage Manager(MSM) Installation on VMware 4.x ESX
     ----------------------------------------------------------------
	Only VMware 4.x ESX is supported 
	
	Detailed install instructions can be found at: 
	ftp://ftp.software.ibm.com/systems/support/system_x_pdf/ibm_sw_msm_1.00-install-guide_vmware_noarch.pdf 

	To, install the MSM on VMWare operating system, the user should execute the
	command "./vmware_install.csh" 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 4.0).
	3. Select the Storelib (Inbox Storelib or Storelib from MSM package).

     2.8 MegaRAID Storage Manager(MSM) Installation on VMware ESXi 5.x
     -----------------------------------------------------------------

	For Vmware ESXi 5.x to work with MegaRAID Storage Manager Software, the SMI-S provider must be installed on the host server.  
	The management is performed through the MegaRAID Stroage Manager software installed on a remote server running Linux or Windows operating systems.
	

     2.9 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....




3.0 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" 


	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.

	Note:
	LSI SNMP Agent is not a supported configuration on VMware Operating system (VMware 3.5
        or VMware 4.0).

4.0  Usage information
______________________
		
    Detailed usage information can be found in the ServeRAID M Series or MR 
    Series Software User's Guide.


	4.1 MSM TCP/UDP Port Information
	==================================

	Component	Sending port/Source Port	Listening Port/Dest Port
	MSM GUI Client	49258 - 50058 (TCP)		49258 - 50058 (TCP)
	Framework 	49258 - 50058 (TCP)		3071(TCP/UDP)
	Popup		49152 - 65535 (TCP)		49152 - 65535 (TCP)
	MrMonitor	49152 - 65535 (TCP)		49152 - 65535 (TCP)

	Port 49152 - 65535 (TCP) – Dynamic ports, can be used by anyone.
	Port 3071(TCP/UDP) - Registered Port with IANA registration.

        4.2 MSM Japanese Language Support
	===================================
	
	If you install the MSM Japanese package onto Windows MegaRAID Storage       
        Manager, please follow steps 1-5 below to to complete installation.      
                                                                        
        1. Copy MSM Japanese package file "ibm_sw_msm_<version_string>-jp_anyos_noarch.zip"
	to temporary folder and extract. 

	<version_string> is the same version string in the MSM English package file name.

	2. Extract "ibm_sw_msm_<version_string>-jp_anyos_noarch.zip". There are two folders
	which is named "Windows" and "Linux". Open the folder "MegaRAID Storage Manager" in
	Windows folder using Windows Explorer, then choose all of folders and files
	(Common, Languages - two folders). Use right click of mouse to click "Copy" on selected
	file and folder.
	
	3. Open the folder where MSM was installed, 
	then right-click, and do "paste". Choose "overwrite all of files" when dialog to check
	"overwrite folder" is seen.

	4. Restart MSMFramework service by using either one of the two methods below.

	(A) open command prompt, then run the following commands.
		net stop  msmframework
                net start msmframework	
	
	(B)  open "service" in Administrative Tools, then restart MSMFramework service

	5. Restart MSM Popup process by using either one of the two methods below.

	(A) Open MegaPopup folder where MSM was installed, then double-click Popup.exe

	(B) Logout from windows, then logon again

	If you install Japanese package onto Linux MegaRAID Storage 
        Manager, please follow steps 1-5 below to complete installation.
	
	1. Copy MSM Japanese package file "ibm_sw_msm_<version_string>-jp_anyos_noarch.zip"
	to /tmp directory commands 

	<version_string> is the same version string in the MSM English package file name.
	
	2. Move to /tmp, then unzip the Japanese package file using following commands:
	
                cd /tmp/
                unzip -q  ibm_sw_msm_<version_string>-jp_anyos_noarch.zip
		
	Note: Two directories "Windows" and "Linux" are created after the extraction of the
	above file
	
	3. Move to Linux directory, then copy all of folders and files
	  (Common, Languages, and startupui.sh ) using following commands:
	
		cd "MegaRAID Storage Manager" 
		cp -af * <inst_dir>
	
	Note: <inst_dir> is the directory where MSM program was being installed.
	
	Note: Initial setting is /usr/local/MegaRAID Storage Manager                  

	4. Run the following command to restart MSM Framework service

		/etc/init.d/vivaldiframeworkd restart

	5. Restart MSM Popup process by using either one of the two methods below.

	(A) Run the following commands.

		 cd  "/usr/local/MegaRAID Storage Manager/MegaPopup"
                 ./popup  &

	(B) Logout from GNOME or KDE desktop, then logon again.

5.0  Unattended Mode
____________________

    To run this package in unattended mode, use the following command:

    1) ibm_utl_msm_17.05.01.03_linux_32-64.bin -s

	
6.0 Web Sites and Support Phone Number
______________________________________

  o  You can find support and downloads for IBM products from the IBM Support 
     Web site:

     http://www.ibm.com/support/
     
     You can find support and downloads specific to disk controllers by 
     searching for the "Disk Controller and RAID Software Matrix" from the 
     main support page.

  o  For the latest compatibility information, see the IBM ServerProven Web 
     site:

     http://www-03.ibm.com/servers/eserver/serverproven/compat/us/

  o  With the original purchase of an IBM hardware product, you have access 
     to extensive support coverage.  During the IBM hardware product warranty 
     period, you may call the IBM HelpCenter (1-800-IBM-SERV in the U.S.) 
     for hardware product assistance covered under the terms of the 
     IBM hardware warranty.


7.0 Trademarks and Notices
__________________________

  This product may contain program code or packages ("code") licensed by third 
  parties, as well as code licensed by IBM.   For non-IBM Code, the third 
  parties, not IBM, are the licensors.  Your use of the non-IBM code is 
  governed by the terms of the license accompanying that code, as identified 
  in the attached files.  You acknowledge that you have read and agree to the 
  license agreements contained in these files. If you do not agree to the 
  terms of these third party license agreements, you may not use the 
  accompanying code.

  IBM and ServeRAID are trademarks or registered trademarks of International 
  Business Machines Corporation in the United States and other countries.

  LSI and MegaRAID are trademarks or registered trademarks of LSI Logic, Corp 
  in the United States and other countries.

  Linux is a registered trademark of Linus Torvalds in the United States and 
  other countries.

  Other company, product, and service names may be trademarks or service marks 
  of others.


8.0 Disclaimer
______________

  THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
  IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED,
  INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS
  FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE
  INFORMATION IN THIS DOCUMENT.  BY FURNISHING THIS DOCUMENT, IBM
  GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.

  Note to U.S. Government Users -- Documentation related to
  restricted rights -- Use, duplication or disclosure is subject
  to restrictions set forth in GSA ADP Schedule Contract with
  IBM Corporation.