7705 SAR Interfaces
124
Interface Configuration Guide
3HE 11011 AAAC TQZZA Edition: 01
If the selected LDP or RSVP-TE LSP has its NHLFE programmed with a LAG
interface, then a second round of hashing is needed, using the net result of the first
round of hashing as the hashing input.
3.2.14.3.2 LSR Label-IP Hashing
In the first round of hashing for LSR label IP hashing, the algorithm parses down the
label stack as described in LSR Label-only Hashing.
When the algorithm reaches the bottom of the stack, it checks the next nibble. If the
nibble value is 4, the packet is assumed to be an IPv4 packet and the result of the
label hash is fed into another hash along with the source and destination address
fields in the IP packet header. If the nibble value is not 4, the algorithm will just use
the label stack hash already calculated for the ECMP path selection.
The second round of hashing for LAG reuses the net result of the first round of
hashing.
3.2.14.3.3 LSR Label-IP Hashing with Layer 4 Header and TEID
If the lbl-ip-l4-teid option is configured, the Layer 4 source and destination UDP or
TCP port fields and the TEID field in the GTP header are included in the label-IP
hashing calculation. See Layer 4 Load Balancing and TEID Hashing for
GTP-encapsulated Traffic for more information.
3.2.14.3.4 Label Stack Profile Options
The lsr-load-balancing command includes a bottom-of-stack option that
determines the significance of the bottom-of-stack label (VC label) based on which
label stack profile option is specified. The profiles are:
• profile 1: favors better load balancing for pseudowires when the VC label
distribution is contiguous (default)
• profile 2: similar to profile 1 where the VC labels are contiguous, but provides an
alternate distribution
• profile 3: all labels have equal influence in hash key generation
To Next Page
Loading...
