Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'}
JIRAIDAUTHTP-548
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}

Panel

In this section:

Table of Contents
maxLevel3

Before you Begin

You must first enable traffic shaping and the GRED/LLQ shaper:

  1. Choose Network > Traffic Shaper.
  2. Select the Enable Traffic Shaping check-box.
  3. Select the Enable GRED/LLQ Shaper check-box.
  4. Click Submit.

Configuring GRED/LLQ

This section outlines how to configure GRED/LLQ.

To Configure GRED/LLQ

  1. Choose Traffic Shaper > Advanced.

  2. Click GRED/LLQ Configuration Rules.


  3. Configure settings using the information in the following table as a guide. When you have finished configuring settings, click Submit to make your changes take effect.

    Caption
    0Table
    1Advanced Traffic Shaper - GRED/LLQ Configuration Rules


    ItemDescription

    LLQ Parameters

    Configures LLQ parameters.

    LLQ Bandwidth

     Percentage

    Sets the amount of bandwidth allocated to the LLQ side. If this is set below 100, the low priority traffic is allowed to send data even when there is high priority traffic to be sent. Use the default value of 100.

    GRED Parameters

    Configures GRED parameters.

    NameSpecifies the name of the GRED and its associated priority queue.
    Priority Class

    Specifies the Per-Hop Behavior (PHB) for the associated GRED:

    • Best Effort—Default. All unmarked traffic is assigned to this class. This traffic is also the first to be dropped during times of congestion. Examples of best effort traffic include web, email, SNMP, and so on.

    • Assured Forwarding / IP Precedence (1 to 4)—For applications that require better reliability than the best-effort service.

    • Expedited Forwarding / IP Precedence 5—Provides low-loss, low-latency, low-jitter, and guaranteed bandwidth. For real-time voice traffic.

    • IP Precedence 6 and 7—Protects critical data from being dropped due to congestion. For example, IGP and BGP, which go to the route processor, get priority and have the least chance of getting dropped.

    Latency

    Sets the desired latency for a packet. More allowed latency means that the packet can remain in the queue longer and is less likely to drop.

    Average packet size

    Specifies the average sized packet in bytes.

    • Internet Mix (IMIX) traffic—880b

    • Voice traffic—64b



  4. In the LLQ Bandwidth percentage field, leave the default value of 100 to manage high priority traffic.

  5. Set GRED parameters:

    1. In the Name field, enter the name of the GRED and its associated priority queue.

    2. In the Priority Class field, choose the PHB for the associated GRED:

      • Best Effort—Default

      • Assured Forwarding / IP Precedence (1 to 4)—IP Precedence classes 1 through 4

      • Expedited Forwarding / IP Precedence 5—IP Precedence class 5

      • IP Precedence 6 and 7

    3. In the Latency field, enter the latency value for a packet.

    4. In the Average Packet Size (bytes) field, choose a value:

      • Internet Mix (IMIX) traffic—880b

      • Voice traffic—64b

  6. Click Submit to save your settings.