
                          HP MPIO DSM Manager
                               v2.00.01

                            READ THIS FIRST
                            ---------------


Please  read  the  following information before installing this release
of the HP MPIO DSM Manager.


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

I.    Contents
II.   Introduction
III.  Changes
IV.   System Requirements
V.    Installing HP MPIO DSM Manager
VI.   Uninstalling HP MPIO DSM Manager
VII.  Silent Installation
VIII. Using the HP MPIO DSM Manager
IX.   Limitations/Known Issues
X.    Notes
XI.   Contact Information

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

I.   Contents

     The installation media (CD) should contain the following:

         * READ THIS FIRST release information (readme.txt)
         * Setup files


II.  Introduction

     HP MPIO DSM Manager is a Microsoft Management Console(MMC) snap-in
     application  that  monitors  and  manages  HP  DSMs  in  a Windows
     Multipath input/output (MPIO) environment. You can use HP MPIO DSM
     Manager  to  view and  manage the disk devices supported by the HP
     DSMs in Windows MPIO environment.

     HP MPIO DSM Manager comprises of client and  server components, as
     described below:
     
     Client Component:
     -----------------
         * HP MPIO DSM Manager Snap-in
           The DSM Manager Snap-in integrates with Microsoft Management
           Console  and  helps manage the supported DSMs locally and/or
           remotely
          
     Server Components:
     ------------------
         * HP MPIO DSM Notification Utility
           The  Notification  Utility  sends  email  notifications  for 
           events generated by the supported DSMs.
           
         * HP MPIO DSM Volume Information Provider
           The   Volume  Information  Provider  generates  notification
           events for changes in drive letters, volume labels and mount
           points for the supported DSMs.
     

III. Changes

     1. Resolved an issue wherein silent installation failed to install
        the Notification Utility component.

     2. Added  support for  saving  the stand-alone Snap-in settings in
        the form of .msc files.


IV. System Requirements

     The  system  requirements  for installing HP MPIO DSM Manager, for
     each of the components described in Section II, are as follows:

     Client Component:
     -----------------
     
     * Supported platforms:

          - Windows 2000 Server and Advanced Server with Service Pack 4
          - Windows Server 2003 with Service Pack 2 (x86, IA64 and x64)
          - WindowsServer2003 R2 with ServicePack2 (x86,x64)          
                  
     Server components:
     ------------------
          
     * At least one of the following DSMs installed on the system.
         
         - HP MPIO Full Featured DSM for Windows for XP Disk Arrays  or
         - HP MPIO Full Featured DSM for Windows for EVA Disk Arrays or
         - HP MPIO Full Featured DSM for Windows for MSA Disk Arrays or
         - HP MPIO Full Featured DSM for Windows  for  EVA3000/5000 VCS
           4.xxx Disk Arrays
    
     
V.   Installing HP MPIO DSM Manager

     Ensure that the system  meets the requirements  for the components
     that you plan to install (refer Section III).

     It is recommended  to close all  open programs  before  proceeding
     with the install/modify/repair options of this package.

     1. To begin installation, log on as an administrator user.
     2. Select Start->Run, browse  to the HpMpioDsmManager.exe program
     3. Follow on-screen instructions to complete the installation.
  

VI.  Uninstalling HP MPIO DSM Manager

     Follow the steps below for uninstallation:

     1. Select Start menu --> Settings --> Control Panel.
     2. Double click "Add/Remove Programs".
     3. Under "Add/Remove Programs", select "HP MPIO DSM Manager 
        v2.00.01" and  click the Remove button.
     4. Follow on-screen instructions to complete uninstallation.


VII. Silent Installation

     Using silent installation

     Silent installation is useful if a large number of servers require
     software installation. 
     
     Syntax:
     <install drive>:\HPMpioDsmManager.exe /s /f1"C:\setup.iss" 
     /f2"C:\InstallLog.txt"

     The  <install drive>  refers  to  the  drive  which  contains  the
     installation media.
     The setup.iss is the response file from which information is taken
     for silent installation.
     The  InstallLog.txt  file  records  information  about the  silent
     installation.
     The ResponseResult section of the InstallLog.txt log file displays
     the   result  code,   indicating    whether   or  not  the  silent
     installation  succeeded. An  integer  value  is  assigned  to  the
     ResultCode keyname in the ResponseResult section.
     Following  are  the  list of common return values along with their
     descriptions in the ResultCode key:
     
     Result Code     Description
     -----------     -----------
      0              Success
     -1              General error
     -3              Required data not found in the setup.iss file
     -4              Not enough memory available
     -5              File does not exist
     -6              Cannot write to the response file
     -7              Unable to write to the log file
     -8              Invalid path to the  Silent response ( .iss ) file
     -51             Cannot create the specified folder
     -52             Cannot access the specified file or folder
     
     
     Note: The C: in /f1C: and /f2C: refers to a  local  drive  on  the
     system  or  a  network  drive  with  write  permission  on   which
     InstallLog.txt  can  be  written.  Also,  the  response  file gets
     created in this drive.
     
     For 32 bit systems, 
     <Default_Target_Dir> =
     "C:\Program Files\Hewlett-Packard\MPIO DSM MANAGER"
     
     For 64 bit systems, <Default_Target_Dir> = 
     "C:\Program Files (x86)\Hewlett-Packard\MPIO DSM MANAGER"
     
     <User_Target_Dir>   is   the  directory  where  you  do  the   new
     installation.  It  can  also  be  the  directory  of  an  existing
     installation.
     
     You must enclose the paths to the response file and the log  file,
     which  records  the  information about the silent installation, in
     quotes (").

     Installing HP MPIO DSM Manager:
     -------------------------------
     To make a new installation, take a backup of the new.iss file from
     the  kit and  rename  it  as setup.iss. Edit this file to suit the
     appropriate requirement  and  use  it with the parameter f1 in the
     command.
     
     For 64 bit systems, to install into the default directory 
     - In line 25 and 28 replace,
     "C:\Program Files\Hewlett-Packard\MPIO DSM MANAGER"  with
     "C:\Program Files (x86)\Hewlett-Packard\MPIO DSM MANAGER"
          
     To  install to a directory other than the default directory,  edit
     the setup.iss file.
     - In line 25 and 28 of the setup.iss file,
       Locate szDir=<Default_Target_Dir> and
       replace it with szDir=<User_Target_Dir>.
     
     To Install both client &  server components of the DSM Manager use
     the default setup.iss file.
       
     To install only the client component of the DSM Manager.
     - Remove the lines from 32 to 37.
     - In line 39, replace "Component-count=2" with "Component-count=1"
     - Remove line 41.
       
     To install only the server component of the DSM.
     - Remove the lines from 29 to 31
     - In line 39, replace "Component-count=2" with "Component-count=1"
     - Remove line 40.
     - In line 41, replace "Component-1=Server" with 
       "Component-0=Server"
       

     Upgrading HP MPIO DSM Manager:
     ------------------------------
     To  update  HP MPIO  DSM  Manager from a previous version to  this
     version, make  a  backup of the  update.iss file and rename it  as
     setup.iss. 

     To Install both client & server components of the DSM Manager  use
     the default setup.iss file.
       
     To install only the client component of the DSM Manager.
     - Remove the lines from 22 to 27.
     - In line 29, replace "Component-count=2" with "Component-count=1"
     - Remove line 31.
       
     To install only the server component of the DSM Manager.
     - Remove the lines from 19 to 21
     - In line 29, replace "Component-count=2" with "Component-count=1"
     - Remove line 30.      
     - In line 31, replace "Component-1=Server" with 
       "Component-0=Server"


     Uninstalling HP MPIO DSM Manager:
     ---------------------------------
     To   uninstall   HP  MPIO  DSM  Manager,  make  a  backup  of  the
     uninstall.iss  file  from  the  kit  and  rename it  as setup.iss.
     
     
     Creating response files for silent mode operations:
     ---------------------------------------------------
     
     The  HP  MPIO DSM  Manager package contains three  response  files
     (.iss files)- "new.iss", "uninstall.iss" and "update.iss" that are
     used   for   silent   mode  installation,  uninstallation,  update 
     respectively. In addition to these, the user can create their  own
     customized  response files for operations  (such as modify/repair)
     with different combinations of the Client and/or Server components
     selected/unselected.
          
     Customized  response  files can be created, by running the HP MPIO
     DSM Manager executable in the record  mode on  one of the systems.
     This response file can then be used for doing the same silent mode
     operation across multiple systems.
     
     The following steps can be used to create the response file:
     
     1. At the command prompt, type the following command
       <CMD> HpMpioDsmManager.exe /r
       
       where, /r option enables the record mode.
     
     2. This will  result in the  GUI installation to run in the record
        mode. Select the responses in  each screen and  run through the
        installation.
        
        Note: When selecting the response on  each screen, do not click
        on the "BACK" button and modify the  selection that was already
        done. The response file will have to be generated again in such
        case.
        
     3. The response file is created at the following location
        "%WINDDIR%\setup.iss"
        
        where, %WINDIR% is the Windows installation directory.
             
     4. Use this "setup.iss" file   for performing the same silent mode
        operation across multiple systems.
     
     
     Configuring Notification Information:
     -------------------------------------

        The Notification  Utility  cannot  be configured during  silent
        installation  because  the  configuration information cannot be
        captured in the silent installation response file.
        
        If   the   setup  was  run  in  silent  mode,  the notification
        information  has  to  be  manually configured on all systems by
        going to, "Start->Programs->Hewlett-Packard->MPIO DSM Manager->
        Configure Notification Utility". 
 
        As a workaround to automate this and configure the notification
        information on multiple systems the following needs to be done:
        
        Configure  the  Notification  Utility  on  one  of  the systems
        manually  and  then  copy  the  "SPNotificationConfig.xml" file
        present in  the  installation  directory  of this system to the
        installation directory of systems where the same  configuration
        information is needed. The default installation  directory  is,
        <PROGRAM_FILES>\Hewlett-Packard\MPIO DSM MANAGER\HP DSM Manager
     
     
VIII.Using the HP MPIO DSM Manager

     1. For help in using the HP MPIO DSM Manager, refer to the  online
        help  provided  by the HP MPIO DSM Manager. To view the  online
        help,
         - Open the HP MPIO DSM Manager by selecting the 
           Start menu->Program Files->Hewlett-Packard->MPIO DSM Manager
           ->Management Console. This  opens  the Microsoft  Management
           Console (MMC).
         - Right-click the  HP  MPIO  DSM  Manager node in the MMC  and
           select help.
     2. For help in configuration of the e-mail notification on failure
        events reported by the HP MPIO Full Featured DSMs  for Windows,
         - Open the Configuration utility by selecting the 
           Start menu->Program Files->Hewlett-Packard->MPIO DSM Manager
           ->Configure Notification Utility.
           This  opens  the  HP  MPIO DSM  Manager Notification Editor.
         - Click on the Help button
              
     
IX.  Limitations/Known Issues

     1. In a cluster environment, the drive  letter information   shown
        by the HP MPIO DSM Manager may not reflect the ownership of the
        disk by a cluster node.

     2. On  Windows 2000 server operating systems, the mof classes used
        by  MPIO may get unregistered at times. The GUI may not be able
        to  display the path details in such  scenarios. These  classes 
        may have to be re-registered by following the steps given below
        for the GUI to display the path details.

        - Open a command prompt window
        - Go to the "%DSM_DIR%\HP MPIO DSM\%DSM_TYPE%\mof" directory
        - Run "mofcomp -N:root\wmi mpio.mof"
        - Run "mofcomp -N:root\wmi pdo.mof"
        - Run "mofcomp -N:root\wmi mpdisk.mof"
        - Exit the command prompt
        - Close and re-open the HP MPIO DSM Manager

        Note: %DSM_DIR% is the folder chosen for the DSM installation.
              %DSM_TYPE% refers to one of XP, EVA or MSA DSMs.

     3. HP MPIO DSM Notification  Utility component of  the HP MPIO DSM
        Manager, should  be installed  only  on  systems where there is
        prior installation of the supported DSMs.
        If  the  Notification Utility component is installed before the
        DSM   installation,  then   the   "HP MPIO DSM Manager Monitor"
        service may have to be started manually after the supported DSM
        installation.
        
     4. Windows Server 2000 systems can be managed only locally, remote
        management of the systems is not possible.

     5. When  remotely  managing a system configured for Windows Server
        2003  for  Itanium  Based  Systems  or  Windows Server 2003 x64
        Edition,  the  disk  number and B-T-L information for the disks
        of the managed system may not be displayed in the GUI.
        

X.   Notes

     1. Before installing on systems running Microsoft Terminal Server,
        Microsoft  recommends that you change the Terminal Server  from
        Execution mode to Installation Mode. For detailed  information,
        refer to the Microsoft web site at 
        http://support.microsoft.com/default.aspx?scid=kb;en-us;186612.
     
     2. The  user  account,  used  to invoke the HP MPIO DSM Manager to
        remotely manage systems, must have 
        
        * administrative privileges
        * matching login credentials on the remotely managed system(s).
        
     3. This version of HP MPIO DSM Manager supports MMC 3.0.


XI.  Contact Information

     To  learn more about HP  and  HP  products, services  and support,
     visit the HP web site at http://www.hp.com.

     For  FAQs, software  updates,  and  contact  information  for  HP
     products, visit the HP Support Home Page at
     http://www.hp.com/go/storage.


--End--
