WAN Interface Bandwidth Priorities

ArubaOS supports minimum bandwidth guarantees per traffic class, and allows critical delay-sensitive applications like voice and video to use more bandwidth and/or be scheduled with higher priority. Each interface can be associated with a scheduler profile that supports four queues with different priority levels. If you use session ACLs Access Control List. ACL is a common way of restricting certain types of traffic on a physical port. to define traffic policies on the managed device, you can use the scheduler profile to automatically associate these different priority levels assigned by these policies to a scheduler profile queue.

 

For information on creating a traffic policy that assigns 802.1p priority levels to a specific application or application type, see Firewall Policies

Each scheduler profile queue is assigned a priority level and one of the following scheduler discipline types:

  • Strict priority: The queue service is based exclusively on the priority of the queue, where the lower priority queues are not serviced until the higher priority queue is clear. With this option, the highest level priority is guaranteed as much bandwidth as possible, but there can be phases where the 2nd, 3rd and 4th priority queues may receive little or no bandwidth.
  • Deficit Round Robin Weight: The queue is assigned a percentage of available bandwidth.

You can define both strict priority and DDR Weight discipline types for a single scheduler profile.

The following procedure describes how to enable WLAN Wireless Local Area Network. WLAN is a 802.11 standards-based LAN that the users access through a wireless connection. interface bandwidth priorities using the WAN Wide Area Network. WAN is a telecommunications network or computer network that extends over a large geographical distance. scheduler feature:

  1. In the Managed Network node hierarchy, navigate to Configuration > Services > WAN tab.
  2. Expand the WAN Scheduler accordion.
  3. Click + below the WAN Scheduler Profiles table to define a new scheduler profile.
    1. Enter a Profile name.
    2. In the Priority fields, enter one or more 802.1p priority levels (0-7) for each queue type. Each of the seven priority levels must be supported by one of the four queues.
    3. For each queue, click the Scheduler Discipline drop-down list and select the Strict Priority or DDR Weight discipline type. If you select the DDR weight option, enter the percentage of available bandwidth that should be made available to traffic in the selected queue. This field appears to the right of the DDR weight option.

If you configure both of strict priority and Deficit Round Robin weighted queues, the strict priority queues should be specified together continuously, followed by the Deficit Round Robin weighted queues. For example, if you want to specify two strict priority queues and two DDR weighted queues, configure queue 0 and 1 with the strict priority type, then configure queues 2 and 3 with a Deficit Round Robin priority type. You cannot alternate between strict priority and DDR weighted queues.

  1. To assign the scheduler profile to a cellular or Gigabit Ethernet Ethernet is a network protocol for data transmission over LAN. interface, click + below the Assignments table.
  2. Click the Ports drop-down list to select an interface.
  3. In the Transmit Rate field, enter the maximum transmit rate for the selected interface, in Mbps Megabits per second.
  4. Create a firewall Firewall is a network security system used for preventing unauthorized access to or from a private network. session policy that assigns a priority level to an application or application group. For details, see Firewall Policies

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 enable WLAN Wireless Local Area Network. WLAN is a 802.11 standards-based LAN that the users access through a wireless connection. interface bandwidth priorities:

(host)[node](config) #scheduler-profile <map-name> {priority-map <q0-q3> <que0-prio-list>} | {queue-weights <q0-q3> <percentage_weight>}

(host)[node](config) #interface cellular|gigabitethernet <slot/module/port> transmit max-rate rate mbits <mbps> scheduler-profile <profile>

(host)[node](config) #ip access-list session any any app salesforce permit priority 3