EdgeRouter Infinity as medium-sized "IXP Peering Router"?

Jared Geiger jared at compuwizz.net
Tue Jul 4 20:43:43 CST 2017


The RAM is upgradeable but it can support quite a few full tables out of
the box. The routing software under the hood got upgraded by Ubiquiti to
ZebOS https://www.ipinfusion.com/products/zebos/ from the VyOS code.

There is a Cavium bug regarding UDP packets though that can be nasty if you
hit it.
https://community.ubnt.com/t5/EdgeMAX/UDP-packet-loss-with-EdgeRouter-Lite/m-p/1343012

Even though the thread starts by talking about the Lite, all of the Cavium
EdgeRouters  currently have the problem. The beta work around is to
restrict packet forwarding to only use one of the CPU cores. This is with
or without hardware offloading enabled. Hopefully Cavium will have a real
fix soon. I have two of these I'm itching to put into production once the
bugs are worked out.

On Mon, Jul 3, 2017 at 8:28 PM, Josh Reynolds <josh at kyneticwifi.com> wrote:

> I kinda feel the same way.  I wish FRR was a big more mature at this
> point though.
>
> On Mon, Jul 3, 2017 at 10:21 PM, Baldur Norddahl
> <baldur.norddahl at gmail.com> wrote:
> > Why not use a Linux or BSD computer for this? It is cheap and you know
> > exactly what you are getting. It will forward 10 gig at line rate at
> least
> > for normal traffic.
> >
> > Regards
> >
> > Baldur
> >
> > Den 3. jul. 2017 21.08 skrev "Job Snijders" <job at instituut.net>:
> >
> >> Dear NANOG,
> >>
> >> Some friends of mine are operating a nonprofit (on shoe string) and
> looking
> >> to connect some CDN caches to an IX fabric. A BGP speaking device is
> needed
> >> between the caches and the BGP peers connected to the fabric. The BGP
> >> speaker is needed to present the peers on the IX with a unified view of
> the
> >> assemblage of CDN nodes.
> >>
> >> I was wondering whether anyone was experience with the "EdgeRouter
> Infinity
> >> XG" device, specifically in the role of a simple peering router for a
> >> couple of tens of thousands of routes. (I'd point default to the left
> and
> >> take just the on-net routes on the right to reduce the table size
> >> requirement).
> >>
> >> I hope the device can do at least 2xLACP trunks, has a sizable FIB, is
> >> automatable (supports idempotency), can forward IMIX at line-rate,
> *flow,
> >> and exposes some telemetry via SNMP.
> >>
> >> Any note sharing would be appreciated!
> >>
> >> Kind regards,
> >>
> >> Job
> >>
>


More information about the NANOG mailing list