Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring VPLS Load Balancing on MX Series 5G Universal Routing Platforms

 

In Junos OS Release 9.5 and later, on MX Series routers, you can configure the load balancing hash key for Layer 2 traffic to use fields in the Layer 3 and Layer 4 headers inside the frame payload. You can also configure VPLS load balancing based on IP and MPLS information on M120 and M320 routers only. For more information, see Configuring VPLS Load Balancing Based on IP and MPLS Information.

You can configure load balancing on MX Series routers based on Layer 3 or Layer 4 information or both.

To configure VPLS load balancing on the MX Series router to include either Layer 3 IP information or Layer 4 headers or both:

  1. Include the payload statement at the [edit forwarding-options hash-key family multiservice] hierarchy level.
  2. Include the ip statement at the [edit forwarding-options hash-key family multiservice payload] hierarchy level.

To configure VPLS load balancing to include the Layer 3 information:

  1. Include the layer-3 statement at the [edit forwarding-options hash-key family multiservice payload ip] hierarchy level.
  2. Include the source-ip-only statement at the [edit forwarding-options hash-key family multiservice payload ip layer-3] hierarchy level to include information about the IP source address only in the hash key.
  3. Include destination-ip-only statement at the [edit forwarding-options hash-key family multiservice payload ip layer-3] hierarchy level to include information about the IP destination address only in the hash key.Note

    You can configure either the source-ip-only or the destination-ip-only statements at a time, not both. They are mutually exclusive.

To configure VPLS load balancing to include Layer 4 information:

  • Include the layer-4 statement at the [edit forwarding-options hash-key family multiservice payload ip] hierarchy level.

The following example shows load balancing configured to use the source Layer 3 IP address option and Layer 4 header fields as well as the source and destination MAC addresses:

Related Documentation