Npv Traffic Management Guidelines; Npv Guidelines And Limitations - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual
Cli software configuration guide
Hide thumbs
Also See for AP775A - Nexus Converged Network Switch 5010:
- Configuration manual (1486 pages) ,
- Reference (886 pages) ,
- Command reference manual (792 pages)
Table of Contents
Advertisement
Configuring N Port Virtualization
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
• Server interfaces configured to use a set of NP uplink interfaces cannot use any other available NP uplink
• When disruptive load balancing is enabled, a server interface may be moved from one NP uplink to
• To link a set of servers to a specific core switch, associate the server interfaces with a set of NP uplink
• Configure Persistent FC IDs on the core switch and use the Traffic Map feature to direct server interface
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
• Edge switches can connect to multiple core switches. In other words, different NP ports can be connected
• NPV uses a load-balancing algorithm to automatically assign end devices in a VSAN to one of the NP
• If a server interface goes down and then returns to service, the interface is not guaranteed to be assigned
• The server interface is only operational when its assigned NP uplink is operational.
OL-16597-01
requirements.
traffic management.
interfaces, even if none of the configured interfaces are available.
another NP uplink. Moving between NP uplink interfaces requires NPV to relogin to the core switch,
causing traffic disruption.
interfaces that all connect to that core switch.
traffic onto NP uplinks that all connect to the associated core switch.
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.
to different core switches.
uplinks (in the same VSAN) upon initial login. If there are multiple NP uplinks in the same VSAN, you
cannot assign an end device to a specific NP uplink.
to the same NP uplink.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
NPV Traffic Management Guidelines
501
Advertisement
Chapters
Table of Contents
Troubleshooting
