Oracle Communications Diameter Signaling Router (DSR)
 

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

In this Document

Symptoms

Changes

Cause

Solution

Confirm the issue

Solution

References

Created from <SR 3-13966849092>

Applies to:

Symptoms

DSR 5.x, Event ID 25510 - Multiple DA-MP Leader Detected

Changes

Cause

The “multiple MP leader” alarms were a common occurrence going back to DSR 3.0. We've observed these with upgrades (application, and firmware), maintenance activities, DSR process restarts, as well as with network interruptions. Because of continuous product improvements (MP race conditions), this has not been a known issue in releases above 6.x/7.x. The Customer is encouraged to upgrade from DSR 5.x to the latest GA release.

Solution

Confirm the issue

1. Active SOAM GUI (Screen Capture)
   1. Navigate to "Main Menu: Diameter -> Maintenance -> DA-MPs"
      Please make sure that the 'MP Leader' column, under the 'Peer DA-MP Status' Tab is visible.
      Here you should be able to determine which MP is incorrectly reporting to be the MP leader, as the other MPs would not see it (from the '# Peer MPs Unavailable' column).
2. Active SOAM GUI (Screen Capture):
   1. Navigate to "Main Menu: Diameter -> Maintenance -> DA-MPs"
   2. Click on the Tab for the MP you suspect is incorrectly reporting to be the MP leader, and take a screen capture.
      Here, the MP should be showing a status of 'Unknown' or some error message.
3. MP CLI (This is the MP you suspect to be reporting incorrectly) :
   
   # appRev; cmver; apw_version
   # date; uptime
   # ha.mystate -w
   # ha.info -d
   # syscheck
   # alarmMgr --alarmStatus
   # ra.stat -m -w
   # inetmstat -w
   # irepstat -w
   # irepstat -w -l -k
   # pl
   # df -kh
   # /usr/TKLC/plat/sbin/savelogs_plat --workdir=/var/TKLC/db/filemgmt/
   The last command is a script that will create a file called 'savelogs_plat...tar.bz2' in the '/var/TKLC/db/filemgmt' directory. Please attach all outputs, and the 'savelogs' file to the SR.

Solution

Restart the DSR application for the MP (This is the MP you suspect to be reporting incorrectly from previous chapter).

From the active NOAM Server (GUI):

1. Navigate to "Main Menu: Status & Manage -> Server"
2. Highlight the MP server, click “Restart”, then “OK” to initiate MP Application restart.

References

This solution has no attachment