Npv Traffic Management Guidelines - Cisco nexus 5000 series Cli Configuration Manual
Hide thumbs
Also See for nexus 5000 series:
- Configuration manual (334 pages) ,
- Command reference manual (196 pages) ,
- Operation manual (45 pages)
Table of Contents
Advertisement
Chapter 1
Configuring N Port Virtualization
S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
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.
NPV Traffic Management Guidelines
When deploying NPV traffic management, follow these guidelines:
•
•
•
•
•
•
Guidelines and Limitations
When configuring NPV, note the following guidelines and limitations:
•
•
•
•
•
OL-16597-01
Use 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, 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 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.
In-order data delivery is not required in 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.
You can configure zoning for end devices that are connected to edge switches using all available
member 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.
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 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.
–
Edge switches can connect to multiple core switches. In other words, different NP ports can be
connected to different core switches.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
Guidelines and Limitations
1-5
Advertisement
Chapters
Table of Contents
Troubleshooting
