Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, NX-OS 4.0 (OL-16598-01, June 2008)

Send comments to [e-mail]
12-4
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 12 Configuring N-Port Virtualization
Guidelines and Limitations
• 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.
Guidelines and Limitations
The following are recommended guidelines and requirements when deploying NPV:
• You can configure zoning for end devices that are connected to NPV devices using all available
member types on the NPV core switch. If fWWN, sWWN, domain, or port-based zoning is used,
then fWWN, sWWN, domain or port of the NPV core switch should be used.
• Port tracking is supported in NPV mode. See the “Information About Port Tracking” section on
page 27-1.
• Port security is supported on the NPV core switch for devices logged in through the NPV switch.
Port security is enabled on the NPV core switch on a per-interface basis. To enable port security on
the NPV core switch for devices logging in through an NPV switch, you must adhere to the
following requirements:
– The internal FLOGI must be in the port security database; in this way, the port on the NPV core
switch will allow communications and links.
– All the end device pWWNs must also be in the port security database.
By grouping devices into different NPV sessions based on VSANs, it is possible to support multiple
VSANs at the NPV-enabled switch. The correct uplink must be selected based on the VSANs that
the uplink can carry.
• NPV uses a load-balancing algorithm to automatically assign end devices in a VSAN to one of the
NPV core switch links (in the same VSAN) upon initial login. If there are multiple NPV core switch
links in the same VSAN, then you cannot assign an end device to a specific core switch link.
• If a server interface goes down and then returns to service, the interface may not be assigned to the
same core switch link.
• The server interface is only operational when its assigned core switch link is operational.
• Both servers and targets can be connected to the switch when in NPV mode.
• Local switching is not supported; all traffic is switched in the NPV core switch.
• NPV devices can connect to multiple NPV core switches. In other words, different NP ports can be
connected to different NPV core switches.
• NPV supports NPIV-capable module servers (nested NPIV).
• Only F, NP, and SD ports are supported in NPV mode.
Configuring NPV
When you enable NPV, your system configuration is erased and the system is rebooted with NPV mode
enabled.
Note We recommend that you save your current configuration either in boot flash memory or to a TFTP server
before NPV (if the configuration is required for later use).