Руководство Разработчика для Cisco Cisco Prime Network 4.1
3GPP OSS Integration
Cisco Prime Network OSS Integration Guide for MTOSI and 3GPP
32
32
OL-31029-01
Unacknowledged
Denotes the acknowledegment status.
Denotes the acknowledegment status.
8
alarmType
ENUM
Indicates the type of the Ticket
Possible values: “Communications Alarm",
"Processing Error Alarm", "Environmental
Alarm". "Quality Of Service Alarm" or
"Equipment Alarm"
Possible values: “Communications Alarm",
"Processing Error Alarm", "Environmental
Alarm". "Quality Of Service Alarm" or
"Equipment Alarm"
9
perceivedSeverity
ENUM
Indicates the Ticket’s severity level.
23. Possible values: Critical, Major, Minor,
Warning, Intermediate, Cleared
10
ackUserId
String
The ID of the user who has performed the
Acknowledge operation.
If the operation is perfomed by User1 on
behalf of User2, user will see - “User1” as
“User2”.
Acknowledge operation.
If the operation is perfomed by User1 on
behalf of User2, user will see - “User1” as
“User2”.
11
ackTime
XMLGregorianCalendar The time when the Ticket is acknowledged.
12
clearUserId
String
The ID of the user who has performed the
Clear operation.
If the operation is perfomed by User1 on
behalf of User2, user will see - “User1” as
“User2”.
Clear operation.
If the operation is perfomed by User1 on
behalf of User2, user will see - “User1” as
“User2”.
13
alarmClearedTime
XMLGregorianCalendar The time when the Ticket is cleared.
Note:
In case of a standalone deployment, the active Tickets from the Prime Network are
retrieved.
retrieved.
In case of standalone deployment, Prime Network doesn’t archive a cleared Ticket for
an hour. So cleared alarms till an hour, will be retrieved by the API.
an hour. So cleared alarms till an hour, will be retrieved by the API.
In case of a suite deployment, the active Tickets from the integrated Prime Networks
will be retrieved through the Fault Management Component.
will be retrieved through the Fault Management Component.
Error:
The following error scenarios will be handled and reported by the API:
Sl.No Condition
Error
1
Total number of Prime Network
Alarms in the Prime Fault
Management component exceeded
the limit specified in the
com.cisco.prime.esb.tgpp.interface.cfg
file.
Alarms in the Prime Fault
Management component exceeded
the limit specified in the
com.cisco.prime.esb.tgpp.interface.cfg
file.
SOAP Fault with message – “Number of alarms in
FM (<No. of PN Alarms in FM>) exceeded the
limit set for retrieval
(<bulkAlarmRetrievalMaxLimit value in cfg.
File>)”
FM (<No. of PN Alarms in FM>) exceeded the
limit set for retrieval
(<bulkAlarmRetrievalMaxLimit value in cfg.
File>)”
2
Prime Fault management component
is down.
is down.
SOAP Fault saying that “Could not send
Message.” will be returned.
Message.” will be returned.