Technical data
Configuring SNMP
13.6 Solving SNMP Problems
Regardless of the default trap type, you can control the trap type for each trap
destination using the appropriate tag (
v1
or
v2c
). For example, the following
entries in the TCPIP$VMS_SNMP_CONF.DAT file will cause a Version 1 trap
to go to the host with the IP address 120.2.1.2 (community name v1type), and a
Version 2 trap to go to the host with the IP address 120.2.2.2 (community name
v2type). Both traps will go to the well-known port 162:
trap v1 v1type 120.1.2.1
trap v2c v2type 12.2.2.2
13.6.6 Solving Management Client Response Problems
When an SNMP client is not getting a response to
set
,
get
,
getnext
,or
getbulk
requests, even though the SNMP server is configured and running, the problem
might be with the operation of the subagent or in the transmission of the query
or response message. To test, follow these guidelines:
1. Confirm that TCP/IP Services is running on your host. Enter:
TCPIP> SHOW INTERFACE
• If TCP/IP Services is not running, a response similar to the following is
displayed:
%TCPIP-E-INTEERROR, error processing interface request
-TCPIP-E-NOTSTARTED, TCP/IP Services is not running
• If TCP/IP Services is running, a response similar to the following is
displayed:
Packets
Interface IP_Addr Network mask Receive Send MTU
WE0 126.65.100.68 255.255.0.0 20298 5 1500
WF0 126.65.100.108 255.255.0.0 20290 2 4470
LO0 127.0.0.1 255.0.0.0 3290 3290 0
2. To ensure the successful startup of the SNMP master agent and subagents
and the operation of the TCPIP$SNMP_REQUEST utility (MIB browser),
confirm that the BIND resolver has been configured correctly by entering the
following command:
TCPIP> SHOW NAME_SERVICE
Refer to Chapter 5 for information about configuring the BIND resolver.
3. Check the status of the SNMP service using the following DCL command:
SHOW LOGICAL/TABLE=TCPIP$STARTUP_TABLE.
This command shows when each TCP/IP Services service startup completed
and which user performed each startup. If the SNMP service is not listed, it
was either shut down or it was not started.
4. Use the MIB browser on the host to retrieve the OID in question, as
described in Compaq TCP/IP Services for OpenVMS SNMP Programming
and Reference.
5. If the local query is successful, use a MIB browser from another host. This is
useful when timeout problems indicate that network delays are the cause of
the problem.
Configuring SNMP 13–27