Juniper ACX1000 Configuration Manual page 852

ACX Series Universal Access Router Configuration Guide
794
payload {
ether-pseudowire;
ip {
layer-3-only;
port-data {
destination-lsb;
destination-msb;
source-lsb;
source-msb;
}
}
}
}
You can include this statement at the
NOTE: When you configure payload ip (
hash-key family mpls payload ip), configuring
mandatory.
Load balancing functionality, without proper hash-keys configuration, may
result in an unpredictable behavior.
For Layer 2 VPN/pseudowire tunnel termination, upto two labels are used for hashing
and payload MAC destination and source addresses can be optionally selected. These
controls can be used to support ether-pseudowire knob in family mpls under hash-key
configuration shown above. However, since ACX2000 and ACX4000 also support TDM
pseudowires, the ether-pseudowire knobs needs to be used only when TDM pseudowires
are not being used.
For Layer 3 VPN tunnel termination, upto two labels are used for hasing and payload IP
source and destination addresses and Layer 4 source and destination ports can be
optionally selected. These controls can be used for supporting ip port-data knobs in
family mpls under hash-key configuration shown above. However, since Layer 4 port
MSB and LSB cannot be individually selected, one of destination-lsb or destination-msb
knobs or one of source-lsb or source-msb knobs would select Layer 4 destination or
source ports, respectively.
For LSR case, upto three labels are used for hashing. If a BOS is seen when parsing the
first three labels, BCM examines the first nibble of payload - if the nibble is 4, the payload
is treated as IPv4 and if the first nibble is 6, the payload is treated as IPv6 and in such
cases payload source and destination IP addresses can be speculatively used for hashing.
These controls can be used for supporting ip port-data knobs in family mpls under
hash-key configuration. However, Layer 4 ports cannot be used for hashing in LSR case,
and only layer-3-only knob is applicable. BCM does not claim support for hashing on
fields beyond the three MPLS labels. Load Balancing for a single pseudowire session
does not take place in case of LSR as all the traffic specific to that session will carry the
same set of MPLS labels.
Load balancing on LSR AE interfaces can be achieved for a higher number of MPLS
sessions, that is minimum of 10 sessions. This is applicable for CCC/VPLS/L3VPN. In
[edit forwarding-options hash-key]
set forwarding-options
user@host#
layer-3-only
Copyright © 2017, Juniper Networks, Inc.
hierarchy level.
and is
port-data