Configuring Bandwidth Contracts

Bandwidth contract configuration lets you configure bandwidth contracts for both the global or application-specific levels.

Global Bandwidth Contract Configuration

To configure bandwidth contracts to limit application and application categories on an application or global level, or to show global bandwidth contract configuration output, execute the following commands.

[host] [md](config) #dpi global-bandwidth-contract[app|appcategory]

[host] [md] #show dpi global-bandwidth-contract

Role-Specific Bandwidth Contracts

Application-specific bandwidth contracts (unlike "generic" bandwidth-contracts) allow you to control or reserve rates for specific applications only on a per-role basis. An optional exclude list is provided that allows you to exclude applications or application categories on which a generic user or role bandwidth-contract is not applied.

Using an Exclude List

Use an exclude to give specific enterprise mission-critical applications priority over other user traffic. An enterprise may have well known applications such as Microsoft Exchange, SAP, Oracle, accounting and finance applications, and other enterprise resource planning or customer relationship management applications.

Instead of enumerating bandwidth limits for each application individually on a per-user or per-role basis, you can configure a single bandwidth contract on a per-user or per-role to limit all non-mission critical applications. You can then exclude all mission-critical applications by placing them in an exclude list. This way all mission-critical applications will not be rate-limited. Important points regarding bandwidth contracts include:

  • Application bandwidth contracts are per-role by default.
  • When an application bandwidth-contract is configured for both a category and an application within the category, always apply the most specific bandwidth contract.

The following procedure describes how to configure role specific bandwidth contracts:

  1. In the Managed Network node hierarchy, navigate to the Configuration > Roles & Policies > Roles tab.
  2. Click + to create a new user role and enter a Name for the new role and click Submit or select a role from the Roles table to modify an existing role.
  3. Click Show Advanced View.
  4. Select the Bandwidth tab.
  5. Expand the Pre-Application Limits for This Role accordion and click + to add an application or application category to a bandwidth contract.
    1. Select the application bandwidth type from the Type drop-down list.
    2. Select the name of the bandwidth contract from the Name drop-down list.
    3. Enter values in Kbits or Mbits in the Upstream and Downstream fields.
    4. Click Submit.
  6. Expand the Pre-Application Limit Exceptions for This Role accordion and click + to add an exception.
    1. Select a value from the Type drop-down list.
    2. Select an application or application category from the Name drop-down list.
    3. Click Submit.

    Make sure that the Enable Deep Packet Inspection option is checked.

  7. Click Submit.
  8. Click Pending Changes.
  9. In the Pending Changes window, select the check box and click Deploy changes.

The following CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. commands configure the bandwidth application-specific parameters:

(host) [md] (config)# user-role <string>

(host) [md](config-role)# bw-contract exclude