  * 		HP Insight Management Agents for OpenVMS2 		(Formerly Compaq Management Agents for OpenVMS.)    		Installation Guide                   Version 3.01    F 	This document contains information required for installing and using 3 	Version 3.01 of the Management Agents for OpenVMS.     / 	The document contains the following sections:    2 	- Section 1, Installing TCP/IP and Enabling SNMP @ 	- Section 2, Prior to Installing the Management Agents SoftwareC 	- Section 3, Installing the Management Agents for OpenVMS Software # 	- Section 4, Working with MultiNet " 	- Section 5, Working with TCPware 	- Section 6, Notes  	- Section 7, Trademarks    ( 1.  Installing TCP/IP and Enabling SNMP ' --------------------------------------- E     Before you install the Management Agents for OpenVMS software on  *     your Alpha system, follow these steps:          1) Install TCP/IP      G        For TCP/IP installation instructions, refer to "TCP/IP Services           for OpenVMS Management".  	      2) Enable SNMP           B        If SNMP is not enabled on your system, follow these steps:   0 	  a. Execute the following command procedures:   # 	      $ @SYS$MANAGER:TCPIP$CONFIG     2   	  b. On the list of displayed options, select:   +               Option 3 - Server components    ;       	  c. On the next list of displayed options, select:    6               Option 17 - SNMP (for Version 5.1-EC0 4)3  	      Option 18 - SNMP (for Version 5.3 or later)   	5 	  d. On the next list of displayed options, select:    5 	      Option 3 - Enable & Start service on this node      2           e. Exit from the configuration utility.   A     3) Enter one of the following commands after the DCL prompt:   	         TCP/IP Command:        ---------------$         $ TCPIP SHOW CONFIGURATION -        _$ SNMP/FULL   A        The resulting display should be similar to the following:                 SNMP Configuration 	        .  	        .  	        .  '        Community   Type   Address_list  !        public      Read   0.0.0.0      E 	  a. If the "public" Community does not appear in the display, enter $              the following commands:   	     $ TCPIP SET CONFIG -$  	     _$ SNMP/COMMUNITY="public"/ -  	     _$ type=read      @ 	  b. Enter the following commands again after the DCL prompt to,              display the "public" Community:  )              $ TCPIP SHOW CONFIGURATION -  	     _$ SNMP/FULL     	     Note: 	     ----- A 	If you use MultiNet and TCPware from Process Software, refer to	 A 	Sections 4 and 5 of this document for information on setting up  4 	the products to operate with the Management Agents.    6 2.  Prior to Installing the Management Agents Software6 ------------------------------------------------------O     Before you install the Management Agents for OpenVMS Version 3.01 kit, you  M     must stop any Management Agents that are running. To do so, follow these       steps:    (     1) Enter the following DCL command:           $ SHOW SYSTEM   I     2) If any of the following processes are running, you must stop them  "        before installing the kit:   E          ------------------------------------------------------------ )           Version 1			Version 2 and later G          ------------------------------------------------------------		 "           ELM/GINKGO			WBEM$SERVER$           CPQHOST_MIB			WBEM$CPQHOST%           CPQSCSI_MIB			WBEM$CPQSTORE )           CPQSYSINFO_MIB		WBEM$CPQSYSINFO +           CPQSTDEQUIP_MIB		WBEM$CPQSTDEQUIP (           CPQHEALTH_MIB			WBEM$CPQHEALTH(           CPQTHRESH_MIB			WBEM$CPQTHRESH9           CPQNIC_MIB			WBEM$CPQNIC                         					WBEM$DCLSHOW  					WBEM$SVRCLU 					WBEM$CPQIDAG           ------------------------------------------------------------    F     3) While logged in to the same account from which you started the *        agents, enter one of the following:H        -----------------------------------------------------------------4         Prior to Version 2.1			Version 2.1 and laterH        -----------------------------------------------------------------/         $ @SYS$SPECIFIC: -			$ @SYS$SPECIFIC: - F         _$ [WBEM]STOP_WEBAGENTS                 _$ [WBEM]WBEM$SHUTDOWNH        -----------------------------------------------------------------  H     4) Enter the following command to verify that the Management Agents          software is not running:           $ SHOW SYSTEM  F     5) Remove the existing version of the Management Agents from your <        system by entering one of the following DCL commands:  &        $ PRODUCT REMOVE V72_MGMTAGENTS	        or &        $ PRODUCT REMOVE V73_MGMTAGENTS  J     6) Download and install the hp Secure Sockets Layer (SSL) for OpenVMS         kit from this web site:>        http://h71000.www7.hp.com/openvms/products/ssl/ssl.html     9 3.  Installing the Management Agents for OpenVMS Software < ------------------------------------------------------------J     Install the Management Agents for OpenVMS software on each system you L     want to monitor. On an OpenVMS Cluster, the agents need to be installed +     separately on each node of the cluster.   N     To install the Management Agents for OpenVMS software, follow these steps:  F 	1) Log in to the OpenVMS system using the SYSTEM account. If you needP            to use another privileged account, it must have the SETPRV privilege +            or all the following privileges:   Q        	   AUDIT, CMKRNL, DETACH, DIAGNOSE, LOG_IO, PHY_IO, NETMBX, OPER, PRMMBX, A            TMPMBX, SECURITY, SHARE, SYSLCK, SYSNAM, SYSPRV, WORLD   7 	2) Copy the Version 7.2-2, or 7.3 file to SYS$UPDATE:   		 		V72_MGMTAGENTS-V0300-30-1.EXE  		or 		V73_MGMTAGENTS-V0300-30-1.EXE    @ 	3) To unpack the kit, enter one of the following DCL commands:  	 , 	        $ RUN V72_MGMTAGENTS-V0300-30-1.EXE 		or% 		$ RUN V73_MGMTAGENTS-V0300-30-1.EXE   H 	4) To install the appropriate PCSI kit, enter one of the following DCL  	   commands:   " 		$ PRODUCT INSTALL V72_MGMTAGENTS 		or" 		$ PRODUCT INSTALL V73_MGMTAGENTS  J 	5) The file SYS$MANAGER:WBEM$LOGICALS.COM defines the logical names used Q            by the Management Agents for OpenVMS. This file lists all the logical  M            names supported by the agents, but the lines are commented out by  M            default. Using a text editor, open this file, uncomment the lines  O            containing the logical names you require, and edit the parameters if P            required. The file includes comments that explain the significance of            each logical name.   A 		- To use the DCL SHOW command application, define the following                     logical name:  		& 		  $ DEFINE/SYSTEM/EXEC WBEM$DCL TRUE   C 		- To make your cluster name known to the cluster subagent, define .                   the following logical name:  		6 		  $ DEFINE/SYSTEM/EXEC WBEM$CLUSTER_NODE clustername   G 		  The cluster name should correspond to a valid TCP/IP cluster alias.   F 		- To modify the default warning temperature for your system, define  		  the following logical name:   L                   $ DEFINE/SYSTEM/EXEC WBEM$WARNING_TEMP warningtemperature                    T                   The warning temperature corresponds to an integer value. If you doM                   not specify this value, a default value will be selected on S                   GS80 and later systems. This value is about 5 degrees C below the ?                   shutdown temperature defined for the system.    R                   For all other hardware, you need to specify a value relevant to S                   your system by defining this logical name. If you do not specify  S                   this value, the temperature threshold will display as 0 degree C, S                   and SNMP traps will not be generated. Refer to the documentation  M                   that came with your system for the appropriate temperature  "                   threshold value.  
 	    Note:             ----Q                   Environmental information (temperature, fan, power supply) will P                   not be available on New Generation Alpha Servers (GS1280, ES47T                   and so on) until a future release of OpenVMS.                       * 	6) Perform one of the following actions:   @ 		- If you are running SNMP, you must stop and restart ESNMP. In2                   SYS$MANAGER, run the following:  	  		  $ @TCPIP$SNMP_SHUTDOWN.COM+                   $ @TCPIP$SNMP_STARTUP.COM   : 		- If you are not running SNMP, you must start ESNMP. In $ 		  SYS$MANAGER, run the following:  	  		  TCP/IP Command File  		  -------------------	  		  $ @TCPIP$SNMP_STARTUP.COM  E 	7) Use the DCL command SHOW SYSTEM to ensure that SNMP is enabled on L            the system. The system should display TCP/IP Version 5.1 or later"            processes, shown below:  1            TCP/IP Version 5.1 or later Processes: 0            -------------------------------------              TCPIP$SNMP_1             TCPIP$OS_MIBS            TCPIP$HR_MIB 		   F   	   If you do not see all of these groups of processes, review your 5 	   TCP/IP setup and repeat Section 1, if necessary.    E 	8) To view environmental details (temperature, fan, and power supply M            information) on DS25, ES45 and later systems, you need to have the $            following on your system:                 " 	  	- OpenVMS Version 7.3 or later* 		- Firmware revision Version 6.2 or later   O            To view environmental details on GS80 and later systems, you need to & 	   have the following on your system: 	   " 		- OpenVMS Version 7.3-1 or later* 		- Firmware revision Version 6.2 or later 	 J 	   If your system meets or exceeds these requirements, you can enable theN            display of the environmental details by defining this logical name:  ) 	   $ DEFINE/SYS/EXEC WBEM$PRIVATEER TRUE  	   	  	   Important Notes: 	   ----------------G 	   - You do not need to make these entries for older hardware on which <              environmental information is already displayed.  I 	   - If you define this logical name on OpenVMS Version 7.3 systems with >              older firmware revisions, the system might crash.  N            - Environmental information will not be available on New GenerationN              Alpha Servers (GS1280, ES47, and so on) until a future release of              OpenVMS.  	 ? 	9) To run the Management Agents, enter the following commands:   & 	    $ SET DEFAULT SYS$SPECIFIC:[WBEM] 	    $ @WBEM$STARTUP   E 	10) To verify that the Management Agents are running, enter the DCL  F 	    command SHOW SYSTEM/PROCESS=WBEM*. The system should display the  	    following processes:    	     WBEM$CPQNIC               WBEM$CPQTHRESH               WBEM$CPQHEALTH               WBEM$CPQSTORE              WBEM$CPQSYSINFO              WBEM$CPQSTDEQUIP               WBEM$CPQHOST               WBEM$SERVER;              WBEM$DCLSHOW (if you defined the logical name) 9              WBEM$SVRCLU (if you have a clustered system) ;              WBEM$GSVIEW (only on a GS-Series Alpha server) N              WBEM$CPQIDA (only if Smart Array 5300A Controllers are installed)   D 	11) To ensure that the Management Agents survive a reboot, edit theV             SYSTARTUP_VMS.COM file. Insert this line in SYS$STARTUP:SYSTARTUP_VMS.COM,Q             following the entries required to start the TCP/IP and SSL processes:              .             $ @SYS$SPECIFIC:[WBEM]WBEM$STARTUP 	 I 	12) You are now ready to view your OpenVMS system or systems using a web T             browser or Insight Manager 7. Use either of the following instructions:   C 		- From a web browser, enter the following URL, which will connect Q                   you with the management agent of the system you want to manage:   *                   http://node_address:2381  Q                   For node_address, substitute the TCP/IP node name or address of 2                   the system you want to monitor.   C 		- If you are using Insight Manager 7, add the TCP/IP addresses of O                   your OpenVMS nodes to the device discovery section, perform a A                   device discovery, and select your OpenVMS node.      4.  Working with MultiNet  --------------------------- V     This section describes how to use the Management Agents for OpenVMS with MultiNet S     TCP/IP Version 4.3 for OpenVMS or later from Process Software. You must install Y     some components of the Compaq or hp TCP/IP product along with MultiNet to ensure that 9     all features of the Management Agents work correctly.   R     For more information about MultiNet, refer to the MultiNet User documentation.       T     Follow these instructions to set up MultiNet to work with the Management Agents      for OpenVMS:  K 	1) Install MultiNet TCP/IP Version 4.3 for OpenVMS or later, with required             patches.       ; 	2) Add the following line to the file MULTINET:SNMPD.CONF:  			 !            AGENTX_PEER 127.0.0.1    < 	3) Comment out SMUX_PEER from the file MULTINET:SNMPD.CONF.  H 	4) Extract TCPIP$ACCESS_SHR.EXE and TCPIP$ESNMP_SHR.EXE from the CompaqJ            TCP/IP Services V5.1 or later kit and place them in SYS$SHARE:      3            $ PRODUCT EXTRACT FILE/SELECT=<filename>  	   	 	   Note:             ---- O                 Make sure all files extracted from the TCP/IP Services kit have $                 WORLD:RE protection.  = 	5) Copy TCPIP$ESNMP_SHR.EXE to SYS$SHARE:UCX$ESNMP_SHR.EXE.    F 	6) Extract TCPIP$HR_MIB.EXE from the TCP/IP Services kit and place itK            in the SYS$SYSTEM directory. Define the following logical names:   <            $ DEFINE/SYSTEM/EXECUTIVE MULTINET_SNMP_AGENTX 1 / 	   $ DEFINE/SYSTEM TCPIP$AGENTX_INET_PORT 705  0 	   $ DEFINE/SYSTEM TCPIP$AGENTX_LOCAL_PORT 705    < 	7) Start MultiNet as described in the MultiNet User Manual.  H 	8) Start the Management Agents for OpenVMS using the following command:     1            $ @SYS$SPECIFIC:[WBEM]WBEM$STARTUP.COM   ! 	9) Enter the following command:    8            $ RUN/PROCESS=HR_MIB SYS$SYSTEM:TCPIP$HR_MIB   R     The Host Resources MIB (RFC 1514) supplied with TCP/IP Services will now work      with MultiNet.       5.  Working with TCPware   --------------------------U     This section describes how to use the Management Agents for OpenVMS with TCPware  S     TCP/IP Version 5.5 for OpenVMS or later from Process Software. You must install X     some components of the Compaq or hp TCP/IP product along with TCPware to ensure that9     all features of the Management Agents work correctly.   P     For more information about TCPware, refer to the TCPware User documentation.       S     Follow these instructions to set up TCPware to work with the Management Agents       for OpenVMS:  J 	1) Install TCPware TCP/IP Version 5.5 for OpenVMS or later, with required            patches.       A 	2) Add the following line to the file TCPWARE_COMMON:SNMPD.CONF:   !            AGENTX_PEER 127.0.0.1    B 	3) Comment out SMUX_PEER from the file TCPWARE_COMMON:SNMPD.CONF.  I 	4) Ensure that the SNMP agent and AGENT X service are enabled during the -            configuration of SNMP on TCPware.   	 H 	5) Extract TCPIP$ACCESS_SHR.EXE and TCPIP$ESNMP_SHR.EXE from the CompaqJ            TCP/IP Services V5.1 or later kit and place them in SYS$SHARE:   3            $ PRODUCT EXTRACT FILE/SELECT=<filename>   	 	   Note:             -----  O                 Make sure all files extracted from the TCP/IP Services kit have $                 WORLD:RE protection.  = 	6) Copy TCPIP$ESNMP_SHR.EXE to SYS$SHARE:UCX$ESNMP_SHR.EXE.    F 	7) Extract TCPIP$HR_MIB.EXE from the TCP/IP Services kit and place itK            in the SYS$SYSTEM directory. Define the following logical names:   5            $ DEFINE/SYSTEM TCPIP$AGENTX_INET_PORT 705 7            $ DEFINE/SYSTEM TCPIP$AGENTX_LOCAL_PORT 705     : 	8) Start TCPware as described in the TCPware User Manual.  H 	9) Start the Management Agents for OpenVMS using the following command:  1            $ @SYS$SPECIFIC:[WBEM]WBEM$STARTUP.COM   '        10) Enter the following command:    7            $ RUN/PROCESS=HR_MIB SYS$SYSTEM:TCPIP$HR_MIB   R     The Host Resources MIB (RFC 1514) supplied with TCP/IP Services will now work      with TCPware.     	 6. Notes: 	 --------- F 	1) The following default file locations are used as the launch pointsK            for the Availability Manager and the OpenVMS Management Station:   G 	   -------------------------------------------------------------------  	   Application 			Location G 	   ------------------------------------------------------------------- L            Availability Manager on      C:\Documents and Settings\All Users\H            Windows 2000 or XP           Start Menu\Programs\Availability<                                         Manager\dataan~1.lnk  = 	   OpenVMS Management Station   C:\WINNT\Profiles\All Users\ < 	   on Windows NT                Start Menu\Programs\OpenVMSA  	                                Management Station\openvm~1.lnk   7 	   OpenVMS Management Station   C:\Windows\Start Menu\ L            on Windows 95                Programs\OpenVMS Management Station\ 					openvm~1.lnk G 	   -------------------------------------------------------------------   H 	   If you are unable to launch one of these products, the products were;            probably not installed at the default locations.  		I 	2) If you ever need to restart the Management Agents without rebooting,  K            stop and then restart the Management Agents'processes using the              following commands:  ' 	   $ @SYS$SPECIFIC:[WBEM]WBEM$SHUTDOWN             .            .            .-            $ @SYS$SPECIFIC:[WBEM]WBEM$STARTUP     		 7.  Trademarks   --------------      R     Hewlett-Packard and the HP logo are trademarks of Hewlett-Packard Development 6     Company, L.P. in the U.S. and/or other countries. G     MultiNet and TCPware are registered trademarks of Process Software.   R     All other product names mentioned herein may be trademarks of their respective     companies.  D      Copyright 1997, 2003 Hewlett-Packard Development Company, L.P.