Diameter Signaling Router (DSR) - How to Clear 19901 Alarm on DSR Where Subsequent DB Operations are ALLOWED

Asset ID:	1-71-2068431.1
Update Date:	2017-06-15
Keywords:

Solution Type Technical Instruction Sure

Solution 2068431.1 : Diameter Signaling Router (DSR) - How to Clear 19901 Alarm on DSR Where Subsequent DB Operations are ALLOWED

Applies to:

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

Goal

How to clear a 19901 alarm where subsequent db operations are ALLOWED

Solution

The 19901 alarm sometimes appears after update operations, indicating that the MP may not have received the full update or there are minor differences detected between the master database and the MP's version. In some cases, the alarm should appear due to the update timing, but should clear and does not. This is a stuck alarm, and may be cleared manually. Other cases, the issue may be persistent signaling that there are differences that need to be resolved. In either case, the method to resolve that will leave the highest confidence the databases are in sync is to reboot the MP so it can get a new copy of the database. This operation is recommended to be done during a maintenance window.

SERVER: dsr-mp1
SEQ_NUM: 1268
EVENT_NUMBER: 19901
SEVERITY: MAJOR
PRODUCT: STK
PROCESS: dsr
TYPE: STK
INSTANCE:
NAME: CFG-DB Validation Error
DESCR: A minor database validation error was detected on the MP server during an update. MP internal database is now out of sync with the configuration database. Subsequent database operations on the MP are ALLOWED.
ERR_INFO:
GN_INFO/WRN
ConfigError<PreUpdateError> in file DpiDbRecordHandler.C at line 6087:
Failed updating the ipfeTsaIpAddresses container for for TSA# 4
^^ [29714:DbRecordHandler.C:759]

Procedure to reboot:

Log into the active NOAM and SOAM, capture the Alarms & Events / View Active output [use the <Export> function and save locally]
Reboot the MP server. Recommend accessing the server console via iLO, then when logged into the command line as root and issue the 'init 6' command. This will allow you to observe the boot progression. If you SSH'd to the iLO address, you could also record the progression output to the buffer (using PuTTY, for instance). If you don't want to use the command line method, you can also go to the NOAM / Status & Manage / Server, highlight the MP, and select 'Reboot' button at the bottom of the screen.
After recovery & the MP has stabilized, you can again capture the Alarms & Events / View Active output as before so we can get a view to any change in alarm status pre- and post-.

References

<NOTE:2275219.1> - Problem to Activate Traces on IDIH SOAM, Can Not Edit or Delete the Trace, System Reporting the CFG-DB Validation Error 19901

Attachments

This solution has no attachment