Cisco MDS SanOS Troubleshooting Guide -- Troubleshooting N-Port Virtualization - Revision history

Pravraj: /* Core NPV Device is Not a Switch */

2010-11-04T10:56:59Z

Core NPV Device is Not a Switch

← Older revision		Revision as of 10:56, 4 November 2010
Line 228:		Line 228:

	===Core NPV Device is Not a Switch===		===Core NPV Device is Not a Switch===
-	To confirm that the core NPV device is not a switch, ~~perform the following tasks~~:	+	To confirm that the core NPV device is not a switch, follow these steps:
	----		----
	<p>1. Enter the '''show npv status''' command to check the status of the link.</p>		<p>1. Enter the '''show npv status''' command to check the status of the link.</p>

Pravraj: /* Waiting on External Link to Come Up */

2010-09-24T09:52:24Z

Waiting on External Link to Come Up

← Older revision		Revision as of 09:52, 24 September 2010
Line 280:		Line 280:
	If you are waiting for the external link to come up:		If you are waiting for the external link to come up:
	----		----
-	<p>1. Enter the show npv status command to check the status of the link. </p>	+	<p>1. Enter the '''show npv status''' command to check the status of the link. </p>
	<pre>switch# show npv status		<pre>switch# show npv status
	npiv is enabled		npiv is enabled
Line 288:		Line 288:
	Number of Server Interfaces: 7		Number of Server Interfaces: 7
	</pre>		</pre>
-	<p>2. If the ~~State~~ is "Waiting for External Interface," check the status of external link. At least one external link must be up for server interface to be up. </p>	+	<p>2. If the state is Waiting for External Interface, check the status of external link. At least one external link must be up for server interface to be up. </p>
	----		----
	--------------------------------------------------------------------------------		--------------------------------------------------------------------------------
	<center>'''Back to Main Page''': [[Cisco MDS SAN-OS Troubleshooting Guide]]		<center>'''Back to Main Page''': [[Cisco MDS SAN-OS Troubleshooting Guide]]
	--------------------------------------------------------------------------------		--------------------------------------------------------------------------------

Pravraj: /* Waiting on FLOGI from the Server or Target */

2010-09-24T09:51:44Z

Waiting on FLOGI from the Server or Target

← Older revision		Revision as of 09:51, 24 September 2010
Line 266:		Line 266:
	If you are waiting for the FLOGI from the server or target:		If you are waiting for the FLOGI from the server or target:
	----		----
-	<p>1. Enter the show npv status command to check the status of the link.</p>	+	<p>1. Enter the '''show npv status''' command to check the status of the link.</p>
	<pre>switch# show npv status		<pre>switch# show npv status
	npiv is enabled		npiv is enabled
Line 274:		Line 274:
	Number of Server Interfaces: 7		Number of Server Interfaces: 7
	</pre>		</pre>
-	<p>2. If the State is "Waiting for FLOGI,~~" then~~ no FLOGI request was received from the server or target. </p>	+	<p>2. If the State is Waiting for FLOGI, no FLOGI request was received from the server or target. </p>
	----		----
		+
	===Waiting on External Link to Come Up===		===Waiting on External Link to Come Up===
	If you are waiting for the external link to come up:		If you are waiting for the external link to come up:

Pravraj: /* Server Interface is Down */

2010-09-24T09:51:04Z

Server Interface is Down

← Older revision		Revision as of 09:51, 24 September 2010
Line 259:		Line 259:
	If the server interface is down:		If the server interface is down:
	----		----
-	<p>1. ~~Check to ensure~~ that the port is properly connected. </p>	+	<p>1. Ensure that the port is properly connected. </p>
-	<p>2. ~~Check to ensure~~ that the port mode on the NPV device side is set to "F~~-Port"~~ and that the '''no shutdown''' command has been ~~issued~~. </p>	+	<p>2. Ensure that the port mode on the NPV device side is set to F port and that the '''no shutdown''' command has been entered. </p>
	----		----
		+
	===Waiting on FLOGI from the Server or Target===		===Waiting on FLOGI from the Server or Target===
	If you are waiting for the FLOGI from the server or target:		If you are waiting for the FLOGI from the server or target:

Pravraj: /* NPV Core Switch Port Is Down */

2010-09-24T09:50:06Z

NPV Core Switch Port Is Down

← Older revision		Revision as of 09:50, 24 September 2010
Line 243:		Line 243:

	===NPV Core Switch Port Is Down===		===NPV Core Switch Port Is Down===
-	If the NPV core switch port is in the shutdown state, or it is not an F-port:	+	If the NPV core switch port is in the shutdown state, or is not an F port:
	----		----
	<p>1. Enter the '''show npv status''' command to check the status.</p>		<p>1. Enter the '''show npv status''' command to check the status.</p>
Line 253:		Line 253:
	Number of External Interfaces: 7		Number of External Interfaces: 7
	</pre>		</pre>
-	<p>2. If the state is "Other," verify that physical link to the NPV core switch or core port is in F port mode or is in administrative shutdown state. </p>	+	<p>2. If the state is Other, verify that the physical link to the NPV core switch or core port is in F port mode or is in administrative shutdown state. </p>
	----		----
		+
	===Server Interface is Down===		===Server Interface is Down===
	If the server interface is down:		If the server interface is down:

Pravraj: /* Core NPV Device Is Not a Switch */

2010-09-24T09:48:42Z

Core NPV Device Is Not a Switch

← Older revision		Revision as of 09:48, 24 September 2010
Line 227:		Line 227:
	----		----

-	===Core NPV Device Is Not a Switch===	+	===Core NPV Device is Not a Switch===
	To confirm that the core NPV device is not a switch, perform the following tasks:		To confirm that the core NPV device is not a switch, perform the following tasks:
	----		----
-	<p>1. Enter the show npv status command to check the status of the link.</p>	+	<p>1. Enter the '''show npv status''' command to check the status of the link.</p>
	<pre>switch# show npv status		<pre>switch# show npv status
	npiv is enabled		npiv is enabled
Line 239:		Line 239:
	Number of External Interfaces: 3		Number of External Interfaces: 3
	</pre>		</pre>
-	<p>2. If the state is "Failed~~" with~~ the reason "neighbor on upstream port is not fabric," ~~then~~ the external link is connected to non-fabric switch. </p>	+	<p>2. If the state is Failed and displays the reason "neighbor on upstream port is not fabric," the external link is connected to a non-fabric switch. </p>
	----		----
		+
	===NPV Core Switch Port Is Down===		===NPV Core Switch Port Is Down===
	If the NPV core switch port is in the shutdown state, or it is not an F-port:		If the NPV core switch port is in the shutdown state, or it is not an F-port:

Pravraj: /* VSAN Mismatches */

2010-09-24T09:47:52Z

VSAN Mismatches

← Older revision		Revision as of 09:47, 24 September 2010
Line 223:		Line 223:
	Number of External Interfaces: 1		Number of External Interfaces: 1
	</pre>		</pre>
-	<p>2. If the state is "Failed~~" with~~ the reason "Mismatch in VSAN for this upstream port" ~~then~~ the external interface is configured to have different VSAN on both ends. </p>	+	<p>2. If the state is Failed and displays the reason "Mismatch in VSAN for this upstream port" the external interface is configured to have different VSAN on both ends. </p>
	Correct the VSAN configuration. The VSAN configured on both ends of the NPV core switch link must be same.		Correct the VSAN configuration. The VSAN configured on both ends of the NPV core switch link must be same.
	----		----
		+
	===Core NPV Device Is Not a Switch===		===Core NPV Device Is Not a Switch===
	To confirm that the core NPV device is not a switch, perform the following tasks:		To confirm that the core NPV device is not a switch, perform the following tasks:

Pravraj: /* NPIV Is Not Enabled */

2010-09-24T09:46:58Z

NPIV Is Not Enabled

← Older revision		Revision as of 09:46, 24 September 2010
Line 193:		Line 193:
	----		----

-	===NPIV Is Not Enabled===	+	===NPIV is Not Enabled===
	If NPIV is not enabled on the NPV core switch:		If NPIV is not enabled on the NPV core switch:
	----		----
Line 205:		Line 205:
	Number of External Interfaces: 1		Number of External Interfaces: 1
	</pre>		</pre>
-	<p>2. If the state is "Failed" with the reason "NPIV is not enabled in upstream switch," ~~then~~ you must enable NPIV on the core NPV switch.</p>	+	<p>2. If the state is Failed with the reason "NPIV is not enabled in upstream switch," you must enable NPIV on the core NPV switch.</p>
	The NPV core switch is defined as an upstream switch on which NPIV is enabled. The NPV core switch receives traffic that is passed to it from a downstream switch that has NPV enabled on it. A switch that is in NPV mode does not switch traffic; instead, it passes traffic to the upstream NPV core switch on which NPIV is enabled.		The NPV core switch is defined as an upstream switch on which NPIV is enabled. The NPV core switch receives traffic that is passed to it from a downstream switch that has NPV enabled on it. A switch that is in NPV mode does not switch traffic; instead, it passes traffic to the upstream NPV core switch on which NPIV is enabled.

	After NPIV is enabled on the core NPV switch, the port should automatically come up (unless there are other issues).		After NPIV is enabled on the core NPV switch, the port should automatically come up (unless there are other issues).
	----		----
		+
	===VSAN Mismatches===		===VSAN Mismatches===
	If there is a VSAN mismatch in VSAN for the core NPV switch ports:		If there is a VSAN mismatch in VSAN for the core NPV switch ports:

Pravraj: /* Moving the Login of an End Device */

2010-09-24T09:45:53Z

Moving the Login of an End Device

← Older revision		Revision as of 09:45, 24 September 2010
Line 182:		Line 182:
	This section includes common NPV issues.		This section includes common NPV issues.
	===Moving the Login of an End Device===		===Moving the Login of an End Device===
-	If an uplink fails, ~~then~~ all the end devices that were logged in ~~via~~ the failed uplink are logged out. When the end devices log in again, the login requests are evenly distributed between all the operational uplink ports.	+	If an uplink fails, all of the end devices that were logged in through the failed uplink are logged out. When the end devices log in again, the login requests are evenly distributed between all the operational uplink ports.

	When a failed uplink comes back up, no existing logins are reassigned to that uplink. New logins are assigned to the operational uplink that has the least number of logins at the time; this is likely to be the previously failed uplink that has come back up.		When a failed uplink comes back up, no existing logins are reassigned to that uplink. New logins are assigned to the operational uplink that has the least number of logins at the time; this is likely to be the previously failed uplink that has come back up.
Line 192:		Line 192:
	<p>2. Enter the '''no shutdown''' command on the same server interface.</p>		<p>2. Enter the '''no shutdown''' command on the same server interface.</p>
	----		----
		+
	===NPIV Is Not Enabled===		===NPIV Is Not Enabled===
	If NPIV is not enabled on the NPV core switch:		If NPIV is not enabled on the NPV core switch:

Pravraj: /* Initial Troubleshooting Checklist */

2010-09-24T09:45:15Z

Initial Troubleshooting Checklist

← Older revision		Revision as of 09:45, 24 September 2010
Line 17:		Line 17:

	==Initial Troubleshooting Checklist==		==Initial Troubleshooting Checklist==
-	Troubleshooting an NPV problem involves gathering information about the switch configuration and connectivity of individual devices and the entire SAN fabric. Begin your troubleshooting activity ~~as follows~~:	+	Troubleshooting an NPV problem involves gathering information about the switch configuration and connectivity of individual devices and the entire SAN fabric. Begin your troubleshooting activity by using this checklist:

	<table border="1" cellpadding="2" cellspacing="0" width="80%" bordercolor="#808080"		<table border="1" cellpadding="2" cellspacing="0" width="80%" bordercolor="#808080"
Line 53:		Line 53:
	</tr>		</tr>
	<tr align="left" valign="top"><td><p class="pB1_Body1">		<tr align="left" valign="top"><td><p class="pB1_Body1">
-	For all NPV core switch links, ensure that the port mode on the NPV device is NP ~~Port~~, and ensure that the port mode on the NPV core switch is F ~~Port~~.	+	For all NPV core switch links, ensure that the port mode on the NPV device is NP port, and ensure that the port mode on the NPV core switch is F port.
	</p>		</p>
	</td>		</td>
Line 85:		Line 85:
	</tr>		</tr>
	<tr align="left" valign="top"><td><p class="pB1_Body1">		<tr align="left" valign="top"><td><p class="pB1_Body1">
-	Verify the status of servers and external interfaces, using the show npv status command.	+	Verify the status of servers and external interfaces, using the '''show npv status''' command.
	</p>		</p>
	</td>		</td>
Line 96:		Line 96:
	===Limitations and Restrictions===		===Limitations and Restrictions===
	* NPV core switches must support NPIV.		* NPV core switches must support NPIV.
-	* You cannot manually assign the server interfaces to a specific NPV core switch link. If an NPIV capable module is connected to the server interface, all the logins from the NPIV capable module will use the same NPIV core switch link.	+	* You cannot manually assign the server interfaces to a specific NPV core switch link. If an NPIV capable module is connected to the server interface, all of the logins from the NPIV-capable module will use the same NPIV core switch link.
	* Remote SPAN is not supported.		* Remote SPAN is not supported.
	* A maximum of 16 VSANs are supported on an NPV device.		* A maximum of 16 VSANs are supported on an NPV device.
-	* Local switching is not supported; ~~rather,~~ all traffic is switched via the NPV core switch.	+	* Local switching is not supported; all traffic is switched via the NPV core switch.
	* Only F, NP, and SD ports are supported in NPV mode.		* Only F, NP, and SD ports are supported in NPV mode.
	* CFS and QoS are not supported.		* CFS and QoS are not supported.
-	* IVR, SDV and FICON are not supported.	+	* IVR, SDV, and FICON are not supported.
	* If an NPV link failover occurs, servers that are booted over the SAN with NPV will temporarily lose access to their boot LUNs.		* If an NPV link failover occurs, servers that are booted over the SAN with NPV will temporarily lose access to their boot LUNs.

	===Common CLI Commands for NPV===		===Common CLI Commands for NPV===
	----		----
-	{{Note\|Because the output is based on name server database information, the show fcns database npv commands can be run from any MDS switch running SAN-OS 3.2(1) or later. The switch does not need to be NPV enabled.}}	+	{{Note\|Because the output is based on name server database information, the '''show fcns database npv''' commands can be run from any MDS switch running SAN-OS 3.2(1) or later. The switch does not need to be NPV enabled.}}
	----		----

-	To display the status and VSAN membership of the different servers and external interfaces, and to verify that NPIV is enabled on the switch, enter the show npv status command.	+	To display the status and VSAN membership of the different servers and external interfaces, and to verify that NPIV is enabled on the switch, enter the '''show npv status''' command.

	<pre>switch# show npv status		<pre>switch# show npv status
Line 125:		Line 125:
	</pre>		</pre>

-	To view all the NPV devices in the name server database, enter the show fcns database npv command.	+	To view all the NPV devices in the name server database, enter the '''show fcns database npv''' command.
	<pre>switch# show fcns database npv		<pre>switch# show fcns database npv
	VSAN 1:		VSAN 1: