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.
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.
- Queues must be consecutively defined starting at queue number zero. For example, a four-queue profile with priority values defined for queues 0, 1, 2, 3 is valid, but a four-queue profile which defines priority values for queues 1, 3, 5, and 7 is not.
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 2 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 qos schedule-profile S1 dwrr queue 0 weight 5 dwrr queue 1 weight 10 dwrr queue 2 weight 15 dwrr queue 3 weight 20 dwrr queue 4 weight 25 dwrr queue 5 weight 50The 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 qos schedule-profile S1 dwrr queue 0 weight 5 dwrr queue 1 weight 10 dwrr queue 3 weight 15 dwrr queue 4 weight 25 dwrr 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