[j-nsp] Layer 3 VPN Routing and Forwarding (VRF) Tables Issue
jimmy at pacnet.net
Mon Oct 5 04:32:54 EDT 2009
I have a situation where the PE (router A) is not advertising the routes
that they got from direct peering (for example under CT vrf) to other PE
(router B) under different vrf (for example premium vrf).
I have confirmed that in router A, all the routes that are learned via
direct peering (CT vrf) are inside premium vrf route table.
It means the import policy is working.
The strange thing, thouse routes are not being advertised to premium vrf in
router B. I have confirmed there is no problem with export policy in router
A and import policy in router B.
In router A, under route table bgp.l3vpn.0, I am seeing the route that is
learned via direct peering interface. This shouldn't be the case right?
route table bgp.l3vpn.0 22.214.171.124/18
bgp.l3vpn.0: 316803 destinations, 316803 routes (316803 active, 0 holddown,
+ = Active Route, - = Last Active, * = Both
*[BGP/170] 6w6d 21:34:02, MED 100, localpref 250, from
AS path: 1334 I
to 126.96.36.199 via so-1/2/0.0 ---------> Direct peering
> to 188.8.131.52 via so-1/3/0.0 ---------> Direct peering
I can confirm that direct connected, static, and customer's BGP routes that
are provisioned in router A under premium vrf are being seen under router B
under premium vrf. So the issue is only on those routes that are learned via
direct peering under CT vrf. Those routes are not advertised to router B
More information about the juniper-nsp