SNMP Configuration and Management Manual

Installing and Configuring the SNMP Agent

SNMP Configuration and Management Manual—424777-006

2-37

Remote Connections

The TCP/IP process used for communicating with SNMP managers does not have to

be on the same node as the agent process. As in the scenario featuring multiple SNMP

agents sharing a TCP/IP process on one host (Figure 2-6), you need to ensure that

every local and remote agent process sharing the TCP/IP process uses a unique

subnet address. In Parallel Library TCP/IP, the agents are not associated with TCP/IP

processes but rather just with the IP addresses. This procedure of altering the

ENDPOINT is the method by which you bind the agent to unique IP addresses in the

Parallel Library TCP/IP process.

In Figure 2-7, agent processes on three nodes are started using the built-in defaults.

Later, the default request/response connection definitions are altered for all three

SNMP agents. The following example illustrates altering connection definitions using

SCF:

SYSTEM \B

ASSUME PROCESS $ZSNMP

STOP ENDPOINT #DEFAULT

ALTER ENDPOINT #DEFAULT, HOSTADDR 130.25.86.2

START #DEFAULT

SYSTEM \A

ASSUME PROCESS $ZSNMP

STOP ENDPOINT #DEFAULT

ALTER ENDPOINT #DEFAULT, NETWORK \B.$ZTC0, &

HOSTADDR 130.25.86.1

START #DEFAULT

SYSTEM \C

ASSUME PROCESS $ZSNMP

STOP ENDPOINT #DEFAULT

ALTER ENDPOINT #DEFAULT, NETWORK \B.$ZTC0, &

HOSTADDR 130.25.86.3

START #DEFAULT

Note that the ENDPOINT definition for the SNMP agent on node \B uses the default

NETWORK attribute value, so this attribute need not be included in the ALTER

command.

Note. H-series RVUs do not provide support for Parallel Library TCP/IP.