To display the routes in the routing-instance-name.inet.0 table, use the show route table
routing-instance-name.inet.0 command.
•
inet.3—Stores all MPLS routes learned from LDP and RSVP signaling done for VPN
traffic. The routing table stores the MPLS routes only if the traffic-engineering bgp-igp
option is not enabled.
For VPN routes to be resolved properly, the inet.3 table must contain routes to all the
PE routers in the VPN.
To display the routes in the inet.3 table, use the show route table inet.3 command.
•
inet.0—Stores routes learned by the IBGP sessions between the PE routers. To provide
Internet access to the VPN sites, configure the routing-instance-name.inet.0 routing
table to contain a default route to the inet.0 routing table.
To display the routes in the inet.0 table, use the show route table inet.0 command.
The following routing policies, which are defined in VRF import and export statements,
are specific to VRF tables.
•
Import policy—Applied to VPN-IPv4 routes learned from another PE router to determine
whether the route should be added to the PE router’s bgp.l3vpn.0 routing table. Each
routing instance on a PE router has a VRF import policy.
•
Export policy—Applied to VPN-IPv4 routes that are announced to other PE routers.
The VPN-IPv4 routes are IPv4 routes that have been announced by locally connected
CE routers.
VPN route processing differs from normal BGP route processing in one way. In BGP, routes
are accepted if they are not explicitly rejected by import policy. However, because many
more VPN routes are expected, the Junos OS does not accept (and hence store) VPN
routes unless the route matches at least one VRF import policy. If no VRF import policy
explicitly accepts the route, it is discarded and not even stored in the bgp.l3vpn.0 table.
As a result, if a VPN change occurs on a PE router—such as adding a new VRF table or
changing a VRF import policy—the PE router sends a BGP route refresh message to the
other PE routers (or to the route reflector if this is part of the VPN topology) to retrieve
all VPN routes so they can be reevaluated to determine whether they should be kept or
discarded.
Related
Documentation
IGP Shortcuts and VPNs•
821Copyright © 2017, Juniper Networks, Inc.
Chapter 26: Configuring Layer 3 VPNs
To Next Page
Loading...
Need help?
General
