Why L3VPN configuration” {import | export} route-policy “not take effected

gennady_fedonov · Created Feb 20, 2016 00:34:12

{Import | export} configured VPN instance route-policy is in terms relative to the VPN instance. import route-policy control from other instances of routing, export route-policy control is the route to go to other instances.

For example, suppose PE1 can receive the VPNv4 routes down from the cross to vpna PE2, PE1 local vpna and vpnb also cross ties, but also with CE under vpna established peer.

In the vpna PE1 with import route-policy, or vpnb cross over from VPNv4 route will by this policy control.
A route from the CE, although the CE is a public network, but in terms of PE1, peer vpna is built, the route received belonged vpna, not the other VPN or VPNv4 or public network from the PE1, and Therefore, this policy is not affected.

Similarly, in the vpna PE1 with export route-policy, to cross from vpna vpnb route, as well as copies of VPNv4 routes that are affected by this policy control.
Sent to CE routing, although no longer belong in the CE vpna, but in terms of PE1, and not to the other VPN routing or VPNv4 or public network PE1 go on, so this policy is not affected.

Why L3VPN configuration” {import | export} route-policy “not take effected

Third Party’s Trade Secret

My Followers

Enterprise

Consumer

Corporate

Carriers

Why L3VPN configuration” {import | export} route-policy “not take effected

Third Party’s Trade Secret

My Followers