SteelHeadā„¢ Deployment Guide : QoS Configuration and Integration : QoS Enforcement Best Practices
  
QoS Enforcement Best Practices
Riverbed recommends the following actions to ensure optimal performance with the least amount of initial and ongoing configuration:
  • Configure QoS while the QoS functionality is disabled and only enable it after you are ready for the changes to take effect.
  • Configure an uplink for the default class and assign a reasonable bandwidth to it.
  • The built-in default class initially does not have uplinks configured. Because of this, the physical bandwidth of the in-path interface is used. This use can lead to a high and undesired oversubscription of the uplink of the local site and thus impact the minimum bandwidth guarantee of the remote sites.
    A typical indication that you must adjust the default class uplinks bandwidth is when traffic that is specified in the sites or QoS rules appears to be slow during times of congestion, while other traffic not specified in sites or QoS rules (typical examples include Web browsing and routing updates) works fine.
  • When configuring a profile, create a default class and point the default rule (Any) to the default class.
  • Be aware that flows can be incorrectly classified if there are asymmetric routes in the network in which you have enabled the QoS features.