There are three main components that make up the MQC (Modular QoS CLI) and are listed below:
- class-map – This is used as a classification filter defined within the policy map to identify traffic for preferential or deferential treatment. Traffic can be identified by IPP or DSCP, named or numbered ACL, Network-Based Application Recognition (NBAR), Layer 2 parameters (CoS, FR DE, ATM cell loss priority [CLP], MPLS Experimental [EXP] value), or combination of all of these.
- policy-map – This is used as a statement that defines how each traffic type, as identified by the class map(s), should be serviced. Options include marking/re-marking, policing, shaping, low-latency or class-based weighted fair queuing, selective dropping, and header compression.
- service-policy – This is used as a statement that binds the policy to an interface and specifies direction
For example:
ip access-list extended VOICE-RTP permit udp 192.168.1.0 0.0.0.255 any range 16384 32767 ip access-list extended VOICE-SIGNALING permit tcp 192.168.1.0 0.0.0.255 any range 2000 2002 ! class-map match-all VOICE-SIGNALING match access-group name VOICE-SIGNALING class-map match-all VOICE-RTP match access-group name VOICE-RTP ! policy-map VOICE class VOICE-RTP set dscp ef class VOICE-SIGNALING set dscp cs3 ! interface Vlan10 description Voice VLAN service-policy input VOICE ! end
References
Cisco QoS Exam Certification Guide (IP Telephony Self-Study) (2nd Edition)
End-to-End QoS Network Design: Quality of Service in LANs, WANs, and VPNs
Disclosure
NetworkJutsu.com is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.
