Configuring HQoS Based on a Main Interface
This section describes how to configure HQoS based on a main interface.
Context
When congestion occurs because the assured bandwidth of traffic exceeds the interface bandwidth, you can change the default CIR, PIR, CBS, PBS, and weight of user queues on a main physical interface, thereby relieving congestion. If all trunk member interfaces are on the same network processor (NP) of the same board, the trunk member interfaces share the bandwidth configured on the trunk interface. Otherwise, the rate limit of each trunk member interface is the one configured on the trunk interface. In this case, the rate limiting fails. Therefore, users need to configure a bandwidth distribution mode so that traffic is allocated to trunk member interfaces based on weights.
In VS mode, this configuration is supported only by the admin VS.
Procedure
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The interface view is displayed.
- Run user-queue cir cir-value [ [ pir pir-value ] | [ flow-queue flow-queue-name ] | [ user-group-queue group-name ] ] * { inbound | outbound } [ service-template template-name [ adjust-on-card ] ]
User queue scheduling parameters are configured to implement HQoS for user services.
- Run user-queue shaping ldp-traffic outbound
HQoS is configured to take effect for L3VPN, IP, VLL, VPLS, and EVPN traffic on the interface.
- (Optional) Run qos schedule-tree distribute-mode outbound
Weight-based bandwidth allocation for a trunk's member interfaces is configured for HQoS scheduling.
- (Optional) Run any of the following commands:
- To configure weight-based CAR bandwidth allocation, run the qos profile-car member-link-scheduler distribute command.
- To configure weight-based bandwidth allocation for outgoing HQoS services on a trunk's member interfaces, run the qos hqos-outbound member-link-scheduler distribute command.
- (Optional) Run user-queue shaping bgp-local-ifnet-traffic outbound
The HQoS function is enabled for the traffic carried by a BGP local IFNET tunnel on the interface.
After HQoS is configured on an outbound interface of a BGP local IFNET tunnel, if the outbound interface resides on a downstream board equipped with a non-eTM subcard, you need to perform this step to allow HQoS to take effect.
- Run qos default user-queue { cir cir-value | pir pir-value | cbs cbs-value | pbs pbs-value | weight weight-value } * outbound
The default user queue scheduling parameters are modified.
- Run commit
The configuration is committed.
- Run quit
Return to the system view.
- Run slot slot-id
The slot view is displayed.
- Run qos user-queue burst-size bytes min-bytes time burst-time
The minimum default burst size and burst time are configured for user queues.
- Run qos channel auto-adjust-quantity disable
The function of automatically adjusting the number of users on a channel is disabled.
- After the function of automatically adjusting the number of users on a channel is enabled or disabled, you must restart the corresponding board for the configuration to take effect.
- After this function is disabled, run the qos channel-profile command to customize a channel profile based on the actual bandwidth to prevent channel insufficiency.
- Run commit
The configuration is committed.