LTM and ASM configuration synchronization without Sync-Failover enabled
Hi everybody,
My question is related to the point of configuration synchronization of LTM and ASM modules between two VE appliances. We have 2 VE VMs in two different geographically dispersed DC environments (1 VM per DC). VM software versions are identical - Version 15.0.0 build 0.0.39. L2 connectivity is already in place between those VMs. The goal is to get appliance configuration synchronized between those VMs (vservers, nodes, pools, ASM policies, bot defense configuration, etc). Unfortunately, due to routing design constraints we are not able to deploy Sync-Failover device groups and each appliance operates in standalone mode. Also, as far as I have understood, at least vserver, node and pool related configuration is not synchronized while using Sync-Only device groups. I am wondering whether it is possible to customize Sync-Only mechanism (or maybe achieve this with other means) and get something like LTM/ASM manual incremental configuration synchronization but without failover feature enabled? I have found information that it is possible to customize UCS configuration backup and include additional files/folders into archive but is it doable to get something similar with configuration synchronization?
Thank you!
Great explanation.
I'd recommend building an Active/Active Sync-failover group with one traffic group per DC
Manual Chapter : Creating an Active-Active Configuration using the Configuration Utility
Split the floating IPs and VIPs into traffic groups using the relevant subnets, and optionally enable BGP Route advertisement.