Configuring A Label Allocation And Substitution Policy For Vpns - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide
Related
Documentation

Configuring a Label Allocation and Substitution Policy for VPNs

850
To allow a Layer 3 VPN to transport IBGP traffic, include the
statement:
independent-domain;
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name routing-options autonomous-system
number]
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options autonomous-system number]
NOTE: All PE routers participating in a Layer 3 VPN with the
independent-domain
OS Release 6.3 or later.
NOTE: The
[edit logical-systems]
Series routers.
The independent domain uses the transitive path attribute 128 (attribute set) to tunnel
the independent domain's BGP attributes through the Internal BGP (IBGP) core. In Junos
OS Release 10.3 and later, if BGP receives attribute 128 and you have not configured an
independent domain in any routing instance, BGP treats the received attribute 128 as an
unknown attribute.
There is a limit of 16 ASs for each domain.
Example: Tunneling Layer 3 VPN IPv6 Islands over an IPv4 Core Using IBGP and
Independent Domains
Disabling Attribute Set Messages on Independent AS Domains for BGP Loop Detection
You can control label-advertisements on MPLS ingress and AS border routers (ASBRs).
Labels can be assigned on a per–next-hop (by default) or on a per-table basis (by
configuring the vrf-table-label
instance. You can also configure a policy to generate labels on a per-route basis by
specifying a label allocation policy.
To specify a label allocation policy for the routing instance, configure the
and specify a label allocation policy using the
label {
allocation label-allocation-policy;
}
statement in its configuration must be running Junos
hierarchy level is not applicable in ACX
statement). This choice affects all routes of a given routing
option:
allocation
Copyright © 2017, Juniper Networks, Inc.
independent-domain
label statement