![switch port mapping template switch port mapping template](https://www.netbraintech.com/ftp/CE60/OnlineHelp/image_image257.png)
Mls qos srr-queue input dscp-map queue 1 threshold 1 0 8 16 18 Mls qos srr-queue input priority-queue 2 bandwidth 30 Mls qos srr-queue input threshold 1 80 90 Following configuration commands will achieve this. 30% bandwidth allocated to Q2 & rest of 70% for the Q1. In my example all VoIP traffic (marked with EF) put into Q2 & all other traffic goes into Q1. Tx-(4q3t) (3t: Two configurable values and one fixed.)īased on the DSCP classification we can put traffic into different queues (Q1 & Q2). QoS scheduling: rx-(not configurable on per port basis), Always Q2 will be the priority queue & all your important traffic needs to map into that queue to get preferred services during congestion.” Show interface capabilities” command can be used to see particular interface queuing capability. In these platforms there will be two queues available for input direction with 3 threshold (1P1Q3T). Queues available in “Ingress” & “Egress” directions are hardware dependent. Once classified at the access layer you have to preserve that value across the network and need to trust DSCP value across the switch-switch trunk links and in any layer 3 links between distribution/core layers. If you want to verify the new settings use “ show mls qos maps ” command. In my example exceed traffic in DSCP 18,34,46 will be mark down to CS0 or DSCP 0″ mls qos map policed-dscp 18 34 46 to 0″. If traffic rate exceed 20Mbps that traffic will be markdown according to the values configured by” mls qos map policed-dscp” configuration command. I found following video by Kevin Wallace explained it very well. 8000 value represent number of bytes send within a given time interval at the line speed (over the time avg rate equivalent to 20Mbps). In addition to the classification, traffic can be policed to a required rate.(20 Mbps in this case). So default mapping can be changed by using “ mls qos maps cos-dscp 0 8 16 24 32 46 48 56″ In most cases CoS value 5 used for RTP traffic marking & should map to DSCP 46.
![switch port mapping template switch port mapping template](https://www.lansweeper.com/wp-content/uploads/2019/04/Switch-Port-Mapping-Tool.jpg)
This classified DSCP/CoS values will be re-write at the egress port depend on how cos-dscp map configured in the switch.
![switch port mapping template switch port mapping template](https://i.pinimg.com/originals/f6/9e/e9/f69ee9d5387f81af65d7fde2f39dc6f0.png)
It is customized version of the Cisco’s classification model to fit for our requirement. Five user defined traffic classes & 3 system defined (CS6,CS7 & CS0) traffic classes.
![switch port mapping template switch port mapping template](https://content.spiceworksstatic.com/service.community/p/post_images/0000029913/53d0014c/attached_image/Network_overview_3-13-14.jpeg)
Police 20000000 8000 exceed-action policed-dscp-transmitīelow is the classification model I used for our campus QoS deployment.
Switch port mapping template how to#
Following show how to reclassify traffic by using a policy-map. If we want to conditionally trust the packet’s marking value we can use ” mls qos trust device ” command in addition to the first command.The other option is to re-classify all traffic by using policy-map. “ mls qos trust ” command can be used to change this behavior. By default switch port will NOT trust any marking values of a IP packet & re-write to DSCP to 0. In layer 2, CoS (Class of Service) can be used to mark the traffic & in layer 3 IPP-IP Precedence or DSCP value can be used to classify traffic. Congestion Avoidance (WTD-Weighted Tail Drop)īest practice is to do Classification/Marking & Policing closer to the source itself (at the access layer switch port). Congestion Management (Queuing or Scheduling)Ĥ. Before configuring those, QoS needs to enable in these platforms using “ mls qos” global configuration command & you can verify it by using “ show mls qos” command. There are 4 main component of configuring QoS in wired network. From the CCIEW lab perspective I believe hardware platform for access layer would be C3560 (but this is same for 3750/2960 those are in my access layer in production network.) I thought of writing this post would help you/me to understand what it involve configuring QoS in access layer. Recently I designed a QoS template for our campus environment (3750 Access & 6500 for Core/Distribution).