OSNTC.049: Why Microbursts Drop Packets on Fast Networks

Data center network technician inspecting optical links on a switch rack, with a small neon-green BitcoinVersus.tech watermark at bottom left.

OSNTC.049 examines a frustrating network failure: a switch can report low average link utilization and still lose packets. The cause may be a microburst—traffic arriving faster than an egress port can transmit for a brief interval. Unlike a disconnected optic or persistent bandwidth saturation, the overload may end before ordinary monitoring notices. The lesson builds on OSNTC.045 on RoCEv2 congestion control but concentrates on packet queues and field evidence.

Accedian (now part of Cisco), “What is a microburst and how does it affect the performance of my network?” Greg Spear explains the basic performance problem. Video listing verified; player availability depends on YouTube.

Why a lightly used port can drop traffic

An interface utilization graph is usually an average across a reporting window. Microbursts occur at a far finer time scale. Cisco’s Catalyst output-drop troubleshooting guide explains why a queue can overflow between polling intervals. Multiple incoming streams can converge on one slower egress interface. Once the allocated buffer is full, additional packets may be discarded even though the port remains electrically and optically healthy.

Do not confuse congestion drops with physical-layer errors. OSNTC.044 covers optical diagnostics and FEC; the counters answer a separate question. Packet drops during congestion may occur without loss of optical signal or a failed transceiver.

A useful 200-microsecond calculation

Consider an illustrative 100 Gbps ingress stream feeding a 25 Gbps egress port for 200 microseconds. The arrival rate exceeds the departure rate by 75 Gbps. The excess data accumulated over the burst is 75 billion bits/second × 0.0002 seconds ÷ 8 = 1,875,000 bytes, or approximately 1.875 MB in decimal units. The result is a simplified backlog estimate, not a claim about any switch’s real buffer capacity: framing overhead, queue scheduling, other traffic and shared-memory policies also matter.

A one-minute bandwidth graph could show very little average activity while missing the event entirely. A narrow burst can still delay packets, cause retransmissions and affect latency-sensitive applications. See the packet-loss and jitter explainer for application-level symptoms.

Look for queue evidence, not only link status

Inspect output-drop and queue counters on the exact egress interface; capture a baseline and a later value, then compute the increase over the observation interval. Check queue occupancy, tail drops, policy drops and any platform-specific microburst records. Cisco’s Nexus 9000 monitoring guide describes rise and fall thresholds for egress-buffer occupancy. Not every switch or software release supports equivalent telemetry.

Original r/networking discussion, “Microburst detection and Shaping” (April 2025). Field questions about shaping, latency and hardware queue behavior are practitioner observations, not vendor test results.

Read-only troubleshooting sequence

First, identify the congested egress port, its speed, peer and relevant traffic classes. Second, record utilization windows together with packet-drop counter deltas, rather than relying on a lifetime total. Third, inspect per-queue data where available and compare timestamps with application latency or retransmissions. Fourth, review ingress-to-egress fan-in, oversubscription and the traffic path. OSDCEC.009 on data-center fabrics supplies useful architectural context.

If a packet capture is authorized, validate whether its collection method and time resolution can actually reveal the short event. A monitoring port or capture host can introduce its own drops. Juniper’s network analytics documentation provides another vendor example of high-frequency traffic and queue monitoring.

Fixing loss involves trade-offs

More buffer space can absorb some bursts but may increase queuing delay. Faster egress links or lower fan-in can reduce oversubscription; traffic shaping, QoS scheduling or congestion feedback can help when implemented with appropriate platform support. Blindly increasing buffers or changing policies on production switches can move the problem rather than solve it. Review OSNTC.048 on EVPN host-mobility troubleshooting for an example of why different network failure classes require different evidence.

Field takeaway: low average utilization does not rule out short-lived congestion. Measure queue behavior at the relevant time scale, separate physical errors from egress drops, and reserve configuration changes for an approved maintenance plan.

Leave a Reply