I'm getting this event:
You have not enabled NetFlow data export on 192.168.200.1 device. For more information, see "Enabling NetFlow and NetFlow Data Export (NDE) on Cisco Catalyst Switches" in the Support - Product Documentation area of www.solarwinds.com.
This must be some kind of bug in NTA, because clearly server receives data, but just doesn't understand it. As told, at the beginning netflow was coming from wrong VLAN, but even then, Orion understood that something IS coming in! Then I changed netflow source interface from switch to VLAN 1 (switch management vlan, which is managed by Orion) and that error disappeared. As said, server seems to undestand that netflow is coming in, but it just cannot draw it to graphs?!?
So, I'll open the ticket now or what?
Solved. I had to create a record. Normally "netflow-original" should do the job, but in Supervisor 2T there is no such a command at all. It's replaced with "platform-original" and I think it doesn't work correctly with NTA. Platform-original configuration sends netflow to NTA but Orion doesn't understand it, I don't know why. But when I replaced this "emulated" netflow with manual record, it started to work ok.
We have the exact same issue but i don't think i understand the solution to this problem...
Can someone explain to me a bit more in details about what needs to be done to make it work?
This comes very late, but didn't see this before. So you need basics? In old netflow you write command after command as normal configuration. But in flex netflow (if you don't use "emulated netflow" which doesn't work in NTA) you have to create a so called "sub-programs" into router configuration and IOS jumps between these programs to know what to do and when. You need 3 netflow elements: Record (here i use word Settings), monitor and exporter.
Looking from interface side of view:
1. Interface has netflow command that points to Monitor sub-program.
2. Monitor tells router what to capture (settings "sub-program") and where to send data (in this case to orion server).
3. Settings tells router what to capture.
Sound complicated, but there can be several Monitor and Settings configurations, so the idea is to tell which interface is using which netflow setting. I don't know did that help anything, because of my bad english, but at least I tried.
Here is the configuration I use:
flow record SETTINGS
match datalink vlan input
match ipv4 version
match ipv4 tos
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match interface input
match flow direction
collect counter bytes
collect counter packets
flow exporter EXPORTER1
description Netflow exporter 1 to SERVER233
transport udp 9996
template data timeout 60
flow monitor MONITOR1
cache timeout active 1
interface vlan NN
ip flow monitor MONITOR1 output