Downlink-to-uplink interface mappings, Disruptive load balancing, Npv configuration task list – H3C Technologies H3C S10500 Series Switches User Manual

Page 107

•

Passes the response packet from the core switch to the node through the downlink interface.

Downlink-to-uplink interface mappings

NPV switches automatically map downlink interfaces to uplink interfaces. Before a downlink interface is

brought up, the NPV switch maps it to the uplink interface to which the minimum number of downlink
interfaces is mapped.
Typically, automatic mapping can meet your requirements. When a downlink interface must be

connected to a fabric through the specified uplink interfaces, you can manually map the downlink

interface to the uplink interfaces. After you configure the mapping, the downlink interface can be

mapped to only the configured uplink interfaces. If none of the configured uplink interfaces is operational,
the downlink interface cannot be operational.
A configured mapping selects the uplink interface with the minimum load from configured uplink

interfaces and then maps the downlink interface to it.
After a mapping is established, all traffic from the downlink interface is forwarded through the uplink
interface.

Disruptive load balancing

When a new uplink interface becomes operational, the NPV switch does not perform a remapping for

load balancing. In the event of remapping, the NPV switch reinitializes the downlink interface. Then, the

node connected to the downlink interface registers with the core switch again. This causes traffic

interruption to the node.
You can trigger a remapping by using commands for better load balancing. In this case, the NPV switch
reinitializes all downlink interfaces.

NPV configuration task list

Tasks at a glance

Remarks

(Required.) Configuring the switch to operate in NPV mode

See "

FCoE configuration restrictions and

guidelines

(Required.)

Configuring uplink interfaces and downlink

interfaces

N/A

(Optional.)