Forum Discussion
the config sync is like config repository which means f5 devices in the Device Group will store shared data replica (e.g. floating ip, virtual server config but not self (static) ip)
so for example if a device is corrupt and you deply new device, then the new device can simply get the shared config by joining the device group.
vip can be shared (in active-standby mode) only if the devices can have Self IP and Floating IP in Traffic Group (basically same IP subnet; in addition to joining same Device Group).
there is workaround to allow separate traffic group to use same VIP using OSPF/BGP and LTM VS RHI method but i think it's not necessary in your case because the upfront GCP LB will load balance both F5 LBs.
https://techdocs.f5.com/en-us/bigip-14-1-0/big-ip-tmos-routing-administration-14-1-0/dynamic-routing.html#GUID-7CDA4A41-3148-4D5F-B031-45E14190398E
- awan_mMay 20, 2024
Cirrostratus
does this mean i need to apply workarounds to make a Active active config work? i am looking for a step by step config for GCP Active Active serup.