SNMP Configuration and Management Manual

IPX/SPX Subagent (G-Series)
SNMP Configuration and Management Manual—424777-006
13-14
Starting and Stopping the Subagent
agent-process
identifies a local or remote SNMP agent process from which you want the
subagent to receive manager requests. You can specify from one through five
alphanumeric characters, but the first character must be alphabetic. If you omit the
-a startup parameter, $ZSNMP on the subagent’s node is assumed. If you specify
more than one agent, separate agent process names with a space. Only one
subagent process can communicate with a particular SNMP agent process at a
time.
If the subagent cannot successfully establish an agent connection, it attempts to
establish one at the rate specified by the -k startup parameter.
After startup, you can use two MIB objects to control agent process connections.
To add a new agent connection, set the value of tdmNwSaAgentName to identify a
SNMP agent process. To activate or deactivate an agent connection, set the value
of tdmNwSaAgentState to connected or disconnected, respectively.
backup-cpu
identifies a CPU number in which the subagent’s backup process should run. Valid
values are -1 or 0 through 15. Specifying -1 is equivalent to omitting the -b startup
parameter; no backup process is started. The integers 0 through 15 identify CPUs.
If the specified CPU is not available, the subagent attempts to start the backup
process at the rate specified by the -k startup parameter. If you do not include the
NAME option to name the subagent process, the subagent cannot start a backup
process.
After startup, you can use three MIB objects to control the subagent backup
process. To create a backup process or change the CPU in which an existing one
is running, set the value of tdmNwSaBackupCPU to identify a CPU. To activate or
deactivate a backup process, set the value of tdmNwSaBackupState to
connected or disconnected, respectively. To cause the backup process to
become the primary process, set the value of tdmNwSaSwitchToBackupNow to
forceBackupTakeover.
ems-collector-process
identifies a local or remote EMS collector process to which the subagent should
send EMS events. You can specify from one through five alphanumeric characters,
but the first character must be alphabetic. If you omit the -c startup parameter,
event messages are sent to $0 on the subagent’s node.
If the subagent cannot establish a connection with the EMS collector process, it
generates no events. The subagent attempts to establish a connection at the rate
specified by the -k startup parameter.