You use the CLI from a local console or remotely using a Telnet or SSH session. The CLI provides a command structure similar to the 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 show system command for information about the system-level components, including cores, errors, and exceptions. To get detailed information about error codes, use the show system error-id command.

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

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.

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. After these frames reach the target, they are looped back to the source and a timestamp is taken.

Use the traceroute feature to do the following:

• Trace the route followed by data traffic.

• Compute inter-switch (hop-to-hop) latency. Traceroute identifies the path taken on a hop-by-hop basis and includes a timestamp at each hop in both directions.

• Test the connectivity of ports along the path between the generating switch and the switch closest to the destination.

  If the destination cannot be reached, the path discovery starts, which traces the path up to the point of failure.

Use the traceroute command to access this feature.

Use the show processes command to identify the processes that are running and to view the status of each process.

switch# show processes ?
cpu Show processes CPU Info
log Show information about process logs
memory Show processes Memory Info
 
switch# show processes
 
PID   State  PC      Start_cnt   TTY     Process
----- ----- -------- ----------- ---- -------------
1 S b7f9e468 1 - init
2 S 0 1 - migration/0
3 S 0 1 - ksoftirqd/0
4 S 0 1 - desched/0
5 S 0 1 - migration/1
6 S 0 1 - ksoftirqd/1
7 S 0 1 - desched/1
8 S 0 1 - events/0
9 S 0 1 - events/1
10 S 0 1 - khelper
15 S 0 1 - kthread
24 S 0 1 - kacpid
101 S 0 1 - kblockd/0
102 S 0 1 - kblockd/1
...

Use the show processes cpu command to display CPU utilization. The command output includes the following

• Runtime(ms)—CPU time the process has used, expressed in milliseconds.

• Invoked—Number of times the process has been invoked.

• uSecs—Microseconds of CPU time in average for each process invocation.

• 1Sec—CPU utilization in percentage for the last one second.

Note	VSE consumes most of the CPU ( 99%) when the system is idle. This usage of CPU causes vCenter to flag CPU usage warning. This warning can be ignored or acknowledged on vCenter.

switch# show processes cpu
 
PID Runtime(ms) Invoked uSecs 1Sec Process
----- ----------- -------- ----- ----- -----------
1 922 4294967295 0 0 init
2 580 377810 1 0 migration/0
3 889 3156260 0 0 ksoftirqd/0
4 1648 532020 3 0 desched/0
5 400 150060 2 0 migration/1
6 1929 2882820 0 0 ksoftirqd/1
7 1269 183010 6 0 desched/1
8 2520 47589180 0 0 events/0
9 1730 2874470 0 0 events/1
10 64 158960 0 0 khelper
15 0 106970 0 0 kthread
24 0 12870 0 0 kacpid
101 62 3737520 0 0 kblockd/0
102 82 3806840 0 0 kblockd/1
115 0 67290 0 0 khubd
191 0 5810 0 0 pdflush
192 983 4141020 0 0 pdflush
...

Use the show system resources command to display system-related CPU and memory statistics. The output includes the following:

• Load average—Number of running processes. The average reflects the system load over the past 1, 5, and 15 minutes.

• Processes—Number of processes in the system and how many processes are actually running when the command is issued.

• CPU states—CPU usage percentage in user mode, kernel mode, and idle time in the last one second.

• Memory usage—Total memory, used memory, free memory, memory used for buffers, and memory used for the cache in KB. Buffers and cache are also included in the used memory statistics.

switch# show system resources
Load average: 1 minute: 0.30 5 minutes: 0.34 15 minutes: 0.28
Processes : 606 total, 2 running
CPU states : 0.0% user, 0.0% kernel, 100.0% idle
Memory usage: 2063268K total, 1725944K used, 337324K free
2420K buffers, 857644K cache

RADIUS is a protocol used for the exchange of attributes or credentials between a head-end RADIUS server and a client device. These attributes relate to three classes of services:

• Authentication: Authentication refers to the authentication of users for access to a specific device. You can use RADIUS to manage user accounts for access to Cisco Nexus 1000V. When you try to log into a device, Cisco Nexus 1000V validates you with information from a central RADIUS server.

• Authorization: Authorization refers to the scope of access that you have once you have been authenticated. Assigned roles for users can be stored in a RADIUS server with a list of actual devices that the user should have access to. Once the user has been authenticated, the switch can then refer to the RADIUS server to determine the extent of access the user will have within the switch network.

• Accounting: Accounting refers to the log information that is kept for each management session in a switch. This information can be used to generate reports for troubleshooting purposes and user accountability. Accounting can be implemented locally or remotely (using RADIUS).

  Note	The accounting log shows only the beginning and ending (start and stop) for each session.

  The following is an example of an accounting log entries:

  switch# show accounting log
  Sun Dec 15 04:02:27 2002:start:/dev/pts/0_1039924947:admin
  Sun Dec 15 04:02:28 2002:stop:/dev/pts/0_1039924947:admin:vsh exited normally
  Sun Dec 15 04:02:33 2002:start:/dev/pts/0_1039924953:admin
  Sun Dec 15 04:02:34 2002:stop:/dev/pts/0_1039924953:admin:vsh exited normally
  Sun Dec 15 05:02:08 2002:start:snmp_1039928528_172.22.95.167:public
  Sun Dec 15 05:02:08 2002:update:snmp_1039928528_172.22.95.167:public:Switchname

The system message logging software saves messages in a log file or directs the messages to other devices. This feature provides the following capabilities:

• Logging information for monitoring and troubleshooting.

• Selection of the types of logging information to be captured.

• Selection of the destination of the captured logging information.

Syslog allows you to store a chronological log of system messages locally or sent to a central syslog server. Syslog messages can also be sent to the console for immediate use. These messages can vary in detail depending on the configuration that you choose.

Syslog messages are categorized into seven severity levels from debug to critical events. You can limit the severity levels that are reported for specific services within the switch.

Log messages are not saved across system reboots. However, a maximum of 100 log messages with a severity level of critical and below (levels 0, 1, and 2) can logged to a local file or server.