1. Define a class-map: The first step in MQC deployment is to identify the interesting traffic (classifying the
packets). This step defines groupings of network traffic by using various classification tools, such as ACLs,
IP addresses, IP precedence, IP Differentiated Services Code Point (DSCP) values, IEEE 802.1p, MPLS EXP,
and Cisco Network-Based Application Recognition (NBAR) technology.
2. Define a policy-map: After the traffic has been identified, a policy-map dictates what action is to be
taken. This step can be considered the actual construction of an MQC through use of a policy-map to
perform specific functions. Examples of functions are queuing, dropping, policing, shaping, bandwidth
control, or marking IP precedence or DSCP values.
3. Apply the policy-map: The final step is to apply the policy-map to the desired interfaces or
subinterfaces. Each interface can have up to two policy-maps applied, each in one direction (inbound and
outbound).
Figure 7-7. Configuring Modular QoS CLI (MQC)
The show policy-map interface
command can be used to display the packet statistics of
all classes that are configured for all service policies on the specified interface.
Pages:
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379