Network Loop Problems and Broadcast Storm Prevention
Network+ · Network Troubleshooting · Bởi Super Admin
Discover the problems caused by redundant links in switched networks, including broadcast storms, duplicate frames, and MAC table thrashing.
Redundant Links and Loop Formation
Redundant links between switches can be a wise thing to implement because they help prevent complete network failures in the event that one link stops working. However, redundant links often cause more problems than they solve because frames can be flooded down all redundant links simultaneously, creating network loops as well as other evils. Understanding these problems is essential for implementing effective loop avoidance schemes in switched networks.
One way to test the loop avoidance operations of your switch network is to plug one end of a cable into one port and the other end of the same cable into another port. If loop avoidance is not operational, this should cause a big broadcast storm. This simple test demonstrates how quickly switching loops can develop and the importance of having proper loop prevention mechanisms in place.
Broadcast Storms and Frame Duplication
If no loop avoidance schemes are put in place, the switches will flood broadcasts endlessly throughout the internetwork. This is sometimes referred to as a broadcast storm, though in real life it's often referred to in less polite ways. A broadcast can be propagated throughout the network continuously, with frames being flooded through the internetwork's physical network media without end.
<img src="/question_assets/Network+/sg_c11f008.png" alt="An illustration shows that the broadcast can receive multiple copies of the same frame because that frame can arrive from different segments at the same time."/>
<figcaption>Broadcast storm</figcaption>
A device can receive multiple copies of the same frame because that frame can arrive from different segments at the same time. When a server sends a unicast frame to another device connected to a segment, multiple switches may receive and forward the frame simultaneously. Because it's a unicast frame, Switch A receives and forwards the frame, and Switch B provides the same service by forwarding the unicast. This is bad because it means that the destination device receives that unicast frame twice, causing additional overhead on the network.
<img src="/question_assets/Network+/sg_c11f009.png" alt="An illustration shows that unicast can demonstrate how a whole bunch of frames can arrive from multiple segments simultaneously."/>
<figcaption>Multiple frame copies</figcaption>
MAC Table Thrashing and Multiple Loop Propagation
The MAC address filter table could be totally confused about the device's location because the switch can receive the frame from more than one link. Worse, the bewildered switch could get so caught up in constantly updating the MAC filter table with source hardware address locations that it might fail to forward a frame. This is called thrashing the MAC table, and it represents a serious degradation of switch performance.
One of the nastiest things that can happen is having multiple loops propagating throughout a network. This means you end up with loops occurring within other loops, and if a broadcast storm happened at the same time, the network wouldn't be able to perform frame switching at all. All of these problems spell disaster and are decidedly ugly situations that just must be avoided or at least fixed somehow. That's where the Spanning Tree Protocol comes into the game, as it was developed to solve each and every one of these problems.
Thảo luận / Bình luận (0)
Chưa có thảo luận nào cho bài viết này. Hãy gửi bình luận đầu tiên nhé!
Vui lòng Đăng nhập để tham gia thảo luận.