Forum Discussion

Brad_Baker's avatar
Aug 14, 2018

Maintaining Config on Load Balancers in Multiple Locations

For those that have systems in multiple locations how do you handle config synchronization? So say you have:

Location1:
    Load Balancer1 
        VIP www.mydomain.com
            web1
            web2
            web3

Location2:
    Load Balancer 2 
        VIP www.mydomain.com
            web4
            web5
            web6

You can't keep the two LTMs in sync because location1 and 2 have different backend nodes unless you had multiple VIPs like: .

Then one of the VIPs in each location just isn't used. That seems a little messy and error prone though? You end up with double the VIPs, if you point to the wrong VIP at the wrong location traffic either might not pass or might be very slow.

If you don't do that though what's the alternative? Maintaining each load balancer as stand alone devices? So every time you need to change an irule or SSL certificate you have to do it on multiple devices? That seems like it would have issues too.

Is there a better way of approaching this?

Thanks Brad

  • If you don't have or want to use BIP-IQ or Enterprise Manager or some other configuration management system you can setup multiple sync groups per device and link them to partitions and folders.

     

    This means you can place common configuration like profiles, irules, SSL certificates and keys etc in the folders that will sync between locations. Your location specific configuration like Virtual Servers, Pools, Nodes etc in partitions/folder that will not sync.