Configuring Routing Between Pe And Ce Routers In Layer 3 Vpns - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide
Related
Documentation

Configuring Routing Between PE and CE Routers in Layer 3 VPNs

830
route destination-prefix {
policy [ policy-names ];
static-options;
}
}
vrf-advertise-selective {
family {
inet-mvpn;
inet6-mvpn;
}
}
vrf-export [ policy-names ];
vrf-import [ policy-names ];
vrf-target (community | export community-name | import community-name);
vrf-table-label;
You can include these statements at the following hierarchy levels:
[edit routing-instances routing-instance-name]
[edit logical-systems logical-system-name routing-instances routing-instance-name]
NOTE: The
[edit logical-systems]
Series routers.
The sham-link , sham-link-remote
not applicable in ACX Series routers.
For Layer 3 VPNs, only some of the statements in the
are valid. For the full hierarchy, see Junos OS Routing Protocols Library.
In addition to these statements, you must enable a signaling protocol, IBGP sessions
between the PE routers, and an interior gateway protocol (IGP) on the PE and P routers.
By default, Layer 3 VPNs are disabled.
Many of the configuration procedures for Layer 3 VPNs are common to all types of VPNs.
Centralized Internet Access Through Layer 3 VPNs
Configuring Hub-and-Spoke VPN Topologies: One Interface
Configuring Overlapping VPNs Using Automatic Route Export
Configuring a Full-Mesh VPN Topology with Route Reflectors
Configuring a GRE Tunnel Interface Between a PE and CE Router
For the PE router to distribute VPN-related routes to and from connected CE routers, you
must configure routing within the VPN routing instance. You can configure a routing
hierarchy level is not applicable in ACX
, and vrf-advertise-selective
[edit routing-instances]
Copyright © 2017, Juniper Networks, Inc.
statements are
hierarchy