Cisco Nexus 9000 Series User manual

Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
First Published: 2015-02-01
Last Modified: 2015-12-14
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright ©1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
This product includes cryptographic software written by Eric Young ([email protected]).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
This product includes software written by Tim Hudson ([email protected]).
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
©2015-2016 Cisco Systems, Inc. All rights reserved.

CONTENTS
Preface Preface ix
Audience ix
Document Conventions ix
Related Documentation for Cisco Nexus 9000 Series Switches x
Documentation Feedback x
Obtaining Documentation and Submitting a Service Request xi
CHAPTER 1 New and Changed Information 1
New and Changed Information 1
CHAPTER 2 Overview 3
Software Image 3
About the Troubleshooting Process 3
Verifying Ports 4
Verifying Layer 2 Connectivity 4
Verifying Layer 3 Connectivity 5
Symptoms 5
System Messages 6
Syslog Server Implementation 6
Troubleshooting with Logs 8
Troubleshooting Modules 8
Viewing NVRAM Logs 8
Contacting Customer Support 9
CHAPTER 3 Troubleshooting Installations, Upgrades, and Reboots 11
About Upgrades and Reboots 11
Upgrade and Reboot Checklist 11
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
iii

Verifying Software Upgrades 12
Verifying a Nondisruptive Upgrade 12
Troubleshooting Software Upgrades and Downgrades 13
Software Upgrade Ends with Error 13
Upgrading the Cisco NX-OS Software 13
Troubleshooting Software System Reboots 14
Power-On or Switch Reboot Hangs 14
Corrupted Bootflash Recovery 15
Recovery from the loader> Prompt 16
System or Process Restarts 18
Recovering System Restarts 19
Unrecoverable System Restarts 23
Standby Supervisor Fails to Boot 24
Recovering the Administrator Password 24
Using the CLI with Network-Admin Privileges to Recover the Administrator
Password 25
Power Cycling the Device to Recover the Administrator Password 25
Reloading the Device to Recover the Administrator Password 30
CHAPTER 4 Troubleshooting Licensing Issues 33
About Troubleshooting Licensing Issues 33
Guidelines and Limitations for Licensing 33
Initial Troubleshooting Checklist for Licensing 34
Displaying License Information Using the CLI 34
Licensing Installation Issues 35
Serial Number Issues 35
RMA Chassis Errors or License Transfers Between Systems 36
License Listed as Missing 36
CHAPTER 5 Troubleshooting Ports 37
About Troubleshooting Ports 37
Guidelines and Limitations for Troubleshooting Ports 37
Initial Port Troubleshooting Checklist 38
Viewing Port Information 38
Troubleshooting Port Statistics from the CLI 39
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
iv
Contents

Troubleshooting Port-Interface Issues 39
The Interface Configuration Has Disappeared 39
You Cannot Enable an Interface 40
You Cannot Configure a Dedicated Port 40
A Port Remains in a Link Failure or Not Connected State 41
An Unexpected Link Flapping Occurs 41
A Port Is in the ErrDisabled State 42
Verifying the ErrDisable State Using the CLI 43
CHAPTER 6 Troubleshooting vPCs 45
About Troubleshooting vPCs 45
Initial Troubleshooting vPCs Checklist 45
Verifying vPCs Using the CLI 46
Received Type 1 Configuration Element Mismatch 47
Cannot Enable the vPC Feature 48
vPCs in Blocking State 48
VLANs on a vPC Moved to Suspend State 48
Hosts with an HSRP Gateway Cannot Access Beyond Their VLAN 49
CHAPTER 7 Troubleshooting VLANs 51
About Troubleshooting VLANs 51
Guidelines and Limitations for Troubleshooting VLANs 51
Initial Troubleshooting VLANs Checklist 52
Troubleshooting VLAN Issues 53
You Cannot Create a VLAN 53
You Cannot Create a PVLAN 53
The VLAN Interface is Down 53
CHAPTER 8 Troubleshooting STP 55
About Troubleshooting STP 55
Initial Troubleshooting STP Checklist 55
Troubleshooting STP Data Loops 56
Troubleshooting Excessive Packet Flooding 59
Troubleshooting Convergence Time Issues 60
Securing the Network Against Forwarding Loops 60
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
v
Contents

CHAPTER 9 Troubleshooting Routing 63
About Troubleshooting Routing Issues 63
Initial Troubleshooting Routing Checklist 63
Troubleshooting Routing 64
Troubleshooting Policy-Based Routing 67
CHAPTER 10 Troubleshooting Memory 69
About Troubleshooting Memory 69
General/High Level Assessment of Platform Memory Utilization 70
User Processes 70
Determining Which Process Is Using a Lot of Memory 71
Built-in Platform Memory Monitoring 71
Memory Thresholds 71
CHAPTER 11 Troubleshooting Packet Flow Issues 73
Packet Flow Issues 73
Packets Dropped Because of Rate Limits 73
Packets Dropped Because of CoPP 73
CHAPTER 12 Troubleshooting PowerOn Auto Provisioning 75
Switch Does Not Come Up in Time for POAP to Complete 75
POAP Fails 75
CHAPTER 13 Troubleshooting the Python API 77
Receiving Python API Errors 77
CHAPTER 14 Troubleshooting NX-API 81
NX-API Guidelines 81
NX-API Is Not Responding 81
Configuration Fails 82
Permission Is Denied for Bash 82
Output Cannot Be Retrieved from the Browser Sandbox 82
CLI Command Errors Are Appearing 82
Error Messages Are Appearing 82
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
vi
Contents

Temporary Files Are Disappearing 83
Chunks of the Command Output Are Not Being Delivered 83
CHAPTER 15 Troubleshooting Service Failures 85
Identifying Memory Allocations for Processes 85
Identifying CPU Utilization for Processes 86
Monitoring Process Core Files 87
Processing the Crash Core Files 87
Clearing the Core 87
Enabling Auto-Copy for Core Files 88
CHAPTER 16 Before Contacting Technical Support 89
Steps to Perform Before Calling TAC 89
Copying Files to or from Cisco NX-OS 91
Using Core Dumps 92
CHAPTER 17 Troubleshooting Tools and Methodology 93
Command-Line Interface Troubleshooting Commands 93
Consistency Checker Commands 94
Configuration Files 95
CLI Debug 95
Debug Filters 96
Ping and Traceroute 96
Using Ping 96
Using Traceroute 97
Monitoring Processes and CPUs 98
Using the show processes cpu Command 99
Using the show system resources Command 100
Using Onboard Failure Logging 100
Using Diagnostics 101
Using Embedded Event Manager 102
Using Ethanalyzer 102
SNMP and RMON Support 104
Using the PCAP SNMP Parser 104
Using RADIUS 106
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
vii
Contents

Using syslog 106
Logging Levels 107
Enabling Logging for Telnet or SSH 107
Using SPAN 108
Using the Blue Beacon Feature 108
Using the watch Command 108
Additional References for Troubleshooting Tools and Methodology 109
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
viii
Contents

Preface
This preface includes the following sections:
•Audience, page ix
•Document Conventions, page ix
•Related Documentation for Cisco Nexus 9000 Series Switches, page x
•Documentation Feedback, page x
•Obtaining Documentation and Submitting a Service Request, page xi
Audience
This publication is for network administrators who install, configure, and maintain Cisco Nexus switches.
Document Conventions
Command descriptions use the following conventions:
DescriptionConvention
Bold text indicates the commands and keywords that you enter literally
as shown.
bold
Italic text indicates arguments for which the user supplies the values.
Italic
Square brackets enclose an optional element (keyword or argument).[x]
Square brackets enclosing keywords or arguments separated by a vertical
bar indicate an optional choice.
[x | y]
Braces enclosing keywords or arguments separated by a vertical bar
indicate a required choice.
{x | y}
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
ix

DescriptionConvention
Nested set of square brackets or braces indicate optional or required
choices within optional or required elements. Braces and a vertical bar
within square brackets indicate a required choice within an optional
element.
[x {y | z}]
Indicates a variable for which you supply values, in context where italics
cannot be used.
variable
A nonquoted set of characters. Do not use quotation marks around the
string or the string will include the quotation marks.
string
Examples use the following conventions:
DescriptionConvention
Terminal sessions and information the switch displays are in screen font.screen font
Information you must enter is in boldface screen font.boldface screen font
Arguments for which you supply values are in italic screen font.
italic screen font
Nonprinting characters, such as passwords, are in angle brackets.< >
Default responses to system prompts are in square brackets.[ ]
An exclamation point (!) or a pound sign (#) at the beginning of a line
of code indicates a comment line.
!, #
Related Documentation for Cisco Nexus 9000 Series Switches
The entire Cisco Nexus 9000 Series switch documentation set is available at the following URL:
http://www.cisco.com/en/US/products/ps13386/tsd_products_support_series_home.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
x
Preface
Related Documentation for Cisco Nexus 9000 Series Switches

Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service
request, and gathering additional information, see What's New in Cisco Product Documentation at: http://
www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical
documentation as an RSS feed and delivers content directly to your desktop using a reader application. The
RSS feeds are a free service.
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
xi
Preface
Obtaining Documentation and Submitting a Service Request

Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
xii
Preface
Obtaining Documentation and Submitting a Service Request

CHAPTER 1
New and Changed Information
This chapter provides release-specific information for each new and changed feature in the Cisco Nexus
9000 Series NX-OS Troubleshooting Guide, Release 7.x.
•New and Changed Information, page 1
New and Changed Information
This table summarizes the new and changed features for the Cisco Nexus 9000 Series NX-OS Troubleshooting
Guide, Release 7.x and tells you where they are documented.
Table 1: New and Changed Features for Cisco NX-OS Release 7.x
Where DocumentedChanged in
Release
DescriptionFeature
Copying Files to or from
Cisco NX-OS, on page 91
7.0(3)I2(1)Added support for the HTTPS
file system.
copy command
Troubleshooting Tools and
Methodology, on page 93
7.0(3)I2(1)Introduced this feature.PCAP SNMP parser
Troubleshooting Tools and
Methodology, on page 93
7.0(3)I2(1)Introduced this feature.watch command
Troubleshooting VLANs, on
page 51
7.0(3)I1(2)Introduced this feature.Private VLANs (PVLANs)
Troubleshooting Tools and
Methodology, on page 93
7.0(3)I1(2)Added source interface
support.
Traceroute
7.0(3)I1(1)Removed PVLAN support,
which is supported in Cisco
NX-OS Release 6.1(2)I3(4).
Private VLANs (PVLANs)
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
1

Where DocumentedChanged in
Release
DescriptionFeature
7.0(3)I1(1)Removed source interface
support, which is supported in
Cisco NX-OS Release
6.1(2)I3(3).
Traceroute
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
2
New and Changed Information
New and Changed Information

CHAPTER 2
Overview
This chapter contains the following sections:
•Software Image, page 3
•About the Troubleshooting Process, page 3
•Symptoms, page 5
•Troubleshooting with Logs, page 8
•Troubleshooting Modules, page 8
•Viewing NVRAM Logs, page 8
•Contacting Customer Support, page 9
Software Image
The Cisco NX-OS software consists of one NXOS software image (for example, n9000-dk9.6.1.2.I1.1.bin).
This image runs on all Cisco Nexus 9000 Series switches.
About the Troubleshooting Process
To troubleshoot your network, follow these general guidelines:
•Maintain a consistent Cisco NX-OS release across all your devices.
•See the Cisco NX-OS release notes for you Cisco NX-OS release for the latest features, limitations, and
caveats.
•Enable system message logging.
•Troubleshoot any new configuration changes after implementing the change.
•Gather information that defines the specific symptoms.
•Verify the physical connectivity between your device and end devices.
•Verify the Layer 2 connectivity.
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
3

•Verify the end-to-end connectivity and the routing configuration.
•After you have determined that your troubleshooting attempts have not resolved the problem, contact
Cisco TAC or your technical support representative.
This section describes the tools that are commonly used to troubleshoot problems within your network.
You should have an accurate topology of your network to isolate problem areas. Contact your network
architect for this information. Use the following commands to gather general information on your device:
Note
•show module
•show version
•show running-config
•show logging log
•show interfaces brief
•show vlan
•show spanning-tree
•show {ip |ipv6}routing
•show processes |include ER
•show accounting log
Verifying Ports
Answer the following questions to verify that your ports are connected correctly and are operational:
•Are you using the correct media (copper, optical, fiber type)?
•Is the media broken or damaged?
•Is the port LED green on the module?
•Is the interface operational?
See Troubleshooting Ports, on page 37 for more troubleshooting tips for ports.
Verifying Layer 2 Connectivity
Use the following commands to verify Layer 2 connectivity:
•Use the show vlan all-ports command to verify that all the necessary interfaces are in the same VLAN.
The status should be active for the VLAN.
•Use the show port-channel compatibility-parameters command to verify that all of the ports in a port
channel are configured the same for the speed, the duplex, and the trunk mode.
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
4
Overview
Verifying Ports

•Use the show running-config spanning-tree command to verify that the Spanning Tree Protocol (STP)
is configured the same on all devices in the network.
•Use the show processes |include ER command to verify that nonessential Layer 2 processes are in the
error state.
•Use the show mac address-table dynamic vlan command to determine if learning or aging is occurring
at each node.
Verifying Layer 3 Connectivity
Answer the following questions to verify Layer 3 connectivity:
•Have you configured a default gateway?
•Have you configured the same dynamic routing protocol parameters throughout your routing domain
or configured static routes?
•Are any IP access lists, filters, or route maps blocking route updates?
Use the following commands to verify your routing configuration:
•show ip arp
•show ip routing
See Troubleshooting Tools and Methodology, on page 93 to verify Layer 3 connectivity. See Troubleshooting
Routing, on page 63 for more information on troubleshooting Layer 3 issues.
Symptoms
This document uses a symptom-based troubleshooting approach that allows you to diagnose and resolve your
Cisco NX-OS problems by comparing the symptoms that you observed in your network with the symptoms
listed in each chapter.
By comparing the symptoms in this publication to the symptoms that you observe in your own network, you
should be able to diagnose and correct software configuration issues and inoperable hardware components so
that the problems are resolved with minimal disruption to the network. Those problems and corrective actions
include the following:
•Identify key Cisco NX-OS troubleshooting tools.
•Obtain and analyze protocol traces using SPAN or Ethanalyzer on the CLI.
•Identify or rule out physical port issues.
•Identify or rule out switch module issues.
•Diagnose and correct Layer 2 issues.
•Diagnose and correct Layer 3 issues.
•Recover from switch upgrade failures.
•Obtain core dumps and other diagnostic data for use by Cisco TAC or your customer support
representative.
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
5
Overview
Verifying Layer 3 Connectivity

System Messages
The system software sends syslog (system) messages to the console (and, optionally, to a logging server on
another device). Not all messages indicate a problem with your device. Some messages are purely informational,
while others might help diagnose problems with links, internal hardware, or the device software.
System message text is a text string that describes the condition. This portion of the message might contain
detailed information about the event, including terminal port numbers, network addresses, or addresses that
correspond to locations in the system memory address space. Because the information in these variable fields
changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A
decimal number, for example, is represented as [dec ].
PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not supported.
Each system message is followed by an explanation and recommended action. The action may be as simple
as "No action is required." It might involve a fix or a recommendation to contact technical support as shown
in the following example:
Error Message PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not
supported.
Explanation Transceiver (SFP) is not from an authorized vendor.
Recommended Action Enter the show interface transceiver CLI command or similar DCNM command to
determine the transceiver being used. Please contact your customer support representative for a list of authorized
transceiver vendors.
Syslog Server Implementation
The syslog facility allows the device to send a copy of the message log to a host for more permanent storage.
This feature allows you to examine the logs over a long period of time or if the device is not accessible.
This example shows how to configure the device to use the syslog facility on a Solaris platform. Although a
Solaris host is being used, the syslog configuration on all UNIX and Linux systems is very similar.
Syslog uses the facility to determine how to handle a message on the syslog server (the Solaris system in this
example) and the message severity. Different message severities are handled differently by the syslog server.
They could be logged to different files or e-mailed to a particular user. Specifying a severity level on the
syslog server determines that all messages of that level and greater severity (lower number) will be acted upon
as you configure the syslog server.
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
6
Overview
System Messages

You should configure the syslog server so that the Cisco NX-OS messages are logged to a different file
from the standard syslog file so that they cannot be confused with other non-Cisco syslog messages. Do
not locate the logfile on the / file system. You do not want log messages to fill up the / file system. This
example uses the following values:
Note
•syslog client: switch1
•syslog server: 172.22.36.211
•(Solaris) syslog facility: local1
•syslog severity: notifications (level 5, the default)
•File to log Cisco NX-OS messages to: /var/adm/nxos_logs
To configure the syslog feature on Cisco NX-OS, follow these steps:
1switch# config terminal
2switch(config)# logging server 192.0.2.1 6 facility local1
Use the show logging server command to verify the syslog configuration.
switch1# show logging server
Logging server: enabled
{172.22.36.211}
server severity: notifications
server facility: local1
server VRF: management
To configure a syslog server, follow these steps:
1Modify /etc/syslog.conf to handle local1 messages. For Solaris, you must allow at least one tab between
the facility.severity and the action (/var/adm/nxos_logs).
local1.notice /var/adm/nxos_logs
2Create the log file.
touch /var/adm/nxos_logs
3Restart the syslog process.
/etc/init.d/syslog stop
/etc/init.d/syslog start
syslog service starting.
4Verify that the syslog process has started.
ps -ef |grep syslogd
Test the syslog server by creating an event in Cisco NX-OS. In this case, port e1/2 was shut down and reenabled,
and the following was listed on the syslog server. The IP address of the device is listed in brackets.
tail -f /var/adm/MDS_logs
Sep 17 11:07:41 [172.22.36.142.2.2] : 2013 Sep 17 11:17:29 pacific:
PORT-5-IF_DOWN_INITIALIZING: %$VLAN 1%$ Interface e 1/2 is down (Initializing)
Sep 17 11:07:49 [172.22.36.142.2.2] : 2013 Sep 17 11:17:36 pacific: %PORT-5-IF_UP: %$VLAN
1%$ Interface e 1/2 is up in mode access
Sep 17 11:07:51 [172.22.36.142.2.2] : 2013 Sep 17 11:17:39 pacific:
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
7
Overview
Syslog Server Implementation

%VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from pts/0 (dhcp-171-71-49-125.cisco.com
Troubleshooting with Logs
Cisco NX-OS generates many types of system messages on the device and sends them to a syslog server. You
can view these messages to determine what events might have led up to the current condition that you are
facing.
Use the following commands to access and view logs in Cisco NX-OS:
switch# show logging ?
console Show console logging configuration
info Show logging configuration
ip IP configuration
last Show last few lines of logfile
level Show facility logging configuration
logfile Show contents of logfile
loopback Show logging loopback configuration
module Show module logging configuration
monitor Show monitor logging configuration
nvram Show NVRAM log
onboard show logging onboard
server Show server logging configuration
source-interface Show logging source-interface configuration
timestamp Show logging timestamp configuration
This example shows the output of the show logging server command:
switch# show logging server
Logging server: enabled
{172.28.254.254}
server severity: notifications
server facility: local7
server VRF: management
Troubleshooting Modules
You can directly connect to a module console port to troubleshoot module bootup issues. Use the attach
console module command to connect to the module console port.
Viewing NVRAM Logs
System messages that are priority 0, 1, or 2 are logged into NVRAM on the supervisor module. After a switch
reboots, you can display these syslog messages in NVRAM by using the show logging nvram command:
switch# show logging nvram
2013 Sep 10 15:51:58 switch %$ VDC-1 %$ %SYSMGR-2-NON_VOLATILE_DB_FULL: System n
on-volatile storage usage is unexpectedly high at 99%.
2013 Sep 10 15:52:13 switch %$ VDC-1 %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual sys
tem restart from Command Line Interface
2013 Sep 10 15:57:49 switch %$ VDC-1 %$ %KERN-2-SYSTEM_MSG: Starting kernel... -
kernel
2013 Sep 10 15:58:00 switch %$ VDC-1 %$ %CARDCLIENT-2-REG: Sent
2013 Sep 10 15:58:01 switch %$ VDC-1 %$ %USER-1-SYSTEM_MSG: R2D2: P1 SUP NO GMTL
FOR P1 SUP - r2d2
2013 Sep 10 15:58:01 switch %$ VDC-1 %$ %USER-1-SYSTEM_MSG: R2D2: P1 SUP NO GMTL
FOR P1 SUP - r2d2
2013 Sep 10 15:58:05 switch %$ VDC-1 %$ %USER-1-SYSTEM_MSG: R2D2: P1 SUP: Reset
Tx/Rx during QOS INIT - r2d2
Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 7.x
8
Overview
Troubleshooting with Logs