North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
re: AGIS Route Flaps Interrupting its Peering?
Depends on which report your talking about...there were two... one that was digex internal and the one gordon sent around... The digex internal one did have a number of flaws and many conclusions that were plain false. The one gordon sent around about having things unreachable inside agis...well thats true...at the time we were having lots of problems with unstable prefixes from agis....as it turns out this may have been a netedge problem with the agis side...(no fault of agis at all) While agis keeps saying that we never contacted them about this problem thats true...We dont get proactive with other providers that have flapping problems..(and that at the time was all that our noc thought it was) Technical problem now fixed...things are back to relative abnormal. Any problems with that Kent? Ed PS. Is it just me or does gordon remind you of fire marshal bill...."Hey letme show ya something" POOF - ---------- Forwarded message ---------- Date: Thu, 4 Jul 1996 14:30:32 -0400 (EDT) From: Mark Kent <[email protected]> To: [email protected], [email protected], [email protected] Subject: re: AGIS Route Flaps Interrupting its Peering? Regarding an internal Digex report of AGIS instability, Gordon Cook asks of an inappropriate audience: >> does anyone know what happened? The Digex report is seriously flawed. Ed Kern of Digex has told us that he is looking into how the conclusions in that report were reached. However, I'm sure that Kern didn't think that he would have to share his findings with nanog, inet-access, and agislist... - -mark ------- end ------- - - - - - - - - - - - - - - - - -