Cisco Cisco Prime Central 1.5.2 Entwickleranleitung
3GPP OSS Integration
Error:
The following Errors will be reported.
Sl.No
Error Condition
Error Response
1
Unable to read the DMs
SOAP reponse indicating
“NO DMs available” will be
reported.
2
Managed Element does not exist
SOAP reponse indicating
“Managed Element does not
exist” will be returned.
NOTE:
1. The 3GPP Inventory XML conforms to the XML schema “InventoryNrm.xsd”.
2. The XML Shema “inventoryNrm.xsd” is the NRM-specific shema for the Inventory
Management NRM IRP IS alternateive 1 defined in 3GPP TS 32.692.
7.5.3.1 InventoryIRP:: getManagedElement Multi DM behaviour
This APIs behavior in a Multi DM environment is given below
Sl.No
Condition
Behavior
1
When
all associated
Domain Managers ( DMs )
are free to take the request
The request to collect inventory will be
initiated to all DMs and the response indicating
that the request is intiated will be sent with a
request ID.
2
When atleast one of the
associated DMs is
processing a previous
inventory request
The request will not be intiated. A reponse
indicating that another request is in progress
will be sent to the user.
7.5.4 InventoryIRP:: getStatus
This interface is used to get the status of the inventory operations i.e.,
getManagedElement & getAllInventory.
Description:
3GPP inventory operations like getManagedElement and getAllInventory operations
usually take longer time for inventory collection and to generate the output XML
containing physical and logical inventory. At any point in time, if the user want to know the
current status of the inventory operations, one can issue the getStatus with requestID as
the input.
Input:
Cisco Prime OSS Integration Guide for MTOSI and 3GPP
25