For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Deee-blue_14536's avatar
Deee-blue_14536
Icon for Nimbostratus rankNimbostratus
Jan 22, 2016
Solved

SFlow routing

Hi All,   I want to setup SFlow sending to a Solarwinds(SW) server. The standard polling is between the SW server and the mgmt. port. Will SFlow use the same mgmt. interface and route or will I n...
application delivery
LTM
Deee-blue_14536's avatar
Deee-blue_14536
Icon for Nimbostratus rankNimbostratus
Jan 28, 2016

Thanks for the reply Eric. Do you know why the destination address must be in a local subnet?

 

Eric_Chen_12394's avatar
Eric_Chen_12394
Historic F5 Account
Jan 28, 2016
The explanation that I've seen before is that if you're processing a lot of sFlow data (i.e. on multiple 40 Gbit interfaces) it would be possible to saturate the 1 Gbit management port. If the sFlow collector is only accessible via the mgmt interface it is possible to create an isolated route domain (using a data plane interface) that sits on the same network as the mgmt interface and reference the collector by route domain notation (i.e. mgmt: 192.168.1.245/24, tmm_mgmt_rd1: 192.168.1.246%1/24, sFlow target: 192.168.1.10%1). Depending on preference/network policy this may or may not be desirable.