Juniper EX9200 Series, Features Manual

Page: 137 / 278

•
Multifield Classification Overview on page 115
•
Multifield Classification Limitations on M Series Routers on page 119
•
Example: Configuring Multifield Classification on page 121
•
tri-color
statement
Multifield Classification Limitations on M Series Routers
This topic covers the following information:
• Problem: Output-Filter Matching on Input-Filter Classification on page 119
• Workaround: Configure All Actions in the Ingress Filter on page 120
Problem: Output-Filter Matching on Input-Filter Classification
On M Series routers (except M120 routers), you cannot classify packets with an output
filter match based on the ingress classification that is set with an input filter applied to
the same IPv4 logical interface.
For example, in the following configuration, the filter called
ingress
assigns all incoming
IPv4 packets to the
expedited-forwarding
class. The filter called
egress
counts all packets
that were assigned to the
expedited-forwarding
class in the
ingress
filter. This configuration
does not work on most M Series routers. It works on all other routing platforms, including
M120 routers, MX Series routers, and T Series routers.
[edit]
user@host #
show firewall
family inet {
filter ingress {
term 1 {
then {
forwarding-class expedited-forwarding;
accept;
}
}
term 2 {
then accept;
}
}
filter egress {
term 1 {
from {
forwarding-class expedited-forwarding;
}
then count ef;
}
term 2 {
then accept;
}
}
}
119 Copyright © 2016, Juniper Networks, Inc.
Chapter 11: Multifield Classification