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. adding a member
to the existing port-channel does not trigger disruptive auto load-balance
Note
Adding a member to the existing port channel does not trigger disruptive auto load balance.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.
FC NPV Traffic Management Guidelines
When deploying FC NPV traffic management, follow these guidelines:
•
Use FC NPV traffic management only when automatic traffic engineering does not meet your network
requirements.
•
You do not need to configure traffic maps for all server interfaces. By default, FC NPV will use automatic
traffic management.
•
Server interfaces configured to use a set of NP uplink interfaces cannot use any other available NP uplink
interfaces, even if none of the configured interfaces are available.
•
When disruptive load balancing is enabled, a server interface may be moved from one NP uplink to
another NP uplink. Moving between NP uplink interfaces requires FC NPV to relogin to the core switch,
causing traffic disruption.
•
To link a set of servers to a specific core switch, associate the server interfaces with a set of NP uplink
interfaces that all connect to that core switch.
•
Configure Persistent FC IDs on the core switch and use the Traffic Map feature to direct server interface
traffic onto NP uplinks that all connect to the associated core switch.
FC NPV Guidelines and Limitations
When configuring FC NPV, note the following guidelines and limitations:
•
Fibre Channel N-port Virtualization (NPV) can co-exist with VXLAN on different fabric uplinks but
on same or different front panel ports on the Cisco Nexus 93180YC-FX switches. VXLAN can only
exist on the Ethernet front panel ports but not on the FC front panel ports.
•
In-order data delivery is not required in FC NPV mode because the exchange between two end devices
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.
Cisco Nexus 9000 Series NX-OS FC NPV Configuration Guide
11
Configuring N Port Virtualization
FC NPV Traffic Management Guidelines
To Next Page
Loading...
