Configure and Attach a Filter Context to a Device Interface in IPFIX
Table of Contents
Configure and Attach a Filter Context to a Device Interface in IPFIX
Configure filter contexts for selecting IPFIX flow records. Attach a filter context to an
ION device interface to filter flow records for export in Prisma SD-WAN IPFIX.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
Filter Context is a criteria used to filter
the flow records that are exported to the collector.
- Select .Enter a name and an optional description.Save the filter context.Use the IPFIX filter context when configuring a filter as part of either an IPFIX profile or an IPFIX device override.If you have configured a filter context and used it in a profile, you must Attach a Filter Context to a Device Interface in IPFIX for filtering the flow records.You can assign an IPFIX filter context to multiple interfaces of a single ION device or multiple ION devices. You cannot assign an IPFIX filter context to a controller interface because the controller interface does not forward application traffic.
Attach a Filter Context to a Device Interface in IPFIX
Attach a filter context to an ION device interface to filter flow records for export. You can assign an IPFIX filter context to multiple interfaces of a single ION device or to multiple ION devices.- Select a filter context and assign to a device interface.
- Select .Click the ellipsis icon for an IPFIX Filter Context, select View Interface Bindings, and then click Bind Interfaces.
![]()
Select a device and an interface to bind the filter context.You can assign a filter context to any of the following interfaces:Interface Type Supports Filter Context Controller No Virtual Ports Yes Loopback No Standard VPN No Virtual Interfaces Yes Port Channel No Sub-interfaces Yes PPPoE Yes Bypass Pair Yes Select an ION device interface and bind the filter context.- Select .Select an interface to assign a filter context for filtering flow records.You cannot assign an IPFIX filter context to a controller interface. This is because the controller interface does not forward application traffic records.
