Issue with setting up replication on software version of PubSub+

Options
PFSolace
PFSolace Member Posts: 8 ✭✭
edited July 2023 in PubSub+ Event Broker #1

I have 2 docker desktop instances of Solace running soltr_10.4.1.66: Solace14 and Solace15 10.0.0.15 and 10.0.0.16 respectively.
Both instances have static IP configured, hostname configured via docker compose file and these settings are working - right after building containers each host is accessible via ping command by ip or hostname ("ping Solace15" works on Solace14 and vice versa). Only 3 ports are exposed:'9014:8008', '8014:8080', '5014:55555' for Solace14 and ports ending with 9015:8008 etc. for Solace15.
I tried to do replication following the guide on this solace guide multiple times but each time I had issues with messages not being replicated from active to standby Solace instance. I ended up with preparing commands to both instances as I found this way of providing configuraiton faster than any other way: In case of issues I deleted the container, removed the storage volume attached to it and recreating all containers using docker-compose up command. This way I ended up in fresh installation and was able to configure containers with commands attached. Commands are divided into sections according to above guide this is why I start with point 3.

The order of commands that were executed is below. Commands are attached in 2 files.

S14: point 3
S15: point 3
S14: point 4
S15: point 4
S14: point 5, with confirmation
S15: point 5, with confirmation
S14: point 6
S15: point 6
S14: point 7
S15: point 7
S14: point 8
S15: point 8

S15 first:
S15: point 9
S14: point 9

S14 only:
S14: point 10

S14: point 11
S15: point 11

Status after all actions:
Queue created automatically on Solace15.
S15: bridge #MSGVPN_REPLICATION_BRIDGE incoming up.

solace15(configure)# show bridge #MSGVPN_REPLICATION_BRIDGE
Total # Bridges : 3 of 50
Local Bridges : 2 of 25
Remote Bridges : 1 of 25
Total Bridge Subscriptions : 0 of 20000
Flags Legend:
A - Admin State (U=Up, D=Down, -=not-applicable)
E - Connection Establisher (L=Local, R=Remote, -=not-applicable)
I - Inbound Oper State (U=Up, D=Down, -=not-applicable)
O - Outbound Oper State (U=Up, D=Down, -=not-applicable)
Q - Queue State (U=Up, D=Down, -=not-applicable)
R - Redundancy Type (P=Primary, B=Backup, A=Auto -=not-applicable)
Local Remote Remote Status
Name MsgVpn MsgVpn Router A E I O Q R Uptime
#MSGVPN_REPL mvpn mvpn v:solace14 U L U - U P 50m 29s
ICATION_BR
IDGE

on Solace14:

solace14# show bridge #MSGVPN_REPLICATION_BRIDGE
Total # Bridges : 3 of 50
Local Bridges : 2 of 25
Remote Bridges : 1 of 25
Total Bridge Subscriptions : 0 of 20000
Flags Legend:
A - Admin State (U=Up, D=Down, -=not-applicable)
E - Connection Establisher (L=Local, R=Remote, -=not-applicable)
I - Inbound Oper State (U=Up, D=Down, -=not-applicable)
O - Outbound Oper State (U=Up, D=Down, -=not-applicable)
Q - Queue State (U=Up, D=Down, -=not-applicable)
R - Redundancy Type (P=Primary, B=Backup, A=Auto -=not-applicable)
Local Remote Remote Status
Name MsgVpn MsgVpn Router A E I O Q R Uptime
#MSGVPN_REPL mvpn D - D - - P N/A
ICATION_BR
IDGE
solace14#

Additionally, I set up ack-propagation interval messages 1 on Solace14.

Messages sent to queue Solace/Replicated/1 on Solace14 are not replicated to Solace15.
When trying to connect to Solace15 as replication1user to queue Solace/Replicated/1 there is an error:
Consumer could not bind to the queue:
Consumer Ack Propagation Enabled when Replication is Standby

Command 'show queue Solace/Replicated/1' detail shows:
S14: Current Messages Spooled : 4

S15: Current Messages Spooled : 0

My question is:
What should I change to get the replication working in my setup ?
Maybe I dont understand something in replication but I believe if messages are being replicated to standby mate I should be able to see how many messages are pending on standby mate if they are not consumed on active replication mate.