R2511-HP MSR Router Series ACL and QoS Configuration Guide(V5)

62
• An inbound QoS policy cannot contain a GTS action or any of these queuing actions: queue ef,
queue af, or queue wfq.
• You must enable the rate limit function for the queuing function to take effect on these interfaces:
tunnel interfaces, subinterfaces, HDLC link bundle interfaces, and VT/dialer interfaces configured
with PPPoE, PPPoA, PPPoEoA, PPPoFR, or MPoFR (frame relay traffic shaping is not enabled on the
frame relay interface). At the same time, you must configure the qos max-bandwidth command to
provide base bandwidth for CBQ bandwidth calculation.
Configuration procedure
To apply a policy to an interface or ATM PVC:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter interface view, port
group view, or PVC view.
• Enter interface view:
interface interface-type
interface-number
• Enter port group view:
port-group manual
port-group-name
• Enter PVC view:
a. interface atm
interface-number
b. pvc vpi/vci
Settings in interface view take
effect on the current interface.
Settings in port group view take
effect on all ports in the port
group. Settings in PVC view take
effect on the current PVC.
3. Apply a policy to the interface
or PVC.
qos apply policy policy-name
{ inbound | outbound }
N/A
Configuring the maximum available interface bandwidth
The maximum available interface bandwidth refers to the maximum interface bandwidth used for
bandwidth check when CBQ enqueues packets, rather than the actual bandwidth of the physical
interface.
Configuration guidelines
• HP recommends that you configure the maximum available interface bandwidth to be smaller than
the actual available bandwidth of the physical interface or logical link.
• On a primary channel or template interface (such as dialer, BRI, PRI, or VT) configured with the qos
max-bandwidth command, AF and EF queues perform queue bandwidth check and calculation
based on the bandwidth specified with the qos max-bandwidth command, so do the AF and EF
queues synchronized to the sub-channel interfaces (for example, VA interfaces or B channels).
Sub-channel interface bandwidth is ignored. Because the QoS configurations of the primary
channel interface and the sub-channel interfaces are the same, prompts are output only for the
primary channel interface. If the qos max-bandwidth command is not configured, AF and EF
queues on the primary channel interface calculate queue bandwidth based on 1 Gbps of
bandwidth, and AF and EF queues synchronized to the sub-channel interfaces calculate queue
bandwidth based on actual sub-channel interface bandwidth. If queuing on a sub-channel interface
fails due to bandwidth change, the prompt will be output for the sub-channel interface.
• On an MP-group interface or MFR interface configured with the qos max-bandwidth command, AF
and EF perform queue bandwidth check and calculation based on the bandwidth specified with the
qos max-bandwidth command. On an MP-group interface or MFR interface without the qos