Latest software headlines from Network World:
Kernel developers, Wall Street to come together
Zoho launches e-mail app with offline, mobile access
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
THAT WHY WE USE NORTEL
I work for Cisco and in the past I have worked in the Cisco TAC supporing routing protocols. That does not make me an expert but I'm not totaly clueless either.
I am not privy to what caused the outage. From the description I assume that it is likely that it was a routing protocol convergence issue.
This could have been caused by a bug or perhaps a mistake in configuration or poor design or a combination of the above.
I have seen large outages caused by configuration issues. What happens is a huge number of routes and alternative paths are dumped into the forwarding table and routers run of memory causing more mayhem and the whole network melts.
I am not saying that was the cause of this outage of course but until the cause is determined I would ask that people hesitate before afixing blame.