First the Hierarchy of the Ethernet pages:
Think of the three associated Data link/Ethernet pages as a drill-down.
Ethernet.html The "Broad View." It introduces the wire, the speeds (25G/100G), and the concept of frames.
mac.html The "Local Delivery." It explains how those frames are addressed and switched using MAC addresses and VLAN tags.
Flow Control.html: (This page) The "Traffic Rules." This is a specialized sub-topic of the MAC layer. It explains a specific feature (IEEE 802.3x) that sounds helpful on paper but is actually a "poison pill" for real-time video.
In high-bandwidth ST 2110 networks, disabling Flow Control is a deliberate engineering requirement, not an oversight.
What is Flow Control (IEEE 802.3x)
Flow control is a mechanism that allows a receiver to tell a sender to "slow down." When a switch or endpoint's internal buffer gets too full, it sends a PAUSE Frame upstream.
The Command: "Stop transmitting for N microseconds."
The Result: The sender freezes all data transmission on that physical link until the timer expires or a "Resume" frame is sent.
Why it is "Toxic" for ST 2110
While Flow Control prevents dropped packets in standard IT networks, it introduces three fatal problems for broadcast:
Timing Instability (PTP): A PAUSE frame is "blind." It stops everything, including PTP sync packets. This introduces jitter and can cause a device to lose its Grandmaster lock even if the network is otherwise healthy.
Head-of-Line Blocking: If one slow multiviewer sends a PAUSE frame to a switch, that switch might pause its uplink to the core. Now, every other device on that switch—even the "fast" ones—is stuck waiting for the one slow device.
Jitter vs. Loss: In 2110, we follow a simple rule: It is better to drop a packet than to delay it. A delayed packet is a late packet, and in real-time video, a late packet is useless.
The Modern Alternative: QoS and Over-Provisioning
Instead of using Flow Control (backpressure), we manage 2110 traffic using:
Strict Priority (QoS): Ensuring PTP always moves to the front of the line, regardless of how much video is behind it.
Non-Blocking Fabrics: Using switches with enough internal "bandwidth" so that they never have to ask a sender to stop.
Traffic Pacing (ST 2110-21): Ensuring senders don't "burst" data too quickly for the receivers to handle.
Engineering Best Practice Rule of Thumb: Disable 802.3x Flow Control on all ports (Switch-to-Switch and Switch-to-Node). If your network is dropping packets because it's full, you need a faster link (e.g., moving from 10G to 25G), not Flow Control.