F5 sFlow with ManageEngine Netflow

I tried running sflow to ManageEngine and I get that F5 is sourcing an incorrect self-IP that isn't in the traffic path for sflow via MPLS. It is sourcing an IP that goes out to the Internet even though routing takes sflow traffic across internal MPLS for 10.10.X.X addresses. This causes a new device in OpManager to be built which gives no info at all as SNMP isn't enabled on that sourced IP and there are no interfaces to look at for monitoring. This is very weird and I haven't been able to see any documentation on this issue.