1 of 1 people found this helpful
Majority of the time this is caused by not having the active timeout command configured on the Netflow sources. Check to see if the commands below are configured. The commands below are for Cisco devices but most other vendors also have this command available.
By default most network devices export long-lived flows every 30 minutes which cause high spikes over what the circuit is configured for. The recommended value is 1 minutes to ensure all Netflow cached data is exported every 1 minute.
If using traditional Netflow version 5 this is the command
ip flow-cache timeout active 1 ( in minutes)
If you are using Flexible Netflow the command will be in the flow monitor configuration
flow monitor NetFlow-Monitor
description Original Netflow captures
cache timeout inactive 10
cache timeout active 60 ( in seconds)