Example Terminology

B

bgp.l3vpn.0

The table on the provider edge (PE) router in which the VPN-IPv4 routes that are received from another PE router are stored. Incoming routes are checked against the vrf-import statements from all the VPNs configured on the PE router. If there is a match, the VPN–Internet Protocol version 4 (IPv4) route is added to the bgp.l3vpn.0 table. To view the bgp.l3vpn.0 table, issue the show route table bgp.l3vpn.0 command.

M

MP-EBGP

The multiprotocol external BGP (MP-EBGP) mechanism is used to export VPN-IPv4 routes across an autonomous system (AS) boundary. To apply this mechanism, use the labeled-unicast statement at the [edit protocols bgp group group-name family inet] hierarchy level.

R

routing-instance-name.inet.0

The routing table for a specific routing instance. For example, a routing instance called VPN-A has a routing table called VPN-A.inet.0. Routes are added to this table in the following ways:
- They are sent from a customer edge (CE) router configured within the VPN-A routing instance.
- They are advertised from a remote PE router that passes the vrf-import policy configured within VPN-A (to view the route, run the show route command). IPv4 (not VPN-IPv4) routes are stored in this table.

V

vrf-export policy-name

An export policy configured on a particular routing instance on a PE router. It is required for the configuration of interprovider and carrier-of-carriers VPNs. It is applied to VPN-IPv4 routes (originally learned from locally connected CE routers as IPv4 routes), which are advertised to another PE router or route reflector.

vrf-import policy-name

An import policy configured on a particular routing instance on a PE router. This policy is required for the configuration of interprovider and carrier-of-carriers VPNs. It is applied to VPN-IPv4 routes learned from another PE router or a route reflector.