Page 1 / 2   >   >>
Duh! 1/2/2019 | 4:16:16 PM
So many questions Well, that was clear as mud.

What exactly is a "third-party network management card" and what is an "invalid frame packet"? [I think I can guess] And how did a broadcast storm in a "secondary channel" (OTN General Communications Channel?) wipe out working paths?

That's the first few that came to mind.  Lots more where they came from.
Phil Harvey 1/2/2019 | 4:58:04 PM
Re: So many questions Hi, Duh!

Yes, CTL isn't going to directly call out the specific vendor product, sku or software provider. We'll find out at some point and report it.

I think the takeaway is that, as my colleague Ray put it, a company that manages networks for a living just had a massive network management problem that it couldn't find, didn't know how to fix, etc. 

That said, please keep the questions coming. We're hoping to have more to report in the next few days.

Keebler 1/2/2019 | 5:07:07 PM
Reminiscent of TARP storms of old The event reminds me of the TARP storms that plagued SONET networks when TARP was first introduced. TARP messages would replicate at the gateways to rings in both directions, circulate the ring, and get replicated again. Even with time-to-live settings, the amount of traffic quickly overwhelmed the systems and resulted in outages. It was hard to find and nontrivial to fix.

Sounds like those who forget history are doomed to repeat it. Or something along those lines.

Anyone taking bets yet on who the third party equipment vendor was this time?
Phil Harvey 1/2/2019 | 5:08:42 PM
Re: Reminiscent of TARP storms of old Good call back. Was that something on one of the old RBOC networks -- US West or SBC? 
Keebler 1/2/2019 | 5:12:46 PM
Re: Reminiscent of TARP storms of old It was definitely on an RBOC network. Around 1997 I believe. My memory isn't quite good enough to recall exactly which one, but maybe Ameritech? That could be completely off. I usually throw out the Ameritech name just to confuse the youngsters.
Phil Harvey 1/2/2019 | 5:17:01 PM
Re: Reminiscent of TARP storms of old That was even years before Verizon started hiring extra creepy white guys as their star pitchmen. 
brooks7 1/2/2019 | 5:37:45 PM
Re: Reminiscent of TARP storms of old The first thing I thought was...somebody still has x.25 in their oss network.


Phil Harvey 1/2/2019 | 5:56:05 PM
Re: Reminiscent of TARP storms of old And that (x.25) is a pre-IP networking way of getting switches to connect to OSS systems/carrier back offices?

If so, then there would be some kind of gateway sitting between the (presumably really old) switch and the IP network? 

brooks7 1/2/2019 | 7:14:36 PM
Re: Reminiscent of TARP storms of old That is correct Phil.  I recently looked at a network that had such gear still in place with an x,25 switch maker that went out of business 20 years ago or so.


Edit:  And yes it was used to connect to the systems for OSMINE.
Duh! 1/2/2019 | 10:49:57 PM
Re: Reminiscent of TARP storms of old X.25 is the absolutely last protocol suite I would ever associate with packet storms. Heavyweight flow control was one of it's main architectural principles.
Page 1 / 2   >   >>