SNMP Configuration and Management Manual

SNMP Configuration and Management Manual—424777-006
7-1
7
Troubleshooting the SNMP Agent
This section contains general guidelines about what to do when you encounter
problems starting the SNMP agent. In this section, a general strategy for
troubleshooting appears first, followed by guidelines for:
•
Diagnosing startup errors
•
Identifying unavailable resources
•
Using EMS filters
•
Using trace records
•
Diagnosing request errors
Troubleshooting Strategy
Because of the interaction between the agent process, the subagents with which it
communicates, the HP TCP/IP subsystem, and the underlying LAN access and X25AM
subsystems, it might be difficult to determine whether problems arose within the SNMP
agent or one of the resources it uses.
When you are troubleshooting a problem, the best approach is to begin with the
assumption that the underlying subsystems are operating normally. Concentrate first
on the interactions of the subsystem in which the problem became apparent. The
guidelines provided in this section should help you.
If you suspect the trouble is in one of the underlying network resources being used by
the SNMP agent, start with the TCP/IP Configuration and Management Manual for
troubleshooting guidelines for the TCP/IP subsystem.
For systems running on a G-series or H-series RVU of the NonStop Kernel, if you
suspect the trouble is in the ServerNet LAN Services Access (SLSA) subsystem, refer
to the LAN Configuration and Management Manual.
If your SNMP agent is communicating through an X.25 subnet, refer to the SCF
Reference Manual for X25AM for information on examining the configuration and
status of the X25AM subsystem, initiating traces, and examining trace information.
Diagnosing Startup Errors
Most of the errors encountered at startup are configuration errors for either the SNMP
agent or the underlying resources it needs.
If you reset any of the default configuration values for the SNMP agent, review your
modifications to make sure they are correct. If possible, rename SNMPCTL and run the
SNMP agent with the WARM startup parameter, using the built-in default values to
isolate the problem.