[77502] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Please Check Filters - BOGON Filtering IP Space 72.14.128.0/19

daemon@ATHENA.MIT.EDU (Joel Aelwyn)
Fri Jan 21 14:27:26 2005

Date: Fri, 21 Jan 2005 12:26:57 -0700
From: Joel Aelwyn <lucifer@lightbearer.com>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.58.0501210859430.19902@efes.iucc.ac.il>
Errors-To: owner-nanog-outgoing@merit.edu



--q7oacCJraRPxsh4K
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 21, 2005 at 09:01:13AM +0200, Hank Nussbacher wrote:
>=20
> On Thu, 20 Jan 2005, James Laszko wrote:
>=20
> > Well, if the router CAN run BGP, the feed from Cymru is only about 84
> > prefixes - not a lot of memory tied up there, is there?
>=20
> I am *not* talking about the leaf - rather the core.  I am curious what
> resources are needed to manage 200K BGP peers other than 200K IP
> addresses.  Is there an IOS limit on the number of BGP peers?  Memory?
>=20
> -Hank

I can't comment on that, but it strikes me that it might be a fairly
non-optimal solution, for the simple reason that we're talking about a
small, low-delta, highly-distributed feed where session state is going
to eat most of your CPU and memory, but any *one* session is unlikely to
really need much except keepalives. And, of course, no need to actually
route anything.

Sounds like an excellent thing to throw commodity (OK, probably rackmount,
but still) PC hardware at (potentially in clusters, I haven't looked into
what the memory/CPU load of sessions boil down to on recent versions of
BGP-capable software that runs on such).
--=20
***************************************************************************
Joel Aelwyn                          System Administrator - lightbearer.com
lucifer@lightbearer.com              http://users.lightbearer.com/lucifer/

--q7oacCJraRPxsh4K
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB8VeB13sEBdj5qMURAtaGAJ9GLsOQK/Q+MbYny2/ssdvUtcUBXACgquFF
oJXLKYKKKegP502TQa9xSvA=
=SesG
-----END PGP SIGNATURE-----

--q7oacCJraRPxsh4K--

home help back first fref pref prev next nref lref last post