Troubleshooting Basics - Cisco Nexus 1000V Troubleshooting Manual
Hide thumbs
Also See for Nexus 1000V:
- Troubleshooting manual (280 pages) ,
- Configuration manual (96 pages) ,
- Deployment manual (49 pages)
Table of Contents
Advertisement
Troubleshooting Basics
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
•
•
Troubleshooting Basics
This section introduces questions to ask when troubleshooting a problem with Cisco Nexus 1000V or
connected devices. Use the answers to these questions to identify the scope of the problem and to plan
a course of action.
This section includes the following topics:
•
•
•
•
•
Troubleshooting Guidelines
By answering the questions in the following subsections, you can determine the paths you need to follow
and the components that you should investigate further.
Answer the following questions to determine the status of your installation:
•
•
•
•
To discover a network problem, use the following general network troubleshooting steps:
Step 1
Gather information on problems in your system. See the
Step 2
Verify the layer 2 connectivity. See the
Step 3
Verify the configuration for your end devices (storage subsystems and servers).
Verify end-to-end connectivity. See the
Step 4
Gathering Information
This section highlights the tools that are commonly used to troubleshoot problems within your network.
These tools are a subset of what you may use to troubleshoot your specific problem.
Each chapter in this guide may include additional tools and commands specific to the symptoms and
possible problems covered in that chapter.
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
1-2
Enable system message logging. See the
Verify and troubleshoot any new configuration changes after implementing the change.
Troubleshooting Guidelines, page 1-2
Gathering Information, page 1-2
Verifying Ports, page 1-3
Verifying Layer 2 Connectivity, page 1-3
Verifying Layer 3 Connectivity, page 1-3
Is this a newly installed system or an existing installation? (It could be a new host, switch, or
VLAN).
Has the host ever been able to see the network?
Are you trying to solve an existing application problem (too slow, too high latency, excessively long
response time) or did the problem show up recently?
What changed in the configuration or in the overall infrastructure immediately before the
applications started to have problems?
"Overview of Symptoms" section on page
"Gathering Information" section on page
"Verifying Layer 2 Connectivity" section on page
"Verifying Layer 3 Connectivity" section on page
Chapter 1
Overview of Troubleshooting
1-4.
1-3.\
1-3.
OL-25387-01
1-2.
Advertisement
Table of Contents
Troubleshooting
