Switch Uplink Bandwidth & Oversubscription Calculator

Calculate switch oversubscription ratio (e.g. 48×1G : 2×10G = 2.4:1), uplink bandwidth, utilization and N+1 redundancy in seconds.

☷

Engineering inputs

Set the engineering assumptions and design parameters.

Planning inputs

Mbps
%
%
%
Mbps
%
▥

Engineering results

Review calculated capacity, limits and design checks.

Calculated result

Capacity assessment—
—
Access line-rate total—Gbps
Estimated busy-hour demand—Gbps
Total uplink capacity—Gbps
Target usable capacity—Gbps
Line-rate oversubscription—
Estimated uplink utilization—%
Minimum uplinks required—
Capacity headroom—Gbps

Worked topology: four 48-port 1G access switches

Four switches × 48 ports × 1 Gbps = 192 Gbps theoretical access line rate. With two aggregation switches and each access switch using a dual 10 Gbps uplink, the normal forwarding capacity is 4 × 20 = 80 Gbps when both members are active. The line-rate oversubscription ratio is 192 ÷ 80 = 2.4:1; this is a physical ratio, not a busy-hour forecast.

For an N-1 test, remove one 10 Gbps member or one aggregation path. Survivable capacity becomes 70 Gbps if only one member is lost, or 60 Gbps if one complete 20 Gbps access uplink pair is lost. Recalculate demand against the surviving topology and confirm the stack link, MLAG/stack control plane and inter-switch paths can carry the traffic without a hidden bottleneck.

A shared LAG provides aggregate capacity across flows, while one flow normally hashes to one member. MLAG or a switch stack can keep forwarding after a peer or member failure, but only if both devices, cabling and hashing policy support it. Independent uplinks without a coordinated LAG may provide redundancy but must not be counted as one shared 20 Gbps pipe. Use the 48-port worked guide and the N-1 guide to document the failure assumptions.

Need the formula, examples and N-1 explanation?

ENGINEERING GUIDE

Read the complete engineering guide before or after modeling your design.

Read the Switch Oversubscription Ratio Guide →

See the 48-Port Switch worked example →

Switch uplink bandwidth and oversubscription planning

Demand = Ports × Port Speed × Utilization × Concurrency × (1 + Allowance)

How the calculator sizes an uplink

Access line rate is active ports multiplied by port speed. Estimated busy-hour demand applies average utilization, concurrent active-port percentage and protocol or burst allowance. Target usable capacity is the sum of active forwarding uplinks multiplied by the target utilization.

Line-rate ratio versus demand

The line-rate oversubscription ratio compares all entered access ports at full speed with active uplink capacity. Estimated uplink utilization compares modeled busy-hour demand with that capacity. A high line-rate ratio can still be workable when measured demand is low, but bursts and correlated traffic can create short congestion.

Campus access and server scenarios

For office, school, Wi-Fi AP and IoT access, use measured busy-hour traffic and allow for growth. Server, storage, backup, imaging and east-west workloads may be more synchronized and bursty, so they often need a lower sharing ratio, larger safety margin and closer queue monitoring.

Normal operation and link failure

Count only uplinks that actively forward in the scenario. First model normal operation, then repeat with the links that survive a cable, optic, member switch or line-card failure. Confirm that the remaining topology still meets the target utilization and that traffic can actually use those links.

Frequently asked questions

What switch uplink oversubscription ratio is acceptable?

There is no universal ratio. Select it from measured busy-hour demand, application sensitivity, growth, buffer and queue behavior, and the failure scenario. Campus user access often tolerates more sharing than storage, backup or server traffic.

Do two 10 Gbps uplinks give one flow 20 Gbps?

Usually not. A link aggregation group can provide 20 Gbps aggregate capacity, but hash-based distribution normally keeps one flow on one component link. Flow mix and hash balance determine how evenly the bundle is used.

Should standby or blocked uplinks count as active capacity?

No. Enter only links that forward traffic in the scenario being evaluated. If a standby link activates only after failure, calculate normal operation and the surviving failure topology separately.

Why can a low busy-hour estimate still show a high oversubscription ratio?

The line-rate ratio compares every access port at full speed with total active uplink capacity. Busy-hour demand also applies measured utilization, concurrency and burst allowance, so the two metrics answer different planning questions.

Can this calculator replace traffic monitoring and QoS design?

No. Validate the estimate with interface counters, percentile and peak data, packet drops, queue statistics and application requirements. QoS, buffers, flow hashing, hardware limits and growth remain separate design checks.

Standards and design references

Link aggregation capacity

IEEE 802.1AX defines link aggregation so parallel links can act as one logical, resilient load-sharing interconnect. RFC 7424 explains that hash-based distribution depends on flow mix and may not balance component links evenly.

Campus oversubscription practice

The Cisco Campus LAN and Wireless LAN Design Guide calculates oversubscription from actual access-port speeds and active uplinks, and recommends checking both normal operation and switch or link failure scenarios.

Part of the switching and bandwidth calculators hub.

ENGINEERING WORKFLOW

Continue the engineering workflow

Current workflowEnterprise LAN & IP Planning Workflow

Plan addressing, VLAN capacity, packet size, uplinks, optics, access policy and DNS behavior as one LAN design sequence.

Step 6 of 12

Related tools

Also used inWireless Access Deployment WorkflowData Center Network Fabric Planning Workflow

Explore the Switch Oversubscription Topic Hub →

Is 2×10G enough for a 48-port switch? →

Calculate oversubscription under N-1 failure →