Moved 1 of my VEs to new vcenter now fail over doesn't work
Opening a ticket right now but... sometimes find better/quicker answers here.
We have had a pair of VEs latest 17.1 running in the same vcenter for years, recently migrated one over to a new/separate vcenter in same data center.
I don't know all the details of how that is configured, as I don't run the vcenter env but I do have read access.
From what I can see , I think that we have promiscuous, forged transmits and mac address changes all set to reject/deny on both the old and new platform. However, failover has always worked perfectly on the old platform where both Units sat side by side on the same vcenter datacenter.
Now after the migration, the 2nd unit's mgmt IPs work fine, self IPs are fine, every indication that it is up and healthy is there, except when we go to fail over, I would say the IPs aren't "moving" and we just end up dropping traffic. As soon as I make the old unit active again it's fine.
We do not use mac Masqerading and haven't used it since we went virtual (if I recall correctly... when we migrated to virtual, the mac masq was removed either by the conversion process or by an individual, I don't know if that is the best practice or not).
Wanted to see if anyone had any quick input while I wait for F5 feedback?