Config-Sync not successful after failover to backup node

PubSub+ Event Broker
1

Hello All
Recently we have issue on config-sync in Solace HA setup. solace usual setup with primary / backup / Monitor.

there is no issue with Redundancy, when we move primary to backup.
The same time Config-sync show down one of the environment.

same setup with 5 set of solace HA was up and running no issue.
except the one set of solace HA have issue on its config-sync.

installation and configuration steps are same as the similar working environment.

solace1> enable
solace1# configure
solace1(configure)# hardware message-spool shutdown
All message spooling will be stopped.
Do you want to continue (y/n)? y

solace1(configure)# redundancy
solace1(configure/redundancy)# switchover-mechanism hostlist
solace1(configure/redundancy)# exit
:

solace2(configure)# redundancy
solace2(configure/redundancy)# group
solace2(configure/redundancy/group)# create node solace1
solace2(configure/redundancy/group/node)# connect-via solace1.solace.come.com
solace2(configure/redundancy/group/node)# node-type message-routing-node
solace2(configure/redundancy/group/node)# exit
solace2(configure/redundancy/group)# create node solace2
solace2(configure/redundancy/group/node)# connect-via solace2.solace.come.com
solace2(configure/redundancy/group/node)# node-type message-routing-node
solace2(configure/redundancy/group/node)# exit
solace2(configure/redundancy/group)# create node solace3
solace2(configure/redundancy/group/node)# connect-via solace3.solace.come.com
solace2(configure/redundancy/group/node)# node-type monitor-node
solace2(configure/redundancy/group/node)# exit
solace2(configure/redundancy/group)# exit
solace2(configure/redundancy)# authentication
solace2(configure/redundancy/authentication)# pre-shared-key key
solace2(configure/redundancy/authentication)# exit
solace2(configure/redundancy)# active-standby-role backup
solace2(configure/redundancy)# no shutdown

after set up all 3 node, we did validation for faiover

solace1> show config-sync

Admin Status : Enabled
Oper Status : Down
Authentication
Client Certificate
Maximum Chain Depth : 3
Validate Certificate Dates : Enabled
Client-Profile
TCP
MSS : 1460
Initial Window : 2
Maximum Window : 256 KB
Keepalive
Count : 5
Idle : 3 seconds
Interval : 1 seconds
Client
Name : #config-sync/solace1
Connection State : Connected
Last Fail Reason :

solace2> show config-sync

Admin Status : Enabled
Oper Status : Oper Status : Down (local table has a problem:
(0,Router,‘site’))
Authentication
Client Certificate
Maximum Chain Depth : 3
Validate Certificate Dates : Enabled
Client-Profile
TCP
MSS : 1460
Initial Window : 2
Maximum Window : 256 KB
Keepalive
Count : 5
Idle : 3 seconds
Interval : 1 seconds
Client
Name : #config-sync/solace1
Connection State : Connecting
Last Fail Reason :

Any Idea, currently we are running with work around
with option inside the group using ip

with all the three node
solace2(configure/redundancy/group)# create node solace1
solace2(configure/redundancy/group/node)# connect-via 192.168.132.3
solace2(configure/redundancy/group/node)# node-type message-routing-node
solace2(configure/redundancy/group/node)# exit
solace2(configure/redundancy/group)# create node solace2
solace2(configure/redundancy/group/node)# connect-via 192.168.132.4
solace2(configure/redundancy/group/node)# node-type message-routing-node
solace2(configure/redundancy/group/node)# exit
solace2(configure/redundancy/group)# create node solace3
solace2(configure/redundancy/group/node)# connect-via 192.168.132.5
solace2(configure/redundancy/group/node)# node-type monitor-node
solace2(configure/redundancy/group/node)# exit
solace2(configure/redundancy/group)# exit
solace2(configure/redundancy)# authentication
solace2(configure/redundancy/authentication)# pre-shared-key key
solace2(configure/redundancy/authentication)# exit
solace2(configure/redundancy)# active-standby-role backup
solace2(configure/redundancy)# no shutdown

2

Hi @venkatn80, I don’t think I’ve ever seen that one before, so I can’t personally give you a likely reason for it. You seem to think that using IP address rather than hostname has affected config-sync, is that right?

I think the easiest thing to do would be to get config-sync in a good state. Can you bring solace1 up, enable redundancy, then make solace1 primary. Then examine the config-sync state on both solace1 and solace2. That will give us a starting point for going further.

3

Hello Tom
Happy thanks for the update. Yes if we make good state config sync then make solace1, as primary again it work for it, but, when we check manual release activity also for primary reboot will move redundancy to backup this is normal behaviour redundancy.
Then after config sync back again the situation i share before like that, I thought you guys meet this before, but wonder your side as well new. OK I will do it again this week will let you know anything positive new.

Same time any other suggestion, then kindly share.
Thanks again for the quick replay.