Yes. we have mixed binding of IPs on clustered hub as well.
What we've done was in the controller config...
- Force hostname of cluster to something like NMSCluster
- Force the IP to be VIP of the cluster
if robot version is >= 5.11
added the following line to the <controller> section of your robot.cfg:
local_ip_validation = no
so it stops trying "fix" IP
The hub config should also show the VIP as IP address near the license.
I have had to have people re-login or click advance button on IM and reselect the cluster to login but for most part it fails over if they are already logged in