Configuring Multifield Classifiers

If you configure both a behavior aggregate (BA) classifier and a multifield classifier, BA classification is performed first; then multifield classification is performed. If they conflict, any BA classification result is overridden by the multifield classifier.

Note: For a specified interface, you can configure both a multifield classifier and a BA classifier without conflicts. Because the classifiers are always applied in sequential order, the BA classifier followed by the multifield classifier, any BA classification result is overridden by a multifield classifier if they conflict.

To activate a multifield classifier, you must configure it on a logical interface. There is no restriction on the number of multifield classifiers you can configure.

Note: For MX Series routers, if you configure a firewall filter with a DSCP action or traffic-class action on a DPC, the commit does not fail, but a warning displays and an entry is made in the syslog.

To configure multifield classifiers, include the following statements at the [edit firewall] hierarchy level:

[edit firewall]family family-name {filter filter-name {term term-name {from {match-conditions;}then {dscp 0;forwarding-class class-name;loss-priority (high | low);}}}simple-filter filter-name {term term-name {from {match-conditions;}then {forwarding-class class-name;loss-priority (high | low | medium);}}}}

The [edit firewall] configuration statements are discussed in detail in the Junos Policy Framework Configuration Guide.