Cisco Cisco IOS Software Release 12.2(27)SBC

Pagina di 24
MQC Hierarchical Queuing with 3 Level Scheduler
  How to Configure Bandwidth-Remaining Ratios
6
Three-Level Scheduler Using MQC Hierarchical Queuing Framework
The priority traffic of one logical interface cannot only impose burstiness on other traffic, but also starve 
other traffic. The only way to prevent the starvation of other traffic is by configuring a policer on the 
priority queue by limiting the percent of priority traffic to less than 90 percent of the parent bandwidth 
and the port bandwidth. 
Configuration Granularity
 describes the configuration granularity for the three-level scheduler.
How to Configure Bandwidth-Remaining Ratios
To configure bandwidth-remaining ratios on subinterface-level and class-level queues, see the 
Distribution of Remaining Bandwidth Using Ratio, Release 12.2(31)SB2 feature module.
Configuration Examples for the Three-Level Scheduler
This section provides the following configuration examples:
Bandwidth Allocation—Policy Attached to an Interface: Example
The following example configuration consists of one policy map named Child with the following traffic 
classes defined: prec0, prec2, and class-default. The policy is attached to the ATM interface 1/0/0, which 
has a configured rate of 1000 kbps.
policy-map Child
class prec0
bandwidth 300
class prec2
bandwidth 100
class class-default
bandwidth 50
!
interface atm 1/0/0
bandwidth 1000
service-policy output Child
Table 3
Three-Level Scheduler Configuration Granularity
Interface Bandwidth
Granularity
Less than or equal to 2 Mbps
.4%
Greater than 2 Mbps and less than 1 Gbps
.2%
Greater than or equal to 1 Gbps
.1%