Prime Network OSS Integration Guide-2-0

8/11/2019 Prime Network OSS Integration Guide-2-0

http://slidepdf.com/reader/full/prime-network-oss-integration-guide-2-0 1/148

Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387) Fax: 408 527-0883

Text Part Number: OL-30201-01

Cisco Prime Network OSS IntegrationGuide for MTOSI and 3GPPVersion 2.0

January, 2014



Abs tr act

The Cisco Prime Network OSS Integration Guide for MTOSI and 3GPP gives information on OSSIntegration using 3GPP and MTOSI north bound interfaces.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARESUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, ANDRECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTEDWITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITYFOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SETFORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND AREINCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARELICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OFTHESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMEDSUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUTLIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS ORLOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IFCISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. andother countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-partytrademarks mentioned are the property of their respective owners. The use of the word partner does notimply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actualaddresses and phone numbers. Any examples, command display output, network topology diagrams, andother figures included in the document are shown for illustrative purposes only. Any use of actual IPaddresses or phone numbers in illustrative content is unintentional and coincidental.

Prime OSS Integration Guide for MTOSI and 3GPP© 1999–2014 Cisco Systems, Inc. All rights reserved.



Contents

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPOL-30201-01 iii

1 Table of Contents

List Of Tables .......................................................................................................................... vi

2 Preface ............................................................................................................................ vii

3 Conventions ................................................................................................................... viii

4 Additional User Documentation .......................................................................................ix

5 Obtaining Documentation, Obtaining Support, and Security Guidelines .......................... x

6 Technologies .................................................................................................................. 11

7 3GPP OSS Integration ..................................................................................................... 12

7.1 Supported Devices for 3GPP Interface ............................................................................... 12

7.2 3GPPIntegration Reference Point (IRP) .............................................................................. 12

7.3 3GPP Integration Layer ...................................................................................................... 13

7.4 Overview of 3GPP Inventory Management ........................................................................ 13 7.4.1 Physical Inventory ................................................................................................................................ 13 7.4.2 Logical Inventory .................................................................................................................................. 14

7.5 3GPP Inventory IRP InterfaceDetails .................................................................................. 14 7.5.1 InventoryIRP:: getAllInventory ............................................................................................................. 14 7.5.2 InventoryIRP:: getAllManagedElementNames .................................................................................... 17 7.5.3 InventoryIRP:: getManagedElement .................................................................................................... 18

7.6 Overview of 3GPP File Transfer IRP .................................................................................... 20

7.7 3GPP File Transfer IRP Interface Details ............................................................................. 20 7.7.1 File Transfer IRP::listAvailableFiles ...................................................................................................... 21

7.8 Overview of 3GPP Notification IRP .................................................................................... 24

7.9 3GPP Notification IRP Details ............................................................................................. 25 7.9.1 Notification IRP::subscribe ................................................................................................................... 25 7.9.2 Notification IRP::unsubscribe .............................................................................................................. 28 7.9.3 3GPP FT Notification Consumer ........................................................................................................... 29

7.10 Overview of 3GPP Notifications ......................................................................................... 29 7.10.1 3GPP File Ready Notification........................................................................................................... 29 7.10.2 3GPP File Preparation Error Notification ........................................................................................ 29 7.10.3 3GPP FT Notification Multi-DM Behavior ....................................................................................... 30

7.11 Scheduling Web Services ................................................................................................... 31 7.12 3GPP Standard Compliance ............................................................................................... 31

7.13 Trouble Shooting – 3GPP ................................................................................................... 31

8 MTOSI OSS Integration .................................................................................................. 35

8.1 Supported Devices for MTOSI Interface ............................................................................. 35



Contents

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPiv OL-30201-01

8.2 MTOSI Inventory Management .......................................................................................... 35

8.3 MTOSI Interface Details ..................................................................................................... 36 8.3.1 Managed Element Retrieval Interface ................................................................................................. 36 8.3.2 Equipment Retrieval Interface ............................................................................................................. 36 8.3.3 Physical Termination Point Retrieval Interface .................................................................................... 36 8.3.4

Ethernet Virtual Connection (EVC) Resource Inventory APIs .............................................................. 39

8.3.5 DataCenter ........................................................................................................................................... 41 8.3.6 L3 MPLS VPN ........................................................................................................................................ 48 8.3.7 Floating termination point ................................................................................................................... 51 8.3.8 Inventory Notification .......................................................................................................................... 52

8.4 Delta Inventory Management ............................................................................................ 60 8.4.1 Managed Element Names Retrieval Interface details ........................................................................ 60

8.5 MTOSI Standard Compliance ............................................................................................. 62

8.6 Trouble Shooting - MTOSI .................................................................................................. 63

9 Cisco Specific Interfaces ................................................................................................. 64

9.1 Alarm Life Cycle Management ........................................................................................... 64 9.1.1 AlarmMgmt::Acknowlege .................................................................................................................... 64 9.1.2 AlarmMgmt::De-Acknowlege .............................................................................................................. 66 9.1.3 AlarmMgmt::Clear ............................................................................................................................... 67 9.1.4 AlarmMgmt::Retire .............................................................................................................................. 68 9.1.5 AlarmMgmt::Add Note ........................................................................................................................ 70

9.2 Alarm Retrieval ................................................................................................................. 71 9.2.1 AlarmRetrieval::getsubtendingEvents ................................................................................................. 71

9.3 Trouble Shooting – Cisco Specific Interfaces....................................................................... 73

10 Appendix I – References to WSDL Documents ................................................................ 75

10.1 3GPP WSDL Documents ..................................................................................................... 75 10.1.1 3GPP Inventory WSDL ................................................................................................... 75

10.1.2 3GPP FT IRP WSDL ......................................................................................................... 75

10.1.3 3GPP Notification IRP WSDL .......................................................................................... 75

10.1.4 3GPP Notification Consumer WSDL................................................................................ 76

10.2 MTOSI WSDL Documents ................................................................................................... 76

10.2.1 Managed Element Retrieval WSDL ................................................................................. 76

10.2.2 Managed Element Names Retrieval WSDL ..................................................................... 77

10.2.3 Equipment Inventory Retrieval WSDL ............................................................................ 77

10.2.4 Termination Point Retrieval WSDL ................................................................................. 77

10.2.5 Resource Inventory Retrieval WSDL ............................................................................... 77

10.2.6 Connection Retrieval WSDL ........................................................................................... 78

10.2.7 Ethernet Virtual Connection (EVC) Resource Retrieval WSDL ......................................... 78



Contents

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPOL-30201-01 v

10.3 Cisco Specific Extensions WSDL Documents ....................................................................... 78

10.3.1 Alarm Life Cycle Management WSDL ............................................................................. 78

10.3.2 Alarm Retrieval Management WSDL .............................................................................. 79

11 Appendix II – 3GPP-Miscellaneous ................................................................................. 79

11.1 3GPP InventoryNrm Schema File ....................................................................................... 79

11.2 3GPP Inventory File ........................................................................................................... 83 11.2.1 Inventory File Contents ................................................................................................................... 83

11.3 3GPP Detailed Inventory Information .............................................................................. 107 11.3.1 Physical Inventory attributes ........................................................................................................ 107 11.3.2 Logical Inventory attributes .......................................................................................................... 111

11.4 3GPP Status File ............................................................................................................... 139 11.4.1 Status File Name ........................................................................................................................... 139 11.4.2 Status File Contents ...................................................................................................................... 140

11.5 3GPP FT-IRP Inventory Notifications ................................................................................ 140 11.5.1 File Ready Notification .................................................................................................................. 140 11.5.2 File Preparation Error Notification ................................................................................................ 141

11.6 FTP Configuration ............................................................................................................ 142

11.7 Useful Code Snippets for 3GPP ........................................................................................ 143 11.7.1 Code Snippet for 3GPP Request Response ................................................................................... 143 11.7.2 Code Snippet for 3GPP Notification Consumer ............................................................................. 144

12 References ................................................................................................................... 147



List Of Tables

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPvi OL-30201-01

List Of Tables

Table 5-1 Technologies to Facilitate the OSS Integration ..................................................... ........ 11 Table 6-1: Supported Devices for 3GPP and MTOSI ..................................................................... 12

Table 6-2: Functional Area Supported by 3GPP .................................................. .......................... 13 Table 6-3: 3GPP Interfaces Names ................................................................................................ 14 Table 6-4: Input Parameters to Retreive Physical and Logical Inventory Information ................ 15 Table 6-5: input Paramters to Retreive List of Managed Elements .............................................. 17 Table 6-6: Input Parameters to Retreive Specific Managed Element ....... ................................... 19 Table 6-7: OSS Integration Problems and Troubleshooting Procedure ........................................ 32 Table 7-1: Supported Devices for 3GPP and MTOSI ..................................................................... 35 Table 7-2: Supported APIs for Managed Elements, Equipment Inventory ........ .......................... 37 Table 7-3: APIs for Retreiving EVC ................................................................................................ 40 Table 7-4: OSS Integration Problems and Troubleshooting Procedure ........................................ 63

Table 8-1: OSS Integration Problems and Troubleshooting Procedures for Cisco SpecificInterfaces ...................................................................................................................................... 73 Table 9-1: Physical Inventory Attributes for Managed Element ............................................... 107 Table 9-2: Physical Inventory Attribute for Chassis ..................................................... ............... 108 Table 9-3: Physical Inventory Attribute for Card .................................................................. ...... 108 Table 9-4: Physical Inventory Attribute for Slot .......................................................... ............... 109 Table 9-5: Physical Inventory Attribute for Port ................................................. ........................ 109 Table 9-6: Physical Inventory Attribute for Sub-port ................................................................. 110 Table 9-7: Physical Inventory Attribute for Power ............................................. ........................ 110 Table 9-8: Physical Inventory Attribute for Fan .................................................. ........................ 111 Table 9-9: Logical Attribute for PGW ........................................................ ................................. 112 Table 9-10: Logical Attribute for SGW ........................................................................................ 113 Table 9-11: Logical Attribute for APN ......................................................................................... 114 Table 9-12: Logical Attribute for SAEGW ................................................... ................................. 118 Table 9-13: Logical Attribute for GGSN ..................................................... ................................. 118 Table 9-14: Logical Attribute for ACS ............................................... ........................................... 121 Table 9-15: Attribute for AAA Group ............................................... ........................................... 129 Table 9-16: Attribute for AAADiameterEndpoint ....................................................................... 133 Table 9-17: Attribute for GTPP ................................................................................................... 135 Table 9-18: Attribute for OperatorPolicy ................................................... ................................. 138



Preface

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPOL-30201-01 vii

2 PrefaceThis documentation provides information about the 3GPP and MTOSI OSS Integration. Itdescribes the associated network management of its supported devices. This document isapplicable for Prime Central release 1.2 and Prime Network release 4.0.

Thisprefacecontainsthefollowingsections:

• Conventions • Additional User Documentation • Obtaining Documentation, Obtaining Support, and Security Guidelines

Conventions

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPviii OL-30201-01

3 ConventionsThis document usesthe following conventions:

Convention Indication

bold font Commands andkeywordsanduser-enteredtextappearinbold font.italic font Documenttitles,neworemphasizedterms,andargumentsforwhichyousupply

valuesarein italic font.

[] Elements insquare brackets areoptional.

{x|y|z} Requiredalternative keywordsaregroupedinbracesand separated byverticalbars.

[x|y|z] Optional alternativekeywordsaregrouped inbracketsandseparated byverticalbars.

String Anonquotedset ofcharacters.Donotuse quotationmarksaroundthestringor thestringwill includethequotationmarks.

courier font For code snippets and XML

<> Nonprintingcharacterssuch aspasswordsareinangle brackets.

[ ] Defaultresponsestosystempromptsareinsquarebrackets.

!,# An exclamationpoint(!) orapoundsign(#)atthe beginningofaline ofcodeindicatesacommentline.

Note Means reader take note. Notes contain helpful suggestions or references tomaterial not covered in the publication.



Additional User Documentation

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPOL-30201-01 ix

4 Additional User DocumentationWe sometimes update the documentation after original publication. Therefore, you shouldalso reviewthe documentation on Cisco.com for any updates.

Other related documents are:• ASR 5000 Product page • 3GPP Telecom Management • MTOSI at TMForum • Addendum: Prime Network OSS Integration – Sample SOAP Request Response on

Cisco Developer Network

http://www.cisco.com/en/US/products/ps11072/index.html


http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--S5.html


http://www.tmforum.org/


http://developer.cisco.com/web/prime-network/home








Obtaining Documentation, Obtaining Support, and Security Guidelines

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPx OL-30201-01

5 Obtaining Documentation, Obtaining Support, and SecurityGuidelinesFor information on obtaining documentation, submitting a service request, andgathering additional information, see the monthly What’s New in Cisco Product

Documentation, which also l ists all new and revised Cisco technical documentation, at:http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really SimpleSyndication (RSS) feed and set content to be delivered directly to your desktop using areader application. The RSS feeds are a free service and Cisco currently supports RSSversion 2.0.

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html





Technologies

Cisco Prime Network OSS Integration Guide for MTOSI and 3GPPOL-30201-01 11

6 Technologies

The NMS / EMS uses SOAP / WSDL to implement the Web Services. This requires the OSSclients to use SOAP understandable clients to communicate and access the interfaces

supported. The below table list thetechnologies used to facilitate the OSS integration.

Table 5-1 Technologies to Facilitate the OSS Integration

Technology ExplanationESB Enterprise Service Bus. The apache Service Mix environmentOSGi Open Software Gateway Interface, The Karaf environment.JMS Java Messaging Service, Queues and topics for communicating

across integration layer and prime networks.SOAP Simple Object Access Protocol, Used for communicating with

the Web Service end pointWeb Service Technology that exposes a SOAP / WSDL for accessing the 3GPPinterfaces.



3GPP OSS Integration


• 3GPP Integration Layer• Overview of 3GPP Inventory Management• 3GPP Inventory IRP InterfaceDetails• Overview of 3GPP File Transfer IRP• 3GPP File Transfer IRP Interface Details

7.3 3GPP Integration Layer

The Integration layer is a component that can be installed on the Prime Network box as aseparate entity. The Integration Layer communicates with the Prime Network system usinga proprietary communication mechanism. The Integration layer exposes the 3GPPInterface via a Web Services Interface. The Web Service request processed with the databeing collected from the Prime Network system .

7.4 Overview of 3GPP Inventory Management

Inventory Management SOAP interface is a vendor extension Web Service used to retrieve

the physical and logical inventory data for ASR 5000 and ASR5500 devices manufactured byCisco. The Inventory management Web Service provides three interfaces to retrievephysical and logical inventory data from the devices.The Interfaces are described in detailin this document under 3GPP OSS Integration.

The below table gives a list of functional areas supported along with the management datatype.

Table 6-2: Functional Area Supported by 3GPP

Functional Area Management

Data Type

Description

InventoryManagement

IM This functional area covers the inventorymanagement needs of the OSS. The IRP Agentsimplement interfaces that enables the IRPManagers ( OSS clients ) to collect inventory datafrom IRP Agents ( EMS / NMS )

7.4.1 Physical Inventory

Inventory Management includes information on following physical inventory data.• Managed element• Chassis• Card• Slot• Port• Sub-port




Cisco Prime Network OSS Integration Guide for MTOSI and 3GPP14 OL-30201-01

• Power unit• Fan

The attributes of the physical inventory units can be found in Appendix section.

7.4.2 Logical Inventory

Inventory Management also captures information on following logical entities:• PGW• SGW• SAEGW• APN• GGSN• ACS ( Active Charging Service )• AAA• GTPP• Operator Policy

Logical entities have both 3GPP prescribed data and Cisco specific vendor extensions. Theattributes details are available in Appendix section.

7.5 3GPP Inventory IRP InterfaceDetails

This section gives a description of all the interfaces with their input, output and thedescription in detail. An OSS user can go through this section to better understand theinterface and to use it according to their business needs.

The WSDL document describing the details of the Interface can be accessed from the

Appendix section.Table 6-3: 3GPP Interfaces Names

Sl.No Interface Name Description1 getAllInventory This API is used to retrieve Inventory data for all

supported devices under the managementdomain

2 getAllManagedElementNames This API is used to retrieve the managed elementname and types for all managed elementspresent in the management domain.

3 getManagedElement This API is used to retrieve the inventory data fora specific Managed Element.

7.5.1 InventoryIRP:: getAllInventory

This interface is invoked by the OSS client to retrieve the Physical and Logical Inventoryinformation for the managed elements present under the management domain.The below table gives the list of parameters that should be used as input to retrievephysical and logical inventory information.





Description:This interface will be used to generate Inventory files according to 3GPP format. Theinventory data will contain both physical and logical inventory information. Physicalinventory 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. Detailsabout this configuration will be captured under the FTP Configuration Section in thisdocument. The inventory collection status will be indicated with a status file present underthe output directory. The status file will contain the information about the managedelements, 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 respectivemacmhines depending on the availability of the primary and secondary FTP servers. If boththe FTP and SFTP servers are not reachable, the inventory data files will be written to thelocal machine.A copy of the status file will be available under the “INSTALL_DIR/sildata” directory on thehost where the Integration Layer is installed. The detail of the status file is explained in thisdocument under the Appendix section.

Table 6-4: Input Parameters to Retreive Physical and Logical Inventory Information

Sl.No Parameter Data Type Description1 InvokeIdentifierIn String This is an optional parameter passed

by the OSS client user. The invokeIdentifier value passed as input to this

interface will be returned(InvokeIdentifierOut) by the WebServices Interface. The invokeIdentifier can be used by the OSS clientfor correlation purpose. The valuepassed to this is not validated and isreturned to the user as is.

2 queryXpathExp String An XPath query string containing the





Management Domain. The valueexpected is “/MD=CISCO_PRIME”. TheInterface will return an“IllegalArgument” Exception if thisparameter is not specified or any valueother than “/MD=CISCO_PRIME” isspecified.

Output:The output will be in three parts:

1. A regular SOAP response to the Web Service request which will contain the invokeidentifier passed originally in the input and a response string indicating that theInventory request is initiated with a request ID.

2. One or more inventory XML files containing the physical and logical inventory datafor the supported devices in the domain. The request ID will be part of theInventory 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 thecaller via., a Inventory File Preparation Error. In addition to this the following SOAPresponses will be returned for the Error conditions described below.

Sl.No Error Condition Error Response1 Unable to reach the EMS system SOAP response indicating

“No DMs available” will bereturned.2 No Managed Elements exist in the network SOAP response indicating

“No Managed Elements existin the network “ will bereturned.

NOTE:There will be one Inventory XML file per supported managed element. For a list ofsupported network equipments, please refer to the section Supported Devices for 3GPPInterface .

7.5.1.1 InventoryIRP:: getAllInventory Multi DM behaviourThis section explains the API behavior in multi-DM environment. The following responseswill be returned to the user under the specified conditions

Sl.No Condition Behavior1 When All associated The request to collect inventory will be





Domain Managers ( DMs )are free to take the request

initiated to all DMs and the response indicatingthat the request is intiated will be sent with arequest ID.

2 When atleast one of theassociated DMs is

processing a previousinventory request

The request will not be intiated. A reponseindicating that another request is in progress

will be sent to the user.

7.5.2 InventoryIRP:: getAllManagedElementNames

This interface is used to get a list of managed element names supported under the“CISCO_PRIME” management domain 1. The interface returns a list of managed elementnames and their device family / device type.

Description:

This interface will be used to retrieve a list of managed elements for the givenmanagement domain. The response will contain the managed element name and thedevice family.The response of this interface can at a later point be used by the OSS client to selectivelyissue request to collect inventory for specific nodes using the “getManagedElement”interface.

The below table gives the list of parameters that should be used as input to retrievephysical and logical inventory information.

Input:

Table 6-5: input Paramters to Retreive List of Managed Elements

Sl.No Parameter Data Type Description1 InvokeIdentifierIn String This is an optional parameter passed

by the OSS client user. The invokeIdentifier value passed as input to thisinterface will be returned(InvokeIdentifierOut) by the WebServices Interface. The invokeIdentifier can be used by the OSS clientfor correlation purpose. The valuepassed to this is not validated and isreturned to the user as is.

1In Prime Network 4.0, this interface will only return the name of devices that are managed by Prime Network .

If file transfer is enabled and both the primary and secondary destinations are notaccessible, the XML file will be generated on the local machine under preconfigured folder.

Input:The below table gives the list of parameters that should be used as input to retrieve

physical and logical inventory information.

Table 6-6: Input Parameters to Retreive Specific Managed Element

Sl.No Parameter Data Type Description1 InvokeIdentifier String This is an optional parameter passed by the

OSS client user. The invoke Identifier valuepassed as input to this interface will bereturned (InvokeIdentifierOut) by the WebServices Interface. The invoke Identifier canbe used by the OSS client for correlationpurpose. The value passed to this is notvalidated and is returned to the user as is.

2 queryXpathExp String An XPath query string containing theManagement Domain. The value expectedis “/MD=CISCO_PRIME/ME=<ME Name>2”.The Interface will return an Exception if:The management domain is NOTCISCO_PRIME.The managed element is NOT specified ORmanaged.

Output:The output will be in three parts:

1. A regular SOAP response to the Web Service request which will contain the invokeidentifier passed originally in the input and a response string indicating that theInventory request is initiated with a request ID.

2. Inventory XML file containing the physical and logical inventory data for thespecified managed element. The request ID will be part of the Inventory file namethat is generated. The user can use the request ID to retrieve the inventory filegenerated for a given request.

3. A Status file to indicate the status (IN-PROGRESS, COMPLETED, FAILED) for aninventory request. The Status file has the request ID as part of its name.

Error:

The following Errors will be reported.

2The Managed Element name should be identical with that of Prime Network Administration GUI





Sl.No Error Condition Error Response1 Unable to read the DMs SOAP reponse indicating

“NO DMs available” will bereported.

2 Managed Element does not exist SOAP reponse indicating

“Managed Element does notexist” will be returned.

7.5.3.1 InventoryIRP:: getManagedElement Multi DM behaviourThis APIs behavior in a Multi DM environment is given below

Sl.No Condition Behavior1 When All associated

Domain Managers ( DMs )are free to take the request

The request to collect inventory will beinitiated to all DMs and the response indicatingthat the request is intiated will be sent with arequest ID.

2 When atleast one of theassociated DMs isprocessing a previousinventory request

The request will not be intiated. A reponseindicating that another request is in progresswill be sent to the user.

7.6 Overview of 3GPP File Transfer IRP

The 3GPP interface for File Transfer IRP provides APIs to retrieve file information. The APIallows user to list files that gets generated as an output of Inventory IRPs “getAllInventory” and“getManagedElement” WS request. The File Transfer IRP also adds support for generating aFileReady and File Preparation Error Notification. The details of which will be discussed in theNotification section of this document.

The FT IRP support the following file transfer protocols,

• SFTP• FTP

7.7 3GPP File Transfer IRP Interface Details

This section describes the 3GPP File Transfer IRP Interface in details. The operations supportedin File Transfer IRP, input, out put and functionality will be explained.

The WSDL document describing the details of the Interface can be accessed from theAppendix section.

NOTE:• Output will list a unique set of files from both primary and seconday• OSS user has to provide the input date time for beginTime and endTime w.r.t management

domain timezone.

Output:

This API will list the set of available files from the configured local, primary and secondary FTPservers

Output paraments

Sl.No Parameter Data Type Description1 fileInfoList fileInfo This specifies the list of files

information retrieved between the

provided beginTime and endTime bythe OSS user.

2 Status String This parameter specifies the status ofthe operation.Possible values areOperationSucceeded andOperationFailed.

Output paraments – FileInfo object

Sl.No Parameter Data Type Description1 managementDataType String It specifies the type of the

management data stored in the filewhich is provided by the OSS user inrequest.Different management data types arePM, CM, IM, TE, CT, NL, CG, OT,BASE.Currently we are supporting only IM –Inventory Management.

2 fileLocation String This specifies the complete path of theIM file located on the disk along with

filename.Format : IP:/<full path>_<filename>3 fileSize Long It identifies the size of the file in bytes.4 fileReadyTime DateTime It identifies the date and time when

the file was created.5 fileExpirationTime DateTime It identifies the date and time beyond

which the file may be deleted.6 fileCompression String It identifies the name of the

compression algorithm used for thefile.Currently this will be empty as we arenot supporting this.

7 fileFormat String It identifies the encodeing techniqueused by the file.Currently we support XML-schema.

Error:

The following error scenarios will be handled and reported by the API:

Sl.No Condition Error1. No files are available If no files present in the specified duration,

FileInfoList in soap response will be emptywith status “OperationSucceeded”.

2 Empty begin time or endTime The response should contain an error messagesaying “Please enter beginTime in standardUTC format YYYY-MM-DDThh:mm:ss”

3 Invalid Management Datatype The response will have an error message“Invalid management data type”.

4 Invalid endTime (EndTime >BeginTime)

The response should contain an errror"Endtime greater than beginTime".

5 No beginTime & endTime The response will list all the files present thedirectory

6 No endTime input The response should list all the available filesin the directory whose time of creation liesbetween user provided beginTime and currentsystem time (as endTime is not mentioned byuser).

7 No input beginTime The response will list all the available fileswhich are created before the specifiedendTime.

8 Non UTC format of begin orendTime

The response will contain an error “Pleaseprovide the begin time in standard UTC format: YYYY-MM-DDThh:mm:ss.”.

9 Large volume of files, potentialtimeout candidate

The response willl list all the available files forthe duration provided from the primary and

secondary directory. In case of huge data, anerror will be shown like “Could not list thecontents of folder, <path>”

10 Timeout due to FTP server un-reachable.

The response willl list all the available files forthe duration provided from the primary andsecondary directory. In case of connectiontimeout from both the servers, an error will beshown like “Both Primary and Secondary are

Not reachable”11 Replication enabled between FTP

servers but directory paths areincorrect.

The response will list all the available files forthe duration provided from the primary andsecondary directory. In case directory pathsare not properly mentioned, error will beshown like “Could not list the contents of<path>.”

7.7.1.1 ListAvailableFiles Multi DM Environment:

Description :

ListAvailable files operation in multi DM environment will be aggregated output of result fromeach DM.

Input :

ListAvailable files operation input for multi DM environment is same as input in standaloneenvironment.

Output:

ListAvailable files operation output in multi DM environment will be aggregated output fromeach DM.

Sl.No Condition Error1 Exception occurred in DM1 orDM2

If any exception happens in DM1 but the sameoperation is successful in DM2, the the finalresult will be from DM2

Error :

The error conditions in standalone are applicable for multi DM environment as well.

7.8 Overview of 3GPP Notification IRP

The Notification IRP support provides support for subscribing and unsubscribing to 3GPPnotifications. The current release supports File Transfer Notifications ONLY. Once theInventory file generation completes successfully a File Ready Notification will be sent. Ifthe inventory collection or file generation encounters an issue a File Preparation ErrorNotification will be sent.





7.9 3GPP Notification IRP Details

This interface supports APIs that will allow an OSS user to subscribe and unsubscribe forvarious notification categories.


7.9.1 Notification IRP::subscribe

This interface is used to subscribe to 3GPP notifications. This request will enable an OSSuser to receive any 3GPP notifications that is supported by the IRP agent. Currently wesupport the following categories

• File Transfer IRP Notifications ( 32347-900 )

Description:The subscribe call can be issued by an OSS user to register for 3GPP notifications andenables the OSS user to receive the registered 3GPP notification. If the optionalparameters are not given, the API registers the OSS user for all supported notificationcategories ( current release supports the File Ready and File Preparation ErrorNotifications ). The Notification consumer should be active when notifications are sent.Notifications will NOT be stored for future forwards.

Input:

The following table lists the input arguments for the request

Sl.No Parameter Data Type Description1 managerReference URL A valid URL where the

OSS client / IRPmanager will belistening to.The URL validation willnot be done during theregistration process.This is a mandatoryfield.

2 timeTicks Long A long value indicatingthe time when thissubscription requestshould expire.This is an optionalvalue and is NOTsupported in this





release ( PN 4.0 ).Giving a non-numericvalue will throw aSOAP / Web Serviceexception.

3 notificationCategories ntfIRPData:NotificationCategorySetType This is a set of stringsthat can be specifiedfor which thesubscription will bedone.This is an optionalparameter. In thisrelease ( PN 4.0 ), wesupport the value“32347-900”indicating the FT IRPversion 9.0.0.Being an optionalparameter the user isnot expected to givethis as an input whichwill automaticallysubscribe the OSS userto receive thecurrently supported (FT Notifications ) only.

4 Filter String This is an optional fieldand is NOT supported

int this release ( PN4.0 ). Any valuespecified in this fieldwill be ignored.If supported the usercan use this field tohave a customerfiltering for specifiedNotificationcategories.

5 ntfTrsnsServiceNS anyURI This parameter is usedto specif thenamespace of theWeb NotificationTransmission Servicethat will be used forsending notification.This is a mandatoryfield, but in the





current release ( PN4.0 ), this field will notbe used.

NOTE: The managerReference and ntfTrsnsServiceNS are the only mandatory paramters.

Output :

The API gives the subscription ID as an output. This subscription ID will be used tounsubscribe for notifications.

Sl.No Parameter Data Type Description1 subscriptionID String The subscription ID

will be returned upona successful subscriberequest. The

subscription ID alongwith the managerReference can be usedto un-subscribe fornotifications.

Error :

The following error conditions will be reported by the API

Sl.No Condition Error1. Invalid Category Exception indicating an

invalid manager Referenceor category

2 Already registered category Exception indicating thatany of the categoriespassed as input is alreadyregistered for this managerReference.

3 One or more categories arenot supported

An exception will bereturned If any of the

category entries passed

7.9.1.1 Multi-DM BehaviourN/A





7.9.2 Notification IRP::unsubscribe

Description:This API is used to unsubscribe to any 3GPP notification. The manager Reference that ispassed as input will be used to un-subscribe the OSS / requesting user. ThemanagerReference is a mandatory parameter.The operation will un-subscribe the Notification consumer from all subscribed categoriesassociated with the manager reference.

Input

Sl.No Parameter Data Type Description1 managerReference URL A valid URL where the

OSS client / IRPmanager will belistening to.

This is a mandatoryfield. This value will beused to remove the

2 subscriptionID String This is an optionalparameter.

Output:

Upon successful completion of un-subscribe operation the manager reference will bereturned.

Sl.No Parameter Data Type Description1 managerReference String The manager

reference that was un-subscribed.

Error:

The following error will be thrown under the specified conditions:

Condition ErrorInvalid Manager Reference Exception indicating an invalid manager Reference

or category





7.9.2.1 Multi-DM environment behaviorN/A

7.9.3 3GPP FT Notification Consumer

The 3GPP Notification consumer endpoint will be exposed as a Web Service endpoint. Thisendpoint can be used by the OSS users who wish to receive notifications to download theNotification Consumer Interface WSDL.This Endpoint will not support any operation and is deployed for getting the 3GPP FT IRPNotificaiton Consumer WSDL.The WSDL document can be accessed from the Appendix section.

7.10 Overview of 3GPP Notifications

The current version of Notification IRP will allow a subscribed user to receive the

following notifications:

• 3GPP File Ready Notification• 3GPP File Preparation Error Notification

7.10.1 3GPP File Ready Notification

A File Ready Notification will be generated for “getAllInventory” and“getManagedElement” API calls on the Inventory IRP. Only one File Ready Notification willbe sent upon a successful completion of the inventory file creation.

7.10.1.1 3GPP File Ready Notification SOAP Format

The SOAP format for the File Ready Notification is shown below. One File ReadyNotification will be generated per request if atleast one file was generated. Thenotification contains information about all the successfully generated files.A notification sample is shown in the Appendix section.

7.10.2 3GPP File Preparation Error Notification

A File Preparation Error Notification will be generated for “getAllInventory” and

“getManagedElement” API calls on the Inventory IRP. Only one FilePreparationNotification will be sent if an error is encountered when inventory collectionor file generation.

7.10.2.1 3GPP File Preparation Error Notification SOAP Format





This SOAP message for 3GPP File Preparation Error Notification is shown below. The SOAPmessage will not contain any information about the files. This notification will begenerated if the file creation process encounters any error.A notification sample is shown in the Appendix section.

7.10.3 3GPP FT Notification Multi-DM BehaviorMulti-DM environment when all participating DMs generate inventory files for all supporteddevices without encountering failure.

1. Notification Consumer ( eg: OSS Client ) subscribes to notifications.2. Issues request to “getAllInventory” to Web Serice on PC host3. All participating DMs are free to handle request.4. Request initiated on all participating DMs5. File Generation is successful on each of the DMs6. Each DM sends a “FileReadyNotification”7. Notification consumer receives one “FileReadyNotification” per DM instance.

Multi-DM environment when no files are generated and DM encounters failure whengenerating inventory files for all managed devices

1. Notification Consumer ( eg: OSS Client ) subscribes to notifications.2. Issues request to “getAllInventory” to Web Serice on PC host3. All participating DMs are free to handle request.4. Request initiated on all participating DMs5. File Generation is un-successful on each of the DMs6. Each DM sends a “FilePreparationErrorNotification”7. Notification consumer receives one “FilePreparationErrorNotification” per DM instance.

Multi-DM environment with partial success and partial failure use case, when some files getsgenerated for a set of managed devices and fails for a sub-set of the devices.

1. Notification Consumer ( eg: OSS Client ) subscribes to notifications.2. Issues request to “getAllInventory” to Web Serice on PC host3. All participating DMs are free to handle request.

4.

Request initiated on all participating DMs5. File Generation is successful for a sub-set of DMs and un-successful for a sub-set oneach / some of the DMs

6. Each DM sends a “FileReadyNotification” containing those files which were successfullycreated AND a “FilePreparationErrorNotification” for those devices where the DM failsto generate any file.





7. Notification consumer receives one “FileReadyNotification” for a set of successful filecreation and ONE “FilePreparationErrorNotification” for all the failed file creation perDM instance.

7.11 Scheduling Web Services

Prime Network Integration Layer uses Prime Network Scheduling framework to schedulethe following 3GPP Web Services.

• getAllInventory• getManagedElement

For Scheduling Web Services, User has to use the options available in the Prime NetworkComponent.

For more details on the Prime Network Web Scheduler , see Cisco Prime Network 4.0 UserGuide .

7.12 3GPP Standard Compliance

This version of 3GPP inventory management is based on 3GPP Release 10 specification (TS32.690 V10.0.0). The interfaces to retrieve inventory information from the IRP Agentfollow the “inventoryNRM.xsd” schema described in TS 32.696 V10.3.0.

The 3GPP standard does not define a SOAP solution set for Inventory Management. This isa Cisco extension for the SOAP solution. The XML output conforms to the 3GPP standardbased inventoryNRM schema. The inventory file contains both the physical and logicalinventory information.

The Logical inventory data contains both standard based and vendor (Cisco) extensiondata. The Vendor extension data will be present under the vendor specific data container(VsDataContainer) section inside the logical inventory section in the XML data file. Formore details on these 3GPP vendor extensions, see Appendix section.

Refer to the 3GPP and MTOSI standards in the link http://www.3gpp.org/specifications.

7.13 Trouble Shooting – 3GPP

The below table includes the issues that might be encountered while setting up OSSintegration layer and steps to troubleshoot the problem.

http://www.cisco.com/en/US/products/ps11879/products_user_guide_list.html



http://www.3gpp.org/specifications









Table 6-7: OSS Integration Problems and Troubleshooting Procedure

ProblemDescription

Indication Probable Cause Troubleshooting Procedure

Web ServicesSecurityException

Web Service call toany of the Interfaceswill throw a WSSecurity exceptionwith authenticationfailure message

The user ID / passwordprovided for the webservice call might notbe correct.

Use a proper User ID / password forthe web services call.

No DMsAvailableException

Exception messagefrom the Web Servicecall, stating that noDMs are available.

The communication toPN is not proper. TheIntegration layer wasnot able tocommunicate with thedomain manager ( DM

).

• Verify that the PrimeNetworks application isrunning.

• Network Connectivity to thePrime Networks machine isproper.

Exceptionindicating NoManagedElement inNetwork

A call togetAllInventoryreturns a WebServices exceptionstating that there areno ManagedElements in thenetwork.

The PN system is notconfigured to have anymanaged elements

• Verify if the PN systemcontains any managedelements.

• Add network elements thatcan be managed by PN.

• Issue the Web Service request.• Verify if the Exception

message disappears and WebService response indicating

start of inventory collectionappears.• Verify if Inventory files are

getting created

Inventory filesare not copiedto FTP servers

Inventory files arenot present on theFTP server (primaryand secondary)configured.

The FTP serverconfiguration is notproper.

• Verify the FTP serverhostname is reachable.

• FTP / SFTP service is runningon the configured hosts.

• Login and password isproperly specified during the

FTP configuration setup.

Note: The password will be encryptedin the configuration file.

getManagedElement returns aSOAP Exception

A call togetManagedElementreturns a WebServices exception

The device namespecified in request isincorrect

Cross check the device name ingetAllManagedElementNamesresponse and verify if the device isnot in up state





stating that thedevice is not in up-state though it isactually up.

getManagedEle,ent returns anME not in upstate message

Call togetManagedElementreturns withexception indicatingthe ME is not in up-state

The Managed Elementis either not managedby the EMS or is not avalid name.

This is a valid condition. The managedelement is expected to be managed bythe EMS.

Call to anyWebServiceoperationreturns atimeoutexception.

JMS did not getresponse in specifiedtime 3000milliseconds ( timeout )

There might be anexception in theprocessing on theserver.

Please check the log file under theINSTALL_DIR/data/log, in theservicemix.log file for any exceptions.

Call to anyWebServiceoperationreturns anauthenticationfailure error

Exception is receivedby the SOAP client.Exception: java.lang.Exception: java.lang.IllegalStateException: Errorcommunicating withANA host10.105.39.39

The credential givendoes not match withthe PN credential.

Please make sure that the credentialsgiven to the Web Service all isconsistent with the PN credentials.

FTIRP

Webservicedoes not list anyfiles for a call tolistAvailableFiles

Message indicating :

No files to display isgiven as a SOAPresponse

No files exists on the

system to be displayed

Log on to the PN host, primary and

secondary FTP server. Match the filesbased on the start time and end timesupplied for the API.

FTIRPWebservice getsfiles present onthe local filesystem.

FTP is configured onPN host. The File listinfo lists the filesindicating the host IPwhere the WebService is deployedinstead of the FTP

servers name.

Probable cause:• (s)FTP servers

are down.• (s)FTP

credentials arenot correct.

• (s)FTP access is

not allowed tothe FTPservers.

• Check the FTP access• Check the FTP permissions• Check the FTP credentials.

FTIRPWebService getsfiles presentunder theprimary FTP

Files listed are onlyfrom the primary FTPserver.

Replication is notconfigured.

• The replication of FTP serversis not configured.





server only.Web ServiceScheduler:getAllInventoryandgetManagedElement Webservices arescheduled butthe jobs are notexecuted.

The inventory filesare not gettinggenerated after thescheduled timeelapses.

The scheduler might bedown on the Primenetwork DM.

• Log on to the PN system onwhich the scheduling is done.

• Verify in the scheduler logs tocheck if the job is scheduled.

• Verify if the Web Service isaccessible.



MTOSI OSS Integration


8 MTOSI OSS IntegrationCisco implementation of MTOSI APIs provide North Bound Interface support for theretrieval of physical inventory, Carrier Ethernet connection resources and notifications ofrespecitive resource changes.

• Managed Elements and Equipment Inventory• Ethernet Virtual Connection Resource Inventory• Inventory Object Create/Delete/Update and Attribute Value Change Notifications

Cisco MTOSI Information Model is designed to conform to MTOSI 2.0 information modeland operational API's. Cisco reference implementation extensions are introduced tosupport proprietary APIs and name space as per Cisco PrimeSuite release.

For a sample SOAP Request and Response for all the APIs defined in these interfaces, referto the Prime Network OSS Integration Guide SOAP Request Response document on CiscoDeveloper Network .

8.1 Supported Devices for MTOSI Interface

The below table list of supported devices for 3GPP and MTOSI.

Table 7-1: Supported Devices for 3GPP and MTOSI

Supported DM Versions Supported Devices

MTOSI PN 4.0, PC 12 Device support is based on PN4.0Mention Cable device support

8.2 MTOSI Inventory Management

Cisco Prime Network support the following features.

• Managed Elements and Equipment Inventory• Inventory Object Create/Delete/Update and Attribute Value Change Notifications• Ethernet Virtual Connection Resource Inventory

Cisco MTOSI Information Model is designed to conform to MTOSI 2.0 information modeland operational API's. Cisco reference implementation extensions are introduced tosupport proprietary APIs and name space as per Cisco PRIME Release requirements.











_Inventory.xsd

getContainedEquipment(...) getAllEquipmentResponse - a list of all of theequipment andequipment holderscontained in theequipment holders

getAllEquipmentRequest- name of theequipmentholder toretrieve thenext levelcontainedequipment andequipmentholders

Returns the next level containedEquipment Holderand Equipment list. See thecorresponding wsdl/xsd files formore details.ManageResourceInventory/IIS/wsdl/EquipmentInventoryRetrieval/EquipmentInventoryRetrievalHttp.wsdl ManageResourceInventory/IIS/xsd/EquipmentInventoryRetrievalMessages.xsd Equipment Attribute Extension asper requirement are defined in –NetworkResourceFulfillment/IIS/

xsd/Cisco_ME_EQ_Inventory.xsdgetAllSupportedPhysicalTerminationPoints( ... )

getAllSupportedPhysicalTerminationPointsResponse - a list of physicaltermination endpoints(PTP) of the specifiedequipment

getAllSupportedPhysicalTerminationPointsRequest - a list ofRDNs thatspecify thecontainingequipment:MD/ME/EH[/EH/EH]/EQ

Returns a list PTPs. See thecorresponding wsdl/xsd files formore details.

• ManageResourceInventory/IIS/wsdl/TerminationPointRetrieval/TerminationPointRetrievalMessages.wsdl

• ManageResourceInventory/IIS/xsd/TerminationPointRetrievalMessages.xsd

PTP Attribute Extensions perrequirements are defined in –

• NetworkResourceFulfillment/IIS/xsd/Cisco_ME_EQ _Inventory.xsd

subscribe(...) subscribeResponse- an unique

subscription identifieris returned to theClient OS to be usedwhen invoking theunsubscribe() for thegiven topic. Note thatit must uniquelyidentify the requestsignature by its three

subscribeRequest - Thisoperationallows theClient tosubscribe fornotifications

The subscribe operation used toreceive subscriptions fromconsumers . See thecorresponding wsdl/xsd files formore details.

• Framework/IIS/wsdl/NotificationProducer/NotificationProducerHttp.wsdl

• Framework/IIS/xsd/NotificationMessages.xsd





elements:consumerEPR, topic,and selector.

unsubscribe(...) unsubscribeResponse- response message

structure of theunsubscribe operation.Note that it is an emptypayload. Failure shouldbe handled as anexception.

unsubscribeRequest- This

operationallows theClient tounsubscribefrom a previoussubscribednotificationchannel.

The unsubscribe operation usedto receive subscriptioncancellations from consumers.See the corresponding wsdl/xsdfiles for more details.

• Framework/IIS/wsdl/NotificationProducer/NotificationProducerHttp.wsdl

• Framework/IIS/xsd/NotificationMessages.xsd

notify(...) not applicable not applicable One way (notification) messagestructure of the notify operation.This operation allows eventnotification to a client OS for thefollowing event types:

• AttributeValueChangeType

• ObjectCreationType • ObjectDeletionType

For more details, seeFramework/IIS/wsdl/NotificationProducer/NotificationProducerHttp.wsdl file.

8.3.4 Ethernet Virtual Connection (EVC) Resource Inventory APIs

EVC resource retrieval is supported by these APIs:• getFlowDomainFragment• getFlowDomainFragmentRoute• getAllFlowDomainFragmentNames


More details of the interfaces and data type are described in these files below .• ManagedResourceInventory/FlowDomainFragmentRetrieval wsdl file• ManagedResourceInventory/FlowDomainFragmentRetrieval xsd file

The below table lists the APIs for the retrieval of Ethernet Virtual Connections (EVC).

Sl.No Response parameter Type Description1 dcNm String Data Center name in the following

format:<VCenter Name>:-:<Data Centername>

2 name NamingAttributeType RDN of Data Center3 DM Specific Info Alias3.1 aliasName String PN Instance Identifier3.2 aliasValue String Identifier inside PN for the specific

DataCenter instance4 VendorExtension

VCenter Information4.1 name String “Cisco_vCenter”4.2 value String VCenter Name

8.3.5.1.2 List of all available Host name from a particular Data center.

Input to getInventory API:

Sl.No Request parameter Type Description1 MD String Management Domain name.

2 Cisco_DC String The value for this should contain theDataCenter name as reported inresponse section of 4.1.5.1.1

3 ObjectType String The value expected is “Cisco_V_Host”

4 Granularity String The value expected is “NAME”

Output:The output will contain list of host names. The parameters in response is explained below.

Response parameter Type DescriptionhostNm String Host server name.

8.3.5.1.3 Details of a particular host


Sl.No Request parameter Type Description1 MD String Management Domain name

2 Cisco_DC String The value for this should contain theDataCenter name as reported in





response section of 4.1.5.1.13 Cisco_V_Host String The value for this parameter should

contain the Host Server Name4 ObjectType String The value expected is “Cisco_V_Host”5 Granularity String The value expected is “FULL”

Output:The output will contain full details of the given hostSome of the parameters in response are explained below.

Sl.No Response parameter Type Description1 hostNm String Host Server name.2 name NamingAttributeType RDN of Host Server3 discoveredName String Host Server name4 DMSpecificInfo Alias4.1 aliasName String PN Instance Identifier

4.2 aliasValue String Identifier inside PN for thespecific Host server instance

5 VendorExtensionVCenter Information

5.1 name String “Cisco_vCenter”5.2 value String VCenter Name6 description String7 management_IP String IP Address of the Host server

specified in the request8 dnsName String9 macAddress String

10 state String11 softwareType String12 softwareVersion String13 uuid String14 dataStoreAllocation CiscoVStoreAllocListType Details of associated data stores15 vNetwkIntfList CiscoVNetwkTPListType Detail of associated network

interfaces15 vMotionEnabled boolean16 evcMode String17 model String Host Server model name18 vendor String Host Server vendor name

19 hypervisorProperty CiscoVHypervisorType20 hostClusterRef NamingAttributeType RDN of Host Cluster in which the

host is participating21 faultToleranceVersion String22 faultToleranceEnabled Boolean23 processPower CiscoVProcessingPwrType





8.3.5.1.4 List of available Host cluster Name from a particular Data Center


Sl.No Request parameter Type Description

1 MD String Management Domain name


4 ObjectType String The value expected is“Cisco_V_HostCluster”


Output:The output will contain list of Host Clusters from a particular Data Center. T he parameters in

response is explained below.

Response parameter Type DescriptionhostClusterNm String Host Cluster name.

8.3.5.1.5 Detail information of a Host cluster




3 Cisco_V_HostCluster String The value for this parameter shouldcontain the Host Cluster Name

4 ObjectType String The value expected is“Cisco_V_HostCluster”

5 Granularity String The value expected is “FULL”

Output:Response will contain detailed information of requested Host ClusterSome of the parameters are explained in the table below.





Sl.No Responseparameter

Type Description

1 hostClusterNm String Host Cluster name.2 name NamingAttributeType RDN of Host Cluster3 discoveredName String Host Cluster name

4 DMSpecificInfo4.1 aliasName String PN Instance Identifier4.2 aliasValue String Identifier inside PN for the

specific Host Cluster instance5 VendorExtension

VCenter Information5.1 name String “Cisco_vCenter”5.2 value String VCenter Name6 state String7 cpuAllocation CiscoVRsrcAllocType CPU allocation details8 memoryAllocation CiscoVRsrcAllocType

9 isHaEnabled Boolean10 isDrsEnabled Boolean11 vmMigrationCount Int12 evcMotion String13 isDpmEnabled Boolean

8.3.5.1.6 List of Data Store Name




3 ObjectType String The value expected is“Cisco_V_DataStore”


Output:

The output will contain list of all available Data Store names from a particular data center. Theparameter is explained below.

Response parameter Type DescriptiondataStoreNm String This is the Data Store name.





8.3.5.1.7 Detail information of a particular data store.





3 Cisco_V_DataStore String The value for this parameter shouldcontain the Data Store Name

4 ObjectType String The value expected is“Cisco_V_DataStore”

5 Granularity String The value expected is “FULL”

Output:Response will contain detailed information of requested Data Store. Some of theparameters are explained below.

Sl.No Response parameter Type Description1 dataStoreNm String Data Store name.2 name NamingAttributeType RDN of Data Store3 discoveredName String Name of the data Store from the

request4 DMSpecificInfo4.1 aliasName String PN Instance Identifier4.2 aliasValue String Identifier inside PN for the

specific Data Store instance5 VendorExtension

VCenter Information5.1 name String “Cisco_vCenter”5.2 value String VCenter Name6 storeType String7 storeLocation String8 freeSpace CiscoQuantityUnitType9 provisionedSpace CiscoQuantityUnitType10 capacity CiscoQuantityUnitType

11 isAccessible String12 isMultiHostAccess String13 uuid String





8.3.5.1.8 List of available Virtual machine ID





4 ObjectType String The value expected is “Cisco_VM”5 Granularity String The value expected is “NAME”

Output:The output will contain list of all available virtual machine names from VCenter. Theparameter is explained below.

Response parameter Type DescriptionvmNm String Virtual Machine Name

8.3.5.1.9 Detail information of a particular data store


Sl.No Request parameter Type Description1 MD String This is the Management Domain name


3 Cisco_VM String The value for this parameter shouldcontain the VM ID

4 ObjectType String The value expected is “Cisco_VM”5 Granularity String The value expected is “FULL”

Output:Response contains detailed information of the requested Virtual machineSl.No Response parameter Type Description1 name NamingAttributeType RDN of Virtual machine2 discoveredName String Virtual machine name3 DMSpecificInfo3.1 aliasName String PN Instance Identifier3.2 aliasValue String Identifier inside PN for the

specific VM instance





4 VendorExtensionVCenter Information

4.1 name String “Cisco_vCenter”4.2 value String VCenter Name5 state String

6 productType String7 softwareType String8 softwareVersion String9 cpuAllocation CiscoVRsrcAllocType10 uuid String11 memoryAllocation CiscoVRsrcAllocType12 dataStoreAllocation CiscoVStoreAllocListType Associated data store details13 serviceId String14 vmVersion String15 virtualCPU String16 minRequiredEVCMode String

17 supportingHostRef NamingAttributeType Host server RDN

8.3.6 L3 MPLS VPN

MPLS VPN functionality is supported as part of two mtosi interfaces.Resource Inventory Retrieval InterfaceConnection Retrieval Interface

Following is the flow to get MPLS inventory.1- Execute getInventory operation(for exact inputs please check the below

table) implemented as part of ResourceInventoryRetrieval Interface to get allthe configured L3 MPLS-VPN names

2- Execute getSubNetworkConnection operation implemented as part ofConnection Retrieval Interface to get the specific VPN details (for exactinputs please check the below table)

3- Execute getRoute operation implemented as part of Connection Retrievalinterface to get the available route table entries for the specific VPN.

8.3.6.1 Resource Inventory Retrieval Interface






8.3.6.1.1 Retrieving list of configured L3 MPLS-VPN names




2 ObjectType String The value expected is “SNC”3 Granularity String The value expected is “NAME”

Output:The output will contain list of all configured VPN IDs. The parameter is explained below.

Sl.No Response parameter Type Description1 sncNm String This contains the VPN Id Information.

For example:{"dmIdentifier":"net://net:1","vpnId":"1"}where “net://net:1” is the DM Identifierand “1” is the VPN Id

8.3.6.2 ConnectionRetrieval Interface

MPLS/VPN attribute retrieval is supported by these APIs:• getSubNetworkConnection• getRoute


8.3.6.2.1 Retrieving details of a VPNInput to getSubNetworkConnection API:

Sl.No Request parameter Type Description1 MD String This is the Management Domain name

2 MLSN String This is Multi Layer SubNetwork3 SNC String A VPN name as returned in the

response section of 4.6.1.1

Output:The output contains detailed information about a VPN. Some of the parameters areexplained below.






Type Description

1 name NamingAttributeType RDN of SNC2 discoveredName String VPN name

3 DMSpecificInfo3.1 aliasName String PN Instance Identifier3.2 aliasValue String VPN Object ID4 vendorExtensions4.1 Cisco_MPLS-

VPNAttrNameCiscoMPLSVPNAttrNameType MPLS VPN Naming Attribute

Type5 direction ConnectionDirectionType The value is “CD_BI” i.e bi-

directional6 layerRate LayerRateType7 aEndTpDataList TerminationPointDataListType8 correlationIdentifier String

9 callName String10 connectionId String

8.3.6.2.2 Retrieving route details

Input to getRoute API:


2 MLSN String This is Multi Layer SubNetwork3 SNC String A VPN name as returned in the

response section of 4.6.1.1

Output:The output contains information related to route tables and enpoints.Some of the parameters in the response are explained below:


Type Description

1 direction ConnectionDirectionType The value is “CD_BI”i.e bi-directional

2 aEndName NamingAttributeType RDN of Interfacesassociated with VRF

3 connectionId String4 vendorExtensions4.1 Cisco_MPLS-

VPNRouteAttrNameCiscoMPLSVPNRouteAttrNameType

4.1.1 VRF_Name Naming attribute type RDN of VRF





4.1.2 VRF_RouteTable CiscoMPLSVPNRouteType VRF Route table4.1.3 DMSpecificInfo 4.1.3.1 aliasName String PN Instance Identifier4.1.3.2 aliasValue String Identifier inside PN for

the specific VRF

instance

8.3.7 Floating termination point

This functionality is implemented as part of getInventory operation defined in ResourceInventory Retrieval Interface.

8.3.7.1 Resource Inventory Retrieval Interface

The WSDL document describing the details of the Interface can be accessed from the

Appendix section.

8.3.7.1.1 Retrieving details of all available port channels in a device



2 ME String Managed Element name3 ObjectType String The value should be “FTP”4 Granularity String The value should be “FULL”

Output:The output will contain detailed information of all the available port channels in a device. Some ofthe parameters in the response are explained below:

Sl.No Response parameter Type Description1 ftpInv FloatingTerminationPointInventoryType2 name NamingAttributeType RDN of FTP3 DM Specific Info3.1 aliasName String “PN_DM_OID”3.2 aliasValue String Identifier inside PN

for the specificDataLinkAggregationinstance

4 vendorExtensions





Logical InventoryType

Change Notification Type

Host

Addition of a Host Object Creation

Deletion of a Host

Object DeletionChanges in HostAttribute value Change

Changes in HostHypervisorAttribute Value Change

Changes in HostProcessor Attribute Value ChangeChanges in HostCPUCapacityProvision Attribute Value ChangeChanges in HostDiskCapacityProvision Attribute Value ChangeChanges in HostMemoryCapacityProvision Attribute Value ChangeAssociation of a Virtual Network Entity to a Host Object CreationDis-association of a Virtual Network Entity to a Host Object DeletionChanges in Host Virtual Network Entity Attribute Value ChangeAssociation of a Data Store with a Host Object CreationDis-association of a Data Store with a Host Object CreationChanges in the Data Store Associated with the Host Attribute Value Change

Virtual Machine

Migration of Virtual Machine to a new Host/Addition of a new Virtual Machine under a Host

Object Creation

Disassociation of a Virtual Machine with Host Object DeletionChanges in Virtual Machine Attribute Value ChangeChanges in VMMemoryCapacityAllocation Attribute Value ChangeChanges in of a VMCPUCapacityAllocation Attribute Value ChangeAssociation of a Virtual Network Entity with a Virtual Machine Object CreationDis-association of a Virtual Network Entity with a VirtualMachine

Object Deletion

Changes in Virtual Machine Virtual network entity Attribute Value ChangeAssociation of a Data Store with a Virtual Machine Object CreationDis-association of a Data Store with a Virtual Machine Object CreationChanges in the Data Store Associated with the Virtual Machine Attribute Value Change

Host Cluster

Addition of a Host Cluster Object CreationDeletion of a Host Cluster Object DeletionChanges in Host Cluster Attribute Value ChangeChanges in HostClusterCPUCapacityProvision Attribute Value ChangeChanges in HostClusterDiskCapacityProvision Attribute Value ChangeChanges in HostClusterMemoryCapacityProvision Attribute Value Change

Data StoreAddition of a new Data Store Object CreationDeleteion of a Data Store Object DeletionChanges in the DataStore Attribute Value Change

The following table gives a quick overview about the information received for thesupported notifications. Only the important attributes are detailed here.

OperationNotificationType

ObjectTypeattribute value

Object Name(FDN)Type of Object sent inNotification

Addition of aHost

Object Creation Cisco_V_Host HINTS= TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>

ObjectCreationType.Cisco_hostList

Deletion of aHost

Object DeletionCisco_V_Host HINTS= TIME:<Date in seconds

format>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>

NA

Changes in HostAttribute valueChange

Cisco_V_Host HINTS= TIME:<Date in secondsformat>;DMLIST:<comURI>

MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>

AttributeValueChangeType.Cisco_hostList

Changes inHostHypervisor Attribute Value

Change

Cisco_V_Host HINTS= TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>


Changes inHostProcessor

Attribute ValueChange

Cisco_V_Host HINTS= TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>


Changes inHostCPUCapacityProvision


Cisco_V_Host HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>


Changes inHostDiskCapacityProvision


Cisco_V_Host HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIME

Cisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>


Changes inHostMemoryCapacityProvision


Cisco_V_Host HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>

Association of aVirtual NetworkEntity to a Host

Object Creation Cisco_V_networkTP HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>

Cisco_V_networkTP=< VirtualNetwork Entity Name>

ObjectCreationType.object

Contained object:Cisco_V_NetworkTPType

Dis-association ofa VirtualNetwork Entityto a Host

Object Deletion Cisco_V_networkTP HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>Cisco_V_networkTP=< VirtualNetwork Entity Name>

NA

Changes in HostVirtual NetworkEntity


Cisco_V_networkTP HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>Cisco_V_networkTP=< VirtualNetwork Entity Name>

AttributeValueChangeType.attributeList

Contained object:Cisco_V_NetworkTPType

Association of aData Store with aHost

Object Creation Cisco_V_dataStoreAllocation

HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>Cisco_V_dataStoreAllocation=<

Allocated Datastore Name>

ObjectCreationType.object

Contained object:Cisco_V_StoreAllocType

Dis-association ofa Data Store witha Host


HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>Cisco_V_dataStoreAllocation=<Allocated Datastore Name>

NA

Changes in theData StoreAssociated withthe Host


Cisco_V_dataStoreAllocation

HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName> Cisco_V_Host =<HostName>Cisco_V_dataStoreAllocation=<Allocated Datastore Name>

AttributeValueChangeType.attributeList

Contained object:Cisco_V_StoreAllocType

Migration ofVirtual Machineto a new Host/Addition of a

Object Creation Cisco_VM HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>

ObjectCreationType. Cisco_vMList

Cisco_VM=<VM ID>Cisco_V_dataStoreAllocation=<Allocated Datastore Name>

Dis-association ofa Data Store witha Virtual

Machine


HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIME

Cisco_DC=<ME Name>:-:<DCName>Cisco_VM=<VM ID>Cisco_V_dataStoreAllocation=<Allocated Datastore Name>

NA

Addition of aHost Cluster

Object Creation Cisco_V_HostCluster HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_HostCluster=< HostCluster Name>

ObjectCreationType.Cisco_hostClusterList

Deletion of aHost Cluster

Object Deletion Cisco_V_HostCluster HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_HostCluster=< HostCluster Name>

NA

Changes in HostCluster


Cisco_V_HostCluster H HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_HostCluster=< Host

Cluster Name>

AttributeValueChangeType.Cisco_hostClusterList

Changes inHostClusterCPUCapacityProvision


Cisco_V_HostCluster HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_HostCluster=< HostCluster Name>


Changes inHostClusterDiskCapacityProvision


Cisco_V_HostCluster HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DC

Name>Cisco_V_HostCluster=< HostCluster Name>


Changes inHostClusterMemoryCapacityProvision


Cisco_V_HostCluster HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_HostCluster=< Host

Cluster Name>Addition of anew Data Store

Object Creation Cisco_V_DataStore HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>

Cisco_V_DataStore=< DatastoreName>

AttributeValueChangeType.Cisco_dataStoreList

Deleteion of aData Store

Object Deletion Cisco_V_DataStore H HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_DataStore=< DatastoreName>

NA

Changes in theDataStore


Cisco_V_DataStore HINTS=TIME:<Date in secondsformat>;DMLIST:<comURI>MD=CISCO_PRIMECisco_DC=<ME Name>:-:<DCName>Cisco_V_DataStore=< DatastoreName>

AttributeValueChangeType.Cisco_dataStoreList

8.4 Delta Inventory Management

Delta Inventory provides a facility to retrieve all Managed Elements whose physicalinventory has changed since a specified time.There are 2 steps involved in performing delta inventory management:a) Start Tracking Inventory Changes- This will initiate tracking of inventory changes.

b) Get Delta Inventory changes – This will retrieve the list of all Managed Elements withinventory changes.

8.4.1 Managed Element Names Retrieval Interface details

Interface Name DescriptiongetAllManagedElementNamesTS This API is used for delta inventory management

getAllManagedElementNamesTS API is used for Delta Inventory Management.


8.4.1.1 Start Tracking Inventory ChangesTo start tracking Inventory changes, getAllManagedElementNamesTS request has to beissued without <timestamp> tag.

The response contains a message, regarding the outcome of Start Tracking Delta InventoryRequest, in addition to the list of Managed Elements. From this point on, any physicalinventory changes to the Managed Elements will be tracked.

Input to getAllManagedElementNamesTS for start tracking inventory changes :

Request parameter Type DescriptionNil NA No parameters needed to initiate Start tracking

inventory changes

Output:Sl.No Response parameter Type Description1 name String Name of the ME2 operation OperationType Type of change on the Managed

Element.This value will be set to “UNKNOWN”in this response as this is the initialrequest to list all Managed Elements

3 Hints String Contains current time in millis followedby comURI

4 status String Contains the status of the StartTracking Inventory changes request.On success the status displayed is:“Start Tracking Executed successfully”On failure, the status displayed is:“Start Tracking Execution failed.”

NOTE: Any failure in sending the Start Tracking request will not stop this API from listingdevices. However the status label will clearly capture the information that start trackingfailed.

8.4.1.2 Get Delta Inventory changesTo get the list of Managed Elemets whose inventory has changed, thegetAllManagedElementNamesTS request needs to be issued with <timestamp> value inUTC Format.The response will contain a list of all managed elements which have been added, deletedor modified since the time specified in the request. Explaining one such entry from theresponse here.

Input to getAllManagedElementNamesTS for get delta inventory changes :

Request parameter Type Descriptiontimestamp Date Valid time in UTC Format i.e

“dd-MMM-yyyy HH:mm:ss ”

For example:2013-02-28T14:15:30

Output:

Sl.No Response parameter Type Description1 name String Name of the ME2 timestamp Date Last inventory updated time3 operation OperationType Type of change in the ME i.e ADD,

DELETE or UPDATE4 Hints String Current time in millis followed by

comURI

Error:Condition ErrorBlank value in <timestamp> tag

-or-Incorrect format in <timestamp> tag

-or-Empty timestamp tag <timestamp/>

Umarshalling Error

NOTE:

Sl.No Scenario Result1 Prime Network restarts

after a Start Tracking

Inventory changesrequest is issued.

If a Prime Network restarts,then all the ManagedElements will be shown as dirty i.e “ UPDATE” in the

operation field in response.

2 When there are nochanges after StartTracking was invokedsuccessfully

-or-When Start Tracking itselfhas failed

The response will contain the message "No changesdetected or Start tracking not issued."

8.5 MTOSI Standard Compliance

Cisco MTOSI Information Model is designed to conform to MTOSI 2.0 specifications.Cisco reference implementation extensions are introduced to support proprietary APIs andname space as per Cisco Prime Release requirements. Refer to the MTOSI standards in thelink: http://www.tmforum.org/MultiTechnologyOperations/2319/home.html

http://www.tmforum.org/MultiTechnologyOperations/2319/home.html




8.6 Trouble Shooting - MTOSI

The below table includes the issues that might be encountered while setting up OSS

integration layer and steps to troubleshoot the problem.

Table 7-4: OSS Integration Problems and Troubleshooting Procedure

ProblemDescription

Indication Probable Cause Troubleshooting Procedure

Web ServicesSecurityException

Web Service call toany of the Interfaceswill throw a WSSecurity exceptionwith authentication

failure message

The user ID / passwordprovided for the webservice call might notbe correct.

Use a proper User ID / password forthe web services call.

No DMsAvailableException

Exception messagefrom the Web Servicecall, stating that noDMs are available.

The communication toPN is not proper. TheIntegration layer wasnot able tocommunicate with thedomain manager ( DM).

• Verify that the PrimeNetworks application isrunning.

• Network Connectivity to thePrime Networks machine isproper.

getManagedElement returns aSOAP Exception

A call togetManagedElementreturns a WebServices exceptionstating that thedevice is not in up-state though it isactually up.

The device namespecified in request isincorrect

Cross check the device name ingetManagedElements response andcorrect if device is not in up state

Delta Inventory:Not receivingdelta inventorychange

notifications.

Notifications are notreceived if there is aninventory change.

If PN-IL is in standlonemode and if the OSSuser is not subscribedfor the notifications.

Subscribe for the notifications onMTOSI Notification Producer WebService.



Cisco Specific Interfaces


9 Cisco Specific InterfacesThis section describes the APIs that are provided as CISCO specific interfacaces. These donot conform to either MTOSI or 3GPP standards.

Cisco Specific Vendor APIs are provided for the following functional areas: Alarm Life Cycle Management Alarm Retrieval

For a sample SOAP Request and Response for all the APIs defined in these interfaces, referto the Prime Network OSS Integration Guide SOAP Request Response document on CiscoDeveloper Network .

9.1 Alarm Life Cycle Management

The alarm life cycle management support allows any OSS user to perform the followingoperations on any Prime Network Ticket. All the following operations are synchronous innature

• Acknowledge• De-Acknowledge• Clear• Retire• AddNote

The WSDL document describing the details of the Interface can be accessed from the Appendix section.

The following table lists the Alarm Life Cycle actions supported by PrimeNetwork.

DM/Operation Ack DeAck Clear AddNote RetirePN √ √ √ √ √

9.1.1 AlarmMgmt::Acknowlege

Add compliance for all the APIs.

Description:This API is used to acknowledge a Prime Network Ticket.







Input:Sl.No Parameter Data Type Description1 uniqueId String This parameter describes the Prime

Network Ticket ID.This ID could be an integer or of

format {[NewAlarm(Id=X)]}2 Hint String Optional value that can be used asextra meta data in processing therequests. For example, OSS applicationor FM can use this as atimestamp/version/state value thatcan be used to correlate actions toavoid issues with concurrent actionsperformed on a Prime Network Ticket.

3 Note String Optional note to include whileperforming the operation.

4 Username String Optional attribute. The user on behalfof whom the operation is done.

Output:Sl.No Parameter Data Type Description1 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 Error1 Invalid ID provided for the

operation in StandAloneIntegration layer deployment.

When user provides improper ticketId (not inexpected format), the operation will return soapfault with the detail containing thealarmApiException. The alarmApiException codewill be API_ERROR and message will contain theinformation:Please enter the PN Ticket Number or OID(format:[NewAlarm(Id=<Ticket Number>)]

2 Ticket does not exist on thePrimeNetwork.

The operation will return soap fault with the detailcontaining the alarmApiException.The alarmApiException code will be API_ERRORand message will contain the information:DM[<comURI>]=>Message[API_ERROR:<OperationName> 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 returnedby DM.

9.1.2 AlarmMgmt::De-Acknowlege

Description:This API is used to de-acknowledge a Prime Network Ticket.


Network Ticket ID.This ID could be an integer or offormat {[NewAlarm(Id=X)]}

2 Hint String Optional value that can be used asextra meta data in processing therequests. For example, OSS applicationor FM can use this as atimestamp/version/state value thatcan be used to correlate actions toavoid issues with concurrent actionsperformed on a Prime Network Ticket.

3 Note String Optional note to include whileperforming the operation.4 Username String Optional attribute. The user on behalf

of whom the de-acknowledgeoperation is done.






operation in StandAloneWhen user provides improper ticketId (not inexpected format), the operation will return soap

Integration layer deployment. fault with the detail containing thealarmApiException. The alarmApiException codewill be API_ERROR and message will contain theinformation:Please enter the PN Ticket Number or OID(format:[NewAlarm(Id=<Ticket Number>)]


The operation will return soap fault with the detailcontaining the alarmApiException.The alarmApiException code will be API_ERRORand message will contain the information:DM[<comURI>]=>Message[API_ERROR:<OperationName> 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 returnedby DM.

9.1.3 AlarmMgmt::Clear

Description:This API is used to force clear a Prime Network Ticket.



2 Hint String Optional value that can be used asextra meta data in processing therequests. For example, OSS applicationor FM can use this as atimestamp/version/state value thatcan be used to correlate actions toavoid issues with concurrent actionsperformed on a Prime Network Ticket.

3 Note String Optional note to include whileperforming the operation.

operation.3 Success boolean Value denoting the result of theoperation - “true” in case of success.



When user provides improper ticketId (not inexpected format), the operation will return soapfault with the detail containing thealarmApiException. The alarmApiException codewill be API_ERROR and message will contain theinformation:

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 detailcontaining the alarmApiException.The alarmApiException code will be API_ERRORand message will contain the information:DM[<comURI>]=>Message[API_ERROR:<OperationName> operation failed. Reason:<DM_Error_Message> ]


9.1.4 AlarmMgmt::Retire

Description:This API is used to retire(archive) a Prime Network Ticket.

Input:Sl.No Parameter Data Type Description1 uniqueId String This parameter describes the prime

network ticket ID.This ID could be an integer or offormat {[NewAlarm(Id=X)]}

2 Hint String Optional value that can be used as

extra meta data in processing therequests. For example, OSS applicationor FM can use this as atimestamp/version/state value thatcan be used to correlate actions toavoid issues with concurrent actionsperformed on an Prime NetworkTicket.




operation.3 Success boolean Value denoting the result of theoperation - “true” in case of success.



When user provides improper ticketId (not inexpected format), the operation will return soapfault with the detail containing thealarmApiException. The alarmApiException codewill be API_ERROR and message will contain the

information:Please enter the PN Ticket Number or OID(format:[NewAlarm(Id=<Ticket Number>)]

9.1.5 AlarmMgmt::Add Note

Description:This API is used to add a note to a Prime Network Ticket.



2 Hint String Optional value that can be used asextra meta data in processing therequests. For example, OSS applicationor FM can use this as atimestamp/version/state value thatcan be used to correlate actions to

avoid issues with concurrent actionsperformed on an Prime NetworkTicket.

3 Note String The mandatory note which is to beadded to the Prime Network Ticket.








When user provides improper ticketId (not inexpected format), the operation will return soapfault with the detail containing thealarmApiException. The alarmApiException codewill be API_ERROR and message will contain theinformation:Please enter the PN Ticket Number or OID(format:[NewAlarm(Id=<Ticket Number>)]








9.2 Alarm Retrieval

This is a vendor extension API provided to retrieve any alarms.


9.2.1 AlarmRetrieval::getsubtendingEvents

This API allows the user to get all subtending events for an Alarm or a Ticket in PrimeNetwork.

Description:This API is used to list all subtending events associated with an Alarm or a Ticket in

Prime Network .

Input :

Parameter Data Type DescriptionuniqueId String This parameter describes the Prime Network Ticket

ID.This ID could be an integer or of format{[NewAlarm(Id=X)]}

Output:

Sl.No Parameter Data Type Description1 eventId String This gives the PN event id for the input

ticket provided by user.2 correlationId String This refers to the alarmId to which the

event is associated with.





3 Description String This gives the description of the event.4 Source String Identifier of the model object that is the

root cause of the event5 duplicationCount String The duplication count as it is calculated

by the VNE. This count is meaningful for

flapping events and represents the totalnumber of non-cleared events that areaggregated by this flapping event.

6 Severity String The severeness of the event in thesystem. Severity enumeration(Indeterminate, Information, Cleared,Warning, Minor, Major , Critical)

7 Timestamp String This gives the origin timestamp of theevent.

8 Archived String Indicates whether this event is archivedin the database of Prime Network.

9 ElementTypeA String The brand name of the device thisnetwork event is associated with.

10 ElementTypeZ String In case of a link, will return the Z sizeelement type.

11 DetectionType String Represents the way this event wasdetected. Possible Values: service,syslogs, trap v1/v2/v3

12 extendedName String This value can be used to distinctbetween event types defined outsidePrime Network, In external OSS systemssuch as PPM which forward events toPrime Network.

13 State String The event state is a short, textualdescription of Name field (defined insend-alarm-msg-util.xml)

14 suppressionDisplay String Indicates whether this event should bedisplayed in the GUI

15 Name String Event's type enumeration. For example:Link down, Port up, Login etc.

16 reductionCount String The reduction count as it is calculated bythe VNE. This count is meaningful forflapping events and represents the totalnumber of events that are aggregated by

this flapping event.17 creationInDeviceTimezone String A human readable string representing

the event creation time in the devicetimezone

Error:

Appendix I – References to WSDL Documents


server –is the hostname or IP address of Prime Central or Prime Network ServertgppPort – is the port number where CXF service for TGPP is running. By default port number is9220.

10.1.4 3GPP Notification Consumer WSDL

This WSDL will be used by the Notification Consumer ( OSS ) to receive 3GPP Notifications.

This WSDL does not support any operation and is provided for the OSS client user to downloadthe WSDL.

The WSDL for 3GPP File Transfer IRP can be accessed from the following URL:

https://<server>:<tgppPort>/TGPPNotificationIRP_Consumer?wsdl

Where:server –is the hostname or IP address of Prime Central or Prime Network ServertgppPort – is the port number where CXF service for TGPP is running. By default port number is9220.

10.2 MTOSI WSDL Documents

This section contains references to the following WSDL Documents:• Managed Element Retrieval WSDL• Managed Element Names Retrieval WSDL• Equipment Inventory Retrieval WSDL• Termination Point Retrieval WSDL• Resource Inventory Retrieval WSDL• Connection Retrieval WSDL• Ethernet Virtual Connection (EVC) Resource Retrieval WSDL

10.2.1 Managed Element Retrieval WSDL

The WSDL documents can be obtained by following URL

https://<server>:< mtosiPort>/ManagedElementRetrieval_RPC?wsdlhttps://<server>:<mtosiport>/ManagedElementNamesRetrieval_RPC?wsdl

Where:server - is the hostname or IP address of Prime Central or Prime Network ServermtosiPort - is the port number where the mtosi service is running. By default port number is9110.

10.2.2 Managed Element Names Retrieval WSDL

The WSDL document can be obtained from the following URL

https://<server>:<mtosiPort>/ManagedElementNamesRetrieval_RPC?wsdl


10.2.3 Equipment Inventory Retrieval WSDL

WSDL document can be obtained by following URL

https://<server>:<mtosiPort>/ EquipmentInventoryRetrieval_RPC?wsdl


10.2.4 Termination Point Retrieval WSDL

The WSDL document can be obtained by following URL

https://<server>:<mtosiPort>/ TerminationPointRetrieval_RPC?wsdl


10.2.5 Resource Inventory Retrieval WSDL


https://<server>:<mtosiPort>/ResourceInventoryRetrievalRPC?wsdl

Where:server –is the hostname or IP address of Prime Central or Prime Network ServermtosiPort – is the port number where CXF service for MTOSI is running. By default port numberis 9110.

10.2.6 Connection Retrieval WSDL


https://<server>:<mtosiPort>/ConnectionRetrievalRPC?wsdl

Where:server –is the hostname or IP address of Prime Central or Prime Network ServermtosiPort – is the port number where CXF service for MTOSI is running. By default port numberis 9110

10.2.7 Ethernet Virtual Connection (EVC) Resource Retrieval WSDL


https://<server>:<mtosiPort>/FlowDomainFragmentRetrievalRPC?wsdl

Where:server –is the hostname or IP address of Prime Central or Prime Network ServermtosiPort – is the port number where CXF service for MTOSI is running. By default port numberis 9110

10.3 Cisco Specific Extensions WSDL Documents

This section has references to the following WSDL Documents:• Alarm Life Cycle Management WSDL• Alarm Retrieval Management WSDL

10.3.1 Alarm Life Cycle Management WSDL

The WSDL for Alarm Life Cycle management Interface can be accessed from the following URL:

https://<server>:<alarmMgmtPort>/AlarmManagementAPI ?wsdl

Where :

server - is the hostname or IP address of Prime Central or Prime Network Server where theWeb Service is running.alarmMgmtPort – is the port number where CXF service for Alarm Mgmt API is running. Bydefault port number is 9020.

10.3.2 Alarm Retrieval Management WSDL

The WSDL for Alarm Retrieval interface can be accessed from the following URL:

https://<server>:<alarmMgmtPort>/AlarmRetrievalAPI?wsdl

Where :

server - is the hostname or IP address of Prime Central or Prime Network Server where theWeb Service is running.alarmMgmtPort – is the port number where CXF service for Alarm Mgmt API is running. Bydefault port number is 9020.

11 Appendix II – 3GPP-Miscellaneous

This section includes:• 3GPP InventoryNrm Schema File• 3GPP Inventory File• 3GPP Detailed Inventory Information• 3GPP Status File• 3GPP FT-IRP Inventory Notifications• FTP Configuration• Useful Code Snippets for 3GPP

11.1 3GPP InventoryNrm Schema File

<?xml ver si on= "1.0" encodi ng= "UTF-8" ?>

<! - -3GPP TS 32. 696 I nvent or y Management NRM I RPI nvent or y dat a f i l e NRM- speci f i c XML schemai nvent or yNr m. xsd

- - >

<schemat ar get Namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.696#inventoryNrm"

el ement For mDef aul t = "qualified" xml ns= "http://www.w3.org/2001/XMLSchema" xml ns: xn=

"http://www.3gpp.org/ftp/specs/archive/32_series/32.626#genericNrm" xml ns: i n=

"http://www.3gpp.org/ftp/specs/archive/32_series/32.696#inventoryNrm" >

Appendix II – 3GPP-Miscellaneous




<! - - I nvent or y Management Al t er nat i ve 1 NRM I RP NRM cl ass associ at ed XMLel ement s - - ><si mpl eType name= "eightOctetsType" ><r est r i ct i on base= "hexBinary" ><l engt h val ue= "8" / ></ r est r i ct i on></ si mpl eType><si mpl eType name= "fourOctetsType" ><r est r i ct i on base= "hexBinary" ><l engt h val ue= "4" / ></ r est r i ct i on></ si mpl eType><si mpl eType name= "angleValueType" ><r est r i ct i on base= "short" ><mi nI ncl usi ve val ue= "0" / ><maxI ncl usi ve val ue= "3600" / ></ r est r i ct i on></ si mpl eType>

<el ementname= "InventoryUnit"

subst i t ut i onGr oup= "xn:ManagedElementOptionallyContainedNrmClass" ><compl exType><compl exCont ent ><ext ensi on base= "xn:NrmClass" ><sequence><el ement

name= "attributes" mi nOccur s= "0" ><compl exType><al l ><el ement

name= "inventoryUnitType" t ype= "string"

/ ><el ement

name= "vendorUnitFamilyType" t ype= "string" mi nOccur s= "0"

/ ><el ement

name= "vendorUnitTypeNumber" t ype= "string" mi nOccur s= "0"

/ ><el ement

name= "vendorName" t ype= "string" / >

<el ementname= "serialNumber" t ype= "string" mi nOccur s= "0" / >

</ ext ensi on></ compl exCont ent ></ compl exType></ el ement ></ schema>

11.2 3GPP Inventory File

A Sample inventory file is given here

I M_20120808_1005+0300_32767_10. 86. 66. 35_10002. xml

Where :

IM – Indicates the management type20120808 – Date of creation32767–File expiry time in hours

10.86.66.35 – Name of the device10002 – Running serial number ( RC )

11.2.1 Inventory File Contents

The inventory file contains physical and logical inventory information. A sample inventoryfile containing inventory data is given here:

<?xml ver si on=" 1. 0" encodi ng=" UTF- 8" st andal one=" yes" ?><?xml - st yl esheet t ype=" t ext / xsl " hr ef =" I nvent oryXSLT. xsl " ?><I nvent oryUni txml ns: ns2=" ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 626#gener i cNr m"xml ns=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 696#i nvent oryNr m" xml ns: ns4=" Ci scoTgppI nvCommon" xml ns: ns3=" Ci scoSpeci f i cGGSNNameSpace"xml ns: ns9="ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_seri es/ 32. 526#sonPol i cyNr m"xml ns: ns5=" ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 755#epcNr m"xml ns: ns6=" ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 636#coreNr m"xml ns: ns10=" Ci scoSpeci f i cPGWNameSpace" xml ns: ns7=" apnpr of i l e"xml ns: ns11=" Ci scoSpeci f i cSGWNameSpace" xml ns: ns8=" saegw" >><at t r i but es>Managed El ement Dat a<vendor Uni t Fami l yType>CI SCO_ASR_5000</ vendor Uni t Fami l yType>

<vendor Uni t TypeNumber ></ vendor Uni t TypeNumber ><vendor Name>Ci sco</ vendor Name><ser i al Number ></ ser i al Number ><ver si onNumber >14. 0 ( 43929) </ ver si onNumber ></ at t r i but es><at t r i but es>Har dwar e Uni t Dat a<vendor Uni t Fami l yType>ASR5000 Chass i s</ vendor Uni t Fami l yType>

<vendor Uni t TypeNumber ></ vendor Uni t TypeNumber ><vendor Name>Ci sco</ vendor Name><ser i al Number ></ ser i al Number ><uni t Posi t i on>ManagedEl ement =10. 56. 22. 105, Chass i s=1</ uni t Posi t i on></ at t r i but es><at t r i but es>Har dwar e Uni t Dat a<vendor Uni t Fami l yType>Redundancy Cr ossbar Car d - 40</ vendor Uni t Fami l yType><vendor Uni t TypeNumber >Unknown Modul e</ vendor Uni t TypeNumber ><vendor Name>Ci sco</ vendor Name><ser i al Number >SAD154000TG</ ser i al Number ><uni t Posi t i on>ManagedEl ement =10. 56. 22. 105, Chass i s=1,Sl ot Num=40</ uni t Posi t i on><ver si onNumber >V03</ ver si onNumber ></ at t r i but es>

:::

<! - - Logi cal I nvent or y - - >

<at t r i but es>Sof t war e Uni t Dat a<vendor Name>Ci sco</ vendor Name></ at t r i but es><ns2: ManagedFunct i oni d=" {[ ManagedEl ement ( Key=10. 56. 22. 105) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=bi swa) ] [ Mobi l e] [ SGWCont ai ner ] [ SGWSer vi ce( Ser vi ceName=bul u) ] }"><ns2: VsDat aCont ai ner i d=" bul u- VsDat a1" >

<ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">cl asscom. ci sco. pr i me. esb. t gpp. model . common. Ser vi ngGWFunct i on</ ns2: vsDat aType><ns2: vsDat aFor mat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema-i nst ance" >ht t p: / / www. 3gpp. or g/ f t p/ specs/ archi ve/ 32_ser i es/ 32. 755#epcNr m-9. 3. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns4: vsDat aCi scoSpeci f i cMobi l eCont ai ner "xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"><ns5: Ser vi ngGWFunct i oni d=" {[ ManagedEl ement ( Key=10. 56. 22. 105) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=bi swa) ] [ Mobi l e] [ SGWCont ai ner ] [ SGWSer vi ce( Ser vi ceName=bul u) ] }"><ns5: at t r i but es><ns5: user Label >bul u</ ns5: user Label ><ns5: pLMNI dLi st / ><ns5: t ACLi st / ></ ns5: at t r i but es><ns2: VsDat aCont ai ner i d=" bul u- VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng" xml ns: xs=" ht t p: / / www

. w3. or g/ 2001/ XMLSchema">Ser vi ngGWFunct i on</ ns2: vsDat aType><ns2: vsDat aFor mat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Ci scoSpeci f i cAt t r i but es. sgw. 1.0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns11: SGWSer vi ceType"><ns11: Account i ngCont ext >bi swa</ ns11: Account i ngCont ext ><ns11: Account i ngMode>GTPP</ ns11: Account i ngMode>

<ns11: Egr essCont ext >bi swa</ ns11: Egr essCont ext ><ns11: Egr essPr ot ocol >gt p- pmi p</ ns11: Egr essPr ot ocol ><ns11: Ser vi ceSt at us>Down</ ns11: Ser vi ceSt at us></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns5: Ser vi ngGWFunct i on></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns2: ManagedFunct i on>

<! - - ACS I nvent or y - - >

<ns2: ManagedFunct i oni d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ Mobi l e] [ Act i veChar gi ngCont ai ner ] [ Act i veChar gi ngSer vi ce( Ser vi ceName=demo) ]}" ><ns2: VsDat aCont ai ner i d=" demo- VsDat a1"><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">cl asscom. ci sco. pr i me. esb. t gpp. model . common. AcsPr of i l e</ ns2: vsDat aType><ns2: vsDat aFormat Ver si on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"

xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema-i nst ance" >Ci scoSpeci f i cAt t r i but es. acs. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns4: vsDat aCi scoSpeci f i cMobi l eCont ai ner"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"><ns8: AcsPr of i l ei d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ Mobi l e] [ Act i veChar gi ngCont ai ner ] [ Act i veChar gi ngSer vi ce( Ser vi ceName=demo) ]}" ><ns8: at t r i but es><ns8: user Label >demo</ ns8: user Label ></ ns8: at t r i but es><ns2: VsDat aCont ai ner i d=" demo- VsDat a1"><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Act i veChar gi ngSer vi ce</ ns2: vsDat aType><ns2: vsDat aFormat Ver si on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Ci scoSpeci f i cAt t r i but es. acs. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns23: Act i veChar gi ngSer vi ceType"xml ns: ns23=" Act i veChar gi ngSer vi ceType" ><Act i veChar gi ngFai r Usage><CpuThr eshol dPer cent >100</ CpuThr eshol dPer cent ></ Act i veChar gi ngFai r Usage>

<Al gMedi aI dl eTi meout >120 sec</ Al gMedi aI dl eTi meout ><Bandwi dt hPol i cyCont ai ner ><Bandwi dt hPol i cy><Bandwi dt hPol i cyName>hi ma</ Bandwi dt hPol i cyName><Tot al Bandwi dt hI DConf i gur ed>0</ Tot al Bandwi dt hI DConf i gur ed>

<Tot al Gr oupLi mi t Conf i gur ed>0</ Tot al Gr oupLi mi t Conf i gur ed></ Bandwi dt hPol i cy><Tot al Bandwi dt hPol i cyConf i gur ed>1</ Tot al Bandwi dt hPol i cyConf i gur ed></ Bandwi dt hPol i cyCont ai ner ><Cdr Fl owCont r ol >Enabl ed</ Cdr Fl owCont r ol ><Cdr Fl owCont r ol Unsent QueueSi ze>75</ Cdr Fl owCont r ol Unsent QueueSi ze><Cdr Fl owUnsent QueueHi gh>56</ Cdr Fl owUnsent QueueHi gh><Cdr Fl owUnsent QueueLow>18</ Cdr Fl owUnsent QueueLow><Char gi ngAct i onCont ai ner ><Char gi ngAct i on><Char geVol ume>i p byt es</ Char geVol ume><Char gi ngAct i onAl l ocat i onRet ent i onPr i or i t y/ ><Char gi ngAct i onBandwi dt h><BandWi dt hI D>0</ BandWi dt hI D><Downl i nk>Di sabl ed</ Downl i nk><Upl i nk>Di sabl ed</ Upl i nk></ Char gi ngAct i onBandwi dt h><Char gi ngAct i onBi l l i ngAct i on><Edr >Di sabl ed</ Edr ><Egcdr >Di sabl ed</ Egcdr ><Radi usAccount i ngRecor d>Di sabl ed</ Radi usAccount i ngRecor d><Rf Account i ng>Di sabl ed</ Rf Account i ng><Udr >Enabl ed</ Udr ></ Char gi ngAct i onBi l l i ngAct i on><Char gi ngAct i onFl owAct i on><Cl ear Quot aRet r yTi mer >Di sabl ed</ Cl ear Quot aRet r yTi mer ><Condi t i onal Redi r ect >4</ Condi t i onal Redi r ect ><Di scar d>Di sabl ed</ Di scar d><OcsRedi r ect URL>Di sabl ed</ OcsRedi r ect URL>

<Redi r ect URL>Di sabl ed</ Redi r ect URL><Ter mi nat eFl ow>Di sabl ed</ Ter mi nat eFl ow><Ter mi nat eSessi on>Di sabl ed</ Ter mi nat eSessi on></ Char gi ngAct i onFl owAct i on><Char gi ngAct i onName>hi m</ Char gi ngAct i onName><Char gi ngAct i onQoS><Renegot i at eTraf f i cCl ass>Di sabl ed</ Renegot i at eTr af f i cCl ass></ Char gi ngAct i onQoS><Char gi ngAct i onVi deo><Readdr ess i ngCAE>Di sabl ed</ Readdr ess i ngCAE><Tr ansr at i ng>Di sabl ed</ Tr ansr at i ng></ Char gi ngAct i onVi deo><Char gi ngEDRName>Di sabl ed</ Char gi ngEDRName><Char gi ngEGCDRs>Di sabl ed</ Char gi ngEGCDRs><Char gi ngRf >Di sabl ed</ Char gi ngRf ><Char gi ngUDRs>Enabl ed</ Char gi ngUDRs><Cont ent Fi l t er i ng>Enabl ed</ Cont ent Fi l t er i ng><Cont ent I d>0</ Cont ent I d><Cr edi t Conr ol >Di sabl ed</ Cr edi t Conr ol ><Fl owI dl eTi meout >300 sec</ Fl owI dl eTi meout ><Fl owMappi ngI dl eTi meout >300 sec</ Fl owMappi ngI dl eTi meout >

<Li mi t For Fl owTypeSt at e>Di sabl ed</ Li mi t For Fl owTypeSt at e><Ret r ansmi ss i onCount >Di sabl ed</ Ret r ansmi ss i onCount ></ Char gi ngAct i on><Char gi ngAct i on><Char geVol ume>i p byt es</ Char geVol ume><Char gi ngAct i onAl l ocat i onRet ent i onPr i or i t y/ ><Char gi ngAct i onBandwi dt h>

<BandWi dt hI D>0</ BandWi dt hI D><Downl i nk>Di sabl ed</ Downl i nk><Upl i nk>Di sabl ed</ Upl i nk></ Char gi ngAct i onBandwi dt h><Char gi ngAct i onBi l l i ngAct i on><Edr >Di sabl ed</ Edr ><Egcdr >Di sabl ed</ Egcdr ><Radi usAccount i ngRecor d>Di sabl ed</ Radi usAccount i ngRecor d><Rf Account i ng>Di sabl ed</ Rf Account i ng><Udr >Enabl ed</ Udr ></ Char gi ngAct i onBi l l i ngAct i on><Char gi ngAct i onFl owAct i on><Cl ear Quot aRet r yTi mer >Di sabl ed</ Cl ear Quot aRet r yTi mer ><Condi t i onal Redi r ect >Di sabl ed</ Condi t i onal Redi r ect ><Di scar d>Di sabl ed</ Di scar d><OcsRedi r ect URL>Di sabl ed</ OcsRedi r ect URL><Redi r ect URL>Di sabl ed</ Redi r ect URL><Ter mi nat eFl ow>Di sabl ed</ Ter mi nat eFl ow><Ter mi nat eSessi on>Enabl ed</ Ter mi nat eSessi on></ Char gi ngAct i onFl owAct i on><Char gi ngAct i onName>act i on1</ Char gi ngAct i onName><Char gi ngAct i onQoS><Renegot i at eTraf f i cCl ass>Di sabl ed</ Renegot i at eTr af f i cCl ass></ Char gi ngAct i onQoS><Char gi ngAct i onVi deo><Readdr ess i ngCAE>Di sabl ed</ Readdr ess i ngCAE><Tr ansr at i ng>Di sabl ed</ Tr ansr at i ng></ Char gi ngAct i onVi deo><Char gi ngEDRName>Di sabl ed</ Char gi ngEDRName>

<Char gi ngEGCDRs>Di sabl ed</ Char gi ngEGCDRs><Char gi ngRf >Di sabl ed</ Char gi ngRf ><Char gi ngUDRs>Enabl ed</ Char gi ngUDRs><Cont ent Fi l t er i ng>Enabl ed</ Cont ent Fi l t er i ng><Cont ent I d>0</ Cont ent I d><Cr edi t Conr ol >Di sabl ed</ Cr edi t Conr ol ><Fl owI dl eTi meout >300 sec</ Fl owI dl eTi meout ><Fl owMappi ngI dl eTi meout >300 sec</ Fl owMappi ngI dl eTi meout ><Li mi t For Fl owTypeSt at e>Di sabl ed</ Li mi t For Fl owTypeSt at e><Ret r ansmi ss i onCount >Di sabl ed</ Ret r ansmi ss i onCount ></ Char gi ngAct i on><Char gi ngAct i on><Char geVol ume>i p byt es</ Char geVol ume><Char gi ngAct i onAl l ocat i onRet ent i onPr i or i t y/ ><Char gi ngAct i onBandwi dt h><BandWi dt hI D>0</ BandWi dt hI D><Downl i nk>Di sabl ed</ Downl i nk><Upl i nk>Di sabl ed</ Upl i nk></ Char gi ngAct i onBandwi dt h><Char gi ngAct i onBi l l i ngAct i on>

<Edr >Di sabl ed</ Edr ><Egcdr >Di sabl ed</ Egcdr ><Radi usAccount i ngRecor d>Di sabl ed</ Radi usAccount i ngRecor d><Rf Account i ng>Di sabl ed</ Rf Account i ng><Udr >Enabl ed</ Udr ></ Char gi ngAct i onBi l l i ngAct i on><Char gi ngAct i onFl owAct i on>

<Cl ear Quot aRet r yTi mer >Di sabl ed</ Cl ear Quot aRet r yTi mer ><Condi t i onal Redi r ect >Di sabl ed</ Condi t i onal Redi r ect ><Di scar d>Di sabl ed</ Di scar d><OcsRedi r ect URL>Di sabl ed</ OcsRedi r ect URL><Redi r ect URL>Di sabl ed</ Redi r ect URL><Ter mi nat eFl ow>Di sabl ed</ Ter mi nat eFl ow><Ter mi nat eSessi on>Di sabl ed</ Ter mi nat eSessi on></ Char gi ngAct i onFl owAct i on><Char gi ngAct i onName>deva- char gi ng</ Char gi ngAct i onName><Char gi ngAct i onQoS><Renegot i at eTraf f i cCl ass>Di sabl ed</ Renegot i at eTr af f i cCl ass></ Char gi ngAct i onQoS><Char gi ngAct i onVi deo><Readdr ess i ngCAE>Di sabl ed</ Readdr ess i ngCAE><Tr ansr at i ng>Di sabl ed</ Tr ansr at i ng></ Char gi ngAct i onVi deo><Char gi ngEDRName>Di sabl ed</ Char gi ngEDRName><Char gi ngEGCDRs>Di sabl ed</ Char gi ngEGCDRs><Char gi ngRf >Di sabl ed</ Char gi ngRf ><Char gi ngUDRs>Enabl ed</ Char gi ngUDRs><Cont ent Fi l t er i ng>Enabl ed</ Cont ent Fi l t er i ng><Cont ent I d>5</ Cont ent I d><Cr edi t Conr ol >Di sabl ed</ Cr edi t Conr ol ><Fl owI dl eTi meout >300 sec</ Fl owI dl eTi meout ><Fl owMappi ngI dl eTi meout >300 sec</ Fl owMappi ngI dl eTi meout >

<Li mi t For Fl owTypeSt at e>Di sabl ed</ Li mi t For Fl owTypeSt at e><Ret r ansmi ss i onCount >Di sabl ed</ Ret r ansmi ss i onCount ></ Char gi ngAct i on><Char gi ngAct i on><Char geVol ume>i p byt es</ Char geVol ume><Char gi ngAct i onAl l ocat i onRet ent i onPr i or i t y><Pr i or i t yCapabi l i t yI ndi cat or >1</ Pr i or i t yCapabi l i t yI ndi cat or ><Pri or i t yLevel >4</ Pr i or i t yLevel ><Pr i or i t yVul ner abi l i t yI ndi cat or >0</ Pr i or i t yVul ner abi l i t yI ndi cat or ></ Char gi ngAct i onAl l ocat i onRet ent i onPr i or i t y><Char gi ngAct i onBandwi dt h><BandWi dt hI D>0</ BandWi dt hI D><Downl i nk>Di sabl ed</ Downl i nk><Upl i nk>Di sabl ed</ Upl i nk></ Char gi ngAct i onBandwi dt h><Char gi ngAct i onBi l l i ngAct i on><Edr >Di sabl ed</ Edr ><Egcdr >Di sabl ed</ Egcdr ><Radi usAccount i ngRecor d>Di sabl ed</ Radi usAccount i ngRecor d><Rf Account i ng>Di sabl ed</ Rf Account i ng><Udr >Enabl ed</ Udr ></ Char gi ngAct i onBi l l i ngAct i on><Char gi ngAct i onFl owAct i on><Cl ear Quot aRet r yTi mer >Di sabl ed</ Cl ear Quot aRet r yTi mer ><Condi t i onal Redi r ect >kar t eekkar t eek</ Condi t i onal Redi r ect >

<Di scar d>Di sabl ed</ Di scar d><OcsRedi r ect URL>Di sabl ed</ OcsRedi r ect URL><Redi r ect URL>Di sabl ed</ Redi r ect URL><Ter mi nat eFl ow>Di sabl ed</ Ter mi nat eFl ow><Ter mi nat eSessi on>Di sabl ed</ Ter mi nat eSessi on></ Char gi ngAct i onFl owAct i on><Char gi ngAct i onName>hi ma</ Char gi ngAct i onName>

<Char gi ngAct i onQoS><Renegot i at eTraf f i cCl ass>Di sabl ed</ Renegot i at eTr af f i cCl ass></ Char gi ngAct i onQoS><Char gi ngAct i onVi deo><Readdr ess i ngCAE>Di sabl ed</ Readdr ess i ngCAE><Tr ansr at i ng>Di sabl ed</ Tr ansr at i ng></ Char gi ngAct i onVi deo><Char gi ngEDRName>Di sabl ed</ Char gi ngEDRName><Char gi ngEGCDRs>Di sabl ed</ Char gi ngEGCDRs><Char gi ngRf >Di sabl ed</ Char gi ngRf ><Char gi ngUDRs>Enabl ed</ Char gi ngUDRs><Cont ent Fi l t er i ng>Enabl ed</ Cont ent Fi l t er i ng><Cont ent I d>0</ Cont ent I d><Cr edi t Conr ol >Enabl ed</ Cr edi t Conr ol ><Cr edi t Rat i ngGr oup>5000</ Cr edi t Rat i ngGr oup><Fl owI dl eTi meout >300 sec</ Fl owI dl eTi meout ><Fl owMappi ngI dl eTi meout >300 sec</ Fl owMappi ngI dl eTi meout ><Li mi t For Fl owTypeSt at e>Di sabl ed</ Li mi t For Fl owTypeSt at e><Ret r ansmi ss i onCount >Di sabl ed</ Ret r ansmi ss i onCount ></ Char gi ngAct i on></ Char gi ngAct i onCont ai ner ><Cont ent Fi l t er i ng>Di sabl ed</ Cont ent Fi l t er i ng><Cont ent Fi l t er i ngCat egor i esCont ai ner / ><Cont ent Fi l t er i ngMat chMet hod>gener i c</ Cont ent Fi l t er i ngMat chMet hod><Cr edi t Cont r ol Cont ai ner >

<Cr edi t Cont r ol Gr oups><ApnType>gn</ ApnType><Cr edi t Cont r ol Di amet er ><Di ct i onar y>dcca- cust om8</ Di ct i onar y><Pendi ngTi meout >10 sec</ Pendi ngTi meout ><Sessi onFai l over >Di sabl ed</ Sessi onFai l over ></ Cr edi t Cont r ol Di amet er ><Fai l ur eHandl i ng>t er mi nat e<Ter mi nat eRequest >r et r y- and- t er mi nat e</ Ter mi nat eRequest ><Updat eRequest >r et r y- and- t er mi nat e</ Updat eRequest ></ Fai l ur eHandl i ng><Gr oup>dcca- 1</ Gr oup><Mode>Radi us</ Mode><MsccFi nal Uni t Act i on>cat egor y</ MsccFi nal Uni t Act i on><Pendi ngTr af f i cTr eat ment ><For cedReaut h>dr op</ For cedReaut h><NoQuot a>dr op</ NoQuot a><Quot aExhaust ed>dr op</ Quot aExhaust ed><Tr i gger >dr op</ Tr i gger ><Val i di t yExpi r ed>dr op</ Val i di t yExpi r ed></ Pendi ngTr af f i cTr eat ment >

<Quot a><Hol di ngTi me>N/ A</ Hol di ngTi me><Request Tr i gger >i ncl ude packet </ Request Tr i gger ><Ti meThr eshol d>N/ A</ Ti meThr eshol d><Uni t sThr eshol d>N/ A</ Uni t sThr eshol d>

<Val i di t yTi me>N/ A</ Val i di t yTi me><Vol umeThr eshol d>N/ A</ Vol umeThr eshol d></ Quot a><Ser ver Unr eachabl eFai l ur eHandl i ng>N/ A<Updat eRequest >N/ A</ Updat eRequest ></ Ser ver Unr eachabl eFai l ur eHandl i ng><Tr i gger Type>N/ A</ Tr i gger Type></ Cr edi t Cont r ol Gr oups><Cr edi t Cont r ol Gr oups><ApnType>gn</ ApnType><Cr edi t Cont r ol Di amet er ><Di ct i onar y>dcca- cust om8</ Di ct i onar y><Pendi ngTi meout >10 sec</ Pendi ngTi meout ><Sessi onFai l over >Di sabl ed</ Sessi onFai l over ></ Cr edi t Cont r ol Di amet er ><Fai l ur eHandl i ng>t er mi nat e<Ter mi nat eRequest >r et r y- and- t er mi nat e</ Ter mi nat eRequest ><Updat eRequest >r et r y- and- t er mi nat e</ Updat eRequest ></ Fai l ur eHandl i ng><Gr oup>deva- cr edi t - cont r ol </ Gr oup><Mode>Di amet er </ Mode><MsccFi nal Uni t Act i on>cat egor y</ MsccFi nal Uni t Act i on><Pendi ngTr af f i cTr eat ment >

<For cedReaut h>dr op</ For cedReaut h><NoQuot a>dr op</ NoQuot a><Quot aExhaust ed>dr op</ Quot aExhaust ed><Tr i gger >dr op</ Tr i gger ><Val i di t yExpi r ed>dr op</ Val i di t yExpi r ed></ Pendi ngTr af f i cTr eat ment ><Quot a><Hol di ngTi me>N/ A</ Hol di ngTi me><Request Tr i gger >i ncl ude packet </ Request Tr i gger ><Ti meThr eshol d>N/ A</ Ti meThr eshol d><Uni t sThr eshol d>N/ A</ Uni t sThr eshol d><Val i di t yTi me>N/ A</ Val i di t yTi me><Vol umeThr eshol d>N/ A</ Vol umeThr eshol d></ Quot a><Ser ver Unr eachabl eFai l ur eHandl i ng>N/ A<Updat eRequest >N/ A</ Updat eRequest ></ Ser ver Unr eachabl eFai l ur eHandl i ng><Tr i gger Type>N/ A</ Tr i gger Type></ Cr edi t Cont r ol Gr oups><Cr edi t Cont r ol Gr oups>

<ApnType>vi r t ual </ ApnType><Cr edi t Cont r ol Di amet er ><Di ct i onar y>dcca- cust om25</ Di ct i onar y><EndPoi nt Real m>N/ A</ EndPoi nt Real m><Endpoi nt Name>deva- or i gi n</ Endpoi nt Name><Pendi ngTi meout >300 sec

</ Pendi ngTi meout ><Sessi onFai l over >Enabl ed</ Sessi onFai l over ></ Cr edi t Cont r ol Di amet er ><Di amet er Peer Sel ect >256pr ef i x234<Peer >deva- peer </ Peer ><Real m>N/ A</ Real m><Secondar yPeer >deva- secondar y</ Secondar yPeer ><Secondar yReal m>N/ A</ Secondar yReal m></ Di amet er Peer Sel ect ><Fai l ur eHandl i ng>cont i nue go- of f l i ne- af t er - t x- expi r y<Ter mi nat eRequest >cont i nue r et r y- af t er - t x- expi r y</ Ter mi nat eRequest ><Updat eRequest >t er mi nat e</ Updat eRequest ></ Fai l ur eHandl i ng><Gr oup>deva- cr edi t </ Gr oup><Mode>Radi us</ Mode><MsccFi nal Uni t Act i on>sessi on onper - mscc- exhaust i on</ MsccFi nal Uni t Act i on><Pendi ngTr af f i cTr eat ment ><For cedReaut h>dr op</ For cedReaut h><NoQuot a>buf f er </ NoQuot a><Quot aExhaust ed>buf f er </ Quot aExhaust ed><Tr i gger >dr op</ Tr i gger ><Val i di t yExpi r ed>dr op</ Val i di t yExpi r ed></ Pendi ngTr af f i cTr eat ment ><Quot a><Request Tr i gger >excl ude packet </ Request Tr i gger >

<Ti meThr eshol d>23 ( per cent ) </ Ti meThr eshol d><Uni t sThr eshol d>45 ( per cent ) </ Uni t sThr eshol d><Val i di t yTi me>6553 sec</ Val i di t yTi me><Vol umeThr eshol d>85 ( per cent ) </ Vol umeThr eshol d></ Quot a><Ser ver Unr eachabl eFai l ur eHandl i ng>cont i nue<Updat eRequest >cont i nue</ Updat eRequest ></ Ser ver Unr eachabl eFai l ur eHandl i ng><Tr i gger Type>cel l i d</ Tr i gger Type></ Cr edi t Cont r ol Gr oups><Cr edi t Cont r ol Gr oups><ApnType>gn</ ApnType><Cr edi t Cont r ol Di amet er ><Di ct i onar y>dcca- cust om8</ Di ct i onar y><Pendi ngTi meout >10 sec</ Pendi ngTi meout ><Sessi onFai l over >Di sabl ed</ Sessi onFai l over ></ Cr edi t Cont r ol Di amet er ><Fai l ur eHandl i ng>t er mi nat e

<Ter mi nat eRequest >r et r y- and- t er mi nat e</ Ter mi nat eRequest ><Updat eRequest >r et r y- and- t er mi nat e</ Updat eRequest ></ Fai l ur eHandl i ng><Gr oup>deva- cr edi t - bug</ Gr oup><Mode>Radi us</ Mode><MsccFi nal Uni t Act i on>cat egor y</ MsccFi nal Uni t Act i on><Pendi ngTr af f i cTr eat ment >

<For cedReaut h>dr op</ For cedReaut h><NoQuot a>dr op</ NoQuot a><Quot aExhaust ed>dr op</ Quot aExhaust ed><Tr i gger >dr op</ Tr i gger ><Val i di t yExpi r ed>dr op</ Val i di t yExpi r ed></ Pendi ngTr af f i cTr eat ment ><Quot a><Hol di ngTi me>N/ A</ Hol di ngTi me><Request Tr i gger >i ncl ude packet </ Request Tr i gger ><Ti meThr eshol d>N/ A</ Ti meThr eshol d><Uni t sThr eshol d>N/ A</ Uni t sThr eshol d><Val i di t yTi me>N/ A</ Val i di t yTi me><Vol umeThr eshol d>N/ A</ Vol umeThr eshol d></ Quot a><Ser ver Unr eachabl eFai l ur eHandl i ng>N/ A<Updat eRequest >N/ A</ Updat eRequest ></ Ser ver Unr eachabl eFai l ur eHandl i ng><Tr i gger Type>N/ A</ Tr i gger Type></ Cr edi t Cont r ol Gr oups><Cr edi t Cont r ol Gr oups><ApnType>gn</ ApnType><Cr edi t Cont r ol Di amet er ><Di ct i onar y>dcca- cust om8</ Di ct i onar y><Pendi ngTi meout >

10 sec</ Pendi ngTi meout ><Sessi onFai l over >Di sabl ed</ Sessi onFai l over ></ Cr edi t Cont r ol Di amet er ><Fai l ur eHandl i ng>cont i nue<Ter mi nat eRequest >cont i nue</ Ter mi nat eRequest ><Updat eRequest >cont i nue</ Updat eRequest ></ Fai l ur eHandl i ng><Gr oup>hi ma</ Gr oup><Mode>Di amet er </ Mode><MsccFi nal Uni t Act i on>cat egor y</ MsccFi nal Uni t Act i on><Pendi ngTr af f i cTr eat ment ><For cedReaut h>pass</ For cedReaut h><NoQuot a>buf f er </ NoQuot a><Quot aExhaust ed>pass</ Quot aExhaust ed><Tr i gger >pass</ Tr i gger ><Val i di t yExpi r ed>pass</ Val i di t yExpi r ed></ Pendi ngTr af f i cTr eat ment ><Quot a><Hol di ngTi me>987937 sec</ Hol di ngTi me><Request Tr i gger >i ncl ude packet </ Request Tr i gger ><Ti meThr eshol d>N/ A</ Ti meThr eshol d>

<Uni t sThr eshol d>100 ( per cent ) </ Uni t sThr eshol d><Val i di t yTi me>235 sec</ Val i di t yTi me><Vol umeThr eshol d>78763 ( byt es) </ Vol umeThr eshol d></ Quot a><Ser ver Unr eachabl eFai l ur eHandl i ng>

cont i nue<Updat eRequest >cont i nue</ Updat eRequest ></ Ser ver Unr eachabl eFai l ur eHandl i ng><Tr i gger Type>l ac</ Tr i gger Type></ Cr edi t Cont r ol Gr oups></ Cr edi t Cont r ol Cont ai ner ><DeepPacket I nspect i on>Enabl ed</ DeepPacket I nspect i on><Dymami cCont ent Fi l t er i ng>Di sabl ed</ Dymami cCont ent Fi l t er i ng><Gr oupof Rul edef Cont ai ner ><Gr oupOf Rul edef ><Appl i cat i onType>Char gi ng</ Appl i cat i onType><Name>Rul edef s1</ Name></ Gr oupOf Rul edef ></ Gr oupof Rul edef Cont ai ner >300 secact i vechar gi nggr oupof -r ul edef s<Pass i veMode>Di sabl ed</ Pass i veMode><Rul ebaseCont ai ner ><Rul ebase><Char gi ngRul eOpt i mi zat i on>Hi gh</ Char gi ngRul eOpt i mi zat i on><Del ayedChar gi ng>Di sabl ed</ Del ayedChar gi ng><Fai r UsageWai ver Per cent age>425</ Fai r UsageWai ver Per cent age>Di sabl ed<P2pDynami cRout i ng>Enabl ed</ P2pDynami cRout i ng><QosRenogot i at i onTi meout >253265 sec

</ QosRenogot i at i onTi meout ><Rt pDynami cRout i ng>Enabl ed</ Rt pDynami cRout i ng><Rul ebaseBi l l i ngAndChar gi ngRecor ds><Edr Supr essZer oByt eRecor ds>Di sabl ed</ Edr Supr essZer oByt eRecor ds></ Rul ebaseBi l l i ngAndChar gi ngRecor ds><Rul ebaseCCAFi el ds><Quot aRet r yTi me>876 sec</ Quot aRet r yTi me><Rul ebaseCCAQuot aHol di ngTi meEnt r i es><Cont ent I d>2147483647</ Cont ent I d><Quot aHol di ngTi me>4000000000 sec</ Quot aHol di ngTi me></ Rul ebaseCCAQuot aHol di ngTi meEnt r i es><Rul ebaseCCATi meDur at i onAl gor i t hmEnt r i es><Al gor i t hmName>Par ki ng Met er </ Al gor i t hmName><Cont ent I d>any</ Cont ent I d><Ti me>4294967295 ( secs) </ Ti me></ Rul ebaseCCATi meDur at i onAl gor i t hmEnt r i es></ Rul ebaseCCAFi el ds><Rul ebaseCont ent Fi l t er i ng/ ><Rul ebaseEGCDRFi el ds><Downl i nkOct et s>100003</ Downl i nkOct et s>

<Rul ebaseEGCDRTar i f f Ti meThr eshol dEnt r i es><Tar i f f Name>Ti me1</ Tar i f f Name><Tar r i f f Ti meVal ue><hr s>23</ hr s><mi ns>59</ mi ns></ Tar r i f f Ti meVal ue></ Rul ebaseEGCDRTar i f f Ti meThr eshol dEnt r i es>

<Thr eshol dI nt er val >40000000 ( secs) </ Thr eshol dI nt er val ><Ti meBasedMet er i ng>Di sabl ed</ Ti meBasedMet er i ng><Tot al Oct et s>5604321</ Tot al Oct et s><Upl i nkOct et s>5000005</ Upl i nkOct et s></ Rul ebaseEGCDRFi el ds><Rul ebaseFl owEndCondi t i ons/ ><Rul ebaseName>hi ma</ Rul ebaseName><Rul ebaseTCPPr oxyMode><Cont ent Fi l t er i ng>Di sabl ed</ Cont ent Fi l t er i ng><DccaEnabl ed>Di sabl ed</ DccaEnabl ed>Enabl ed<Next HopReaddr ess i ng>Di sabl ed</ Next HopReaddr ess i ng><Pr oxyMode>Dynami c</ Pr oxyMode><Xheader I nser t i on>Di sabl ed</ Xheader I nser t i on></ Rul ebaseTCPPr oxyMode><Rul ebaseTet her i ngDet ect i on><OsBasedDet ect i on>Di sabl ed</ OsBasedDet ect i on><Tet her i ngDet ect i on>Enabl ed</ Tet her i ngDet ect i on><UaBasedDet ect i on>Enabl ed</ UaBasedDet ect i on></ Rul ebaseTet her i ngDet ect i on><Rul ebaseUDRFi el ds><Downl i nkOct et s>2000075</ Downl i nkOct et s><Thr eshol dI nt er val >60 sec</ Thr eshol dI nt erval ><Tot al Oct et s>0</ Tot al Oct et s><Udr Tr i gger >Enabl ed</ Udr Tr i gger ><Upl i nkOct et s>584533</ Upl i nkOct et s></ Rul ebaseUDRFi el ds>

<Ur l Bl ackLi st i ngAct i on>t er mi nat e- f l ow</ Ur l Bl ackLi st i ngAct i on><Ur l Bl ackl i st i ngCont ent I d>35</ Ur l Bl ackl i st i ngCont ent I d><XHeader ReEncr ypt i onPer i od>0 mi n</ XHeader ReEncr ypt i onPer i od></ Rul ebase><Rul ebase><Char gi ngRul eOpt i mi zat i on>Hi gh</ Char gi ngRul eOpt i mi zat i on><Del ayedChar gi ng>Di sabl ed</ Del ayedChar gi ng><Fai r UsageWai ver Per cent age>20</ Fai r UsageWai ver Per cent age>Di sabl ed<P2pDynami cRout i ng>Di sabl ed</ P2pDynami cRout i ng><Rt pDynami cRout i ng>Di sabl ed</ Rt pDynami cRout i ng><Rul ebaseBi l l i ngAndChar gi ngRecor ds><Edr Supr essZer oByt eRecor ds>Di sabl ed</ Edr Supr essZer oByt eRecor ds></ Rul ebaseBi l l i ngAndChar gi ngRecor ds><Rul ebaseCCAFi el ds><Quot aRet r yTi me>60 sec</ Quot aRet r yTi me></ Rul ebaseCCAFi el ds><Rul ebaseCont ent Fi l t er i ng/ ><Rul ebaseEGCDRFi el ds><Downl i nkOct et s>0</ Downl i nkOct et s><Thr eshol dI nt er val >0 ( secs) </ Thr eshol dI nt er val >

0 sec</ Thr eshol dI nt erval ><Tot al Oct et s>0</ Tot al Oct et s><Udr Tr i gger >Di sabl ed</ Udr Tr i gger ><Upl i nkOct et s>0</ Upl i nkOct et s></ Rul ebaseUDRFi el ds><Ur l Bl ackLi st i ngAct i on>Not Conf i gur ed</ Ur l Bl ackLi st i ngAct i on>

<XHeader ReEncr ypt i onPer i od>0 mi n</ XHeader ReEncr ypt i onPer i od></ Rul ebase></ Rul ebaseCont ai ner ><Rul edef Cont ai ner ><Rul edef ><Appl i cat i onType>Char gi ng</ Appl i cat i onType><CopyPacket ToLog>Di sabl ed</ CopyPacket ToLog><Mul t i Li neOR>Di sabl ed</ Mul t i Li neOR><Rul eName>t est 1</ Rul eName><Tet her edFl owCheck>Di sabl ed</ Tet her edFl owCheck></ Rul edef ><Rul edef ><Appl i cat i onType>Char gi ng</ Appl i cat i onType><CopyPacket ToLog>Di sabl ed</ CopyPacket ToLog><Mul t i Li neOR>Di sabl ed</ Mul t i Li neOR><Rul eName>r ul e1</ Rul eName><Tet her edFl owCheck>Di sabl ed</ Tet her edFl owCheck></ Rul edef ></ Rul edef Cont ai ner ><Sel ect edChar gi ngRul ebaseFor AVP>Last </ Sel ect edChar gi ngRul ebaseFor AVP><TcpFl owI dl eTi meout >300 sec</ TcpFl owI dl eTi meout ><TcpFl owMappi ngI dl eTi meout >300 sec</ TcpFl owMappi ngI dl eTi meout ><UdpFl owI dl eTi meout >

300 sec</ UdpFl owI dl eTi meout ><UdpFl owMappi ngTi meout >N/ A</ UdpFl owMappi ngTi meout ><Ur l Bl ackLi st i ng>Enabl ed</ Ur l Bl ackLi st i ng><Ur l Bl ackl i st i ngMat chMet hod>exact </ Ur l Bl ackl i st i ngMat chMet hod></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns8: AcsPr of i l e></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns2: ManagedFunct i on></ ns15: I nvent or yUni t >

:::

<! —AAA Gr oup I nvent or y - - >

<ns2: ManagedFunct i oni d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ AAACont ai ner ] [ AAAGr oupCont ai ner ] [ AAAGr oup( Gr oupName=def aul t ) ] }">

<ns2: VsDat aCont ai ner i d=" def aul t - VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">cl asscom. ci sco. pr i me. esb. t gpp. model . common. AAAGr oup</ ns2: vsDat aType><ns2: vsDat aFor mat Vers i on xsi : t ype=" xs: st r i ng"

xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema-i nst ance" >Ci scoSpeci f i cAt t r i but es. aaa. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns4: vsDat aCi scoSpeci f i cMobi l eCont ai ner "xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"><ns10: AAAGr oupi d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ AAACont ai ner ] [ AAAGr oupCont ai ner ] [ AAAGr oup( Gr oupName=def aul t ) ] }"><ns10: at t r i but es><ns10: user Label >def aul t </ ns10: user Label ></ ns10: at t r i but es><ns2: VsDat aCont ai ner i d=" def aul t - VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">AAAGr oup</ ns2: vsDat aType><ns2: vsDat aFor mat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Ci scoSpeci f i cAt t r i but es. aaa. 1.0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns23: AAAGr oupType" xml ns: ns23=" AAAGr oupType"><AAADi amet er Conf i gur at i on><AAADi amet er Account i ngGener al Conf i gur at i on><Di ct i onar y>nasr eq</ Di ct i onar y><Request Ti meout >20 sec</ Request Ti meout ></ AAADi amet er Account i ngGener al Conf i gur at i on><AAADi amet er Account i ngSer ver sEnt r i es><Di amet er Ser ver Host Name>sdf g</ Di amet er Ser ver Host Name><Number Of I nst anceI nDownSt at e>21</ Number Of I nst anceI nDownSt at e>

<Number Of I nst anceI nUpSt at e>0</ Number Of I nst anceI nUpSt at e><Pri or i t y>23</ Pri or i t y></ AAADi amet er Account i ngSer ver sEnt r i es><AAADi amet er Account i ngSer ver sEnt r i es><Di amet er Ser ver Host Name>s123</ Di amet er Ser ver Host Name><Number Of I nst anceI nDownSt at e>21</ Number Of I nst anceI nDownSt at e><Number Of I nst anceI nUpSt at e>0</ Number Of I nst anceI nUpSt at e><Pri or i t y>36</ Pri or i t y></ AAADi amet er Account i ngSer ver sEnt r i es><AAADi amet er Aut hent i cat i onGener al Conf i gur at i on><Di ct i onar y>aaa- cust om11</ Di ct i onar y><Request Ti meout >20 sec</ Request Ti meout ><Redi r ect Host AVP>Di sabl ed</ Redi r ect Host AVP></ AAADi amet er Aut hent i cat i onGener al Conf i gur at i on><AAADi amet er Aut hent i cat i onSer ver sEnt r i es><Di amet er Ser ver Host Name>abcder t </ Di amet er Ser ver Host Name><Number Of I nst anceI nDownSt at e>21</ Number Of I nst anceI nDownSt at e><Number Of I nst anceI nUpSt at e>0</ Number Of I nst anceI nUpSt at e><Pri or i t y>444</ Pr i ori t y></ AAADi amet er Aut hent i cat i onSer ver sEnt r i es><AAADi amet er Aut hent i cat i onSer ver sEnt r i es><Di amet er Ser ver Host Name>ab</ Di amet er Ser ver Host Name>

<Number Of I nst anceI nDownSt at e>21</ Number Of I nst anceI nDownSt at e><Number Of I nst anceI nUpSt at e>0</ Number Of I nst anceI nUpSt at e><Pri or i t y>34</ Pri or i t y></ AAADi amet er Aut hent i cat i onSer ver sEnt r i es><Gr oupName>def aul t </ Gr oupName></ AAADi amet er Conf i gur at i on><AAARadi usConf i gur at i on>

<AAARadi usAccount i ngGener al Conf i gur at i on><Account i ngGTPt r i gger Pol i cy>st andar d</ Account i ngGTPt r i gger Pol i cy><Account i ngRequest MaxRet r i es>5</ Account i ngRequest MaxRet r i es><Account i ngResponseTi meout >3 sec</ Account i ngResponseTi meout ><ApnToBeI ncl uded>Gn</ ApnToBeI ncl uded><Ar chi ve>Enabl ed</ Ar chi ve><Fi r eAndFor get >Di sabl ed</ Fi r eAndFor get ><MaxOut st andi ngAAAMessages>256</ MaxOut st andi ngAAAMessages><MaxPDUSi ze>2048</ MaxPDUSi ze><Remot eAddr ess >Di sabl ed</ Remot eAddr ess><Ser ver Bi l l i ngVer si on>0</ Ser ver Bi l l i ngVer si on><Ser ver DeadTi me>10 mi n</ Ser ver DeadTi me><Ser ver Sel ect i onAl gori t hm>Fi r st - ser ver </ Ser ver Sel ect i onAl gor i t hm></ AAARadi usAccount i ngGener al Conf i gur at i on><AAARadi usAccount i ngKeepAl i veAndDeadSer ver Conf i gur at i on><Cal l i ngSt at i onI D>000000000000000</ Cal l i ngSt at i onI D><Det ect DeadSer ver Consecut i veFai l ur es>4</ Det ect DeadSer ver Consecut i veFai l ur es><Det ect DeadSer ver KeepAl i ve>Di sabl ed</ Det ect DeadSer ver KeepAl i ve><KeepAl i veConsecut i veResponse>1</ KeepAl i veConsecut i veResponse><KeepAl i veI nt er val >30 sec</ KeepAl i veI nt erval ><KeepAl i veMaxRet r i es>3</ KeepAl i veMaxRet r i es><KeepAl i veTi meout >

3 sec</ KeepAl i veTi meout ><User Name>Tes t - User name</ User Name></ AAARadi usAccount i ngKeepAl i veAndDeadSer ver Conf i gur at i on><AAARadi usAut hent i cat i onGener al Conf i gur at i on><ApnToBeI ncl uded>Gn</ ApnToBeI ncl uded><Aut hent i cat eNul l User Name>Enabl ed</ Aut hent i cat eNul l User Name><Aut hent i cat i onRequest MaxRet r i es>5</ Aut hent i cat i onRequest MaxRet r i es><Aut hent i cat i onResponset i meout >3 sec</ Aut hent i cat i onResponset i meout ><MaxOut st andi ngAAAMessages>256</ MaxOut st andi ngAAAMessages><Modi f yNASI P>Di sabl ed</ Modi f yNASI P><Pr obeI nt er val >60 sec</ ProbeI nt er val ><Pr obeMaxRet r i es>5</ Pr obeMaxRet r i es><Pr obeTi meout >3 sec</ Pr obeTi meout ><Ser ver DeadTi me>10 mi n</ Ser ver DeadTi me><Ser ver Sel ect i onAl gori t hm>Fi r st - ser ver </ Ser ver Sel ect i onAl gor i t hm></ AAARadi usAut hent i cat i onGener al Conf i gur at i on>

<AAARadi usAut hent i cat i onKeepAl i veAndDeadSer ver Conf i gur at i on><Cal l i ngSt at i onI D>000000000000000</ Cal l i ngSt at i onI D><Det ect DeadSer ver Consecut i veFai l ur es>4</ Det ect DeadSer ver Consecut i veFai l ur es><Det ect DeadSer ver KeepAl i ve>Di sabl ed</ Det ect DeadSer ver KeepAl i ve><KeepAl i veConsecut i veResponse>1</ KeepAl i veConsecut i veResponse><KeepAl i veI nt er val >

30 sec</ KeepAl i veI nt erval ><KeepAl i veMaxRet r i es>3</ KeepAl i veMaxRet r i es><KeepAl i veTi meout >3 sec</ KeepAl i veTi meout ><User Name>Tes t - User name</ User Name><Al l owAccessRej ect >Di sabl ed</ Al l owAccessRej ect ><Aut hent i cat i onPasswor d>Test - Passwor d</ Aut hent i cat i onPasswor d></ AAARadi usAut hent i cat i onKeepAl i veAndDeadSer ver Conf i gur at i on><AAARadi usChar gi ngGener al Conf i gur at i on><Account i ngSer ver Sel ect i onAl gori t hm>Fi r st -ser ver </ Account i ngSer ver Sel ect i onAl gori t hm><Aut hent i cat i onSer ver Sel ect i onAl gor i t hm>Fi r st -ser ver </ Aut hent i cat i onSer ver Sel ect i onAl gor i t hm><Char gi ngDet ect DeadSer ver Consecut i veFai l ur es>4</ Char gi ngDet ect DeadSer ver Consecut i veFai l ur es><Maxi mumOut st andi ngAAAMessages>256</ Maxi mumOut st andi ngAAAMessages><Ser ver DeadTi me>10 mi n</ Ser ver DeadTi me><Ser ver MaxRet r i es>5</ Ser ver MaxRet r i es><Ser ver ResponseTi meout >3 sec</ Ser ver ResponseTi meout ></ AAARadi usChar gi ngGener al Conf i gur at i on><AAARadi usChar gi ngTr i gger sConf i gur at i on><MsTi mezoneChangeTr i gger >Enabl ed</ MsTi mezoneChangeTr i gger ><Qual i t yOf Ser vi ceChangeTr i gger >Enabl ed</ Qual i t yOf Ser vi ceChangeTr i gger >

<Radi oAccessTechnol ogyChangeTr i gger >Enabl ed</ Radi oAccessTechnol ogyChangeTri gger ><Rout i ngAr eaI nf or mat i onChangeTr i gger >Enabl ed</ Rout i ngAr eaI nf or mat i onChange

Tr i gger ><Ser vi ngNodeChangeTr i gger >Enabl ed</ Ser vi ngNodeChangeTr i gger ><User Locat i onI nf or mat i onChangeTr i gger >Enabl ed</ User Locat i onI nf or mat i onChangeTr i gger ></ AAARadi usChar gi ngTr i gger sConf i gur at i on><Al l owAccount i ngDown>Enabl ed</ Al l owAccount i ngDown><Al l owAut hent i cat i onDown>Di sabl ed</ Al l owAut hent i cat i onDown><Aut hent i cat orVal i dat i on>Enabl ed</ Aut hent i cat orVal i dat i on><Di ct i onar y>st arent - vsa1</ Di ct i onar y><Gr oupName>def aul t </ Gr oupName></ AAARadi usConf i gur at i on></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns10: AAAGr oup></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns2: ManagedFunct i on></ ns15: I nvent or yUni t >.

.

.

.

<! —AAA Di amet er Endpoi nt I nvent or y - - >

<ns2: ManagedFunct i on

i d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ AAACont ai ner ] [ AAADi amet er Endpoi nt Cont ai ner ] [ AAADi amet er Endpoi nt ( Endpoi nt Name=endpoi nt 2) ] }"><ns2: VsDat aCont ai ner i d=" endpoi nt 2- VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">cl asscom. ci sco. pr i me. esb. t gpp. model . common. AAADi amet er Endpoi nt </ ns2: vsDat aType><ns2: vsDat aFormat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema-i nst ance" >Ci scoSpeci f i cAt t r i but es. aaa. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns4: vsDat aCi scoSpeci f i cMobi l eCont ai ner "xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"><ns11: AAADi amet er Endpoi nti d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ AAACont ai ner ] [ AAADi amet er Endpoi nt Cont ai ner ] [ AAADi amet er Endpoi nt ( Endpoi nt Name=endpoi nt 2) ] }"><ns11: at t r i but es><ns11: user Label >endpoi nt 2</ ns11: user Label ></ ns11: at t r i but es><ns2: VsDat aCont ai ner i d=" endpoi nt 2- VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">AAADi amet er Endpoi nt </ ns2: vsDataType><ns2: vsDat aFormat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Ci scoSpeci f i cAt t r i but es. aaa. 1.

0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns23: AAADi amet er Endpoi nt Type"xml ns: ns23=" AAADi amet er Endpoi nt Type"><AAADi amet er Rout eEnt r i es><Appl i cat i on>CC Not Conf i gur ed</ Appl i cat i on><Or i gi n>*</ Or i gi n><Peer Host Name>*</ Peer Hos t Name><Peer Name>peer 2</ Peer Name><Peer Real m>st ar ent net wor ks. com</ Peer Real m><Rout eType>St at i c</ Rout eType><Rout eWei ght >10</ Rout eWei ght ></ AAADi amet er Rout eEnt r i es><AAADi amet er Rout eEnt r i es><Appl i cat i on>CC Not Conf i gur ed</ Appl i cat i on><Or i gi n>*</ Or i gi n><Peer Host Name>peer 2</ Peer Hos t Name><Peer Name>peer 2</ Peer Name><Peer Real m>st ar ent net wor ks. com</ Peer Real m><Rout eType>St at i c</ Rout eType><Rout eWei ght >10</ Rout eWei ght ></ AAADi amet er Rout eEnt r i es><AAADi amet er Rout eEnt r i es><Appl i cat i on>CC Not Conf i gur ed</ Appl i cat i on><Or i gi n>*</ Or i gi n><Peer Host Name>*</ Peer Hos t Name>

<AAADi amet er Rout eHeal t hSt at usEnt r i es><Avai l abl eCount >21</ Avai l abl eCount ><Fai l edCount >0</ Fai l edCount ><Or i gi nCount >21</ Or i gi nCount ><Peer Hos t Name></ Peer Hos t Name><Peer Name>peer - 5</ Peer Name></ AAADi amet er Rout eHeal t hSt at usEnt r i es>

<AAADi amet er Rout eHeal t hSt at usEnt r i es><Avai l abl eCount >21</ Avai l abl eCount ><Fai l edCount >0</ Fai l edCount ><Or i gi nCount >21</ Or i gi nCount ><Peer Host Name>peer - 5</ Peer Host Name><Peer Name>peer - 5</ Peer Name></ AAADi amet er Rout eHeal t hSt at usEnt r i es></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns11: AAADi amet er Endpoi nt ></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns2: ManagedFunct i on></ ns15: I nvent or yUni t >

.

.

.

.<! —GTPP I nvent or y - - >

<ns2: ManagedFunct i oni d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=hai m) ] [ Mobi l e] [ GTPPGr oupCont ai ner ] [ GTPPGr oup( Gr oupName=def aul t ) ] }"><ns2: VsDat aCont ai ner i d=" def aul t - VsDat a1" ><ns2: at t r i but es>

<ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">cl asscom. ci sco. pr i me. esb. t gpp. model . common. Gt ppPr of i l e</ ns2: vsDat aType><ns2: vsDat aFormat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema-i nst ance" >Ci scoSpeci f i cAt t r i but es. gt pp. 1. 0</ ns2: vsDat aFormat Ver si on><ns2: vsDat a xsi : t ype=" ns4: vsDat aCi scoSpeci f i cMobi l eCont ai ner "xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"><ns9: gt ppPr of i l ei d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=hai m) ] [ Mobi l e] [ GTPPGr oupCont ai ner ] [ GTPPGr oup( Gr oupName=def aul t ) ] }"><ns9: at t r i but es><ns9: user Label >def aul t </ ns9: user Label ></ ns9: at t r i but es><ns2: VsDat aCont ai ner i d=" def aul t - VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Gt ppPr of i l e</ ns2: vsDat aType><ns2: vsDat aFormat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Ci scoSpeci f i cAt t r i but es. gt pp. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns23: GTPPGr oupType" xml ns: ns23=" GTPPGr oupType"><Account i ngSer ver Fai l ur eDet ect i on>

<DeadSer ver Suppr ess CDRs>Di sabl ed</ DeadSer ver Suppr ess CDRs><DeadTi me>120 sec</ DeadTi me><Det ect DeadSer ver Consecut i veFai l ur es>0</ Det ect DeadSer ver Consecut i veFai l ur es><Dupl i cat eHol dTi meMi nut es>

60 mi n</ Dupl i cat eHol dTi meMi nut es><EchoMaxRet r i es>4</ EchoMaxRet r i es><EchoTi meout >60 sec</ EchoTi meout ><Redi r ect i onAl l owed>yes</ Redi r ect i onAl l owed></ Account i ngSer ver Fai l ur eDet ect i on><CDRAt t r i but esI ndi cat or ><ApnPr esent >Enabl ed</ ApnPr esent ><Camel I nf o>Di sabl ed</ Camel I nf o><Cel l PLMNI d>Enabl ed</ Cel l PLMNI d><Char gi ngChar act er i st i cSel ect i onModePr esent >Enabl ed</ Char gi ngChar act er i st icSel ect i onModePr esent ><Dest i nat i onNumber >Enabl ed</ Dest i nat i onNumber ><Di agnost i csPr esent >Di sabl ed</ Di agnost i csPr esent ><Dur at i on>Di sabl ed</ Dur at i on><Dynami cFl agPr esent >Enabl ed</ Dynami cFl agPr esent >Enabl ed<Li st Of Ser vi ceDat aPr esent >Enabl ed</ Li st Of Ser vi ceDat aPr esent ><Local RecSeqNumPr esent >Di sabl ed</ Local RecSeqNumPr esent ><Msi sdn>Enabl ed</ Msi sdn><NodeI DPr esent >Enabl ed</ NodeI DPr esent ><PdnConnect i onI DPr esent >Enabl ed</ PdnConnect i onI DPr esent ><PdpAddr essPr esent >Enabl ed</ PdpAddr essPr esent ><PdpTypePr esent >Enabl ed</ PdpTypePr esent ><PgwPLMNI DPr esent >Enabl ed</ PgwPLMNI DPr esent ><Pl mnI DPr esent >Enabl ed</ Pl mnI DPr esent ><Rat >Di sabl ed</ Rat >

<Rat Pr esent >Enabl ed</ Rat Pr esent ><Recor di ngEnt i t y>Enabl ed</ Recor di ngEnt i t y><Ser vedMNAI Pr esent >Enabl ed</ Ser vedMNAI Pr esent ><Ser vedPDPPDNAddr essExt ensi onPr esent >Di sabl ed</ Ser vedPDPPDNAddr essExt ensi onPr esent ><Ser vi ceCent r e>Enabl ed</ Ser vi ceCent r e><St ar t Ti mePr esent >Enabl ed</ St ar t Ti mePr esent ><St opTi mePr esent >Enabl ed</ St opTi mePr esent ><User Locat i onI nf or mat i onPr esent >Enabl ed</ User Locat i onI nf or mat i onPr esent ></ CDRAt t r i but esI ndi cat or ><CDRTr i gger s><Cel l Updat e>Di sabl ed</ Cel l Updat e><Di r ect Tunnel >Enabl ed</ Di r ect Tunnel ><Egcdr MaxLosdvLi mi t >Di sabl ed</ Egcdr MaxLosdvLi mi t >Enabl edDi sabl ed<MsTi mezoneChange>Enabl ed</ MsTi mezoneChange><OnRATChangeGener at e>CDR</ OnRATChangeGener at e><Pl mnI DChange>Di sabl ed</ Pl mnI DChange><QosChange>Enabl ed</ QosChange><Rat Change>Enabl ed</ Rat Change><Rout i ngAr eaUpdat e>Enabl ed</ Rout i ngAr eaUpdat e><Ser vi ngNodeChangeLi mi t >Enabl ed</ Ser vi ngNodeChangeLi mi t ><Tar i f f Ti meChange>Enabl ed</ Tar i f f Ti meChange>

<Ti meLi mi t >Enabl ed</ Ti meLi mi t ><Vol umeLi mi t >Enabl ed</ Vol umeLi mi t ></ CDRTr i gger s><Cdr MaxRet r i es>4</ Cdr MaxRet r i es><Cdr St or ageMode>r emot e</ Cdr St or ageMode><Cdr Ti meout >20 sec

</ Cdr Ti meout ><Char gi ngAgent ><Char gi ngAgent Addr ess>0. 0. 0. 0</ Char gi ngAgent Addr ess></ Char gi ngAgent ><Dat aReqSt ar t SeqNum>0</ Dat aReqSt ar t SeqNum><Di ct i onar y>st andar d</ Di ct i onar y><EGCDRDat aGener at i onConf i gur at i on><Cl osi ngCauseUni que>no</ Cl osi ngCauseUni que><Del et eSer vi ceThr eshol ds>no</ Del et eSer vi ceThr eshol ds>no<LosdvMaxCont ai ner s>10</ LosdvMaxCont ai ner s><Lot dvMaxCont ai ner s>8</ Lot dvMaxCont ai ner s><Ser vi ceI dl eTi meout >0 sec</ Ser vi ceI dl eTi meout ><Ser vi ceI nt er val >N/ A</ Ser vi ceI nt er val ></ EGCDRDat aGener at i onConf i gur at i on><Gr oupName>def aul t </ Gr oupName><Local St or age><Fi l eCompr essi on>none</ Fi l eCompr essi on><Fi l eFor mat >cust om1</ Fi l eFor mat ><Fi l eRot at i onCDRCount >10000</ Fi l eRot at i onCDRCount ><Fi l eRot at i onTi meI nt er val >3600 sec</ Fi l eRot at i onTi meI nt er val >

<Fi l eRot at i onVol umeLi mi t >4</ Fi l eRot at i onVol umeLi mi t ><For ceFi l eRot at i onByTi meI nt erval >Di sabl ed</ For ceFi l eRot at i onByTi meI nt er val><Pur gePr ocessedFi l es>Di sabl ed</ Pur gePr ocessedFi l es></ Local St or age><MBMSCDRTr i gger s><Bucket s>4</ Bucket s>N/ A</ MBMSCDRTr i gger s><MaxCDRSi nMsg>1</ MaxCDRSi nMsg><MaxCDRSi ze>65400</ MaxCDRSi ze><MaxCDRsWai t Ti me>N/ A</ MaxCDRsWai t Ti me><Recover Fi l eSeqNum>No</ Recover Fi l eSeqNum><Sour cePor t Val i dat i on>Enabl ed</ Sour cePor t Val i dat i on><St ar t Fi l eSeqNum>1</ St ar t Fi l eSeqNum><St or ageSer ver ><St or ageSer ver Addr ess>6. 6. 6. 6</ St or ageSer ver Addr ess><St or ageSer ver MaxRet r i es>2</ St or ageSer ver MaxRet r i es><St or ageSer ver Por t >44</ St or ageSer ver Por t >

<St or ageSer ver Ti meout >30 sec</ St or ageSer ver Ti meout ></ St or ageSer ver ></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner >

</ ns9: gt ppPr of i l e></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns2: ManagedFunct i on></ ns15: I nvent or yUni t >

.

.

.

.<! —Oper at or Pol i cy I nvent or y - - >

<ns2: ManagedFunct i oni d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ Mobi l e] [ Pol i cyCont ai ner ] [ Oper at or Pol i cyCont ai ner ] [ Oper at or Pol i cy(Oper at or Pol i cyName=t 4demo) ] }"><ns2: VsDat aCont ai ner i d=" t 4demo- VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">cl asscom. ci sco. pr i me. esb. t gpp. model . common. Pol i cyPr of i l e</ ns2: vsDat aType><ns2: vsDat aFormat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema"xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema-i nst ance">Ci scoSpeci f i cAt t r i but es. pol i cy. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns4: vsDat aCi scoSpeci f i cMobi l eCont ai ner "xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance">

<ns12: Pol i cyPr of i l ei d=" {[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext ( Cont ext Name=l ocal ) ] [ Mobi l e] [ Pol i cyCont ai ner ] [ Oper at or Pol i cyCont ai ner ] [ Oper at or Pol i cy(Oper at or Pol i cyName=t 4demo) ] }"><ns12: at t r i but es><ns12: user Label >t 4demo</ ns12: user Label ></ ns12: at t r i but es><ns2: VsDat aCont ai ner i d=" t 4demo- VsDat a1" ><ns2: at t r i but es><ns2: vsDat aType xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. or g/ 2001/ XMLSchema">Pol i cyPr of i l e</ ns2: vsDat aType><ns2: vsDat aFormat Vers i on xsi : t ype=" xs: st r i ng"xml ns: xs=" ht t p: / / www. w3. org/ 2001/ XMLSchema" >Ci scoSpeci f i cAt t r i but es. pol i cy. 1. 0</ ns2: vsDat aFor mat Ver si on><ns2: vsDat a xsi : t ype=" ns23: Oper at or Pol i cyType"xml ns: ns23=" Oper at or Pol i cyType"><ApnRemapTabl eName>{[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Context ( Cont ext Name=l ocal ) ] [ Mobi l e] [ Prof i l esCont ai ner ] [ APNRemapCont ai ner] [ APNRemap( ApnRemapName=t 4demo) ] }</ ApnRemapTabl eName><Cal l Cont r ol Pr of i l eName>t 4demo</ Cal l Cont r ol Pr of i l eName><Def aul t APNPr of i l eName>{[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [Cont ext ( Cont ext Name=l ocal ) ] [ Mobi l e] [ Prof i l esCont ai ner ] [ APNPr of i l eCont ai ner] [ APNPr of i l e( ApnPr of i l eName=t 4demo) ] }</ Def aul t APNPr of i l eName><Oper at or Pol i cyAPNEnt r i es>

<Net wor kI dent i f i er >t 4demo</ Net wor kI dent i f i er ><Net wor kI dent i f i er APNPr of i l eName>{[ ManagedEl ement ( Key=Si mul at edASR5K) ] [ Logi cal Root ] [ Cont ext( Cont extName=l ocal ) ] [ Mobi l e] [ Pr of i l esCont ai ner ] [ APNPr of i leCont ai ner ] [ APNProf i l e( ApnPr of i l eName=t 4demo) ] }</ Net wor kI dent i f i er APNPr of il eName><Oper at or I dent i f i er > </ Oper at or I dent i f i er ></ Oper at or Pol i cyAPNEnt r i es>

<Oper at or Pol i cyDescr i pt i on>" demo"</ Oper at or Pol i cyDescr i pt i on><Oper at or Pol i cyI MEI RangesEnt r i es><Pr of i l eName>t 4demo</ Pr of i l eName><St ar t Range>120</ St ar t Range><ToRange>125</ ToRange></ Oper at or Pol i cyI MEI RangesEnt r i es><Oper at or Pol i cyName>t 4demo</ Oper at or Pol i cyName></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns12: Pol i cyPr of i l e></ ns2: vsDat a></ ns2: at t r i but es></ ns2: VsDat aCont ai ner ></ ns2: ManagedFunct i on></ ns15: I nvent or yUni t >

.

.

.

.





11.3 3GPP Detailed Inventory Information

This section includes:• Physical Inventory attributes• Logical Inventory attributes

11.3.1 Physical Inventory attributes

This section lists the physical inventory attributes for:• Managed Element • Chassis • Card • Slot • Port • Sub-Port • Power • Fan

Table 9-1: Physical Inventory Attributes for Managed Element

Attr ibute name

3GPPPrescribedSupportQualifier

3GPPPrescribedRead Qualif ier

3GPPPrescribedWrite Qualifier

Id M M -

inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M -

relatedFunction O M -





Table 9-2: Physical Inventory Attribute for Chassis

Attr ibute name


3GPPPrescribedRead Qualifi er


Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M -

Table 9-3: Physical Inventory Attribute for Card

Attr ibute name




Id M M - inventoryUnitType M M -

vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M -





Table 9-4: Physical Inventory Attribute for Slot

Attr ibute name




Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M -

manufacturerData O M - relatedFunction O M -

Table 9-5: Physical Inventory Attribute for Port

Attr ibute name










Table 9-6: Physical Inventory Attribute for Sub-port

Attr ibute name






Table 9-7: Physical Inventory Attribute for Power

Attr ibute name










Table 9-8: Physical Inventory Attribute for Fan

Attr ibute name






11.3.2 Logical Inventory attributes

This section lists the logical inventory attributes for:• PGW

o Logical Inventory Attribute for PGWo Vendor Extensions for PGW

• SGWo Logical Inventory Attribute for SGWo Vendor Extensions for SGW

• APNo Logical Inventory Attribute for APNo Vendor Extension for APN

• SAEGWo Logical Inventory Attribute for SAEGWo Vendor Extensions for SAEGW

• GGSNo Logical Inventory Attribute for GGSNo Vendor Extension for GGSN

• ACSo Logical Inventory Attribute for ACSo Vendor Extension for ACS

• AAAo Logical Inventory Attribute for AAAo Vendor Extension for AAAGroup

• GTPP





o Logical Inventory Attribute for GTPPo Vendor Extension for GTPP

• Operator Policyo Logical Inventory Attribute for Operator Policyo Vendor Extension for Operator Policy

11.3.2.1 Logical Inventory Attribute for PGW

Table 9-9: Logical Attribute for PGW

11.3.2.1.1 Vendor Extensions for PGW• PgwStatus •

NewcallPolicy • EgtpService • LmaService • GgsnService • QciQosMappingTable • SessionDeleteDelayTimeout • SaeGwService

Attr ibute name





vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id PGWFunction Id userLabel linkList





• PgwStatus

11.3.2.2 Logical Inventory Attribute for SGW

Table 9-10: Logical Attribute for SGW

Attr ibute name




Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id ServingGWFunction userLabel PLMNIdList TACList

11.3.2.2.1 Vendor Extensions for SGW• AccountingContext• AccountingGtppGroup• AccountingMode• EgressProtocol • EgressContext • EgressMagService • ImsAuthorizationService • AccountingPolicy • ServiceStatus • SaeGwService • NewcallPolicy





11.3.2.3 Logical Inventory Attribute for APN

Table 9-11: Logical Attribute for APN

Attr ibute name



3GPPPrescribedWriteQualifier

Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M -

dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id APN Id userLabel

11.3.2.3.1 Vendor Extension for APN• AccountingMode • SelectionMode • L3toL2AddressPolicy • AllocationType • DnsConfiguration • Id • PrimaryDnsAddress • Secondarty DnsAddress • IpHeaderCompression • PDP • Id • PdpType • PrimaryContexts • TotoalContexts • RadiusServerConfiguration • Id





• ApnlpParameterso ido Access Groupo Local Addresso NextHopGatewayAddress

o

OutAccessGroupo DiscardEnabled• ApnChargingCharacteristics

o Ido AllBitBehavioro HomeBitBehavioro RoamingBitBehavioro VisitingBitBehavioro RadiusReturnedo AllProfileo HomeProfileo RoamingProfileo VisitingProfileo UseGgsn

• GSMQoS o Ido ResidualBERCodeo SDUErrorRatioCode

• NewcallPolicy o MobileIP

Id MnAAARemovalIndication MnHaHashAlgorithm

MnHaSharedKey MnHaSPI AlternateHA HA

• APNIPv6 o Ido AddressPrefixPoolNameo DNSPrimaryAddresso DNSSecondaryAddresso EgressAddressFilteringo InboundAccessGroupName

o

OutboundAccessGroupNameo InitialRouterAdvertisementIntervalo InitialRouterAdvertisementNumber

• VirtualAPNs o ido RuleDefinitiono RuleType





o QciToDscpo QciArpToDscp

• Gtpp o Ido AccountingContext

o

AccountingContextNameo Groupo GroupTypeo GroupXid

• APNQoSDownlinkTrafficPolicingEntries o IDo BurstSizeAutoReadjusto BurstSizeAutoReadjustDurationo CommittedDataRateo ExceedActiono GuaranteedBurstSizeo NegotiateLimito PeakBurstSizeo PeakDataRateo QciNameo RateLimito ViolateAction

• APNQoSUplinkTrafficPolicingEntries o IDo BurstSizeAutoReadjusto BurstSizeAutoReadjustDurationo CommittedDataRateo ExceedAction

o GuaranteedBurstSizeo NegotiateLimito PeakBurstSizeo PeakDataRateo QciNameo RateLimito ViolateActiono ActiveChargingBandwidthPolicyo ActiveChargingRulebaseo ContentFilteringCategoryPolicyIdo CreditControlGroup





11.3.2.4 Logical Inventory Attribute for SAEGW

Table 9-12: Logical Attribute for SAEGW

Attr ibute name





dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id SAEGWFunction Id userLabel

11.3.2.4.1 Vendor Extensions for SAEGW• SgwService• PgwService

11.3.2.5 Logical Inventory Attribute for GGSN

Table 9-13: Logical Attribute for GGSN

Attr ibute name

3GPPPrescribed

SupportQualifier

3GPPPrescribed

ReadQualifier

3GPPPrescribed

WriteQualifier

Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M -





o Ido CcBehaviorNoRecordso Intervalso Profileso Tariffs

• IGGSNChargingCharacteristicsIntervalTableEntry o Ido ProfileIdo Intervalo DownLinko UpLinko Totalo Sgsns

• IGGSNChargingCharacteristicsProfilesTableEntry o Ido Profileo Bucketso Prepaido DownLinko UpLinko Total

• IGGSNChargingCharacteristicsTariffTableEntry o Ido ProfileIdo Time1o Time2o Time3o Time4

o Time5o Time6

• Sgsns o Ido IPAddresso SubnetMasko PLMNIdo RejectForeignSubscriber

• PLMNForeign o RATTypeo Description





11.3.2.6 Logical Inventory Attribute for ACS

Table 9-14: Logical Attribute for ACS

11.3.2.6.1 Vendor Extension for ACSThe vendor extension information is given here

• ActiveChargingFairUsageo CpuThresholdPercento DeactivateMarginPercento ThresholdPercent

• ActiveChargingServiceRedirectUserAgentEntrieso userAgent

• AlgMediaIdleTimeout• BandwidthPolicyContainer

o BandwidthPolicy BandwidthPolicyFlowLimitEntries

o BandwidthIDo GroupID

Attr ibute name





dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id AcsProfileId userLabel





• ContentFiltering• ContentFilteringCategoriesContainer

o ContentFilteringCategory CategoryPolicy

o ContentCategory

o ContentFailureActiono ContentInserto ContentPriorityo ContentRedirecto ContentReplyCodeo EdrFileFormat

ContentFilteringPolicyId EdrFile FailureAction

• ContentFilteringMatchMethod•

CreditControlContainero CreditControlGroups ApnType CreditControlDiameter

o Dictionaryo EndPointRealmo EndpointNameo PendingTimeouto SessionFailover

DiameterPeerSelecto ImsiEndValueo ImsiRangeModeo ImsiStartValueo Peero Realmo SecondaryPeero SecondaryRealm

FailureHandlingo InitialRequesto TerminateRequesto UpdateRequest

Group Mode MsccFinalUnitAction PendingTrafficTreatment

o ForcedReautho NoQuotao QuotaExhausted





o Triggero ValidityExpired

Quotao HoldingTimeo RequestTrigger

o TimeThresholdo UnitsThresholdo ValidityTimeo VolumeThreshold

ServerUnreachableFailureHandlingo InitialRequesto UpdateRequest

TriggerType• DeepPacketInspection• DymamicContentFiltering•

GroupofRuledefContainero GroupOfRuledef ApplicationType DynamicCommandContentFilteringPolicyId GroupOfRuledefPriorityEntries

o Priorityo RuledefNameo RuledefValue

Name• IcmpFlowIdleTimeout• InterpretationOfChargingRulebaseName• PassiveMode• RulebaseContainer

o Rulebase ChargeMidSessionPackets ChargeSeparateFromApplication ChargingRuleOptimization DefaultBandwidthPolicyName DelayedCharging FairUsageWaiverPercentage FlowErrorChargingAction

IgnorePortInapplicationHeader LimitForTCPFlows LimitForTotalFlows LimitforNonTCPFlows P2pDynamicRouting PrefixedUrlForPreprocessingGroupName QosRenogotiationTimeout





RtpDynamicRouting RuleBaseRoutingActionPrioritiesEntries

o Analyzero Descriptiono Priority

o RoutingRuledef RulebaseBillingAndChargingRecordso BillingFormatEGCDRso BillingFormatRadiuso BillingFormatRfo BillingFormatUDRso EdrSupressZeroByteRecordso EdrTransactionCompleteProtocolo FailureHandlingUDRso FailureHandlingUdrFormatName

o TransactionCompleteChargingEDRFormat

o TransactionCompleteReportingERFormato UDRFormatname

RulebaseCCAFieldso DiameterRequestedServiceSpecificUnitso DiameterRequestedServiceUnitTimeo DiameterRequestedServiceVolumeInputOctetso DiameterRequestedServiceVolumeOutputOctetso DiameterRequestedServiceVolumeTotalOctetso QuotaRetryTimeo RadiusChargingContext

o RadiusChargingGroupo RadiusInterimIntervalo RulebaseCCAQuotaHoldingTimeEntries

o ContentIdo QuotaHoldingTime

o RulebaseCCATimeDurationAlgorithmEntrieso AlgorithmNameo ContentIdo Time

RulebaseChargingActionPrioritiesEntries

o

ChargingActionNameo Descriptiono Priorityo Ruledefo TimeDefo Type

RulebaseContentFilteringo ContentFilteringFlowAnyError





o ContentFilteringGroupo ContentFilteringModeo ContentFilteringPolicy

RulebaseEGCDRFieldso DownlinkOctets

o InactivityTimeo ParkingMeterTimeouto RulebaseEGCDRTariffTimeThresholdEntries

o TariffNameo TarriffTimeValue

o ThresholdIntervalo TimeBasedMeteringo TimeBasedMeteringAlgorithmo TimePeriodo TotalOctets

o UplinkOctets

RulebaseFlowEndConditionso ChargingEDRo ContentFilteringEDRo FlowOverflowEDRo HagrEDRo HandOffEDRo NormalEndSignallingEDRo ReportingEDRo SessionEndEDRo TimeoutEDR

o UrlBlacklistingEDR RulebaseName RulebasePostProcessingActionPrioritiesEntries

o ChargingActiono Descriptiono Priorityo RuledefNameo RuledefValueo Type

RulebaseTCPProxyMode

o

ContentFilteringo DccaEnabledo IpReaddressingo NextHopReaddressingo ProxyModeo XheaderInsertion

RulebaseTetheringDetection





o OsBasedDetectiono TetheringDetectiono UaBasedDetection

RulebaseUDRFieldso DownlinkOctets

o ThresholdIntervalo TotalOctetso UdrTriggero UplinkOctets

UrlBlackListingAction UrlBlacklistingContentId XHeaderCertificateName XHeaderReEncryptionPeriod

• RuledefContainero Ruledef

ApplicationType CopyPacketToLog

MultiLineOR RuleName R uledefProtocolConfigurationEntries

o Fieldso Operatoro Value

TetheredFlowCheck• SelectedChargingRulebaseForAVP• TcpFlowIdleTimeout• TcpFlowMappingIdleTimeout• UdpFlowIdleTimeout• UdpFlowMappingTimeout• UrlBlackListing• UrlBlacklistingMatchMethod

11.3.2.7 Logical Inventory Attribute for AAAThe Logical inventory Attributes for AAAGroup and AAADiameterEndpoint are givenbelow

A. AAAGroup

Table 11-25: Attribute for AAAGroup

The Logical inventory Attributes for AAAGroup is given below





Table 9-15: Attribute for AAA Group

11.3.2.7.1 Vendor Extension for AAAGroupA. The vendor extension information of AAAGroup is given here

• AAADiameterConfigurationo AAADiameterAccountingGeneralConfiguration

Dictionary EndPointName MaxRetries MaxTransmissions RequestTimeout

o AAADiameterAccountingServersEntries

DiameterServerHostName NumberOfInstanceInDownState NumberOfInstanceInUpState Priority

o AAADiameterAuthenticationGeneralConfiguration Dictionary EndPointName

Attr ibute name





manufacturerData O M - relatedFunction O M - ManagedFunction Id AAAGroupId userLabel





MaxRetries MaxTransmissions RequestTimeout RedirectHostAVP

o AAADiameterAuthenticationServersEntries

DiameterServerHostName NumberOfInstanceInDownState NumberOfInstanceInUpState Priority

o GroupName• AAARadiusConfiguration

o AAARadiusAccountingGeneralConfiguration AccountingGTPtriggerPolicy AccountingRequestMaxRetries AccountingRequestMaxTransmissions

AccountingResponseTimeout ApnToBeIncluded Archive FireAndForget InterimAccountingDownlinkVolume InterimAccountingInterval InterimAccountingTotalVolume InterimAccountingUplinkVolume MaxOutstandingAAAMessages MaxPDUSize RemoteAddress

ServerBillingVersion ServerDeadTime ServerSelectionAlgorithm

o AAARadiusAccountingKeepAliveAndDeadServerConfiguration CallingStationID DetectDeadServerConsecutiveFailures DetectDeadServerKeepAlive DetectDeadServerResponseTimeout KeepAliveConsecutiveResponse KeepAliveInterval

KeepAliveMaxRetries KeepAliveTimeout UserName FramedIPAddress

o AAARadiusAccountingServersEntries AdministrativeStatus KeepAliveRepresentativeGroup





OperationalState Preference RequestTimeout RetainAdministrativeStatusAfterReboot RetransmitCount

RetransmitEnabled Role ServerIP ServerPort

o AAARadiusAuthenticationGeneralConfiguration ApnToBeIncluded AuthenticateNullUserName AuthenticationRequestMaxRetries AuthenticationRequestMaxTransmissions AuthenticationResponsetimeout MaxOutstandingAAAMessages ModifyNASIP ProbeInterval ProbeMaxRetries ProbeTimeout ServerDeadTime ServerSelectionAlgorithm

o AAARadiusAuthenticationKeepAliveAndDeadServerConfiguration CallingStationID DetectDeadServerConsecutiveFailures DetectDeadServerKeepAlive

DetectDeadServerResponseTimeout KeepAliveConsecutiveResponse KeepAliveInterval KeepAliveMaxRetries KeepAliveTimeout UserName AllowAccessReject AuthenticationPassword

o AAARadiusAuthenticationServersEntries AdministrativeStatus

KeepAliveRepresentativeGroup OperationalState Preference RequestTimeout RetainAdministrativeStatusAfterReboot RetransmitCount RetransmitEnabled





B. The vendor extension information of AAADiameterEndpoint is given here

• AAADiameterPeersEntrieso LocalHostName

o LocalIPAddresso LocalPorto LocalRealmo PeerHostNameo PeerIPAddresso PeerPorto PeerRealmo SecondaryLocalIPAddresso SecondaryLocalPorto State

o

TaskName• AAADiameterRouteEntrieso Applicationo Origino PeerHostNameo PeerNameo PeerRealmo RouteExpiryTimeOuto RouteTypeo RouteWeight

• AAADiameterRouteHealthStatusEntrieso AvailableCounto FailedCounto OriginCounto PeerHostNameo PeerName

• AAARealmTaskManagerEntrieso ApplicationNameo CardNumbero CpuNumbero TaskName

• OriginRealmName





11.3.2.8 Logical Inventory Attribute for GTPP

The Logical inventory Attributes for GTPP is given below

Table 9-17: Attribute for GTPP

11.3.2.8.1 Vendor Extension for GTPPThe vendor extension information is given here

• AccountingServero ContextNameo Groupo Porto PrimaryAccountingServerAddress

o Priorityo State

• AccountingServerFailureDetectiono DeadServerSuppressCDRso DeadTimeo DetectDeadServerConsecutiveFailureso DuplicateHoldTimeMinutes

Attr ibute name




Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id GTPPProfileId userLabel





o EchoMaxRetrieso EchoTimeouto RedirectionAllowed

• CDRAttributesIndicatoro ApnPresent

o CamelInfoo CellPLMNIdo ChargingCharacteristicSelectionModePresento DestinationNumbero DiagnosticsPresento Durationo DynamicFlagPresento ImeiPresento ListOfServiceDataPresento LocalRecSeqNumPresent

o

Msisdno NodeIDPresento NodeIDSuffixo PdnConnectionIDPresento PdpAddressPresento PdpTypePresento PgwPLMNIDPresento PlmnIDPresento PlmnIDUnknownUseo Rato RatPresent

o RecordingEntityo ServedMNAIPresento ServedPDPPDNAddressExtensionPresento ServiceCentreo StartTimePresento StopTimePresento UserLocationInformationPresent

• CDRTriggerso CellUpdateo DirectTunnel

o EgcdrMaxLosdvLimito InterPLMNSGSNChangeo IntraSGSNGroupChangeo MsTimezoneChangeo OnRATChangeGenerateo PlmnIDChangeo PresvModeStateChange





o QosChangeo RatChangeo RoutingAreaUpdateo ServingNodeChangeLimito TariffTimeChange

o TimeLimito VolumeLimit

• CdrMaxRetries• CdrStorageMode• CdrTimeout• ChargingAgent

o ChargingAgentAddresso ChargingAgentPort

• DataReqStartSeqNum• Dictionary• EGCDRDataGenerationConfiguration

o ClosingCauseUniqueo DeleteServiceThresholdso IncludeAllLosdvso LosdvMaxContainerso LotdvMaxContainerso ServiceDownlinko ServiceIdleTimeouto ServiceIntervalo ServiceTotalo ServiceUplink

• LocalStorage• FileCompression• FileFormat• FileRotationCDRCount• FileRotationTimeInterval• FileRotationVolumeLimit• ForceFileRotationByTimeInterval• PurgeProcessedFiles• MBMSCDRTriggers

o Bucketso Intervalo Time1o Time2o Time3o Time4o Volume

• MaxCDRSinMsg





• MaxCDRSize• MaxCDRsWaitTime• RecoverFileSeqNum• SourcePortValidation• StartFileSeqNum• StorageServer

o StorageServerAddresso StorageServerMaxRetrieso StorageServerPorto StorageServerTimeout

11.3.2.9 Logical Inventory Attribute for Operator Policy

The Logical inventory Attributes for Operator Policy is given below

Table 9-18: Attribute for OperatorPolicy

Attr ibute name




Id M M - inventoryUnitType M M - vendorName M M - vendorUnitFamilyType CM M - vendorUnitTypeNumber CM M - serialNumber CM M - versionNumber O M - dateOfManufacture O M - dateOfLastService O M - unitPosition O M - manufacturerData O M - relatedFunction O M - ManagedFunction Id PolicyProfileId userLabel

11.3.2.9.1 Vendor Extension for Operator PolicyThe vendor extension information is given here

• ApnRemapTableName• ApnRemapTableValidity• CallControlProfileName• CallControlValidity• DefaultAPNProfileName• DefaultAPNProfileValidity• OperatorPolicyAPNEntries

o NetworkIdentifiero NetworkIdentifierAPNProfileNameo NetworkIdentifierAPNProfileValidityo OperatorIdentifiero OperatorIdentifierAPNProfileNameo OperatorIdentifierAPNProfileValidity

• OperatorPolicyDescription• OperatorPolicyIMEIRangesEntries

o ImeiValidityo ProfileNameo SoftwareVersiono StartRangeo ToRange

11.4 3GPP Status File

A Status file will be generated to indicate the completion status of the web service calls“getAllInventory” and “getManagedElement”. This file will be present under the“INSTALL_DIR”/sil-data folder and on the respective FTP / SFTP servers under theconfigured output directory.The status file will be referred to get the status of the web service requests.

11.4.1 Status File Name

The status file name contains the request ID, the module and the status of the completionof web service request.<Request_ID >_<Module_Identifier >_<Status >.status

Where:• Request_ID : A running sequence number generated by the server to uniquely

identify a request. The request ID is returned to the web service user in theresponse. The Web service user can use the request ID to query on the status of therequest.

• Module_Identifier : Indicates the module on which the status file was generated inresponse to an operation.

• Status : Indicates if the call has completed successfully, failed or in-progress.The status file will have the status strings as part of the name based on the followingconditions:

• IN_PROGRESS – Indicates that the file creation is started• SUCCESS - Indicates that the request is successfully executed• FAILURE – Indicates if any failure was encountered while processing the request

A Sample status file will have the following name: 10008_IM_SUCCESS.status

11.4.2 Status File Contents

The status file will contain information about the management elements for whichinventory was collected, their name, the inventory file name and the location of storage.

Total Managed Element Count : 1Success Count : 1Skipped Count : 0Failed Count : 0

ManagedElementName FamilyType Status InventoryFileName LocationSize(Bytes)10.86.66.35 CISCO_ASR_5500 SUCCESSIM_20120808_1005+0300_32767_10.86.66.35_10002.xmllocalhost://tmp/IM_20120808_1005+0300_32767_10.86.66.35_10002.xml

Where10.86.66.35 – Indicates the managed element for which the inventory is collected.CISCO_ASR_5500 – Indicates the device familySUCCESS – Indicates the status of the request.IM_20120808_1005+0300_32767_10.86.66.35_10002.xml – Name of the inventory file.10.10.56.55:/tmp – Indicates the location where the inventory file is generated.123456 – Indicates IM file size in bytes.

11.5 3GPP FT-IRP Inventory Notifications

11.5.1 File Ready Notification

<soap: Envel ope xml ns: soap=" ht t p: / / schemas. xml soap. or g/ soap/ envel ope/ " ><soap: Body>

<ns2: noti f yxml ns: ns2=" ht t p: / / www. 3gpp. org/ f t p/ Specs/ ar chi ve/ 32_ser i es/ 32. 307/ schema/32307- 810/ not i f i cat i on/ Not i f i cat i onI RPNt f Dat a"xml ns: ns3=" ht t p: / / www. 3gpp. org/ f t p/ Specs/ ar chi ve/ 32_ser i es/ 32. 317/ schema/

32317- 810/ Gener i cI RPDat a"xml ns: ns4="ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_seri es/ 32. 305#not i f i cat i on"xml ns: ns5="ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_seri es/ 32. 345#f TI RPI OCs"xml ns: ns6=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 345#f TI RPNot i f "

xml ns: ns7=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 526#sonPol icyNr m"xml ns: ns8=" ht t p: / / www. 3gpp. org/ f t p/ Specs/ ar chi ve/ 32_ser i es/ 32. 347#FTI RPData"xml ns: ns9=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 626#gener i cNr m" >

<not i f i cat i onHeader AndBody><ns4: Not i f i cat i on

xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"xsi : t ype=" ns6: Not i f yFi l eReady">

<ns4: header ><ns4: obj ect I nst ance>FTI RP=1</ ns4: obj ect I nst ance><ns4: event Ti me>2013- 04-

16T12: 55: 13. 171+05: 30</ ns4: event Ti me><ns4: sys t emDN>FTI RP=1</ ns4: sys t emDN><ns4: not i f i cat i onType>FI LE-

READY</ ns4: not i f i cat i onType></ ns4: header ><ns6: body>

<ns6: Fi l eI nf oLi st ><ns5: f i l eI nf o>

<ns5: management Dat aType>I M</ ns5: management Dat aType>

<ns5: f i l eLocat i on>10. 106. 2. 220: / t mp/ I M_20130416_1255+0530_32767_ASR- 5000_10005. xml </ ns5: f i l eLocat i on> <ns5: f i l eSi ze>1117964</ ns5: f i l eSi ze>

<ns5: f i l eReadyTi me>2013- 04-16T12: 55: 00. 000+05: 30</ ns5: f i l eReadyTi me>

<ns5: f i l eExpi r at i onTi me>2013- 05-

03T13: 35: 42. 086+05: 30</ ns5: f i l eExpi r at i onTi me><ns5: f i l eCompr essi on/ ><ns5: f i l eFor mat >XML-

schema</ ns5: f i l eFor mat ></ ns5: f i l eI nf o>

</ ns6: Fi l eI nf oLi st ><ns6: Addi t i onal Text >10005</ ns6: Addi t i onal Text >

</ ns6: body></ ns4: Not i f i cat i on>

</ not i f i cat i onHeader AndBody></ ns2: not i f y>

</ soap: Body></ soap: Envel ope>

11.5.2 File Preparation Error Notification<soap: Envel ope xml ns: soap=" ht t p: / / schemas. xml soap. or g/ soap/ envel ope/ " >

<soap: Body><ns2: noti f y

xml ns: ns2=" ht t p: / / www. 3gpp. org/ f t p/ Specs/ ar chi ve/ 32_ser i es/ 32. 307/ schema/32307- 810/ not i f i cat i on/ Not i f i cat i onI RPNt f Dat a"xml ns: ns3=" ht t p: / / www. 3gpp. org/ f t p/ Specs/ ar chi ve/ 32_ser i es/ 32. 317/ schema/32317- 810/ Gener i cI RPDat a"

xml ns: ns4="ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_seri es/ 32. 305#not i f i cat i on"xml ns: ns5="ht t p: / / www. 3gpp. or g/ f t p/ specs/ ar chi ve/ 32_seri es/ 32. 345#f TI RPI OCs"xml ns: ns6=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 345#f TI RPNot i f "xml ns: ns7=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 526#sonPol i

cyNr m"xml ns: ns8=" ht t p: / / www. 3gpp. org/ f t p/ Specs/ ar chi ve/ 32_ser i es/ 32. 347#FTI RPData"xml ns: ns9=" ht t p: / / www. 3gpp. org/ f t p/ specs/ ar chi ve/ 32_ser i es/ 32. 626#gener i cNr m" >

<not i f i cat i onHeader AndBody><ns4: Not i f i cat i on

xml ns: xsi =" ht t p: / / www. w3. or g/ 2001/ XMLSchema- i nst ance"xsi : t ype="ns6: Not i f yFi l ePr epar at i onEr r or ">

<ns4: header ><ns4: obj ect I nst ance>FTI RP=1</ ns4: obj ect I nst ance><ns4: event Ti me>2013- 04-

16T16: 39: 04. 464+05: 30</ ns4: event Ti me><ns4: sys t emDN>FTI RP=1</ ns4: sys t emDN><ns4: not i f i cat i onType>FI LE-

PREPARATI ON_ERROR</ ns4: not i f i cat i onType></ ns4: header ><ns6: body>

<ns6: Fi l eI nf oLi st / ><ns6: Reason>er r or I nPr epar at i on</ ns6: Reason><ns6: Addi t i onal Text >10012: Encount er ed Er r or whi l e

pr epar i ng I nvent or y Fi l es f or Some managed Devi ces</ ns6: Addi t i onal Text ></ ns6: body>

</ ns4: Not i f i cat i on></ not i f i cat i onHeader AndBody>

</ ns2: not i f y></ soap: Body>

</ soap: Envel ope>

11.6 FTP Configuration

File Transfer is required to transfer inventory files to a remote file server as specified byend user. User can configure the file server details using the script (ftpConfig.sh) availablein the SIL installation directory ($SIL_HOME/bin).

Each FTP server has a primary and a secondary ftp server setup with fail-over option orreplication option. In fail-over option, files are transferred to the secondary ftp server if theprimary is not reachable or copied on to the configured directory on local machine if thesecondary is not reachable as well. However, in replication option, files are transferred to

both the primary and the secondary ftp servers. In cases, where both primary andsecondary servers are not available, the files will be stored in the local storage directory.

For information on managing FTP for Standalone integration layer, see the Next Stepschapter in Cisco Prime Network 3.10 Installation Guide .

http://preview.cisco.com/en/US/products/ps11879/prod_installation_guides_list.html





11.7 Useful Code Snippets for 3GPP

This section has sample code snippets to retrieve the inventory using 3GPP interface.

11.7.1 Code Snippet for 3GPP Request Response

This section provides code snippets that can be used by a SOAP client to communicate withthe 3GPP Web Service to perform the required operation.

/ / J ava SOAP cl i ent I mport s

i mpor t j avax. xml . soap. SOAPBody;i mpor t j avax. xml . soap. SOAPConnect i on;i mpor t j avax. xml . soap. SOAPConnect i onFact or y;i mpor t j avax. xml . soap. SOAPEl ement ;i mpor t j avax. xml . soap. SOAPEnvel ope;i mport j avax. xml . soap. SOAPExcept i on;i mport j avax. xml . soap. SOAPFact or y;i mpor t j avax. xml . soap. SOAPHeader ;

i mpor t j avax. xml . soap. SOAPMessage;i mport j avax. xml . soap. SOAPPart ;i mpor t j avax. xml . t r ansf orm. Sour ce;

/ / Const r uct i ng t he SOAP Header

SOAPHeader header = message. get SOAPHeader ( ) ;i f ( header == nul l )

header = envel ope. addHeader ( ) ;

/ / Const r uct i ng t he cont ent s f or per f or mi ng Aut hor i zat i on

St r i ng AUTH_NS = " ht t p: / / docs. oasi s- open. org/ wss/ 2004/ 01/ oasi s-200401- wss- wssecur i t y- secext- 1. 0. xsd";

St r i ng AUTH_PREFI X = " wsse";SOAPFact or y soapFact or y = SOAPFact or y. newI nst ance( ) ;SOAPEl ement wsSecHeader El m = soapFact or y. cr eat eEl ement ( " Secur i t y",

AUTH_PREFI X, AUTH_NS) ;SOAPEl ement user NameTokenEl m = soapFact or y. cr eat eEl ement (

" User nameToken" , AUTH_PREFI X, AUTH_NS) ;Name qname = envel ope

. cr eat eName(" I d" ," wsu","ht t p: / / docs. oas i s -

open. or g/ wss/ 2004/ 01/ oasi s- 200401- wss- wssecur i t y- ut i l i t y- 1. 0. xsd") ;user NameTokenEl m. addAt t r i but e( qname, "User nameToken- 27" ) ;SOAPEl ement user NameEl m = soapFact or y. cr eat eEl ement ( " User name",

AUTH_PREFI X, AUTH_NS) ;user NameEl m. addText Node( user name) ;

SOAPEl ement passwdEl m = soapFact or y. cr eat eEl ement ( " Passwor d",AUTH_PREFI X, AUTH_NS) ;

pass wdEl m. addText Node( pass wor d) ;Name passwor dType = envel ope. cr eat eName( " Type") ;pass wdEl m

. addAt t r i but e(passwor dType,





"ht t p: / / docs. oas i s -open. or g/ wss/ 2004/ 01/ oasi s- 200401- wss- username- t oken- pr of i l e-1. 0#Passwor dText " ) ;

user NameTokenEl m. addChi l dEl ement ( user NameEl m) ;user NameTokenEl m. addChi l dEl ement ( passwdEl m) ;

/ / add chi l d el ement s t o t he r oot el ement

wsSecHeader El m. addChi l dEl ement ( user NameTokenEl m) ;/ / add SOAP el ement f or header t o SOAP header obj ectheader . addChi l dEl ement ( wsSecHeader El m) ;/ / end: set t i ng SOAP headers

/ / st ar t : set t i ng SOAP body/ / Cr eat e and popul at e t he bodySOAPBody body = envel ope. get Body( ) ;

/ / Cr eat e t he mai n el ement and namespace/ / Cr eat es mai n el ement f or “get Al l I nvent or y” Oper at i on.

SOAPEl ement bodyEl ement = body. addChi l dEl ement ( envel ope

. cr eat eName("get Al l I nvent or y" ," i nv" ,

"ht t p: / / www. 3gpp. or g/ f t p/ Specs/ ar chi ve/ 32_seri es/ ci scoTgppI nvent ory/ schema/ I nvent or yI RPDat a") ) ;

/ / Add cont ent

bodyEl ement . addChi l dEl ement ( "i nvokeI dent i f i er I n") . addText Node( "123") ;bodyEl ement . addChi l dEl ement ( " quer yXpat hExp" ) . addText Node(

" / MD=CI SCO_PRI ME") ;

/ / Save t he messagemessage. saveChanges( ) ;

Mi meHeader s header s = message. get Mi meHeader s( ) ;header s. addHeader ( "SOAPAct i on", " get Al l I nvent ory") ;

/ / Set t he dest i nat i on/ / Send t he message and get t he r epl y

SOAPMessage r epl y = connect i on. cal l ( message, wsdl name) ;

11.7.2 Code Snippet for 3GPP Notification ConsumerDevel opi ng a not i f i cat i on consumer i nvol ves i mpl ement i ng t he 3GPPNot i f i cat i on I RP Webser vi ce i nt er f ace and publ i shi ng i t .

• Sampl e I mpl ement at i on of t he Not i f i cat i on I RP Webservi ce i nt er f ace:

i mpor t j ava. i o. St r i ngWr i t er ;

i mpor t j avax. j ws. Oneway;i mpor t j avax. j ws. WebMet hod;i mpor t j avax. j ws. WebPar am;i mpor t j avax. xml . bi nd. J AXBCont ext ;i mport j avax. xml . bi nd. J AXBEl ement ;i mpor t j avax. xml . bi nd. J AXBExcept i on;i mpor t j avax. xml . bi nd. Mar shal l er ;i mpor t j avax. xml . namespace. QName;





i mpor t j avax. xml . ws. Request Wr apper ;

i mportor g. _3gpp. f t p. specs. ar chi ve. _32_seri es. _32_307. schema. _32307_810. noti f i cati on. not i f i cat i oni r pnt f dat a. AnySequenceType;i mportor g. _3gpp. f t p. specs. ar chi ve. _32_seri es. _32_307. schema. _32307_810. noti f i cat

i on. not i f i cat i oni r pnt f sys tem. Not i f i cat i onI RPNt f ;@j avax. j ws. WebSer vi ce( ser vi ceName = " Not i f i cat i onI RPNt f " , por t Name =" Not i f i cat i onI RPNt f " , t ar get Namespace =" ht t p: / / www. 3gpp. or g/ f t p/ Specs/ archi ve/ 32_ser i es/ 32. 307/ schema/ 32307-810/ not i f i cat i on/ Not i f i cat i onI RPNt f Syst em", name = "Not i f i cat i onI RPNt f ",endpoi nt I nt er f ace ="or g. _3gpp. f t p. specs. ar chi ve. _32_seri es. _32_307. schema. _32307_810. not i f i cat i on. not i f i cat i oni r pnt f sys tem. Not i f i cat i onI RPNt f ")publ i c cl ass TGPPNot i f i cat i onConsumerI mpl i mpl ement s Not i f i cat i onI RPNt f {

@Oneway@Request Wr apper ( l ocal Name = " not i f y" , t ar get Namespace =

" ht t p: / / www. 3gpp. or g/ f t p/ Specs/ archi ve/ 32_ser i es/ 32. 307/ schema/ 32307-810/ not i f i cat i on/ Not i f i cat i onI RPNt f Dat a", cl assName ="or g. _3gpp. f t p. specs. ar chi ve. _32_seri es. _32_307. schema. _32307_810. not i f i cat i on. not i f i cat i oni r pnt f dat a. Not i f y" )

@WebMet hod( act i on =" ht t p: / / www. 3gpp. or g/ f t p/ Specs/ archi ve/ 32_ser i es/ 32. 307/ schema/ 32307-810/ not i f i cat i on/ not i f y" )

publ i c voi d not i f y( @WebPar am( name = " not i f i cat i onHeader AndBody" ,t ar get Namespace = " " ) AnySequenceType anySequence) {

/ / Do somet hi ng wi t h t he not i f i cat i on/ / Thi s i mpl ement at i on j ust mar shal l s t he not i f i cat i on and pr i nt s

i t .par seJ AXBEl ement ( anySequence) ;

}

@Suppr essWar ni ngs( { "unchecked" , " r awt ypes" })

publ i c voi d par seJ AXBEl ement ( AnySequenceType anySequence) {try {

J AXBCont ext j axbCont ext = J AXBCont ext . newI nst ance( anySequence. get Cl ass ( ) ,

or g. _3gpp. f t p. specs. ar chi ve. _32_ser i es . _32. Obj ectFactory. cl ass) ;

Mar shal l er j axbMar shal l er = j axbCont ext . cr eat eMar shal l er ( ) ;

/ / out put pr et t y pr i nt ed j axbMar shal l er . set Pr oper t y( Mar shal l er . J AXB_FORMATTED_OUTPUT,

t r ue) ;

St r i ngWr i t er st r i ngWr i t er = new St r i ngWr i t er ( ) ; j axbMar shal l er . mar shal ( new J AXBEl ement (

new QName( " ur i " , "l ocal ") ,anySequence. get Cl ass( ) , anySequence ) , st r i ngWr i t er ) ;

Sys tem. out . pr i nt l n( "Not i f i cat i on Recei ved. . . . " ) ;Sys tem. out . pr i nt l n( s t r i ngWr i t er . get Buf f er ( ) . t oSt r i ng( ) ) ;

} cat ch ( J AXBExcept i on e) {e. pr i nt St ackTr ace( ) ;

}





}}

• Publ i shi ng t he Webservi ce:

Once you have i mpl ement ed Not i f i cat i on I RP I nt er f ace, you can publ i sh t hewebser vi ce usi ng t he Endpoi nt . publ i sh met hod as bel ow:

Endpoi nt . publ i sh( "ht t p: / / 10. 105. 39. 39: 9229/ Noti f i cat i onConsumer ", new TGPPNot i f i cat i onConsumer I mpl ( ) ) ;



References


12 References

Refer the following document alongwith this guide.

• Addendum: Prime Network OSS Integration – Sample SOAP Request Response onCisco Developer Network . To view the information on the CDN website, you musthave a Cisco.com account with partner level access, or you must be a PrimeNetwork licensee.






References

Prime Network OSS Integration Guide-2-0

Documents

Transcript of Prime Network OSS Integration Guide-2-0