Cisco MDS SanOS Troubleshooting Guide -- Troubleshooting PortChannels and Trunking - Revision history

Pravraj: /* Newly Added Interface Does Not Come Online In a PortChannel */

2010-11-08T07:29:57Z

Newly Added Interface Does Not Come Online In a PortChannel

← Older revision		Revision as of 07:29, 8 November 2010
Line 166:		Line 166:
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Or, use the '''no shutdown''' CLI command to enable the PortChannel manually or use the '''channel-mode active''' CLI command in the interface submode for the PortChannel interface.	+	Also, use the '''no shutdown''' CLI command to enable the PortChannel manually or use the '''channel-mode active''' CLI command in the interface submode for the PortChannel interface.
	</p>		</p>
	</td>		</td>
Line 179:		Line 179:
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Or, use the '''channel-group''' ''<x>'' '''force''' CLI command in the interface submode for the physical interface.	+	Also, use the '''channel-group''' ''x'' '''force''' CLI command in the interface submode for the physical interface.
	</p>		</p>
	</td>		</td>

Pravraj: /* Trunking Issues */

2010-09-24T10:54:02Z

Trunking Issues

← Older revision		Revision as of 10:54, 24 September 2010
Line 223:		Line 223:
	</td>		</td>
	<td><p class="pB1_Body1">		<td><p class="pB1_Body1">
-	Enable trunking. In Fabric Manager, choose Switches > Interfaces > FC Logical, select the Trunk Config tab, and set the Admin drop-down menu to trunk. Click Apply Changes.	+	Enable trunking. In Fabric Manager, choose '''Switches''' > '''Interfaces''' > '''FC Logical''', select the '''Trunk Config''' tab, and set the Admin drop-down menu to trunk. Click '''Apply''' Changes.
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Use the trunk protocol enable CLI command.	+	Use the '''trunk protocol enable''' CLI command.
	</p>		</p>
	</td>		</td>
Line 257:		Line 257:
	</td>		</td>
	<td><p class="pB1_Body1">		<td><p class="pB1_Body1">
-	Add VSAN to allowed-active list. In Fabric Manager, choose Switches > Interfaces > FC Logical, select the Trunk Config tab, and set the Allowed VSANs field. Click Apply Changes.	+	Add VSAN to allowed-active list. In Fabric Manager, choose '''Switches''' > '''Interfaces''' > '''FC Logical''', select the Trunk Config tab, and set the Allowed VSANs field. Click '''Apply''' Changes.
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Use the switchport trunk allowed vsan CLI command.	+	Use the '''switchport trunk allowed vsan''' CLI command.
	</p>		</p>
	</td>		</td>

Pravraj: /* Newly Added Interface Does Not Come Online In a PortChannel */

2010-09-24T10:52:43Z

Newly Added Interface Does Not Come Online In a PortChannel

← Older revision		Revision as of 10:52, 24 September 2010
Line 166:		Line 166:
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Or, use the no shutdown CLI command to enable the PortChannel manually or use the channel-mode active CLI command in the interface submode for the PortChannel interface.	+	Or, use the '''no shutdown''' CLI command to enable the PortChannel manually or use the '''channel-mode active''' CLI command in the interface submode for the PortChannel interface.
	</p>		</p>
	</td>		</td>
Line 176:		Line 176:
	</td>		</td>
	<td><p class="pB1_Body1">		<td><p class="pB1_Body1">
-	Use the force option to force the physical interface to take on the parameters of the PortChannel. In Fabric Manager, choose ISLs > Port Channels, check the Force check box, and click Apply Changes.	+	Use the force option to force the physical interface to take on the parameters of the PortChannel. In Fabric Manager, choose '''ISLs''' > '''Port Channels''', check the '''Force''' check box, and click '''Apply''' Changes.
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Or, use the channel-group <x> force CLI command in the interface submode for the physical interface.	+	Or, use the '''channel-group''' ''<x>'' '''force''' CLI command in the interface submode for the physical interface.
	</p>		</p>
	</td>		</td>
Line 192:		Line 192:

	You see the PortChannels configured in the Information pane.</p>		You see the PortChannels configured in the Information pane.</p>
-	<p>2. Click the '''Protocols''' tab and, from the Mode drop-down menu, ~~select~~ the appropriate mode for the ~~Port Channel~~.</p>	+	<p>2. Click the '''Protocols''' tab and, from the Mode drop-down menu, click the appropriate mode for the PortChannel.</p>
	<p>3. Click '''Apply Changes''' icon to save any modifications or click '''Undo Changes''' to discard any changes.</p>		<p>3. Click '''Apply Changes''' icon to save any modifications or click '''Undo Changes''' to discard any changes.</p>
	----		----

Pravraj: /* PortChannel Issues */

2010-09-24T10:51:00Z

PortChannel Issues

← Older revision		Revision as of 10:51, 24 September 2010
Line 129:		Line 129:
	</td>		</td>
	<td><p class="pB1_Body1">		<td><p class="pB1_Body1">
-	Disable autocreation if you want to manually configure PortChannels. In Device Manager, select Interfaces > FC ALL..., ~~select~~ the Other tab, uncheck the AutoChannelCreate check box, and click Apply.	+	Disable autocreation if you want to manually configure PortChannels. In Device Manager, select '''Interfaces''' > '''FC ALL...''', click the '''Other''' tab, uncheck the '''AutoChannelCreate''' check box, and click '''Apply'''.
	</p>		</p>
	<p class="pB1_Body1">		<p class="pB1_Body1">
-	Use the no channel-group auto CLI command.	+	Use the '''no channel-group auto''' CLI command.
	</p>		</p>
	</td>		</td>

Pravraj: /* Initial Troubleshooting Checklist */

2010-09-24T10:49:42Z

Initial Troubleshooting Checklist

← Older revision		Revision as of 10:49, 24 September 2010
Line 27:		Line 27:

	==Initial Troubleshooting Checklist==		==Initial Troubleshooting Checklist==
-	Begin troubleshooting ~~Portchannel~~ and trunking issues by verifying that you have completed following actions first:	+	Begin troubleshooting PortChannel and trunking issues by verifying that you have completed following actions first:

	<table border="1" cellpadding="3" cellspacing="0" width="80%" bordercolor="#808080"		<table border="1" cellpadding="3" cellspacing="0" width="80%" bordercolor="#808080"
Line 39:		Line 39:
	</tr>		</tr>
	<tr align="left" valign="top"><td><p class="pB1_Body1">		<tr align="left" valign="top"><td><p class="pB1_Body1">
-	Use the show port-channel compatibility-parameters CLI command to determine PortChannel requirements.	+	Use the '''show port-channel compatibility-parameters''' CLI command to determine PortChannel requirements.
	</p>		</p>
	</td>		</td>
Line 71:		Line 71:
	</tr>		</tr>
	<tr align="left" valign="top"><td><p class="pB1_Body1">		<tr align="left" valign="top"><td><p class="pB1_Body1">
-	Verify that all required ~~VSANS~~ on a TE port are in the allowed-active VSAN list.	+	Verify that all required VSANs on a TE port are in the allowed-active VSAN list.
	</p>		</p>
	</td>		</td>
Line 80:		Line 80:
	</table>		</table>
	----		----
-	{{Note\|Use the show running interface CLI command to view the interface configuration in Cisco SAN-OS Release 3.0(1) or later. The interface configuration as seen in the show running-config CLI command is no longer consolidated.}}	+	{{Note\|Use the '''show running interface''' CLI command to view the interface configuration in Cisco SAN-OS Release 3.0(1) or later. The interface configuration as seen in the '''show running-config''' CLI command is no longer consolidated.}}
	----		----
	===Common Troubleshooting Tools in Fabric Manager===		===Common Troubleshooting Tools in Fabric Manager===
-	The following Fabric Manager navigation paths ~~may~~ be useful in troubleshooting any issues with PortChannel and trunking:	+	The following Fabric Manager navigation paths can be useful in troubleshooting any issues with PortChannel and trunking:

	* Choose '''ISLs > PortChannel''' to access the PortChannel configuration.		* Choose '''ISLs > PortChannel''' to access the PortChannel configuration.
-	* Choose '''Switches > Interfaces > FC''' ~~Logical~~ and ~~select~~ the '''Trunk Config''' tab to access the trunking configuration.	+	* Choose '''Switches > Interfaces > FC Logical''' and click the '''Trunk Config''' tab to access the trunking configuration.

	===Common Troubleshooting Commands in the CLI===		===Common Troubleshooting Commands in the CLI===
-	The following commands ~~may~~ be useful in troubleshooting PortChannel and trunking:	+	The following commands can be useful in troubleshooting PortChannel and trunking:

-	* show port-channel compatibility-parameters	+	* '''show port-channel compatibility-parameters'''
-	* show port-channel summary	+	* '''show port-channel summary'''
-	* show port-channel database	+	* '''show port-channel database'''
-	* show port-channel consistency detail	+	* '''show port-channel consistency detail'''
-	* show port-channel usage	+	* '''show port-channel usage'''
-	* show interface	+	* '''show interface'''
-	* show interface trunk	+	* '''show interface trunk'''
-	* show trunk protocol	+	* '''show trunk protocol'''

	==PortChannel Issues==		==PortChannel Issues==

Pravraj at 10:47, 24 September 2010

2010-09-24T10:47:22Z

← Older revision		Revision as of 10:47, 24 September 2010
Line 1:		Line 1:
	{{Template:Required Metadata}}		{{Template:Required Metadata}}
-	A ~~Portchannel~~ can aggregate multiple physical interfaces into one logical interface to provide higher aggregated bandwidth, load balancing, and link redundancy.	+	A PortChannel can aggregate multiple physical interfaces into one logical interface to provide higher aggregated bandwidth, load balancing, and link redundancy.

	__TOC__		__TOC__

Pravraj: /* Trunking Overview */

2010-09-24T10:47:10Z

Trunking Overview

← Older revision		Revision as of 10:47, 24 September 2010
Line 23:		Line 23:

	* PortChannel enables several physical links to be combined into one aggregated logical link.		* PortChannel enables several physical links to be combined into one aggregated logical link.
-	* Trunking enables a link transmitting frames in the EISL format to carry (trunk) multiple VSAN traffic. When trunking is operational on an E port, that E port becomes a TE port. A TE port is specific to switches in the Cisco MDS 9000 Family. An industry standard E port can link to other vendor switches and is referred to as a nontrunking interface.	+	* Trunking enables link transmitting frames in the EISL format to carry (trunk) multiple VSAN traffic.
		+	* When trunking is operational on an E port, that E port becomes a TE port. A TE port is specific to switches in the Cisco MDS 9000 Family. An industry standard E port can link to other vendor switches and is referred to as a nontrunking interface.

	==Initial Troubleshooting Checklist==		==Initial Troubleshooting Checklist==

Pravraj: /* PortChannel Overview */

2010-09-24T10:46:39Z

PortChannel Overview

← Older revision		Revision as of 10:46, 24 September 2010
Line 9:		Line 9:
	* Increases the aggregate bandwidth on an ISL by distributing traffic among all functional links in the channel.		* Increases the aggregate bandwidth on an ISL by distributing traffic among all functional links in the channel.
	* Load balances across multiple links and maintains optimum bandwidth utilization. Load balancing is based on the source ID, destination ID, and exchange ID (OX ID).		* Load balances across multiple links and maintains optimum bandwidth utilization. Load balancing is based on the source ID, destination ID, and exchange ID (OX ID).
-	* Provides high availability on an ISL. If one link fails, traffic previously carried on this link is switched to the remaining links. If a link goes down in a PortChannel, the upper protocol is not aware of it. ~~To the~~ upper protocol, the link is still there, although the bandwidth is diminished. The routing tables are not affected by link failure. PortChannels ~~may~~ contain up to 16 physical links and ~~may~~ span multiple modules for added high availability.	+	* Provides high availability on an ISL. If one link fails, traffic previously carried on this link is switched to the remaining links. If a link goes down in a PortChannel, the upper protocol is not aware of it. The upper protocol functions as if the link is still there, although the bandwidth is diminished. The routing tables are not affected by link failure. PortChannels can contain up to 16 physical links and can span multiple modules for added high availability.

	On switches with Generation 1 switching modules, or a combination of Generation 1 and Generation 2 switching modules, you can configure a maximum of 128 PortChannels. On switches with Generation 2 switching modules only, you can configure a maximum of 265 PortChannels.		On switches with Generation 1 switching modules, or a combination of Generation 1 and Generation 2 switching modules, you can configure a maximum of 128 PortChannels. On switches with Generation 2 switching modules only, you can configure a maximum of 265 PortChannels.

-	A PortChannel number refers to the unique (to each switch) identifier associated with each channel group. This number ranges from of 1 to 256.	+	A PortChannel number refers to the unique (to each switch) identifier associated with each channel group. This number ranges from of 1 to 256.

	==Trunking Overview==		==Trunking Overview==

Pravraj at 10:45, 24 September 2010

2010-09-24T10:45:36Z

← Older revision		Revision as of 10:45, 24 September 2010
Line 1:		Line 1:
	{{Template:Required Metadata}}		{{Template:Required Metadata}}
-	~~PortChannels refer to the aggregation of~~ multiple physical interfaces into one logical interface to provide higher aggregated bandwidth, load balancing, and link redundancy.	+	A Portchannel can aggregate multiple physical interfaces into one logical interface to provide higher aggregated bandwidth, load balancing, and link redundancy.

	__TOC__		__TOC__

Pravraj at 05:29, 4 August 2010

2010-08-04T05:29:46Z

← Older revision		Revision as of 05:29, 4 August 2010
Line 264:		Line 264:
	</tr>		</tr>
	</table>		</table>
		+
		+	--------------------------------------------------------------------------------
		+	<center>'''Back to Main Page''': [[Cisco MDS SAN-OS Troubleshooting Guide]]
		+	--------------------------------------------------------------------------------