apply qos

Syntax

apply qos [queue-profile <QUEUE-NAME>] schedule-profile <SCHEDULE-NAME>

no apply qos schedule-profile <SCHEDULE-NAME>

Description

Applies a queue profile and schedule profile globally to all Ethernet and LAG interfaces on the switch, or applies only a schedule profile to a specific interface. When applied globally, the specified schedule profile is configured only on Ethernet interfaces and LAGs that do not already have their own schedule profile.

The no form of this command removes the specified schedule profile from an interface and the interface uses the global schedule profile. This is the only way to remove a schedule profile override from the interface.

NOTE:

When applying QoS settings to a port configured to support priority-based flow control, specific configuration settings must be respected when defining a CoS map and queue profile. See the command flow-control in the ArubaOS-CX 10.04 Command-Line Interface Guide for details.

NOTE:

Interfaces may shut down briefly during reconfiguration.

Command context

config

config-if

Parameters

queue-profile <QUEUE-NAME>

Specifies the name of the queue profile to apply. Range: 1 to 64 alphanumeric characters, including period (.), underscore (_), and hyphen (-). This parameter is not supported in the config-if context.

schedule-profile <SCHEDULE-NAME>

Specifies the name of the schedule profile to apply. Range: 1 to 64 alphanumeric characters, including period (.), underscore (_), and hyphen (-).

Authority

Administrators or local user group members with execution rights for this command.

Usage

  • For a queue profile to be complete and ready to be applied, all eight local priorities must be mapped to a queue.
  • For a schedule profile to be complete and ready to be applied, all eight queues must be defined. All queues must use the same algorithm, except for the highest numbered queue, which can be strict.
  • Both the queue profile and the schedule profile must specify the same number of queues.
  • An applied profile can only be updated or deleted when it is not applied to an interface.
The following commands illustrate a valid configuration, where every local priority value is assigned to a queue, and all assigned queues are defined.
map queue 0 local-priority 0
map queue 1 local-priority 1
map queue 1 local-priority 2
map queue 3 local-priority 3
map queue 4 local-priority 4
map queue 5 local-priority 5
map queue 5 local-priority 6
map queue 5 local-priority 7

wfq queue 0 weight 5
wfq queue 1 weight 10
wfq queue 3 weight 15
wfq queue 4 weight 25
wfq queue 5 weight 50
The following commands illustrate an invalid configuration, because local priority 2 is not assigned to a queue.
qos cos-map 1 local-priority 1
qos queue-profile Q1
map queue 0 local-priority 0
map queue 1 local-priority 1
map queue 3 local-priority 3
map queue 4 local-priority 4
map queue 5 local-priority 5
map queue 5 local-priority 6
map queue 5 local-priority 7

wfq queue 0 weight 5
wfq queue 1 weight 10
wfq queue 3 weight 15
wfq queue 4 weight 25
wfq queue 5 weight 50

Example

Applying the QoS profile myprofile and the schedule profile myschedule to all interfaces that do not have an applied profile:

switch(config)# apply qos queue-profile myprofile schedule-profile myschedule