Operations 17 min read

Understanding QoS: Principles, Benefits, Models, and Configuration Examples for Huawei, Cisco, and Juniper Routers

This article explains Quality of Service (QoS) concepts, benefits, common metrics, service models, deployment strategies, and provides detailed configuration examples for Huawei, Cisco, and Juniper routers to manage network traffic effectively in enterprise networks.

Architects' Tech Alliance
Architects' Tech Alliance
Architects' Tech Alliance
Understanding QoS: Principles, Benefits, Models, and Configuration Examples for Huawei, Cisco, and Juniper Routers

Quality of Service (QoS) is a set of techniques that manage data‑flow on a network to reduce packet loss, delay and jitter by assigning different priorities to traffic classes.

Benefits include guaranteeing bandwidth for critical applications such as voice and video, improving network utilization, and lowering operational costs by avoiding unnecessary bandwidth upgrades.

Typical WAN scenarios involve enterprises connecting headquarters and branches via leased lines, where traffic is classified into voice, video, production, office, testing, and big‑data streams, each with distinct latency and bandwidth requirements.

Key QoS metrics are packet‑loss rate, jitter, latency, bandwidth, and Mean Opinion Score (MOS) for voice quality.

Three service models are commonly used:

Best‑Effort : all packets receive the same priority; the network forwards them as best it can.

IntServ : applications signal required resources; the network reserves bandwidth along a path (requires RSVP support).

DiffServ : traffic is marked with DSCP values and treated according to class, without per‑flow signaling.

QoS mechanisms include classification & marking, congestion management (priority queues, FIFO, low‑latency queues), congestion avoidance (WRED, RED), and traffic shaping.

Deployment guidelines recommend placing rate‑limiting policies near the traffic source (inbound) and protection policies near the egress (outbound), with bidirectional traffic configured on both ends.

Configuration examples

Huawei router (inbound limit and outbound guarantee)

acl name AAA advance
rule x permit ip source x.x.x.x x.x.x.x destination x.x.x.x x.x.x.x
traffic classifier AAA
 if-match acl AAA
traffic behavior AAA
 car cir xxxxx kbps
traffic policy AAA
 classifier AAA behavior AAA
interface x/x/x
 traffic-policy AAA inbound

Cisco router (CBWFQ and policing)

class-map match-all class-1
 match access-group name acl-1
class-map match-all class-2
 match access-group name acl-2
class-map match-all class-3
 match protocol http
policy-map CBWFQ
 class class-1
  bandwidth 1800
 class class-2
  bandwidth 1000
 class class-3
  police cir 1500000 conform-action transmit exceed-action drop violate-action drop
interface x/x
 service-policy output CBWFQ

Juniper router (class‑of‑service and scheduler)

set chassis fpc 1 pic 1 max-queues-per-interface 8
set groups group-1 firewall family inet filter <*> term <*> from source-address x.x.x.x/x
set class-of-service forwarding-classes class class-1 queue-num 1
set class-of-service forwarding-classes class class-2 queue-num 2
set firewall family inet filter filter-1 term term-1 apply-groups group-1 then loss-priority low then forwarding-class class-1 then accept
set class-of-service schedulers scheduler-1 transmit-rate 2m priority medium-high
set class-of-service scheduler-maps map-1 forwarding-class class-1 scheduler scheduler-1
set interfaces x/x/x unit x scheduler-map map-1 shaping-rate 20m

Additional reading links and download resources are listed at the end of the original article.

QoSnetwork managementtraffic shapingDiffServIntServrouter configuration
Architects' Tech Alliance
Written by

Architects' Tech Alliance

Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.