If you are concerned about fixing it, and the outage you will or are causing to your customers, perhaps you ought to think about discussing why this is so with either your architect/engineering group or perhaps with your upper management/finance group. One would hope that the major backbone players would at least engineer thier backbone to survive or be able to recover quickly from a single failure event for equipment that has shown that tendancy. We all know routers don't have the greatest reliability standards. Backbones who have overloaded routers either are working under a very risky business model, or they have not desinged and engineered thier network correctly? I suppose in some small cases with lower performance routers, something like this could possibly sneak up on you, however, in the statistically aggregated traffic models of a larger backbone, this shouldn't be able to sneak up on you. Just my plug for intelligent backbone engineering. I learned the hard way. Chris A. Icide Nap.Net, L.L.C. ---------- From: Alex P. Rudnev[SMTP:alex@Relcom.EU.net] Sent: Tuesday, July 01, 1997 12:02 PM To: Wayne Bouchard Cc: Deepak Jain; spork@inch.com; jbeck@connectnet.com; nanog@merit.edu Subject: Re: Plethora of UUnet outages and instabilities On Mon, 30 Jun 1997, Wayne Bouchard wrote:

Thats my point. It often ISN'T easy. For example, say you've got a 7505 in one spot and find its getting killed. You can't put an rsp4 in a 7505. You've got to replace the router. Anyone got any spare 7507s or 7513s lying around? Chances are that if they do, its 2 or 3. It's often not easy to FIX. But it's not hard to _notify the customers_. And to work around by some way (temporary).