[177155] in North American Network Operators' Group
Re: MPLS VPN design - RR in forwarding path?
daemon@ATHENA.MIT.EDU (Mark Tinka)
Fri Jan 2 13:25:42 2015
X-Original-To: nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
To: nanog@nanog.org
Date: Fri, 2 Jan 2015 20:24:05 +0200
In-Reply-To: <CAPkb-7DQ2L5=fgmzgdY9d6n0P+HrPDAs2g=Ou=tON-MXCezD8w@mail.gmail.com>
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces@nanog.org
--nextPart1803421.82aQOzJlYS
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Thursday, January 01, 2015 11:37:25 PM Baldur Norddahl=20
wrote:
> Is there a good reason to use actual router hardware for
> the route reflector role?
Nope.
It used to be code maturity - but major vendors are=20
supporting service-grade code on VM's.
> Even a cheap server has more
> CPU and memory. If it is not in the forwarding path,
> this is a computing task - not a move packets at line
> speed task.
Agree.
> Are anyone using Bird, Quagga etc. for this?
Wish I could - to be honest, these don't give me enough=20
comfort for a production network.
We use Quagga on FreeBSD for Anycast-this-&-that - from that=20
experience, I'd not use it for backbone routing. YMMV.
Mark.
--nextPart1803421.82aQOzJlYS
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJUpuJFAAoJEGcZuYTeKm+G4bQP/0xwQp5U3QZ1Hwp8z9bMH31G
5fPSRrGAhwnSVuLViEO9V+EBK3/Qy79ooi6Gzg1XhXcE0QSSMnTy0ZuZGk+7/JbA
jWCANc8x5RkzTCVgJUFAKLJMO5t+3V48kCZs9afx5Wwk1T6rm9Gt73ZXiOJUbLEz
hV+qarMc8BaFwGbJEwcT8YvPVHhlh5d+NW5L1OPuoLSVRxiZC6WEloQJMdwC6HWs
WhTNrixoYG8ArwiR0H5EXkHr5ymPsWVwOa/j4vIxtzWx7EggTf/f4EOUv9lfh3ve
1SZUr/BCNy3aqhdSASdtA8NYBcpncE1KpGhe8YOGwEma63GQSvEDheglTFJ5Swit
weVHYcx+gDNb5naD52P8CKWly4Y9Yxv2+o29CG9ZZKLMLfEYlG7Enj940zNNVKA7
qSkJB5ywIOEV3fplXlzgEbkcsAlp4f5esAwQliSpWRUCv2U5ezyerujicsHf+RvL
Y8mCPzIUKKu7E+ScT3TZCMSKFHjSAwKvus6frqbmu9yb9OytduzcSvffe+COh4Z6
VMiSDqKF8ocaV7khc2/FWS2c7oLBO9FJZSc7CjUDgpr9w8V89ZriqwBXpCS/6Z90
eLhvwXUMduQHyMBTqFFhbhPGg7NhbzWQZuZciifeo2yYp7PV1TBD16HXc4RAwZkR
EZU469+G4HnkWchxZHMz
=RPGf
-----END PGP SIGNATURE-----
--nextPart1803421.82aQOzJlYS--
