These instructions assume:
- You’re running Firepower Management Center (FMC) software version 6.2 or higher.
- Firepower Threat Defence (FTD) devices are connected to your FMC device.
- The date, time and time zone are correctly set on the Firepower devices.
- You have login credentials and admin access to your Firepower Management Center.
- The IP address of your Auvik collector is known.
If you are using a shared collector and want TrafficInsights to associate flow data with the correct site, you must add the source IP address as a dedicated /32 network within Auvik.
For example:
192.168.1.10/32Even if the source IP address is already included in a larger monitored subnet, a dedicated /32 entry is required for TrafficInsights to correctly associate flow records with the appropriate site.
After making this change, it may take several minutes before flow data appears in TrafficInsights.
Set the Auvik collector parameters
- Navigate to Objects
- Click on Objects Management
- Click on FlexConfig
- Click on Text Object
- Edit the netflow_Destination object
- In this variable, set the interface sending Netflow, the Auvik collector IP address, and the port
Note: You need to change the count to 3, it is 1 by default.
Create the FlexConfig Policy
- Navigate to Device
- Click on FlexConfig
- Click on New Policy
- Give a name to the policy
- Select the Firewall(s) to receive the policy
- Click Save
- Select the objects: Netflow_Add_Destination and Netflow_Set_Parameters
It will look like this: - Click Save
- Deploy on the target firewall
- Go to the Auvik portal
- Click on TrafficInsights
- Approve the flow
You may see a message in TrafficInsights informing you that no templates are being sent from the device. Do not troubleshoot it right away. Wait for about 30 to 60 minutes and check it again.
