[Contents] [Prev] [Next] [Index] [Report an Error]

QoS Profile Attachments

You can attach a QoS profile to an interface at the base of an interface hierarchy, or you can associate a QoS profile with all the ports of a certain interface type.

Attaching a Profile to an Interface

To attach a profile to an interface:

  1. Enter Interface Configuration mode for the interface.
    2. host1(config)#interface atm 1.0/1
  2. Attach a QoS profile to the interface. 
    3. host1(config-if)#qos-profile qosp-vc-queuing

atm-vp qos-profile

interface

qos-profile

Attaching a Profile to a Port Type

By default, the router attaches a QoS port-type profile to all ATM, Ethernet, serial, or server ports. The port-type profile supplies QoS information for all forwarding interfaces stacked above all ports of the associated interface type.

Instead of using the default port-type profile, you can explicitly attach a QoS profile to a port. The QoS profile overrides the default QoS port-type profile. The QoS profile associates queue profiles, drop profiles, statistics profiles, and scheduler profiles with interface types, and it applies to all interfaces stacked above ports of the associated type.

qos-port-type-profile

Munged QoS Profile

QoS profile attachments affect the queuing configuration of all the forwarding interfaces stacked above the attachment point. The subtree of the interface hierarchy stacked above the attachment point is the scope of the attachment. When multiple QoS profiles are attached beneath a forwarding interface, the forwarding interface lies in the scope of all the QoS profiles. Rules from all the QoS profiles are combined in a process called mungeing. The set of rules used for a given forwarding interface is called the munged QoS profile.

When a QoS profile is attached to an interface, the router searches the interface stack, from the point of attachment down to the port interface at the base of the interface hierarchy, to find all QoS profiles attached under that interface. The rules are combined to form the munged QoS profile. The router reconfigures queues for all forwarding interfaces in the scope of the attachment to conform to the munged profile.

The munge algorithm works as follows:

  1. Start with the rules in the QoS profile being attached.
  2. Traverse down the stack of interfaces until another QoS profile attachment is found.
  3. Add rules from the lower-attached QoS profile to the munged QoS profile. Conflicting rules from the lower-attached QoS profile are not added: rules in higher-attached QoS profiles override or eclipse rules in lower-attached QoS profiles.
  4. Repeat Steps 2 and 3 until a port interface is reached at the bottom of the interface stack.
  1. If there is a QoS profile attached at the port, add the profile's rules to the munged QoS profile, and the munge algorithm is then complete.
  2. 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.

Once 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.

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.

Example

Figure 33 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 33: 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.


[Contents] [Prev] [Next] [Index] [Report an Error]