2-2
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 2 Troubleshooting Tools
Traceroute
The ping utility allows you to ping a port or end device. By specifying the IPv4 address, you can send a
series of frames to a target destination. Once these frames reach the target, they are looped back to the
source and a time stamp is taken. Ping helps you to verify the connectivity and latency to destination.
Traceroute
Use traceroute to do the following:
• Trace the route followed by data traffic.
• Compute interswitch (hop-to-hop) latency.
Traceroute identifies the path taken on a hop-by-hop basis and includes a time stamp at each hop in both
directions. You can use traceroute to test the connectivity of ports along the path between the generating
switch and the switch closest to the destination.
Use the traceroute CLI command to access this feature.
If the destination cannot be reached, the path discovery starts, which traces the path up to the point of
failure.
Monitoring Processes and CPUs
There CLI enables you to for monitor switch processes. CPU status, and utilization.
This section contains the following topics:
• Identifying the Running Processes and their States, page 2-2
• Displaying CPU Utilization, page 2-3
• Displaying CPU and Memory Information, page 2-4
Identifying the Running Processes and their States
Use the show processes command to identify the processes that are running and the status of each
process. (See Example 2-1.) The command output includes the following:
• PID—Process ID.
• State —Process state.
• PC—Current program counter in hex format.
• Start_cnt—How many times a process has been started (or restarted).
• TTY—Terminal that controls the process. A “-” usually means a daemon is not running on any
particular TTY.
• Process—Name of the process.
Process states are as follows:
• D—Uninterruptible sleep (usually I/O).
• R—Runnable (on run queue).
• S—Sleeping.
• T—Traced or stopped.
To Next Page
Loading...
