Configuring VPLS Load Balancing Based on IP and MPLS Information
Load balancing for VPLS traffic is handled differently by different routing platforms. For more information, see Configuring VPLS Load Balancing on MX Series 5G Universal Routing Platforms.
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.
To optimize VPLS flows across multiple paths based on IP and
MPLS information, include the family multiservice statement
at the [edit forwarding-options hash-key] hierarchy level:
[edit forwarding-options hash-key] family multiservice { label-1; label-2; payload { ip { layer-3-only; } } }
To use the first MPLS label in the hash key, include the label-1 statement:
[edit forwarding-options hash-key family multiservice] label-1;
To use the second MPLS label, include both the label-1 and label-2 statements:
[edit forwarding-options hash-key family multiservice] label-1; label-2;
To use the packet’s IPv4 payload in the hash key, include
the payload and ip statements:
[edit forwarding-options hash-key family multiservice]
payload {
ip;
}
Only IPv4 is supported.
To include only Layer 3 information from the IPv4 payload,
specify the layer-3-only option to the payload ip statement:
[edit forwarding-options hash-key family multiservice]
payload {
ip {
layer-3-only;
}
}
To use the first and second MPLS labels and the packet’s
IP payload in the hash key, include the label-1, label-2, and payload ip statements:
[edit forwarding-options hash-key family multiservice]
label-1;
label-2;
payload {
ip;
}