Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
NOTE: J Series Services Routers do not support this feature.
Configuring VPLS Load Balancing Based on IP and MPLS Information
In Junos OS Release 9.4 and later, you can configure load balancing for VPLS traffic to
have the hash key include IP information and MPLS labels on the M120 and M320 routers
only. In earlier Junos OS Releases, you can configure load balancing based only on Layer 2
information. In Junos OS Release 9.5 and later, you can configure load balancing for VPLS
traffic based on Layer 3 IP and Layer 4 information on MX Series routers only. For more
information, see “Configuring VPLS Load Balancing on MX Series Ethernet Services
Routers” on page 151.
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.
NOTE: VPLS load balancing based on MPLS labels and IP information is
supported only on the M120 and M320 routers. In Junos OS Release 9.5 and
later, on MX Series routers only, you can configure VPLS load balancing based
on IP and Layer 4 information.
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:
150
Copyright © 2010, Juniper Networks, Inc.