On Fri, Jun 01, 2018 at 09:37:56AM +0200, Olivier Benghozi wrote:
>
> > Le 1 juin 2018 à 05:05, Arvin Gan a écrit :
> >
> > I also notice the explanation from Cisco is all redistributed route are
> > INCOMPLETE. What's your opinion ?
That it does nor really matter.
> And on Juniper side, all
On Fri, Jun 01, 2018 at 09:39:04AM +0200, Olivier Benghozi wrote:
> But as a mandatory attribute, how can it be conceptually allowed to remove
> this attribute between BGP and BGP ?
Most attributes can be defined and undefined in configurable filters,
regardless of their meaning. After export fil
But as a mandatory attribute, how can it be conceptually allowed to remove this
attribute between BGP and BGP ?
> Le 31 mai 2018 à 16:10, Ondrej Zajicek a écrit :
>
> If the route is from BGP but bgp_origin attribute was removed by filters ->
> use ORIGIN_INCOMPLETE.
And on Juniper side, all redistributed route are IGP :P
Which is probably smart, since BGP origin attribute is an oldie created for
compatibility with EGP, and that should have since been killed a long time ago,
so everything as IGP makes sense (to basically remove origin from the best
route cho
