18. Queue management policies

Note:

This chapter is only applicable to the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12.

This chapter provides information to configure queue management policies using the command line interface.

18.1. Overview

Note:

The 7210 SAS-R6 and 7210 SAS-R12 equipped with an IMM-c card do not use the configured CBS and MBS parameter values in the queue management policy. The CBS and MBS values are system-defined for each queue. That is, CBS and MBS parameters are not user-configurable. In this section, references to modifying the CBS and MBS values in the queue management policies applies only to the 7210 SAS-R6 and 7210 SAS-R12 equipped with an IMM-b card.

A set of profiles or templates are available in hardware for configuring the queue parameters such as CBS, MBS, and WRED slopes. These profiles are available for use with multiple queues in the system. Queue management policies allow the user to define the queue parameters and allow sharing among the queues.

A single system buffer pool is available for use by all the queues in the system. Users can allocate the amount of buffers that each queue can use by specifying the CBS and MBS parameters in the queue management policy.

Weighted Random Early Detection (WRED) is available to manage buffers during periods of congestion. WRED slopes are supported for each queue in the system. Queue management policies allow the user to configure slope parameters that dictate a WRED profile for each queue. Each queue supports the following slopes:

  1. slope for in-profile or high priority traffic
  2. slope for out-of-profile or low priority traffic

Each slope allows specifying the start-average, the max-average, the drop-probability and the Time Average Factor (TAF). Each queue has a default slope policy. Multiple queues in the system can share a single policy. If a policy is shared the system computes the WRED drop probabilities for each of the queues separately based on their average queue length.

18.1.1. Basic configurations

A basic queue management policy must conform to the following restrictions:

  1. Each slope policy must have a unique policy ID.
  2. High slope and low slope are shut down by default.
  3. Default values can be modified but parameters cannot be deleted.

18.1.2. Service management tasks

18.1.2.1. Creating a queue management policy

To create a new queue management policy, define the following:

  1. a queue management policy name
  2. a brief description of the policy features
  3. CBS and MBS values
  4. high slope for the high priority WRED slope graph
  5. low slope for the low priority WRED slope graph
  6. time average factor (TAF)
  7. slope parameters, such as max-avg, start-avg, max-prob, time-average-factor

Use the following CLI syntax to configure a queue management policy.

CLI Syntax:
config>qos
queue-mgmt name
description description-string
cbs kbytes
mbs kbytes
high-slope
start-avg percent
max-avg percent
max-prob percent
no shutdown
low-slope
start-avg percent
max-avg percent
max-prob percent
no shutdown
time-average-factor taf

The following is a sample queue management policy configuration output:

A:7210>config>qos>queue-mgmt# info 
     
      ----------------------------------------------
                high-slope
                    shutdown
                    start-avg 40
                    max-avg 50
                exit
                low-slope
                    shutdown
                    start-avg 40
                    max-avg 80
                exit
            cbs 5000
            mbs 800000
       time-average-factor 7
       ----------------------------------------------

18.1.2.2. Editing QoS policies

Existing policies and entries can be edited through the CLI or NMS. The changes are applied immediately to all services where the policy is applicable.

To prevent configuration errors, perform the following:

  1. Copy the policy to a work area.
  2. Edit the policy.
  3. Overwrite the original policy.