14-28
Ethernet Card Software Feature and Configuration Guide, R7.2
January 2009
Chapter 14 Configuring Quality of Service
ML-Series Egress Bandwidth Example
For example, if 18x bandwidth is available after servicing priority uni cast traffic (CoS 5), then the
remaining bandwidth will be allocated as follows:
Unicast traffic with CoS 2 : 2x
Unicast traffic with CoS 7: 6x
Unicast default (without CoS 2, CoS 5, CoS 7): 9x
All multicast/broadcast (any CoS value): 1x
Example 14-17QoS with Priority and Bandwidth Configured without Priority Multicast
!
class-map match-all customer_voice
match cos 5
class-map match-all customer_data
match cos 7
class-map match-all customer_core_traffic
match cos 2
!
!
policy-map policy_egress_bandwidth
class customer_core_traffic
bandwidth 1000
class customer_voice
priority 1000
class customer_data
bandwidth 3000
class class-default
bandwidth 5000
!
!
interface POS0
no ip address
crc 32
service-policy output policy_egress_bandwidth
!
Case 2: QoS with Priority and Bandwidth Configured with Priority Multicast
In this case, only multicast traffic of CoS 3 is allocated a guaranteed bandwidth. This multicast traffic
will now participate in the queue along with other WRR queues. After servicing the customer_voice
traffic, the remaining interface bandwidth is utilized for WRR queues, such as customer_core_traffic,
customer_data, class-default, and multicast CoS 3 traffic in the ratio of 1:3:5:2.
At any given time, the sum of the bandwidth assigned cannot exceed the i nterface bandwidth (in kbps).
Example 14-18QoS with Priority and Bandwidth configured with Priority Multicast
cos priority-mcast 3 2000
!
class-map match-all customer_voice
match cos 5
class-map match-all customer_data
match cos 7
class-map match-all customer_core_traffic
match cos 2
!
!