Cisco N5K-C5010P-BF Troubleshooting Guide - Page 140

Traps, Traps not received, DNS, DNS resolution not working correctly

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 140 highlights

Traps Chapter 7 Troubleshooting System Management Issues Send document comments to [email protected]. • Check to see if the destination syslog server is accessible from VRF management. Use the ping 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 command. 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: • 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. Solution Use the following commands to check whether the proper VRF is configured for the SNMP host and that the trap is enabled: • snmp-server enable traps • snmp-server host use-vrf where x.x.x.x is the IP address of the trap receiving device. 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 OL-25300-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
7-4
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 7
Troubleshooting System Management Issues
Traps
•
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
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:
•
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.
Solution
Use the following commands to check whether the proper VRF is configured for the SNMP host and that
the trap is enabled:
•
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.
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: