[c-nsp] Redist "BGP" routes to "other" PE's (In same VRF)

Will Tardy will.tardy at vocus.com.au
Thu Jan 15 03:50:23 EST 2015

This might work: On the ASR9K try the "advertise-as-vpn" command in the vrf definition section, for the import/export to GRT. On 1Ks, use a VASI pair to advertise via a BGP peering session.

> On 11 Jan 2015, at 11:19 pm, Oliver Boehmer (oboehmer) <oboehmer at cisco.com> wrote:
>> Hi Everyone,
>> I have a vrf (TEST), configured on 2 PE's...both learn each others
>> connected+static routes (redist connnected, redist static), so that
>> portion is working fine...but I also have leaked the default route from
>> PE_A (That we receive  from an upstream provider), into the vrf
>> TEST....on PE_A, I can see the detault route in the VRF TEST, and also
>> GRT, and I can get to the Internet from an IP within the VRF....I have
>> "default-information originate" on PE_A for vrf TEST, but the default
>> route is not being propagated to PE_B...the default route is seen as type
>> "BGP" when I issue "sh ip route vr TEST/sh ip route vrf test
>>"....any suggestions on what is needed to redist this BGP route to
>> the other PE in the VRF?   i.e. under address family vrf TEST,
>> redistribute BGP xxx (with a route map to ensure only the default is
>> distributed to the other PE?)
> A PE which imports a route into a VRF (and importing from global is no
> exception) will not advertise this route via iBGP to other PEs. So you
> would need to configure the same import on PE_B too..
>    oli
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list