apply qos

Syntax

apply qos [queue-profile] schedule-profile没有应用qos的时间表-profile

Description

Applies a queue profile and schedule profile globally to all Ethernet and LAG interfaces on the switch, or applies 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 same profile can be applied both globally and locally to an interface. This guarantees that an interface always uses the specified profile, even if the global profile is changed.

Thenoform 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 commandflow-controlin theArubaOS-CX Command-Line Interface Guidefor details.

NOTE:

Interfaces may shut down briefly during reconfiguration.

Command context

config

config-if

config-lag-if

Parameters

queue-profile

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 theconfig-ifcontext.

schedule-profile

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, it must define all queues specified in the queue profile. All queues must use the same algorithm, except for the highest numbered queue, which can bestrict.

  • Both the queue profile and the schedule profile must specify the same number of queues.

  • Schedule profiles can be modified while applied, but only in ways where a single command will not result in the profile becoming invalid. For example, queue 7 can have the algorithm changed, and weighted queues can have their weights changed.

  • The following commands illustrate a valid configuration, where every local priority value is assigned to a queue, and all assigned queues are defined.
    qos cos-map 1 local-priority 1qos queue-profile Q1map queue 0 local-priority 0map queue 1 local-priority 1map queue 2 local-priority 2地图3本地优先级队列map queue 4 local-priority 4map queue 5 local-priority 5map queue 5 local-priority 6map queue 5 local-priority 7qos schedule-profile S1dwrr queue 0 weight 5dwrr queue 1 weight 10dwrr queue 2 weight 15dwrr queue 3 weight 20dwrr queue 4 weight 25dwrr 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 1qos queue-profile Q1map queue 0 local-priority 0map queue 1 local-priority 1地图3本地优先级队列map queue 4 local-priority 4map queue 5 local-priority 5map queue 5 local-priority 6map queue 5 local-priority 7qos schedule-profile S1dwrr queue 0 weight 5dwrr queue 1 weight 10dwrr queue 3 weight 15dwrr queue 4 weight 25dwrr queue 5 weight 50

Example

Applying the QoS profilemyprofileand the schedule profilemyscheduleto all interfaces that do not have an applied interface-specific schedule profile:

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