If you will be using proxy accounts, you must set them up prior to issuing any ACMSMGR commands. If you have already set them up, you can skip to the example ACMSMGR command.

If you have not set up your proxies, you start by running the ACMSUDU utility. It's best to run this from the SYS$SYSTEM directory, since that is where ACMSUDU expects to find the file in which it stores proxies.

Start ACMSUDU as follows:

$ SET DEFAULT SYS$SYSTEM $ MCR ACMSUDU UDU>

If you have never set up an ACMS proxy before, create the proxy file now. Use the following command:

UDU> CREATE/PROXY

Now you need to define the proxy acounts. Proxy accounts have three components: the remote node, the remote account, and the local account.

The remote node is the node from which you will be accessing this node. You can either specify a node name or use the asterisk wildcard (*). Be aware that the Remote Manager treats every access as a remote access. This means that even if you access the Remote Manager only from the same node it runs on, you must create a proxy. In that case, the remote and local nodes are the same.

The remote account is the account on the remote node that will be accessing the Remote Manager. This is the user name on the remote node.

The local account is the account on the local node that will be used for authorization. It must be a valid account on the local node.

To add the proxy record, use the following command:

UDU> ADD/PROXY remote-node::remote-account local-account

Once the proxy record has been added, you can attempt to access the Remote Manager. Using a proxy does not require a separate login; you just issue the command. Also, do not define the ACMS$MGMT_USER logical. If it is defined, the ACMSMGR utility will look for login information and will not attempt proxy access.

Try this command:

$ AMCMSGR SHOW USERS/NODE=remote-manager-node

If no error messages are returned, a list of users logged in to the Remote Manager will be displayed. To reduce typing when issuing more commands, define the process logical ACMS$MGMT_SERVER_NODE to be the name of the node you want to access; this eliminates the need for using the /NODE qualifier in ACMSMGR commands.

If an error is returned, refer to Section 2.4.

2.4 Troubleshooting the ACMS Remote Manager Startup

The following sections provide troubleshooting information for the following problems:

• Problems starting ACMS ( Section 2.4.1)
• Problems starting the ACMS Remote Manager ( Section 2.4.2)
• Problems with ACMSMGR ( Section 2.4.3)

The following message is displayed when the ACMS run-time system is being started and the ACMS Central Controller (ACC) cannot open the Remote Manager configuration file:

%ACMSMGMT-I-CFGNOTOPEN, Unable to open management config file, using defaults

Possible reasons for this message include:

• The logical name ACMS$MGMT_CONFIG is not defined.
  Solution: This logical is typically defined in the file SYS$STARTUP:ACMS$MGMT_SETUP.COM, which is created by the SYS$STARTUP:ACMS_POST_INSTALL.COM command procedure. If the ACMS$MGMT_SETUP.COM file does not exist, run ACMS_POST_INSTALL.COM. If it does exist, edit it and add the definition of ACMS$MGMT_CONFIG. In either case make sure to run ACMS$MGMT_SETUP.COM, and then run the ACMSCFG utility to create a new, default file.
• The logical name ACMS$MGMT_CONFIG does not point to the configuration file, or the file has not been created.
  Solution: Ensure that the logical is defined properly (see the first bullet). If it is, you can create a new file by running the ACMSCFG utility. ACMSCFG will ask whether you want to create a new file. Answer yes, and then review the default settings.
• The ACC process does not have read access to the file pointed to by the logical name ACMS$MGMT_CONFIG.
  Solution: Modify the permissions on the file and restart ACMS.
• The ACMS_POST_INSTALL.COM procedure has not been run.
  Solution: Run this procedure to prepare your system to run the ACMS Remote Manager. See the first bullet for more information.

The Remote Manager writes error messages to two locations. If you are experiencing problems with the Remote Manager, check both locations for messages.

• SYS$ERRORLOG:ACMS$MGMT_SERVER.OUT (see Section 2.4.2.1)
• Remote Manager log, pointed to by logical ACMS$MGMT_LOG (see Section 2.4.2.2)

This is an ASCII text file that contains the redirected SYS$OUTPUT from the Remote Manager process. In general, messages appear in this log only if the Remote Manager is unable to write to its log file. The following conditions are exceptions:

• The literal "log_to_sysout" is passed to the Remote Manager startup procedure as P1 (for example, @SYS$STARTUP:ACMS$MGMT_STARTUP.COM log_to_sysout). Except for rare debugging circumstances, the "log_to_sysout" literal should not be passed to the Remote Manager startup procedure as P1.
• The Remote Manager experiences an access violation or other nontrapped fatal error.

Under these circumstances, OpenVMS exception output is written to ACMS$MGMT_SERVER.OUT.

If you experience problems with SNMP, refer to Section 6.9 for information about obtaining SNMP debug output.

LOG: Could not open file acms$mgmt_log

This message indicates that the Remote Manager could not open the file pointed to by the logical ACMS$MGMT_LOG. Possible reasons for this include:

• The logical is not defined, or is improperly defined.
  Solution: This logical is typically defined in the file SYS$STARTUP:ACMS$MGMT_SETUP.COM, which is created by the SYS$STARTUP:ACMS_POST_INSTALL.COM command procedure. If the ACMS$MGMT_SETUP.COM file does not exist, run ACMS_POST_INSTALL.COM. If it does exist, edit it and add the definition of ACMS$MGMT_LOG. In either case, make sure to run ACMS$MGMT_SETUP.COM, and then start the Remote Manager again.
• The device is full.
  Solution: If there is insufficient space for the log file, either redefine the logical to point to another device or make room on the device.
• The Remote Manager does not have write access to the file.
  Solution: Modify the permissions on the file or directory to which the ACMS$MGMT_LOG logical points.
• The ACMS_POST_INSTALL.COM procedure has not been run.
  Solution: Run this procedure to prepare your system to run the ACMS Remote Manager. See the first bullet for more information.

The messages written to the Remote Manager are determined by Remote Manager parameter settings (for example, mgr_audit_level, rpc_audit_level, and so on). Changing the parameter values results in either more or fewer messages appearing in the Remote Manager log. By default, messages with a severity of warning (w), error (e), or fatal (f) are written to the Remote Manager log. The log is pointed to by logical ACMS$MGMT_LOG.

You can use the ACMSMGR SHOW LOG command to display messages in the Remote Manager log. If the Remote Manager is not running, use the /LOCAL qualifier to read the log file directly. You must be logged in to a node with direct access to the log file in order to use the /LOCAL switch. For instance:

$ ACMSMGR SHOW LOG/LOCAL

See Section 3.7 for detailed information about the log file maintained by the ACMS Remote Manager.

mgr: f : Failure opening config file

The Remote Manager could not open the configuration file. See the discussion in Section 2.4.2.1.

mgr: f : No Interfaces were enabled. Process will shutdown

At least one interface must be enabled when the Remote Manager is started. Otherwise, it is impossible to communicate with the Remote Manager. If both interfaces are disabled, the Remote Manager will not start.

Solution: Issue the following command to see the current interface settings in the configuration file:

$ ACMSCFG SHOW INTERFACE

Enable at least one of the interfaces as follows (substitute SNMP for RPC if you want to enable the SNMP interface instead of the RPC interface):

$ ACMSCFG SET INTERFACE/INTERFACE=RPC/STATE=ENABLED

Now restart the Remote Manager.

procmon: e : Failure obtaining current collection states. Bypassingqti

This message can safely be ignored. It is generated when an ACMS entity is not started and the Remote Manager is parsing the collection table.

procmon: f : Failure waiting on mgmt$x_proc_mon_cond_var

This message can safely be ignored. It is generated when the process monitor thread is unexpectedly interrupted, generally during Remote Manager shutdown.

Remote Manager hangs during process startup

Most Remote Manager hangs during process startup are due to problems with the Portmapper. Verify that the Portmapper is functioning properly, and restart the Remote Manager.

rpc: f : Unable to initialize security. Aborting

The Remote Manager was unable to find a rights identifier in the UAF.

Solution: Create the rights identifier.

sec: e : Failure obtaining uaf info for ACMS$SNMP

If the SNMP interface is enabled, the ACMS$SNMP account must exits. Otherwise, it can perform no operations. If the account exists, it must be granted at least one of the following rights identifiers: ACMS$MGMT_READ, ACMS$MGMT_WRITE, ACMS$MGMT_OPER.

Solution: Either disable the SNMP interface ($[ACMSCFG,ACMSMGR] SET INTERFACE/INTERFACE=SNMP/STATE=DISABLED), or create the ACMS$SNMP account and grant it one of the rights.

sec: e : MGMT$L_ACMS$MGMT_READ Rights identifier not found in rights db!

The Remote Manager was unable to find the rights identifier in the UAF.

Solution: Create the rights identifier.

sec: f : ACMS$SNMP user has been granted no rights.

If the SNMP interface is enabled, the ACMS$SNMP account must be granted at least one of the following rights identifiers: ACMS$MGMT_READ, ACMS$MGMT_WRITE, ACMS$MGMT_OPER. Otherwise, the account cannot perform any operations. If it is not granted any rights identifiers, the thread will not start.

Solution: Either disable the SNMP interface ($[ACMSCFG,ACMSMGR] SET INTERFACE/INTERFACE=SNMP/STATE=DISABLED), or grant one of the rights to the ACMS$SNMP account.

snmp: e : Terminating....

This is a general error that simply reports that the thread is exiting. Look in the log file for the reason the thread is exiting. If there are no other error messages, look in SYS$ERRORLOG:ACMS$MGMT_SERVER.OUT.

snmp: f : Internal Initialization failed, exiting...

This is a general error that simply reports that the thread is exiting. Look in the log file for the reason the thread is exiting. If there are no other error messages, look in SYS$ERRORLOG:ACMS$MGMT_SERVER.OUT.

snmp: w : An esnmp error has occurred: -1

This message, if followed by termination of the SNMP thread, usually indicates that SNMP has not been set up properly on the node.

Solution: Configure and enable the SNMP interface. Restart TCP/IP and then restart the Remote Manager.

If this message is received, but is not followed by termination of the SNMP thread, the SNMP interface was able to recover from this error and there is no action that must be taken.

snmp: w : An esnmp error has occurred: -5

This is a warning message that refers to a problem communicating with the SNMP master agent. These errors usually are recoverable and the SNMP interface continues to work. In general, you can ignore this message.

However, frequent occurrences of this error may be attributable to a busy system and may indicate a need to modify one or more of the following parameters: snmp_agent_time_out, snmp_are_you_there, snmp_sel_time_out.

2.4.3 Problems with the ACMSMGR Utility

ACMSMGR problems typically fall into two categories:

• ACMSMGMT-W-NOCLNT_ATTACH messages (see Section 2.4.3.1)
• ACMSMGR hangs (see Section 2.4.3.2)

ACMSMGR can display the following message:

%ACMSMGMT-W-NOCLNT_ATTACH, Cannot create client for node NODE\NOCLNT_ATTACH

This message usually is followed by these messages:

%ACMSMGMT-E-NOCLIENTS, No clients created, cannot continue %ACMSMGMT-E-FAIL, Operation failed

These messages usually are returned when the Remote Manager is not running on the target node. Possible reasons for this include:

• The Remote Manager is not started.
  Solution: Start the Remote Manager as follows:

  $ @SYS$STARTUP:ACMS$MGMT_STARTUP

• The Remote Manager is not fully initialized. Complete initialization of the Remote Manager may take several seconds.
  Solution: Wait several seconds and then reissue the command that resulted in this error.
• The node name is incorrect.
  Solution: Double-check the spelling of the node name in the /NODE qualifier or in the ACMS$MGMT_SERVER_NODE logical.

ACMSMGR hangs are generally the result of a problem with the Portmapper or the Remote Manager. To verify that the Remote Manager has connected to the Portmapper, issue the following commands on the node on which the Remote Manager is running:

$ TCPIP TCPIP> SHOW PORTMAPPER

If the Remote Manager has connected, you will see a display similar to the following:

Program Number Version Protocol Port-number Process Service-name ---------------------- ------- -------- ----------- -------- ------------ 000186A0 ( 100000) 2 TCP 111 20407E5E PORTMAPPER 000186A0 ( 100000) 2 UDP 111 20407E5E PORTMAPPER 20000099 ( 536871065) 1 UDP 1023 20408675 20000099 ( 536871065) 1 TCP 1023 20408675

If the bottom two lines are missing (program number 20000099, version 1), then the Remote Manager is not connected to the Portmapper. Either the Remote Manager is not started or has terminated, or the RPC interface is not enabled.

If no lines are displayed (that is, if a "record not found" message is displayed), the Portmapper is not started. Refer to Section 2.2 for more information.

Solution: Correct the problem with the Remote Manager or the Portmapper.

This chapter describes how to manage the ACMS Remote Manager.

3.1 Overview

The ACMS Remote Manager runs on the same node as the ACMS run-time system but runs independently of it. The Remote Manager may be started and stopped at any time without affecting the ACMS run-time system. Similarly, the ACMS system can be started and stopped at any time without affecting the Remote Manager process. Remote management can be performed only on nodes where the Remote Manager has been started.

ACMS system managers configure the Remote Manager process (for example, which interfaces are enabled, what alarms to send) using a combination of the ACMSCFG utility (which provides initial configuration settings at process startup) and the ACMSMGR utility (to change settings once the process has started). Management consoles that support SNMP can also be used to configure and manage the Remote Manager.

Before the Remote Manager process can communicate with external entities, either SNMP or RPC must be configured and running on the appropriate nodes. See the Compaq ACMS Version 4.3 for OpenVMS Installation Guide for information about configuring and starting SNMP and RPC.

3.2 Configuring Remote Manager Startup

Before the Remote Manager is started, the configuration file should contain the appropriate settings. Both the ACMS run-time system and the Remote Manager read the configuration file during startup. If the ACMS Central Controller (ACC) process cannot read the configuration file when starting up, it uses default values. If the Remote Manager cannot read the configuration file when starting up, it logs an error and exits. By default, the configuration file is stored in SYS$SYSTEM:ACMS$MGMT_CONFIG.ACM. This location can be changed using the systemwide logical ACMS$MGMT_CONFIG. Use the ACMSCFG utility to change values in this file. The ACMSCFG utility allows ACMS system managers to set:

• The interfaces to be started
• Data-collection options
• Remote Manager run-time parameters
• SNMP traps

The configuration file is created during postinstallation with a set of default values. ACMS system managers should review these settings prior to starting the Remote Manager to determine whether the settings are appropriate for the node on which the process will run. Use the ACMSCFG SHOW commands as follows to display the settings:

$ ACMSCFG SHOW INTERFACE $ ACMSCFG SHOW COLLECTION $ ACMSCFG SHOW PARAMETER $ ACMSCFG SHOW TRAP

The ACMSCFG utility is a DCL command line tool that is invoked using a foreign command. The ACMSCFG utility accepts a number of command line arguments that determine what operations it should perform. The basic syntax for running the ACMSCFG utility is as follows:

ACMSCFG verb object qualifier

For example, to display the current data collection settings, you would use the following command:

$ ACMSCFG SHOW COLLECTION

You can get help on the available ACMSCFG commands and their syntax using the following command:

$ ACMSCFG HELP

You can define your own foreign command by using the following DCL command:

$ MYCOMMAND :== $SYS$SYSTEM:ACMS$MGMT_CONFIG_CMD

If you do this, you would substitute MYCOMMAND for ACMSCFG in the preceding examples.

When the ACMSCFG utility is started, it attempts to locate the ACMS$MGMT_CONFIG.ACM file by translating the logical name ACMS$MGMT_CONFIG. If that attempt fails, it looks in the default location, SYS$SYSTEM:ACMS$MGMT_CONFIG. If that lookup fails, ACMSCFG asks the user whether to create a new file. New files are created with default values in the directory that the logical name ACMS$MGMT_CONFIG translates to. If the logical name is not defined or does not include a directory specification, the default directory location is the current directory.

3.2.2 Displaying Current Values

Current ACMSCFG values can be displayed using the SHOW command, as follows:

ACMSCFG SHOW object

Valid SHOW objects are:

• Collection
• Control
• Interface
• Parameter
• Trap

The values for each object type correspond directly to fields in management configuration tables. These tables are discussed in Chapter 8.

The following is an example SHOW command and its output:

SPARKS> ACMSCFG SHOW COLLECTION Entity Entity Coll Collection Name Type Class State ------------------------------------- * * id enabled * * config enabled * * error enabled