Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Understanding RED Drop Profiles

    When you configure the RED drop profile on an interface, the queue no longer drops packets from the tail of the queue, which is the default. Rather, packets are dropped after they reach the head of the queue.

    You specify drop probabilities in the drop profile section of the class-of-service (CoS) configuration hierarchy and reference them in each scheduler configuration. For each scheduler, you can configure multiple separate drop profiles, one for each combination of loss priority (low, medium-low, medium-high, or high) and IP transport protocol (TCP, non-TCP, or any).

    You can configure a maximum of 32 different drop profiles. By default, if you configure no drop profiles, RED is still in effect and functions as the primary mechanism for managing congestion. In the default RED drop profile, when the fill level is 0 percent, the drop probability is 0 percent. When the fill level is 100 percent, the drop probability is 100 percent.

    Note: For J Series devices and SRX210, SRX240, and SRX650 devices, TCP, and non-TCP values are not supported, only the value “any” is supported.

    To configure RED drop profiles, include the following statements at the [edit class-of-service] hierarchy level of the configuration:

    [edit class-of-service]
    drop-profiles {profile-name {fill-level percentage drop-probability percentage;interpolate {drop-probability [ values ];fill-level [ values ];}}}

    Modified: 2016-09-01