59
•
On some cards, QoS policies can be applied but cannot take effect due to limited system
resources. In this case, you can adjust related parameters (for example, reducing the number of
queues) according to system prompt and then apply a QoS policy again.
Configuration procedure
To apply a policy to an interface or ATM PVC:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view or PVC
view.
•
Enter
interface
view:
interface
interface-type
interface-number
•
Enter PVC view:
a. interface atm
interface-number
b. pvc
vpi/vci
Settings in interface view take
effect on the current interface.
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
•
Hewlett Packard Enterprise 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 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 max-bandwidth
command configured, if the sum of sub-channel bandwidth
equals to or exceeds the sum of AF bandwidth and EF bandwidth, AF and EF calculate
bandwidth based on the actual interface bandwidth. Otherwise, AF and EF calculate bandwidth
based on 1 Gbps of bandwidth, and the message indicating insufficient bandwidth is displayed.
In the latter case, the queuing function might fail to take effect.
•
On tunnel interfaces, subinterfaces, Layer 3 aggregate interfaces, HDLC link bundle interfaces,
RPR logical interfaces, or VT interfaces using PPPoE, PPPoA, or PPPoEoA at the data link
