R3303-HP HSR6800 Routers ACL and QoS Command Reference

65
qos apply policy (interface view)
Use qos apply policy to apply a QoS policy to an interface or PVC.
Use undo qos apply policy to remove the QoS policy.
Syntax
qos apply policy policy-name { inbound | outbound }
undo qos apply policy [ policy-name ] { inbound | outbound }
Views
Interface view, PVC view
Default command level
2: System level
Parameters
inbound: Inbound direction.
outbound: Outbound direction.
policy-name: Specifies a policy name, a string of 1 to 31 characters.
Usage guidelines
To successfully apply a policy to an interface or PVC, make sure that the total bandwidth assigned to AF
and EF in the policy is smaller than the available bandwidth of the interface or PVC. If the available
bandwidth of the interface or PVC is modified to a value smaller than the total bandwidth for AF and EF,
the applied policy is removed. For a policy to be applied in the inbound direction, the referenced traffic
behaviors must not be configured with commands queue af, queue ef, queue wfq, and gts.
Settings in interface view take effect on the current interface. Settings in PVC view take effect on the
current PVC.
A policy must be applied to an interface or PVC following these rules:
• You can apply a QoS policy configured with various QoS actions (such as remark, car, gts, queue
af, queue ef, queue wfq, and wred) to common physical interfaces, PVCs, and VT interfaces used
by Multilink PPP (MP).
• An inbound QoS policy cannot contain a GTS action or any of these queuing actions: queue ef,
queue af, or queue wfq.
On a primary channel interface (for example, VT, dialer, BRI, and PRI interfaces) configured with the qos
max-bandwidth command, AF and EF queues perform bandwidth check and calculation based on the
bandwidth specified in the qos max-bandwidth command, so do the AF and EF queues synchronized to
the sub-channel interfaces (for example, VA interfaces and B channels). In this case, the sub-channel
interface bandwidth is ignored. Because the primary channel interfaces and the sub-channel interfaces
are the same in QoS configurations, prompts are displayed for only the primary interface. If the qos
max-bandwidth command is not configured on a primary channel interface, AF and EF queues on the
primary channel interface performs bandwidth check and calculation based on bandwidth of 1 Gbps,
and AF and EF queues synchronized to sub-channel interfaces (for example, VA interfaces and B
channels) perform bandwidth check and calculation based on the actual bandwidth. If queuing on a
sub-channel interface fails due to bandwidth changes, the prompts are output for the sub-channel
interface.