Juniper JUNOSE 11.1.X - QUALITY OF SERVICE CONFIGURATION GUIDE 3-21-2010, Configuration Manual

Page: 170 / 398

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
All forwarding interfaces stacked above the port are within the scope of the
attachment, so all IP interfaces stacked above the port will be provisioned with a
queue in the priority-data traffic class, shaped to 64 Kbps.
The QoS profile attached at subinterface ATM 11/0.2 contains the following two rules:
host1(config)# qos-profile atmVc
host1(config-qos-profile)# ip queue traffic-class priority-data scheduler-profile 1mbps
host1(config-qos-profile)# ip queue traffic-class voice-over-ip
host1(config-qos-profile)# exit
The queue rule for {interface type IP, traffic-class priority-data} in the QoS profile
that is attached to ATM 11/0.2 effectively overrides the queue rule for the same
interface type and traffic class in the port-attached QoS profile on ATM11.0.
The second queue rule, which is for the voice-over-ip traffic-class, is not conflicting.
In this configuration, the provider has configured a 64 Kbps priority-data queue for
each IP interface stacked above the port. But the IP interface above the ATM 11/0.2
attachment provides 1 Mbps for priority-data, and also has a second queue provisioned
for VoIP.
NOTE: When a QoS profile is attached to an interface, the router first searches to
determine if a munged QoS profile already exists. If you modify an existing QoS
profile, the router automatically updates all munged QoS profiles that are dependent
on the modified profile.
138 ■
Munged QoS Profile Overview
JUNOSe 11.1.x Quality of Service Configuration Guide