Earliar this afternoon, approx. 2:45pm est, a multihomed customer of ours introduced thousands of routes to us as being behind them. Needless to say, this cause some major routing instability. We immediately shut that connection and contacted the customer. We are in the process of switching from AS Path filters to prefix filters and this customer was still on the AS Path filter. Just thought you folks might like to know what happened. Sorry for any problems that this created. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Harold Willison AGIS Network Engineering | * Network Engineer 313-730-5151 * | News Admin. 313-730-1130 | | news@agis.net 24 hours a day, 7 days a week | * harold@agis.net noc@agis.net * | <bold><italic> <underline>http://www.agis.net</underline></italic></bold> |<bold><italic> </italic></bold>\*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*/
On Wed, 12 Nov 1997, Harold Willison wrote:
Earliar this afternoon, approx. 2:45pm est, a multihomed customer of ours introduced
thousands of routes to us as being behind them. Needless to say, this cause some major
routing instability. We immediately shut that connection and contacted the customer.
Yes it is true that we announced out incorrect routes through AGIS. No, AGIS did not shut off the connection. I noticed the problem within a few seconds,because I was on the offending router at the time, and fixed the problem. My connection to AGIS was not stopped until I reset it for the new filter some time later. The only one of my connections to have this problem was AGIS. The problem was caused by an internal routing protocol that decided it wanted to be God. I did not recieve a call from AGIS until over an hour after I had already fixed the problem. I have patched the broken filter on our routers so this won't happen again.
We are in the process of switching from AS Path filters to prefix filters and this customer
was still on the AS Path filter.
No comment. I requested this when I turned up the connection.
Mark E Larson Senior Engineer
On Wed, 12 Nov 1997, Mark E. Larson wrote:
The only one of my connections to have this problem was AGIS. The problem was caused by an internal routing protocol that decided it wanted to be God.
Thou shalt not redistribute into BGP sayeth the Lord... ;) +------------------- H U R R I C A N E - E L E C T R I C -------------------+ | Mike Leber Direct Internet Connections Voice 408 282 1540 | | Hurricane Electric Web Hosting & Co-location Fax 408 971 3340 | | mleber@he.net http://www.he.net | +---------------------------------------------------------------------------+
participants (4)
-
Forrest W. Christian -
Harold Willison -
Mark E. Larson -
Mike Leber