Chapter 2 and Chapter 3 describe how to install and configure both the Remote Manager and the Remote Manager web agent. Chapter 4 and Chapter 5 explain how to manage data collection and how to use the Remote Manager to modify a running ACMS system.

Finally, Chapter 6 and Chapter 7 show you how to write programs that perform remote management using RPC and SNMP.

This chapter provides an overview of ACMS remote management.

1.1 Architecture and Implementation

The ACMS Remote Manager provides system managers with the capability of monitoring and managing their ACMS application environment across a network. The facilities that comprise the Remote Manager are based on a client/server architecture. Two protocols are supported for accessing the ACMS remote management server: Open Network Computing Remote Procedure Call (ONC RPC), which is used by command line utilities (provided with the remote management option) and can be called directly from user-written programs; and Simple Network Management Protocol (SNMP), for use with third-party management consoles.

As Figure 1-1 shows, users communicate with the ACMS Remote Manager over a TCP/IP network using one of the supported interfaces:

• The SNMP interface provides network access to ACMS management information using the industry-standard SNMP protocol. This protocol is supported by most leading system management packages (including PATROL from BMC).
• The RPC interface provides local or remote access to ACMS management information and is used by the ACMSMGR command line utility, the Remote Manager web agent, and user-written programs to access ACMS management information.
  ACMSMGR provides command line access to management information as well as control of the Remote Manager process. This utility can be run from any OpenVMS node that has TCP/IP network connectivity to the ACMS node. For more information about the ACMSMGR and its commands, see Chapter 5 and Chapter 11.
  The Remote Manager provides web-based access to management and process information via the Remote Manager Hyper-Media Management Object (ACMS$MGMT_HMMO). Integrated into Compaq's web-based enterprise management (WBEM) architecture, this server-based object communicates with the WBEM$SERVER management agent, which handles all communication to and from the client web browser. For more information about the Remote Manager web agent, see Chapter 3. For information about the WBEM architecture, visit the OpenVMS system management page:

  http://www.openvms.compaq.com/openvms/products/mgmt_agents/intro.html

Figure 1-1 ACMS Remote Manager Architecture

Using SNMP or RPC commands, ACMS system managers can configure and control the system data being collected, automatic variable monitoring, and operation of the interfaces themselves.

Communications between the ACMS Remote Manager and the ACMS run-time system are transparent. Users may be on the same or a different node than the Remote Manager, but the Remote Manager must be running on the same node as the ACMS run-time system it is monitoring or accessing.

The Remote Manager obtains initial configuration information during process startup from a user-maintained configuration file (described in Chapter 4). Once started, the Remote Manager provides ACMS system managers remote access to their ACMS application environment through the interfaces.

1.2 Remote Management Capabilities

The Remote Manager provides ACMS system managers with the ability to:

• Configure and enable the Remote Manager web agent for browser-based access to remote ACMS information (Chapter 3)
• Remotely manage the Remote Manager and set standard configuration options (Chapter 4)
• Remotely manage data collection and error reporting (Chapter 5), including:
  • Remotely view ACMS and OpenVMS system management information online
  • Remotely save and view snapshots of collected data
  • Remotely generate and view run-time error logs
  • Remotely configure SNMP traps
• Remotely modify ACMS run-time systems (Chapter 5)
• Write programs that remotely access management information online using ONC RPC (Chapter 6) and SNMP (Chapter 7)

This chapter describes how to prepare and run the ACMS Remote Manager software on a node where Compaq ACMS for OpenVMS, Version 4.4 has been installed. This chapter does not describe the actual installation. For information about installing Compaq ACMS for OpenVMS, Version 4.4, refer to the Compaq ACMS for OpenVMS Version 4.4 Installation Guide.

Terminology

The following terms are used in this chapter:

• Server node
  A node on which ACMS Version 4.4 has been installed and on which the ACMS Remote Manager server will run. Server nodes can be either ACMS application or submitter nodes, and can be managed either locally or remotely using one of the supported interfaces (RPC or SNMP). Server nodes are automatically client nodes, but not all client nodes are server nodes.
• Client node
  A node on which ACMS Version 4.4 may or may not be installed. Client nodes can get information from and perform operations on server nodes. However, users cannot obtain ACMS system management information from or perform system management functions on nodes that are client nodes only.

The following sections outline the steps required to get the ACMS Remote Manager running on an OpenVMS system. If you are an inexperienced user of ACMS, you should first read Section 2.2 and Section 2.3 for detailed information about how to set up a node for ACMS remote management.

This section describes setup for both client and server nodes. Server nodes automatically support all client functions; once a node is set up as a server, it can function as a client and a server without additional work. Client nodes can function only as clients.

When you complete the following procedures, the ACMS Remote Manager will be running on your system and you can access it using the ACMSMGR command line utility, the Remote Manager web agent, or a third-party or user-written client that uses one of the supported interfaces.

Note that the Remote Manager web agent requires some configuration before use. See Chapter 3 for detailed configuration instructions as well as for a brief overview of the browser interface.

2.1.1 Server Node Setup

Before you begin, you must have already installed the ACMS Version 4.4 kit on your system. Also ensure that you have the minimum supported version of TCP/IP (as described in the ACMS Software Product Description [SPD 25.50.xx]) installed on your node, and that it is operational. (If TCP/IP is not installed and operational, the ACMS Remote Manager will not run.) For information about TCP/IP setup, see Section 2.2.

Once you have installed the ACMS and TCP/IP software, perform the following steps to set up a Remote Manager server node:

1. Verify Portmapper (RPC) setup (see Section 2.1.1.1)
2. Run the ACMS postinstallation procedure (see Section 2.1.1.2)
3. Define process logicals and symbols (see Section 2.1.1.3)
4. Prepare the ACMS environment (see Section 2.1.1.4)
5. Start the ACMS Remote Manager (see Section 2.1.1.5)

Server nodes are automatically client nodes. Therefore, you do not need to perform the tasks in Section 2.1.2 for nodes that you set up as server nodes.

2.1.1.1 Verify Portmapper (RPC) Setup

Before you attempt to start the Remote Manager, ensure that the proper TCP/IP support is in place. This section provides an overview of the Portmapper (RPC) verification process. If you need more detailed information, or if you will be using third-party tools or writing your own SNMP management tools, see Section 2.2.

1. Look for the process TCPIP$PORTM (UCX$PORTM on older versions):

   $ SHOW SYSTEM/PROCESS=TCPIP*

   
   If you find the TCPIP$PORTM process, RPC is running and you can skip to Section 2.1.1.2. Otherwise, go to step 2.

2. See whether the Portmapper service is enabled:

   $ TCPIP TCPIP> SHOW SERVICE PORTMAPPER Service Port Proto Process Address State PORTMAPPER 111 TCP,UDP TCPIP$PORTM 0.0.0.0 Enabled

   
   The Portmapper should have both the TCP and UDP protocols defined. If it does not, you may need to configure the Portmapper (see Section 2.2.2). If the Portmapper state is Enabled, skip to Section 2.1.1.2. Otherwise, go to step 3.

3. To enable the Portmapper, enter the following commands:

   $ TCPIP TCPIP> ENABLE SERVICE PORTMAPPER TCPIP> SET CONFIGURATION ENABLE SERVICE PORTMAPPER TCPIP> EXIT

   
   Then restart TCP/IP. The Portmapper process does not automatically start when TCP/IP starts, so you may not see the TCPIP$PORTM process. The process starts the first time the Portmapper is accessed.

If you did not run the postinstallation procedure when you installed the ACMS Version 4.4 kit, do so now. For details, see Section 2.3.

1. Run the postinstallation procedure as follows:

   $ @SYS$STARTUP:ACMS_POST_INSTALL

2. When you are asked whether you want to configure the ACMS Remote Manager, answer YES:

   Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]? YES

3. Answer the questions according to the needs of your organization.

The ACMS$MGMT_ENV.COM command procedure is provided to define some symbols that make using the ACMSMGR utility simpler. For more information, see Section 2.3.2, or run the procedure now by entering the following command:

$ @SYS$STARTUP:ACMS$MGMT_ENV.COM

2.1.1.4 Prepare the ACMS Environment

You are now ready to start the Remote Manager. If you need more information about this procedure, see Section 2.3.3. Then follow these steps:

1. Ensure that the ACMSTART.COM procedure has been run by entering the following command:

   $ ACMS/SHOW SYSTEM

   
   If you get the following error, you must invoke the SYS$STARTUP:ACMSTART.COM procedure described in step 2:

   %DCL-W-ACTIMAGE, error activating image ACMSHR

   
   If you get a message indicating that the ACMS system is stopped, or if some information about the ACMS system is displayed, go to Section 2.1.1.5.

2. Invoke the ACMSTART command procedure:

   $ @SYS$STARTUP:ACMSTART

To start the ACMS Remote Manager, follow these steps:

1. Enter the following command:

   $ STARTMGR

2. Check that the Remote Manager processes (ACMS$MGMT_SVR, ACMS$TRACE_MON, and ACMS$MGMT_DCL) are started by entering the following command:

   $ SHOW SYSTEM/PROCESS=ACMS$*

3. If the processes are running, you should be able to communicate with them using ACMSMGR commands (see Section 2.1.3).
   If any of the process are not running, you can look for information in the following places:
   • Type out the SYS$ERRORLOG:ACMS$MGMT_SERVER.OUT text file:

     $ TYPE/PAGE SYS$ERRORLOG:ACMS$MGMT_SERVER.OUT

   • View the Remote Manager log file by using the following command:

     $ ACMSMGR SHOW LOG/LOCAL

   
   For more information about these sources, refer to Section 2.4.2.1 and Section 2.4.2.2.

All ACMS Remote Manager client nodes require that TCP/IP be installed and operational. (For information about TCP/IP setup, refer to Section 2.2.) Other than TCP/IP connectivity to the server node, no additional TCP/IP setup is required. (The Portmapper does not need to be running on the client node.)

The following sections describe how to set up an ACMS Remote Manager client node. You can skip these sections if you are installing the ACMS Remote Mangement server; server nodes are automatically client nodes.

If the client node will not be used as an ACMS submitter node, the ACMS Remote Option kit does not need to be installed. How you set up the client node depends upon whether the ACMS Remote Option kit has been installed.

• If the ACMS Remote Option kit has been installed, simply run the ACMS_POST_INSTALL.COM command procedure (see Section 2.1.2.1).
• If the ACMS Remote Option kit has not been installed, you must copy some files and define several symbols before you can use the ACMSMGR utility on a client node (see Section 2.1.2.2).

Once you have completed these tasks, you can try to communicate with a Remote Manager on a server node using the procedure in Section 2.1.3.

Note that you cannot obtain ACMS system management information or perform system management functions on nodes that are client nodes only. Client nodes can get information from and perform operations on server nodes only.

2.1.2.1 Run ACMS_POST_INSTALL.COM

Follow these steps to run the ACMS_POST_INSTALL.COM command procedure:

1. Run the postinstallation procedure as follows:

   $ @SYS$STARTUP:ACMS_POST_INSTALL

2. When you are asked whether you want to configure the ACMS Remote System Manager, answer YES:

   Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]? YES

3. Answer the questions according to the needs of your organization.
4. Now execute the ACMS$MGMT_ENV.COM command procedure to define some symbols that make using the ACMSMGR utility simpler:

   $ @SYS$STARTUP:ACMS$MGMT_ENV.COM

If you did not install the ACMS Remote Option kit (that is, if this node will not be an ACMS submitter node), follow this procedure. You will need access to a node with one of the ACMS Version 4.4 Run-Time kits installed.

1. Copy the ACMSMGR executable to your node from SYS$SYSTEM on the node that has ACMS Version 4.4 installed. Which executable to copy depends on the version of Compaq TCP/IP Services for OpenVMS (TCP/IP) you have installed:
   • If you are running Version 4.2 of TCP/IP, copy the ACMS$MGMT_CMD_UCX.EXE file to SYS$SYSTEM on your node.
   • If you are running TCP/IP Version 5.0 or higher, copy the ACMS$MGMT_CMD_TCPIP.EXE file to SYS$SYSTEM on your node.
2. Copy ACMS$MGMT_ENV.COM to your node and run it. This file is located in SYS$STARTUP of a node where ACMS Version 4.4 is installed. ACMS$MGMT_ENV.COM defines some symbols that make using the ACMSMGR utility simpler. Execute the command procedure as follows:

   $ @SYS$STARTUP:ACMS$MGMT_ENV.COM

Before you issue any ACMSMGR commands, you must either log in to the Remote Manager (see step 1) or use an ACMS proxy (see step 2). For detailed information, see Section 2.3.5.

1. To log in to the Remote Manager, you must have a valid user account and password on the node on which the Remote Manager is running. The following example commands log in to the Remote Manager on node SERVER, using account MYACCT and password MYPASS. (For more details, see Section 2.3.5.1.)

   $ DEFINE ACMS$MGMT_SERVER_NODE SERVER $ DEFINE ACMS$MGMT_USER MYACCT $ ACMSMGR LOGIN ACMS Remote Management -- Command line utility Password:MYPASS

   
   If the login succeeds, no messages are displayed. Go to step 3.
   If the login fails, check the following possible reasons:

   • You typed in an invalid user name or password.
   • You defined the ACMS$MGMT_SERVER_NODE logical incorrectly (wrong or misspelled node name).
   • You defined the ACMS$MGMT_USER logical incorrectly (wrong or misspelled account name).
   • The Remote Manager is not running on the node you specified.
   
   Refer to Section 2.4 for more help.
2. If you will be using ACMS proxies to access the Remote Manager, and you already know that you have a valid proxy account, go to step 3. If you have not set up proxies but would like to use them, create a proxy file on the node on which the Remote Manager will run. (For more information, see Section 2.3.5.2.)

   $ SET DEFAULT SYS$SYSTEM $ MCR ACMSUDU UDU> CREATE/PROXY

   
   Now you can add a proxy. To add a proxy, you need to know the following information:

   • The nodes and accounts from which you will access the Remote Manager
   • The account on the Remote Manager node you will use
   
   For example, assume you will be on node CLIENT using account MYACCT, and you will be accessing node SERVER using account SRVACCT. Enter the following command on node SERVER:

   UDU> ADD/PROXY CLIENT::MYACCT SRVACCT

3. You can now enter any of the ACMSMGR commands. For example:

   $ ACMSMGR SHOW INTERFACES

   
   This command results in output similar to the following:

   ACMS Remote Management -- Command line utility ACMS V4.4-0 Interfaces Display Time: 18-APR-2001 13:59:15.51 Enabled Running Get Set Alarms Time Last Node Interface State State Requests Requests Sent Alarm Sent ------ --------- ------- ------- -------- -------- ------ ----------------------- SERVER rpc enabled started 987 0 0 17-NOV-1858 00:00:00.00 SERVER snmp enabled started 0 0 0 17-NOV-1858 00:00:00.00

   
   If you get error messages instead, refer to Section 2.4.

There are three components to the TCP/IP setup for the ACMS Remote Manager:

• Reviewing the TCP/IP host names (see Section 2.2.1)
  In order for ACMS to parse and display node names consistently, ACMS TCP/IP and DECnet host names should be identical, following the DECnet Phase IV naming conventions. If the TCP/IP host name for a potential ACMS client or server system differs from this convention, you must define a six-character alias for that system in the hosts database.
• Portmapper (RPC) setup (see Section 2.2.2)
  Portmapper setup is required if you will be using the DCL command line utility ACMSMGR for remote management, or if you intend to write your own programs using the RPC API.
• SNMP setup (see Section 2.2.3)
  SNMP setup is required if you will be using third-party tools (such as PATROL from BMC) for remote system management, or if you will be writing your own SNMP management tools.

The information in the following sections applies mainly to server nodes on which the ACMS Remote Manager will run. Section 2.2.2 and Section 2.2.3 do not apply to ACMS Remote Manager client nodes.

2.2.1 Review TCP/IP Host Names

For consistent handling and display of commands that use the ACMSMGR /NODE qualifier and the ACMS$MGMT_SERVER_NODE logical, all potential ACMS systems should have a TCP/IP host name (or alias) that matches the current six-character DECnet host name.

To determine whether potential ACMS hosts are named appropriately, use the following command to list the contents of the TCP/IP hosts database:

$ TCPIP TCPIP> SHOW HOST

You will see a display similar to the following, where SPARKS.ACMS.COMPAQ.COM is the host name and SPARKS a system alias:

Host address Host name . . . 160.113.95.52 SPARKS.ACMS.COMPAQ.COM, SPARKS

Review this list and do one of the following for each potential ACMS host:

• If the host name (or alias) matches the current DECnet name in length and case, no further action is required for that host.
• If the host name (or alias) does not match the DECnet host name, define an alias as follows, where NAME is the name of the host system for which you want to define an alias, FirstAlias represents an existing alias, and SYSTEM represents the new alias you are assigning:

  $ TCPIP TCPIP> SET HOST NAME - _TCPIP> /ALIAS=("FirstAlias", "SYSTEM")

If you have defined any new aliases, restart TCP/IP to apply the changes made in the host database.