You have to make sure that you leave the processes on for enough time that
your routers send a template packet that describe the netflow data. Until
nfsen receives the template, it (and wireshark as well) doesn't decode the
data. The routers can send this packet once every few seconds, up to one
every hour or so...
On Thu, Aug 28, 2014 at 12:59 PM, Juan Quintanilla <
juan.quintani...@dante.net> wrote:
> Hi list,
>
>
>
> We have NfSen deployed in our environment for many years now.
>
> I am in the process of migrating from netflow v5 to v9 our Juniper devices.
>
>
>
> During the tests, I can see flows are reaching the server, but not
> processed – there’s not a single flow in the channel.
>
>
>
> We are running nfsen 1.3.6 and nfdump 1.6.6
>
>
>
> Config in nfsen.conf is the same as for the other devices:
>
>
>
> 'device' => { 'port' => '<number>', 'col' => '#0000ff' },
>
>
>
> Is there anything I am missing?
>
>
>
> Many thanks in advance for your help.
>
>
>
> Regards/Saludos,
>
>
>
> Juan
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds. Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Nfsen-discuss mailing list
> Nfsen-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
>
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Nfsen-discuss mailing list
Nfsen-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
