Configuration Mode Commands : SteelHead Configuration Commands : QoS Commands : qos profile class-params
  
qos profile class-params
Configures the QoS class parameters for the specified profile.
Syntax
qos profile <name> class-params class <class-name> [priority <priority-id>] [min-bw <min-bw-percent>] [max-bw <max-bw-percent>] [ob-queue <method>] [ob-queue-length <length>] [out-dscp <out-dscp-value>] [conn-limit <optimized-connection-number>] [link-share <link-share-weight>] [ib-queue-length <length>]
Parameters
<name>
QoS profile name.
class <class-name>
Specifies the QoS class name. The QoS class indicates how delay-sensitive a traffic class is to the QoS scheduler. Select a service class for the profile from the following (highest priority to lowest):
•  Real Time - Specifies real-time traffic class. Give this value to your highest priority traffic; for example, VoIP, or video conferencing.
•  Interactive - Specifies an interactive traffic class: for example, Citrix, RDP, telnet and ssh.
•  Business Critical - Specifies the business critical traffic class: for example, Thick Client Applications, ERPs, and CRMs.
•  Normal - Specifies a normal priority traffic class: for example, Internet browsing, file sharing, and email.
•  Low Priority - Specifies a low priority traffic class: for example, FTP, backup, replication, other high-throughput data transfers, and recreational applications such as audio file sharing.
•  Best Effort - Specifies the lowest priority.
These are minimum service class guarantees; if better service is available, it is provided: for example, if a class is specified as low priority and the higher priority classes are not active, then the low priority class receives the highest possible available priority for the current traffic conditions. This parameter controls the priority of the class relative to the other classes.
priority <priority-id>
Modifies QoS class priority settings. The priority range is from 1 to 6, where 1 is the highest and 6 is the lowest priority.
min-bw <min-bw-percent>
Specifies the QoS class guaranteed minimum bandwidth setting (as a percentage).
Flows that do not use all of their allocated minimum bandwidth will share this excess bandwidth with other flows that exceed their minimum bandwidth allocation. All the classes combined cannot exceed 100%. During contention for bandwidth, the class is guaranteed at least to the amount of specified bandwidth. It will receive more if there is unused bandwidth remaining.
A default class is automatically created with minimum bandwidth of 10 percent. Traffic that does not match any of the rules is put into the default class. Riverbed recommends that you change the minimum default bandwidth of the default class to the appropriate value.
You can adjust the value as low as 0%. The system rounds decimal numbers to 5 points.
max-bw <max -bw-percent>
Specifies the maximum allowed bandwidth (as a percentage) a QoS class receives as a percentage of the parent class guaranteed maximum bandwidth. The limit is applied even if there is excess bandwidth available. The system rounds decimal numbers to 5 points.
ob-queue <method>
Selects one of the following outbound queue methods for the leaf class (the queue does not apply to the inner class):
•  sfq - Stochastic Fair Queuing (SFQ) is the default queue for all classes. Determines SteelHead behavior when the number of packets in a QoS class outbound queue exceeds the configured queue length. When SFQ is used, packets are dropped from within the queue in a round-robin fashion, among the present traffic flows. SFQ ensures that each flow within the QoS class receives a fair share of output bandwidth relative to each other, preventing bursty flows from starving other flows within the QoS class.
•  fifo - Transmits all flows in the order that they are received (first in, first out). Bursty sources can cause long delays in delivering time-sensitive application traffic and potentially to network control and signaling messages.
•  mx-tcp - Maximum speed TCP queue has very different use cases than the other queue parameters. MX-TCP also has secondary effects that you need to understand before configuring. See the SteelHead Management Console User’s Guide and the SteelHead Deployment Guide for information about usage scenarios and configuration details for MX-TCP.
ob-queue-length <length>
Specifies the outbound QoS class queue length. By default, each class has a queue length of 1024. Riverbed recommends that you consult with Riverbed Support or your sales engineer before you set this parameter.
out-dscp <out-dscp-value>
Specifies the QoS class outbound DSCP value. The DSCP values are 0-63 or preserve. Preserve is the default setting for a service class. Preserve means that the DSCP level or IP ToS value found on pass-through traffic is unchanged when it passes through the SteelHead.
conn-limit <optimized- connection-number>
Specifies the connection limit. The connection limit is the maximum number of optimized connections for the class. When the limit is reached, all new connections are passed through unoptimized.
In hierarchical mode, a parent class connection limit does not affect its child. Each child-class optimized connection is limited by the connection limit specified for their class. For example, if B is a child of A, and the connection limit for A is set to 5, while the connection limit for B is set to 10, the connection limit for B is 10. Connection limit is supported only in in-path configurations. It is not supported in out-of-path or virtual-in-path configurations.
Connection limit is supported only in in-path configurations. It is not supported in out-of-path or virtual-in-path configurations.
RiOS does not support a connection limit assigned to any QoS class that is associated with a QoS rule with an Application Flow Engine component. An Application Flow Engine component consists of a Layer-7 protocol specification. RiOS cannot honor the class connection limit because the QoS scheduler might subsequently reclassify the traffic flow after applying a more precise match using Application Flow Engine identification.
In RiOS 9.0 and later, this parameter is only available through the CLI.
link-share <link-share-weight>
Specifies the weight for the class. This parameter applies to flat mode only. The link share weight determines how the excess bandwidth is allocated among sibling classes. Link share does not depend on the minimum guaranteed bandwidth. By default, all the link shares are equal.
Classes with a larger weight are allocated more of the excess bandwidth that classes with a lower link share weight.
ib-queue-length <length>
Specifies the QoS class inbound queue length. By default, each class has a queue length of 1024. Riverbed recommends that you consult with Riverbed Support or your sales engineer before you set this parameter.
Usage
The minimum bandwidth must fall within the bandwidth limit for the SteelHead. Excess bandwidth is allocated based on the relative ratios of minimum bandwidth. The total minimum guaranteed bandwidth of all QoS classes must be less than or equal to 100% of the parent class. A default class is automatically created with minimum bandwidth of 10%. Traffic that does not match any of the rules is put into the default class.
Example
amnesiac (config) # qos profile profile0 class-params class class5 priority 5 min-bw 0.0 max-bw 100.0 ob-queue SFQ ob-queue-length 1024 out-dscp Preserve
Product
SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands
qos profile class, show qos profile