How to Clear an Errant 22960 "DA-MP Profile Not Assigned" Alarm on a Diameter Signaling Router Operations Administration and Maintenance (OAM) Server

Asset ID:	1-71-2188264.1
Update Date:	2016-10-04
Keywords:

Solution Type Technical Instruction Sure

Solution 2188264.1 : How to Clear an Errant 22960 "DA-MP Profile Not Assigned" Alarm on a Diameter Signaling Router Operations Administration and Maintenance (OAM) Server

Applies to:

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

Goal

The goal of this document is to identify an Event ID 22960 "DA-MP Profile Not Assigned" critical alarm that has been asserted against an xOAM (NOAM - Network Operations Administration and Maintenance, or SOAM - Site Operations Administration and Maintenance) server in error, and how to safely clear the alarm.

Solution

The Event ID 22960 "DA-MP Profile Not Assigned" is raised as a CRITICAL alarm, and if it is valid it requires immediate attention. Once in a while the alarm is raised in error, usually traced to a user mistake while executing commands at the command line. Any time command-line activity is undertaken, care must be exercised because the software will not challenge the user intention. The GUI remains the standard interface for user actions.

If a user logged in at the command line accidentally issues the command 'dsr' the system will attempt to spawn the dsr process as instructed. Depending on the role of the server, this is unlikely to succeed but can have adverse consequences. In an xOAM server, the dsr process will fail to spawn however the Event ID 22960 "DA-MP Profile Not Assigned" will be raised. This alarm will not clear autonomously, but in this situation is not indicating any active error.

To identify the 22960 alarm raised in error, view the Alarm Report and check the Server, Instance, and INFO for the alarm. Here's an example:

Problem Details: TIMESTAMP: 2016-09-11 20:50:37.878 UTC
NETWORK_ELEMENT: DsrSOAM
SERVER: dsr-SOAM-b
SEQ_NUM: 2769671
EVENT_NUMBER: 22960
SEVERITY: CRITICAL
PRODUCT: DPI
PROCESS: dsr
TYPE: DIAM
INSTANCE: dsr-SOAM-b
NAME: DA-MP Profile Not Assigned

DESCR: A DA-MP configuration profile has not been assigned to this DA-MP.
ERR_INFO:
GN_INFO/FTL A DA-MP configuration profile has not been assigned to DA-MP: dsr-SOAM-b
^^ [22155:DaMpProfileManager.C:195]

Note all identify the same server, and the server --here evident by its hostname-- is not a DA-MP server.

If the server identified in any part of this Alarm Report is not a NOAM or SOAM server, STOP. This resolution is not applicable.

To clear this errant alarm log into the server named in INSTANCE of the alarm Report and execute the following command:

alarm.put -e 22960 -s 5 -i <INSTANCE>

Example from the Alarm Report above, logged in as admusr:

[admusr@dsr-SOAM-b ~]$ alarm.put -e 22960 -s 5 -i dsr-SOAM-b

Allow up to 5 minutes for the alarm to clear. If indeed the alarm was in error, it will not return.

Attachments

This solution has no attachment