Flexible Netflow

[Daniel Smith]

I need to move to Netflow V9, and am not sure if I am heading down the right path. I have the following config in place, and am generating test flows with a Smartbits. However, I never see the router export a net flow packet. Any ideas?

!
flow record test-flow-name
match ipv4 tos
match ipv4 dscp
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match interface input
match interface output
collect transport icmp ipv4 type
collect transport icmp ipv4 code
collect transport tcp source-port
collect transport tcp destination-port
collect transport tcp flags
collect transport udp source-port
collect transport udp destination-port
collect transport udp message-length
collect counter bytes
collect counter packets
collect timestamp sys-uptime first
collect timestamp sys-uptime last
!
!
flow exporter test-harvester
destination 10.92.99.121
source Loopback0
template data timeout 60
!
!
flow monitor test-monitor
record aep-flow-name
exporter aep-harvester
cache timeout active 60

interface GigabitEthernet0/2
ip address 10.41.22.254 255.255.255.0
ip flow monitor test-monitor input
ip flow monitor test-monitor output
duplex auto
speed auto

[skarthic]

flow exporter test-harvester
 destination 10.92.99.121
 source Loopback0
 template data timeout 60
!
!
flow monitor test-monitor
 record aep-flow-name
 exporter aep-harvester -------->
 cache timeout active 60

Hi,

Shdn't the exporter name be "test-harverster" ?

Please try changing "exporter aep-harvester" to "test-harvester". The exported command must have

one of the flow exporters name.Or do u have an exporter with name "aep-harvester".

Regards.

[Daniel Smith]

I had tried to sanitize the config before posting and missed that one line. The line should read 'test-harve

ster'. However, with that config in place. No luck. IN order to get Netflow packets to be exported, I had to add in some global commands:

ip flow-cache entries 50000
ip flow-cache timeout active 1
ip flow-export source Loopback0
ip flow-export version 9
ip flow-export destination 10.92.99.121 9995

Which to me seems to bypass the flow exporter configuration.

[Don Jacob]

I think the destination port is not defined in the flow exporter which is why NetFlow is not being exported. Set the export port in the exporter using the command 'transport udp 9996' (9996 is the default port for ManageEngine) and then check the issue. You may need to remove the flow exporter from the monitor to edit it.

Regards,

Don Thomas

ManageEngine NetFlow Analyzer