Managing Congestion by Setting Packet Loss Priority for Different Traffic Flows

By default, the least significant bit of the CoS value sets the packet loss priority (PLP) value. For example, CoS value 000 is associated with PLP low, and CoS value 001 is associated with PLP high. In general, you can change the PLP by configuring a behavior aggregate (BA) or multifield classifier, as discussed in Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic and Overview of Assigning Service Levels to Packets Based on Multiple Packet Header Fields.

However, on Juniper Networks M320 Multiservice Edge Routers, MX Series 5G Universal Routing Platforms, and T Series Core Routers and EX Series switches that do not have tricolor marking enabled, the loss priority can be configured by setting the PLP within a multifield classifier or by behavior aggregate (BA) classifier. This setting can then be used by the appropriate drop profile map and rewrite rule.

On M320 routers and T Series routers with Enhanced II Flexible PIC Concentrators (FPCs) and tricolor marking enabled, you can set the PLP with a BA or multifield classifier, as described in Configuring Behavior Aggregate Classifiers and Using Multifield Classifiers to Set Packet Loss Priority.

On T Series routers with different Packet Forwarding Engines (non-Enhanced Scaling and Enhanced Scaling FPCs), you can configure PLP bit copying for ingress and egress unicast and multicast traffic. To configure, include the copy-plp-all statement at the [edit class-of-service] hierarchy level.