Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an equal chance of being dropped. When you configure the QoS feature, you can select specific network traffic, prioritize it according to its relative importance, and use congestion-management and congestion-avoidance techniques to provide preferential treatment. Implementing QoS in your network makes network performance more predictable and bandwidth utilization more effective. The QoS implementation is based on the Differentiated Services (Diff-Serv) architecture, an emerging standard from the Internet Engineering Task Force (IETF). This architecture specifies that each packet is classified upon entry into the network. The following Figure shows the model of the QoS.<\/p>\n
Classification is the process of distinguishing one kind of traffic from another by examining the fields in the packet. Classification is enabled only if QoS is globally enabled on the switch. By default, QoS is globally disabled, so no classification occurs. During classification, the switch performs a lookup and assigns a QoS label to the packet. The QoS label identifies all QoS actions to be performed on the packet and from which queue the packet is sent. The QoS label is based on the DSCP or the CoS value in the packet and decides the queueing and scheduling actions to perform on the packet. The label is mapped according to the trust setting and the packet type. Trust CoS:<\/p>\n
Trust DSCP\uff1a<\/p>\n
No trust\uff1a<\/p>\n
Policing(Ingress) The ingress policer meters the given flow and classifies as either in-profile or out-of-profile. Out-of-profile packets may be discarded or have their QOS attributes remarked.<\/p>\n
After a packet is classified and has a DSCP-based or CoS-based QoS label assigned to it, the marking process can begin. For packets with CoS labels\uff1a<\/p>\n
Generally, there are 8 queues for QoS exit, which map the 0-7 priority relationship of CoS. The packet enters the corresponding egress queue according to the final marked CoS and CoS-to-Queue relationship. For the priority of packet processing in the egress queue, there are the following algorithms:<\/p>\n
Policing(Egress) The egress policer meters the given flow and classifies as either in-profile or out-of-profile. Out-of-profile packets may be discarded.<\/p>\n
SWITCH(config)#mls qos enable<\/code><\/pre>\nSWITCH(config)#no mls qos<\/code><\/pre>\nEnabling QoS Globally. Default is disabled.<\/p>\n
SWITCH(config)#mls qos algorithm {sp | wrr}<\/code><\/pre>\nConfiguring the queue scheduling algorithm, support two modes: wrr and sp.<\/p>\n
SWITCH(config)#mls qos weight <0-7> <0-32><\/code><\/pre>\nConfigure the queue weight. The queue weight is only valid for wrr mode. The default weight of all queues is 1. When in wrr mode, configure the queue weight to 0, the queue will schedule in sp mode.<\/p>\n
SWITCH(config-if)#mls qos trust {cos | dscp}<\/code><\/pre>\nSWITCH(config-if)#no mls qos trust<\/code><\/pre>\nConfigure the port trust mode, the default is not trust mode. When in no trust mode, the CoS field and DHCP field of the packet will be modified according to the default CoS of the port. When in trust cos mode, the same as the no trust mode for untagged packets, and for tagged packets, use the own CoS of the packet. When configuring trust dscp mode, for ip packets, select the packet with DSCP, and for non-ip packets, the same as trust cos mode.<\/p>\n
SWITCH(config-if)#mls qos cos <0-7><\/code><\/pre>\nSWITCH(config-if)#no mls qos cos<\/code><\/pre>\nConfigure the default CoS of the port. The default CoS takes effect for the ingress packets without tags. The default port cos is 0.<\/p>\n
SWITCH(config)#mls qos cos-dscp <0-63> <0-63> <0-63> <0-63> <0-63> <0-63> <0-63> <0-63><\/code><\/pre>\nSWITCH(config)#no mls qos cos-dscp<\/code><\/pre>\nConfigure CoS-to-DSCP mapping. Default CoS-to-DSCP mapping: 0-0, 1-8, 2-16, 3-24, 4-32, 5-40, 6-48, 7-56.<\/p>\n
SWITCH(config)#mls qos cos-queue <0-7> <0-7><\/code><\/pre>\nSWITCH(config)#no mls qos cos-queue <0-7><\/code><\/pre>\nConfigure CoS-to-Queue mapping. Default CoS-to-Queue mapping: 0-0, 1-1, 2-2, 3-3, 4-4, 5-5, 6-6, 7-7.<\/p>\n
Note<\/h2>\n
When the configured port is no trust, trust cos or trust dscp and the port is not ip: the cos-dscp configuration takes effect, modify the packet dscp according to the mapping relationship, and the cos-queue configuration takes effect, modify the packet export queue according to the mapping relationship.<\/p>\n
\n- Configuring DSCP-to-CoS Mapping<\/li>\n<\/ul>\n
SWITCH(config)#mls qos dscp-cos <0-63> to <0-7><\/code><\/pre>\nSWITCH(config)#no mls qos dscp-cos<\/code><\/pre>\nConfigure DSCP-to-CoS mapping. Default DSCP-to-CoS mapping: <0-7>-0, <8-15>-1, <16-23>-2, <24-31>-3, <32-39>-4, <40-47>- 5, <48-55>-6, <56-63>-7.<\/p>\n
SWITCH(config)#mls qos dscp-mutation <0-63> to <0-63><\/code><\/pre>\nSWITCH(config)#no mls qos dscp-mutation<\/code><\/pre>\nConfigure DSCP-to-DSCP mapping.<\/p>\n
SWITCH(config)#mls qos dscp-queue <0-63> <0-7><\/code><\/pre>\nSWITCH(config)#no mls qos dscp-queue <0-63><\/code><\/pre>\nConfigure DSCP-to-Queue mapping. Default DSCP-to-Queue mapping: <0-7>-0, <8-15>-1, <16-23>-2, <24-31>-3, <32-39>-4, <40-47>- 5, <48-55>-6, <56-63>-7.<\/p>\n
Note<\/h2>\n
When configuring the port as trust dscp and ip packets: the dscp-cos configuration takes effect, modify the packet dscp according to the mapping relationship, and the dscp-queue configuration takes effect, and modify the packet egress queue according to the mapping relationship. When a colleague configures dscp-dscp at the same time, first perform dscp-dscp conversion, and then perform dscp-cos mapping as a result.<\/p>\n
\n- Creating Class-map<\/li>\n<\/ul>\n
SWITCH(config)#class-map CNAME<\/code><\/pre>\nSWITCH(config-cmap)#<\/code><\/pre>\nSWITCH(config)#no class-map CNAME<\/code><\/pre>\nCreate class-map. After creating a class-map, automatically enter the class-map mode.<\/p>\n
SWITCH(config-cmap)# match access-group ACLNAME<\/code><\/pre>\nSWITCH(config-cmap)#no match access-group ACLNAME<\/code><\/pre>\nConfigure to match ACL entries for class-map.<\/p>\n
SWITCH(config-cmap)#match ip-dscp <0-63><\/code><\/pre>\nSWITCH(config-cmap)#no match ip-dscp<\/code><\/pre>\nConfigure to match the DHCP field in the IP packet, up to 64 different DHCP values \u200b\u200bcan be configured.<\/p>\n
SWITCH(config-cmap)#match cos <0-7><\/code><\/pre>\nSWITCH(config-cmap)#no match cos<\/code><\/pre>\nConfigure to match the CoS field in the packet, up to 8 different CoS values \u200b\u200bcan be configured.<\/p>\n
SWITCH(config-cmap)#match ethertype ETYPE<\/code><\/pre>\nSWITCH(config-cmap)#no match ethertype<\/code><\/pre>\nConfigure to match the ethernet protocol type field of the packets.<\/p>\n
SWITCH(config-cmap)#match {vlan <1-4094> | vlan-range <1-4094> to <1-4094>}<\/code><\/pre>\nSWITCH(config-cmap)#no match {vlan | vlan-range}<\/code><\/pre>\nConfigure to match vlan field in the packet, support range configuration.<\/p>\n
SWITCH(config-cmap)#match layer4 {tcp | udp} {source-port | destination-port} VALUE<\/code><\/pre>\nSWITCH(config-cmap)#no match layer4 {tcp | udp} {source-port | destination-port} VALUE<\/code><\/pre>\nConfigure to match Layer 4 port fields of TCP and UDP packets.<\/p>\n
SWITCH(config-cmap)#match vlan-range <1-4094> to <1-4094> ethertype ETYPE<\/code><\/pre>\nSWITCH(config-cmap)#no match vlan-range<\/code><\/pre>\nConfigure to match vlan and etype fields in the packets.<\/p>\n
SWITCH(config)#policy-map PNAME<\/code><\/pre>\nSWITCH(config-pmap)#<\/code><\/pre>\nSWITCH(config)#no policy-map PNAME<\/code><\/pre>\nConfigure policy-map<\/p>\n
SWITCH(config-pmap)# class CNAME<\/code><\/pre>\nSWITCH(config-pmap-c)#<\/code><\/pre>\nSWITCH(config-pmap)#no class CNAME<\/code><\/pre>\nAttach class-map to policy-map. A policy-map can attach up to 8 class-maps.<\/p>\n
SWITCH(config-pmap-c)#set cos <0-7><\/code><\/pre>\nSWITCH(config-pmap-c)#no set cos<\/code><\/pre>\nConfigure policy action: modify the cos field of packets.<\/p>\n
SWITCH(config-pmap-c)#set ip-dscp <0-63><\/code><\/pre>\nSWITCH(config-pmap-c)#no set ip-dscp<\/code><\/pre>\nConfigure policy action: modify the ip-dscp field of packets.<\/p>\n
SWITCH(config-pmap-c)#set vlan <1-4094><\/code><\/pre>\nSWITCH(config-pmap-c)#no set vlan<\/code><\/pre>\nConfigure policy action: modify packet vlan.<\/p>\n
SWITCH(config-pmap-c)#nest vlan <1-4094><\/code><\/pre>\nSWITCH(config-pmap-c)#no nest vlan<\/code><\/pre>\nConfigure policy action: add external tags to matching packets.<\/p>\n
SWITCH(config-pmap-c)#police cir <32-1000000> cbs <4-31250> exceed-action drop<\/code><\/pre>\nSWITCH(config-pmap-c)#no police<\/code><\/pre>\nConfigure policy action: rate-limit. Cir is the speed limit water line, in kbps. Cbs is burst capacity, unit Kbyte.<\/p>\n
Note<\/h2>\n
The value of cir is determinable. For example, if the speed limit is 1M, then the value of cir is 1024, but the value of cbs is taken from the empirical value. When the cbs value is set large, the flow peak is higher, and the speed limit is stable, but the average speed may be higher than the speed limit value; when the cbs value is set small, the flow peak is lower, the speed limit fluctuates greatly, and the average speed may be lower than the speed limit value. It is recommended that the cbs configuration take 4 times the value of cir.<\/p>\n
\n- Applying Policy-map on the Interface<\/li>\n<\/ul>\n
SWITCH(config-if)#service-policy input PNAME<\/code><\/pre>\nSWITCH(config-if)#no service-policy input PNAME<\/code><\/pre>\nApply the policy-map on the interface. Only one policy-map can be applied to an interface.<\/p>\n
SWITCH(config-if)#rate-limit input <64-1000000> <32-16384><\/code><\/pre>\nSWITCH(config-if)#no rate-limit input<\/code><\/pre>\nConfigure port ingress rate limit. The first parameter is limit level, in kbps. The second parameter is burst level, in Kbyte.<\/p>\n
SWITCH(config-if)#rate-limit output <64-1000000> <32-16384><\/code><\/pre>\nSWITCH(config-if)#no rate-limit output<\/code><\/pre>\nConfigure port egress rate limit. The first parameter is limit value, in kbps. The second parameter is burst value, in Kbyte.<\/p>\n
Note<\/h2>\n
The limit value is determinable. For example, if the speed limit is 1M, then the limit value is 1024, but the burst value is taken from the experience value. When the burst value is large, the flow peak is higher, and the speed limit is stable, but the average rate may be higher than the speed limit value; when the burst value is small, the flow peak is lower, the speed limit fluctuates greatly, and the average rate may be lower than the speed limit value. . It is recommended that the burst configuration be 4 times the limit value.<\/p>\n
Examples<\/h2>\n
Example 1: This example shows how to Configure ingress and egress rate-limit on the interface. Step 1: Configuring Ingress rate-limit on interface gigabitEthernet0\/1.<\/p>\n
SWITCH(config-if)#rate-limit input 1024 4096<\/code><\/pre>\nStep 2: Configuring Egress rate-limit on interface gigabitEthernet0\/1.<\/p>\n
SWITCH(config-if)#rate-limit output 1024 4096<\/code><\/pre>\nExample 2: This example shows how to configure flow-based rate-limit. Step 1: Enable QoS globally.<\/p>\n
SWITCH(config)#mls qos enable<\/code><\/pre>\nStep 2\uff1aCreate ACL rule.<\/p>\n
SWITCH(config)#ip-access-list 1 permit 192.168.64.1<\/code><\/pre>\nStep 3\uff1aCreate class-map, policy-map, attach ACL to the class-map, attach class-map to the policy-map, and configure the policy-map action.<\/p>\n
SWITCH(config)#class-map c1<\/code><\/pre>\nSWITCH(config-cmap)#match access-group 1<\/code><\/pre>\nSWITCH(config-cmap)#exit<\/code><\/pre>\nSWITCH(config)#policy-map p1<\/code><\/pre>\nSWITCH(config-pmap)#class c1<\/code><\/pre>\nSWITCH(config-pmap-c)#police cir 1024 cbs 4096 exceed-action drop<\/code><\/pre>\nStep 4: Apply policy-map to the interface.<\/p>\n
SWITCH(config)#interface gigabitEthernet0\/1<\/code><\/pre>\nSWITCH(config-if)#service-policy input p1<\/code><\/pre>\nExample 3: This example shows how to configure port-based QoS service, to Implement preferential forwarding of specific port packets. Step 1: Enable QoS globally.<\/p>\n
SWITCH(config)#mls qos enable<\/code><\/pre>\nStep 2: Configure interface gigabitEthernet0\/1 and gigabitEthernet0\/2 trust cos. Set gigabitEthernet0\/1 default CoS to 0. Set gigabitEthernet0\/2 default CoS to 2.<\/p>\n
SWITCH(config)#interface gigabitEthernet0\/1<\/code><\/pre>\nSWITCH(config-if)#mls qos trust cos<\/code><\/pre>\nSWITCH(config-if)#mls qos cos 0<\/code><\/pre>\nSWITCH(config-if)#exit<\/code><\/pre>\nSWITCH(config)#interface gigabitEthernet0\/2<\/code><\/pre>\nSWITCH(config-if)#mls qos trust cos<\/code><\/pre>\nSWITCH(config-if)#mls qos cos 2<\/code><\/pre>\nStep 3: Configure CoS-to-Queue mapping.<\/p>\n
SWITCH(config)#mls qos cos-queue 0 0<\/code><\/pre>\nSWITCH(config)#mls qos cos-queue 2 2<\/code><\/pre>\nStep 4: Configure scheduling algorithm wrr.<\/p>\n
SWITCH(config)#mls qos algorithm wrr<\/code><\/pre>\nStep 5: Configuring queue 2 weight 0.<\/p>\n
SWITCH(config)#mls qos weight 2 0<\/code><\/pre>\nDisplay Information<\/h2>\n\n- Display Scheduling Algorithm and Weight Information<\/li>\n<\/ul>\n
SWITCH#show mls qos algorithm<\/code><\/pre>\nMls qos algorithm is WRR. Queue-id 0 1 2 3 4 5 6 7 Weight 1 1 1 1 1 1 1 1<\/p>\n
SWITCH#show mls qos cos-maps<\/code><\/pre>\n—————————-<\/p>\n
Cos Dscp Queue<\/h2>\n
—————————- 0 0 0 1 8 1 2 16 2 3 24 3 4 32 4 5 40 5 6 48 6 7 56 7<\/p>\n
\n- Display DSCP-to-CoS, DSCP-to-DSCP and DSCP-to-Queue Mapping Information<\/li>\n<\/ul>\n
SWITCH#show mls qos dscp-maps<\/code><\/pre>\n——————————————<\/p>\n
Dscp Cos Mutation Queue<\/h2>\n
—————————————— 0 0 0 0 1 0 1 0 2 0 2 0 3 0 3 0 4 0 4 0 5 0 5 0 6 0 6 0 7 0 7 0 8 1 8 1 9 1 9 1 10 1 10 1 11 1 11 1 12 1 12 1 13 1 13 1 14 1 14 1 15 1 15 1<\/p>\n
\n- Display QoS Configuration on the Interfaces<\/li>\n<\/ul>\n
SWITCH#show mls qos interfaces<\/code><\/pre>\n——————————-<\/p>\n
Interface Trust mode Cos<\/h2>\n
——————————- GiE0\/1 Not 0 GiE0\/2 Not 0 GiE0\/3 Not 0 GiE0\/4 Not 0 GiE0\/5 Not 0 GiE0\/6 Not 0 GiE0\/7 Not 0 GiE0\/8 Not 0<\/p>\n
\n- Display Class-map Configuration<\/li>\n<\/ul>\n
SWITCH#show class-map<\/code><\/pre>\nCLASS-MAP-NAME: c1 Match Cos: 3<\/p>\n
SWITCH#show policy-map<\/code><\/pre>\nPOLICY-MAP-NAME: p1 State: detached CLASS-MAP-NAME: c1 Match Cos: 3 Police: Mode: SrTCM cir (1024 Kbps) cbs (4096 KBytes) exceed-action (drop)<\/p>\n
SWITCH#show rate-limit<\/code><\/pre>\n——————————————————-<\/p>\n
Interface In limit In burst Out limit Out burst<\/h2>\n
——————————————————- GiE0\/1 — — — — GiE0\/2 — — — — GiE0\/3 1024 4096 — — GiE0\/4 — — — — GiE0\/5 — — — — GiE0\/6 — — — — GiE0\/7 — — — — GiE0\/8 — — — — GiE0\/9 — — — — GiE0\/10 — – 1024 4096<\/p>\n","protected":false},"excerpt":{"rendered":"
Networking \u203a Switching \u203a Edge \u203a Synapse<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":6349,"menu_order":19,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[115,119,116],"class_list":["post-6368","docs","type-docs","status-publish","hentry","doc_tag-connexite","doc_tag-network","doc_tag-synapse-cli-documentation","no-post-thumbnail"],"acf":[],"_links":{"self":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6368","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/comments?post=6368"}],"version-history":[{"count":1,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6368\/revisions"}],"predecessor-version":[{"id":6416,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6368\/revisions\/6416"}],"up":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6349"}],"wp:attachment":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/media?parent=6368"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/doc_tag?post=6368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}