Danny McPherson wrote:
Again, I think you're missing the application wrt it residing on the trib side of the ADM -- to protect against router failures -- continuing to use the same network portion (i.e. the expensive portion) of the connection. ... Perhaps in your experience, though I can argue quite the contrary, especially when your company owns the the transmission facilities. Though again, I was referring primarily to local protection against router failure on the trib side of the ADM.
That's an interesting reply, for two reasons. I doubt many of us participating here own the transmission facilities. Virtually every router I've installed, even "ancient" NetBlazers and Ascends sitting out at the customer sites, has been stable for years without interruption. OTOH, links fail often, in ice storms, in rain, on windy days, even for no known reason at all! The windy day one perplexed us for some time, as the cable was supposedly underground. Then, I followed the cable for 40 miles, and found that they'd run it over creeks, one pole up and down again, instead of the extra expense of drilling under, and the lines were heavy with kudzu. Heck, I've got a frame circuit that fails and resyncs half a dozen times every evening, between 8 and 11 pm local. It's fine all day. We've replaced almost every component on both ends, and the RBOC refuses to believe that it's their problem. Your experience leasing lines from RBOCs other than BellSouth and Ameritech must be vastly better? Now, in my experience, when routers _do_ fail, usually soon after upgrading the software, APS won't help at all. The card is down, too. IP has to route around the problem. Maybe this is some new use of the term "router"? WSimpson@UMich.edu Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32