Upgrading F5 units configured as Active-Active without Traffic Groups behind Azure LB
When upgrading F5 units configured as Active-Active, without failover link config, load balanced using Azure Load balancer to the respective units, will I face any issues with with config sync? Since I don't have failover link, my understanding is I don't have failover feasibility. Please share your inputs.BigDB.dat: Configsync.PeerIpaddr : No longer used in v11.6?
I have just found that the "[Configsync.PeerIpaddr]" section in the BigDB.dat contains an IP address that is different from what I get from: tmsh list /cm device my_device_name configsync-ip , and it does not get overwritten by changes done via the Configuration Utility. It seems that this variable is no longer used in v11.6.x. Can anybody confirm this?