The qos schedule-tree distribute-mode outbound command configures weight-based bandwidth allocation for a trunk's member interfaces for HQoS scheduling.
The undo qos schedule-tree distribute-mode outbound command cancels weight-based bandwidth allocation for a trunk's member interfaces for HQoS scheduling.
By default, TM-based HQoS scheduling is implemented for traffic on a trunk interface.
Usage Scenario
When traffic on a trunk interface is scheduled using HQoS based on the TM, if a trunk member interface is congested, traffic on other member interfaces is affected. To resolve this problem, run the qos schedule-tree distribute-mode outbound command to configure weight-based bandwidth allocation for a trunk's member interfaces for HQoS scheduling.
Precautions
This command can be configured regardless of whether a trunk interface has member interfaces. However, the configuration can be canceled only when a trunk interface has no member interfaces. After this command is run on a trunk interface, the board or subcard on which a new member interface resides must support this function.
If this command has been configured and the Eth-Trunk has member interfaces, services will be interrupted during configuration rollback. After the configuration rollback is complete, services are automatically restored. If a trunk interface has member interfaces, the trunk interface's scheduling tree is switched from the trunk-based scheduling model to the member interface-based scheduling model after this command is run. During the switching, traffic matching the default forwarding behavior may be transiently interrupted. Rate limiting does not take effect for traffic matching service rate limiting within a short period of time.This command is supported on the equipped with a -E subcard.
If member interfaces of a trunk interface reside on TM subcards of different types on the same board, this command cannot be configured on the trunk interface. For the CR5D0L2XFE71 CR5D0EAGFE70 subcard, this command can be configured and deleted only when the trunk interface does not have member interfaces. For other boards and subcards, this command can be configured regardless of whether the trunk interface has member interfaces. However, the configuration can be canceled only when a trunk interface has no member interfaces. After this command is run on a trunk interface, the board or subcard on which a new member interface resides must support this function. If this command has been configured and the Eth-Trunk has member interfaces, services will be interrupted during configuration rollback. After the configuration rollback is complete, services are automatically restored. If a trunk interface has member interfaces, the trunk interface's scheduling tree is switched from the trunk-based scheduling model to the member interface-based scheduling model after this command is run. During the switching, traffic matching the default forwarding behavior may be transiently interrupted. Rate limiting does not take effect for traffic matching service rate limiting within a short period of time.