10.2.4.4. Priority Control Setting¶
This section describes the settings for preferential control of traffic which is output from the interface.
Presumed case for sample setting
To set for traffic which is output from interface “dp0s5”
The restrictive bandwidth of interface “dp0s5” is 10 Mbps.
Setting the traffic from virtual server 7 to virtual server 9 as the priority traffic
Flowing 9.3 Mbps traffic from virtual server 6 to virtual server 8 for 60 seconds
During communications just mentioned, flowing 2.3 Mbps traffic from virtual server 7 to virtual server 9 for 30 seconds so that interruption occurs.
Setting flow
1.Setting the name of QoS to be set, with PRIORITY_EF Applying QoS at interface “dp0s5”
2.Setting control rule 1 (highest priority) named ef to UDP communications originated from virtual server 7 “172.16.9.7” and setting control rule 2 named af11 to UDP communications originated from virtual server 6 “172.16.9.6”
3.Setting the default policy for traffic The policy name is PROF1.
4.Setting the restrictive bandwidth of policy PROF1 to 10 Mbps
5.Applying control rule af11 to queue 1 and specifying Traffic-Class(1) to be used Applying control rule ef to queue 0 and specifying Traffic-Class(0) to be used
6.Setting the restrictive bandwidth of Traffic-Class(0) to 3 Mbps
Command to be entered with CLI
set interfaces dataplane dp0s5 policy qos 'PRIORITY_EF'
set policy qos name PRIORITY_EF shaper class 1 match RULE1 mark dscp 'ef'
set policy qos name PRIORITY_EF shaper class 1 match RULE1 protocol 'udp'
set policy qos name PRIORITY_EF shaper class 1 match RULE1 source address '172.1 6.9.7/32'
set policy qos name PRIORITY_EF shaper class 1 match RULE2 mark dscp 'af11'
set policy qos name PRIORITY_EF shaper class 1 match RULE2 protocol 'udp'
set policy qos name PRIORITY_EF shaper class 1 match RULE2 source address '172.1 6.9.6/32'
set policy qos name PRIORITY_EF shaper class 1 profile 'PROF1'
set policy qos name PRIORITY_EF shaper default 'PROF1'
set policy qos name PRIORITY_EF shaper profile PROF1 bandwidth '10Mbit'
set policy qos name PRIORITY_EF shaper profile PROF1 map dscp af11 to '1'
set policy qos name PRIORITY_EF shaper profile PROF1 map dscp ef to '0'
set policy qos name PRIORITY_EF shaper profile PROF1 queue 0 traffic-class '0'
set policy qos name PRIORITY_EF shaper profile PROF1 queue 1 traffic-class '1'
set policy qos name PRIORITY_EF shaper profile PROF1 traffic-class 0 bandwidth ' 3Mbit'
interfaces {
dataplane dp0s4 {
address 172.16.9.90/24
}
dataplane dp0s5 {
address 172.16.19.90/24
policy {
qos PRIORITY_EF
}
}
dataplane dp0s6 {
}
dataplane dp0s7 {
address 10.0.0.90/24
}
loopback lo
}
policy {
qos {
name PRIORITY_EF {
shaper {
class 1 {
match RULE1 {
mark {
dscp ef
}
protocol udp
source {
address 172.16.9.7/32
}
}
match RULE2 {
mark {
dscp af11
}
protocol udp
source {
address 172.16.9.6/32
}
}
profile PROF1
}
default PROF1
profile PROF1 {
bandwidth 10Mbit
map {
dscp af11 {
to 1
}
dscp ef {
to 0
}
}
queue 0 {
traffic-class 0
}
queue 1 {
traffic-class 1
}
traffic-class 0 {
bandwidth 3Mbit
Operation check result
The verification result log below allows to confirm that packets of the priority traffic do not drop in the following case: in the process of traffic flow from virtual server 6 “172.16.9.6” in the verification configuration diagram to virtual server 8 “172.16.19.8”, the priority traffic is flowed from virtual server 7 “172.16.9.7” to virtual server 9 “172.16.19.9”, and then the total traffic exceeds the restrictive bandwidth (10 Mbps). (* See the virtual server 7 verification result log/ Vserver9 verification result log.)
At that time, it was also confirmed that packets of non-priority traffic dropped. (* See the virtual server 6 verification result log/ Vserver8 verification result log.)
<Priority traffic verification log>
Virtual server 7 verification result log
[user1@vserver7 ~]$ iperf -c 172.16.19.9 -u -b 9.3M -t 60
[user1@vserver7 ~]$
[user1@vserver7 ~]$
[user1@vserver7 ~]$
[user1@vserver7 ~]$
[user1vserver7 ~]$
[user1@vserver7 ~]$
[user1@vserver7 ~]$
[user1@vserver7 ~]$
[user1@vserver7 ~]$ iperf -c 172.16.19.9 -u -b 2.3M -t 30
------------------------------------------------------------
Client connecting to 172.16.19.9, UDP port 5001
Sending 1470 byte datagrams, IPG target: 5113.04 us (kalman adjust)
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 172.16.9.7 port 58006 connected with 172.16.19.9 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-30.0 sec 8.23 MBytes 2.30 Mbits/sec
[ 3] Sent 5869 datagrams
[ 3] Server Report:
[ 3] 0.0-30.1 sec 8.23 MBytes 2.29 Mbits/sec 3.804 ms 0/ 5869 (0%)
Virtual server 9 verification result log
[user1@vserver9 ~]$
[user1@vserver9 ~]$ iperf -s -u
------------------------------------------------------------
Server listening on UDP port 5001
Receiving 1470 byte datagrams
UDP buffer size: 208 KByte (default)
------------------------------------------------------------
[ 3] local 172.16.19.9 port 5001 connected with 172.16.9.7 port 58006
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 3] 0.0-30.1 sec 8.23 MBytes 2.29 Mbits/sec 3.804 ms 0/ 5869 (0%)
<Non-priority traffic verification log>
Virtual server 6 verification result log
[user1@vserver6 ~]$ iperf -c 172.16.19.8 -u -b 9.3M -t 60
------------------------------------------------------------
Client connecting to 172.16.19.8, UDP port 5001
Sending 1470 byte datagrams, IPG target: 1264.52 us (kalman adjust)
UDP buffer size: 208 KByte (default)
-----------------------------------------------------------
[ 3] local 172.16.9.6 port 56259 connected with 172.16.19.8 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-60.0 sec 66.5 MBytes 9.30 Mbits/sec
[ 3] Sent 47450 datagrams
[ 3] Server Report:
[ 3] 0.0-60.0 sec 58.9 MBytes 8.22 Mbits/sec 0.898 ms 5468/47450 (12%)
Virtual server 8 verification result log
