I’m above average familiar with networking, but likely not as much as you. Currently working on going into that field tho.
I’m also semi-familiar with how ATC works from touring their local facilities as part of a course on aerodynamics.
I’m fairly certain they’re lying to cover their ass.
Everything in the ATC system has redundancy. They’re saying they clipped one copper wire and the whole system went down, but there would be another established path for that connection, severing one copper wore wouldn’t stop any communications, they would transmit through a fail safe.
Also, the last time they had to ground all flights was 09/11/2001, and let’s just say it was not because of issues with the extremely reliable technology used in ATC.
They installed their AI slop bullshit a few days ago.
They think we’re all stupid, so they didn’t bother asking anyone who understands the systems before formulating their low-quality lie (in a similar fashion to how they came up with their slop ATC system - without speaking to anyone who knows how the shit works).
You are correct. One physical disconnect of a copper cable isn’t going to kill off an entire system. As you noted, they have redundant network paths, equipment, etc. Those systems were designed not to go down hard, and until this week, never did.
Copper maxes out at 10gbps in a production environment and if they were still using copper Ethernet, they were trunking multiple cables together for higher throughput. The trunking also had to be redundant, so it would take a lot of cutting or unplugging to take it all down as an oopsy.
Again, all speculation, but I’m still betting on a human-grade fuckup. When in doubt, blame DNS.
With network-loop type shit, it’s less likely they clipped the copper wire, and more likely they brought up the fiber before taking down the copper link and things sent over the copper were coming back on the fiber, looping and exploding everything.
It is possible but the old routing protocols that used to do this (spanning tree) have protections in place to prevent it.
At one point, routing protocols were a little more promiscuous and you could create a loop by plugging a single Ethernet cable into two ports on the same switch. Cue Benny hill music as everyone went running around trying to figure out what happened.
Now there are mechanisms like BPDU guard and portfast configs that should prevent this. In most cases, they would be enabled by default. However, I’m sure there are some folks out there who have no idea how to handle an old port config done at the command line. They could have been tinkering to try and make something work, turned off some of the protective features and now they’re back to the 90s with routing loops and broadcast storms. The song is Yakety Sax fwiw, always have it at the ready.
If you ever wonder why the networking people are grouchy, this is why. Networks were and remain complex, highly interdependent, challenging to build and maintain. It takes only a few ignorant people to send something tumbling.
Oh I’m very familiar with (R,M)STP, but yeah I’m assuming they were doing something incredibly incompetent though we have the technology to easily prevent it. Wouldn’t be the current administration if it wasn’t
But you are right, it could have been a minor misconfig that exploded without any real incompetence involved; it’s just more fun to make fun
I’m above average familiar with networking, but likely not as much as you. Currently working on going into that field tho.
I’m also semi-familiar with how ATC works from touring their local facilities as part of a course on aerodynamics.
I’m fairly certain they’re lying to cover their ass.
Everything in the ATC system has redundancy. They’re saying they clipped one copper wire and the whole system went down, but there would be another established path for that connection, severing one copper wore wouldn’t stop any communications, they would transmit through a fail safe.
Also, the last time they had to ground all flights was 09/11/2001, and let’s just say it was not because of issues with the extremely reliable technology used in ATC.
They installed their AI slop bullshit a few days ago.
They think we’re all stupid, so they didn’t bother asking anyone who understands the systems before formulating their low-quality lie (in a similar fashion to how they came up with their slop ATC system - without speaking to anyone who knows how the shit works).
You are correct. One physical disconnect of a copper cable isn’t going to kill off an entire system. As you noted, they have redundant network paths, equipment, etc. Those systems were designed not to go down hard, and until this week, never did.
Copper maxes out at 10gbps in a production environment and if they were still using copper Ethernet, they were trunking multiple cables together for higher throughput. The trunking also had to be redundant, so it would take a lot of cutting or unplugging to take it all down as an oopsy.
Again, all speculation, but I’m still betting on a human-grade fuckup. When in doubt, blame DNS.
With network-loop type shit, it’s less likely they clipped the copper wire, and more likely they brought up the fiber before taking down the copper link and things sent over the copper were coming back on the fiber, looping and exploding everything.
It is possible but the old routing protocols that used to do this (spanning tree) have protections in place to prevent it.
At one point, routing protocols were a little more promiscuous and you could create a loop by plugging a single Ethernet cable into two ports on the same switch. Cue Benny hill music as everyone went running around trying to figure out what happened.
Now there are mechanisms like BPDU guard and portfast configs that should prevent this. In most cases, they would be enabled by default. However, I’m sure there are some folks out there who have no idea how to handle an old port config done at the command line. They could have been tinkering to try and make something work, turned off some of the protective features and now they’re back to the 90s with routing loops and broadcast storms. The song is Yakety Sax fwiw, always have it at the ready.
If you ever wonder why the networking people are grouchy, this is why. Networks were and remain complex, highly interdependent, challenging to build and maintain. It takes only a few ignorant people to send something tumbling.
Oh I’m very familiar with (R,M)STP, but yeah I’m assuming they were doing something incredibly incompetent though we have the technology to easily prevent it. Wouldn’t be the current administration if it wasn’t
But you are right, it could have been a minor misconfig that exploded without any real incompetence involved; it’s just more fun to make fun