Quality of Service Commands on the Cisco IOS XR Software
On ingress, you cannot use the bandwidth command to set the minimum bandwidth guarantee. Therefore,
the bandwidth remaining command is used to proportionally allocate bandwidth to the particular classes,
but there is no reserved bandwidth capacity.
Note
On ingress, the interface reference value is the Layer 3 capacity of the interface.
On both ingress and egress, if the bandwidth remaining command is not present, then the bandwidth is
shared equally among the configured queueing classes present in the policy-map. When attempting precise
calculations of expected MDRR behavior, you must bear in mind that because you are dealing with the
bandwidth remaining on the link, you must convert the values to the bandwidth remaining percentages on the
link, based upon the packet sizes of the traffic within the class. If the packet sizes are the same in all the
classes, then the defined ratio is enforced precisely and predictably on the link.
On ATM subinterfaces, only one bandwidth action can be configured in a class.
Task ID
Task ID
qos
Examples
In the following example, remaining bandwidth is shared by classes class1 and class2 in a 20:80 ratio.
RP/0/RP0/CPU0:router(config)# policy-map policy1
RP/0/RP0/CPU0:router(config-pmap)# class class1
RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth remaining percent 20
RP/0/RP0/CPU0:router(config-pmap-c)# exit
RP/0/RP0/CPU0:router(config-pmap)# class class2
RP/0/RP0/CPU0:router(config-pmap-c)# bandwidth remaining percent 80
OL-23235-03
Cisco IOS XR Modular Quality of Service Command Reference for the Cisco CRS Router, Release 4.0
Operations
read, write
bandwidth remaining
9