Skip Headers
Oracle® Communications Services Gatekeeper Alarm Handling Guide
Release 5.0

Part Number E16614-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

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

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 Communication Service Reference, 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 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:

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 Plugin 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 Plugin manager

110600-110618, 110680 Short messaging: SMPP plugin

110901-110922 Presence SIP plugin

111000-111006 Budget service

111100-111104 Storage service

111202-111209 MLP plugin

111700-111718 MM7 plugin

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 plugin

120100- 120111 Call Notification plugin

121000-121067 Audio Call - Parlay plugin

130100- 130105 Subscriber Profile LDAP plugin

131001- 131009 Third Party Call - INAP plugin

132100- 1321005 EWS Push Message - PAP plugin

400200-400207 Native UCP Protocol Server Service

400300-400312 Native UCP SMS plugin

400400-400407 Terminal Status - MAP plugin

400500-400513 SMPP Service Service

400600400617 Native SMPP

401050-401053 Native MM7 plugin

199900 Default