* Olivier Benghozi [2018-05-29 18:38]:
> I guess you have an explicit match for those routes in your VRF
> export policy for the downstream VRF instance ?
I don't know what you mean by "explicit match" exactly, but we have an
vrf-export policy that matches these routes.
Regards
Sebastian
--
G
I guess you have an explicit match for those routes in your VRF export policy
for the downstream VRF instance ?
> On 29 may 2018 at 11:15, Sebastian Wiesinger wrote :
> b) with advertise-from-main-vpn-tables
>
> [Hub instance] -> [Downstream hub instance] --> [bgp.l3vpn.0] -> MP-BGP
> neig
> Of Sebastian Wiesinger
> Sent: Tuesday, May 29, 2018 10:15 AM
>
> * Olivier Benghozi [2018-02-15 10:33]:
> > Hi Sebastian,
> >
> > This is an old workaround by the way.
>
> > Simpler workaround: use advertise-from-main-vpn-tables knob available
> > since 12.3 (required if you have NSR anyway):
Hi,
On 29.05.2018 11:15, Sebastian Wiesinger wrote:
So, I'm still stuck on this.
When using 'advertise-from-main-vpn-tables' Hub&Spoke VRFs with a
downstream hub[1] break.
In my mind the problem is that the downstream hub instance does not
advertise the hub routes to the bgp.l3vpn.0 table. Rou
* Olivier Benghozi [2018-02-15 10:33]:
> Hi Sebastian,
>
> This is an old workaround by the way.
> Simpler workaround: use advertise-from-main-vpn-tables knob
> available since 12.3 (required if you have NSR anyway):
So, I'm still stuck on this.
When using 'advertise-from-main-vpn-tables' Hub&
5 matches
Mail list logo
