Core Npv Device Is Not A Switch; Npv Core Switch Port Is Down; Server Interface Is Down - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Common Problems with NPV
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
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

To confirm that the core NPV device is not a switch, perform the following tasks:
Enter the show npv status command to check the status of the link
Step 1
switch# show npv status
npiv is enabled
External Interfaces:
====================
Interface: ext17, FCID: 0x000000, State: Failed(neighbor on the upstream
port is not fabric)
Number of External Interfaces: 3
If the state is "Failed" with the reason "neighbor on upstream port is not fabric," then the external link
Step 2
is connected to non-fabric switch.

NPV Core Switch Port Is Down

If the NPV core switch port is in the shutdown state, or it is not an F-port:
Enter the show npv status command to check the status.
Step 1
switch# show npv status
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, VSAN: 1, FCID: 0x000000, State: Other
Number of External Interfaces: 7
Step 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.

Server Interface is Down

If the server interface is down:
Check to ensure that the port is properly connected.
Step 1
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
9-6
Chapter 9 Troubleshooting N-Port Virtualization
OL-9285-05