qos-profile (interface view)

Function

The qos-profile command applies the QoS profile to interfaces.

The undo qos-profile command removes the QoS profile that is applied to interfaces.

By default, no QoS profile is applied to an interface.

Format

undo qos-profile { inbound | outbound }

qos-profile qos-profile-name { inbound | outbound } [ identifier { none | vid | ce-vid | vid-ce-vid } ] [ group group-name ]

qos-profile qos-profile-name { inbound | outbound } [ identifier none ] linkage-bandwidth

qos-profile qos-profile-name { inbound | outbound } { identifier { vid | ce-vid | vid-ce-vid } } linkage-bandwidth

Parameters

Parameter	Description	Value
qos-profile-name	Specifies the name of a QoS profile.	The value is a string of 1 to 63 characters.
inbound	Specifies the inbound direction.	-
identifier	Specifies which queue packets enter.	-
none	Indicates that users share the bandwidth of one SQ.	-
vid	Specifies the external VLAN ID.	-
ce-vid	Specifies the internal VLAN ID.	-
vid-ce-vid	Specifies the internal and external VLAN ID.	-
group group-name	Specifies the name of a shared group of QoS profile instances. After the CAR percentage is configured in a QoS profile, the group parameter cannot be specified when the QoS profile is applied to an interface.	The value is a string of 1 to 31 characters.
outbound	Specifies the outbound direction.	-
linkage-bandwidth	Enables bandwidth association. By default, bandwidth association is disabled. The bandwidth association configuration in the qos-profile command allows the bandwidth value in percentage rate limiting to be changed with the bandwidth configuration change, and minimizes the configuration workload during service deployment change. This parameter is mutually exclusive with the group parameter.	-

Views

100GE interface view, 10G LAN interface view, EVC view of a 10GE interface, 25GE interface view, 400GE sub-interface view, 400GE interface view, Eth-Trunk sub-interface view, Eth-Trunk interface view, GE optical interface view, Global VE sub-interface view, PW-VE sub-interface view, VNI view, EVC view of an Eth-Trunk interface, EVC view of a GE interface

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
qos	write

Usage Guidelines

Usage Scenario

To achieve uniform scheduling of incoming traffic flows on multiple interfaces, you need to implement traffic management by user levels.

Profile-based HQoS, by comparison, allows traffic on multiple interfaces to enter an SQ for scheduling. It implements uniform scheduling of traffic on multiple interfaces by defining a QoS profile and applying the profile to different interfaces.
The profile-based HQoS technique is used mainly on the access routers deployed at the edge of a MAN.

Precautions

If the direction configured in the QoS profile is different from the direction to which the QoS profile is applied on the interface, the profile does not take effect. If directionless traffic control is configured in the QoS profile, the QoS profile takes effect on traffic in the direction that is specified when the QoS profile is applied to the interface.
The QoS profile in which the CAR percentage is configured applies only to physical main interfaces and trunk main interfaces.
If an interface is already configured with the car command, or the user-queue command, or layer-2 traffic suppression commands, and these commands are configured for the same direction as the direction of the QoS profile, you need to delete these configured commands before being able to configure the qos-profile command to apply the QoS profile to the interface.
Bandwidth association is mutually exclusive with member interfaces of a trunk using the qos schedule-tree distribute-mode outbound command. Bandwidth association cannot be configured on the VE interface.
If a traffic rate limit is configured in a QoS profile, the number of TMs on an interface board must be considered when the QoS profile is applied to an Eth-Trunk interface. This is because the traffic rate limit takes effect on TMs. The number of TMs varies with interface boards. When multiple member interfaces of an Eth-Trunk interface correspond to different TMs, the times by which the rate limit increases depends on the number of TMs. As a result, the rate limiting may not be as expected. In this case, you need to reconfigure a rate limit.
If an interface is bound to a VSI instance, the hard-pipe enable command configured for the VSI instance is mutually exclusive with the qos-profile(interface view) command.
To configure weight-based bandwidth allocation for member interfaces of a trunk, run the qos member-link-scheduler distribute command.

If the direction configured in the QoS profile is different from the direction to which the QoS profile is applied on the interface, the profile does not take effect. If directionless traffic control is configured in the QoS profile, the QoS profile takes effect on traffic in the direction that is specified when the QoS profile is applied to the interface.
The QoS profile in which the CAR percentage is configured applies only to physical main interfaces and trunk main interfaces.
If an interface is already configured with the car command, or the user-queue command, or layer-2 traffic suppression commands, and these commands are configured for the same direction as the direction of the QoS profile, you need to delete these configured commands before being able to configure the qos-profile command to apply the QoS profile to the interface.
Bandwidth association is mutually exclusive with member interfaces of a trunk using the qos schedule-tree distribute-mode outbound command. Bandwidth association cannot be configured on the VE interface.
If a traffic rate limit is configured in a QoS profile, the number of TMs on an interface board must be considered when the QoS profile is applied to an Eth-Trunk interface. This is because the traffic rate limit takes effect on TMs. The number of TMs varies with interface boards. When multiple member interfaces of an Eth-Trunk interface correspond to different TMs, the times by which the rate limit increases depends on the number of TMs. As a result, the rate limiting may not be as expected. In this case, you need to reconfigure a rate limit.
If an interface is bound to a VSI instance, the hard-pipe enable command configured for the VSI instance is mutually exclusive with the qos-profile(interface view) command.
To configure weight-based bandwidth allocation for member interfaces of a trunk, run the qos member-link-scheduler distribute command.

Example

# Apply a QoS profile named test in vni view.

<HUAWEI> system-view
[~HUAWEI] qos-profile test
[*HUAWEI-qos-profile-test] quit
[*HUAWEI] vni 8
[*HUAWEI-vni8] qos-profile test inbound

# Apply a QoS profile named p1 to the incoming traffic on GE 0/1/0.

<HUAWEI> system-view
[~HUAWEI] qos-profile p1
[*HUAWEI-qos-profile-p1] quit
[*HUAWEI] interface GigabitEthernet 0/1/0
[*HUAWEI-GigabitEthernet0/1/0] qos-profile p1 inbound