|
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]
|
|
Outage
Anyone who has run a large network long enough knows that the source of this could be at least any of these reasons: A) vendor software bug or hardware related issue, B) human error either fat finger or misconfigured/poorly configured routers/protocols, or managing the network in such a way that memory resources, for example, were not properly managed so that instabilities could creep in, or C) another vendor injecting malformed BGP information (or whatever else), which happened several years ago with a major provider, where again, Cisco was blamed, but their only fault was not coding BGP to account for flaws in the code of another vendor. It's hard to say whether the real details of this outage will get past the few who know the details intimately or not. Everyone will most certainly spin it to their advantage though. Just don't assume that the title of the article is complete or accurate. DISCLAIMER: Not a cisco employee, stockholder, etc. Just a passerby...