1 Handling Alarms

This document enumerates the types of alarms that may be generated in the course of running Oracle Communications Services Gatekeeper and gives the recommended steps for resolving them.

• Interpreting alarms

• Alarm numbering overview

  Note:

  There is a one-to-one correspondence between Oracle Communications Services Gatekeeper alarms and the defined SNMP traps. To view the MIB directly, point your MIB browser to the file BEA-WLNG-MIB available in the <wlng_domain>/snmp directory of your installation. Oracle Communications Services Gatekeeper does not provide a MIB browser, but most vendors of SNMP utilities do.

Interpreting alarms

An alarm list stored in the database contains information about alarms. Alarm information retrieved using listeners will have slightly different parameters.

Table 1-1 describes the parameters associated with alarms.

Table 1-1 Alarm Parameters

Information	Description
alarm_id	A unique sequential identifier
source	The name of the software module that raised the alarm and the IP address of the server in which the module runs
timestamp	The time at which the event was triggered (in milliseconds from midnight 1 January 1970)
severity	The alarm's severity level. Valid entries are: 1: warning 2: minor 3: major critical
identifier	The alarm type
alarm_info	Information provided by the software module that raised the alarm
additional_info	3.0 style alarms only. This field includes: Service Provider ID Application ID Application Instance Group ID (account login) Other information depending on context

For more information, see "Events, Alarms, and Charging" in Oracle Communications Services Gatekeeper Communication Service Guide, another document in this set.

Alarm numbering overview

Alarms are grouped into two large sets: those raised by 2.2 style mechanisms and those raised by 3.0 style mechanisms. For more information on the differences between them, see "Events, Alarms, and Charging" in the Oracle Communications Services Gatekeeper Communication Service Reference, a separate document in this set. Descriptions of each alarm and steps to take to resolve them can be found in the following two chapters:

• Resolving 2.2 Style Alarms

• Resolving 3.0 and Higher Style Alarms

2.2 Style (Legacy) Alarms

The numbers correspond to the new style sequential alarm_id. The old 2.2 style identifiers continue to exist in the alarm.xml file as attributes in key “AlarmIdentifier22” value “<old number>” pairs.

Protocol plug-in

102700-102704 plug-in OSA access

Policy

102800-102825 Policy

SLEE

103900-103902 - SLEE charging

104000-104001 - SLEE EDR (listeners)

104100 - SLEE statistics

3.0 Style (Current) Alarms

110000-110008 Corba

110100-110105 Java management (JMX)

110500-110504 Plug-inlug-in manager

110600-110618, 110680 Short messaging: SMPP plug-in

110901-110922 Presence SIP plug-in

111000-111006 Budget service

111100-111104 Storage service

111202-111209 MLP plug-in

111700-111718 MM7 plug-in

113300 Subscriber-centric policy interceptor

113400-113404 CDR to Diameter

113500-113504 Credit control interceptor

113601-11360 Geo-redundancy service

113701-113702 Geo-storage service

118100-118102 Heartbeater

119000-119017 Third Party Call - MPCC Parlay plug-in

120100- 120111 Call Notification plug-in

121000-121067 Audio Call - Parlay plug-in

130100- 130105 Subscriber Profile LDAP plug-in

131001- 131009 Third Party Call - INAP plug-in

132100- 1321005 EWS Push Message - PAP plug-in

400200-400207 Native UCP Protocol Server Service

400300-400312 Native UCP SMS plug-in

400400-400407 Terminal Status - MAP plug-in

400500-400513 SMPP Service Service

400600400617 Native SMPP

401050-401053 Native MM7 plug-in

98000001-98000009 QoS plug-in

981001-981011 Email service plug-in

199900 Default