> # Internal FLOGI Parameters

> When an NP port comes up, the NPV device first logs itself in to the NPV core switch and sends a FLOGI request that includes the following parameters:

> - The fWWN (fabric port WWN) of the NP port used as the pWWN in the internal login.
> - The VSAN-based sWWN (switch WWN) of the NPV device used as nWWN (node WWN) in the internal FLOGI.

> After completing its FLOGI request, the NPV device registers itself with the fabric name server using the following additional parameters:

> - Switch name and interface name (for example, fc1/4) of the NP port is embedded in the symbolic port name in the name server registration of the NPV device itself.
> - The IP address of the NPV device is registered as the IP address in the name server registration of the NPV device.

> Note The BB_SCN of internal FLOGIs on NP ports is always set to zero. The BB_SCN is supported at the F-port of the NPV device.

> Table 11-1 identifies the internal FLOGI parameters .

> Table 11-1 Internal FLOGI Parameters
> Parameter | Derived From
> --- | ---
> pWWN | The fWWN of the NP port.
> nWWN | The VSAN-based sWWN of the NPV device.
> fWWN | The fWWN of the F port on the NPV core switch.
> symbolic port name | The switch name and NP port interface string. Note If there is no switch name available, then the output will display “switch.” For example, switch: fc1/5.
> IP address | The IP address of the NPV device.
> symbolic node name | The NPV switch name.

> Although fWWN-based zoning is supported for NPV devices, it is not recommended because:

> - 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 (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.

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.