Forum Discussion

Kevin_Manavadar's avatar
Kevin_Manavadar
Icon for Nimbostratus rankNimbostratus
Mar 05, 2015

Sync datagroups in Bigip

We are having multiple bigips in every locations.

 

We have some datagroup which are same in all, we need to synchronize those datagroup to all bigip.

 

All bigip are different and not in cluster or sync mode. All having different configuration.

 

Please provide me some solution or any inputs from your end.

 

3 Replies

  • The option that I've used in the past would be to use tmsh to get the config and then merge it on the target machine(s).

    Get the config like this and copy it:

    tmsh list ltm data-group internal DG_NAME
    Set the config on the other ones like this:
    tmsh
    >>
    load sys config from-terminal merge verify
    . (Then paste the config and execute it. To merge it instead of "verify"ing it, just take off the verify)

  • you could Create a partition just for your data-groups and add that folder to a sync-only group on all your devices. Only that partition woul then be replicated amongst your devices.

     

  • Hi Kevin,

    if it would be an option to use external datagroups you can automate the distribution of shared elements to each unit and import from CLI via script, i.e.:
    tmsh modify sys file data-group datagroup_exernal source-path file:/var/tmp/datagroup_external.class
    tmsh save sys config partitions all
    

    This will replace the current datagroup with the content of the file in /var/tmp/ after distributing it i.e. via SCP.

    If it comes to import multiple files (may be external datagroups, keys/certs, monitors or iFiles) you can automate it as I described here (just change to the modify syntax):

    Import key, certificate, data-group (class), external monitor and iFile objects to TMOS v11 filestore from CLI

    I´m not sure if admin partitions will be helpful as the objects in a specific partition cannot be used by objects i.e. in the common partition (at least I didn´t find a way by now).

    Thanks, Stephan

    PS: This requires to run TMOS v11+.