hsflowd Polling Interval

64 views
Skip to first unread message

Thomas Shen

unread,
Oct 23, 2017, 7:43:10 PM10/23/17
to Host-sFlow
Hi,

I am using 2.0.8-1 and I have configured counter polling interval to be x seconds. The collector receives the export samples every 2x seconds. I thought this was supposed to be every x seconds. I've verified hsflowd is receiving x in the configuration and was unable to find any documentation that the interval is doubled. Is this a bug or an undocumented feature? Apologies if I've missed the documentation.

Thanks,

Thomas

Neil McKee

unread,
Oct 23, 2017, 8:17:59 PM10/23/17
to Thomas Shen, Host-sFlow
I checked with the latest version (2.0.11) on Linux and it does seem to be a little off,  but not as much as a factor of 2 (when I set "polling" to 8 seconds I'm getting samples every 9 or 10 seconds,  but when I set it to 1 then I get samples every second).   If you try 2.0.11 then please let me know what you see.

------
Neil McKee
InMon Corp.
http://www.inmon.com

--
You received this message because you are subscribed to the Google Groups "Host-sFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to host-sflow+unsubscribe@googlegroups.com.
To post to this group, send email to host-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/host-sflow/8ecdd0bd-1792-4d1a-b405-0223c1d3cc13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thomas Shen

unread,
Oct 24, 2017, 12:54:00 AM10/24/17
to Host-sFlow
Hi Neil,

Thanks for checking. I tried the latest and it is much better. Logs below. First two packets are for 2.0.8-1 and shows 19.8 second interval. Rest are for 2.0.11 and shows around 12 second interval. Similar improvement for 20 second interval. At least it has mostly been fixed.

Thanks,

Thomas


tcpdump -n -i lo 'port 6343'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 65535 bytes

2.0.8-1
13:34:25.117597 IP 127.0.0.1.47170 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:34:44.960763 IP 127.0.0.1.47170 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
  


2.0.11
13:38:45.482381 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:38:57.476985 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:39:09.471478 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:39:21.466185 IP 127.0.0.1.52343 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692

Using 20 second interval:

2.0.8-1 (~39.8 seconds)
13:44:22.590410 IP 127.0.0.1.42988 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:45:02.273512 IP 127.0.0.1.42988 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:45:41.956961 IP 127.0.0.1.42988 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692

2.0.11 (~24 seconds)
13:46:45.470938 IP 127.0.0.1.47797 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:47:09.458107 IP 127.0.0.1.47797 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692
13:47:33.445218 IP 127.0.0.1.47797 > 127.0.0.1.6343: sFlowv5, IPv4 agent 172.29.105.62, agent-id 1, length 692

Reply all
Reply to author
Forward
0 new messages