Navigation
Related Documentation
Guidelines for Applying Simple Filters
This topic covers the following information:
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
You can apply a simple filter to the ingress IPv4 traffic at a logical interface configured on the following hardware only:
- Gigabit Ethernet intelligent queuing (IQ2) PICs installed on M120, M320, or T Series routers.
- Enhanced Queuing Dense Port Concentrators (EQ DPCs) installed on MX Series routers and EX Series switches.
For more information about Ethernet IQ2 PICs and EQ DPCs and related features, see the Junos OS Class of Service Configuration Guide. For more information about configuring the MX Series routers, on which EQ DPCs are supported, see the Junos OS Layer 2 Configuration Guide.
The following additional 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 inet traffic 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.
