Automatic bandwidth limiting: brakes for abnormal traffic.
When a server's average bandwidth over a time window exceeds the threshold, DCIM limits its switch port to a set rate. Once traffic falls back and stays stable the limit is lifted automatically, or an administrator can lift it by hand.
Automatic bandwidth limits (cropped) · Actual product interface · sensitive data redacted
Key capabilities
- 01
Averages, not spikes
Decisions use the average over the last N minutes, so brief spikes do not trigger a limit.
- 02
Independent directions
Set thresholds and limits separately for inbound and outbound; leave one empty to ignore it.
- 03
Any or all
Limit when either direction exceeds its threshold, or only when both do.
- 04
Automatic or manual release
Restore the original speed after traffic stays low for a set time, or release with one click.
Why automatic limiting matters
When a server is attacked, infected with a crypto miner or abused by a customer, its traffic can surge within minutes and hurt every other customer on the same switch or uplink. By the time someone notices on a graph and logs in to the switch, it is often too late.
Automatic bandwidth limiting keeps watch for you: when average bandwidth crosses the red line it hits the brakes, and when traffic returns to normal it lets go.
What a rule contains
Rules are attached to the server’s traffic pool, so traffic billing must be configured first. A rule includes:
| Setting | Unit | Notes |
|---|---|---|
| Trigger threshold | Mbps | Set per direction; empty or 0 means that direction is ignored |
| Limit after trigger | Mbps | The rate the direction is reduced to, minimum 1 |
| Time window | Minutes | Average over the last N minutes, so short spikes do not trigger |
| Trigger logic | Any / All | Trigger when either direction exceeds, or only when both do |
| Release mode | Automatic / Manual | Automatic release waits until bandwidth stays low for 1–1,440 minutes |
Status at a glance
The top of the bandwidth limit panel shows the current rule: trigger logic, time window and release mode. Two direction cards show the threshold and limit for inbound and outbound. An enabled rule is marked as enabled, a port that is currently limited shows a red “Limited” badge, and administrators can click “Release limit” at any time to restore the original speed.
Templates and bulk apply
Servers on the same plan usually share the same limiting rule. Save it as a bandwidth limit template and apply it to other servers in bulk, so newly installed machines are configured in one go.
Working with traffic billing
Traffic billing answers “how much did we use this month”; automatic limiting answers “is something wrong right now”. Both live on the same traffic pool, one handling the invoice and the other handling bursts, without getting in each other’s way.
Automatic bandwidth limiting
How is this different from over-quota throttling in traffic billing?
Traffic billing looks at cumulative traffic over a cycle and acts when the quota is used up. Automatic limiting looks at average bandwidth over the last few minutes to handle sudden abnormal traffic. Both are configured on the same traffic pool.
Is the original port speed restored when the limit is lifted?
Yes. DCIM records the port's original speed when it applies a limit and restores it on release.
Can I apply the rule to many servers at once?
Yes. Save the rule as a bandwidth limit template and apply it to other servers in bulk.
See how it works in your data center.
Start with a product demo and map out your next step.
Hotline 400-112-2951