IP Router Configuration
Router Configuration Guide 105
Context config>router>flowspec
Description This command configures the maximum number of IPv6 flowspec routes or rules that can be
embedded into the auto-created embedded filter (fSpec-X). Flowspec filter entries embedded in a filter
policy in this routing instance will use filter entries from the range between “embedding offset + 1”
and “embedding offset + ip-filter-max-size”.
The sum of the ip-filter-max-size value parameter and the highest offset in any IPv6 filter that embeds
IPv6 flowspec rules from this routing instance (excluding filters that embed at offset 65535) must not
exceed 65535.
The ip-filter-max-size configuration can be adjusted up or down at any time. If the number of IPv6
flowspec rules that are currently installed is M, and the new limit is N, where N<M, then the last set of
rules from N to M (by flowspec order) are immediately removed, but are retained in the BGP RIB. If
the limit is increased, new rules are programmed only as they are received again in new BGP updates.
Default ipv6-filter-max-size default
Parameters value — The maximum number of flowspec routes or rules that can be embedded into an ingress
IP filter policy
Values 0 — 65535
default — Keyword to configure the maximum size as 512
weighted-ecmp
Syntax weighted-ecmp
no ecmp
Context config>router
Description This command enables the weighted load-balancing, or weighted ECMP, over MPLS LSP.
When this command is enabled, packets of IGP, BGP, and static route prefixes resolved to a set of
ECMP tunnel next-hops are sprayed proportionally to the weights configured for each MPLS LSP in
the ECMP set.
Weighted load-balancing over MPLS LSP is supported in the following forwarding contexts:
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 or advertise-
tunnel-link 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.
To Next Page
Loading...
