After Binding SBR switch over, Binding Query Tool query results in error [Error Code 21266] Psbr Soap Fault: Could not connect to host <hostname of stdby Binding SBR>

Asset ID:	1-72-2181018.1
Update Date:	2017-11-12
Keywords:

Solution Type Problem Resolution Sure

Solution 2181018.1 : After Binding SBR switch over, Binding Query Tool query results in error [Error Code 21266] Psbr Soap Fault: Could not connect to host

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 6.0 and later
Information in this document applies to any platform.

Symptoms

There are certain instances where the Binding Query Tool will not work if a switch over is performed on the Binding SBR by stopping the dsr application.

When testing the Binding Query Tool it was discovered that when you stop the dsr application on the Active Binding SBR to force a switch over, the Binding Query Tool will query the previously Active Binding SBR. The result is a failure in the GUI, [Error Code 21266] Psbr Soap Fault: Could not connect to host <hostname of stdby Binding SBR>

Changes

N/A

Cause

The dsr application is stopped on the active Binding SBR to cause a switch over. Causing a switch over by stopping the DSR application is an acceptable way to cause a switch over but due to the Bug found in the Binding Query Tool the switch over should not be performed this way.

Solution

The work around until the Binding Query Tool bug is resolved:

If a switch over of the Binding SBR is necessary.

To force the switchover of the Binding SBR, go to Status & Manage > HA select Edit and set the Max Allowed HA Role on Active Binding SBR to OOS. This will cause the switch over and the Binding Query Tool will query the Newly Active Binding SBR as it should and the query will be successful. Note: The Max Allowed HA Role on the OOS server will need to be set back to Active once the switch of activity is complete.

Attachments

This solution has no attachment