Hi Axel,
Thanks for this notice.
On 2/15/12 11:34, Axel Fischer wrote:
> Hi list,
> at first a big thanks to everybody working and contributing to the project
> especially Peter. Keep up the good work.
>
> I have nfsen 1.3.6p1 and nfdump 1.6.5 running with "$EXTENSIONS = 'all';" on a
> 64Bit Debian. When starting to configure profiles e.g. to group routers
> together
> I used the exporter addresses (router ip). The numbers in the graphs were not
> adding up so I checked what exporters are really in the profile. The Netflow
> exporters (v5) were listed but the Sflow exporters (v5) were not. The live
> profile showed that _not_ the Sflow agent address is used but the interface IP
> were the Sflows are send from to the server. If the exported flows take a
> different path the interface (address) changes. The Sflow exporting routers
> are
> Brocade NetIron XMR.
>
> I dumped a few Sflow packets and checked with wireshark that the agent address
> is in there and it is.
>
> - Why is the agent address not used?
> - Is this a bug? If yes is there a fix?
> - Or am I missing something?
That's correct. Times back, when sflow was implemented, the same approach was
taken
as with netflow. That's for the 'why'. If it's a bud depends on the view :)
However, I see the point, and if this is something required, I'd happily will
change
that. I'll contact you off list.
- Peter
>
>
> Regards,
> Axel
>
--
--
Be nice to your netflow data
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
