HP Cisco Nexus 5000 Cisco Nexus 5000 Series Switch CLI Software Configuration - Page 547

Configuring N Port Virtualization NPV Traffic Management Guidelines 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 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. 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 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. • NPV uses a load-balancing algorithm to automatically assign end devices in a VSAN to one of the NP 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. • If a server interface goes down and then returns to service, the interface is not guaranteed to be assigned to the same NP uplink. • The server interface is only operational when its assigned NP uplink is operational. OL-16597-01 Cisco Nexus 5000 Series Switch CLI Software Configuration Guide 501