Cisco Cisco Prime Network 4.2 開発者ガイド

Cisco Specific Interfaces

 

 

Cisco Prime OSS  Integration  Guide for  MTOSI and 3GPP 

 

 

119

 

extra meta data in processing the 
requests. For example, OSS application 
or FM can use this as a 
timestamp/version/state value that 
can be used to correlate actions to 
avoid issues with concurrent actions 
performed on a Prime Network Ticket. 

3 

Note 

String 

Optional note to include while 
performing the operation. 

4 

Username 

String 

Optional attribute. The user on behalf 
of whom the de-acknowledge 
operation is done. 

 
Output: 

1 

uniqueId 

String 

The same value which is used in the  
operation. 

2 

Hint 

String 

The same value which is used in the 
operation. 

3 

Success 

Boolean 

Value denoting the result of the 
operation - “true” in case of success. 

 

     Error: 

Sl.No 

Condition 

Error 

1 

Invalid ID provided for the 
operation in StandAlone 
Integration layer deployment. 

When user provides improper ticketId (not in 
expected format), the operation will return soap 
fault with the detail containing the 
alarmApiException. The alarmApiException code 
will be API_ERROR and message will contain the 
information: 
Please enter the PN Ticket Number or OID(format:  
[NewAlarm(Id=<Ticket Number>)] 

2 

Ticket does not exist on the 
PrimeNetwork. 

The operation will return soap fault with the detail 
containing the alarmApiException. 
The alarmApiException code will be API_ERROR 
and message will contain the information: 
DM[<comURI>]=>Message[API_ERROR:<Operation 
Name> operation failed. Reason: 
<DM_Error_Message>] 
 
where:  
<Operation Name>: the operation name, e.g. 
Acknowledge 
<comURI>: the comURI of the responding DM 
<DM_Error_Message>: the error message returned 
by DM.