Weighted Load-Balancing over MPLS LSP
46 Router Configuration Guide
• IGP prefix resolved to IGP shortcuts in RTM (rsvp-shortcut or advertise-tunnel-
link enabled in the IGP instance).
• BGP prefix with the BGP next-hop resolved to IGP shortcuts in RTM (rsvp-shortcut
enabled in the IGP instance).
• Static route prefix resolved to an indirect next-hop which itself is resolved to a set of
equal-metric MPLS LSPs in TTM. The user can allow automatic selection or specify
the names of the equal-metric MPLS LSPs in TTM to be used in the ECMP set.
• Static route prefix resolved to an indirect next-hop which itself is resolved to IGP
shortcuts in RTM.
• BGP prefix with a BGP next-hop resolved to a static route which itself resolves to set
of tunnel next-hops towards an indirect next-hop in RTM or TTM.
• BGP prefix resolving to another BGP prefix which next-hop is resolved to set of
ECMP tunnel next-hops with a static route in RTM or TTM or to IGP shortcuts in
RTM.
This feature does not modify the route calculation, thus the same set of ECMP next-hops is
computed for a prefix. It also does not change the hash routine, but only the spraying of the
flows over the tunnel next-hops is modified to reflect the normalized weight of each tunnel
next-hop.
As part of this feature, static route implementation has been enhanced to support ECMP over
a set of equal-cost MPLS LSPs. The user can allow automatic selection or specify the names
of the equal-metric MPLS LSPs in TTM to be used in the ECMP set. For more information
see Static Route Resolution Using Tunnels.
Weighted Load Balancing IGP, BGP, and Static Route
Prefix Packets over IGP Shortcut
Feature Configuration
The user must have IGP shortcut or forwarding adjacency feature enabled in one or more IGP
instances:
configure>router>ospf(isis)>rsvp-shortcut
configure>router>ospf(isis)>advertise-tunnel-link
The user can also disable specific MPLS LSPs from being used in IGP shortcut or forwarding
adjacency by configuring the following:
To Next Page
Loading...
