SflowTrend not working

[Shane Hanson]

Hello

I'm running sFlowTrend 6.2 on a windows 2k8 R2 VM with the latest JDK. I can confirm that the box is seeing sflow traffic on 6343 (using wireshark) and that is the port that sFlowTrendis listening on. However it's not receiving packets from any agents other than 0.0.0.0. (i.e. the green light RHS does not flash)

I have uninstalled and reinstalled, I have also re-installed after deleting the directory c:\programdata\inmon

Any suggestions before I give up totally?

Thanks

SHANE

[Stuart Johnston]

Shane,

If sFlowTrend is showing 0.0.0.0 as an agent, then you will have a switch using this address as the agent. Some vendors default to this address, which is not very useful. Can you check this on your switches, and configure the agent address there?

If sFlowTrend still isn't showing data, then one other thing to confirm is that a host firewall isn't blocking udp:6343. The Windows firewall needs to be configured as Administrator to allow it, since the service runs as Administrator. Also, wireshark inserts itself before the firewall, so that's not a good indication that things are ok. It's always worth trying temporarily disabling the firewall to test if this is the problem.

Regards,

Stuart

--
You received this message because you are subscribed to the Google Groups "sFlowTrend" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sflowtrend+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stuart Johnston]

Shane,

If sFlowTrend is showing 0.0.0.0 as an agent, then you will have a switch using this address as the agent. Some vendors default to this address, which is not very useful. It is not a valid address, and doesn't mean the local agent. Can you check this on your switches, and configure the agent address there?

If sFlowTrend still isn't showing data, then one other thing to confirm is that a host firewall isn't blocking udp:6343. The Windows firewall needs to be configured as Administrator to allow it, since the service runs as Administrator. Also, wireshark inserts itself before the firewall, so that's not a good indication that things are ok. It's always worth trying temporarily disabling the firewall to test if this is the problem.

Regards,

Stuart

On 31 Dec 2015, at 01:10, Shane Hanson <ist...@gmail.com> wrote:

[Shane Hanson]

Gidday, yep that's exactly what it was, configure the agent address on my switches the it jumped into life.

Thanks heaps for your help!

SHANE