Configure Prisma SD-WAN 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 Prisma SD-WAN IPFIX
Configure Prisma SD-WAN IPFIX (provides network and application visibility by
transmitting flow information to an external collector) globally for multiple or for a
single ION device.
Where Can I Use This? | What Do I Need? |
---|---|
|
|
Prisma SD-WAN IPFIX provides network and application
visibility by transmitting flow information to an external collector. This increased
awareness allows for more efficient network operations, decreased operation costs,
and better utilization of the network infrastructure.
IPFIX monitors traffic across the network by collecting traffic records
at different points in the network. The ION device exports these flow records to
third-party collector applications. The IPFIX implementation and the terms used are
based on the guidelines outlined in RFC 7011
(https://tools.ietf.org/html/rfc7011). You can use the exported IPFIX records for
various purposes such as network management and planning, optimized troubleshooting,
enterprise accounting, studying trends in performance metrics, data mining,
understanding network anomalies, and protecting the network from security
vulnerabilities.
Configure IPFIX to apply to all sites and
devices globally or configure IPFIX for an ION device to override
the global IPFIX configuration.
- Configure IPFIX globally for multiple ION devices.Configure IPFIX globally by creating an IPFIX profile and attaching it to multiple ION devices.
- Configure an IPFIX profile.Bind IPFIX profiles to ION devices.To verify that you have pushed the IPFIX profile to a device, select ProfilesEdit a profileView Device Bindings. The IPFIX configuration bound to the device displays in the Device Binding column.Configure IPFIX on a device to override the global IPFIX profile settings.You can optionally configure device specific IPFIX parameters to override parameters such as collectors, filters, and sampling configured in an IPFIX profile.
- Select ManageDevicesClaimedSelect a deviceConfigure the deviceIPFIX.Enter a name and select a profile from the IPFIX Profile drop-down and Save.(Optional) Click the + icon next to IPFIX Profile to create an IPFIX profile.
- When you create a new profile at the device level, it becomes a part of the global profiles and you can use it for multiple devices.
- You can optionally configure an IPFIX templat, configure collectors, filters and sampling on the ION device to override the parameters configured in the IPFIX profile.
The ION device uses the collectors, filters, and sampling configured in the IPFIX profile, unless you provide optional overriding configuration.Configure High Availability (HA) for IPFIX
Prisma SD-WAN supports High Availability (HA) between ION devices by ensuring automatic switchover between active and backup devices, maintaining all services and forwarding paths when an ION device experiences a software, hardware, or network related failure.To ensure uninterrupted IPFIX exports, replicate the IPFIX configuration on both devices.- Configure interfaces.Configure interfaces as per the network topology.Configure and attach the same IPFIX profile to both the ION devices.Attach the collector context to both the ION devices.(Optional) If using filters, attach the filter context to both the ION devices.After a device switchover, the collector application receives IPFIX records from the new source interface, so this is considered as a new IPFIX session.