Obtaining A File Of Core Memory Information - Cisco Nexus 1000V Troubleshooting Manual

Hide thumbs Also See for Nexus 1000V:
Table of Contents

Advertisement

Obtaining a File of Core Memory Information

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 .
Collect switch information and configuration. This should be done before and after the issue has been
Step 1
resolved.
Configure your Telnet or SSH application to log the screen output to a text file. Use the terminal length
0 CLI command and then use the show tech-support details CLI command.
Capture the exact error codes you see in CLI message logs using one of the following commands.
Step 2
Answer the following questions before calling for technical support:
Step 3
Step 4
Is your problem related to a software upgrade attempt?
Obtaining a File of Core Memory Information
Cisco customer support engineers often use files from your system for analysis. One of these is a file
containing memory information, and is referred to as a core dump. The file is sent to a TFTP server or
to a Flash card in slot0: of the local switch. You should set up your switch to generate this file under the
instruction of your customer support representative, and send it to a TFTP server so that it can be
e-mailed to them.
To generate a file of core memory information, or a core dump, use the command in the following
example.
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
27-2
show logging log CLI (displays the error messages)
show logging last number (displays the last lines of the log)
On which switch or port is the problem occurring?
Cisco Nexus 1000V software, driver versions, operating systems versions and storage device
firmware are in your fabric?
ESX and vCenter Server software that you are running?
What is the network topology?
Were any changes being made to the environment (VLANs, adding modules, upgrades) prior to or
at the time of this event?
Are there other similarly configured devices that could have this problem, but do not?
Where was this problematic device connected (which switch and interface)?
When did this problem first occur?
When did this problem last occur?
How often does this problem occur?
How many devices have this problem?
Were any traces or debug output captured during the problem time? What troubleshooting steps have
you attempted? Which, if any, of the following tools were used?
Ethanalyzer, local or remote SPAN
CLI debug commands
traceroute, ping
What was the original Cisco Nexus 1000V version?
What is the new Cisco Nexus 1000V version?
Chapter 27
Before Contacting Technical Support
OL-28795-01

Advertisement

Table of Contents
loading

Table of Contents