Juniper ACX1000 Configuration Manual page 878

ACX Series Universal Access Router Configuration Guide
820
The Junos OS uses the following routing tables for VPNs:
—Stores all VPN-IPv4 unicast routes received from other PE routers. (This
bgp.l3vpn.0
table does not store routes received from directly connected CE routers.) This table is
present only on PE routers.
When a PE router receives a route from another PE router, it places the route into its
routing table. The route is resolved using the information in the
bgp.l3vpn.0
table. The resultant route is converted into IPv4 format and redistributed to all
routing-instance-name.inet.0
policy.
The table is also used to resolve routes over the MPLS tunnels that connect
bgp.l3vpn.0
the PE routers. These routes are stored in the
connectivity must exist in
When a router is advertising non-local VPN-IPv4 unicast routes and the router is a
route reflector or is performing external peering, the VPN-IPv4 unicast routes are
automatically exported into the VPN routing table (
router to perform path selection and advertise from the
To determine whether to add a route to the
checks it against the VRF instance import policies for all the VPNs configured on the
PE router. If the VPN-IPv4 route matches one of the policies, it is added to the
bgp.l3vpn.0 routing table. To display the routes in the
the
show route table bgp.l3vpn.0
routing-instance-name.inet.0
connected CE routers in a routing instance (that is, in a single VPN) and all explicitly
configured static routes in the routing instance. This is the VRF table and is present
only on PE routers. For example, for a routing instance named
for that instance is named
When a CE router advertises to a PE router, the PE router places the route into the
corresponding
routing-instance-name.inet.0
other PE routers if it passes a VRF export policy. Among other things, this policy tags
the route with the route distinguisher (route target) that corresponds to the VPN site
to which the CE belongs. A label is also allocated and distributed with the route. The
routing table is not involved in this process.
bgp.l3vpn.0
The
routing-instance-name.inet.0
PE router that match the VRF import policy for that VPN. The remote PE router
redistributed these routes from its
Routes are not redistributed from the
table; they are directly advertised to other PE routers.
bgp.l3vpn.0
For each routing-instance-name.inet.0
in the router's Packet Forwarding Engine. This table is maintained in addition to the
forwarding tables that correspond to the router's
with the and
inet.0 mpls.0
routing-instance-name.inet.0
routing tables on the PE router if it matches the VRF import
inet.3
inet.3 (not just in inet.0 ) for VPN routes to be resolved properly.
bgp.l3vpn.0
command.
—Stores all unicast IPv4 routes received from directly
.
VPN-A.inet.0
routing table and advertises the route to
table also stores routes announced by a remote
table.
bgp.l3vpn.0
routing-instance-name.inet.0
routing table, one forwarding table is maintained
inet.0
routing tables, the best routes from the
routing table are placed into the forwarding table.
inet.3
routing table. PE-to-PE router
). This enables the
bgp.l3vpn.0
bgp.l3vpn.0 routing table.
routing table, the Junos OS
bgp.l3vpn.0 routing table, use
, the routing table
VPN-A
table to the
and routing tables. As
mpls.0
Copyright © 2017, Juniper Networks, Inc.
routing