

       README File for OpenView Operations Agents and SPI for OpenVMS
       ==============================================================

 To manage an OpenVMS system from an OpenView Management Server, you 
 must complete actions on both the Management Server system and on 
 the OpenVMS system.  These include:
 
    - Verifying that prerequisites are met on the OpenVMS system
    - Configuring the Management Server
    - Installing the Agent and Smart Plug-In (SPI) software on the 
      OpenVMS system
    - Starting the Agent and SPI software
    - Making templates and policies available to the OpenVMS system
 
 Some of the steps differ depending on whether your Management Server is 
 running on a UNIX or a Windows system.   Please follow
 the directions in the relevant section.  Refer to the OpenView Operations 
 documentation for your Management Server if you need additional instructions 
 for completing any of the tasks performed on the Management Server.
 
-------------------------------------------------------------------------------
Kit Prerequisites
-------------------------------------------------------------------------------

  First, you must verify that your OpenVMS system meets the 
  prerequisites. OpenView Agents for OpenVMS works on OpenVMS Version 7.3-1 
  or later. Make sure that the required OpenVMS patches listed below have 
  been applied.  The patches are available at the services web site:

        http://www2.itrc.hp.com/service/patch/mainPage.do

  OpenVMS V7.3-1
  --------------
        - VMS731_RPC V4.0 or later
        - VMS731_UPDATE V4.0 or later
        - VMS731_PCSI V2.0 or later (required for the UPDATE kit) 

      HP recommends that you also install the DCE Denial of Service Security
      Patch (DCE_030_SSRT3608 V1.0).

  OpenVMS V7.3-2
  --------------
      - VMS732_UPDATE V2.0
      - VMS732_RPC V3.0


  OpenVMS V8.2 (Alpha)
  OpenVMS V8.2 (Itanium)
  ----------------------
    There are no prerequisites for customers who are using OpenVMS V8.2.

  TCP/IP Services for OpenVMS
  ---------------------------
    If you are managing your OpenVMS system from a UNIX Management Server, 
    you must enable the rexec (remote execution) service so that the 
    installation can be performed from the Management Server.
    
    
-------------------------------------------------------------------------------
Configuring the Management Server 
-------------------------------------------------------------------------------

  The Management Server from which you manage your OpenVMS system requires 
  a number of configuration updates.  The steps you need to perform differ 
  depending on whether your Management Server is running on a UNIX or a
  Windows system.  Please follow the directions in the appropriate section.
  
-----------------------------------------------------------------------------
Configuration Steps for a UNIX Management Server (OVOU) 
-----------------------------------------------------------------------------
  
  For a UNIX Management Server, configuration updates are supplied within a
  gunzip-compressed depot file.  To distribute the configuration updates on 
  a UNIX Management Server, follow the numbered steps below:

1) Log into your OVOU server.

2) Copy the required files to the UNIX Management Server into a temporary
   directory such as /tmp.  The files are:

    Description       HP-UX OVO Server            Solaris OVO Server
    ---------------------------------------------------------------
    A.07.12 Agent     OVOPC-VMS-CLT.depot.gz      OVOPC-VMS-CLT-sol.depot.gz
    for Alpha depot
    
    A.07.23 Agent     PHSS_31237                  ITOSOL_00343
    for Alpha patch
    
    A.07.23 Agent     OVOPC-VMSIA-CLT.depot.gz    OVOPC-VMSIA-CLT-sol.depot.gz  
    for Itanium depot

    New Templates,    PHSS_31238                  ITOSOL_00344
    MotifGUI install
    patch

3) To make the required configuration updates to the Management Server, 
   perform the following lettered steps:

   A) Add support for the OpenVMS agent to your Management Server:

      To add support for the OpenVMS Alpha A.07.23 agent, you need the 
      A.07.12 OpenVMS Alpha agent software depot, the A.07.23 OpenVMS Alpha 
      agent patch, and the patch containing templates and MotifGUI capability.
   
      - Install the A.07.12 Agent for Alpha where <ovopc-clt-file> is 
        OVOPC-VMS-CLT or OVOPC-VMS-CLT-SOL depending on your OVO Server 
        platform:
        
          # cd / 
          # gunzip <your-temp-directory><ovopc-clt-file>.depot.gz 
          # swinstall -s <your-temp-directory><ovopc-clt-file>.depot \
            OVOPC-CLT-ENG.<ovopc-clt-file>
      
      - Install the A.07.23 Agent for Alpha patch using the instructions
        that come with that patch file.
            
      - Install the patch containing the new templates and MotifGUI install
        capabilities using the instructions that come with that patch file.

      To add support for the OpenVMS Itanium A.07.23 agent, you need the 
      A.07.23 OpenVMS Itanium agent software depot, and the patch containing 
      templates and MotifGUI capability.
   
      - Install the A.07.23 Agent for Itanium where <ovopc-clt-file> is 
        OVOPC-VMSIA-CLT or OVOPC-VMSIA-CLT-SOL, depending on your OVO Server 
        platform:
        
          # cd / 
          # gunzip <your-temp-directory><ovopc-clt-file>.depot.gz 
          # swinstall -s <your-temp-directory><ovopc-clt-file>.depot \
            OVOPC-CLT-ENG.<ovopc-clt-file>
      
      - Install the patch containing the new templates and MotifGUI install
        capabilities using the instructions that come with that patch file.

   B) Load the AgentPlatform file into the OpenView database:

      # opcagtdbcfg -p hp/ia64/vms -d -f
      # opcagtdbcfg -p hp/alpha/vms -d -f

   C) Upload the templates so that they can be distributed later to the
      agent nodes:

      # opccfgupld -replace VMSAgent
      # opccfgupld -replace VMSSPI

      NOTE: These commands replace the templates supplied with 
            earlier versions of the OpenView Agent for OpenVMS.  If you 
            have made customizations to any of those templates, save them
            with a different template name before executing the above commands.
            If you have never completed this step before, use the -add command
            instead of the -replace command.

4) Add the OpenVMS nodes and clusters you want to monitor.
   
5) Add the OpenVMS message group to the responsibilities matrix for
   the users who will monitor messages from the SPIs.
  
-------------------------------------------------------------------------
Configuration Steps for a Windows Management Server (OVOW)
-------------------------------------------------------------------------

  Follow the numbered steps below if you plan to manage your OpenVMS system 
  from a Windows Management Server. Note that the installation should be done
  on the C: drive of the Windows Management Server.

1) Log into the Windows Management Server.

2) Go to the directory that contains the Zipped OpenVMS PCSI files:

     for Alpha servers:
     <DOS prompt> cd C:\Program Files\HP OpenView\Packages\OpenVMS\Alpha

     for Integrity servers:
     <DOS prompt> cd C:\Program Files\HP OpenView\Packages\OpenVMS\Itanium

3) Unzip the .PCSI files that you want to install on your managed node.
   There are two sets of files, one set for Alpha servers and one set for
   Integrity servers. Replace <arch> and <kit> with the strings
   from the file names.

Note: If you are using WinZip V9 or later, rename opc_pkg.Z to opc_pkg.zip
and spi_pkg.Z to spi_pkg.zip prior to unzipping. 

   The files:
        opc_pkg.Z and
        spi_pkg.Z
   Will unzip into:
	HP-<arch>VMS-OVOAGENTS-<kit>.PCSI and
        HP-<arch>VMS-VMSSPI-<kit>.PCSI


4) FTP the resulting .PCSI files to your managed node by entering the 
   following commands (replacing <arch> and <kit> with the strings
   from the file names):
  
      <DOS prompt> ftp <your OpenVMS node>
      SYSTEM
      <password>
      ftp> cd SYS$UPDATE:               (The colon is required.)
      ftp> bin
      ftp> put HP-<arch>VMS-OVOAGENTS-<kit>.PCSI
      ftp> put HP-<arch>VMS-VMSSPI-<kit>.PCSI

Note: Install the OVOAGENTS and VMSSPI on your managed node or nodes before
performing the next set of steps.

5) Add your node to the OpenVMS operations console.

6) Upload the new policies for the OpenVMS Agent and for the OpenVMS SPI by
   running the following command procedure:

	%OvInstallDir%\install\OpenVMS\Upload_Policies.bat

7) Deploy the policies that are provided with this patch kit. For example,
   go to both of the following directories and select all the files:

	\Policy management\Policy groups\OpenVMS_policies
        \Policy management\Policy groups\OpenVMS_SPI_policies

   Select the polices from either directory. Either drag and drop the policies
   from the directory to the managed node OR select the policies to deploy,
   right click at the policy window, select all tasks, select deploy on, check
   node to deploy the policy on and select OK.
   
-------------------------------------------------------------------------------
Installing the OpenVMS Agent and SPI Software
-------------------------------------------------------------------------------

  The steps for installing the Agent and SPI software differ depending on 
  whether you are going to manage them with a UNIX or a Windows Management 
  Server.  Please follow the directions in the appropriate section.

-----------------------------------------------------------------------------
Installation Steps if Managing OpenVMS from a UNIX Management Server (OVOU) 
-----------------------------------------------------------------------------

1) Log into your OVOU server and run the opc GUI.
   - From the Unix command line prompt, enter the command opc.

2) In the VPO Node Bank window, select the nodes on which you want to
   install the OpenVMS Agent and SPI Software.
   
3) Navigate down the Actions menu to Agents and then Install/Update SW & Config.

4) In the components box, select Agent Software and de-select any other   
   components.  If this is not the first time that you have installed the
   OpenVMS Agent, select Force Update in the Options box.  Click OK.
   
5) A set of scripts will be run on your behalf to perform the installation on
   the remote node.  You will need to supply the password for the SYSTEM account
   twice.  In some cases, the script may not be able to determine whether
   the version of OpenVMS on the target node is supported by the agent.  In
   this case, you will need to answer a question about whether it is.  The
   script then installs the PCSI kits for both the Agent and the SPI.

------------------------------------------------------------------------------
Installation Steps if Managing OpenVMS from a Windows Management Server (OVOW) 
------------------------------------------------------------------------------

To install the kit, follow these numbered steps:

1) Log into the system account.

2) Set your default directory to SYS$UPDATE, which is where the product
   kits were copied while configuring the Management Server:

   $ SET DEFAULT SYS$UPDATE

3) Use the PRODUCT INSTALL command to install the kits (you must install
   the OVOAGENT product before the VMSSPI product):
   
   $ PRODUCT INSTALL OVOAGENTS 
   $ PRODUCT INSTALL VMSSPI 

-------------------------------------------------------------------------------
Using the OpenVMS Agent and SPI
-------------------------------------------------------------------------------
   
   The installation procedures of the OpenVMS Agent and SPI install most
   files in subdirectories under SYS$SPECIFIC:[OVO].  Sharable images are 
   installed in SYS$SYSROOT:[SYSLIB].   Several files are installed in 
   standard system directories such as SYS$STARTUP and SYS$MANAGER.  
    
1) To start the OVO agents, enter these commands (when requested, also 
   enter the name of your Management Server):

        $ @SYS$MANAGER:OVO$CONFIG
        
 	$ @SYS$STARTUP:OVO$STARTUP

2) Use the Management Server to distribute the templates or deploy the  
   policies that you want to use on your OpenVMS node.
    
   - From a UNIX Management Server, distribute templates.
    
        The templates that are provided with the OpenVMS Agent and SPI are 
        in these template groups:

            OpenVMS
            SPI for OpenVMS

   - From a Windows Management Server, deploy policies.
    
        The policies provided with the OpenVMS Agent and SPI are 
        in these policy groups:

            OpenVMS_policies
            OpenVMS_SPI_policies

3) Start the OSSPI:

	$ @SYS$STARTUP:VMSSPI$STARTUP

   To customize the SPI configuration files, refer to the manual "HP OpenView 
   Smart Plug-In (SPI) for OpenVMS User's Guide."  You can find this manual at
       SYS$SPECIFIC:[OVO]VMSSPI_USER_GUIDE.PDF
