Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

ASA 8.4(5) NetFlow Problem

After we upgraded our Cisco Asa firewalls to version 8.4(5), NetFlow exports from the Asa cannot be processed by Solarwinds NTA. The error is as follows:
NetFlow Receiver Service [SECUOMNF01] received an invalid V9 template with ID from device.

This problem started with Asa version 8.4(5), no problems in previous versions.

Asa flow-export configuration:

flow-export template timeout-rate 1

flow-export delay flow-create 30

flow-export active refresh-interval 1

Find more posts tagged with

template

asa

8.4(5)

netflow

cisco

nta

Accepted answers

All comments

Sohail.Bhamani

It doesnt seem like that is enough config to export flows from an ASA. Here is a KB article showing some of the additional config you will need.

http://knowledgebase.solarwinds.com/kb/questions/795/Configuring+Cisco+ASA+devices+for+use+with+Orion+NTA

I realize the KB is written for an older version of the ASA IOS, but the commands should generally be the same.

Sohail Bhamani

Loop1 Systems

http://www.loop1systems.com

p01nt5h0t

Hello Sohail,

I did not write the whole netflow export config. There is nothing wrong with the configuration. Asa is sending flow exports to the NTA server (I captured packets with Wireshark installed on the Solarwinds NTA server).

I think Cisco has changed the NetFlow template on version 8.4(5) and Solarwinds NTA is not compatible with the new template.

choly

Hi p01nt5h0t,

This is an issue we are aware of, and we are currently investigating the root cause.

choly

For future reference - there is a HotFix 3 for NTA 3.10 available that addresses the issue.