Obtain Quality of Service with Junos CoS

Junos CoS enables prioritization of traffic flows over a common path. It offers a means to recognize and control different types of
traffic, provides the ability for applications to be considered more or less important, and provides mechanisms to manage congestion.
Junos CoS is implemented “hop by hop”, at each device in the data path.

Packet flow through a device running the Junos OS

NETWORK DEVICE

POLICING QUEUING/ SHAPING REMARKING

CLASSIFICATION
(optional) SCHEDULING (optional) (optional)

CLASSIFICATION POLICING

Class A (Queue 1)
Policer Further
Data
Data Data Data Accept CoS
processing
Class B (Queue 2) Traffic within
Further CoS thresholds
Data Data Data Classifier Data processing
Traffic exceeding
thresholds
Class C (Queue 3)
(make lower priority)
Data
Drop

Classifiers assign inbound traffic to forwarding classes. Policing controls inbound traffic burstiness.
• Forwarding classes are linked to physical queues in the device. • Defines what is considered “too much” traffic.
Classifiers also specify packet loss priority (drop precedence). • Provides first-level congestion management.
• Used by policers and schedulers to help determine which traffic to drop under congestion. Thresholds determine in-profile vs. excess traffic.

Bandwidth
Junos OS includes four default classes: • Bandwidth – data rate for traffic sent through policer (in bps).
• Best effort (BE), Expedited forwarding (EF), Assured forwarding (AF), Network control (NC). • Burst size – number of bytes allowed during a burst (in bytes).
Three methods of classification: • Both thresholds exceeded together = excess traffic.
Burst Size
• Behavior aggregate (BA) – separates incoming traffic based on existing CoS markings. Two policer actions:
• Multifield (MF) – separates incoming traffic based on packet header fields. • ‘Hard’ policer – drops excess traffic.
• Fixed – assigns all of an interface’s incoming traffic to one forwarding class. • ‘Soft’ policer – marks excess traffic with lower priority.

QUEUING/SCHEDULING SHAPING

Class A (Queue 1)

Data
Outbound packets at line rate Outbound packets at sub-line rate
Data
Class B (Queue 2) Further
Further
Scheduler Data Data Data CoS Data Data Data Data Shaper Data Data Data CoS
Data processing processing
Data
Class C (Queue 3)

Data

Queuing and scheduling control the prioritization of traffic flows. Shaping controls outbound traffic flow.
• Defines treatment of packets and queues. • Throttles the amount of traffic passing through an interface or queue to less than line rate.
Each queue has four configurable characteristics: • Provides egress rate-limiting for downstream congestion management.
• Transmission rate – bandwidth assigned to the queue.
• Priority – importance of the queue (relative to other queues).
• Delay buffer – storage space during congestion.
• Congestion management (drop profiles) – amount and type of traffic to drop as
congestion increases.

REMARKING

Rewrite
Data Data Data Data Data Data
rules
Class C Class B Class A DSCP DSCP DSCP
xxxxxx yyyyyy zzzzzz

Remarking applies CoS values to outbound traffic.

• Simplifies packet classification processing for downstream devices.
• CoS values are assigned based on packets’ forwarding class and packet loss priority (PLP) settings.
Reverse function of classification:
• Classification = inbound packet forwarding class (and PLP).
• Remarking = Forwarding class (and PLP) CoS-marked outbound packet.

CoS Fields in Packet Headers

IPv4 IPv6 Ethernet (802.1p)
Version IHL Type of Service Total Length Version Traffic Class Flow Label Dest Addr Src Addr TPID TCI Type/Len Data FCS

Identification Flags Fragment Offset Payload Length Next Header Hop Limit

Time to Live Protocol Header Checksum PCP* CFI VLAN ID

Source Address
Source Address
*Priority Code Point
Destination Address
MPLS
Options Padding
Destination Address Label TC S TTL

DSCP
Traffic Class
IP DSCP
Precedence (formerly EXP)

For additional technical resources, please visit: www.juniper.net/documentation/

DAY O NE POSTER

Junos CoS

Class of Service Feature Learning Bytes Series: Day One: Deploying Day One: Junos QoS Training Course: Junos Learn About: Juniper Networks
Guide for Routing Devices Class of Service Basics Basic QoS for IOS Engineers Class of Service (JCOS) Quality of Service (QoS) Information and
©2016 by Juniper Networks, Inc. All rights reserved. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, Learning Experience (iLX)
modify, transfer, or otherwise revise this publication without notice.
www.juniper.net/posters
ISBN: 978-1-941441-33-6 234567
 Configuring Junos CoS
This example contains the main CoS configuration elements for a device running the Junos OS: forwarding classes, classifiers,
policers, schedulers, shapers, and rewrite rules. Note that this example is for illustrative purposes only; while functional, there
are many more configuration options and advanced settings not displayed here.

Class of Service Stanza Firewall Stanza

class-of-service {
classifiers { firewall {
dscp DSCP-BA-CLASSIFIER { A family inet {
forwarding-class Voice { filter MF-CLASSIFIER { C
loss-priority low code-points ef; term VOICE {
} from {
forwarding-class Data-1 { protocol udp;
Code Point Aliases port 16384-32767;
loss-priority low code-points af41;
CLASSIFICATION

(included by default on Junos devices) }

loss-priority medium-high code-points cs4; can be used in place of numeric values
loss-priority high code-points cs3; then {
} loss-priority low;
user@device> show class-of-service forwarding-class Voice;
forwarding-class Data-2 { code-point-aliases dscp
loss-priority low code-points af21; accept;
loss-priority high code-points cs2; }
Code point type: dscp }
} Alias Bit pattern
forwarding-class Data-3-BE { term INTERACTIVE-VIDEO {
af11 001010 from {
loss-priority low code-points be; af12 001100
loss-priority high code-points cs1; protocol [ tcp udp ];
af13 001110 port 6060-6061;
} af21 010010
forwarding-class Network-Control { }
af22 010100 then {
loss-priority low code-points [ cs6 cs7 ]; af23 010110
} loss-priority low;
af31 011010 forwarding-class Data-1;
} af32 011100
} accept;
af33 011110 }
drop-profiles { af41 100010
QUEUING/SCHEDULING

WRED-DROP-PROFILE-MODERATE { D }
af42 100100 term CALL-SIGNALING {
fill-level 75 drop-probability 20; af43 100110
fill-level 85 drop-probability 35; from {
be 000000 protocol tcp;
fill-level 95 drop-probability 50; cs1 001000
fill-level 100 drop-probability 100; port 1720;
cs2 010000 }
} cs3 011000
WRED-DROP-PROFILE-AGGRESSIVE { D then {
cs4 100000 loss-priority high;
fill-level 50 drop-probability 10; cs5 101000
fill-level 70 drop-probability 40; forwarding-class Data-1;
cs6 110000 accept;
fill-level 85 drop-probability 75; cs7 111000
fill-level 100 drop-probability 100; }
ef 101110 }
} nc1 110000
} term NETWORK-MANAGEMENT-TELNET-SSH {
nc2 111000

CLASSIFICATION
forwarding-classes { from {
queue 0 Data-3-BE; protocol tcp;
queue 2 Voice; port [ telnet ssh ];
E }
queue 3 Network-Control;
queue 4 Data-2; then {
queue 6 Data-1; loss-priority high;
} forwarding-class Network-Control;
interfaces { accept;
ge-* { }
scheduler-map SCHEDULER-MAP-A; F CoS uses a modularized configuration }
unit * { model. Some elements are created and term ICMP-POLICE {
classifiers { then referenced elsewhere. from {
dscp DSCP-BA-CLASSIFIER; A protocol [ icmp icmp6 ];
} Create Reference }
rewrite-rules { then {
dscp DSCP-REMARKING; G policer POLICER-ICMP-5M-DISCARD; B
} forwarding-class Data-2;
A Apply the BA classifier to the desired accept;
} inbound interface(s)
} }
ge-0/0/1 { }
SHAPING

scheduler-map SCHEDULER-MAP-A; F B Apply the policers within the firewall term BEST-EFFORT-INTRANET-TRAFFIC {
shaping-rate 800m; filters (MF classifiers) from {
} protocol tcp;
} C Apply the firewall filter (MF classifier) port 8080;
rewrite-rules { to the desired inbound interface(s) }
dscp DSCP-REMARKING { G then {
forwarding-class Voice { policer POLICER-250M-FC_D3-BE; B
D Apply the drop profiles within the
loss-priority low code-point ef; schedulers forwarding-class Data-2;
} accept;
forwarding-class Data-1 { }
loss-priority low code-point af41; E Use a scheduler-map to apply }
schedulers to traffic classes term BEST-EFFORT-TRAFFIC {
loss-priority medium-high code-point cs4;
REMARKING

loss-priority high code-point cs3; from {

} F Apply the scheduler-map to the desired protocol tcp;
forwarding-class Data-2 { outbound interface(s) port [ ftp ftp-data http https ];
loss-priority low code-point af21; }
loss-priority high code-point cs2; G Apply the rewrite rule to the desired then {
} outbound interface(s) loss-priority high;
forwarding-class Data-3-BE { forwarding-class Data-3-BE;
loss-priority low code-point be; accept;
loss-priority high code-point cs1; }
} }
} term all-else {
} then accept;
scheduler-maps { }
SCHEDULER-MAP-A { F }
forwarding-class Voice scheduler Voice-Scheduler; }
forwarding-class Data-1 scheduler Data-1-Scheduler; E policer POLICER-ICMP-5M-DISCARD { B
forwarding-class Data-2 scheduler Data-2-Scheduler;
if-exceeding {
forwarding-class Data-3-BE scheduler Data-3-Scheduler;
bandwidth-limit 10m;
forwarding-class Network-Control scheduler Nwk-Ctl-Scheduler;
burst-size-limit 625k;
}
}
}
then discard;
schedulers {
}
Voice-Scheduler {
POLICING

policer POLICER-250M-FC_D3-BE { B
transmit-rate percent 10;
if-exceeding {
buffer-size percent 5;
bandwidth-limit 250m;
priority high;
burst-size-limit 625k;
}
}
QUEUING/SCHEDULING

Data-1-Scheduler {
then {
transmit-rate percent 10;
loss-priority low;
buffer-size percent 10;
forwarding-class Data-3-BE;
priority medium-high;
}
}
}
Data-2-Scheduler {
}
transmit-rate percent 40;
buffer-size percent 25;
priority medium-low;
drop-profile-map loss-priority low protocol any drop-profile WRED-DROP-PROFILE-MODERATE; D
Interfaces Stanza
} E
Data-3-Scheduler { interfaces {
transmit-rate { …
remainder; ge-0/0/2 {
} unit 0 {
buffer-size { family inet {
remainder; filter {
} input MF-CLASSIFIER; C
priority low; }
drop-profile-map loss-priority low protocol any drop-profile WRED-DROP-PROFILE-AGGRESSIVE; D address 192.168.1.254/24;
} }
Nwk-Ctl-Scheduler { }
transmit-rate percent 5; }
buffer-size percent 5; …
priority high; }
}
}

For additional technical resources, please visit: www.juniper.net/documentation/

©2016 by Juniper Networks, Inc. All rights reserved. Juniper Networks assumes no responsibility for any inaccuracies in this document.
Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

ISBN: 978-1-941441-33-6 234567