Enabling Chained Composite Next Hops For Ipv6 Labeled Unicast; Routes; Understanding Per-Packet Load Balancing - Juniper ACX1000 Configuration Manual

Enabling Chained Composite Next Hops for IPv6 Labeled Unicast Routes
Related
Documentation

Understanding Per-Packet Load Balancing

Copyright © 2017, Juniper Networks, Inc.
[edit chassis]
user@host>set network-services enhanced-ip
NOTE: A router reboot might be required. See Network Services Mode
Overview in the Junos OS Administration Library for details.
After you have completed the configuration, you can determine whether or not a Layer
3 VPN route is a part of a composite next hop by examining the display output of the
following commands:
show route route-value extensive
show route forwarding-table destination destination-value extensive
You can enable chained composite next hops for IPv6 labeled unicast routes by
configuring the labeled-bgp and inet6 statements:
To enable chained composite next hops for inet6 labeled unicast routes, include the
inet6 statement at the
chained-composite-next-hop ingress labeled-bgp]
disabled by default.
Chained Composite Next Hops for Transit Devices for VPNs
Configuring the Junos OS to Allocate More Memory for Routing Tables, Firewall Filters,
and Layer 3 VPN Labels
Network Services Mode Overview
Configuring Junos OS to Run a Specific Network Services Mode in MX Series Routers
By default, when there are multiple equal-cost paths to the same destination for the
active route, Junos OS uses a hash algorithm to choose one of the next-hop addresses
to install in the forwarding table. Whenever the set of next hops for a destination changes
in any way, the next-hop address is rechosen using the hash algorithm.
You can configure Junos OS so that, for the active route, all next-hop addresses for a
destination are installed in the forwarding table. This feature is called per-packet load
balancing. You can use load balancing to spread traffic across multiple paths between
routers.
Figure 44 on page 790 shows a simple load balancing scenario. Device R1 is in AS 65000
and is connected to both Device R2 and Device R3, which are in AS 65001. Device R1 can
be configured to load balance traffic across the two links.
Chapter 25: Configuring Layer 2 and Layer 3 Services
[edit routing-options forwarding-table
hierarchy level. This statement is
789