[Contents] [Prev] [Next] [Index] [Report an Error]

Associating the PLP with a Drop-Profile Map

RED drop profiles take action on outgoing packets. When TCM is enabled, T-series and M320 platforms support four drop-profile map PLP designations: low, medium-low, medium-high, and high.

To configure the PLP for the drop-profile map, include the schedulers statement at the [edit class-of-service] hierarchy level:



[edit class-of-service]

schedulers {



scheduler-name {

drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol any drop-profile profile-name;
}


}

When you configure TCM, the drop-profile map’s protocol type must be any.

The inputs for a drop-profile map are the loss priority and the protocol type. The output for a drop-profile map is the drop profile name. In other words, the map sets the drop profile for each packet with a specific PLP and protocol type exiting the interface.

For example, in the following configuration, the dp drop profile is assigned to all packets exiting the interface with a medium-low PLP and belonging to any protocol:



class-of-service {


schedulers {


af {
drop-profile-map loss-priority medium-low protocol any
drop-profile dp;
}


}


}

To use this drop-profile map, you must configure the settings for the dp drop profile at the [edit class-of-service drop-profiles dp] hierarchy level. For more information, see Configuring RED Drop Profiles.

[Contents] [Prev] [Next] [Index] [Report an Error]