How does a single network card emitting bad packets effect other sites? > investigations into the logs, including packet captures, was occurring in tandem, which ultimately identified a suspected card issue in Denver, CO. Field Operations were dispatched to remove the card. Once removed, it did not appear there had been significant improvement; however, the logs were further scrutinized .. to identify that the source…
CenturyLink 911 outage was caused by a single network card sending bad packets
21–30 of 166 posts
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#22Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#23Earlier quoted context omitted.
Packet storms are real, and they are tricky to troubleshoot. Modern tech has made it less likely to happen, but that just means when it does happen noone suspects it.
I used to look after an office location that had three racks with older generation HP Procurve switches. About once every 4-6 months, the whole lot would go haywire and the only way to settle down the network was to switch them all off, wait, and then power up again. We never did track down the root cause and could never make it happen on demand,
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#24Summary: the specific Symantec disk imaging software was partly loaded via PXE boot, and that machine started to flood the network with bad packets. Switching the computer off for a few seconds didn't help, since the SMPS capacitors still held current - enough to keep the card alive and for the sysadmins to not suspect that computer!
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#25Someone was displeased - https://fuckingcenturylink.com/ I'd love to see an in-depth technical analysis of the outage.
This is probably the same guy from fuckinglevel3.com. We used level3 for years and sent each other that link almost daily. I guess he had to update after CL bought them :] Don't expect a technical report from CL/L3. We had 60+ mpls/vpls circuits from them and all our reports were very high level. Source: am neteng
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#26Someone was displeased - https://fuckingcenturylink.com/ I'd love to see an in-depth technical analysis of the outage.
This is probably the same guy from fuckinglevel3.com. We used level3 for years and sent each other that link almost daily. I guess he had to update after CL bought them :] Don't expect a technical report from CL/L3. We had 60+ mpls/vpls circuits from them and all our reports were very high level. Source: am neteng
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#27The descriptions so far about this problem are either at 30000 foot vagueness or they're in technical shorthand that just assumes the audience is 100% pro network engineers. Don't "bad packets" get dropped at the first switch? Isn't that one of the main benefits of packet based switching? Was this even an ethernet packet or something else like an optical transport protocol (eg OTN)?
Since checksums are hardware accelerated, the invalid packet probably had a valid checksum applied to it.
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#28How does a single network card emitting bad packets effect other sites? > investigations into the logs, including packet captures, was occurring in tandem, which ultimately identified a suspected card issue in Denver, CO. Field Operations were dispatched to remove the card. Once removed, it did not appear there had been significant improvement; however, the logs were further scrutinized .. to identify that the source…
It will be almost impossible to get a good idea of the actual RCA from public reports, since even if they are accurate, we would need a complete understanding of the topology of the network in question to understand them. That said, the public descriptions will be filtered through so many layers of PR and lawyers as to be incomprehensible. "invalid frame packet"? Were they invalid frames or invalid packets? As fun as…
I’ve had invalid spanning tree (protocol typically used to prevent loops in networks) packets cause a trunk link to flap as the invalid packet made the switch think its only trunk link (the link to the rest of the network) was part of a loop and shut it down. When the link went down, it could no longer get the bad packets, so after a delay it would enable the trunk again and get the invalid packets again.
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#29Makes you wonder how secure their backhaul really is? If the whole thing is a single flat logical network (one that could allow bad packets to propagate as we witnessed) that would suggest it is also quite vulnerable to malicious actions. It is all well and good applying a filter, but that seems like a bandaid fix. Why is equipment even able to talk that has no reason to do so? Seems like they've put convenience over…
Re: CenturyLink 911 outage was caused by a single network card sending bad packets
#30This also happened to coincide with them receiving a notice of a $50/month increase on their bill from CenturyLink, as well as my SO giving them a Roku for the holidays and setting them up with streaming services, which they got lots of practice using in the two whole days the cable TV didn't work.
Guess who's cutting the cord and switching to Internet-only service from Verizon FIOS at a much cheaper rate now?
This is what happens when you treat IT like a cost center and don't provide the necessary funds to tackle technical debt and keep your services up and running: You get huge costly outages revealing your basic incompetence and customers fleeing to superior competitors forever.