Cisco MDS SanOS Troubleshooting Guide -- Troubleshooting Ports - Revision history

Pravraj: /* Overview of Symptoms */

2010-11-08T08:02:13Z

Overview of Symptoms

← Older revision		Revision as of 08:02, 8 November 2010
Line 1,578:		Line 1,578:
	* Why does the storage device fail to complete FLOGI to the switch?		* Why does the storage device fail to complete FLOGI to the switch?

-	~~'''~~Figure 8-7~~'''~~ illustrates one possible method for troubleshooting Fx ports.	+	Figure 8-7 illustrates one possible method for troubleshooting Fx ports.

	'''Figure 8-7 Fx Port Troubleshooting Method'''		'''Figure 8-7 Fx Port Troubleshooting Method'''

Pravraj: /* Troubleshooting E Port Isolation Using the CLI */

2010-11-08T08:01:43Z

Troubleshooting E Port Isolation Using the CLI

← Older revision		Revision as of 08:01, 8 November 2010
Line 1,421:		Line 1,421:
	3. Use one of the following two approaches to resolve a zone merge failure:		3. Use one of the following two approaches to resolve a zone merge failure:
	* Overwrite the zoning configuration of one switch with the other switch's configuration. This can be done with the following commands:		* Overwrite the zoning configuration of one switch with the other switch's configuration. This can be done with the following commands:
-
	** '''zone copy interface fc'''<span style="font-weight: normal">''<font color="Black"> slot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">import vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>		** '''zone copy interface fc'''<span style="font-weight: normal">''<font color="Black"> slot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">import vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>
	** '''zone copy interface fc s'''<span style="font-weight: normal">''<font color="Black">lot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">export vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>		** '''zone copy interface fc s'''<span style="font-weight: normal">''<font color="Black">lot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">export vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>

Pravraj: /* Troubleshooting E Port Isolation Using the CLI */

2010-11-08T08:01:15Z

Troubleshooting E Port Isolation Using the CLI

← Older revision		Revision as of 08:01, 8 November 2010
Line 1,421:		Line 1,421:
	3. Use one of the following two approaches to resolve a zone merge failure:		3. Use one of the following two approaches to resolve a zone merge failure:
	* Overwrite the zoning configuration of one switch with the other switch's configuration. This can be done with the following commands:		* Overwrite the zoning configuration of one switch with the other switch's configuration. This can be done with the following commands:
		+
	** '''zone copy interface fc'''<span style="font-weight: normal">''<font color="Black"> slot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">import vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>		** '''zone copy interface fc'''<span style="font-weight: normal">''<font color="Black"> slot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">import vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>
	** '''zone copy interface fc s'''<span style="font-weight: normal">''<font color="Black">lot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">export vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>		** '''zone copy interface fc s'''<span style="font-weight: normal">''<font color="Black">lot</font>''</span><span style="font-style: normal">'''<font color="Black">/</font>'''</span><span style="font-weight: normal">''<font color="Black">port </font>''</span><span style="font-style: normal">'''<font color="Black">export vsan </font>'''</span><span style="font-weight: normal">''<font color="Black">vsan-id</font>''</span>

Pravraj: /* Troubleshooting ELP Issues Using the CLI */

2010-11-08T08:00:18Z

Troubleshooting ELP Issues Using the CLI

← Older revision		Revision as of 08:00, 8 November 2010
Line 1,273:		Line 1,273:
	This sample output shows the default settings for these timeout values.		This sample output shows the default settings for these timeout values.

-	3. Use the ~~<span style="font-style: normal">~~'''~~<font color="Black">~~fctimer ~~</font>~~'''~~</span>~~command in config mode to globally set these timeout values across all VSANs or use the ~~<span style="font-style: normal">~~'''~~<font color="Black">~~fctimer~~</font>'''</span> <span style="font-style: normal">'''<font color="Black">~~D_S_TOV~~</font>~~'''~~</span> <span style="font-weight: normal">~~''~~<font color="Black"><~~timeout~~></font>~~''~~</span> <span style="font-style: normal">~~'''~~<font color="Black">~~vsan~~</font>~~'''~~</span> <span style="font-weight: normal">~~''~~<font color="Black"><~~vsan-id~~> </font>~~''~~</span>~~command ~~for example~~, to set the D_S_TOV timeout for a particular VSAN to override the global values.	+	3. Use the '''fctimer''' command in config mode to globally set these timeout values across all VSANs or use the '''fctimer D_S_TOV''' ''timeout'' '''vsan''' ''vsan-id'' command, to set the D_S_TOV timeout for a particular VSAN to override the global values.

	4. Use the <span style="font-style: normal">'''<font color="Black">show port internal info interface fc</font>'''</span> command to verify that Rx buffer size matches on both ends of the ISL.		4. Use the <span style="font-style: normal">'''<font color="Black">show port internal info interface fc</font>'''</span> command to verify that Rx buffer size matches on both ends of the ISL.

Pravraj: /* Link Initialization Flow */

2010-11-08T07:54:50Z

Link Initialization Flow

Pravraj: /* Troubleshooting Port States from the CLI */

2010-11-08T07:53:38Z

Troubleshooting Port States from the CLI

← Older revision		Revision as of 07:53, 8 November 2010
Line 381:		Line 381:
	=== Troubleshooting Port States from the CLI ===		=== Troubleshooting Port States from the CLI ===

-	To display complete information for an interface, use the '''show''''<span style="font-style: normal">'''<font color="Black"> interface</font>'''</span> command. In addition to the state of the port, this command displays:	+	To display complete information for an interface, use the '''show'''<span style="font-style: normal">'''<font color="Black"> interface</font>'''</span> command. In addition to the state of the port, this command displays:

	* Port WWN		* Port WWN
Line 393:		Line 393:
	Example 8-1 displays the <span style="font-style: normal">'''<font color="Black">show interface</font>'''</span> command output.		Example 8-1 displays the <span style="font-style: normal">'''<font color="Black">show interface</font>'''</span> command output.

-	Example 8-1 show interface Command Output	+	'''Example 8-1 show interface Command Output'''
	<pre>		<pre>
	switch# show interface fc1/3		switch# show interface fc1/3

Pravraj: /* Isolating Port Issues Using Device Manager */

2010-11-08T07:52:18Z

Isolating Port Issues Using Device Manager

← Older revision		Revision as of 07:52, 8 November 2010
Line 369:		Line 369:
	3. Repeat Step 1 to determine if the port is online.		3. Repeat Step 1 to determine if the port is online.

-	: * If either of the ports fails to remain in the online state, then you may have a faulty GBIC, cabling or HBA/subsystem port.	+	:* If either of the ports fails to remain in the online state, then you may have a faulty GBIC, cabling or HBA/subsystem port.

	4. If both ports are online, click the <span style="font-style: normal">'''<font color="Black">FLOGI</font>'''</span> tab to verify that the Fibre Channel ports for the host and storage have performed a fabric login (FLOGI) and are communicating with their respective switches.		4. If both ports are online, click the <span style="font-style: normal">'''<font color="Black">FLOGI</font>'''</span> tab to verify that the Fibre Channel ports for the host and storage have performed a fabric login (FLOGI) and are communicating with their respective switches.

Pravraj: /* Device Manager: Port Selection */

2010-11-08T07:51:19Z

Device Manager: Port Selection

← Older revision		Revision as of 07:51, 8 November 2010
Line 317:		Line 317:
	Additional tabs include:		Additional tabs include:

-	* Rx BB Credit ~~—C onfigure~~ and view buffer-to-buffer credits (BB credits).	+	* Rx BB Credit —Configure and view buffer-to-buffer credits (BB credits).
-	* Other — View PortChannel ID, WWN, ~~Maximum Transmission Unit~~ (MTU), configure maximum receive buffer size.	+	* Other — View PortChannel ID, WWN, maximum transmission unit (MTU), configure maximum receive buffer size.
	* FLOGI — View FC ID, pWWN, nWWN, BB credits and class of service for N port connections.		* FLOGI — View FC ID, pWWN, nWWN, BB credits and class of service for N port connections.
	* ELP — View pWWN, nWWN, BB credits and supported classes of service for ISLs.		* ELP — View pWWN, nWWN, BB credits and supported classes of service for ISLs.

Pravraj: /* Device Manager: Summary View */

2010-11-08T07:50:39Z

Device Manager: Summary View

← Older revision		Revision as of 07:50, 8 November 2010
Line 298:		Line 298:
	=== Device Manager: Summary View ===		=== Device Manager: Summary View ===

-	In Device Manager, selecting the Summary View (~~'''~~Figure 8-2~~'''~~) expands on the information available for port monitoring. The display includes:	+	In Device Manager, selecting the Summary View (Figure 8-2) expands on the information available for port monitoring. The display includes:

	* VSAN assignment		* VSAN assignment
Line 305:		Line 305:
	* Speed		* Speed
	* Frames transmitted and received		* Frames transmitted and received
-	* Percent utilization for the CPU, dynamic memory, and ~~Flash~~ memory	+	* Percent utilization for the CPU, dynamic memory, and flash memory

	'''Figure 8-2 Device Manager: Summary View'''		'''Figure 8-2 Device Manager: Summary View'''

Pravraj: /* Overview of Symptoms */

2010-09-28T10:35:38Z

Overview of Symptoms

← Older revision		Revision as of 10:35, 28 September 2010
Line 1,565:		Line 1,565:
	=== Overview of Symptoms ===		=== Overview of Symptoms ===

-	An F port ~~may~~ be connected to a single N port, which is the mode used by peripheral devices (hosts or storage). In all the possible cases ~~an administrator~~ can encounter in troubleshooting an Fx port, two different scenarios can ~~be recognized~~:	+	An F port might be connected to a single N port, which is the mode used by peripheral devices (hosts or storage). In case all of the possible cases you can encounter in troubleshooting an Fx port, two different scenarios can occur:

	* The port does not come up (check the interface configuration, cabling, and the port connected to the switch).		* The port does not come up (check the interface configuration, cabling, and the port connected to the switch).
Line 1,578:		Line 1,578:
	* Why does the storage device fail to complete FLOGI to the switch?		* Why does the storage device fail to complete FLOGI to the switch?

-	'''Figure 8-7''' illustrates one possible ~~methodology~~ for troubleshooting Fx ports.	+	'''Figure 8-7''' illustrates one possible method for troubleshooting Fx ports.

-	'''Figure 8-7 Troubleshooting ~~Methodology~~'''	+	'''Figure 8-7 Fx Port Troubleshooting Method'''

	[[Image:Example.jpg]]		[[Image:Example.jpg]]

← Older revision		Revision as of 07:54, 8 November 2010
Line 1,054:		Line 1,054:
	Figure 8-6 shows the link initialization flow. It displays the following ordered sets transmitted between the ports and the primary operational states of the port during the process:		Figure 8-6 shows the link initialization flow. It displays the following ordered sets transmitted between the ports and the primary operational states of the port during the process:

-	1. Active state.	+	<p>1. Active state.</p>
-	2. Link recovery state (LR):	+	<p>2. Link recovery state (LR):</p>
	: a. LR transmit substate (LR1)		: a. LR transmit substate (LR1)
	: b. LR receive substate (LR2)		: b. LR receive substate (LR2)
	: c. LRR receive substate (LR3)		: c. LRR receive substate (LR3)
-	3. Offline state (OLS):	+	<p>3. Offline state (OLS):</p>
	: a. OLS transmit substate (OL1)		: a. OLS transmit substate (OL1)
	: b. OLS receive substate (OL2)		: b. OLS receive substate (OL2)
	: c. Wait for OLS substate (OL3)		: c. Wait for OLS substate (OL3)
-	4. Link failure state:	+	<p>4. Link failure state:</p>
	: a. NOS receive substate (LF1)		: a. NOS receive substate (LF1)
	: b. NOS transmit substate (LF2)		: b. NOS transmit substate (LF2)