I don't know much at all about networking, and I when I tried to find an answer to this online I found someone who posted a one sentence answer saying "It would cause lots of broadcasts and collisions."

What would happen, if anything at all, if I were to connect an unmanaged network switch to itself with a normal Ethernet cable?

Scenario 1

If I had an 8-port unmanaged switch and I plug one end of an Ethernet cable into port 1 and the other end into port 2. This would be a consumer level switch, the kind available on Amazon for $20.

Scenario 2

If I had a small network similar to the diagram below, would the answer be different from Scenario 1?

Diagram of a network containing switched connected in a loop.

  • 4
    Regarding both scenarios 1) and 2). This is what the IEEE 802.1d Spanning-Tree protocol was designed to facilitate; however, I do not know of an unmanaged switch which implements STP (or any of the later versions, 802.1w / 802.1s). If you loop unmanaged switches like this, you'll quickly find out why people use spanning-tree ;-). Bad Things© happen when you do this; it's one of the things professional network engineers work hard to prevent (including people who bought a switch from Walmart and do this through complete ignorance). – Mike Pennington Mar 12 '14 at 18:46
  • I thought it better not to test this in production. ;) Thanks for the help. – Jonathan Mar 12 '14 at 18:48
  • 2
    Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light. – Daniel R Hicks Mar 12 '14 at 19:58
  • This is much more detail than originally provided. In this situation, as @MikePennington stated you would have issues. On unmanaged consumer switches this will create a loop and it will cause a broadcast storm, as previously stated. STP was designed to prevent issues with this type of setup. A proper implementation of STP or a deriviative (RSTP, MSTP) is needed. You would need managed layer 2 switches in order to accomplish the setup you've described. Daniel, thanks for clearing up the whole "good, bad" thing... :-) – Mike Naylor Mar 13 '14 at 20:26
  • For any n00b coming behind, break any one of the inter-switch links and you would not break your network. Then read the accepted answer and learn why. – YetAnotherRandomUser Apr 16 '16 at 15:26

Auto-sensing versus a crossover cable

If the switch's ports do not auto-sense the orientation of the tx/rx pairs, then absolutely nothing will happen because you've probably used a straight-through cable; the type of cable you'd normally use to connect a workstation/client to the switch.

So, instead let's assume you've used a crossover cable, or much more likely, you have a non-stoneage switch with auto-sensing tx/rx orientation, then...

"Dumb" Switches

You have just created a loop in the network topology. In a moment or two, your network, (all the segments off this dumb switch) will probably stop working as the dumb switch sends the first broadcast packet out one of those two switch ports, receives the packet on the other, and then sends it out the other, etc. Packet storm, meet network, network, this is a packet storm. The switch will probably, (hopefully) squelch the storm, things will come back to working... until the next storm comes along shortly.

So let's assume you're not using "dumb" switches, then...

Managed Switches

Managed switches almost always have loop detection, called Spanning Tree Protocol. When a port comes up with a new link, the switch does not immediately join it to the switch fabric at-large. Instead, it segregates the new port(s) and uses STP to see if a loop would exist if the new port(s) were added to the fabric. (In real-world networks, the loop might not be nearly as obvious as one mis-plugged cable.) Some people, (known as "novices") disable STP so the switch ports "come up" faster. This is great, until you discover why you need STP.


(See also Introductory Level... or our VLAN tag.)

If the two ports are administratively configured in two separate VLANs, then you may well have intentionally wanted to put that cable there to provide connectivity between the VLANs. (But really that makes little sense. Change you're VLANs, or redesign the network, etc. instead of adding a wacky cable.)

  • Thank you for the detailed answer, this helps a lot! I added a diagram to my question, because I realized that there could be a difference between these two scenarios. Would the network have the same problem in scenario 2? Also, when you saw "dumb" switch does that apply to most of the consumer level switches, such as the average $20 switch sold on Amazon? – Jonathan Mar 12 '14 at 18:43
  • 1
    $20 switch is definitely a "dumb" switch w/o STP. My answer only addresses your "scenario 1" since you added "scenario 2" after I answered. BUT, in my section "switches", where I mention real-world networks making less-obvious loops; Your scenario 2 is a loop -- a big obvious loop. Bring all your switches back to the router's interfaces, or have one "core" switch into which your router and distribution switches connect (aka "uplink".) – Craig Constantine Mar 12 '14 at 19:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.