Oracle Communications Diameter Signaling Router (DSR)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
 

In this Document

Goal

Solution

Created from <SR 3-15529056371>

Applies to:

Goal

DB Merging and Replication Alarms (including 31106 31107 31114) seen after Disaster Recovery (DR) on MP Server

After performing the disaster recovery on a server, a default route was failed to add on vlan interface (bond2.x).
after fixing the default route, observed a new alarm which is related to data replication.


Further investigation showed Server server is not able to communicate with servers at the other site.

Solution

As suspected I see that server in question does not contain a specific route that would allow it to communicate with
server at the other site.

From the previous savelogs the xmi IP addres for server at the other site is:

  inet 1yy.2xx.xxx.199/25 brd 1yy.2xx.xxx.255 scope global xmi
  
From the output of ip route (which can also be seen in the NOAM GUI on Main Menu: Configuration -> Networking -> Routes) server in question shows:

1yy.2xx.xxx.0/25 dev bond1 proto kernel scope link src 1yy.2xx.xxx.ab

However a healthy server shows:

1yy.2xx.xxx.0/25 dev bond1 proto kernel scope link src 1yy.2xx.xxx.ac
1yy.2xx.xxx.128/25 via 1yy.2xx.xxx.1 dev bond1

The absence of specific route "1yy.2xx.xxx.128/25 via 1yy.2xx.xxx.1 dev bond1" makes the server in question unable to communicate with servers at other site.
Please add this specific route to server in question via the NOAM GUI on Main Menu: Configuration -> Networking -> Routes. You may also want to confirm if there are other routes that should be added based on routes provisioned on other servers in same server group as well.

 ----------------------------------------------------------

Note: This issue is often the result of routes showing a status of "Discovered" in the NOAM GUI on "Main Menu: Configuration -> Networking -> Routes" before Disaster Recovery is performed on the server.
A status of Discovered implies that the route was not added via the GUI (in was added on command line of the server) and so it would not automatically be re-added during the DR process.
Adding the routes back via the GUI will give them a state of "Deployed" and will help ensure that they would not need to be readded manually after a DR is done on the server.

This solution has no attachment