Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring VPLS Load Balancing

By default, when there are multiple equal-cost paths to the same destination for the active route, the Junos OS uses a hash algorithm to select one of the next-hop addresses to install in the forwarding table. Whenever the set of next hops for a destination changes, the next-hop address is reselected using the hash algorithm.

You can configure the Junos OS so that, for the active route, all next-hop addresses for a destination are installed in the forwarding table. This feature is called per-packet load balancing. You can use load balancing to spread traffic across multiple paths between routers. You can also configure per-packet load balancing to optimize VPLS traffic flows across multiple paths.

You can load-balance VPLS traffic based on Layer 2 media access control (MAC) information, IP information and MPLS labels, or MPLS labels only.

Note: This feature is not supported on J Series Services Routers or MX Series routers. VPLS load balancing based on IP information and MPLS labels is supported only on the M120 and M320 routers.

To optimize VPLS traffic flows across multiple paths, include the family multiservice statement at the [edit forwarding-options hash-key] hierarchy level:

• destination-mac—Include the destination MAC address in the hash key used to load-balance the VPLS traffic.
• source-mac—Include the source MAC address in the hash key used to load-balance the VPLS traffic.

You can include the source MAC address in the hash key, the destination MAC address, or both.

For IPv4 traffic, only the IP source and destination addresses are included in the hash key. For MPLS and IPv4 traffic, one or two MPLS labels and IPv4 source and destination addresses are included. For MPLS Ethernet pseudowires, only one or two MPLS labels are included in the hash key. Optionally, you can include only Layer 3 information the IPv4 payload in the hash key.

• label-1—Include the first MPLS label in the hash key used to load-balance VPLS traffic.
• label-2—Include the second MPLS label in the hash key used to load-balance VPLS traffic.
• payload—Include bits from the IP payload in the hash key used to load-balance VPLS traffic.
• ip—Include the IP address of the IPv4 payload in the hash key used to load-balance VPLS traffic.
• layer-3-only—Include only Layer 3 information in the hash key used to load-balance VPLS traffic

For more information about how to configure per-packet load balancing, see the Junos OS Policy Framework Configuration Guide .