Cisco Cisco Prime Network 4.0 開発者ガイド
3GPP OSS Integration
Cisco Prime Network OSS Integration Guide for MTOSI and 3GPP
16
OL-30201-01
Management Domain. The value
expected is “/MD=CISCO_PRIME”. The
Interface will return an
“IllegalArgument” Exception if this
parameter is not specified or any value
other than “/MD=CISCO_PRIME” is
specified.
Output:
The output will be in three parts:
1. A regular SOAP response to the Web Service request which will contain the invoke
identifier passed originally in the input and a response string indicating that the
Inventory request is initiated with a request ID.
2. One or more inventory XML files containing the physical and logical inventory data
for the supported devices in the domain. The request ID will be part of the
Inventory file name that is generated. The user can use the request ID to retrieve
the inventory files generated for a given request.
3. A Status file to indicate the status ( IN-PROGRESS, COMPLETED, FAILED ) for an
inventory request. The Status file has the request ID as part of its name.
Error:
Any error that happens during the inventory file generation process will be notified to the
caller via., a Inventory File Preparation Error. In addition to this the following SOAP
responses will be returned for the Error conditions described below.
Sl.No
Error Condition
Error Response
1
Unable to reach the EMS system
SOAP response indicating
“No DMs available” will be
returned.
2
No Managed Elements exist in the network
SOAP response indicating
“No Managed Elements exist
in the network “ will be
returned.
NOTE:
There will be one Inventory XML file per supported managed element. For a list of
7.5.1.1 InventoryIRP:: getAllInventory Multi DM behaviour
This section explains the API behavior in multi-DM environment. The following responses
will be returned to the user under the specified conditions
Sl.No
Condition
Behavior
1
When All associated
The request to collect inventory will be