One of my old upstreams which we still run a little traffic through only has 64 Megs of memory in a 7202, and it seems like it is running out of memory with full tables. I have not been on the router to verify, but I am receiving 88473 prefixes from them. Anybody else seeing this? Mark -- Mark Segal Director, Network Engineering Axxent Corp. Tel: (416)907-2858
Saw more than that from one of the big boys today. %BGP-4-MAXPFX: Number of unicast prefixes received from xxx.xxx.xxx.xxx reaches 96857 "neighbor xxx.xxx.xxx.xxx maximim-prefix" is your friend... ;-) scott On Fri, 29 Sep 2000, Segal, Mark wrote:
One of my old upstreams which we still run a little traffic through only has 64 Megs of memory in a 7202, and it seems like it is running out of memory with full tables. I have not been on the router to verify, but I am receiving 88473 prefixes from them.
Anybody else seeing this?
Mark
-- Mark Segal Director, Network Engineering Axxent Corp. Tel: (416)907-2858
On Fri, 29 Sep 2000, scott w wrote:
Saw more than that from one of the big boys today. %BGP-4-MAXPFX: Number of unicast prefixes received from xxx.xxx.xxx.xxx reaches 96857
sprint does this to us every few weeks. never seen it from any of our other links.
"neighbor xxx.xxx.xxx.xxx maximim-prefix" is your friend... ;-)
maximum-prefix sucks because it kills your session, but sucks less than killing the entire bgp router process. i wish there was an option to simply drop announcements over the limit rather than killing the session. -Dan
The session wasn't lost. Set it to warn you well before killing the session. scott ps. It wasn't Sprint... On Fri, 29 Sep 2000, Dan Hollis wrote:
On Fri, 29 Sep 2000, scott w wrote:
Saw more than that from one of the big boys today. %BGP-4-MAXPFX: Number of unicast prefixes received from xxx.xxx.xxx.xxx reaches 96857
sprint does this to us every few weeks. never seen it from any of our other links.
"neighbor xxx.xxx.xxx.xxx maximim-prefix" is your friend... ;-)
maximum-prefix sucks because it kills your session, but sucks less than killing the entire bgp router process. i wish there was an option to simply drop announcements over the limit rather than killing the session.
-Dan
Dan Hollis writes:
On Fri, 29 Sep 2000, scott w wrote:
"neighbor xxx.xxx.xxx.xxx maximim-prefix" is your friend... ;-)
maximum-prefix sucks because it kills your session, but sucks less than killing the entire bgp router process. i wish there was an option to simply drop announcements over the limit rather than killing the session.
But would that be worse? ``maximum-prefix n p warning-only'' along with a log analyzer that recognizes the warning, are perhaps a better pair of friends.
participants (4)
-
Dan Hollis -
Mark Milhollan - Franklin Employee -
scott w -
Segal, Mark