Configuring N Port Virtualization
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
symbolic port name
symbolic node name
Although fWWN-based zoning is supported for NPV devices, it is not recommended because:
Default Port Numbers
Port numbers on NPV-enabled switches will vary depending on the switch model. For details about port
numbers for NPV-eligible switches, see
NPV Traffic Management
Before Cisco MDS SAN-OS release 3.3(1a), NPV supported automatic selection of external links. When
a server interface is brought up, an external interface with the minimum load is selected from the
available links. There is no manual selection on the server interfaces using the external links. Also, when
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Internal FLOGI Flows
NPV Core Switch
identifies the internal FLOGI parameters that appear in
Internal FLOGI parameters
The fWWN of the NP port.
The VSAN-based sWWN of the NPV device.
The fWWN of the F port on the NPV core switch.
The switch name and NP port interface string.
The IP address of the NPV device.
The NPV switch name.
Zoning is not enforced at the NPV device (rather, it is enforced on the NPV core switch).
Multiple devices behind an NPV device log in via the same F port on the core (hence, they use same
fWWN and cannot be separated into different zones).
The same device might log in using different fWWNs on the core switch (depending on the NPV
link it uses) and may need to be zoned using different fWWNs.
If there is no switch name available, then the output will simply read
"switch." For example,
Chapter 4, "On-Demand Port Activation Licensing."
Cisco MDS 9000 Family CLI Configuration Guide