NetScaler GSLB Synchronization Fails When Using Force Synchronization

NetScaler GSLB Synchronization Fails When Using Force Synchronization

book

Article ID: CTX210691

calendar_today

Updated On:

Description

Force Synchronization of configuration between two NetScaler GSLB sites is not successful through CLI or GUI.

There is no success message for GSLB sync. At times GSLB partial synchronization takes place and then an error occurs or at times the synchronization is initiated and does not proceed.

Force Synchronization Through CLI

User-added image 

Force Synchronization Through Through GUI

User-added image

The following are the ns.log file during the issue:

[gayatrig@sjanalysis-2 /upload/ftp/64673875/collector_P_10.20.64.82_18Dec2014_09_51/var/log]$ cat ns.log.* | grep sync
Dec 17 10:59:13 <local0.info> 10.x.x.82 12/17/2014:06:59:13 GMT egtc-corp-adc1 0-PPE-0 : GUI CMD_EXECUTED 159639 0 :  User nsroot - Remote_ip 127.x.x.1 - Command "show gslb syncStatus" - Status "Success"
Dec 17 07:19:30 <local0.info> 10.x.x.82 12/17/2014:03:19:30 GMT egtc-corp-adc1 0-PPE-0 : CLI CMD_EXECUTED 156924 0 :  User nsroot - Remote_ip 57.x.x.3 - Command "sync gslb config -forceSync DOZ -saveconfig" - Status "Success"
Dec 17 07:19:38 <local0.info> egtc-corp-adc1 nsgslbautosync: sync started
Dec 17 07:19:46 <local0.info> egtc-corp-adc1 nsgslbautosync: DOZ: Syncing gslb static proximity database: ok.
Dec 17 07:19:47 <local0.info> egtc-corp-adc1 nsgslbautosync: DOZ: Syncing ha files on the remote site: ok.
Dec 17 07:20:10 <local0.info> egtc-corp-adc1 nsgslbautosync: DOZ: Generating config: ok.
Dec 17 07:21:33 <local0.info> egtc-corp-adc1 nsgslbautosync: Error executing command on gslb site...Reason:  Done exec: unbind gslb service gslb_svc_TCP5614-itlinuxbl127 -monitorName tcp  Done exec: unbind gslb service gslb_svc_TCP5614-hqlinuxbl127 -monitorName tcp  Done exec: unbind gslb service gslb_svc_DOLINUXBL501_aacsfl -monitorName ping  Done exec: unbind gslb service gslb_svc_HQLINUXBL501_aacsfl -monitorName ping  Done exec: unbind gslb service gslb_svc_DOLINUXBL501_aacsfla -monitorName ping  Done exec: unbind gslb service gslb_svc_HQLINUXBL501_aacsfla -monitorName ping  Done exec: unbind gslb service gslb_svc_T6517-DOLINUXBL660 -monitorName tcp  Done exec: unbind gslb service gslb_svc_T6517-HQLINUXBL660 -monitorName tcp  Done exec: unbind gslb service gslb_svc_t5091-dolinuxbl613 -monitorName tcp  Done exec: unbind gslb service gslb_svc_t5091-hqlinuxbl613 -monitorName tcp  Done exec: unbind gslb service gslb_svc_H_10.20.211.201 -monitorName ping  Done exec: unbind gslb service gslb_svc_H_10.x.x.47 -monitorName ping  Done e
Dec 17 07:21:33 <local0.info> egtc-corp-adc1 nsgslbautosync: sync ended

Resolution

To resolve this issue create a different monitor for the GSLB service and load balanced service. In this case we created tcpGSLB monitor and bound it to GSLB service, and tcpLB monitor was created and bound to the load balanced service.


Problem Cause

When a force sync is initiated, the NetScaler removes the gslb config from the other site and then tries to copy it's own config. From the ns.log it was observed that this is where the failure occurs.
Done exec: unbind gslb service gslb_svc_T6517-DOLINUXBL660 -monitorName tcp 

The reason was that same monitor name tcp was bound to another load balanced virtual server service due to which we were not able to remove the configuration.

At present this is a bug which will be fixed in NetScaler 10.5.55.x build.

Issue/Introduction

Force Synchronization of configuration between two NetScaler GSLB sites is not successful through CLI or GUI.