Cisco Cisco Prime Central 1.5.2 Guia Do Programador
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
3GPP OSS Integration
identifies the
device/component instance in
the Prime Network.
3
notificationId
Long
Identifies the notification
which is a sequential number
that uniquely identifies the
alarm information
4
eventTime
XMLGregorianCalendar
The time when the Ticket is
raised. Shall be of best effort
basis.
5
systemDN
String
Indicates the instance of the
IRP Agent
6
notificationType
String
Type of the notification.The
value will be
"notifyUpdateAlarm"
7
additionalText
String
Description of the Ticket.
8
additionalInformation List
Additional information related
to the ticket
Contains the following fields:
Identifier,
AlarmCategory,
AlarmServerAddress,
AlertGroup,
AlarmManagedObjectAddress,
AlertId, OriginalTrapName,
Details, Troubleshooting
9
alarmId
String
The identifier which uniquely
identifies a Ticket in the Prime
Central Fault Management.
10
perceivedSeverity
ENUM
Indicates the Ticket’s severity
level.
Possible values: Critical,
Major, Minor, Warning,
Intermediate, Cleared
11
alarmType
ENUM
Indicates the type of the
Ticket.
Possible values:
“Communications Alarm",
"Processing Error Alarm",
"Environmental Alarm".
"Quality Of Service Alarm" or
"Equipment Alarm"
7.9.10 AlarmIRP :: notifyChangedAlarm
The subscribed OSS clients are notified about changes in the severity state of alarms. It is
only supported for non-security alarms.
Note: Supported only on Suite Mode and applicable for Prime Network alarms.
Cisco Prime OSS Integration Guide for MTOSI and 3GPP
52