Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
Configuring Load Balancing Based on MPLS Labels
To load-balance based on the MPLS label information, include the family mpls statement
at the [edit forwarding-options hash-key] hierarchy level:
[edit forwarding-options hash-key]
family mpls {
label-1;
label-2;
label-3;
no-labels;
no-label-1-exp;
payload {
ether-pseudowire;
ip {
layer-3-only;
port-data {
destination-lsb;
destination-msb;
source-lsb;
source-msb;
}
}
}
}
This feature applies to aggregated Ethernet and aggregated SONET/SDH interfaces as
well as multiple equal-cost MPLS next hops. In addition, on the T Series, MX Series, M120,
and M320 routers only, you can configure load balancing for IPv4 traffic over Layer 2
Ethernet pseudowires. You can also configure load balancing for Ethernet pseudowires
based on IP information. The option to include IP information in the hash key provides
support for Ethernet circuit cross-connect (CCC) connections. For more information
about configuring load balancing for Ethernet pseudowires, see “Configuring Load
Balancing for Ethernet Pseudowires” on page 148.
To include the first label in the hash key, include the label-1 option. This is used for a
one-label packet.
To include the first and second label in the hash key, include both the label-1 and label-2
options. This is used for a two-label packet. The router provides hashing on the first and
second labels by default. If both labels are specified, the entire first label and the first
16 bits of the second label are hashed.
To include the third MPLS label in the hash function, include the label-3 option at the
[edit forwarding-options hash-key family mpls] hierarchy level. To include no MPLS labels
in the hash function, include the no-labels option at the [edit forwarding-options hash-key
family mpls] hierarchy level.
Hashing can include IP addresses to provide better distribution of traffic to aggregated
interfaces.
146
Copyright © 2010, Juniper Networks, Inc.