NS12.0 add cluster node, node sync stuck in "IN PROGRESS" state
Article ID: CTX236729
Updated On:
Description
Customer have new added a cluster node to an existing cluster. The new added node synchronization state stuck in "IN PROGRESS" state. But customer found configuration files have already synced.
Resolution
Change Backplane switch jumbo frame setting from 1500 to a bigger value.
Problem Cause
Synchronization stuck due to new added node cannot establish TCP Connection to CCO.in ns.log, you may see the following logs for this problem.
Enable debug log on Netscaler through System>Auditing>Syslog settings， You can get more detailed logs about the synchronization process.
Refer log pattern:
cat /var/log/ns.log |grep cluster
Jul 11 15:13:00 <local0.info> ns [1510]: cld_fullsync_req_handler(): Received config sync START message from Clusterd (sync_id=2)
Jul 11 15:13:00 <local0.info> ns [22327]: cfsync_pullcfg_n_apply(): Connection failed [Could not connect to any of master nodes provided in sync start message from clusterd]
Jul 11 15:13:00 <local0.info> ns [22327]: cld_fullsync_req_handler(): Sync FAILURE sent to clusterd for sync_id=2
Jul 11 15:13:00 <local0.info> 172.16.1.73 07/11/2018:07:13:00 GMT 2-PPE-2 : default CLUSTERD Message 1394 1531293180485406 : "REC: status FAILURE from client CFSYNCD for ID 2 "
cfsync_pullcfg_n_apply(): Connection failed [Could not connect to any of master nodes provided in sync start message from clusterd]\
After check, customer found it was caused by backplane switch jumbo frame setting.
