SNMP Configuration and Management Manual

Host Resources Subagent
SNMP Configuration and Management Manual—424777-006
11-23
Manager Timeouts
System Call Suspension
If the subagent does not respond in a timely fashion to a manager request but appears
to be running, the subagent might be suspended because it cannot complete a system
call needed to process the request or refresh MIB values. This situation can occur
when the subagent attempts to retrieve MIB values for remote printers if the connection
to the remote system, the remote system itself, or a remote printer becomes unstable.
Remote printers are known as “pseudo” printers. They are actually Spooler collector
processes running on a remote system but are configured in the Spooler system as
printers. You can use the SPOOLCOM DEV command to display the names of pseudo
printers. Their names consist of a node name and a process name; for example,
\mysys.$s. To determine the status of a remote printer, use the SPOOLCOM DEV
command, specifying a particular remote printer name:
DEV \MYSYS.$S, STATUS DETAIL
You can also use the TACL STATUS command:
STATUS \MYSYS $S, DETAIL
To determine the status of the subagent process, use the TACL STATUS command:
STATUS $ZHMSA,DETAIL
If the WAIT state is %004 (LDONE) and the process time does not change (increase),
the subagent is most likely waiting for an internal call to complete.
In many cases, this condition is transient. The subagent becomes responsive again as
soon as the communications line or remote system become available. If you
experience this problem frequently, you can modify the subagent’s initialization file to
exclude offending devices. Refer to information about the -e startup parameter under
Starting and Stopping the Subagent on page 11-12 for complete information about
encoding initialization file entries.
Large MIBs
The larger the MIB being maintained, the longer it takes the subagent to refresh the
values of MIB objects. You can minimize data refresh wait time in several ways:
•
The -d and -s startup parameters control the frequency at which the subagent
refreshes MIB values. You can specify long refresh intervals at startup and then
force refreshes after startup when needed by setting the values of two objects in
the zhrmRefresh group: zhrmDynamRefreshNow and zhrmStableRefreshNow.
•
The -e startup parameter specifies an initialization file that defines devices and
processes to exclude from the MIB. You can use this parameter to limit the
resources monitored by the subagent to only those of particular interest at any
time.