you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 day ago (1 child)

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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 19 hours ago

    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.

  • source
  • parent