Cisco MDS SanOS Troubleshooting Guide -- Before Contacting Technical Support - Revision history

Pravraj: /* Copying Files Using the CLI */

2010-11-08T09:16:38Z

Copying Files Using the CLI

← Older revision		Revision as of 09:16, 8 November 2010
Line 156:		Line 156:
	</pre>		</pre>

-	To back up the startup-configuration to a ~~sftp~~ server, use the following command:	+	To back up the startup-configuration to a SFTP server, use the following command:

	<pre>		<pre>

Pravraj at 09:13, 8 November 2010

2010-11-08T09:13:05Z

← Older revision		Revision as of 09:13, 8 November 2010
Line 1:		Line 1:
	{{Template:Required Metadata}}		{{Template:Required Metadata}}
-	This section introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using the Cisco MDS 9000 Family of multilayer directors and fabric switches. This section discusses ~~about~~ the steps to be taken before contacting TAC.	+	This section introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using the Cisco MDS 9000 Family of multilayer directors and fabric switches. This section discusses the steps to be taken before contacting TAC.

	__TOC__		__TOC__
Line 26:		Line 26:
	: a. Select <span style="font-style: normal">'''<font color="Black">Tools > Show Tech Support</font>'''</span> in Fabric Manager. Fabric Manager can capture switch configuration information from multiple switches simultaneously. The file can be saved on the local PC.		: a. Select <span style="font-style: normal">'''<font color="Black">Tools > Show Tech Support</font>'''</span> in Fabric Manager. Fabric Manager can capture switch configuration information from multiple switches simultaneously. The file can be saved on the local PC.
	: b. Configure your Telnet or SSH application to log the screen output to a text file. Use the <span style="font-style: normal">'''<font color="Black">terminal length 0</font>'''</span> CLI command and then use the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command.		: b. Configure your Telnet or SSH application to log the screen output to a text file. Use the <span style="font-style: normal">'''<font color="Black">terminal length 0</font>'''</span> CLI command and then use the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command.
-	: c. Use the <span style="font-style: normal"><font color="Black">'''tac-pac''' ~~<~~''filename''~~&gt~~; </font></span>CLI command to redirect the output of the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command<span style="font-style: normal">'''<font color="Black"> </font>'''</span>to a file, and then gzip the file.	+	: c. Use the <span style="font-style: normal"><font color="Black">'''tac-pac''' ''filename''; </font></span>CLI command to redirect the output of the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command<span style="font-style: normal">'''<font color="Black"> </font>'''</span>to a file, and then gzip the file.

	<pre>		<pre>

Pravraj at 11:38, 28 September 2010

2010-09-28T11:38:58Z

← Older revision		Revision as of 11:38, 28 September 2010
Line 1:		Line 1:
	{{Template:Required Metadata}}		{{Template:Required Metadata}}
-	This section introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using the Cisco MDS 9000 Family of multilayer directors and fabric switches.	+	This section introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using the Cisco MDS 9000 Family of multilayer directors and fabric switches. This section discusses about the steps to be taken before contacting TAC.

	__TOC__		__TOC__
Line 15:		Line 15:

	== Steps to Perform Before Calling TAC ==		== Steps to Perform Before Calling TAC ==
-	At some point, you may need to contact your customer support representative or Cisco TAC for some additional assistance. This section outlines the steps that ~~the~~ you should perform prior to contacting your next level of support, ~~as this will~~ reduce the amount of time spent resolving the issue.	+	At some point, you may need to contact your customer support representative or Cisco TAC for some additional assistance. This section outlines the steps that you should perform prior to contacting your next level of support, because you can reduce the amount of time spent resolving the issue.

	----		----
-	{{Note \|Do not reload the module or the switch at least until you have completed Step 1 ~~below~~. Some logs and counters are kept in volatile storage and will not survive a reload.}}	+	{{Note \|Do not reload the module or the switch at least until you have completed Step 1. Some logs and counters are kept in volatile storage and will not survive a reload.}}
	----		----

Line 26:		Line 26:
	: a. Select <span style="font-style: normal">'''<font color="Black">Tools > Show Tech Support</font>'''</span> in Fabric Manager. Fabric Manager can capture switch configuration information from multiple switches simultaneously. The file can be saved on the local PC.		: a. Select <span style="font-style: normal">'''<font color="Black">Tools > Show Tech Support</font>'''</span> in Fabric Manager. Fabric Manager can capture switch configuration information from multiple switches simultaneously. The file can be saved on the local PC.
	: b. Configure your Telnet or SSH application to log the screen output to a text file. Use the <span style="font-style: normal">'''<font color="Black">terminal length 0</font>'''</span> CLI command and then use the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command.		: b. Configure your Telnet or SSH application to log the screen output to a text file. Use the <span style="font-style: normal">'''<font color="Black">terminal length 0</font>'''</span> CLI command and then use the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command.
-	: c. Use the <span style="font-style: normal">~~'''~~<font color="Black">tac-pac <filename> </font>~~'''~~</span>CLI command to redirect the output of the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command<span style="font-style: normal">'''<font color="Black"> </font>'''</span>to a file, and then gzip the file.	+	: c. Use the <span style="font-style: normal"><font color="Black">'''tac-pac''' <''filename''> </font></span>CLI command to redirect the output of the <span style="font-style: normal">'''<font color="Black">show tech-support details </font>'''</span>CLI command<span style="font-style: normal">'''<font color="Black"> </font>'''</span>to a file, and then gzip the file.

	<pre>		<pre>
Line 37:		Line 37:

	3. Capture the exact error codes you see in the message logs from either Fabric Manager or the CLI.		3. Capture the exact error codes you see in the message logs from either Fabric Manager or the CLI.
-	: a. ~~Select~~ the <span style="font-style: normal">'''<font color="Black">Logs</font>'''</span> tab in the Map pane in Fabric Manager or choose <span style="font-style: normal">'''<font color="Black">Switches > Events</font>'''</span> to see the recent list of messages generated.	+	: a. Click the <span style="font-style: normal">'''<font color="Black">Logs</font>'''</span> tab in the Map pane in Fabric Manager or choose <span style="font-style: normal">'''<font color="Black">Switches > Events</font>'''</span> to see the recent list of messages generated.
-	: b. Copy the error from the message log, which can be displayed using either the <span style="font-style: normal">'''<font color="Black">show logging log </font>'''</span>CLI command<span style="font-style: normal">'''<font color="Black"> </font>'''</span>or the <span style="font-style: normal">'''<font color="Black">show logging last </font>'''</span><span style="font-weight: normal">''<font color="Black">number</font>''</span> to view the last lines of the log.	+	: b. Copy the error from the message log, which can be displayed using either the <span style="font-style: normal">'''<font color="Black">show logging log </font>'''</span>CLI command<span style="font-style: normal">'''<font color="Black"> </font>'''</span>or the <span style="font-style: normal">'''<font color="Black">show logging last </font>'''</span><span style="font-weight: normal">''<font color="Black">number</font>''</span> command to view the last lines of the log.

	4. Answer the following questions before calling for technical support:		4. Answer the following questions before calling for technical support:
Line 63:		Line 63:
	* What is the new Cisco SAN-OS version?		* What is the new Cisco SAN-OS version?
	* Did you use Fabric Manager or the CLI to attempt this upgrade?		* Did you use Fabric Manager or the CLI to attempt this upgrade?
-	* ~~Please collect~~ the output from the following commands ~~and forward them to your customer support representative~~:	+	* Collect the output from the following commands:
-	** show install all status	+	** '''show install all status'''
-	** show system internal log install	+	** '''show system internal log install'''
-	** show system internal log install details	+	** '''show system internal log install details'''
-	** show log nvram	+	** '''show log nvram'''
-		+	* Forward them to your customer support representative.
	6. If your problem is related to zoning, use the <span style="font-style: normal">'''<font color="Black">show zone tech-support </font>'''</span>CLI command to gather relevant information.		6. If your problem is related to zoning, use the <span style="font-style: normal">'''<font color="Black">show zone tech-support </font>'''</span>CLI command to gather relevant information.

Line 102:		Line 102:
	2. Select <span style="font-style: normal">'''<font color="Black">Copy</font>'''</span> to copy a file. You see the copy file dialog box.		2. Select <span style="font-style: normal">'''<font color="Black">Copy</font>'''</span> to copy a file. You see the copy file dialog box.

-	3. ~~select~~ the protocol you want to use to copy the file to the switch.	+	3. Select the protocol that you want to use to copy the file to the switch.

	4. Set the server address and the file that you want to copy.		4. Set the server address and the file that you want to copy.
Line 170:		Line 170:
	----		----
	'''Tip'''<br>		'''Tip'''<br>
-	Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save and then backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename.	+	Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save, and then a backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename.
	----		----

	== Using Core Dumps ==		== Using Core Dumps ==

-	Core dumps are available in situations where unknown problems exist. Dumps are sent to a TFTP server or to a ~~Flash~~ card in slot0: of the local switch. You should set up your switch to generate core dumps under the instruction of your customer support representative. Core dumps are decoded by technical support engineers.	+	Core dumps are available in situations where unknown problems exist. Dumps are sent to a TFTP server or to a flash card in slot0: of the local switch. You should set up your switch to generate core dumps under the instruction of your customer support representative. Core dumps are decoded by technical support engineers.

-	Best practice is to set up cores dumps to go to a TFTP server,. ~~Then these~~ core dumps can be e-mailed directly to your customer support representative.	+	Best practice is to set up cores dumps to go to a TFTP server. These core dumps can be e-mailed directly to your customer support representative.

	=== Setting Up Core Dumps Using the CLI ===		=== Setting Up Core Dumps Using the CLI ===
Line 189:		Line 189:
	</pre>		</pre>
	----		----
-	{{Note \| The ~~file name~~ (indicated by jsmith_cores) must exist in the TFTP server directory.}}	+	{{Note \| The filename (indicated by jsmith_cores) must exist in the TFTP server directory.}}
	----		----

Gkanmas: /* Copying Files Using the CLI */

2010-07-23T08:03:38Z

Copying Files Using the CLI

← Older revision		Revision as of 08:03, 23 July 2010
Line 169:		Line 169:

	----		----
-	{{ Tip \| Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save and then backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename. }}	+	'''Tip'''<br>
		+	Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save and then backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename.
	----		----

Gkanmas: /* Copying Files Using the CLI */

2010-07-23T08:03:05Z

Copying Files Using the CLI

← Older revision		Revision as of 08:03, 23 July 2010
Line 169:		Line 169:

	----		----
-	{{Tip \| Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save and then backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename. }}	+	{{ Tip \| Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save and then backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename. }}
	----		----

Gkanmas: /* Before Contacting Technical Support */

2010-07-23T08:02:28Z

Before Contacting Technical Support

← Older revision		Revision as of 08:02, 23 July 2010
Line 11:		Line 11:
	* Using Core Dumps		* Using Core Dumps
	----		----
-	{ Note \| If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco, contact Cisco Technical Support at this URL: [http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml http://www.cisco.com/warp/public/687/Directory/DirTAC.shtm}}	+	{{ Note \| If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco, contact Cisco Technical Support at this URL: [http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml http://www.cisco.com/warp/public/687/Directory/DirTAC.shtm}}
	----		----

Gkanmas at 08:02, 23 July 2010

2010-07-23T08:02:14Z

← Older revision		Revision as of 08:02, 23 July 2010
Line 1:		Line 1:
		+	{{Template:Required Metadata}}
		+	This section introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using the Cisco MDS 9000 Family of multilayer directors and fabric switches.
		+
		+	__TOC__
		+
		+	<br>
	== Before Contacting Technical Support ==		== Before Contacting Technical Support ==

Line 184:		Line 190:
	{{Note \| The file name (indicated by jsmith_cores) must exist in the TFTP server directory.}}		{{Note \| The file name (indicated by jsmith_cores) must exist in the TFTP server directory.}}
	----		----
		+
		+
		+
		+	--------------------------------------------------------------------------------
		+	<center>'''Back to Main Page''': [[Cisco MDS SAN-OS Troubleshooting Guide]]
		+	--------------------------------------------------------------------------------

Gkanmas: New page: == Before Contacting Technical Support == This appendix describes the steps to perform before calling for technical support for any Cisco MDS 9000 Family multilayer director and fabric sw...

2010-07-23T07:59:46Z

New page: == Before Contacting Technical Support == This appendix describes the steps to perform before calling for technical support for any Cisco MDS 9000 Family multilayer director and fabric sw...

New page

== Before Contacting Technical Support ==

This appendix describes the steps to perform before calling for technical support for any Cisco MDS 9000 Family multilayer director and fabric switch. This appendix includes the following sections:
* Steps to Perform Before Calling TAC
* Using Core Dumps
----
{ Note | If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco, contact Cisco Technical Support at this URL: [http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml http://www.cisco.com/warp/public/687/Directory/DirTAC.shtm}}
----

== Steps to Perform Before Calling TAC ==
At some point, you may need to contact your customer support representative or Cisco TAC for some additional assistance. This section outlines the steps that the you should perform prior to contacting your next level of support, as this will reduce the amount of time spent resolving the issue.

----
{{Note |Do not reload the module or the switch at least until you have completed Step 1 below. Some logs and counters are kept in volatile storage and will not survive a reload.}}
----

To prepare for contacting your customer support representative, follow these steps:
----
1. Collect switch information and configuration. This should be done before and after the issue has been resolved. The following three methods each provide the same information:
: a. Select '''Tools > Show Tech Support''' in Fabric Manager. Fabric Manager can capture switch configuration information from multiple switches simultaneously. The file can be saved on the local PC.
: b. 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.
: c. Use the '''tac-pac <filename> '''CLI command to redirect the output of the '''show tech-support details '''CLI command''' '''to a file, and then gzip the file.

<pre>
<nowiki>switch# tac-pac bootflash://showtech.switch1 <nowiki>
</pre>

If no filename is specified, the file is created as volatile:show_tech_out.gz. The file should then be copied from the switch using the procedure outlined in the "Copying Files to or from the Switch" section.

2. If an error occurs in Fabric Manager, take a screen shot of the error. In Windows, press '''Alt PrintScreen '''to capture the active window, or press only '''PrintScreen '''to capture the entire desktop. Then paste this into a new '''Microsoft Paint '''(or similar program) session and save the file.

3. Capture the exact error codes you see in the message logs from either Fabric Manager or the CLI.
: a. Select the '''Logs''' tab in the Map pane in Fabric Manager or choose '''Switches > Events''' to see the recent list of messages generated.
: b. Copy the error from the message log, which can be displayed using either the '''show logging log '''CLI command''' '''or the '''show logging last '''''number'' to view the last lines of the log.

4. Answer the following questions before calling for technical support:

* On which switch, host bus adapter (HBA), or storage port is the problem occurring?
* Which Cisco SAN-OS software, driver versions, operating systems versions and storage device firmware are in your fabric?
* What is the network topology? (In Fabric Manager, go to '''Tools > Show Tech Support''' and check the '''Save Map''' check box.)
* Were any changes being made to the environment (zoning, 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 MDS 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?
** FC Analyzer, PAA-2, Ethereal, local or remote SPAN
** CLI debug commands
** FC traceroute, FC ping
** Fabric Manager or Device Manager tools

5. Is your problem related to a software upgrade attempt?

* What was the original Cisco SAN-OS version?
* What is the new Cisco SAN-OS version?
* Did you use Fabric Manager or the CLI to attempt this upgrade?
* Please collect the output from the following commands and forward them to your customer support representative:
** show install all status
** show system internal log install
** show system internal log install details
** show log nvram

6. If your problem is related to zoning, use the '''show zone tech-support '''CLI command to gather relevant information.

----

=== Copying Files to or from the Switch ===

It may be required to move files to or from the switch. These files may include log, configuration, or firmware files.

=== Copying Files Using Device Manager ===

To copy the configuration from the switch using Device Manager, follow these steps:

----
1. Choose''' Admin > Copy Configuration'''. You see the Copy Configuration dialog box.

2. Set the To field to the server where you want to copy the configuration file to.

3. Set the From field to running or startup configuration.

4. Select the protocol you want to use to copy the file from the switch.

4. Select '''Apply''' to copy the file.

----

To copy files to the switch using Device Manager, follow these steps:

----

1. Choose''' Admin > Flash Files'''. You see the list of files in the chosen device and partition.

2. Select '''Copy''' to copy a file. You see the copy file dialog box.

3. select the protocol you want to use to copy the file to the switch.

4. Set the server address and the file that you want to copy.

5. Select '''Apply''' to copy the file.

----

=== Copying Files Using the CLI ===

The CLI offers a broad range of protocols to use for copying to or from the switch. Note that the switch always acts as a client, such that an ftp/scp/tftp session will always originate from the switch and either push files to an external system or pull files from an external system.

<pre>
File Server: 172.22.36.10

File to be copied to the switch: /etc/hosts
</pre>

The '''copy''' CLI command supports four transfer protocols and 12 different sources for files.
<pre>
ca-9506# copy ?
bootflash: Select source filesystem
core: Select source filesystem
debug: Select source filesystem
ftp: Select source filesystem
licenses Backup license files
log: Select source filesystem
modflash: Select source filesystem
nvram: Select source filesystem
running-config Copy running configuration to destination
scp: Select source filesystem
sftp: Select source filesystem
slot0: Select source filesystem
startup-config Copy startup configuration to destination
system: Select source filesystem
tftp: Select source filesystem
volatile: Select source filesystem

</pre>

Use the following syntax to use secure copy (scp) as the transfer mechanism:

<pre>
"scp:[//[username@]server][/path]"
</pre>

To copy /etc/hosts from 172.22.36.10 using the user user1, where the destination would be hosts.txt, use the following command:

<pre>
switch# copy scp://user1@172.22.36.10/etc/hosts bootflash:hosts.txt
user1@172.22.36.10's password:
hosts 100% |*****************************| 2035 00:00
</pre>

To back up the startup-configuration to a sftp server, use the following command:

<pre>
switch# copy startup-config sftp://user1@172.22.36.10/MDS/startup-configuration.bak1

Connecting to 172.22.36.10...
User1@172.22.36.10's password:

switch#

</pre>

----
{{Tip | Backing up the startup-configuration to a server should be done on a daily basis and prior to any changes. A short script could be written to be run on the MDS to perform a save and then backup of the configuration. The script only needs to contain two commands: '''copy running-configuration startup-configuration''' and then '''copy startup-configuration tftp://server/name.''' To execute the script use: run-script filename. }}
----

== Using Core Dumps ==

Core dumps are available in situations where unknown problems exist. Dumps are sent to a TFTP server or to a Flash card in slot0: of the local switch. You should set up your switch to generate core dumps under the instruction of your customer support representative. Core dumps are decoded by technical support engineers.

Best practice is to set up cores dumps to go to a TFTP server,. Then these core dumps can be e-mailed directly to your customer support representative.

=== Setting Up Core Dumps Using the CLI ===

Use the '''system cores''' CLI command to set up core dumps on your switch.

<pre>
switch# system cores tftp://10.91.51.200/jsmith_cores
switch# show system cores
Cores are transferred to tftp://10.91.51.200/jsmith_cores
</pre>
----
{{Note | The file name (indicated by jsmith_cores) must exist in the TFTP server directory.}}
----