Npv Traffic Management; Automatic Uplink Selection; Traffic Maps; Disruptive Load Balancing - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

NPV Traffic Management

• The same device might log in using different fWWNs on the core switch (depending on the NPV link
Related Topics
•
NPV Traffic Management

Automatic Uplink Selection

NPV supports automatic selection of NP uplinks. When a server interface is brought up, the NP uplink interface
with the minimum load is selected from the available NP uplinks in the same VSAN as the server interface.
When a new NP uplink interface becomes operational, the existing load is not redistributed automatically to
include the newly available uplink. Server interfaces that become operational after the NP uplink can select
the new NP uplink.

Traffic Maps

In Release 4.0(1a)N2(1) and later software releases, NPV supports traffic maps. A traffic map allows you to
specify the NP uplinks that a server interface can use to connect to the core switches.
When an NPV traffic map is configured for a server interface, the server interface must select only from
Note
the NP uplinks in its traffic map. If none of the specified NP uplinks are operational, the server remains
in a non-operational state.
The NPV traffic map feature provides the following benefits:
• Facilitates traffic engineering by allowing configuration of a fixed set of NP uplinks for a specific server
• Ensures correct operation of the persistent FC ID feature, because a server interface will always connect

Disruptive Load Balancing

In Release 4.0(0)N1(2a) and later software releases, NPV supports disruptive load balancing. When disruptive
load balancing is enabled, NPV redistributes the server interfaces across all available NP uplinks when a new
NP uplink becomes operational. To move a server interface from one NP uplink to another NP uplink, NPV
forces reinitialization of the server interface so that the server performs a new login to the core switch.
Only server interfaces that are moved to a different uplink are reinitialized. A system message is generated
for each server interface that is moved.
Redistributing a server interface causes traffic disruption to the attached end devices.
Note
To avoid disruption of server traffic, you should enable this feature only after adding a new NP uplink, and
then disable it again after the server interfaces have been redistributed.
If disruptive load balancing is not enabled, you can manually reinitialize some or all of the server interfaces
to distribute server traffic to new NP uplink interfaces.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
500
it uses) and may need to be zoned using different fWWNs.
Configuring and Managing Zones, page 543
interface (or range of server interfaces).
to the same NP uplink (or one of a specified set of NP uplinks) after an interface reinitialization or switch
reboot.
Configuring N Port Virtualization
OL-16597-01