Configuring Load Balancing Based On Mpls Labels On Acx Series Routers - Juniper ACX1000 Configuration Manual

Related
Documentation

Configuring Load Balancing Based on MPLS Labels on ACX Series Routers

Copyright © 2017, Juniper Networks, Inc.
[edit]
policy-options {
policy-statement load-balancing-policy {
from {
route-filter 192.168.10/24 orlonger;
route-filter 10.114/16 orlonger;
}
then {
load-balance per-packet;
}
}
}
routing-options {
forwarding-table {
export load-balancing-policy;
}
}
Configuring Per-Packet Load Balancing on page 790
ACX Series routers can load-balance on a per-packet basis in MPLS. Load balancing can
be performed on information in both the IP header and on up to three MPLS labels,
providing a more uniform distribution of MPLS traffic to next hops. This feature is enabled
on supported platforms by default and requires no configuration.
Load balancing is used to evenly distribute traffic when there is a single next hop over
an aggregated interface or a LAG bundle. Load balancing using MPLS labels is supported
only for LAG interfaces and not for equal-cost multipath (ECMP) links.
By default, when load balancing is used to help distribute traffic, Junos OS employs a
hash algorithm to select a next-hop address to install into the forwarding table. Whenever
the set of next hops for a destination changes in any way, the next-hop address is
reselected by means of the hash algorithm. You can configure how the hash algorithm
is used to load-balance traffic across interfaces in an aggregated Ethernet (ae) interface.
An LSP tends to load-balance its placement by randomly selecting one of the interfaces
in an ae- interface bundle and using it exclusively. The random selection is made
independently at each transit router, which compares Interior Gateway Protocol (IGP)
metrics alone. No consideration is given to bandwidth or congestion levels.
To load-balance based on the MPLS label information, configure the
statement:
[edit forwarding-options hash-key]
family mpls {
all-labels;
label-1;
label-2;
label-3;
no-labels;
Chapter 25: Configuring Layer 2 and Layer 3 Services
family mpls
793