Configuring Drop Profile Maps for Schedulers
Drop-profile maps associate drop profiles with a scheduler. The map examines the current loss priority setting of the packet (high, low, or any) and assigns a drop profile according to these values. For example, you can specify that all TCP packets with low loss priority are assigned a drop profile that you name low-drop. You can associate multiple drop-profile maps with a single queue.
The scheduler drop profile defines the drop probabilities across the range of delay-buffer occupancy, thereby supporting the RED process. Depending on the drop probabilities, RED might drop packets aggressively long before the buffer becomes full, or it might drop only a few packets even if the buffer is almost full. For information on how to configure drop profiles, see RED Drop Profiles Overview.
By default, the drop profile is mapped to packets with low PLP and any protocol type. To configure how packet types are mapped to a specified drop profile, include the drop-profile-map statement at the [edit class-of-service schedulers scheduler-name] hierarchy level:
The map sets the drop profile for a specific PLP and protocol type. The inputs for the map are the PLP and the protocol type. The output is the drop profile. For more information about how CoS maps work, see CoS Inputs and Outputs Overview.
 | Note: On Juniper Network MX Series 3D Universal Edge Routers, T4000 Core Routers, and PTX Series Packet Transport Switches, you can configure only the any option for the protocol statement. |
For each scheduler, you can configure separate drop profile maps for each loss priority.
You can configure a maximum of 32 different drop profiles.
