topic Re: ProCurve 2910al sFlow in Switches, Hubs, and Modems

ProCurve 2910al sFlow

Kenneth Østrup — Mon, 14 Dec 2009 15:47:43 GMT

Hello,

I am having trouble configuring a ProCurve 2910al switch for sending sFlow packets.

As far as I can understand, on this model switch, I can configure sFlow directly from CLI, and not only through SNMP.

I am setting up according to this example:

sflow 1 destination 10.19.0.100 6343
sflow 1 polling ethernet 1-15 20
sflow 1 sampling ethernet 1-15 512

However on the destination server, I am running nfcapd (with sFlow support).
But I am not getting any data from the switch.

If I listen directly to the interface, I cannot see any UDP on port 6343.

The switch has previously been configured to use sFlow.

If I run:

walkmib 1.3.6.1.4.1.14706

I see the old configuration. Even if I set the old configuration parameters to zero or
their default setting, they show up there again eventually?

Is there a configuration parameter which I am missing, or have I completely misunderstood something?

Re: ProCurve 2910al sFlow

cenk sasmaztin — Mon, 14 Dec 2009 22:43:51 GMT

fristly
nfcapd don't support sFlow ,nfcapd Netflow protocol

http://manpages.ubuntu.com/manpages/intrepid/man1/nfcapd.1.html

please test currunt sflow connector

Re: ProCurve 2910al sFlow

cenk sasmaztin — Mon, 14 Dec 2009 22:45:06 GMT

current sflow connector
http://www.sflow.org/products/collectors.php

Re: ProCurve 2910al sFlow

Kenneth Østrup — Thu, 17 Dec 2009 13:50:28 GMT

Hello,

Correct. By default, nfdump does not have sFlow support enabled. E.g. the package in the Ubuntu repository.

sFlow can however be enabled during compilation.

Therefore I must correct myself, from my first post stating I was using "nfcapd". I am using "sfcapd".

However, the problem is, as I see it, not within the client software.

But that I am not seeing any sFlow packages coming from the switch.

I have no idea where to look for debug info regarding this. Can anybody help me?

Re: ProCurve 2910al sFlow

Kenneth Østrup — Thu, 17 Dec 2009 16:35:13 GMT

Update:

I have resolved the problem. It was not due to a switch problem. But a configuration issue, specific for my network setup, which I had overseen.