Users Guide

461 | Roles and Policies Dell Networking W-Series ArubaOS 6.4.x| User Guide
n source: network 10.0.0.0/24
n destination: any
n service/application: TCP 80
n action: destination nat
In the WebUI
1. Navigate to Configuration > Access Control > Policies.
2. Click Add/Edit.
3. Click Add under Rules/IP Version.
4. Select application or application category from the Service drop-down menu and select configuration
options.
5. Click Apply.
In the CLI
To configure the ACL application-specific parameters using the command-line interface, access the command-
line interface in config mode, run the following commands:
(host)(config)#ip access-list
Configuring Bandwidth Contracts for AppRF 2.0
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, access the command-line interface and use
the commands dpi global-bandwidth-contract and show dpi global-bandwidth-contract.
(host)(config) #dpi global-bandwidth-contract[app|appcategory]
(host) #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/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 (ERP) or customer relationship management (CRM)
applications.
Instead of enumerating bandwidth limits for each application individually on a per-user/per-role basis, you can
configure a single bandwidth contract on a per-user/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:
l Application bandwidth contracts are per-role by default.
l When an application bandwidth-contract is configured for both a category and an application within the
category, always apply the most specific bandwidth contract.