GSLB Sync Stops Working After ADC Upgrade to 13.0-58.x or 13.0-61.x Builds

GSLB Sync Stops Working After ADC Upgrade to 13.0-58.x or 13.0-61.x Builds

book

Article ID: CTX281430

calendar_today

Updated On:

Description

GSBL Autosync stops working.
After executing CLI command "sync gslb config -preview" one may get the below error

> sync gslb config -preview
Sync Time: Jul 25 2020 8:17:3
Retrieving local site info: ok
Retrieving all participating gslb sites info: ok
GSLBSite_DC1[Master]:
Getting Config: ok
GSLBSite_DC2[Slave]:
Error executing command on gslb site...ERROR: Connection failed
Make sure that you have:
1. Configured the Local GSLB site on all the GSLB Sites.
2. Enabled the management access on GSLBSITEIP using set ns ip command.
3. Configured the firewall to accept autosync connections by specifying the remote site IP (clip for cluster setup) and port (3010 for RPC and 3008 for secure RPC).

Trying to connect using SSH...
unable to establish master SSH connection: master process exited unexpectedly
Make sure that the keys are setup appropriately
Could not connect to node DC2. Aborting ...
Done

When tracing the network traffic - despite of setting Secure rpcNode (to work over 3008 port) communication is attempted to establish over 3010 port.
 

Resolution

Permanent code fix available in upcoming 13.0-64.x build (tentative ETA first week of September)

Problem Cause

Code defect investigated under issue ID#NSHELP-24178

NOTE:  
Only ADC 13.0 release is affected (builds: 58.32 and 61.48)
GSLB Sync configured over secure TCP port: 3008 (rpcNode Secure set to ON).