Network Loop

Network Loop could happen when there is a redundancy within the network, especially in 202207051851# and 202207051907# network. The packet could be trapped in a circle where they will travel endlessly around the same path. As more and more packets get involved in the loop, the network will inevitably come to a halt as no more bandwidth is available to the hosts due to broadcast-storms (infinite flooding of frames originally for broadcasting), multiple copies of frames (most protocols can’t handle duplicated transmissions), and 202206151451 address table instability (receiving the same frame on different ports).

There are solutions for this:

Use 202207061800# to break up the networks into smaller segments
202207081637#

Links to this page

Switch

However, there are some limitation for the switch, especially in coming to solve the #Network Loop.
Spanning Tree Protocol (STP)

STP is a #202206131651 protocol designed to run on 202207051851# and 202207051907# in order to prevent #202207081644 inside the network. It has been standardised by the Institute of Electrical and Electronic Engineers (IEEE) with 802.1d.
Router

It is one of the solution that could prevent #Network Loop.
Rapid Spanning Tree Protocol (RSTP)

RSTP, defined by 802.1w standard, is an alternative to #202207081637, would speed the process, that put a port into a forwarding state, up (by default, it took around at least 30 seconds to set up) by allowing ports (alternative and backup port) to be immediately put into forwarding state, which is especially helpful in critical system. However, this allows the possibility of 202207081644#.
Bridge

Be aware that #202207081644 could happen within the network.

#networking