Real-time synchronization between sites participating in GSLB

If you want to synchronize GSLB configuration across slave sites automatically when the commands are executed on master sites, you can now use the AutomaticConfigSync option to automatically synchronize the real-time GSLB configuration. You do not have to manually trigger the AutoSync option to synchornize the configuration.

If you attempt to manually synchronize (with the sync gslb config command) a site while it is being autosynchronized, a “Sync in progress” error message appears. Autosynchronization cannot be triggered for a site that is in the process of being synchronized manually.

Attention:

Starting with NetScaler 12.1 build xx.xx, SNMP traps are generated when you synchronize the GSLB configuration. Note that in real-time synchronization, the synchronization status in the first SNMP trap is captured as failure. You can ignore this status because a second SNMP trap is automatically generated immediately after the first trap with the actual synchronization status. However, if the synchronization failed in the second attempt also, SNMP trap is not generated because the synchronization status has not changed from the previous synchronization status.

For details on configuring NetScaler appliance to generate traps, see Configuring the NetScaler to generate SNMP traps.

Notes:

  • All logs related to real-time sync are stored in the /var/netscaler/gslb/periodic_sync.log file.
  • The sync status file and default configuration file are stored in the location /var/netscaler/gslb_sync.
  • Enabling AutomaticConfigSync from default partition of a partitioned appliance is not supported. However, it can be enabled from all other partitions. The sync status file and default configuration file are stored in the location /var/partitions/<partition name>/netscaler/gslb_sync.

Best practices for using the real-time synchronization feature

  • It is recommended that all the NetScaler appliances participating as sites have the sameNetScaler software version.
  • To change the RPC node password, first change the password on the slave site and then on the master site.
  • Configure local GSLB sites on each site participating in GSLB.
  • Enable automaticConfigSync on one of the sites where the configuration is performed. This site eventually gets synchronized to other GSLB sites.
  • If there is a new configuration or changes are made to the existing configuration, make sure to check the status using the “show gslb syncStatus” command to confirm if the changes are synchronized across all sites or if there was any error.

To enable real-time synchronization by using the CLI

At the command prompt, type:

set gslb parameter –automaticConfigSync (ENABLED | DISABLED)

Example:

set gslb parameter –automaticConfigSync ENABLED

To enable real-time synchronization by using the GUI  

  1. Navigate to Configuration > Traffic Management > GSLB > Change GSLB Settings.
  2. Select Automatic ConfigSync.

           Note: This option must be enabled only in the site where the configuration is performed.

Tip

For information on the following topics, see Manual synchronization between sites participating in GSLB.

  • Previewing GSLB synchronization
  • Debugging the commands triggered during synchronization process