Posted on February 22, 2021 11:26 pm
 |  Asked by Michael Johnson
Print Friendly, PDF & Email


We are trying to configure IPFIX on our campus switch (CCS 720XP) running EOS 4.25.1F and want to utilize the IPFIX Hardware Export capability to send flows for tracking to CloudVision Portal running version CVP2020.2.3 but we are not able to have any active flows being formed to be exported. We tried running with flow tracking sampled (for IPFIX) and we got see the active flows populated by looking at show flow tracking sampled flow-table command but no display on CVP – Traffic Flows tab. Am I missing something?


Below is the configuration (for Hardware-based export) for what we expect:

flow tracking hardware
tracker ftr1
record export on interval 3000
exporter exp1
collector <cvp-ip-address>
local interface loopback0
template interval 5000
record format ipfix standard timestamps counters
no shutdown

int Ethernet1
flow tracker hardware ftr1
no shutdown

720XP-IDF#show flow tracking hardware
Flow Tracking Status
Type: Hardware
Running: yes
Standard record format for counters: yes
Standard record format for timestamps: yes
Tracker: ftr1
Active interval: 3000ms
Inactive timeout: 10000ms
Groups: IPv4, IPv6, VxlanIPv4, VxlanIPv6
Exporter: exp1
VRF: default
Local interface: Loopback0 (
Export format: IPFIX version 10, MTU 9152
Template interval: 5000ms
x.x.x.x port 4739
Active interfaces:



Posted by Tamas Plugor
Answered on February 22, 2021 11:31 pm

Hi Michael,

The collector IP has to be, as TerminAttr on EOS is doing the collector part, which then streams the data to ingest on CVP.




Post your Answer

You must be logged in to post an answer.