Cisco Cisco Prime Network 4.0 開発者ガイド
3GPP OSS Integration
Cisco Prime Network OSS Integration Guide for MTOSI and 3GPP
OL-30201-01
15
Description:
This interface will be used to generate Inventory files according to 3GPP format. The
inventory data will contain both physical and logical inventory information. Physical
inventory will contain information about the hardware details and the logical inventory has
information about the following types of services running on the devices.
• PGateway
• SGateway
• SAEGW
• GGSN
• APN Profile
• ACS ( Active Charging Service )
• AAA
• GTPP
• Operator Policy
The Inventory data will be stored in XML files under preconfigured directories. Details
document. The inventory collection status will be indicated with a status file present under
the output directory. The status file will contain the information about the managed
elements, the device type, its status and the inventory file location.
If FTP/SFTP servers are configured, the inventory data file will be moved to the respective
macmhines depending on the availability of the primary and secondary FTP servers. If both
the FTP and SFTP servers are not reachable, the inventory data files will be written to the
local machine.
A copy of the status file will be available under the “INSTALL_DIR/sildata” directory on the
host where the Integration Layer is installed. The detail of the status file is explained in this
section.
Table 6-4: Input Parameters to Retreive Physical and Logical Inventory Information
Sl.No
Parameter
Data Type
Description
1
InvokeIdentifierIn
String
This is an optional parameter passed
by the OSS client user. The invoke
Identifier value passed as input to this
interface will be returned
(InvokeIdentifierOut) by the Web
Services Interface. The invoke
Identifier can be used by the OSS client
for correlation purpose. The value
passed to this is not validated and is
returned to the user as is.
2
queryXpathExp
String
An XPath query string containing the