Float a single broker with podman for each of the two vm’s with static ip.
I’m working on the DR configuration between the two brokers.
But even if I follow the official document, I can’t replicate it, and before that, the operating status of config-sync is still down. What should I do?
I’m going to use Node03 as the primary
I’m going to sweep Node04 into DR
Node03(show)> config-sync
Admin Status : Enabled
Oper Status : Down (remote replication table has a
problem: (2,Vpn,‘dr-vpn’) [stale])
SSL Enabled : No
Client-Profile
TCP
MSS : 1460
Keepalive
Count : 5
Idle : 3 seconds
Interval : 1 seconds
Client
Name : #config-sync/Node03
Connection State : Connected
Last Fail Reason :
Synchronize
Username : Yes
Node04(show)> config-sync
Admin Status : Enabled
Oper Status : Down (remote replication table has a
problem: (2,Vpn,‘dr-vpn’) [stale])
SSL Enabled : No
Client-Profile
TCP
MSS : 1460
Keepalive
Count : 5
Idle : 3 seconds
Interval : 1 seconds
Client
Name : #config-sync/Node04
Connection State : Connected
Last Fail Reason :
Synchronize
Username : Yes
PubSub+ Enterprise Evaluation
Warning: The following procedure cannot be reversed. Once the Enterprise
Evaluation key is installed the broker will cease to function after 90 days
and all configuration will be lost unless it is upgraded to PubSub+
Enterprise prior to the 90 day expiration.
To start a 90 day evaluation of PubSub+ Enterprise:
1) Create an instance of PubSub+ Standard (using your preferred packaging).
2) Enter the PubSub+ CLI and run the following commands:
solace> enable
solace# admin
solace(admin)# product-key quscWoxxdp4-Gg88sDQ9dcA-k8vnR1QrpBr-EVAL-G-GA_1
3) Restart the instance.
---
I follow this guide
I am trying to set up the same configuration and am encountering the same issue. I followed the same process used for the PubSub+ Enterprise Evaluation, but I am still facing this problem.
Could you please suggest a possible solution and what the underlying cause might be?
Additionally, I would like to confirm whether redundancy needs to be enabled in this setup for config-sync to work with replication.
Glad to see you trying out the enterprise eval. Sorry you’re running into issues. To be honest I’m not an expert on our DR configuration. I’ll get this in front of someone who is.
Thank you for the response, I really appreciate it. No worries at all. I’m glad you’re helping get this in front of someone with more expertise on the DR configuration.
In the meantime, I’ll continue debugging the issue from my side to see if I can identify the root cause and a possible solution.
I’m jumping in from the technical support team to help you troubleshoot.
Based on the “Oper Status” you’ve shared, there appears to be a problem with Replication config-sync. Here are some possible causes to investigate:
Possible Causes:
The replication message VPN bridge is down
show bridge #CFGSYNC_REPLICATION_BRIDGE detail
Check if the #CFGSYNC_REPLICATION_BRIDGE is up and operational.
The queue state is ‘unbound’
Verify that #CFGSYNC_REPLICATION_QUEUE is properly bound.
The SMF service is not enabled Ensure the SMF (Solace Message Format) service is enabled on your broker.
Connect-via settings are misconfigured Review your connect-via address, port, and SSL settings.
TLS-PSK authentication configuration issue
Important: If you’re using the newer TLS-PSK authentication key, you must have mate connect-via configured for SSL using port 55443, even if your replication bridges use plaintext.
Can you also confirm which documentation you followed to configure DR? I assume you used the official guide: Steps for Replication Configuration