Disruptive; Multiple Vsan Support; Npv Guidelines And Requirements - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

NPV Guidelines and Requirements

S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
•

Disruptive

Disruptive load balance works intependent of automatic selection of interfaces and configured traffic
map of external interfaces. This feature forces re-init of the server interfaces to achieve load balance
when this feature is enabled and whenever a new external interface comes up. To avoid flapping the
server interfaces too often undesirably, enable this feature once and then disable it whenever the needed
load balance is achieved.
If disruptive load balance is not enabled, you need to manually flap the server interface to move some
of the load to a new external interface.

Multiple VSAN Support

By grouping devices into different NPV sessions based on VSANs, it is possible to support multiple
VSANs on the NPV-enabled switch. The correct uplink must be selected based on the VSAN that the
uplink is carrying.
NPV Guidelines and Requirements
Following are recommended guidelines and requirements when deploying NPV:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco MDS 9000 Family Fabric Manager Configuration Guide
21-6
Balances the load by allowing the user to evenly distribute the load across external interfaces.
NPV core switches must support NPIV.
You can have up to 100 NPV devices.
Nondisruptive upgrades are supported. See
Port tracking is supported. See
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 or the domain/port of the NPV core switch should be used.
Port security is supported on the NPV core switch for devices logged in via NPV.
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 a specific one to an end device.
Both servers and targets can be connected to an NPV device.
Remote SPAN is not supported.
Local switching is not supported; all traffic is switched using 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.
In the case of servers that are booted over the SAN with NPV, if an NPV link failover occurs, servers
will lose access to their boot LUN temporarily.
NPV switches do not recognize the BB_SCN configuration on the xNP ports because of
interoperability issues with the third-party core switches.
Chapter 15, "Software Images."
Chapter 65, "Configuring Port Tracking."
Chapter 21 Configuring N Port Virtualization
OL-17256-03, Cisco MDS NX-OS Release 4.x