Configure and Attach a Collector Context to a Device Interface in IPFIX
Table of Contents
Expand all | Collapse all
-
-
- Add a Branch
- Add a Data Center
- Add a Branch Gateway
- Configure Circuits
- Configure Internet Circuit Underlay Link Aggregation
- Configure Private WAN Underlay Link Quality Aggregation
- Configure Circuit Categories
- Configure Device Initiated Connections for Circuits
- Add Public IP LAN Address to Enterprise Prefixes
- Manage Data Center Clusters
- Configure a Site Prefix
- Configure a DHCP Server
- Configure NTP for Prisma SD-WAN
- Configure the ION Device at a Branch Site
- Configure the ION Device at a Data Center
- Switch a Site to Control Mode
- Allow IP Addresses in Firewall Configuration
-
- Configure a Controller Port
- Configure Internet Ports
- Configure WAN/LAN Ports
- Configure a Loopback Interface
- Configure a PoE Port
- Configure and Monitor LLDP Activity and Status
- Configure a PPPoE Interface
- Configure a Layer 3 LAN Interface
- Configure Application Reachability Probes
- Configure a Secondary IP Address
- Configure a Static ARP
- Configure a DHCP Relay
- Configure IP Directed Broadcast
- VPN Keep-Alives
-
- Configure Prisma SD-WAN IPFIX
- Configure IPFIX Profiles and Templates
- Configure and Attach a Collector Context to a Device Interface in IPFIX
- Configure and Attach a Filter Context to a Device Interface in IPFIX
- Configure Global and Local IPFIX Prefixes
- Flow Information Elements
- Options Information Elements
- Configure the DNS Service on the Prisma SD-WAN Interface
- Configure SNMP
-
-
- Prisma SD-WAN Branch Routing
- Prisma SD-WAN Data Center Routing
-
- Configure Multicast
- Create a WAN Multicast Configuration Profile
- Assign WAN Multicast Configuration Profiles to Branch Sites
- Configure a Multicast Source at a Branch Site
- Configure Global Multicast Parameters
- Configure a Multicast Static Rendezvous Point (RP)
- Learn Rendezvous Points (RPs) Dynamically
- View LAN Statistics for Multicast
- View WAN Statistics for Multicast
- View IGMP Membership
- View the Multicast Route Table
- View Multicast Flow Statistics
- View Routing Statistics
- Prisma SD-WAN Incident Policies
-
- Prisma SD-WAN Branch HA Key Concepts
- Configure Branch HA
- Configure HA Groups
- Add ION Devices to HA Groups
- View Device Configuration of HA Groups
- Edit HA Groups and Group Membership
-
- Configure Branch HA with Gen-1 Platforms (2000, 3000, 7000, and 9000)
- Configure Branch HA with Gen-2 Platforms (3200, 5200, and 9200)
- Configure Branch HA with Gen-2 Embedded Switch Platforms (1200-S or 3200-L2)
- Configure Branch HA for Devices with Software Cellular Bypass (1200-S-C-5G)
- Configure Branch HA for Platforms without Bypass Pairs
- Configure Branch HA in a Hybrid Topology with Gen-1 (3000) and Gen-2 (3200) Platforms
- Prisma SD-WAN Incidents and Alerts
Configure and Attach a Collector Context to a Device Interface in IPFIX
A collector context is an ID to associate with an interface of the ION device. We can
configure and assign a collector context in IPFIX Prisma SD-WAN.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
A collector context is an optional ID to associate
with an interface of the ION device. The interface acts as the source
interface for the IPFIX packets exported from the ION device to
the collector.
- Select ManageResourcesConfiguration ProfilesIPFIXContextsCreate Collector Context.Enter a name and an optional description and Save the collector context.(Optional) Use the IPFIX collector context when configuring a collector as part of either an IPFIX profile or when configuring IPFIX profile overrides on the device.You need to attach the collector context to an interfaceon the ION device to designate the interface as a source interface for exporting IPFIX packets.You can define multiple collectors that use the same collector context, but you can assign the IPFIX collector context to only one interface of an ION device.
Attach a Collector Context to a Device Interface
Attach a collector context to an ION device interface to configure the device interface as a source interface for exporting flow records. You cannot attach a collector context to more than one interface on the same device, however you can reuse the collector context for different devices.If you do not bind a collector context to an interface, the device uses the controller port by default to establish the connection with the third-party collector. For platforms that do not have a controller port, it is mandatory to specify a collector context and bind it to an interface. Otherwise, the device raises a major alarm DEVICE_SW_IPFIX_COLLECTORS_DOWN.The device raises the DEVICE_SW_IPFIX_COLLECTORS_DOWN major alarm only when it is not able to connect to any of the configured collectors. There may be different collector configurations on a device that use different collector contexts. If the device is able to connect to any of the configured collectors, it will not raise the DEVICE_SW_IPFIX_COLLECTORS_DOWN alarm.There are two ways of attaching a collector context to a device.- Select a collector context and assign it to a device interface.
- Select ManageResourcesConfiguration ProfilesIPFIXContextsCollector.Click the ellipsis icon for an IPFIX Collector Context, select View Interface Bindings, and then click Bind Interfaces.Select a device and an interface to bind the collector context and Save.You can assign a collector context to any of the following interfaces:
Interface Type Supports Collector Context Controller Yes Virtual Ports Yes Loopback No Standard VPN No Virtual Interfaces Yes Port Channel No Sub-interfaces Yes PPPoE Yes Bypass Pair Yes (Optional) Repeat the procedure to bind the collect context to an interface on another device.Select a device interface and then assign the collector context.- Select ManageSetup DevicesClaimedSelect a deviceConfigure the deviceInterfaces.Select an interface to assign as a source interface for exporting flow records.Select a previously configured IPFIX Collector Context and Save.You can assign a collector context to only one interface of an ION device.