Netflow collection not working on VIPs

Question

After migrating our Solarinds infrastructure to Azure, we have been facing issue with receiving Netflow on VIP IPs. Currently all devices are pointing the Netflow to our Primary Additional Polling engines which works, but the moment it fails over to the secondary node, the Netflow collections stops unless the devices shift their netflow to secondary node IP or the primary server becomes the active polling engine again.

Was wondering what are we missing. The other thing I have noticed is all our Active Polling Engines will have two records in DNS, one with Server's own IP and other with the HA VIP. and the resolution keeps hovering between the two resulting in RTO whenever the resolution shifts to VIP record.

I believe the NTA issue might have something to do with the way IPs are assigned on server and DNS. Has anyone faced similar issue ever?

ver. 2025.4.0

Thanks

HerrDoktor · Answer

Last time I checked, Single Subnet Failover with a VIP is not supported in Azure. Only Multi-Subnet with DNS entry is supported.

As you can only configure Netflow destination as an IP, you need to simultaneously send Netflow data to both HA pair servers.

They will get discarded on the passive node. Only the active node will be processing Netflow data.

cnorborg · Answer

I don't think we're having that issue?   So you have configured the Netflow on the device to send to the VIP and not the primary poller, right?    Do you have firewall rules that might prevent it?   Are both of your HA pair on the same subnet?