[195202] in North American Network Operators' Group
Re: EdgeRouter Infinity as medium-sized "IXP Peering Router"?
daemon@ATHENA.MIT.EDU (Hugo Slabbert)
Mon Jul 3 22:28:34 2017
X-Original-To: nanog@nanog.org
Date: Mon, 3 Jul 2017 19:28:30 -0700
From: Hugo Slabbert <hugo@slabnet.com>
To: Josh Reynolds <josh@kyneticwifi.com>
In-Reply-To: <CAC6=tfZEizjKBfsn5kSoASHGRBTOuLcgnEQHJcnCnAWZ3Ob_ew@mail.gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--gDGSpKKIBgtShtf+
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon 2017-Jul-03 19:26:17 -0500, Josh Reynolds <josh@kyneticwifi.com> wro=
te:
>On Jul 3, 2017 7:23 PM, "Josh Reynolds" <josh@kyneticwifi.com> wrote:
>
>> Specs...
>>
>>
>> - MIPS64 16 Core 1.8 GHz
>> - 16 GB DDR4 RAM
>> - 8 MB NOR Flash 4 GB eMMC NAND Flash
>> - Data Ports: (1) RJ45 Serial Port, (8) SFP+ Ports (1) RJ45 Gigabit
>> Ethernet Port
>> - 2 hotswap power supplies
>>
>>
>> No LACP. ECMP is currently broken. MPLS/VPLS is currently broken and not
>> done in hardware - this may eventually change. As far as the other stuff,
>> "telemetry" etc - no.
>>
>> As far as BGP crunching, plenty of routes, etc - it would easily and
>> happily be fine with that.
>>
>> As far as automation, it's a JunOS-like CLI originally based on vyatta,
>> which AT&T now owns - and one of the main reasons is it's scriptability,
>> use of Ansible and other tools right on the device, python, etc.
Technically I believe it's based on VyOS rather than Vyatta. Same base,=20
but just delineating that VyOS is open source and I don't believe AT&T=20
wields any control over it.
>>
>> - Josh
>>
--=20
Hugo Slabbert | email, xmpp/jabber: hugo@slabnet.com
pgp key: B178313E | also on Signal
>> On Jul 3, 2017 2:09 PM, "Job Snijders" <job@instituut.net> wrote:
>>
>>> 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 a=
nd
>>> 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, *flo=
w,
>>> and exposes some telemetry via SNMP.
>>>
>>> Any note sharing would be appreciated!
>>>
>>> Kind regards,
>>>
>>> Job
>>>
>>
--gDGSpKKIBgtShtf+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBCgAGBQJZWv1OAAoJEFsnhBAb2KmAgCcP+wTNTDFR+cvzFAJ9srcWHR1F
bET9aEThILm+gdYvMgct7Joqj4TEc3YSsdNffSBaq+TlOinEYHbfzdhnjvMpPUWM
/hsMo+xNKlfE8/878Bwy7snAsYgY6ancNSkEH4jLaylXhEFnsqojILPUCiY9ibwQ
LnuKN33ETUbKHd9HpWmNlzzr9czfe0i9Rc6Mlj8uu3gZ+G1Lh6atXe2ziPxLnCt1
zcRcQU6+Ol0xmq/0xL7NzUeZJlDpJ2qcc6FhoVFC+Uwx/2qoh0XPY13BUZZUkYcC
kZ3pPgLBPNbK159dYY9OnEXt29nuep5MGczK46cUWN3L5hVo1xOhZrtThSpThVmv
5WRbmia04Ib9/a5e1l30p50m5YKvEINnoeHUE5QAR01ZhgpJzWxP7sgvlMVFMZk3
pSXuOrmFc3aLQBkr98dLCSfTdRgGxSM+nXrt7MvlM1FJ6XQP+lKAnjQlB7RLGh+x
5NxxOPqVudqAShLmlcUS96ALm+17AI20NUSgNXX5HwUxhgTwDWaAzisEUhN5aYg6
0FFUHhnp6Id5U4E52vrFO8OmmK9/uP5xDbMJ7aZmeOMkNZqprG+32K0Yzw8fZH1E
+hPw9q9hhSgU5nt0bWyYgXfxsyH/QIU1ns2wPiXaQITeI+8oWnsmEbmBKWUdUzCc
Ny8r6UMGyj3fsGRoHxZH
=fI5+
-----END PGP SIGNATURE-----
--gDGSpKKIBgtShtf+--
