Configuring Protocol-Independent Load Balancing In Layer 3 Vpns; Configuring Load Balancing For Layer 3 Vpns - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide

Configuring Protocol-Independent Load Balancing in Layer 3 VPNs

Configuring Load Balancing for Layer 3 VPNs

852
a label substitution policy:
reject
.
term default then reject
Protocol-independent load balancing for Layer 3 VPNs allows the forwarding next hops
of both the active route and alternative paths to be used for load balancing.
Protocol-independent load balancing works in conjunction with Layer 3 VPNs. It supports
the load balancing of VPN routes independently of the assigned route distinguisher. When
protocol-independent load balancing is enabled, both routes to other PE routers and
routes to directly connected CE routers are load-balanced.
When load-balancing information is created for a given route, the active path is marked
as in the output of the
Routing Use Only
The following sections describe how to configure protocol-independent load balancing
and how this configuration can affect routing policies:
Configuring Load Balancing for Layer 3 VPNs on page 852
Configuring Load Balancing and Routing Policies on page 854
The configuration of protocol-independent load balancing for Layer 3 VPNs is a little
different for IPv4 versus IPv6:
IPv4—You only need to configure the
routing-instances routing-instance-name routing-options]
routing-instances routing-instance-name routing-options rib routing-table-name]
level.
IPv6—You need to configure the
routing-instance-name routing-options]
routing-instance-name routing-options rib routing-table-name]
NOTE: You cannot configure the
at the same time that you have configured the
To configure protocol-independent load balancing for Layer 3 VPNs, include the
statement:
multipath {
vpn-unequal-cost equal-external-internal;
}
When you include the multipath
protocol-independent load balancing is applied to the default routing table for that
routing instance (routing-instance-name.inet.0):
[edit routing-instances routing-instance-name routing-options]
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options]
set policy-options policy-statement no-label-substitution
command.
show route table
statement at either the
multipath
statement at both the
multipath
hierarchy level and the
statement and sub-statements
multipath
statement at the following hierarchy levels,
Copyright © 2017, Juniper Networks, Inc.
[edit
hierarchy level or the [edit
hierarchy
[edit routing-instances
[edit routing-instances
hierarchy level.
l3vpn statement.
multipath