Traps; Dns - Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual

Traps

S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m .
•
•
•
Traps
Traps not received
The results of traps are not received.
Possible Cause
The traps might not be enabled or the SNMP host might not be accessible.
The following are possible causes:
•
•
•
•
Solution
Use the following commands to check whether the proper VRF is configured for the SNMP host and that
the trap is enabled:
•
•

DNS

DNS resolution not working correctly
When specifying a host name using DNS or VRF, the host name is not resolved and an error occurs.
Possible Cause
The DNS client is not configured correctly.
Solution
Use the following commands to configure the DNS client:
Cisco Nexus 5000 Series Troubleshooting Guide
7-4
Check to see if the destination syslog server is accessible from VRF management. Use the ping
<dest-ip> vrf management command to ping the server.
Check that the syslog configuration on the DUT has use-vrf management.
Example:
logging server 10.193.12.1 5 use-vrf management
Check that the appropriate logging level is enabled to send logging messages. Use the show logging
info command. If the logging level is not appropriate, then set the appropriate level using the
logging level <feature> <log-level> command.
Traps might not be enabled.
The SNMP host might not be accessible.
A firewall might be blocking access.
An access list might be blocking UDP port 162.
snmp-server enable traps <trapname>
snmp-server host <x.x.x.x> use-vrf <vrf-name>
where x.x.x.x is the IP address of the trap receiving device.
Chapter 7 Troubleshooting System Management Issues
OL-25300-01