Configuring VLANs and QoS Rate Limiting on a Router for Different Subnet Bandwidth Limits
This guide explains how to create VLANs, assign IP addresses, and apply inbound QoS traffic policing on a router to limit the 192.168.10.0 subnet to 6400 kbit/s and the 192.168.20.0 subnet to 12800 kbit/s.
Routers serve as the gateway for enterprise networks, and enterprises often need to control outbound traffic from different internal subnets. In this scenario, the 192.168.10.0 subnet must be limited to 6400 kbit/s, while the 192.168.20.0 subnet must be limited to 12800 kbit/s.
Principle
Traffic policing monitors the inbound traffic rate and penalizes any excess, keeping the flow within a reasonable range. By specifying a source IP address range, the policy can be applied to an entire subnet.
Configuration Steps
1. Create VLANs and allow them on interface Eth2/0/0.
[Router]vlan batch 10 20
[Router]interface ethernet 2/0/0
[Router-Ethernet2/0/0]port link-type trunk
[Router-Ethernet2/0/0]port trunk allow-pass vlan 10 20
[Router-Ethernet2/0/0]quit
2. Create VLANIF interfaces for each VLAN and assign IP addresses.
[Router]interface Vlanif 10
[Router-Vlanif10]ip address 192.168.10.1 255.255.255.0
[Router-Vlanif10]quit
[Router]interface Vlanif20
[Router-Vlanif20]ip address 192.168.20.1 255.255.255.0
[Router-Vlanif20]quit
3. Apply QoS traffic policing on each VLANIF interface for the respective subnet.
[Router]interface Vlanif 10
[Router-Vlanif10]qos car inbound source-ip-address range
192.168.1.2 to 192.168.1.254 cir 6400
[Router]interface Vlanif20
[Router-Vlanif20]qos car inbound source-ip-address range
192.168.1.2 to 192.168.1.254 cir 12800
After completing these steps, traffic from the 192.168.10.0/24 subnet will be limited to 6400 kbit/s and traffic from the 192.168.20.0/24 subnet to 12800 kbit/s, ensuring controlled bandwidth usage across the enterprise network.
Practical DevOps Architecture
Hands‑on DevOps operations using Docker, K8s, Jenkins, and Ansible—empowering ops professionals to grow together through sharing, discussion, knowledge consolidation, and continuous improvement.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.