[ERROR] sflow: we do not support vendor specific enterprise numbers

41 views
Skip to first unread message

Kees Louwen

unread,
Oct 29, 2024, 10:33:36 AM10/29/24
to FastNetMon user group
Hello, 

I test the fastnetmon community edition with sflow enabled and get this error in the log file fastnetmon.log : 

[ERROR] sflow: we do not support vendor specific enterprise numbers

I have tested with another sflow collector and that works fine with same agent (hsflowd) config. 

Any thoughts on this? 

thanks. 

addtional info:

fastnetmon server: 
Ubuntu 24.04 LTS
fastnetmon --version
Version: 1.2.8 a427d8b6  (not sure why I see 1.2.8 which is not on the community github..used installer on 2024.10.28 ?)

sflow agent on switch:
OS cumulus linux 5.7
host-sflowd -  hsflowd  2.0.30-1-cl5.3.0u1

if I check the code where the message is posted from ( I assume): 

it seems to check on enterprise != 0  

so I traced the package with tcpdump but all I see is enterprise 0 ( see below )

snippet of tcpdump on the fastnetmon vm of the sflow package (port 6343):

14:23:21.027733 0c:42:a1:28:4a:38 > bc:24:11:34:56:ef, ethertype IPv4 (0x0800), length 858: (tos 0x0, ttl 64, id 35656, offset 0, flags [DF], proto UDP (17), length 844)
    10.100.0.21.51347 > 10.100.0.14.6343: sFlowv5, IPv4 agent 10.100.0.21, agent-id 100000, seqnum 91641, uptime 87282272, samples 4, length 816
        counter sample (2), length 128, seqnum 4364, type 0, idx 16, records 2
            enterprise 0, Unknown (1005) length 12
                0x0000:  0000 0005 7377 7031 3300 0000
            enterprise 0, Generic counter (1) length 88
              ifindex 16, iftype 6, ifspeed 10000000000, ifdirection 1 (full-duplex)
              ifstatus 3, adminstatus: up, operstatus: up
              In octets 8516737, unicast pkts 64460, multicast pkts 11957, broadcast pkts 0, discards 0
              In errors 0, unknown protos 4294967295
              Out octets 7797460, unicast pkts 62646, multicast pkts 11959, broadcast pkts 0, discards 0
              Out errors 0, promisc mode 0
        counter sample (2), length 204, seqnum 4364, type 3, idx 148490, records 5
            enterprise 0, Unknown (2103) length 52
                0x0000:  0000 0000 0000 0000 0000 0000 0000 0000
                0x0010:  0000 0000 0000 0000 0000 0000 0000 0000
                0x0020:  00b5 814a 0000 0000 0000 0000 001b 6afd
                0x0030:  0000 0000




Pavel Odintsov

unread,
Oct 29, 2024, 10:40:51 AM10/29/24
to Kees Louwen, FastNetMon user group
Hello, Kees!

Thank you for report.

If you can capture the whole pcap with all sFlow data then I can check it with engineers.



--
Follow us on social media: Twitter: https://twitter.com/fastnetmon | Facebook: https://www.facebook.com/fastnetmon/ | LinkedIn: https://www.linkedin.com/company/fastnetmon/
---
You received this message because you are subscribed to the Google Groups "FastNetMon user group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fastnetmon+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/fastnetmon/0380a1f3-4dbd-4be6-998b-76ac9b55573bn%40googlegroups.com.


--

___________

Kind regards,

Pavel Odintsov

CTO, FastNetMon LTD

fastnetmon.com


Kees Louwen

unread,
Oct 30, 2024, 3:08:20 AM10/30/24
to FastNetMon user group
Thanks, please attached a pcap file with the sflow data. 
regards, Kees

Op dinsdag 29 oktober 2024 om 15:40:51 UTC+1 schreef Pavel Odintsov:
sflow_data.pcap

Pavel Odintsov

unread,
Nov 7, 2024, 3:31:38 AM11/7/24
to Kees Louwen, FastNetMon user group
Hello!

We've checked it and it's not an actual error. You're safe to ignore it as it does not affect parsing of packets.  

The issue with this sFlow sample that your agent does not send any flow information at all:

sflow_bad_packets: 0
sflow_flow_samples: 0
sflow_bad_flow_samples: 0

And I can confirm it after checking pcap.

"I have tested with another sflow collector and that works fine with same agent (hsflowd) config. "

Another vendor may read per interface counters which are not useful for FastNetMon as we use only raw packet headers and they're missing in this pcap.

I can recommend checking configuration or raising ticket to vendor.

Thank you!

Reply all
Reply to author
Forward
0 new messages