Cigarette Takes Down Internet2 Network

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
A fire started by a homeless man knocked out service between Boston and New York on the experimental Internet2 network Tuesday night. The whole network, brought down by a cigarette. Wow.

Looks like all our circuits between Boston and New York are down due to a fire under the Longfellow Bridge in Boston. Level3 is telling us 1-2 days for service restoration right now, though they information could change as time progresses. We'll look into whether or not Level3 can re-route the Chicago to New York OC-192 through DC until the Boston path comes back.
 
Heh, default judgment "$5 billion in damages and eviction from under the bridge".

lol i dont know much about sueing and grabbin money from people but... how could they get even a minimal amount from a homeless guy? >.< come to think of it some homeless people do make more money than part time minimum wage people in my area.
 
lol i dont know much about sueing and grabbin money from people but... how could they get even a minimal amount from a homeless guy? >.< come to think of it some homeless people do make more money than part time minimum wage people in my area.

Make the guy do community service for the rest of his life.
 
Instead of blaming and suing the homeless guy, I would rather sue and fire whoever was in charge of the infrastructure... this is a bad step for the internet2 infrastructure. Horrible placement of an OC-192.


Heck, last week that bridge in SF burned down due to a tanker that got caught fire underneath it.
 
I'm gonna estimate 3 hours before someone blames cigarettes and tobacco companies for this whole caper.
 
No, it was clearly caused by video games that the homeless man had been playing on a stolen laptop...that still had some battery power left. Improved his cigarette-flicking aim while training him to flick calmly yet relentlessly.
 
No, it was clearly caused by video games that the homeless man had been playing on a stolen laptop...that still had some battery power left. Improved his cigarette-flicking aim while training him to flick calmly yet relentlessly.

i agree with that statement 120%
 
Instead of blaming and suing the homeless guy, I would rather sue and fire whoever was in charge of the infrastructure... this is a bad step for the internet2 infrastructure. Horrible placement of an OC-192

Hmm... Odd. Last time I remember, the "internet2" wasnt a physical network, and never was. Is there some reason why people insist on calling any projects that these people are involved with, the "internet2"?

http://www.internet2.edu/about/

"Internet2 is the foremost U.S. advanced networking consortium. Led by the research and education community since 1996, Internet2 promotes the missions of its members by providing both leading-edge network capabilities and unique partnership opportunities that together facilitate the development, deployment and use of revolutionary Internet technologies."

http://www.google.com/search?hl=en&defl=en&q=define:CONSORTIUM&sa=X&oi=glossary_definition&ct=title

"Definitions of CONSORTIUM on the Web: A coalition of organizations, such as banks and corporations, set up to fund ventures requiring large capital resources"
 
at no point did inet2 go offline. They simply had to reroute the traffic around that one broken link. Traffic was still able to get through using a different route. That link did go down but not the entire inet2. Please correct your misleading article title..and you all may want to do some research into how large scale WANS like this are designed. Barring some national catastrophe inet2 was never in danger of going dark due to one fiber failure.
 
http://i2net.blogspot.com/2007/05/boston-circuits-update.html



The backbone links have dual (and in many cases triple) redundancy. Most of the permutations of the story have made it sound like the whole network was down. Not the case, of course. At no point, did we lose routing capability out of our New York node.

SONET-based protection of OC-192 circuits on the long-haul is extremely expensive and rare. Every national backbone network that I know of uses individual unprotected lambdas for their long-haul circuits and rely on the diverse paths between cities to route around problems. That's what happened here. New York traffic was routed down through Washington DC. Everything worked perfectly.

Now, when I said we were working on routing the backbone circuit down to Washington DC, I was talking about at the optical level. Th DWDM lambda between Chicago and New York goes through Cleveland, up to Boston and down to New York. Re-routing the circuit through Cleveland, down to DC and up to New York would give us interface redundancy on the routers, but would obviously collapse the two backbone paths between Chicago and New York together onto the same fiber path. That's one reason why it wasn't heavily attempted. If we were in a situation where the network were really going to be down for days, we may have attempted it. It would only have provided us protection from things like failing linecards and interfaces, but that's useful in and of itself.

The bottom line is that it wasn't as bad as all the cloned news articles made it out to sound. Internet2 didn't go down. One link went down, in a fashion that's not very typical. Backbone outages occur all the time and there's no reason to make a fuss about this one other than the fact that the story behind the outage was kind of interesting.
5/04/2007 02:39:00 AM
 
Hmm... Odd. Last time I remember, the "internet2" wasnt a physical network, and never was. Is there some reason why people insist on calling any projects that these people are involved with, the "internet2"?

I think internet2 in it's physical manifestation is ipv6 traffic hardware. I'd guess thats what's meant :confused:
 
Back
Top