CHAPTER
2-1
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
2
Troubleshooting Tools
This chapter describes the troubleshooting tools available for the Cisco Nexus 1000V and includes the
following topics:
• Commands, page 2-1
• Ping, page 2-1
• Traceroute, page 2-2
• Monitoring Processes and CPUs, page 2-2
• RADIUS, page 2-4
• Syslog, page 2-5
Commands
You use the command line interface (CLI) from a local console or remotely using a Telnet or Secure Shell
SSH session. The CLI provides a command structure similar to Cisco NX-OS software, with
context-sensitive help, show commands, multi-user support, and role-based access control.
Each feature has show commands that provide information about the feature configuration, status, and
performance. Additionally, you can use the following commands for more information:
• show system—Provides information on system-level components, including cores, errors, and
exceptions. Use the show system error-id command to find details on error codes:
switch# copy running-config startup-config
[########################################] 100%
2008 Jan 16 09:59:29 zoom %$ VDC-1 %$ %BOOTVAR-2-AUTOCOPY_FAILED: Autocopy of file
/bootflash/n1000-s1-dk9.4.0.0.837.bin.S8 to standby failed, error=0x401e0008
switch# show system error-id 0x401e0008
Error Facility: sysmgr
Error Description: request was aborted, standby disk may be full
Ping
The ping utility generates a series of echo packets to a destination across a TCP/IP internetwork. When
the echo packets arrive at the destination, they are rerouted and sent back to the source. Using ping, you
can verify connectivity and latency to a particular destination across an IP-routed network.
To Next Page
Loading...
