Being somewhat of a paranoid body, I have all my BGP peers currently set for max-prefix of 75000. On Friday, my Sprint peer (usually around 67k) exceeded that number and we stopped the session. This in itself is not a big deal, but looking at http://www.telstra.net/ops/bgptable.html I notice that they suck a large influx in the table at a similar time.. Did anyone else see something similar? If so, what peers did you see this from? Here is the log for my incident in question.. Dec 10 15:03:54 No. of prefix received from SPRINTROUTER reaches 67117, max 75000 Dec 10 15:31:16 No. of prefix received from SPRINTROUTER reaches 67137, max 75000 Dec 10 15:50:50 No. of prefix received from SPRINTROUTER reaches 67133, max 75000 Dec 10 15:54:10 No. of prefix received from SPRINTROUTER reaches 67100, max 75000 Dec 10 15:54:40 No. of prefix received from SPRINTROUTER reaches 67102, max 75000 Dec 10 15:55:10 No. of prefix received from SPRINTROUTER reaches 67099, max 75000 Dec 10 16:27:34 No. of prefix received from SPRINTROUTER reaches 67024, max 75000 Dec 10 16:42:38 No. of prefix received from SPRINTROUTER reaches 67024, max 75000 Dec 10 16:45:53 No. of prefix received from SPRINTROUTER reaches 67068, max 75000 Dec 10 17:18:58 No. of prefix received from SPRINTROUTER reaches 67078, max 75000 Dec 10 17:39:35 No. of prefix received from SPRINTROUTER reaches 73712, max 75000 Dec 10 17:39:39 No. of prefix received from SPRINTROUTER: 75001 exceed limit 75000 My session was disabled so I'm not sure how much bigger their table got. The only reason I bring this up here instead of directly to Sprint is that the data on the Telestra page appears to point the finger at this being a multi-provider incident, and I haven't heard anything on this list or others regarding the situation.. TIA, -- Tim -------------------------------------------------- * Timothy M. Wolfe, Chief Network Engineer * * ClipperNet Corporation / It's a wireless world * * tim@clipper.net 800.338.2629 x 402 * * Sufficient for today = Inadequate for tomorrow * --------------------------------------------------
On Mon, Dec 13, 1999 at 08:59:59AM -0800, Tim Wolfe wrote:
Being somewhat of a paranoid body, I have all my BGP peers currently set for max-prefix of 75000. On Friday, my Sprint peer (usually around 67k) exceeded that number and we stopped the session. This in itself is not a big deal, but looking at http://www.telstra.net/ops/bgptable.html I notice that they suck a large influx in the table at a similar time.. Did anyone else see something similar? If so, what peers did you see this from? Here is the log for my incident in question.. [snip] Dec 10 17:39:39 No. of prefix received from SPRINTROUTER: 75001 exceed limit 75000
My session was disabled so I'm not sure how much bigger their table got. The only reason I bring this up here instead of directly to Sprint is that the data on the Telestra page appears to point the finger at this being a multi-provider incident, and I haven't heard anything on this list or others regarding the situation..
None of our full routing sessions show this ... x.x.x.x 4 1 1288729 35709 3747858 0 0 1w4d 66566 x.x.x.x 4 1239 1392203 36716 3747606 0 0 1w1d 66970 x.x.x.x 4 3561 91930 1560 392057 0 0 06:19:18 66647 /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
On Mon, 13 Dec 1999, Jesper Skriver wrote:
None of our full routing sessions show this ...
x.x.x.x 4 1 1288729 35709 3747858 0 0 1w4d 66566 x.x.x.x 4 1239 1392203 36716 3747606 0 0 1w1d 66970 x.x.x.x 4 3561 91930 1560 392057 0 0 06:19:18 66647
/Jesper
Sorry, I didn't explain that as well as I might have. As of today when I reset the bgp session to AS1239, all is well, table is back to around 67K. However, for at least some period Friday night, Sprint (and possibly others) had an ~10K increase in their global routing tables. That is what I am trying to find out about. -- Tim -------------------------------------------------- * Timothy M. Wolfe, Chief Network Engineer * * ClipperNet Corporation / It's a wireless world * * tim@clipper.net 800.338.2629 x 402 * * Sufficient for today = Inadequate for tomorrow * --------------------------------------------------
participants (2)
-
Jesper Skriver -
Tim Wolfe