Contents

QoS Processes QoS Scheme Priority Queue Packet Loss Priority Drop Profile Configuration of QoS

QoS Processes
Classification refers to the examination of an incoming packet. This function often associates the packet with a particular CoS servicing level. Queuing After a packet is sent to the outgoing interface on a router, it is queued for transmission on the physical media. The amount of time a packet is queued on the router is determined by the availability of the outgoing physical media as well as the amount of traffic using the interface. Scheduling An individual router interface may have multiple queues assigned to store packets. The router then decides which queue to service based on a particular method of scheduling. This process often involves a determination of which type of packet should be transmitted before another. Rewrite Rules sets the appropriate CoS bits in the outgoing packet. This allows the next downstream router to classify the packet into the appropriate service group (forwarding class).

QoS Scheme

Data, Nb and Sigtran packets come at the same time. Classifier check the marked of the packet either in IP Header or EXP Bit in MPLS Label Header, then it will put each packet to the appropriate forwarding class. Based on the mark, the classifier will decide which loss priority & priority queue will be applied to the packet. The scheduler will manage how big is the transmit rate and buffer memory for each forwarding class. The High Priority Queues are transmitted in Round Robin, and the Low Priority Queues are in the other Round Robin. As long as there is a packet of the high priority queue in profile, the Low Priority Queue will have to wait. The queue is in profile when the transmitted traffic is less than the allocated bandwidth for the queue. The Random Early Discard (RED) is applied based on the drop profile. The fullness of buffer will determine the probability of the packet will be drop when it arrives on the head of the queue. This mechanism helps the TCP traffic to manage network congestion.

Priority Queue
The JUNOS software performs priority queuing using the following steps: 1. The router first locates all high-priority queues that are currently in profile. These queues are serviced first in a weighted round-robin fashion. 2. The router then locates all low-priority queues that are currently in profile. These queues are also serviced using a weighted roundrobin scheme. 3. The router then locates all high-priority queues that are currently out of profile and that are not rate limited. The weighted round-robin algorithm is applied to these queues for servicing. 4. The router finally locates all low-priority queues that are currently out of profile and are also not rate limited. These queues are serviced last in a weighted round-robin manner.

Packet Loss Priority (PLP)

To manage congestion, the Random Early Drop (RED) is applied so the packet at the head of the queue will have probability variously depends on the fullness of the outgoing interface. This drop mechanism is useful for TCP traffic which has ability to resend the drop packet and to avoid one TCP session flooding the link. The probability drop packet versus interface fullness is defined in drop profile parameter (diagram).

Drop profile
transmit
Once RED is operational on an interface, the queue no longer drops result cells from the tail of the queue. Rather, cells are dropped after they reach the head of the queue. At this point, the router generates a random number to plot against the drop profile graph. This ultimately determines if the result cell is dropped from the network or transmitted out the physical interface.

Drop probability % 25 50

100

drop

Fullness %

75

100

When buffer fullness is 75%, if the random number more than 25% , it ( )is above the line, so the packet is transmitted. On the other hand if the random number is less than 25%, it ( ) is under the line, the packet is dropped.

Configuration of QoS
Defining Code Points
This code defines user friendly name mapped to bit code. The bit code is marked in the IP Header or MPLS Header. The router will recognize this code and classified the packed based on this code. Code point type: dscp Alias Bit pattern af11 001010 af12 001100 af13 001110

Configuration of QoS (cont.)

Forwarding Classes
The forwarding class is referenced in both a classifier and a rewrite rule. In addition, the forwarding classes are closely aligned with the operation and definitions of the routers queues.

Example:
noc@JKT-PE05> show configuration class-of-service forwarding-classes queue 0 best_effort_data; queue 1 critical_data; queue 2 real_time_and_video; queue 3 network_control;

Taufiq Budiman

Configuration of QoS (Cont.)

A drop profile is the most basic building block of implementing a random early discard (RED) configuration. Simply put, the drop profile defines parameters that allow the packet to be dropped from the network. The two main portions of the drop profile are the queue fullness and the drop probability. The queue fullness represents a percentage of the memory used to store result cells in relation to the total amount that has been allocated for that specific queue. Only the result cells sent by the Internet Processor ASIC are stored in this queue memory. In a similar manner, the drop probability is a percentage value that correlates to the likelihood that an individual packet is dropped from the network. noc@JKT-PE05> show configuration class-of-service drop-profiles high_drop_priority_be { interpolate { fill-level [ 30 50 70 90 100 ]; drop-probability [ 0 25 50 75 100 ]; } } low_drop_priority_be { interpolate { fill-level [ 50 70 90 100 ]; drop-probability [ 0 50 75 100 ]; } }

Taufiq Budiman

Scheduler

Configuration of QoS

Scheduler is to define the properties of an individual queue: Bandwidth assigned for the queue (outgoing interface), it is transmit-rate. Memory buffer allocated for the result cells (out going FPC), it is buffer-size. Priority for the queue. Drop Profile for RED.
noc@JKT-PE05 show configuration class-of-service schedulers | display inheritance sch_be_scheduler { transmit-rate remainder; buffer-size remainder; priority low; drop-profile-map loss-priority low protocol tcp drop-profile low_drop_priority_best_efforts; drop-profile-map loss-priority high protocol tcp drop-profile high_drop_priority_best_efforts; } sch_critical_scheduler { transmit-rate percent 15; buffer-size percent 15; priority high; drop-profile-map loss-priority any protocol tcp drop-profile drop_priority_critical_data; } sch_real_time_scheduler { transmit-rate percent 50; buffer-size percent 30; priority high; drop-profile-map loss-priority high protocol tcp drop-profile high_drop_priority_video_and_realtime; drop-profile-map loss-priority low protocol tcp drop-profile low_drop_priority_video_and_realtime; } sch_network_control { transmit-rate percent 5; buffer-size percent 5; priority high; }

Scheduler-map
Scheduler-map functions:
Associating individual scheduler to outgoing interface and forwarding class.
noc@JKT-PE05 show configuration class-of-service scheduler-maps map_scheduler { forwarding-class best_effort_data scheduler sch_be_scheduler; forwarding-class critical_data scheduler sch_critical_scheduler; forwarding-class real_time_and_video scheduler sch_real_time_scheduler; forwarding-class network_control scheduler sch_network_control; }