Sample Munged Qos Profile Process; Figure 36: Munged Profile Example - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - QUALITY OF SERVICE CONFIGURATION GUIDE 2010-09-22 Configuration Manual

Sample Munged QoS Profile Process

Copyright © 2010, Juniper Networks, Inc.
After the munged QoS profile is complete, the router reprocesses the queues for all
forwarding interfaces in the scope of the attachment, adding, deleting, or modifying the
scheduler hierarchy as required by the munged QoS profile rules. Conflicting node rules
operate differently than this.
With conflicting node rules, the mungeing algorithm for QoS nodes start at the base of
the interface hierarchy (usually near the physical interface), instead of at the top of the
interface column. If a QoS profile is not attached to the port, nodes are added to the
interface column according to the QoS port-type profile. Nodes are subsequently added
from profiles that are attached higher in the interface column until all node rules from
the interface column have been added, or the maximum hierarchy of three nodes has
been reached. Higher level nodes can not eclipse lower-attached nodes. For example, if
a QoS hierarchy is Ethernet node > Ethernet group node > VLAN node > queue, an IP
node from a higher-attached QoS profile cannot eclipse the VLAN node.
In Step 3, the router must decide which rules from a QoS profile conflict with rules already
contained within the munged QoS profile. Queue rules are identified by their {interface
type, traffic class} pair; two queue rules with the same interface type and traffic class
are deemed conflicting. Node rules are identified by their {interface type, traffic-class
group} pair; two node rules with the same interface type and traffic-class group are
deemed conflicting.
NOTE: The munge algorithm is modified when you configure QoS for 802.3ad
link aggregation interfaces.
Figure 36 on page 131 shows the relationship between a port-attached QoS profile and
a QoS profile that is attached to the specific interface, ATM 11/0.2.

Figure 36: Munged Profile Example

The port-attached QoS profile on ATM 11.0 contains the following queue rule:
host1(config)#qos-profile atmPort
host1(config-qos-profile)#ip queue traffic-class priority-data scheduler-profile 64kbps
host1(config-qos-profile)#exit
Chapter 16: Configuring and Attaching QoS Profiles to an Interface
131