Understanding Network Flooding, Broadcast Storms, and Loop Prevention in Data Center Ethernet

Recently I have been studying SDN and revisiting basic networking concepts. During the learning process I found some useful video resources, which I share here for readers with weak network fundamentals.

[Video] Network Technology Series – Basic Network Knowledge

[Video] Network Technology Series – Detailed TCP/IP Reference Model

[Video] Network Technology Series – Detailed IP Subnetting

[Video] Network Technology Series – Detailed Network Device Management

[Video] Network Technology Series – OSPF Fundamentals

[Video] Network Technology Series – RIP Fundamentals

[Video] Network Technology Series – IP Routing Selection Principles

(Video source: Huawei product materials)

Today we briefly discuss the network flooding problem. In a Layer‑2 switch communication process, when a switch receives a frame it examines the destination MAC address; if the address table contains a matching entry, the frame is forwarded out the associated port, otherwise the switch floods the frame out all ports except the one it arrived on.

If loops exist between switches, flooded frames circulate endlessly, creating a broadcast storm that consumes all network resources, causing the network to become unable to carry any other traffic.

Origin of Loops

The core issue in Layer‑2 networks is loops and the resulting broadcast storms. A simple tree‑shaped Layer‑2 network with a single device and link has no loops or broadcast storms.

However, such a topology has poor reliability because there is no redundancy; a single device or link failure disconnects all downstream hosts.

To improve reliability, redundant devices and links are added, inevitably forming loops. In complex Layer‑2 networks, physical loops are almost everywhere.

Although Layer‑2 isolates collision domains, all devices share the same broadcast domain. Broadcast frames in a loop are repeatedly forwarded, and because Layer‑2 frames lack a TTL field, they can circulate indefinitely, causing a broadcast storm that quickly blocks ports and cripples devices.

How to Solve Loops

To address flooding and broadcast storms, Layer‑2 networks employ two main techniques:

VLAN segmentation to shrink broadcast domains

VLAN technology partitions a large physical Layer‑2 domain into many smaller logical domains (VLANs). Devices within the same VLAN can communicate at Layer‑2, while different VLANs are isolated, limiting broadcast traffic to the VLAN scope.

Spanning‑tree protocols to prevent loops

This approach tackles the root cause of broadcast storms by blocking redundant ports and links under normal operation. When a primary link or device fails, the blocked redundant port/link is activated, restoring connectivity.

The protocols that provide this automatic control are collectively called “loop‑prevention protocols”. The most common is STP (Spanning Tree Protocol) and its enhancements RSTP and MSTP, collectively referred to as xSTP. Other protocols such as SEP and RRPP share the same fundamental concept.

Traditional Data Center Network Architecture

Traditional data centers typically use a two‑layer + three‑layer architecture: the access layer operates at Layer‑2, the aggregation layer provides routing upward and switching downward, and the core layer offers Layer‑3 routing.

This architecture is mature; the combination of VLAN + xSTP at Layer‑2 and routing at Layer‑3 is well‑established and aligns with the modular nature of data‑center workloads.

In summary, we explored network flooding issues in data‑center environments and the methods to mitigate them. Understanding these fundamentals is essential for deeper knowledge of virtualization and cloud‑computing network technologies.

Recommended Reading

[Video] Data Center Two‑Layer Network Technology Analysis

Friendly Reminder

Please search for “ICT_Architect” or scan the QR code to follow the public account and click the original link for more technical materials.

Stay hungry, stay foolish