Diameter Signaling Router (DSR) After Adding New MP to Server Group It Is Reporting Communication Agent Connection Down with Alarm ID 19800

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

Solution Type Problem Resolution Sure

Solution 2391955.1 : Diameter Signaling Router (DSR) After Adding New MP to Server Group It Is Reporting Communication Agent Connection Down with Alarm ID 19800

Applies to:

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

Symptoms

After Adding MP to the Server Group on site 1, It has ComAgent Connection down with C-level Servers of other sites.

Alarm ID 19800 : Communication Agent Connection Down

Changes

Upgrade to 7.3.1

Cause

Site 1 was upgraded to DSR 7.3.1 where as other sites were still on DSR 7.3.0 release.

Site1:

[admusr@SODSR1-a ~]$ appRev
Install Time: Sat Apr 21 23:35:07 2018
Product Name: DSR
Product Release: 7.3.1.0.0_73.20.0
Base Distro Product: TPD
Base Distro Release: 7.0.3.0.0_86.46.0
Base Distro ISO: TPD.install-7.0.3.0.0_86.46.0-OracleLinux6.7-x86_64.iso
ISO name: DSR-7.3.1.0.0_73.20.0-x86_64.iso
OS: OracleLinux 6.7

Site2:

[admusr@SODSR2-b ~]$ appRev
Install Time: Tue Jun 13 22:31:59 2017
Product Name: DSR
Product Release: 7.3.0.0.0_73.18.0
Base Distro Product: TPD
Base Distro Release: 7.0.3.0.0_86.46.0
Base Distro ISO: TPD.install-7.0.3.0.0_86.46.0-OracleLinux6.7-x86_64.iso
ISO name: DSR-7.3.0.0.0_73.18.0-x86_64.iso
OS: OracleLinux 6.7

Due to upgrade barrier, data replication between the sites will be disabled.

So when the MP was added to the server group on site1 (upgrade to 7.3.1) it will not be able to replicate to other sites.

In general making topology changes while operating in mixed version mode is not supported because topology tables and some application tables will not be replicated.

Across sites ComAgent Auto connections are made by reading the entries from the table ComAgtAutoConn (a replicated table).

The replication from NO to SO and from SO to C-LEVEL servers may work fine but the data i.e. entries for the MP will not replicate from the NO to SO and from SO to C-LEVEL servers of other sites and further it will not get replicated to the C-LEVEL servers. Thus, the C-LEVEL server will not process the incoming ComAgent connection request from the newly added MP.

We do see the tables are not replicated between Site1 and other sites :

Site1 NOAM with 7.3.1 has 2137 entries
[admusr@NODSR1-a ~]$ iqt ComAgtAutoConn|wc -l
2137

Site1 SOAM with 7.3.1 has 2137 entries
[admusr@SODSR1-a ~]$ iqt ComAgtAutoConn|wc -l
2137

Other Site SOAM with 7.3.0 has 2107 entries
[admusr@SODSR2-b ~]$ iqt ComAgtAutoConn|wc -l
2107

Solution

To overcome this situation it is advised to finish all other sites upgrade.

Once all sites are on same release then add the MP to the server group.

Attachments

This solution has no attachment