Hello We activated sflow on our HP 7500 switch as explained in the HP manual. Executing the SFlow test we see that everything works smoothly except that the Data Format reports all packages failed. So we infer that the switch is not executing the Flow Data format in the Raw pachet Header.

Obviously if we are going to activate a SFlow sensor on the PRTG monitor this is never populated and is waiting for data.

We wanted to ask you if you have already dealt with a similar issue and if there is a resolvable reason. in the documentation of HP we did not find anything about SFlow Data format.

Thanks for the attention Best regards

Article Comments

Hi there,

Do you see any flows within our SFlow Tester? Note that the original sensor needs to be paused in order for the tester to occupy the port.

Kind regards,
Stephan Linke, Tech Support Team


Jan, 2018 - Permalink

Hello Stephan, thank you so much for your answer

Yes, in the box "Decoded Flows..." there are lines of visible flows, the only anomaly is that in the box PRTG Compatibility the "(6) Data Format:" has the same number under "OK" and "Failed".

if we then activate SFlow Sensor, it remains perpetually awaiting data.

thank you for your time

Regards


Jan, 2018 - Permalink

Could you post a screenshot of that? Thanks!

Kind regards,
Stephan Linke, Tech Suppor Team


Jan, 2018 - Permalink

Please drop us a mail via support@paessler.com and lets continue there, since the screenshots are containing IP addreses which should stay unpublished. Please also provide me with the settings. The traffic is rather large, about a terabyte for one connection for example. Does this match the actual traffic?


Jan, 2018 - Permalink

Was there any resolution on this? I am trying PRTG and hoping to buy but all attempts to get my HP 5406 using sFlow to PRTG are failing. However if I stop the sFlow sensor and use the Tester it is flowing - but like the original poster - the failed packets equal the ok packets and no data ever shows in the sensor. I have tried both sFlow and sFlow custom.

There was a another thread https://helpdesk.paessler.com/en/support/solutions/articles/74967-sflow-problems-with-hp-procurve-2810 with the same issue - different HP Procurve switch model.


Apr, 2018 - Permalink

Not at this time. The user never sent us the flows we needed so we could examine them.


Apr, 2018 - Permalink

Support got back to me on my issue. Nothing to do with the HP or PRTG. My issue was putting the IP address of the switch in the SenderIP field. Leaving that blank solved the issue - simply used the filter fields to narrow the scope.

Scott


Apr, 2018 - Permalink

Glad to hear it!


Apr, 2018 - Permalink