Manualshelf

Users Guide

ManualsBrandsDell ManualsAccess PlatformsW-Series Controller AOS
391392393394395396397398399400
Table Of Contents
393| Roles and Policies Dell Networking W-Series ArubaOS 6.5.x| User Guide
Parameter Description
Rate limit CP trusted ucast
traffic (pps)
Specifies the trusted unicast traffic rate limit. Range is 1-65535 packets
per seconds (pps).
Default: 65535 pps
Rate limit CP trusted mcast
traffic (pps)
Specifies the trusted multicast traffic rate limit. Range is 1-65535
packets per seconds (pps).
Default: 1953 pps
Rate limit CP route traffic (pps) Specifies the traffic rate limit that needs ARP requests. Range is 1-
65535 packets per seconds (pps).
Default: 976 pps
Rate limit CP session mirror
traffic (pps)
Specifies the session mirrored traffic forwarded to the controller.
Range is 1-65535 packets per seconds (pps).
Default: 976 pps
Rate limit CP auth process
traffic (pps)
Specifies the traffic rate limit that is forwarded to the authentication
process. Range is Range is 1-65535 packets per seconds (pps).
Default: 976 pps
Using AppRF 2.0
The AppRF 2.0 feature improves application visibility and control by allowing you to configure access control
list (ACL) and bandwidth-control applications and application categories. AppRF 2.0 supports a Deep Packet
Inspection (DPI) engine for application detection for over a thousand applications. All wired and wireless traffic
that traverses the controller can now be categorized and controlled by application and application category.
AppRF 2.0 provides the ability to:
l permit or deny an application or application category for a specific role. For example, you can block
bandwidth monopolizing applications on a guest role within an enterprise.
l rate limit an application or application category, such as video streaming applications, globally or for a
specific role.
l mark different L2/L3 Quality of Service (QoS) for an application or application category for a user role. For
example, you can mark video and voice sessions that originate from wireless users with different priorities
so that traffic is prioritized accordingly in your network.
To configure AppRF 2.0, see the following topics:
l Enabling Deep Packet Inspection (DPI) on page 393
l Configuring Policies for AppRF 2.0 on page 394
l Configuring Bandwidth Contracts for AppRF 2.0 on page 396
Enabling Deep Packet Inspection (DPI)
For application and application category specific configuration to take affect, you must first enable DPI.
You must reboot (reload) the controller after you enable or disable DPI for global classification to take effect.