Cisco IOS bandwidth control
Choose modern MQC / Policy-Map or legacy rate-limit compatibility.
Generate Cisco IOS/IOS XE bandwidth policing with MQC / Policy-Map or legacy Committed Access Rate (CAR), including CIR and burst calculations.
Choose modern MQC / Policy-Map or legacy rate-limit compatibility.
MQC organizes QoS through policies that can be attached to interfaces with service-policy. The generated baseline applies a single-rate policer to class-default: traffic within the CIR is transmitted and traffic above it is dropped.
The legacy rate-limit option generates the older interface-level Committed Access Rate style. It is kept here for operational compatibility with older environments, not as a replacement for MQC.
The generator converts Mbps to bps and uses the selected time interval to obtain a byte quantity: burst = CIR (bps) × interval (seconds) ÷ 8. A 100 ms interval therefore represents one tenth of a second of traffic at the configured CIR.
Burst sizing affects how the policer reacts to short traffic bursts. Do not treat the generated value as a universal recommendation: hardware architecture, interface speed, traffic behavior and IOS/IOS XE release can impose different limits or syntax.
Policing enforces a rate by taking an action when traffic exceeds the configured profile; in this generator, exceeding traffic is dropped. Shaping is a different mechanism that normally buffers and schedules excess traffic. Choose the mechanism according to the objective and platform.
For the classic IOS rate-limit command, Cisco documents the average rate in 8 kbps increments and a range from 8,000 to 2,000,000,000 bps. This generator validates those constraints in legacy mode instead of silently producing a value that falls outside the documented command range.
Cisco QoS capabilities vary by platform, interface type and IOS/IOS XE release. Minimum and maximum police rates, burst granularity, supported directions and hardware resource consumption can differ substantially. Always validate the generated policy against the target model and release before deployment.
No. QoS capabilities, command syntax, direction support and hardware limits vary by Cisco platform and software release. Validate the generated configuration against the target device documentation.
Some older Cisco IOS environments used interface-level rate-limit configuration. The option is provided for compatibility and operational reference, while MQC remains the preferred baseline when supported.
No. Both generated modes are policing examples. Traffic that exceeds the configured profile is dropped by the generated configuration.