Overview Of Symptoms; System Messages; System Message Text - Cisco Nexus 1000V Troubleshooting Manual

Overview of Symptoms

• Are any IP access lists, filters, or route maps blocking route updates?
Use the ping or trace commands to verify connectivity. See the following for more information:
• Ping, page 2-1
Traceroute, page 2-2
•
Overview of Symptoms
The symptom-based troubleshooting approach provides multiple ways to diagnose and resolve
problems. By using multiple entry points with links to solutions, this guide best serves users who may
have identical problems that are perceived by different indicators. Search this guide in PDF form, use
the index, or rely on the symptoms and diagnostics listed in each chapter as entry points to access
necessary information in an efficient manner.
Using a given a set of observable symptoms on a network, it is important to 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 Nexus 1000V 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.
Obtain core dumps and other diagnostic data for use by the Technical Assistance Center (TAC).
•
Recover from switch upgrade failures.
•

System Messages

The system software sends the syslog (system) messages to the console (and, optionally, to a logging
server on another system) during operation. Not all messages indicate a problem with your system. Some
messages are purely informational, while others might help diagnose problems with links, internal
hardware, or the system software.
This section contains the following topics:
• System Message Text, page 1-4
syslog Server Implementation, page 1-5
•

System Message Text

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].
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
1-4
Chapter 1 Overview
OL-31593-01