Applying a QoS Profile to a Domain

You can define a QoS profile and then apply it to the AAA domain to perform QoS scheduling for access user traffic.

Context

Applying a QoS profile to an interface functions differently from applying a QoS profile to a domain. The parameters about the bandwidth allocated to family users are obtained through the QoS profile applied to the interface while the parameters about the bandwidth allocated based on service types are obtained through the QoS profile applied to the domain.

The system performs traffic scheduling on common online users in a domain by directly adopting the parameters in the QoS profile applied to the domain. For family users, however, the system adopts only the parameters in the car command that is configured in the view of the QoS profile applied to the domain for traffic rate limiting.

Procedure

Run system-view
The system view is displayed.
Run aaa
The AAA view is displayed.
Run domain domain-name
An AAA domain is created and its view is displayed.

Here, domain-name specifies the domain to which the service needs to be mapped.
Run qos-profile profile-name { inbound | outbound } lns-gts
The QoS profile is applied to the domain.

The lns-gts parameter can be used only on the LNS device to bind a QoS profile to L2TP users.
Run quit
Return to the AAA view.
Run quit
Return to the system view.
(Optional) When a user accesses the device through an Eth-Trunk interface and the Eth-Trunk member interfaces reside on different forwarding modules or traffic management modules, to prevent the bandwidth of the trunk interface from being multiplied, perform the following operations to configure the total bandwidth to be allocated among the trunk member interfaces based on weights.
1. Run interface interface-type interface-number
  The Eth-Trunk interface view is displayed.
2. Perform either of the following operations based on the user access type:
  - For common access users, run the qos subscriber-access member-link-scheduler distribute inbound command to allocate the bandwidth to trunk member interfaces based on weights.
  - For private line access users, run the qos leased-line-access member-link-scheduler distribute { inbound | outbound } command to allocate the bandwidth to trunk member interfaces based on weights.
Run commit
The configuration is committed.