Configuring global QoS
To configure QoS, you need to enable QoS as a feature and build QoS profiles based on source and destination sites. The profile includes QoS rule configurations. The final task is to choose certain SteelHeads to obtain this common configuration.
To configure global QoS on the SCC
1. Choose Manage > Services: Quality of Service.
2. Enable QoS for SteelHeads.
You can also select to enable outbound QoS, inbound QoS, and DSCP marking.
You’ve the option to override QoS interface settings on a per SteelHead basis. You might need to disable QoS configuration on an interface level because certain deployments do not support QoS across all SteelHead interfaces.
3. Select Add a QoS Profile.
The following step is specific to SCC only and is not available directly on the SteelHead.
4. When you configuring a new profile, you must indicate the source and destination sites.
You can configure the source and destination sites per site or by types of site that have already been defined in the sites and networks. You also have the option to select Any Site to indicate that the profile is applied to all known predefined sites.
This configuration example doesn’t have an equivalent configuration directly on a SteelHead. Unlike the path selection single global configuration, the SCC can deploy a different QoS configuration based on the site or the site types. A global QoS configuration is not capable of differentiating between different types of sites, requiring different QoS parameters. With these settings, SCC only applies the proper profile that matches the correct sites and site types the profile is tied to. During an SCC push, the site profile is matched to the SteelHead first, and if that profile is not present, then the site types profile is matched. If neither is present, then Any Site profile is matched.
5. Choose either to start with new QoS classes and rules or copy from another existing profile. New installations generally require starting with new QoS classes. By default, SCC creates an Any Site-to-Any Site configuration; therefore, you can’t create a new profile based upon a similar site delineation, although you’re able to edit the default profile if needed.
6. Click Create Profile.
7. Select Edit Profile to manage the associated QoS classes and rules.
8. Click Edit to create the classes.
9. Click add class.
10. Specify a name and desired percentage for a minimum and maximum bandwidth range.
You can also alter the queue type, change the DSCP mark, and manipulate the priority level from 1 to 6 with 1 being highest.
We recommend that you start with the default catch-all class parameters, and then configure the other additional classes.
11. After you’ve created all the classes, you must create the QoS rules and associate them to the classes you’ve just created.
QoS rules are application centric. You select an application or application group, choose the class from the list you had just completed, and optionally manipulate the DSCP marking for this traffic. The DSCP marking overrides whatever you set at the class level.
12. Click Include in Push.
13. Select the SteelHeads for which you want to obtain the QoS configuration based on site type or per site.
14. You’ve the option to push only QoS profiles or include the sites and networks configuration. Push the entire topology (sites and networks) and application configuration if there was a change made to the topology or application sections.
After you’ve pushed the changes, the Push Status window shows additional detail on the operation.