You can apply a QoS profile to a type of user packets on an interface to perform HQoS for the user packets based on the scheduling parameters. You can also bind a service identification policy to the interface so that packets that meet specified conditions can be mapped to the domain for authentication.
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.
You can apply a QoS profile configured with CAR to the AAA domain for a single service of family users, and then to the interface for all family users.
When rate limiting is configured for all family users on the interface, CAR and user-queue cannot both take effect in the upstream direction. If both CAR and user-queue are configured, CAR takes effect in the upstream direction. CAR and user-queue can both take effect in the downstream direction.
The system view is displayed.
The interface view is displayed.
The BAS interface view is displayed.
The access type cannot be configured on the Ethernet interface that is added to an Eth-Trunk interface. You can configure the access type of such an Ethernet interface only on the associated Eth-Trunk interface.
When configuring static routes for Layer 3 users, specify the next hop as the user IP address and do not specify the outbound interface. Otherwise, network-to-user traffic may fail to be forwarded.
Automatic PIR bandwidth adjustment is configured for DHCPv4, DHCPv6, and PPPoE users.
Option 82 is inserted for static users so that static users can be identified using a QoS profile.
Each SQ can be mapped to only one GQ.
A service identification policy is bound to the BAS interface.
The configuration is committed.