b.
If there is no QoS profile attached at the port, then locate the QoS profile
indicated in the
qos-port-type-profile
command that corresponds to the
interface type of the port. For example, if the port is an ATM interface, the
default QoS port-type profile for type ATM is named atm-default. Add the
rules in the QoS port-type profile to the munged QoS profile.
The entries in the QoS profile specified in the corresponding
qos-port-type-profile
command have the lowest precedence.
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.
Sample Munged QoS Profile Process
Figure 36 on page 138 shows the relationship between a port-attached QoS profile
and a QoS profile that is attached to the specific interface, ATM 11/0.2.
Munged QoS Profile Overview
■
137
Chapter 16: Configuring and Attaching QoS Profiles to an Interface
Содержание JUNOSE 11.1.X - QUALITY OF SERVICE CONFIGURATION GUIDE 3-21-2010
Страница 6: ...vi...
Страница 24: ...xxiv List of Figures JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 28: ...xxviii List of Tables JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 33: ...Part 1 QoS on the E Series Router Quality of Service Overview on page 3 QoS on the E Series Router 1...
Страница 34: ...2 QoS on the E Series Router JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 44: ...12 Classifying Queuing and Dropping Traffic JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 76: ...44 Scheduling and Shaping Traffic JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 156: ...124 Monitoring QoS Scheduling and Shaping JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 162: ...130 Scaling Subscribers on the TFA ASIC with QoS JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 190: ...158 Interface Solutions for QoS JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 238: ...206 Monitoring QoS Configurations for L2TP JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 256: ...224 Managing Queuing and Scheduling with QoS Parameters JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 344: ...312 Monitoring and Troubleshooting QoS JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 388: ...356 Monitoring QoS Parameter Definitions JUNOSe 11 1 x Quality of Service Configuration Guide...
Страница 391: ...Part 8 Index Index on page 361 Index 359...
Страница 392: ...360 Index JUNOSe 11 1 x Quality of Service Configuration Guide...