Solace bridge no starting.

General Discussions
1

I have created a unidirectional guaranteed message bridge between my solace vpns which are on same broker but the bridge status still seems to be down, can someone help me what i missed.

a576a7d2708c(configure/message-vpn)# show bridge guaranteed_bridge

Total # Bridges : 1 of 50

Local Bridges : 1 of 25

Remote Bridges : 0 of 25

Total # with Connect-Via : 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

guaranteed_b TESTVPN1 TESTVPN2 U - D - - A N/A
ridge

a576a7d2708c(configure/bridge)# show bridge guaranteed_bridge detail

Bridge Name: guaranteed_bridge
Message VPN
Local: TESTVPN1
Remote: TESTVPN2
Redundancy: auto
Admin State: Enabled
Conn Establisher: NotApplicable
Inbound Oper State: NotReady-WaitNext
Outbound Oper State: NotApplicable
Queue Oper State: NotApplicable
Connection Uptime: 0d 0h 0m 0s
Authentication
Scheme: Basic
Basic
Default Client Username: default
Password Configured: No
Client Certificate
Certificate File:
Using Server Certificate: No
Transport Property
Compressed: -
SSL: -
Retry Count: 0 of 0
Retry Delay: 3 seconds ( 2 remaining )
Max TTL: 8
Dto Priority: P1
Client Name:
One Shot Events
TTL Exceeded: not raised
Subscriptions
Local: 0
Remote: 0

Remote Message VPN: TESTVPN2 via 127.0.0.1:55555 ()
Admin State: Enabled
Connect Order: 4
Connect Port Mode: non-compressed, non-ssl
Connection State: Down (Login Response: The RADIUS profile is shutdown)
Message Spool
Queue: my_queue
Queue Bind State: Down (Not connected)
Queue Bind Uptime: 0d 0h 0m 0s
Window Size: 255
Unidirectional
Client Profile: #client-profile

2

This points you in the right direction:


Connection State: Down (Login Response: The RADIUS profile is shutdown)

RADIUS is the default (old legacy) authentication mechanism when you create a new Message VPN. You’ll probably want to amend the basic authentication to “internal” or “none” on your remote VPN (not the VPN where your bridge is, but where it’s connecting to). Internal means you’ll need to have a client-username and password for the bridge to connect with. And that client-username will have to be associated with a client-profile that allows bridges to connect. And of course, if you are making this a Guaranteed bridge, the client-profile on the remote VPN will also have to allow send/receive of Guaranteed messages, and you’ll need a queue in the remote VPN for your bridge to connect to.