Cisco Cisco Prime Network 4.2 Developer's Guide

3GPP OSS Integration

 

 

Cisco Prime OSS Integration Guide for MTOSI and 3GPP 
42

 

 

   

did not succeed for all/some of the remaining 
Tickets.  FM update failure after the operation 
succeeded on the DM is considered as partial 
success. 

6 

Alarm Id(In this case the Ticket ID in 
Prime Network) provided is empty. 

The badAlarmInformationReferenceList will 
contain the corresponding AlarmId along with 
the failureReason - “Id provided is invalid. Id 
cannot be null or empty.” 
 
The overall status of the operation will be 
"OperationFailed" if the operation did not 
succeed for all the remaining Tickets or 
otherwise “OperationPartiallySucceeded” if the 
operation succeeded for some of the Tickets. 

7 

 

The badAlarmInformationReferenceList will 
contain the corresponding AlarmId along with 
the failureReason – “AcknowledgmentFailed” 
and additionalFailureReason – “DM (<DM ID>) 
not found.” 
 
The overall status of the operation will be 
“OperationFailed” if the operation did not 
succeed for all the remaining Tickets or 
otherwise “OperationPartiallySucceeded” if the 
operation succeeded for some of the Tickets. 

8 

List don't have even a single Alarm Id 
(Empty list) 

SOAP Fault with message – “Invalid Request. At 
least one Alarm Id is required.” 

9 

User (commentUserId) is not present 

SOAP Fault with message – “Invalid User Id. User 
Id cannot be null or empty.” 

10 

Alarm Ids in the request exceeded the 
limit specified in the 
com.cisco.prime.esb.tgpp.interface.cfg 
file. 

SOAP Fault with message – “Number of alarms in 
request (<No. of Alarm Ids in request>) exceeded 
the maximum limit set (<bulkAlarmOpMaxLimit 
value in cfg. File>)” 

 

 

The API will be used to Force Clear one or more Tickets in the Prime Network. 

1 

alarmInformationReferenceList  List 

List of