Users Guide

OS10(config-pmap-c)# set qos-group 2
OS10(config-pmap-c)# police cir 100 pir 100
View policy-map
OS10(config)# do show policy-map
Service-policy (control-plane) input: example-copp-policy-map-name
Class-map (control-plane): example-copp-class-map-name
set qos-group 2
police cir 100 bc 100 pir 100 be 100
Configuration notes
Dell EMC PowerSwitch S4200-ON Series:
● Shaping does not support traffic less than 468 kbps. Configure the shaping rates in multiples of 468.
● In System Flow ACL, ARP request and ARP response packets share the same CPU queue.
● CPU queues support shaping instead of rate limiting.
● Port shaping, storm control rate shaping, and CoPP rates are converted to kbps internally, even when configured in pps.
Assign service-policy
Rate controlling the traffic towards CPU requires configuring the control-plane type policy. To enable CoPP, apply the defined
policy-map to CONTROL-PLANE mode.
1. Enter CONTROL-PLANE mode from CONFIGURATION mode.
control-plane
2. Define aninput type service-policy and configure a name for the service policy in CONTROL-PLANE mode.
service-policy input example-copp-policy-map-name
Assign control-plane service-policy
OS10(config)# control-plane
OS10(conf-control-plane)# service-policy input example-copp-policy-map-name
View control-plane service-policy
OS10(conf-control-plane)# do show qos control-plane
Service-policy (input): example-copp-policy-map-name
Re-map protocols to queues
On switches that have a fewer number of queues, multiple protocols are mapped to a single queue. OS10 allows you to re-map
the protocols to available queues depending on your needs.
NOTE: This feature is not supported on the S4200-ON and S5100-ON series platforms.
For example, if your deployment does not need multicast protocols, re-map the multicast protocols to another queue. And use
the original multicast queue, queue 2 for other protocols or applications that you need.
If the protocols or applications that your deployment needs share the same queue, re-map some of them to other queues that
are mapped to protocols or applications that are not required.
If your deployment uses only a few protocols or applications, you can re-map these protocols or applications to individual
queues. Also, you can change the buffer settings for the remaining queues that are mapped to unused protocols or applications.
Ensure that you transfer the allocated buffer space from such queues to the common pool, which is used for lossy or lossless
traffic.
If you re-map the protocols or applications to different queues when the system is operational, then until queue transition
completes, egress traffic flows through queue 0.
The following show commands display protocol-to-queue mapping:
Quality of service
1545