nanog mailing list archives

Re: 1GE L3 aggregation


From: Baldur Norddahl <baldur.norddahl () gmail com>
Date: Thu, 16 Jun 2016 21:36:13 +0200

Hi

If I need to speak BGP with a customer that only has 1G I will simply make
a MPLS L2VPN to one of my edge routers. We use the ZTE 5952E switch with
48x 1G plus 4x 10G for the L2VPN end point. If that is not enough the ZTE
8900 platform will provide a ton of ports that can do MPLS.

The tunnel is automatically redundant and will promote link down events, so
there is not really any downside to doing it this way on low bandwidth
peers.

Regards

Baldur
Den 16. jun. 2016 09.52 skrev "Saku Ytti" <saku () ytti fi>:

Hey,

I've been bit poking around trying to find reasonable option for 1GE
L3 full BGP table aggregator. It seems vendors are mostly pushing
Satellite/Fusion for this application.

I don't really like the added complexity and tight coupling
Satellite/Fusion forces me. I'd prefer standards based routing
redundancy to reduce impact of defects.

ASR9001 and MX104 are not an options, due to control-plane scale. New
boxes in vendor pipeline are completely ignoring 1GE.

I've casually talked with other people, and it seems I'm not really
alone here. My dream box would be 96xSFP + 2xQSFP28, with pretty much
full edge features (BGP, LDP, ISIS, +1M FIB, +5M RIB, per-interface
VLANs, ipfix or sflow, at least per-port QoS with shaper, martini
pseudowires).

With tinfoil hat tightly fit on my head, I wonder why vendors are
ignoring 1GE? Are business cases entirely driven now by Amazon,
Google, Facebook and the likes? Are SP volumes so insignificant in
comparison it does not make sense to produce boxes for them?
Heck even 10GE is starting to become problematic, if your application
is anything else than DC, because you can't choose arbitrary optics.

--
  ++ytti


Current thread: