Guidelines for Applying Simple Filters
Statement Hierarchy for Applying Simple Filters
You can apply a simple filter to the IPv4 ingress traffic at a logical interface by including the simple-filter input simple-filter-name statement at the [edit interfaces interface-name unit unit-number family inet] hierarchy level.
[edit]
interfaces {
interface-name {
unit logical-unit-number {
family inet {
simple-filter {
input filter-name;
}
}
}
}
}
Restrictions for Applying Simple Filters
The following restrictions pertain to applying simple filters:
Simple filters are not supported on Modular Port Concentrator (MPC) interfaces, including Enhanced Queuing MPC interfaces.
Simple filters are not supported for interfaces in an aggregated-Ethernet bundle.
You can apply simple filters to
family inettraffic only. No other protocol family is supported.You can apply simple filters to ingress traffic only. Egress traffic is not supported.
You can apply only a single simple filter to a supported logical interface. Input lists are not supported.
Platform-Specific Behavior
Use Feature Explorer to confirm platform and release support for specific features.
Use the following table to review platform-specific behavior for your platform:
|
Platform |
Behavior |
|---|---|
|
MX Series Routers |
You can apply a simple filter to the ingress IPv4 traffic at a logical interface configured on Enhanced Queuing Dense Port Concentrators (EQ DPCs) |
|
EX Series Routers |
You can apply a simple filter to the ingress IPv4 traffic at a logical interface configured on Enhanced Queuing Dense Port Concentrators (EQ DPCs) |