Configuring Hash Factors (L2/L3VPN Over L2VPN Scenarios)

Configuration Guide

In VS mode, this configuration process is supported only by the admin VS.

Suitable Scenarios

Figure 1 L2/L3VPN Over L2VPN

As shown in Figure 1, in the L2/L3VPN over L2VPN scenarios, L2-PEs are the ingress of the L2VPN tunnel for MPLS L2/L3VPN packets. L2-PEs balance traffic among member interfaces of the outbound Eth-Trunk interface based on MAC addresses carried in packets by default. Because packets transmitted over the same VPLS tunnel carry the same MAC address, traffic from the same site but different L3VPNs cannot be load-balanced among member interfaces of the Eth-Trunk interface. To solve this problem, you can run this command to configure backbone PEs to work in IP-address-based load-balancing mode, evenly distributing traffic from the same site but different L3VPNs among links between L2-PE1 and L2-P1.

Follow-up Procedure

If this command is configured but traffic load balancing cannot be performed well, you can try to modify hash-arithmetic. For detailed information, see Configuring Hash-arithmetic.

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.