Policy Framework Configuration Guide - Juniper Networks

Chapter 6: Extended Actions Configuration
To include the bits in the IP address of the IPv4 or IPv6 payload as well as the first label
in the hash key, include the label-1 and payload ip statements at the
[edit forwarding-options hash-key family mpls] hierarchy level:
[edit forwarding-options hash-key]
family mpls {
label-1;
payload {
ip;
}
}
To include the bits of the IP address of the IPv4 or IPv6 payload as well as both the first
label and the second label in the hash key, include the label-1, label-2, and payload ip
statements at the [edit forwarding-options hash-key family mpls] hierarchy level.
[edit forwarding-options hash-key family mpls]
label-1;
label-2;
payload {
ip {
layer-3-only;
port-data {
source-msb;
source-lsb;
destination-msb;
destination-lsb;
}
}
}
To include only Layer 3 IP information in the hash key, specify the layer-3-only option at
the [edit forwarding-options hash-key family mpls payload ip] hierarchy level. To include
the most significant byte of the source port, specify the source-msb option. To include
the least significant byte of the source port, specify the source-lsb option. To include the
most significant byte of the destination port, specify the destination-msb option. To
include the least significant byte of the destination port, specify the destination-lsb option.
By default, the most significant byte and least significant byte of the source and
destination port fields are hashed. To select specific bytes to be hashed, include one or
more of the source-msb, source-lsb, destination-msb, and destination-lsb options at the
[edit forwarding-options hash-key family mpls payload ip port-data] hierarchy level. To
prevent all four bytes from being hashed, include the layer-3-only option at the [edit
forwarding-options hash-key family mpls payload ip] hierarchy level.
In an Layer 2 VPN scenario, the router could encounter a reordering complication. When
a burst of traffic pushes the customer traffic bandwidth to exceed its limits, the traffic
might be affected in mid flow. Packets may be reordered as a result.
You can configure the EXP bit of the top label to be excluded from the hash calculations
to avoid the reordering complication. To exclude the EXP bit of the first label from the
hash calculations, include the no-label-1-exp statement at the [edit forwarding-options
hash-key family mpls] hierarchy level:
Copyright © 2010, Juniper Networks, Inc.
147