[j-nsp] Spine & leaf

[Payam Chychi]

Id also keep with L3/BGP over L2 or even L3/OSPF for DC. For ENT, you can
get away with L2 if you need and want to stay away from more advance
L3VPN/XVLAN
Really depends on what you are trying to do... however, most cases L3/BGP
will be a great start point and a friend =)

On Mon, Jun 25, 2018 at 9:04 AM Aaron Gould <aaron1 at gvtc.com> wrote:

> I'm not sure of the overall context of the question but I will say that,
> over the last decade at least, BGP in general has evolved into the
> multiprotocol/multi-address family mechanism for doing many things of
> virtual networking internal to an SP network and even some, what I would
> call, progressive enterprise networks.
>
> An IGP like Ospf is definitely still used "underneath" those SP/ENT clouds
> in what would be known as the core network
>
>
> Aaron
>
> > On Jun 25, 2018, at 10:50 AM, Chris Boyd <cboyd at gizmopartners.com>
> wrote:
> >
> >
> >
> >> On Jun 23, 2018, at 10:56 PM, joel jaeggli <joelja at bogus.com> wrote:
> >>
> >> Personally I'm kind of done with large L2s so I would  probably just use
> >> ebgp with a private asn per server and eschew all these l2 topologies.
> >
> > Other than the administrative controls of mature route filtering tools
> in BGP, I’m curious why people choose BGP over OSPF for route injection.
> >
> > —Chris
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


-- 
Payam Tarverdyan Chychi
Network Security Specialist / Network Engineer