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

Defining Classifiers

You can override the default IP precedence classifier by defining a classifier and applying it to a logical interface. To define new classifiers for all code point types, include the classifiers statement at the [edit class-of-service] hierarchy level:



[edit class-of-service]

classifiers {


(dscp | dscp-ipv6 | exp | ieee-802.1 | inet-precedence) classifier-name {

import [classifier-name | default];



forwarding-class class-name {



loss-priority level {

code-points [ aliases ] [ 6-bit-patterns ];
}


}


}


}

The map sets the forwarding class and PLP for a specific set of code-point aliases and bit patterns. The inputs of the map are code-point aliases and bit patterns. The outputs of the map are the forwarding class and the PLP. For more information about how CoS maps work, see Table 7.

The classifiers work as follows:

dscp—Handles incoming IPv4 packets.
dscp-ipv6—Handles incoming IPv6 packets. For more information, see Applying DSCP IPv6 Classifiers.
exp—Handles MPLS packets using Layer 2 headers.
ieee-802.1—Handles Layer 2 CoS.
inet-precedence—Handles incoming IPv4 packets. IP precedence mapping requires only the upper three bits of the DSCP field.

A classifier takes a specified bit pattern as either the literal pattern or as a defined alias and attempts to match it to the type of packet arriving on the interface. If the information in the packet’s header matches the specified pattern, the packet is sent to the appropriate queue, defined by the forwarding class associated with the classifier.

The code-point aliases and bit patterns are the input for the map. The loss priority and forwarding class are outputs of the map. In other words, the map sets the PLP and forwarding class for a given set of code-point aliases and bit patterns.

Note: On T-series, MX-series, and M320 platforms that do not have tricolor marking enabled, the loss priority can be configured only by setting the PLP within an MF classifier. This setting can then be used by the appropriate drop profile map and rewrite rule. For more information, see Setting the PLP on T320 and M320 Platforms.

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