[c-nsp] Memory and Flash requeriments for BGP peering router

David Coulson david at davidcoulson.net
Thu Jun 22 23:12:11 EDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

omar parihuana wrote:
> Currently, I'm working in a small Wireless Internet Service Provider
> that serves about 500 customer, all with static routes. Our ISP,
> route by static routing the customer IPs (16 class-C no contiguous)
> too. We're going to implement BGP peering with our ISP for
> multihommed. Actually, we have a 7513 with 64RAM and 16 Flash, and the
> CPU in high traffic is about 70%. (at 45Mbps -DS3)

What CPU are you running? That seems high for 45Meg on an RSP4. Check
out my discussion from yesterday to see if you're running dCEF on it all.

> Will be necessary more Memory -RAM/Flash, aditional cards (VIPs)?.
> Which will be the minimum requriments for BGP peering for multihommed?

Are you peering to two different ISPs, or just doing two pipes into one?
First case, you'll want 256Mb on your RSP and 128Mb on your VIPs. Second
case, why even use BGP at all when you can use static routes and CEF
load balancing across it, or you can use BGP and just pull in a default
and use multipath to load balance two routes.

Need more info on your hardware and your config to get a good idea of
what you'll need to change.

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEm1wLTIgPQWnLowkRAk1/AJ0Vx7YCvFc4OxdalDxVqFsYjtPZQwCgl11g
+d44b3d+XFUjXiKyasLExHg=
=OqnK
-----END PGP SIGNATURE-----


More information about the cisco-nsp mailing list