You can define a QoS profile and apply it to interfaces to implement unified scheduling of traffic on these interfaces.
Context
To achieve uniform scheduling of incoming traffic flows on multiple interfaces, you need to implement traffic management by user levels. Interface-based HQoS only supports classifying traffic flows on one interface into an SQ for scheduling. It does not support uniform scheduling of traffic flows on multiple interfaces. Profile-based HQoS, by comparison, supports classifying traffic flows on multiple interfaces into an SQ for scheduling. It implements uniform scheduling of traffic flows on multiple interfaces by defining QoS profiles and applying the profiles to different interfaces.
Procedure
- Apply a QoS profile.
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The interface or sub-interface view is displayed.
- Run any of the following commands:
- To apply a QoS profile to or an Dot1Q interface, run the qos-profile qos-profile-name { inbound | outbound } [ identifier none ] [ group group-name ] command.
- To apply a QoS profile to a Layer 2 interface or dot1q VLAN tag termination sub-interface, run the qos-profile qos-profile-name { inbound | outbound } vlan vlan-id-begin [ to vlan-id-end ] [ identifier { vlan-id | none } ] [ group group-name ] command.
- To apply a QoS profile to a QinQ VLAN tag termination sub-interface, run the qos-profile qos-profile-name { inbound | outbound } pe-vid pe-vlan-id { ce-vid ce-vlan-id-begin [ to ce-vlan-id-end ] } [ identifier { pe-vid | ce-vid | pe-ce-vid | none } ] [ group group-name ] command.
- To apply a QoS profile to an EVC Layer 2 sub-interface, run the qos-profile qos-profile-name { inbound | outbound } [ identifier { none | vid | ce-vid | vid-ce-vid } ] [ group group-name ] command.
- To apply a QoS profile to an NVE interface, run the qos-profile qos-profile-name { inbound | outbound } vni vni-id source sourceip peer peerip 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 commit
The configuration is committed.
- Run quit
Return to the system view.