See below:Ībove you’ll notice I’m using NBAR options to help match specific traffic by protocols. One thing to keep in mind is that difference values at the same level of CoS can have a difference Drop Probability. Routing is CS6 in Cisco’s documentation which falls under Critical Data, so we placed BGP in Critical Data but we are tagging it with AF31. You can see for Network Mgmt they recommend CS2 and above we have SSH set to CS2 in Preferred Data since that’s where CS2 belongs (look at the SP’s settings). Below is a snapshot of Cisco’s best practices: Try to follow best practices when you can. Match access-group name CRITICAL-APPS_ACLĬlass-map match-any PREFERRED-DATA :SSH was put here so that the IT staff can still have remote access to their devices to help troubleshootĪgain this is just an example but you can customize it to fit your environment. Ip access-list extended CRITICAL-APPS_ACL :A nice ACL to prioritize critical applicationsĬlass-map match-any INTERACTIVE-VOICE :Voice is Voice and always need to be the highest prioritizedĬlass-map match-any CRITICAL-DATA :Here's where you need to do some homework and find out what's critical in your environment and put it here So now if I want to throw something together, it would look like this: Below was an option from one of our providers: You can’t just turn it on and it works like some people think. It’s critical that you match DSCP Names/Values with what they have configured or else it won’t work. Work with your provider to find out what options you have.

Maplestroy terminal packet sender