The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the troubleshooting tools available for the Cisco Nexus 1000VE and includes the following topics:
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:
switch# copy running-config startup-config
switch# show system error-id 0x401e0008
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. 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.
Use traceroute to do the following:
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.
There CLI enables you to for monitor switch processes. CPU status, and utilization.
This section contains the following topics:
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:
Process states are as follows:
Note The ER state typically designates a process that has been restarted too many times, causing the system to classify it as faulty and disable it.
Example 2-1 show processes Command
switch# show processes ?
switch# show processes
Use the show processes cpu command to display CPU utilization. See Example 2-2. The command output includes the following:
Example 2-2 show processes cpu Command
switch# show processes cpu
Use the show system resources command to display system-related CPU and memory statistics. See Example 2-3. The output includes the following:
Example 2-3 show system resources Command
switch# show system resources
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 refers to the authentication of users for access to a specific device. You can use RADIUS to manage user accounts for access to a Cisco Nexus 1000VE. When you try to log into a device, the Cisco Nexus 1000VE validates you with information from a central RADIUS server.
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 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).
The following is an example of an accounting log entries:
switch# show accounting log
Note The accounting log shows only the beginning and ending (start and stop) for each session.
The system message logging software saves messages in a log file or directs the messages to other devices. This feature provides the following capabilities:
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.
The Cisco Nexus 1000VE supports the following logging levels:
By default, the switch logs normal but significant system messages to a log file and sends these messages to the system console. Users can specify which system messages should be saved based on the type of facility and the severity level. Messages are time-stamped to enhance real-time debugging and management.
System logging messages are sent to the console based on the default or configured logging facility and severity values.
Users can disable logging to the console or enable logging to a given Telnet or SSH session.
Note Note: When logging to a console session is disabled or enabled, that state is applied to all future console sessions. If a user exits and logs in again to a new session, the state is preserved. However, when logging to a Telnet or SSH session is enabled or disabled, that state is applied only to that session. The state is not preserved after the user exits the session.
The no logging console command shown in Example 2-4 does the following:
Example 2-4 no logging console Command
switch(config)# no logging console
The terminal monitor command shown in Example 2-5 does the following:
Example 2-5 terminal monitor Command
switch# terminal monitor
For more information about configuring syslog, see the Cisco Nexus 1000VE System Management Configuration Guide.