Npv Traffic Management Guidelines; Npv Guidelines And Limitations - Cisco Nexus 6000 Series Configuration Manual

NPV Guidelines and Limitations

• The same device might log in using different fWWNs on the core switch (depending on the NPV link
Related Topics
Information About Zones, on page 79

NPV Traffic Management Guidelines

When deploying NPV traffic management, follow these guidelines:
• Use NPV traffic management only when automatic traffic engineering does not meet your network
• You do not need to configure traffic maps for all server interfaces. By default, NPV will use automatic
NPV Guidelines and Limitations
When configuring NPV, note the following guidelines and limitations:
• In-order data delivery is not required in NPV mode because the exchange between two end devices
• You can configure zoning for end devices that are connected to edge switches using all available member
• Port tracking is not supported in NPV mode.
• Port security is supported on the core switch for devices logged in through the NPV switch. Port security
• Servers can be connected to the switch when in NPV mode.
• When initiators and targets are assigned to the same border port (NP or NP-PO), then Cisco Nexus 5000
• Fibre Channel switching is not performed in the edge switch; all traffic is switched in the core switch.
• NPV supports NPIV-capable servers. This capability is called nested NPIV.
• Connecting two Cisco NPV switches together is not supported.
• Only VF and VNP port types are supported in NPV mode.
• For an NPV switch which is configured for trunking on any interface, or for a regular switch where the
Cisco Nexus 6000 Series NX-OS SAN Switching Configuration Guide, Release 6.x
30
it uses) and may need to be zoned using different fWWNs.
requirements.
traffic management.
always takes the same uplink from the edge switch to the core. Upstream of the edge switch, core switches
will enforce in-order delivery if configured.
types on the core switch. For fWWN, sWWN, domain, or port-based zoning, use the fWWN, sWWN,
domain, or port of the core switch in the configuration commands.
is enabled on the core switch on a per-interface basis. To enable port security on the core switch for
devices that log 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 core switch
will allow communications and links.
◦ All the end device pWWNs must also be in the port security database.
Series switches in NPIV mode do not support hairpinning.
f port-channel-trunk command is issued to enable the Trunking F Port Channels feature, follow these
configuration guidelines for reserved VSANs and isolated VSAN:
Configuring N Port Virtualization
OL-27932-01