Diameter Signaling Router (DSR) : Both NOAM's Showing As Standby In GUI

Asset ID:	1-72-2391920.1
Update Date:	2018-04-27
Keywords:

Solution Type Problem Resolution Sure

Solution 2391920.1 : Diameter Signaling Router (DSR) : Both NOAM's Showing As Standby In GUI

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0.1 and later
Tekelec

Symptoms

After Upgrade of Standby NOAM to DSR 7.0.1, Both NOAMs are showing as Standby in GUI.

Changes

DSR 5.0 to DSR 7.0.1 Upgrade

Cause

After upgrade of standby NOAM (NOAM-B) from DSR 5.0 to 7.0.1 a switchover is required to make NOAM-B as Active and start the upgrade of NOAM-A.
At this point NOAM-B continued to show Standby Status in GUI.

ha.mystate showed Active state for NOAM-B and it showed Active role

[admusr@NOAM-B ~]$ ha.mystate
            resourceId   role         node       subResources      lastUpdate
         DbReplication Active    A3943.086                  0 1218:153716.788
                   VIP Active    A3943.086                  0 1218:153716.791
        CacdProcessRes Active    A3943.086                  0 1218:153716.791
        CAPM_HELP_Proc    OOS    A3943.086                  0 1214:222058.875
           DSROAM_Proc Active    A3943.086                  0 1218:153716.782
        CAPM_PSFS_Proc    OOS    A3943.086                  0 1214:222058.876
[admusr@NOAM-B ~]$

So, Only issue is GUI has not updated its correct status after the Upgrade Switch over.

Solution

The above symptoms indicate that the apwSoapServer process is not updating the GUI Status correctly,

It is recommended to restart the apwSoapServer process on Active NOAM CLI i.e. NOAM B

After the restart of this apwSoapServer process GUI started to show correct status.

Procedure to Restart apwSoapServer process :

pm.set off apwSoapServer
pm.set on apwSoapServer

Attachments

This solution has no attachment