SFlow routing

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.

Thanks. I understand the possibility of mgmt. interface saturation but was curious why the destination would be limited to a local subnet. I've linked the Sflow output to a local firewall and NET'td the connection. I just need to get data through the device to see if it all works. I'll add a post once once I have it working. Thanks for you responses they're greatly appreciated.