86011REV000 - V1 - Navis EMS-CBGX TMF 814 Adapter Implementation Reference Software Release 09.02.00.00

Beta Draft Confidential
Navis EMS-CBGX
TMF 814 Adapter Implementation Reference
Software Release 09.02.00.00
Product Code: 86011

Revision 000
June 2004
Copyright© 2004 Lucent Technologies. All Rights Reserved.
This material is protected by the copyright laws of the United States and other
countries. It may not be reproduced, distributed, or altered in any fashion by any entity
(either internal or external to Lucent Technologies), except in accordance with
applicable agreements, contracts or licensing, without the express written consent of
Lucent Technologies.
For permission to reproduce or distribute, please contact: Technical Publications,

Integrated Network Solutions/Core Switching Division at 978-692-2600.
Notice. Every effort was made to ensure that the information in this document was
complete and accurate at the time of printing. However, information is subject to
change.
Trademarks. IP Navigator, Navis, NavisXtend, Navis iEngineer, CBX 3500 and

AQueView are trademarks of Lucent Technologies. CBX 500, GX 550 and B-STDX
9000 are registered trademarks of Lucent Technologies. Other trademarks and trade
names mentioned in this document belong to their respective owners.
Limited Warranty. Lucent Technologies provides a limited warranty to this

product. For more information, see the software license agreement in this document.
Ordering Information. To order copies of this document, use the online ordering
instructions presented later in this guide.
Support Telephone Numbers. For technical support and other services, see the
customer support contact information in the “About This Guide” section of this
document.
ii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

LUCENT TECHNOLOGIES END-USER LICENSE AGREEMENT

LUCENT TECHNOLOGIES IS WILLING TO LICENSE THE ENCLOSED SOFTWARE
AND ACCOMPANYING USER DOCUMENTATION (COLLECTIVELY, THE
“PROGRAM”) TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF
THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. PLEASE READ
THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY
BEFORE OPENING THE PACKAGE(S) OR USING THE LUCENT SWITCH(ES)
CONTAINING THE SOFTWARE, AND BEFORE USING THE ACCOMPANYING USER
DOCUMENTATION. OPENING THE PACKAGE(S) OR USING THE LUCENT
SWITCH(ES) CONTAINING THE PROGRAM WILL INDICATE YOUR ACCEPTANCE
OF THE TERMS OF THIS LICENSE AGREEMENT. IF YOU ARE NOT WILLING TO BE
BOUND BY THE TERMS OF THIS LICENSE AGREEMENT, LUCENT IS UNWILLING
TO LICENSE THE PROGRAM TO YOU, IN WHICH EVENT YOU SHOULD RETURN
THE PROGRAM WITHIN TEN (10) DAYS FROM SHIPMENT TO THE PLACE FROM
WHICH IT WAS ACQUIRED, AND YOUR LICENSE FEE WILL BE REFUNDED. THIS
LICENSE AGREEMENT REPRESENTS THE ENTIRE AGREEMENT CONCERNING
THE PROGRAM BETWEEN YOU AND LUCENT, AND IT SUPERSEDES ANY PRIOR
PROPOSAL, REPRESENTATION OR UNDERSTANDING BETWEEN THE PARTIES.
1. License Grant. Lucent hereby grants to you, and you accept, a non-exclusive,
non-transferable license to use the computer software, including all patches, error
corrections, updates and revisions thereto in machine-readable, object code form only
(the “Software”), and the accompanying User Documentation, only as authorized in
this License Agreement. The Software may be used only on a single computer owned,
leased, or otherwise controlled by you; or in the event of inoperability of that
computer, on a backup computer selected by you. You agree that you will not pledge,
lease, rent, or share your rights under this License Agreement, and that you will not,
without Lucent’s prior written consent, assign or transfer your rights hereunder. You
agree that you may not modify, reverse assemble, reverse compile, or otherwise
translate the Software or permit a third party to do so. You may make one copy of the
Software and User Documentation for backup purposes. Any such copies of the
Software or the User Documentation shall include Lucent’s copyright and other
proprietary notices. Except as authorized under this paragraph, no copies of the
Program or any portions thereof may be made by you or any person under your
authority or control.
2. Lucent’s Rights. You agree that the Software and the User Documentation are
proprietary, confidential products of Lucent or Lucent's licensor protected under US
copyright law and you will use your best efforts to maintain their confidentiality. You
further acknowledge and agree that all right, title and interest in and to the Program,
including associated intellectual property rights, are and shall remain with Lucent or
Lucent's licensor. This License Agreement does not convey to you an interest in or to
the Program, but only a limited right of use revocable in accordance with the terms of
this License Agreement.
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04iii

3. License Fees. The license fees paid by you are paid in consideration of the license
granted under this License Agreement.
4. Term. This License Agreement is effective upon your opening of the package(s) or
use of the switch(es) containing Software and shall continue until terminated. You
may terminate this License Agreement at any time by returning the Program and all
copies or portions thereof to Lucent. Lucent may terminate this License Agreement
upon the breach by you of any term hereof. Upon such termination by Lucent, you
agree to return to Lucent the Program and all copies or portions thereof. Termination
of this License Agreement shall not prejudice Lucent's rights to damages or any other
available remedy.
5. Limited Warranty. Lucent warrants, for your benefit alone, for a period of 90
days from the date of shipment of the Program by Lucent (the “Warranty Period”) that
the program diskettes in which the Software is contained are free from defects in
material and workmanship. Lucent further warrants, for your benefit alone, that during
the Warranty Period the Program shall operate substantially in accordance with the
User Documentation. If during the Warranty Period, a defect in the Program appears,
you may return the Program to the party from which the Program was acquired for
either replacement or, if so elected by such party, refund of amounts paid by you under
this License Agreement. You agree that the foregoing constitutes your sole and
exclusive remedy for breach by Lucent of any warranties made under this Agreement.
EXCEPT FOR THE WARRANTIES SET FORTH ABOVE, THE PROGRAM IS LICENSED
“AS IS”, AND LUCENT DISCLAIMS ANY AND ALL OTHER WARRANTIES,
WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT
LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE AND ANY WARRANTIES OF NONINFRINGEMENT.
6. Limitation of Liability. Lucent’s cumulative liability to you or any other party

for any loss or damages resulting from any claims, demands, or actions arising out of
or relating to this License Agreement shall not exceed the greater of: (i) ten thousand
US dollars ($10,000) or (ii) the total license fee paid to Lucent for the use of the
Program. In no event shall Lucent be liable for any indirect, incidental, consequential,
special, punitive or exemplary damages or lost profits, even if Lucent has been advised
of the possibility of such damages.
iv6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

7. Proprietary Rights Indemnification. Lucent shall at its expense defend you

against and, subject to the limitations set forth elsewhere herein, pay all costs and
damages made in settlement or awarded against you resulting from a claim that the
Program as supplied by Lucent infringes a United States copyright or a United States
patent, or misappropriates a United States trade secret, provided that you: (a) provide
prompt written notice of any such claim, (b) allow Lucent to direct the defense and
settlement of the claim, and (c) provide Lucent with the authority, information, and
assistance that Lucent deems reasonably necessary for the defense and settlement of
the claim. You shall not consent to any judgment or decree or do any other act in
compromise of any such claim without first obtaining Lucent’s written consent. In any
action based on such a claim, Lucent may, at its sole option, either: (1) obtain for you
the right to continue using the Program, (2) replace or modify the Program to avoid
the claim, or (3) if neither (1) nor (2) can reasonably be effected by Lucent, terminate
the license granted hereunder and give you a prorata refund of the license fee paid for
such Program, calculated on the basis of straight-line depreciation over a five-year
useful life. Notwithstanding the preceding sentence, Lucent will have no liability for
any infringement or misappropriation claim of any kind if such claim is based on: (i)
the use of other than the current unaltered release of the Program and Lucent has
provided or offers to provide such release to you for its then current license fee, or (ii)
use or combination of the Program with programs or data not supplied or approved by
Lucent to the extent such use or combination caused the claim.
8. Export Control. You agree not to export or disclose to anyone except a United
States national any portion of the Program supplied by Lucent without first obtaining
the required permits or licenses to do so from the US Office of Export Administration,
and any other appropriate government agency.
9. Governing Law. This License Agreement shall be construed and governed in

accordance with the laws and under the jurisdiction of the Commonwealth of
Massachusetts, USA. Any dispute arising out of this Agreement shall be referred to an
arbitration proceeding in Boston, Massachusetts, USA by the American Arbitration
Association.
10. Miscellaneous. If any action is brought by either party to this License

Agreement against the other party regarding the subject matter hereof, the prevailing
party shall be entitled to recover, in addition to any other relief granted, reasonable
attorneys’ fees and expenses of arbitration. Should any term of this License
Agreement be declared void or unenforceable by any court of competent jurisdiction,
such declaration shall have no effect on the remaining terms hereof. The failure of
either party to enforce any rights granted hereunder or to take action against the other
party in the event of any breach hereunder shall not be deemed a waiver by that party
as to subsequent enforcement of rights or subsequent actions in the event of future
breaches.
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04v

vi6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Contents
About This Guide
Purpose...................................................................................................................... xvii
What You Need to Know.......................................................................................... xvii
What’s New in This Guide ......................................................................................xviii
About the Provisioning Server Document Set ........................................................... xix
About the Navis EMS-CBGX TMF 814 Adapter Document Set............................... xx
How to Use This Guide.............................................................................................. xxi
Conventions .............................................................................................................. xxii
Related Documents ..................................................................................................xxiii
Lucent................................................................................................................xxiii
Third Party.........................................................................................................xxiii
Ordering Printed Manuals Online............................................................................xxiii
Customer Comments................................................................................................ xxiv
Technical Support .................................................................................................... xxiv
Chapter 1 Overview
System Architecture...................................................................................................1-1
Requirements .............................................................................................................1-2
EMS Requirements..............................................................................................1-2
Recommendations for Notification Service Usage....................................................1-3
General Recommendations..................................................................................1-3
QoS and Admin Parameters ................................................................................1-3
Constraints...........................................................................................................1-3
TMF Objects ..............................................................................................................1-4
Usage Information .....................................................................................................1-5
Chapter 2 emsMgr Module

Interfaces....................................................................................................................2-2
EMSMgr_I...........................................................................................................2-2
Data Types .................................................................................................................2-6
Notifications...............................................................................................................2-6
Navis EMS-CBGX TMF 814 Adapter Implementation Reference rvii

Contents
Chapter 3 emsSessionFactory Module

Interfaces....................................................................................................................3-2
EmsSessionFactory_I ..........................................................................................3-2
Chapter 4 emsSession Module

Interfaces....................................................................................................................4-2
EmsSession_I ......................................................................................................4-2
Data Types .................................................................................................................4-3
Notifications...............................................................................................................4-3
Chapter 5 multiLayerSubnetwork Module

Interfaces....................................................................................................................5-2
MultiLayerSubnetworkMgr_I .............................................................................5-2
SubnetworkIterator_I.........................................................................................5-19
Data Types ...............................................................................................................5-20
Notifications.............................................................................................................5-20
Chapter 6 managedElement Module

Interfaces....................................................................................................................6-2
ManagedElementMgr_I.......................................................................................6-2
ManagedElementIterator_I................................................................................6-15
Data Types ...............................................................................................................6-15
Notifications.............................................................................................................6-15
Termination Point Usage .........................................................................................6-16
Chapter 7 equipment Module

Interfaces....................................................................................................................7-2
EquipmentInventoryMgr_I..................................................................................7-2
EquipmentOrHolderIterator_I .............................................................................7-9
Data Types ...............................................................................................................7-10
Notifications.............................................................................................................7-10
Mandatory Provisioning Server Object Attributes ..................................................7-10
Chapter 8 terminationPoint Module

Interfaces....................................................................................................................8-2
TerminationPointIterator_I..................................................................................8-2
Data Types .................................................................................................................8-2
Chapter 9 topologicalLink Module

Interfaces....................................................................................................................9-2
TopologicalLinkIterator_I ...................................................................................9-2
Data Types .................................................................................................................9-2
viii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Contents
Chapter 10 subnetworkConnection Module

Interfaces..................................................................................................................10-2
SNCIterator_I ....................................................................................................10-2
Data Types ...............................................................................................................10-2
Chapter 11 protection Module

Interfaces..................................................................................................................11-2
ProtectionGroupIterator_I .................................................................................11-2
ProtectionMgr_I ................................................................................................11-2
Data Types ...............................................................................................................11-6
Notifications.............................................................................................................11-6
Chapter 12 trafficDescriptor Module

Interfaces..................................................................................................................12-2
TrafficDescriptorMgr_I.....................................................................................12-2
TrafficDescriptorIterator_I................................................................................12-5
Data Types ...............................................................................................................12-5
Notifications.............................................................................................................12-6
Mandatory Provisioning Server Object Attributes ..................................................12-7
Chapter 13 transmissionParameters Module

Data Types ...............................................................................................................13-2
Chapter 14 guiCutThrough Module

Interfaces..................................................................................................................14-2
GuiCutThroughMgr_I .......................................................................................14-2
Data Types ...............................................................................................................14-3
Notifications.............................................................................................................14-3
Chapter 15 maintenanceOps Module

Interfaces..................................................................................................................15-2
CurrentMaintenanceOperationIterator_I ...........................................................15-2
MaintenanceMgr_I ............................................................................................15-2
Data Types ...............................................................................................................15-3
Notifications.............................................................................................................15-3
Chapter 16 mtnmVersion Module

Interfaces..................................................................................................................16-2
Version_I ...........................................................................................................16-2
Chapter 17 nmsSession
Interfaces..................................................................................................................17-2
NmsSession_I....................................................................................................17-2
Navis EMS-CBGX TMF 814 Adapter Implementation Reference ix

Contents
Chapter 18 performance Module
Chapter 19 session Module

Interfaces..................................................................................................................19-2
Session_I ...........................................................................................................19-2
Chapter 20 globaldefs Module

Interfaces..................................................................................................................20-2
NamingAttributesIterator_I ...............................................................................20-2
Data Types ...............................................................................................................20-2
Chapter 21 notifications Module

Interfaces..................................................................................................................21-2
EventIterator_I...................................................................................................21-2
Data Types ...............................................................................................................21-2
Chapter 22 common Module

Interfaces..................................................................................................................22-2
Common_I.........................................................................................................22-2
Data Types ...............................................................................................................22-4
Notifications.............................................................................................................22-4
Chapter 23 TMF 814A Object NamingAttributes for Provisioning Server

ems ...........................................................................................................................23-2
multiLayerSubnetwork ............................................................................................23-2
managedElement......................................................................................................23-2
equipment Holder.....................................................................................................23-3
equipment.................................................................................................................23-3
TPPool......................................................................................................................23-4
PTP...........................................................................................................................23-4
CTP ..........................................................................................................................23-5
topologicalLink ........................................................................................................23-6
subnetworkConnection ............................................................................................23-7
Protection .................................................................................................................23-8
trafficDescriptor.......................................................................................................23-9
Other Objects ...........................................................................................................23-9
Chapter 24 Mapping TMF 814A Data Type and Provisioning Server Attributes
ems ...........................................................................................................................24-3
emssession................................................................................................................24-4
multiLayerSubnetwork ............................................................................................24-5
managedElement......................................................................................................24-7
equipment Holder.....................................................................................................24-9
equipment...............................................................................................................24-12
terminationPoint.....................................................................................................24-14
PTP.........................................................................................................................24-18
x6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Contents
CTP ........................................................................................................................24-20
topologicalLink ......................................................................................................24-22
SubnetworkConnection..........................................................................................24-23
protection ...............................................................................................................24-29
trafficDescriptor.....................................................................................................24-34
transmissionParameters..........................................................................................24-36
guiCutThrough.......................................................................................................24-37
maintenanceOps.....................................................................................................24-38
performance ...........................................................................................................24-41
common..................................................................................................................24-41
Chapter 25 Iterators for Provisioning Server TMF 814A Implementation
Chapter 26 Troubleshooting Navis EMS-CBGX TMF 814A Implementation

Implementation Problems ........................................................................................26-1
Appendix A Mapping TMF 814 Layer Rates with Provisioning Server

Transport Technologies ............................................................................................ A-1
ATM CTP Layering.................................................................................................. A-3
8 Port DS3 (ATM) Card..................................................................................... A-4
8 Port E3 (ATM) Card........................................................................................A-5
4 Port OC-3c/STM1 Card................................................................................... A-6
6 Port FR DS3 Card............................................................................................ A-7
6 Port FR Channelized DS3 Card (Only 3/1/10)................................................ A-8
Appendix B Supported Layer Rates in Navis EMS-CBGX TMF 814 Adapter

Layer Rates ............................................................................................................... B-1
Transmission Parameters for Layer Rates ................................................................ B-3
Acronyms
Index
Navis EMS-CBGX TMF 814 Adapter Implementation Reference xi

Contents
List of Figures
Figure 1-1. Navis EMS-CBGX TMF 814 Adapter Overview ...........................1-1
Figure 6-1. Termination Point Usage ...............................................................6-16
Figure A-1. Transport Technologies at various layers, and TMF object ........... A-1
Figure A-2. MTNM and G.805 Layered Model................................................. A-2
Figure A-3. 8 Port E3 ATM Card on CBX 500 ................................................. A-4
Figure A-4. 8 Port E3 ATM Card on CBX 500 ................................................. A-5
Figure A-5. 4 Port OC3c/STM1 ATM Card on CBX 500 ................................. A-6
Figure A-6. 6 Port FR Channelized DS3 Card................................................... A-8
xii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Contents
List of Tables
Table 1-1. Provisioning Server Object Hierarchy.............................................1-2
Table 1-2. TMF Objects....................................................................................1-4
Table 2-1. List of Sections - emsMgr................................................................2-1
Table 2-2. getAllEMSAndMEActiveAlarms....................................................2-2
Table 2-3. getAllEMSSystemActiveAlarms.....................................................2-3
Table 2-4. getAllTopLevelSubnetworks...........................................................2-3
Table 2-5. getAllTopLevelSubnetworkNames .................................................2-4
Table 2-6. getAllTopLevelTopologicalLinks ...................................................2-4
Table 2-7. getAllTopLevelTopologicalLinkNames..........................................2-5
Table 2-8. getTopLevelTopologicalLink ..........................................................2-5
Table 2-9. getEMS ............................................................................................2-6
Table 3-1. List of Sections - emsSessionFactory ..............................................3-1
Table 3-2. getEmsSession .................................................................................3-2
Table 4-1. List of Sections - emsSession ..........................................................4-1
Table 4-2. getEventChannel..............................................................................4-2
Table 4-3. getManager ......................................................................................4-2
Table 4-4. getSupportedManagers ....................................................................4-3
Table 5-1. List of Sections - multiLayerSubnetwork........................................5-1
Table 5-2. activateSNC .....................................................................................5-3
Table 5-3. checkValidSNC ...............................................................................5-3
Table 5-4. createSNC ........................................................................................5-4
Table 5-5. deactivateSNC .................................................................................5-4
Table 5-6. deleteSNC ........................................................................................5-5
Table 5-7. getAllTPPoolNames ........................................................................5-5
Table 5-8. getAllTPPools..................................................................................5-6
Table 5-9. getAssociatedTP ..............................................................................5-6
Table 5-10. createAndActivateSNC....................................................................5-6
Table 5-11. deactivateAndDeleteSNC ................................................................5-8
Table 5-12. getAllEdgePoints .............................................................................5-9
Table 5-13. getAllEdgePointNames..................................................................5-10
Table 5-14. getAllManagedElements................................................................5-11
Table 5-15. getAllManagedElementNames ......................................................5-12
Table 5-16. getAllSubnetworkConnections ......................................................5-12
Table 5-17. getAllSubnetworkConnectionNames ............................................5-13
Table 5-18. getAllSubnetworkConnectionsWithTP .........................................5-14
Table 5-19. getAllSubnetworkConnectionNamesWithTP................................5-14
Table 5-20. getAllTopologicalLinks.................................................................5-15
Table 5-21. getAllTopologicalLinkNames .......................................................5-16
Table 5-22. getMultiLayerSubnetwork .............................................................5-16
Table 5-23. getRoute.........................................................................................5-17
Table 5-24. getSNC...........................................................................................5-17
Table 5-25. getSNCsByUserLabel....................................................................5-18
Table 5-26. getTopologicalLink........................................................................5-18
Table 6-1. List of Sections - managedElement .................................................6-1
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xiii

Contents
Table 6-2. getAllActiveAlarms.........................................................................6-3

Table 6-3. getAllCrossConnections ..................................................................6-3
Table 6-4. getAllManagedElements..................................................................6-4
Table 6-5. getAllManagedElementNames ........................................................6-4
Table 6-6. getAllPTPs.......................................................................................6-5
Table 6-7. getAllPTPNames .............................................................................6-6
Table 6-8. getContainedCurrentTPs..................................................................6-6
Table 6-9. getContainedCurrentTPNames ........................................................6-7
Table 6-10. getContainedInUseTPs ....................................................................6-8
Table 6-12. getContainedPotentialTPs................................................................6-9
Table 6-11. getContainedInUseTPNames...........................................................6-9
Table 6-13. getContainedPotentialTPNames ...................................................6-10
Table 6-15. getContainingTPs ..........................................................................6-11
Table 6-14. getContainingSubnetworkNames ..................................................6-11
Table 6-17. getManagedElement ......................................................................6-12
Table 6-16. getContainingTPNames.................................................................6-12
Table 6-19. setTPData.......................................................................................6-13
Table 6-18. getTP..............................................................................................6-13
Table 7-1. List of Sections - equipment ............................................................7-1
Table 7-2. getAllEquipment..............................................................................7-3
Table 7-3. getAllEquipmentNames...................................................................7-3
Table 7-4. getAllSupportedPTPs ......................................................................7-4
Table 7-5. getAllSupportedPTPNames.............................................................7-5
Table 7-6. getAllSupportingEquipment ............................................................7-5
Table 7-7. getAllSupportingEquipmentNames.................................................7-6
Table 7-8. getContainedEquipment ..................................................................7-6
Table 7-9. getEquipment...................................................................................7-7
Table 7-10. provisionEquipment.........................................................................7-7
Table 7-11. setAlarmReportingOff .....................................................................7-8
Table 7-12. setAlarmReportingOn......................................................................7-9
Table 7-13. unprovisionEquipment.....................................................................7-9
Table 7-14. Mandatory Provisioning Server Object Attributes ........................7-10
Table 8-1. List of Sections - terminationPoint ..................................................8-1
Table 9-1. List of Sections - topologicalLink ...................................................9-1
Table 10-1. List of Sections - subnetworkConnection......................................10-1
Table 11-1. List of Sections - protection...........................................................11-1
Table 11-2. getAllNUTTPNames .....................................................................11-2
Table 11-3. getAllPreemptibleTPNames ..........................................................11-3
Table 11-4. getAllProtectedTPNames ..............................................................11-3
Table 11-5. getAllProtectionGroups .................................................................11-4
Table 11-6. getProtectionGroup........................................................................11-4
Table 11-7. performProtectionCommand .........................................................11-5
Table 11-8. retrieveSwitchData ........................................................................11-5
Table 12-1. List of Sections - trafficDescriptor ................................................12-1
Table 12-2. createTrafficDescriptor..................................................................12-2
Table 12-3. deleteTrafficDescriptor..................................................................12-3
Table 12-4. getAllTrafficDescriptors................................................................12-3
Table 12-5. getAllTrafficDescriptorNames ......................................................12-4
xiv6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Contents
Table 12-6. getAssociatedCTPs ........................................................................12-4

Table 12-7. getTrafficDescriptor ......................................................................12-5
Table 12-8. Mandatory Object Attributes for TDCreateData_T.......................12-7
Table 12-9. Mandatory Object Attributes for TrafficParameterList_T ............12-7
Table 13-1. List of Sections - transmissionParameters.....................................13-1
Table 14-1. List of Sections - guiCutThrough ..................................................14-1
Table 14-2. destroyGCT....................................................................................14-2
Table 14-3. getGCTProfileInfo.........................................................................14-2
Table 14-4. launchGCT.....................................................................................14-3
Table 15-1. List of Sections - maintenanceOps ................................................15-1
Table 15-2. getActiveMaintenanceOperation ...................................................15-2
Table 15-3. performMaintenanceOperation......................................................15-3
Table 16-1. List of Sections - mtnmVersion.....................................................16-1
Table 16-2. getVersion......................................................................................16-2
Table 17-1. List of Sections - nmsSession ........................................................17-1
Table 17-2. eventLossCleared...........................................................................17-2
Table 17-3. eventLossOccurred ........................................................................17-2
Table 19-1. List of Sections - session ...............................................................19-1
Table 19-2. oneway...........................................................................................19-2
Table 19-3. ping ................................................................................................19-2
Table 19-4. getAssociatedSession.....................................................................19-3
Table 20-1. List of Sections - globaldefs ..........................................................20-1
Table 21-1. List of Sections - notifications.......................................................21-1
Table 22-1. List of Sections - common.............................................................22-1
Table 22-2. getCapabilities ...............................................................................22-2
Table 22-3. setNativeEMSName ......................................................................22-2
Table 22-4. setOwner ........................................................................................22-3
Table 22-5. setUserLabel ..................................................................................22-3
Table 23-1. ems - NamingAttributes.................................................................23-2
Table 23-2. multiLayerSubnetwork - NamingAttributes ..................................23-2
Table 23-3. managedElement NamingAttributes..............................................23-2
Table 23-4. equipment Holder - NamingAttributes ..........................................23-3
Table 23-5. equipment NamingAttributes.........................................................23-3
Table 23-6. PTP - NamingAttributes ................................................................23-4
Table 23-7. CTP - NamingAttributes................................................................23-5
Table 23-8. topologicalLink NamingAttributes................................................23-6
Table 23-9. subnetworkConnection NamingAttributes ....................................23-7
Table 23-10. Protection NamingAttributes .........................................................23-8
Table 23-11. trafficDescriptor - NamingAttributes ............................................23-9
Table 23-12. Other Objects NamingAttributes ...................................................23-9
Table 24-1. ems - Provisioning Server Object Mapping...................................24-3
Table 24-2. ems - Attributes..............................................................................24-3
Table 24-3. emssession - Provisioning Server Object Mapping .......................24-4
Table 24-4. emssession - Attributes ..................................................................24-4
Table 24-5. multiLayerSubnetwork - Provisioning Server Object Mapping....24-5
Table 24-6. multiLayerSubnetwork- Attributes................................................24-5
Table 24-7. managedElement - Provisioning Server Object Mapping .............24-7
Table 24-8. managedElement - Attributes ........................................................24-7
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xv

Contents
Table 24-9. equipment Holder - Provisioning Server Object Mapping ............24-9

Table 24-10. equipment Holder - Attributes .......................................................24-9
Table 24-11. equipment - Provisioning Server Object Mapping ......................24-12
Table 24-12. equipment - Attributes .................................................................24-12
Table 24-13. terminationPoint - Attributes .......................................................24-14
Table 24-14. PTP - Provisioning Server Object Mapping ................................24-18
Table 24-15. PTP - Attributes ...........................................................................24-18
Table 24-16. CTP - Provisioning Server Object Mapping................................24-20
Table 24-17. CTP - Attributes...........................................................................24-20
Table 24-18. topologicalLink - Provisioning Server Object Mapping .............24-22
Table 24-19. topologicalLink - Attributes ........................................................24-22
Table 24-20. SubnetworkConnection - Provisioning Server Object Mapping .24-23
Table 24-21. SubnetworkConnection - Attributes ............................................24-23
Table 24-22. protection - Provisioning Server Object Mapping ......................24-29
Table 24-23. protection - Attributes..................................................................24-29
Table 24-24. trafficDescriptor - Attributes .......................................................24-34
Table 24-25. transmissionParameters - Attributes ...........................................24-36
Table 24-26. guiCutThrough - Attributes .........................................................24-37
Table 24-27. maintenanceOps - Attributes .......................................................24-38
Table 24-28. common - Attributes ....................................................................24-41
Table 25-1. Iterators for Provisioning Server TMF 814A Implementation ......25-1
Table A-1. TMF 814 Layer Rates for ATM ..................................................... A-3
Table A-2. PTP/CTP Naming for Provisioning Server PPort / LPort .............. A-4
Table B-1. Supported Layer Rates.................................................................... B-1
Table B-2. Transmission Paramenters for Layer Rates .................................... B-3
xvi6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

About This Guide

The Navis® EMS-CBGX TMF 814 Adapter Implementation Reference contains
detailed information about Navis EMS-CBGX TMF 814 Adapter.
Purpose
This document describes the modules, interfaces and data types for TMF 814.
The purpose of this document is to explain the support for TMF 814A specification
(version 2.1) and as such serves as the implementation reference for Provisioning
Server EMS. This document explains the Application Programming Interface (API)
and covers the following parameters for the Provisioning Server operations:
• Supported/UnSupported parameter
• In, Out and InOut parameter
These parameters provide the Provisioning Server mapping.
This document covers the TMF object naming for the Provisioning Server Objects. It
also covers the mapping of the TMF data types and the corresponding Provisional
Server object attributes.
What You Need to Know

This guide assumes that you have a working knowledge of network management and
provisioning operations.
To develop a NMS — an application that runs on a workstation in a Lucent network,

you need to be familiar with programming. You use the NMS to query and configure
switch nodes, cards, physical ports, circuits, and other objects.
Be sure to read the Software Release Notice (SRN) for NavisXtend Provisioning
Server. The SRN contains the most current product information and requirements.
Navis EMS-CBGX TMF 814 Adapter Implementation Reference xvii

About This Guide
What’s New in This Guide

This guide describes the following new product features in Navis EMS-CBGX TMF
814 Adapter Release 09.02.00.00, and includes the following changes:
Feature or Enhancement Description
New Features in This Release
Support for CBX 3500 switch Navis EMS-CBGX TMF 814 Adapter Release
09.02.00.00 supports CBX 3500 switch.
xviii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Beta Draft Confidential About This Guide
About the Provisioning Server Document Set

The following table describes the six guides that make up the NavisXtend
Provisioning Server document set.
Title Description
NavisXtend Provisioning Server This guide describes how to:

User’s Guide
• Install the Provisioning Server.
• Customize the Provisioning Server environment.
• Troubleshoot problems.
The guide also provides overview information about Provisioning Server
objects. Specific topics include:
• Object types supported by the Provisioning Server.
• Naming conventions for object types.
NavisXtend Provisioning Server CLI This guide is a reference for Provisioning Server CLI users. The guide
User’s Reference includes:
• CLI commands in a UNIX man-page format.
• Sample CLI commands for all Provisioning Server objects.
NavisXtend Provisioning Server This guide is a reference for programmers who are using the Provisioning
C++ API User’s Reference Server C++ API to design provisioning clients. The guide includes:
• C++ functions in a UNIX man-page format.
• C++ sample code.
NavisXtend Provisioning Server This guide is a reference for programmers who are using the Provisioning
Object Attribute Definitions Server CLI or C/C++ API. The guide includes:
User’s Reference
• Provisioning Server support for switch, card, LPort, PPort, and circuit
types.
• Alphabetical listing of Provisioning Server object attributes.
• Alphabetical listing of Provisioning Server enumerated data types.
NavisXtend Provisioning Server This guide lists Provisioning Server error codes and their associated text
Error Codes User’s Reference messages.
NavisXtend Provisioning Server This guide describes legacy C API functions. With Release 05.00.02.00,
Legacy C API Reference Lucent stopped developing C API and SNMP interfaces for new features.
Note, however, that Lucent still supports the legacy C API functions
described in this guide.
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xix

About This Guide
About the Navis EMS-CBGX TMF 814 Adapter

Document Set
The following table describes the guides that make up the Navis EMS-CBGX TMF
814 Adapter document set.
Title Description
Navis EMS-CBGX TMF 814 Adapter This guide is a reference for programmers using the Navis
Implementation Reference Guide (Product EMS-CBGX TMF 814 Adapter APIs to design NMS.
Code: 86011 Revision 000) The guide provides information about Navis EMS-CBGX TMF
814A Implementation for Provisioning Server objects. Specific
topics include:
• Object types supported by the Navis EMS-CBGX TMF 814
Adapter
• Naming conventions for object types.
Navis EMS-CBGX TMF 814 Adapter This guide describes how to:
Installation and Administration Guide
• Install the Navis EMS-CBGX TMF 814 Adapter.
(Product Code: 86012 Revision 000)
• Customize the Navis EMS-CBGX TMF 814 Adapter
environment.
• Troubleshoot problems.
xx6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

How to Use This Guide

This guide contains the following information:
Read To Learn About
Chapter 1 This chapter covers the system architecture,

requirements and TMF objects of Navis
EMS-CBGX TMF 814 Adapter.
“Chapter 2 to Chapter 22” These chapters covers the TMF operations for
modules such as emsMgr, emsSession,
equipment, multiLayerSubnetwork and others.
“Chapter 23” This chapter covers the TMF 814A Object

NamingAttributes for Provisioning Server.
“Chapter 24” This chapter covers the mapping of TMF data

types and the corresponding Provisioning
Server object attributes.
“Chapter 25” This chapter covers the iterators for

Provisioning Server TMF 814A
Implementation.
“Chapter 26” This chapter covers the troubleshooting

information for Navis EMS-CBGX TMF 814
Adapter.
“Appendix A” This appendix covers the layer rates mapping

of Navis EMS-CBGX TMF 814 Adapter and
Provisioning Server.
“Appendix B” This appendix covers the layer rates supported

for Navis EMS-CBGX TMF 814 Adapter.
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xxi

About This Guide
Conventions
This guide uses the following conventions, when applicable:
Convention Indicates Example
Courier Bold User input. > cvadd switch.xxxx

- Name
Courier Regular System output, filenames, Please wait...

and command names
<Courier Italics> Variable text output. <cdrompath>/docs/

atmcfg.pdf
Italics Book titles, new terms, and Navis EMS-CBGX TMF

emphasized text. 814 Adapter Installation
and Administration
Guide
Menu => Option A selection from a menu. Navis EMS-CBGX =>

Logon
A box around text A note, caution, or warning. See examples below.
Note – provide additional information or helpful suggestions that may apply to the
subject text.
Caution – notify the reader to proceed carefully to avoid possible equipment damage
! or data loss.
Warning – notify the reader to proceed carefully to avoid possible personal injury.
xxii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Related Documents
This section lists the related Lucent and third-party documentation that may be helpful
to read.
Lucent
• NavisXtend Provisioning Server Release 09.02.00.00 User’s Guide
(Product Code: 86000)
• NavisXtend Provisioning Server Release 09.02.00.00 Object Attribute Definitions
User’s Reference (Product Code: 86001)
• NavisXtend Provisioning Server Release 09.02.00.00 Command Line Interface
User’s Reference (Product Code: 86002)
• NavisXtend Provisioning Server Release 09.02.00.00 C++ API User’s Reference
• NavisXtend Provisioning Server Release 09.02.00.00 Error Codes User’s
Reference (Product Code: 86004)
• NavisXtend Provisioning Server Legacy C API Reference (Product Code: 80163)
• Navis EMS-CBGX TMF 814 Adapter Installation and Administration Guide
All manuals for Core Systems and the Master Glossary are available on the Core
Systems Documentation Library CD-ROM (Product Code: 80025).
Third Party
• TMF 513, TMF 608, TMF 814A
See the TeleManagement Forum (TM Forum) at www.tmforum.org for more
information.
Ordering Printed Manuals Online

You can order Core Switching manuals online. Use the following URL to access the
Lucent Bookstore:
http://www.lucentdocs.com
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xxiii

About This Guide
Customer Comments
Customer comments are welcome. Please respond in one of the following ways:
• Fill out the Customer Comment Form located at the back of this guide and return
it to us.
• E-mail your comments to cspubs@lucent.com
Technical Support
The Lucent Technical Assistance Center (TAC) is available to assist you with any
problems encountered while using this Lucent product. Log on to our Customer
Support web site and click on the ‘Contact Us’ link at the top right-hand side of the
page to obtain telephone numbers for the Lucent TAC in your region:
http://www.lucent.com/support
xxiv6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

1
Overview
This chapter covers the following:
• “System Architecture” on page 1-1
• “Requirements” on page 1-2
• “TMF Objects” on page 1-4
System Architecture
To interface with Provisioning Server, NMS interacts with the Navis EMS-CBGX
TMF 814 Adapter. The Navis EMS-CBGX TMF 814 Adapter is a multithreaded
application implementing TMF 814, and uses Lucent Provisioning Server EMS, Trap
Server along with Access Control Server through CORBA. The system architecture is
as depicted in the following illustration.
Figure 1-1. Navis EMS-CBGX TMF 814 Adapter Overview
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 1-1

Overview
Requirements
To configure Lucent Switches and access devices, use Navis EMS-CBGX for the
features not available in TMF 814. Also, there can be more than one Provisioning
Server or Access Control Server in the same network for load balancing and handling
more than 200 requests at a time. Navis EMS-CBGX can also be used with other
Lucent Servers for username/password and other features.
Requirements
EMS Requirements
The following objects show the Provisioning Server object hierarchy and should exist
(these objects should be added) in the Provisioning Server database:
Table 1-1. Provisioning Server Object Hierarchy

Object Parent-Child Objects
Customer No parent. Use “guiCutThrough Module” on page 14-1.
Network No parent. Use “guiCutThrough Module” on page 14-1.
switch Network (parent). Use “guiCutThrough Module” on

page 14-1.
card Use “provisionEquipment” on page 7-7.
pport Use “setTPData” on page 6-13 to modify LPort.
lport Use “setTPData” on page 6-13 to create, modify, or delete

LPort.
circuit Use “createAndActivateSNC” on page 5-6.
trafficDescriptor Use “trafficDescriptor Module” on page 12-1.
1-26/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Beta Draft Confidential Overview
Recommendations for Notification Service Usage
Recommendations for Notification Service Usage
General Recommendations
The following recommendations will be implemented:
• Use only Push Model in EMS.
• Use one channel (a set of processes of Navis EMS-CBGX TMF 814 Adapter
associated with a single Provisioning Server Database) to avoid ordering
problems.
• Use one notification service for a set of processes of Navis EMS-CBGX TMF 814
Adapter associated with a single Provisioning Server Database.
QoS and Admin Parameters

The following parameters should be used to provide an efficient way of using the
notification service (proven by test-runs):
• Use Persistency for EventReliability and ConnectionReliability parameter.
• All events shall have the same priority (0) to avoid ordering problems.
• Use FifoOrder for order and discard policy.
• Use FALSE for STARTTIMESUPPORTED.
• Use 0 for maximum batch size (batching is not used).
• Use 0 for Pacing Interval (batching is not used).
• The RejectNewEvents admin property should be set to TRUE so that the EMS
will know that the notification channel is not accepting new events anymore
• The TimeOut QoS property should be set to 30 minutes for NT_TCA and
NT_ALARM events; it should be set to 24 hours for all other events.
Constraints
Object Creation Notifications, Object Deletion Notifications, Attribute Value Changes
(AVC), and State Change Notifications will not be provided while using the Command
Line Interface (CLI).
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/041-3

Overview
TMF Objects
TMF Objects
Navis EMS-CBGX TMF 814 Adapter maps the Provisioning Server objects to the
TMF 814A defined objects in the best way possible. The following list contains the
conversion between the Provisioning Server objects and the TMF 814A Naming
Attributes:
Table 1-2. TMF Objects

Object Description
EMS Defines the Provisioning Server itself.
managedElement Represents the network elements (switches).
MultiLayer Represents the network.

Subnetwork
Topological Link Represents the trunk or PNNI links.
SNC (Subnetwork Represents Lucent circuits.

Connection)
PTP (Physical Symbolizes physical end points in Lucent switches.

Termination Point)
CTP (Connection Represents logical endpoint (LPort or IMA links).

Termination Point)
equipment Represents card and subcards on Lucent GX 550

switches.
equipmentHolder Represents card on Lucent BSTDX 9000 and CBX 500 /

CBX 3500 switches.
Protection Group Represents APS.
trafficDescriptor Represents the trafficDescriptor properties.
Transmission Represents the transmission parameters properties.

Parameters

Beta Draft Confidential Overview
Usage Information
Usage Information
Follow these instructions:
• Use Provisioning Server Command Line Interface (CLI), NavisCore, or Navis
EMS-CBGX for creating Trunk/PnniLink (Topological Link of TMF 814), and
also for switch addition, modification and deletion.
• For the value of each attribute pertaining to Provisioning Server object, use CLI or
guiCutThrough:
cvhelp <object> <attributeName>

• The attributes that Navis EMS-CBGX TMF 814 Adapter uses should follow the
conventions specified by Provisioning Server. For more information about the
attributes, see Provisioning Server Object Attribute Definition User’s Reference
documentation.

Overview
Usage Information

2
emsMgr Module
Table 2-1. List of Sections - emsMgr

Section Covers
Interfaces “EMSMgr_I” on page 2-2
Data Types “EMS_T” on page 24-3
Notifications “Notifications” on page 2-6
Note – PNNILink is not implemented for getAllTopLevelTopologicalLinks,

getAllTopLevelTopologicalLinkNames and getTopLevelTopologicalLink APIs for
emsMgr module in Navis EMS-CBGX TMF 814 Adapter Release 09.02.00.00.

emsMgr Module
Interfaces
Interfaces
EMSMgr_I
This interface covers the following:
• “getAllEMSAndMEActiveAlarms” on page 2-2
• “getAllEMSSystemActiveAlarms” on page 2-3
• “getAllTopLevelSubnetworks” on page 2-3
• “getAllTopLevelSubnetworkNames” on page 2-4
• “getAllTopLevelTopologicalLinks” on page 2-4
• “getAllTopLevelTopologicalLinkNames” on page 2-5
• “getTopLevelTopologicalLink” on page 2-5
• “getEMS” on page 2-6
Table 2-2. getAllEMSAndMEActiveAlarms
Operation getAllEMSAndMEActiveAlarms
Status Mandatory
Supported Yes
Exceptions globaldefs::ProcessingFailureException
• EXCPT_INTERNAL_ERROR
• EXCPT_TOO_MANY_OPEN_ITERATORS
in arguments • notifications::ProbableCauseList_T excludeProbCauseList
• notifications::PerceivedSeverityList_T excludeSeverityList
• unsigned long how_many
out / inout / return • notifications::EventList_T eventList

values
• notifications::EventIterator_I eventIt
Comments This operations returns the list of EMSAndMEActiveAlarms in

EventList_T.

Beta Draft Confidential emsMgr Module
Interfaces
Table 2-3. getAllEMSSystemActiveAlarms
Operation getAllEMSSystemActiveAlarms
Status Mandatory
Supported Yes
in arguments • notifications::PerceivedSeverityList_T excludeSeverityList
out / inout / return • notifications::EventList_T eventList

values
Comments This operation returns all the TCAs and system alarms list.
Table 2-4. getAllTopLevelSubnetworks
Operation getAllTopLevelSubnetworks
Status Mandatory
Supported Yes
in arguments unsigned long how_many
out / inout / return • multiLayerSubnetwork::SubnetworkList_T sList

values (see “SubnetworkList_T” on page 24-6)
• multiLayerSubnetwork::SubnetworkIterator_I sIt
Comments This operation returns the list of subnetworks in SubnetworkList_T.

emsMgr Module
Interfaces
Table 2-5. getAllTopLevelSubnetworkNames
Operation getAllTopLevelSubnetworkNames
Status Mandatory
Supported Yes
out / inout / return • globaldefs::NamingAttributeList_T nameList

values
• globaldefs::NamingAttributesIterator_I nameIt
Comments This operation returns the list of subnetwork object IDs as

NamingAttributeList_T.
Table 2-6. getAllTopLevelTopologicalLinks
Operation getAllTopLevelTopologicalLinks
Status Optional
Supported Yes
out / inout / return • topologicalLink::TopologicalLinkList_T topoList

values (see “TopologicalLinkList_T” on page 24-22)
• topologicalLink::TopologicalLinkIterator_I topoIt
Comments This operation returns a list (TopologicalLinkList_T) of trunks on all

the networks.

Beta Draft Confidential emsMgr Module
Interfaces
Table 2-7. getAllTopLevelTopologicalLinkNames
Operation getAllTopLevelTopologicalLinkNames
Status Optional
Supported Yes
• EXCPT_INVALID_INPUT
• EXCPT_ENTITY_NOT_FOUND
in arguments • unsigned long how_many
out / inout / return • globaldefs::NamingAttributeList_T nameList

values
Comments This operation returns the list of TopologicalLink object IDs (trunks
supported) as NamingAttributeList_T.
Table 2-8. getTopLevelTopologicalLink
Operation getTopLevelTopologicalLink
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T topoLinkName
out / inout / return topologicalLink::TopologicalLinkList_T topoLink

Comments This operation returns a top level topological link object structure
(trunks supported) as TopologicalLinkList_T.

emsMgr Module
Data Types
Table 2-9. getEMS

Operation getEMS
Status Mandatory
Supported Yes
in arguments None
out / inout / return EMS_T emsInfo

values (see “EMS_T” on page 24-3)
Comments This operation returns EMS_T object structure.
Data Types
The data types for emsMgr module are as follows:
• “EMS_T” on page 24-3
Notifications
Attribute Value Changes (AVC) and State Change Notifications will be provided when
appropriate.

3
emsSessionFactory Module
Table 3-1. List of Sections - emsSessionFactory

Section Covers
Interfaces “EmsSessionFactory_I” on page 3-2
Operations “getEmsSession” on page 3-2
Note – This module does not have any data types that represent second level
objects. Also, there are no specific notifications associated with this module.
This module also implements mtnmVersion::getVersion() API.

emsSessionFactory Module
Interfaces
Interfaces
EmsSessionFactory_I
• “getEmsSession” on page 3-2
Table 3-2. getEmsSession
Operation getEmsSession
Status Mandatory
Supported Yes
• EXCPT_ACCESS_DENIED
in arguments • string user
• string password
• nmsSession::NmsSession_I client
(see “NmsSession_I” on page 17-2)
out / inout / return emsSession::EmsSession_I emsSessionInterface

values (see “EmsSession_I” on page 4-2)
Comments The user and password are configured using Navis EMS-CBGX.
Otherwise, empty string should be used for user name and password.

4
emsSession Module
Table 4-1. List of Sections - emsSession

Section Covers
Interfaces “EmsSession_I” on page 4-2
Data Types “managerNames_T” on page 24-4

emsSession Module
Interfaces
Interfaces
EmsSession_I
• “getEventChannel” on page 4-2
• “getManager” on page 4-2
• “getSupportedManagers” on page 4-3
Table 4-2. getEventChannel
Operation getEventChannel
Status Mandatory
Supported Yes
in arguments None
out / inout / return CosNotifyChannelAdmin::EventChannel eventChannel

values
Comments This operation returns the IOR of the notification channel.
Table 4-3. getManager
Operation getManager
Status Mandatory
Supported Yes
in arguments string managerName
out / inout / return common::Common_I managerInterface

values (see “Common_I” on page 22-2)

Beta Draft Confidential emsSession Module
Data Types
Table 4-3. getManager (Continued)
Operation getManager
Comments This operation returns appropriate manager which must be narrowed by

the Helper class of Manager interface.
Table 4-4. getSupportedManagers
Operation getSupportedManagers
Status Mandatory
Supported Yes
in arguments string managerName
out / inout / return managerNames_T supportedManagerList

values (see “managerNames_T” on page 24-4)
Comments The TMF 814 (version 2.1) specifies 9 managers (4 optional and 5
mandatory).
This operation returns the object reference of each supported manager
implemented by Navis EMS-CBGX TMF 814 Adapter.
Data Types
The data types for emsSession module are as follows:
• managerNames_T on page 24-4
Notifications
appropriate.

emsSession Module
Notifications

5
multiLayerSubnetwork Module
Table 5-1. List of Sections - multiLayerSubnetwork
Section Covers
Interfaces • “MultiLayerSubnetworkMgr_I” on page 5-2
• “SubnetworkIterator_I” on page 5-19
Data Types • “MultiLayerSubnetwork_T” on page 24-5
• “EMSFreedomLevel_T” on page 24-6
• “SubnetworkList_T” on page 24-6
• “Topology_T” on page 24-6

Interfaces
Interfaces
• “MultiLayerSubnetworkMgr_I” on page 5-2
• “SubnetworkIterator_I” on page 5-19
MultiLayerSubnetworkMgr_I
The following table lists the interfaces:
• “activateSNC” on page 5-3
• “checkValidSNC” on page 5-3
• “createSNC” on page 5-4
• “deactivateSNC” on page 5-4
• “deleteSNC” on page 5-5
• “getAllTPPoolNames” on page 5-5
• “getAllTPPools” on page 5-6
• “getAssociatedTP” on page 5-6
• “createAndActivateSNC” on page 5-6
• “deactivateAndDeleteSNC” on page 5-8
• “getAllEdgePoints” on page 5-9
• “getAllEdgePointNames” on page 5-10
• “getAllManagedElements” on page 5-11
• “getAllManagedElementNames” on page 5-12
• “getAllSubnetworkConnections” on page 5-12
• “getAllSubnetworkConnectionNames” on page 5-13
• “getAllSubnetworkConnectionsWithTP” on page 5-14
• “getAllSubnetworkConnectionNamesWithTP” on page 5-14
• “getAllTopologicalLinks” on page 5-15
• “getAllTopologicalLinkNames” on page 5-16
• “getMultiLayerSubnetwork” on page 5-16
• “getRoute” on page 5-17
• “getSNC” on page 5-17
• “getSNCsByUserLabel” on page 5-18
• “getTopologicalLink” on page 5-18

Beta Draft Confidential multiLayerSubnetwork Module
Interfaces
Table 5-2. activateSNC
Operation activateSNC
Status Optional
Supported No
• EXCPT_NOT_IMPLEMENTED
in arguments • globaldefs::NamingAttributes_T sncName

(see “sncName” on page 23-7)
• subnetworkConnection::GradesOfImpact_T tolerableImpact
(see “GradesOfImpact_T” on page 24-24)
• EMSFreedomLevel_T emsFreedomLevel
(see “EMSFreedomLevel_T” on page 24-6)
out / inout / return • inout subnetworkConnection::TPDataList_T tpsToModify

values (see “TPDataList_T” on page 24-28)
• subnetworkConnection::SubnetworkConnection_T theSNC
(see “SubnetworkConnection_T” on page 24-23)
• string errorReason
Comments This operation throws EXCPT_NOT_IMPLEMENTED exception.
Table 5-3. checkValidSNC
Operation checkValidSNC
Status Optional
Supported No
in arguments • subnetworkConnection::SNCCreateData_T createData

(see “SNCCreateData_T” on page 24-25)
• subnetworkConnection::TPDataList_T tpsToModify
(see “TPDataList_T” on page 24-28)
• boolean considerResources
out / inout / return boolean valid

values

Interfaces
Table 5-4. createSNC
Operation createSNC
Status Optional
Supported No

out / inout / return • subnetworkConnection::SubnetworkConnection_T theSNC

values (see “SubnetworkConnection_T” on page 24-23)
Table 5-5. deactivateSNC
Operation deactivateSNC
Status Optional
Supported No



Interfaces
Table 5-5. deactivateSNC (Continued)
Operation deactivateSNC
Table 5-6. deleteSNC
Operation deleteSNC
Status Optional
Supported No
• EXCPT_NE_COMM_LOSS

out / inout / return None

values
Table 5-7. getAllTPPoolNames
Operation getAllTPPoolNames
Status Optional
Supported No
in arguments • globaldefs::NamingAttributes_T subnetworkName

(see “subnetworkName” on page 23-7)
out / inout / return • globaldefs::NamingAttributesList_T nameList

values

Interfaces
Table 5-8. getAllTPPools
Operation getAllTPPools
Status Optional
Supported No
in arguments • globaldefs::NamingAttributes_T subnetworkName

(see “subnetworkName” on page 23-7)
out / inout / return • terminationPoint::TerminationPointList_T tpList

values (see “TerminationPointList_T” on page 24-16)
• terminationPoint::TerminationPointIterator_I tpIt
Table 5-9. getAssociatedTP
Operation getAssociatedTP
Status Optional
Supported No
in arguments globaldefs::NamingAttributes_T tpName
out / inout / return terminationPoint::TerminationPointList_T tpList

Table 5-10. createAndActivateSNC
Operation createAndActivateSNC
Status Mandatory
Supported Yes

Interfaces
Table 5-10. createAndActivateSNC (Continued)
• EXCPT_OBJECT_IN_USE
• EXCPT_TIMESLOT_IN_USE
• EXCPT_PROTECTION_EFFORT_NOT_MET
• EXCPT_UNABLE_TO_COMPLY
• EXCPT_UNSUPPORTED_ROUTING_CONSTRAINTS
• EXCPT_USERLABEL_IN_USE


values (see “TPDataList_T”on page 24-28)

Interfaces
Table 5-10. createAndActivateSNC (Continued)
Comments This operation returns TPDataList_T and SubnetworkConnection_T.

EMSFL_CC_AT_SNC_LAYER (enum EMSFreedomLevel_T) and
EMSFL_TERMINATE_AND_MAP are supported in Navis
EMS-CBGX TMF 814 Adapter Release 09.02.00.00.
For all SNCs, aEnd is the source endpoint and zEnd is the
sink/destination endpoint.
Inputs for additionalInfo is as follows:
• For PMPCktRoot, PMPCktLeaf, PMPOffNetCktRoot,

PMPOffNetCktLeaf circuit types, following format should be
followed:
[aEnd/<name1>, value1], [aEnd/<name2>, value2]…….
[<zEnd=1/<name1>], [<zEnd=1/<name2>]
• For pvc, offnet and svcaddress circuit types, following format

should be followed.
[name1, value1], [name2, value2]….[nameN, valueN]
• For redirect PVC creation pvc2ndEndPoint should be provided in

the additionalInfo of the i/p structure as follows:
'/switch=<ipaddress>/shelf=1/slot=<1>/port=<1>/lport=<1>/vpi=<
1>/vci=<33>.' ( For ATM).
• For offnet circuit types, targetaddr and its related parameters should
be provided in the additionalInfo as input.
Specific attribute or flag is not required to create leaf only. Specify the
aEnd as existing root name and the zEnd as leaf name to create leaf
only.
If the root does not exist, Navis EMS-CBGX TMF 814 Adapter returns
root data. Otherwise, returns the leaf data in the 'out' parameter.
Table 5-11. deactivateAndDeleteSNC
Operation deactivateAndDeleteSNC
Status Mandatory
Supported Yes

Interfaces
Table 5-11. deactivateAndDeleteSNC
Operation deactivateAndDeleteSNC


Comments This operation deletes circuit and endpoint CTP depending on the
values of EMSFreedomeLevel_T.
EMSFL_CC_AT_SNC_LAYER (enum EMSFreedomLevel_T) and
EMSFL_TERMINATE_AND_MAP are supported in Navis
For EMSFL_TERMINATE_AND_MAP, deletion is not supported in
Navis EMS-CBGX TMF 814 Adapter Release 09.02.00.00.
This operation fetches circuit information and deletes the circuit. Navis
EMS-CBGX TMF 814 Adapter returns the retrieved information in the
out parameter (SubnetworkConnection_T).
Table 5-12. getAllEdgePoints
Operation getAllEdgePoints
Status Mandatory
Supported Yes

Interfaces
Table 5-12. getAllEdgePoints (Continued)
Operation getAllEdgePoints
in arguments • globaldefs::NamingAttributes_T subnetName

(see “subnetName” on page 23-7)
• transmissionParameters::LayerRateList_TlayerRateList
(see “LayerRateList_T” on page 24-36)
• transmissionParameters::LayerRateList_T connectionLayerRate
List (see “LayerRateList_T” on page 24-36)

Comments This operation returns an empty list.
Table 5-13. getAllEdgePointNames
Operation getAllEdgePointNames
Status Mandatory
Supported Yes

Interfaces
Table 5-13. getAllEdgePointNames (Continued)
Operation getAllEdgePointNames

• transmissionParameters::LayerRateList_T layerRateList

values
Table 5-14. getAllManagedElements

Operation getAllManagedElements
Status Mandatory
Supported Yes

out / inout / return • managedElement::ManagedElementList_T meList

values (see “ManagedElementList_T” on page 24-8)
• managedElement::ManagedElementIterator_I meIt
Comments This operation returns the list (ManagedElementList_T) of switches in

a particular network.

Interfaces
Table 5-15. getAllManagedElementNames

Operation getAllManagedElementNames
Status Mandatory
Supported Yes


values
Comments This operation returns the list of switch object IDs in a particular
network as NamingAttributesList_T.
Table 5-16. getAllSubnetworkConnections
Operation getAllSubnetworkConnections
Status Mandatory
Supported Yes

Interfaces
Table 5-16. getAllSubnetworkConnections (Continued)
Operation getAllSubnetworkConnections

• transmissionParameters::LayerRateList_T connectionRateList
(see “LayerRateList_T”on page 24-36)
out / inout / return • subnetworkConnection::SubnetworkConnectionList_T sncList

values (see “SubnetworkConnectionList_T” on page 24-28)
• subnetworkConnection::SNCIterator_I sncIt
Comments This operation returns the list of PVCs as

SubnetworkConnectionList_T.
Table 5-17. getAllSubnetworkConnectionNames

Operation getAllSubnetworkConnectionNames
Status Mandatory
Supported Yes


values

Interfaces
Operation getAllSubnetworkConnectionNames
Comments This operation returns the list of PVC object IDs as

NamingAttributesList_T.
Table 5-18. getAllSubnetworkConnectionsWithTP

Operation getAllSubnetworkConnectionsWithTP
Status Mandatory
Supported Yes
in arguments • globaldefs::NamingAttributes_T tpName
out / inout / return • subnetworkConnection::SubnetworkConnectionList_T sncList

• subnetworkConnection::SNCIterator_I sncIt
Comments This operation returns the list of PVCs as

SubnetworkConnectionList_T.
Only PPort and LPort as TP are supported in Navis EMS-CBGX TMF
814 Adapter Release 09.02.00.00.
Table 5-19. getAllSubnetworkConnectionNamesWithTP
Operation getAllSubnetworkConnectionNamesWithTP
Status Mandatory
Supported Yes

Interfaces
Table 5-19. getAllSubnetworkConnectionNamesWithTP (Continued)
Operation getAllSubnetworkConnectionNamesWithTP

values
Comments This operation returns the list of PVC object IDs as

Only PPort and LPort as TP are supported in Navis EMS-CBGX TMF
814 Adapter Release 09.02.00.00.
Table 5-20. getAllTopologicalLinks

Operation getAllTopologicalLinks
Status Optional
Supported Yes

Interfaces
Operation getAllTopologicalLinks

out / inout / return • topologicalLink::TopologicalLinkList_T topoList

• topologicalLink::TopologicalLinkIterator_I topoIt
Comments This operation returns the list of trunks in TopologicalLinkList_T.
Table 5-21. getAllTopologicalLinkNames

Operation getAllTopologicalLinkNames
Status Optional
Supported Yes


values
Comments This operation returns the list of trunk object IDs as

Table 5-22. getMultiLayerSubnetwork
Operation getMultiLayerSubnetwork
Status Mandatory
Supported Yes

Interfaces
Table 5-22. getMultiLayerSubnetwork (Continued)
Operation getMultiLayerSubnetwork
in arguments globaldefs::NamingAttributes_T subnetName

out / inout / return MultiLayerSubnetwork_T subnetwork

values (see “MultiLayerSubnetwork_T” on page 24-5)
Comments This operation returns the network object structure

(MultiLayerSubnetwork_T).
Table 5-23. getRoute

Operation getRoute
Status Optional
Supported No

• boolean includeHigherOrderCCs
out / inout / return subnetworkConnection::Route_T route

values (see “Route_T” on page 24-25)
Table 5-24. getSNC
Operation getSNC
Status Mandatory
Supported Yes

Interfaces
Table 5-24. getSNC (Continued)
Operation getSNC
in arguments globaldefs::NamingAttributes_T sncName
out / inout / return subnetworkConnection::SubnetworkConnection_T snc

values (see “SubnetworkConnection_T” on page 24-23)
Comments This operation returns the Provisioning Server circuit as

SubnetworkConnection_T object structure.
Table 5-25. getSNCsByUserLabel

Operation getSNCsByUserLabel
Status Mandatory
Supported No
in arguments string userLabel
out / inout / return subnetworkConnection::SubnetworkConnectionList_T sncList

Table 5-26. getTopologicalLink
Operation getTopologicalLink
Status Mandatory
Supported Yes

Interfaces
Table 5-26. getTopologicalLink (Continued)
Operation getTopologicalLink
in arguments globaldefs::NamingAttributes_T topoLinkName
out / inout / return topologicalLink::TopologicalLink_T topoLink

values (see “TopologicalLink_T” on page 24-22)
Comments This operation returns the Provisioning Server trunks as

TopologicalLink_T object structure (TopologicalLink_T).
SubnetworkIterator_I
See “Iterators for Provisioning Server TMF 814A Implementation” on page 25-1 for
information about the supported iterators.

Data Types
Data Types
The data types for multiLayerSubnetwork module are as follows:
• “EMSFreedomLevel_T” on page 24-6
• “MultiLayerSubnetwork_T” on page 24-5
• “SubnetworkList_T” on page 24-6
• “Topology_T” on page 24-6
Notifications
(AVC), and State Change Notifications will be provided when appropriate.

6
managedElement Module
Table 6-1. List of Sections - managedElement
Section Covers
Interfaces • “ManagedElementMgr_I” on page 6-2
• “ManagedElementIterator_I” on page 6-15
Data Types • “ManagedElement_T” on page 24-7
• “CommunicationState_T” on page 24-8
• “ManagedElementList_T” on page 24-8

Interfaces
Interfaces
ManagedElementMgr_I
• “getAllActiveAlarms” on page 6-3
• “getAllCrossConnections” on page 6-3
• “getAllManagedElements” on page 6-4
• “getAllManagedElementNames” on page 6-4
• “getAllPTPs” on page 6-5
• “getAllPTPNames” on page 6-6
• “getContainedCurrentTPs” on page 6-6
• “getContainedCurrentTPNames” on page 6-7
• “getContainedInUseTPs” on page 6-8
• “getContainedInUseTPNames” on page 6-9
• “getContainedPotentialTPs” on page 6-9
• “getContainedPotentialTPNames” on page 6-10
• “getContainingSubnetworkNames” on page 6-11
• “getContainingTPs” on page 6-11
• “getContainingTPNames” on page 6-12
• “getManagedElement” on page 6-12
• “getTP” on page 6-13
• “setTPData” on page 6-13

Beta Draft Confidential managedElement Module
Interfaces
Table 6-2. getAllActiveAlarms
Operation getAllActiveAlarms
Status Mandatory
Supported Yes
in arguments • globaldefs::NamingAttributes_T meName

(see “managedElement” on page 23-2)
• notifications::ProbableCauseList_T excludeProbCauseList
• notifications::PerceivedSeverityList_T excludeSeverityList
out / inout / • notifications::EventList_T eventList

return values
Comments This operation returns the list of ActiveAlarms in EventList_T.

Filtering for excludeProbCauseList and excludeSeverityList is not
supported in Navis EMS-CBGX TMF 814 Adapter Release
09.02.00.00.
Table 6-3. getAllCrossConnections
Operation getAllCrossConnections
Status Mandatory
Supported No
in arguments • globaldefs::NamingAttributes_T managedElementName


Interfaces
Table 6-3. getAllCrossConnections (Continued)
Operation getAllCrossConnections
out / inout / return • subnetworkConnection::CrossConnectList_T ccList

values
• subnetworkConnection::CCIterator_I ccIt
Comments This operation is not supported for Navis EMS-CBGX TMF 814
Adapter Release 09.02.00.00.
This operation returns an empty list.
Table 6-4. getAllManagedElements
Operation getAllManagedElements
Status Mandatory
Supported Yes
out / inout / return • managedElement::ManagedElementList_T meList

values (see “ManagedElementList_T” on page 24-8)
• managedElement::ManagedElementIterator_I meIt
Comments This operation returns the list of switches and all its attributes in
ManagedElementList_T.
Table 6-5. getAllManagedElementNames
Status Mandatory
Supported Yes

values

Interfaces
Comments This operation returns the list of switch object ids as

Table 6-6. getAllPTPs
Operation getAllPTPs
Status Mandatory
Supported Yes

• transmissionParameters::LayerRateList_T tpLayerRateList

Comments This operation returns the list of PTPs in TerminationPointList_T.

Interfaces
Table 6-7. getAllPTPNames
Operation getAllPTPNames
Status Mandatory
Supported Yes


values
Comments This operation returns the list of PTP object IDs as

Table 6-8. getContainedCurrentTPs
Operation getContainedCurrentTPs
Status Optional
Supported Yes

Interfaces
Operation getContainedCurrentTPs

Comments This operation returns the list of TPs in TerminationPointList_T.

This operation returns only LPorts. Only ATM (LR_ATM_NI) and
Frame Relay (LR_FR_IF) layer rates are supported.
Table 6-9. getContainedCurrentTPNames
Operation getContainedCurrentTPNames
Status Optional
Supported Yes

Interfaces
Operation getContainedCurrentTPNames

values
Comments This operation returns the list of TPs as NamingAttributesList_T.

This operation returns only LPorts. Only ATM (LR_ATM_NI) and
Frame Relay (LR_FR_IF) layer rates are supported.
Table 6-10. getContainedInUseTPs

Operation getContainedInUseTPs
Status Mandatory
Supported Yes

Comments This operation returns the object IDs of TPs (includes the TPs that are
in use by the circuit) in TerminationPointList_T.
Only ATM and Frame Relay layer rates are supported.

Interfaces
Table 6-11. getContainedInUseTPNames
Operation getContainedInUseTPNames
Status Mandatory
Supported Yes

values
Comments This operation returns the object IDs of TP (includes the TPs that are in
use by the circuit) as NamingAttributesList_T.
Table 6-12. getContainedPotentialTPs

Operation getContainedPotentialTPs
Status Mandatory
Supported Yes

Interfaces
Operation getContainedPotentialTPs

Comments This operation returns the object IDs of TPs (includes the TPs that are
configured and non-configured) in TerminationPointList_T.
If the input layer rate is LR_ATM_VP, getContainedPotentialTPs on
PPort returns VPI circuit endpoint.
If the input layer rate is LR_ATM_VC, getContainedPotentialTPs on
PPort returns VCI circuit endpoint on that VPI.
If the input laye rate is LR_ATM_NI, getContainedPotentialTPs on
PPort returns direct LPort, virtual LPort and OpticellTrunk LPort.
Similar behavior is supported for Frame Relay layer rate.
Table 6-13. getContainedPotentialTPNames

Operation getContainedPotentialTPNames
Status Mandatory
Supported Yes

Interfaces
Operation getContainedPotentialTPNames

values
Comments This operation returns the object ids of TPs (includes the TPs that are
configured and non-configured) as NamingAttributesList_T.
If the input layer rate is LR_ATM_VP, getContainedPotentialTPs on
PPort returns VPI circuit endpoint.
If the input layer rate is LR_ATM_VC, getContainedPotentialTPs on
PPort returns VCI circuit endpoint on that VPI.
If the input laye rate is LR_ATM_NI, getContainedPotentialTPs on
PPort returns direct LPort, virtual LPort and OpticellTrunk LPort.
Similar behavior is supported for Frame Relay layer rate.
Table 6-14. getContainingSubnetworkNames
Operation getContainingSubnetworkNames
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T managedElement

out / inout / return globaldefs::NamingAttributesList_T subnetNames

values (see “subnetNames” on page 23-7)
Comments This operation returns the network as NamingAttributesList_T.
Table 6-15. getContainingTPs

Operation getContainingTPs
Status Mandatory
Supported Yes

Interfaces
Operation getContainingTPs
out / inout / return terminationPoint::TerminationPointList_T tpList

Comments This operation returns the TP object structure as

TerminationPointList_T.
This operatio returns the hierarchy of TPs up to the parent TP level.
Table 6-16. getContainingTPNames
Operation getContainingTPNames
Status Mandatory
Supported Yes
out / inout / return globaldefs::NamingAttributesList_T tpNameList

values
Comments This operation returns the list of TP objects structure (as

NamingAttributesList_T) up to the parent object of the input TP.
Table 6-17. getManagedElement

Operation getManagedElement
Status Mandatory

Interfaces
Operation getManagedElement
Supported Yes
in arguments globaldefs::NamingAttributes_T managedElementName

out / inout / return managedElement::ManagedElement_T me

values (see “ManagedElement_T” on page 24-7)
Comments This operation returns the ManagedElement object structure

(ManagedElement_T).
Table 6-18. getTP
Operation getTP
Status Mandatory
Supported Yes
out / inout / return terminationPoint::TerminationPoint_T tp

values (see “TerminationPoint_T” on page 24-14)
Comments This operation returns the TP object structure (TerminationPoint_T).
Table 6-19. setTPData

Operation setTPData
Status Mandatory

Interfaces
Operation setTPData
Supported Yes
in arguments subnetworkConnection::TPData_T tpInfo

(see “TPData_T” on page 24-28)
out / inout / return terminationPoint::TerminationPoint_T modifiedTP

values (see “TerminationPoint_T” on page 24-14)
Comments This operation returns the TP object structure (TerminationPoint_T).

Navis EMS-CBGX TMF 814 Adapter creates LPort (CTP), modifies
LPort (CTP) and deletes (LPort) based on the tpMappingMode.
If the tpMappingMode is TM_TERMINATED_AND_
AVAILABLE_FOR_MAPPING, Navis EMS-CBGX TMF 814
Adapter does the following:
• If the LPort Name attribute is specified, creates the LPort.
• If the LPortName attribute is not specified, modifies the LPort.
If the tpMappingMode is TM_NEITHER_TERMINATED_AND_
AVAILABLE_FOR_MAPPING, Navis EMS-CBGX TMF 814
Adapter deletes the LPort.
Modify Channel operation of Provisioning Server is supported when
tpMappingMode is TM_TERMINATED_AND_AVAILABLE_
FOR_MAPPING.
Modify PPort operation of Provisioning Server is supported when
tpMappingMode is TM_NA.
There are no add or delete operations for Channel and PPort.
All cards on BSTDX 8000, BSTDX 9000, CBX 500 / CBX 3500, and
GX 550 are EquipmentHolders and have only one Equipment in it. GX
550 EquipmentHolder can have maximum four subslots depending on
the card type, defined type and installAndExpectedEquipmentType,
which contains only one equipment in it.
Lucent proprietary attributes are used as transmissionParams.
LPort's "Name" and "ServiceType" attributes are "Not Best Effort"
parameter/attribute, (because once LPort is created, these two
parameters cannot be changed).

Data Types
ManagedElementIterator_I
Data Types
The data types for managedElement Manager module are as follows:
• “ManagedElement_T” on page 24-7
• “CommunicationState_T” on page 24-8
• “ManagedElementList_T”on page 24-8
Notifications
Attribute Value Changes (AVC), and State Change Notifications will be provided
when appropriate.

Termination Point Usage

Following illustration depicts the Termination Point usage.
Figure 6-1. Termination Point Usage
Current TPs refer to configured TPs. Potential TPs refer to configured and
non-configured TPs. InUse TPs refer to TPs in use by the child object (for example,
circuit is child for the LPort).
The following table describes the examples for InUseTP, CurrentTP and PotentialTP
shown in the illustration.
Termination Point Type Examples from the Illustration
InUseTP (PPort) • Channel 1
• Channel 3
• LPort 1
InUseTP (Channel 1) LPort 1
InUseTP (Channel 2) Empty
InUseTP (Channel 3) Empty

Termination Point Type Examples from the Illustration
CurrentTP (PPort) • LPort 1
• LPort 2
• LPort 4
• LPort 5
CurrentTP (Channel 1) • LPort 1
• LPort 2
CurrentTP (Channel 2) Empty
CurrentTP (Channel 3) • LPort 4
• LPort 5
PotentialTP (PPort) (No Layer Rate) • Pseudo LPort 3
• Pseudo LPort 6
• LPort 2
• LPort 4
• LPort 5
PotentialTP (Channel 1) • LPort 1
• LPort 2
• Pseudo LPort 3
PotentialTP (Channel 2) • Pseudo LPort 6
PotentialTP (Channel 3) • LPort 4
• LPort 5


7
equipment Module
Table 7-1. List of Sections - equipment

Section Covers
Interfaces • “EquipmentInventoryMgr_I” on page 7-2
• “EquipmentOrHolderIterator_I” on page 7-9
Data Types • “EQTCreateData_T” on page 24-13
• “Equipment_T” on page 24-12
• “EquipmentHolder_T” on page 24-9
• “EquipmentHolderType_T” on page 24-10
• “EquipmentObjectType_T” on page 24-10
• “EquipmentObjectTypeList_T” on page 24-10
• “EquipmentOrHolder_T” on page 24-10
• “EquipmentOrHolderList_T” on page 24-10
• “EquipmentTypeQualifier_T” on page 24-10
• “HolderState_T” on page 24-11
• “ServiceState_T” on page 24-11
Mandatory Provisioning “Mandatory Provisioning Server Object Attributes” on

Server Object Attributes page 7-10

equipment Module
Interfaces
Interfaces
EquipmentInventoryMgr_I
• “getAllEquipment” on page 7-3
• “getAllEquipmentNames” on page 7-3
• “getAllSupportedPTPs” on page 7-4
• “getAllSupportedPTPNames” on page 7-5
• “getAllSupportingEquipment” on page 7-5
• “getAllSupportingEquipmentNames” on page 7-6
• “getContainedEquipment” on page 7-6
• “getEquipment” on page 7-7
• “provisionEquipment” on page 7-7
• “setAlarmReportingOff” on page 7-8
• “setAlarmReportingOn” on page 7-9
• “unprovisionEquipment” on page 7-9

Beta Draft Confidential equipment Module
Interfaces
Table 7-2. getAllEquipment
Operation getAllEquipment
Status Mandatory
Supported Yes
in arguments • gobaldefs::NamingAttributes_T meOrHolderName

(see “managedElement” on page 23-2 and “Equipment Holder” on
page 23-3)
out / inout / return • EquipmentOrHolderList_T eqList

values (see “equipment” on page 24-12 and “equipment Holder” on page
24-9)
• EquipmentorHolderIterator_I eqIt
Comments This operation returns the list of equipments (cards) in

EquipmentOrHolderList_T.
Table 7-3. getAllEquipmentNames
Operation getAllEquipmentNames
Status Mandatory
Supported Yes

equipment Module
Interfaces
Operation getAllEquipmentNames
in arguments • globaldefs::NamingAttributes_T meOrHolderName

(see “managedElement” on page 23-2 and “equipment Holder” on
page 23-3)

values
(see NamingAttributesIterator_I on page)
Comments This operation returns the list of card object IDs as

Table 7-4. getAllSupportedPTPs
Operation getAllSupportedPTPs
Status Mandatory
Supported Yes
in arguments • globaldefs::NamingAttributes_T equipmentName

(see “equipment” on page 23-3)

• terminationPoint:TerminationPointIterator_I tpIt
Comments This operation returns the list (TerminationPointList_T) of physical

ports on the switch.

Interfaces
Table 7-5. getAllSupportedPTPNames
Operation getAllSupportedPTPNames
Status Mandatory
Supported Yes
in arguments • globaldefs::NamingAttributes_T equipmentName


values
Comments This operation returns the list of physical ports object IDs on the switch
as NamingAttributeList_T.
Table 7-6. getAllSupportingEquipment
Operation getAllSupportingEquipment
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T ptpName

(see “Physical Termination Point” on page 23-4)
out / inout / return EquipmentOrHolderList_T eqList

24-9)

equipment Module
Interfaces
Table 7-6. getAllSupportingEquipment (Continued)
Operation getAllSupportingEquipment
Comments This operation returns the list of cards in EquipmentOrHolder_T

structure
Table 7-7. getAllSupportingEquipmentNames
Operation getAllSupportingEquipmentNames
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T ptpName

(see “Physical Termination Point” on page 23-4)
out / inout / return globaldefs::NamingAttributesList_T nameList

values
Comments The operation returns the list of equipment object IDs and equipment
holder object IDs as NamingAttributesList_T.
Table 7-8. getContainedEquipment
Operation getContainedEquipment
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T equipmentHolder Name

(see “equipment Holder” on page 23-3)

Interfaces
Table 7-8. getContainedEquipment (Continued)
Operation getContainedEquipment
out / inout / return EquipmentOrHolderList_T equipmentOrHolderList

24-9)
Comments This operation returns the equipment and equipmentHolders (cards, or

cards and subcards). If the subcards do not exist, returns only card in
equipmentOrHolderList.
Table 7-9. getEquipment
Operation getEquipment
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T equipmentOrHolderName

(see “equipment” on page 23-3 and “equipment Holder” on page 23-3)
out / inout / return EquipmentOrHolderList_T equip

values
Comments The operation returns the equipment and equipment Holder object
structure (EquipmentOrHolderList_T).
Table 7-10. provisionEquipment
Operation provisionEquipment
Status Optional
Supported Yes

equipment Module
Interfaces
Table 7-10. provisionEquipment (Continued)
Operation provisionEquipment
in arguments EQTCreateData_Tequipment CreateData

(see “EQTCreateData_T” on page 24-13)
out / inout / return Equipment_T createdEquipment

values (see “Equipment_T” on page 24-12)
Comments This operation is required after a card is inserted into a network

element, since Provisioning Server does not support automatic
provisioning.
Provisioning Server needs to receive a modifyObject from the Navis
EMS-CBGX TMF 814 Adapter to put the card into the database and
create the PPorts.
This operation is used to create and modify cards and subcards. This
operation returns Equipment_T object structure.
Table 7-11. setAlarmReportingOff
Operation setAlarmReportingOff
Status Optional
Supported No


values

Interfaces
Table 7-12. setAlarmReportingOn

Operation setAlarmReportingOn
Status Optional
Supported No


values
Table 7-13. unprovisionEquipment
Operation unprovisionEquipment
Status Optional
Supported Yes
• EXCPT_NE_COMM_LOSS_IN
in arguments globaldefs::NamingAttributes_T equipmentName


values
Comments This call will return EXCPT_OBJECT_IN_USE if the CTPs are

configured on the card. This operation is similar to removing a card.
EquipmentOrHolderIterator_I
information about the supported iterators

equipment Module
Data Types
Data Types
The data types for equipment module are as follows:
• “EQTCreateData_T” on page 24-13
• “Equipment_T” on page 24-12
• “EquipmentHolder_T” on page 24-9
• “EquipmentHolderType_T” on page 24-10
• “EquipmentObjectType_T” on page 24-10
• “EquipmentObjectTypeList_T” on page 24-10
• “EquipmentOrHolder_T” on page 24-10
• “EquipmentOrHolderList_T” on page 24-10
• “EquipmentTypeQualifier_T” on page 24-10
• “HolderState_T” on page 24-11
• “ServiceState_T” on page 24-11
Notifications
(AVC), and State Change Notifications will be provided when appropriate.
Mandatory Provisioning Server Object Attributes

The following table lists the mandatory Provisioning Server object attributes.
Table 7-14. Mandatory Provisioning Server Object Attributes

Attribute Name Filled in Data Data Type Default Access Range of Values
Structure Value
DefinedType EquipmentObject String Read-Write Includes: Empty,

Type_T 6PortV35,
1Port24ChanFractT1,
installed
AxDs3Fr, AxAlarm,
Equipment AxDsp2b.
ObjectType
For a complete listing of
the values, use the
following CLI command:
cvhelp card
-definedtype

8
terminationPoint Module
Table 8-1. List of Sections - terminationPoint

Section Covers
Interfaces “TerminationPointIterator_I” on page 8-2
Data Types • “Directionality_T” on page 24-14
• “TerminationMode_T” on page 24-14
• “TerminationPointList_T” on page 24-16
• “TPConnectionState_T” on page 24-16
• “TPProtectionAssociation_T” on page 24-16
• “TPType_T” on page 24-17
• “TerminationPoint_T” on page 24-20
Note – There are no specific notifications associated with this module.

terminationPoint Module
Interfaces
Interfaces
TerminationPointIterator_I
Data Types
The data types for terminationPoint module are as follows:
• “Directionality_T” on page 24-14
• “TerminationMode_T” on page 24-14
• “TerminationPointList_T” on page 24-16
• “TPConnectionState_T” on page 24-16
• “TPProtectionAssociation_T” on page 24-16
• “TPType_T” on page 24-17
• “TerminationPoint_T” on page 24-20

9
topologicalLink Module
Table 9-1. List of Sections - topologicalLink

Section Covers
Interfaces “TopologicalLinkIterator_I” on page 9-2
Data Types • “TopologicalLink_T” on page 24-22
• “TopologicalLinkList_T” on page 24-22
Note – If you use CLI or guiCutThrough to create, delete and modify Topological
Links, a fully-standard non-proprietary (except for proprietary EMS/NE data) TMF
814 Version 2.1 implementation is required.

topologicalLink Module
Interfaces
Interfaces
TopologicalLinkIterator_I
Data Types
The data types for topologicalLink module are as follows:
• “TopologicalLink_T” on page 24-22
• “TopologicalLinkList_T” on page 24-22

10
subnetworkConnection Module
Table 10-1. List of Sections - subnetworkConnection
Section Covers
Interfaces • CCIterator (Not supported)
• “SNCIterator_I” on page 10-2
Data Types • “SubnetworkConnection_T” on page 24-23
• “GradesOfImpact_T” on page 24-24
• “NetworkRouted_T” on page 24-24
• “ProtectionEffort_T” on page 24-25
• “Reroute_T” on page 24-25
• “RerouteChangeEvent_T” on page 24-25
• “Resource_T” on page 24-25
• “ResourceList_T” on page 24-25
• “Route_T” on page 24-25
• “SNCCreateData_T” on page 24-25
• “SNCState_T” on page 24-27
• “SNCType_T” on page 24-27
• “StaticProtectionLevel_T” on page 24-27
• “SubnetworkConnectionList_T” on page 24-28
• “TPData_T” on page 24-28
• “TPDataList_T” on page 24-28

subnetworkConnection Module
Interfaces
Interfaces
SNCIterator_I
Data Types
The data types for subnetworkConnection module are as follows:
• “SubnetworkConnection_T” on page 24-23
• “GradesOfImpact_T” on page 24-24
• “NetworkRouted_T” on page 24-24
• “ProtectionEffort_T” on page 24-25
• “Reroute_T” on page 24-25
• “RerouteChangeEvent_T” on page 24-25
• “Resource_T” on page 24-25
• “ResourceList_T” on page 24-25
• “Route_T” on page 24-25
• “SNCCreateData_T” on page 24-25
• “SNCState_T” on page 24-27
• “SNCType_T” on page 24-27
• “StaticProtectionLevel_T” on page 24-27
• “SubnetworkConnectionList_T” on page 24-28
• “TPData_T” on page 24-28
• “TPDataList_T” on page 24-28

11
protection Module
Table 11-1. List of Sections - protection
Section Covers
Interfaces • “ProtectionGroupIterator_I” on page 11-2
• “ProtectionMgr_I” on page 11-2
Data Types • “ProtectionCommand_T” on page 24-31
• “ProtectionGroup_T” on page 24-29
• “ProtectionGroupList_T” on page 24-31
• “ProtectionGroupType_T” on page 24-31
• “ProtectionSchemeState_T’ on page 24-31
• “ProtectionType_T” on page 24-31
• “ReversionMode_T” on page 24-32
• “SwitchData_T” on page 24-32
• “SwitchDataList_T” on page 24-32
• “SwitchReason_T” on page 24-33

protection Module
Interfaces
Interfaces
ProtectionGroupIterator_I
ProtectionMgr_I
• “getAllNUTTPNames” on page 11-2
• “getAllPreemptibleTPNames” on page 11-3
• “getAllProtectedTPNames” on page 11-3
• “getAllProtectionGroups” on page 11-4
• “getProtectionGroup” on page 11-4
• “performProtectionCommand” on page 11-5
• “performProtectionCommand” on page 11-5
Table 11-2. getAllNUTTPNames

Operation getAllNUTTPNames
Status Optional
Supported No
in arguments • globaldefs::NamingAttributes_T pgName

(see “protectiongroupName” on page 23-8)

values

Beta Draft Confidential protection Module
Interfaces
Table 11-3. getAllPreemptibleTPNames

Operation getAllPreemptibleTPNames
Status Optional
Supported No


values
Table 11-4. getAllProtectedTPNames

Operation getAllProtectedTPNames
Status Optional
Supported No


values

protection Module
Interfaces
Table 11-5. getAllProtectionGroups

Operation getAllProtectionGroups
Status Mandatory
Supported Yes
in arguments • globaldefs::NamingAttributes_T meName

out / inout / return • ProtectionGroupList_T pgList

values (see “ProtectionGroupList_T” on page 24-31)
• ProtectionGroupIterator_I pgpIt
Comments This operation returns the list of ProtectionGroups in

ProtectionGroupList_T.
Table 11-6. getProtectionGroup

Operation getProtectionGroup
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T pgName

(see “protectiongroup Name” on page 23-8)
out / inout / return ProtectionGroup_T protectionGroup

values (see “ProtectionGroup_T” on page 24-29)

Beta Draft Confidential protection Module
Interfaces
Operation getProtectionGroup
Comments This operation returns the ProtectionGroup_T object structure

(ProtectionGroup_T).
Table 11-7. performProtectionCommand

Operation performProtectionCommand
Status Optional
Supported Yes
in arguments • ProtectionCommand_T protectionCommand

(see “ProtectionCommand_T” on page 24-31)
• globaldefs::NamingAttributes_T reliableSinkCtpOrGroupName
• globaldefs::NamingAttributes_T fromTp
• globaldefs::NamingAttributes_T toTp
out / inout / return SwitchData_T switchData

values (see “SwitchData_T” on page 24-32)
Comments Optional, but already in place for APS and servicename bindings. This
operation returns SwitchData_T.
Table 11-8. retrieveSwitchData
Operation retrieveSwitchData
Status Optional
Supported Yes

protection Module
Data Types
Table 11-8. retrieveSwitchData (Continued)
Operation retrieveSwitchData
in arguments globaldefs::NamingAttributes_T reliableSinkCtpOrGroupName
out / inout / return SwitchDataList_T switchData

values (see “SwitchDataList_T” on page 24-32)
Comments This operation is not implemented in Navis EMS-CBGX TMF 814

Data Types
The data types for protection module are as follows:
• “ProtectionCommand_T” on page 24-31
• “ProtectionGroup_T” on page 24-29
• “ProtectionGroupList_T” on page 24-31
• “ProtectionGroupType_T” on page 24-31
• “ProtectionSchemeState_T’ on page 24-31
• “ProtectionType_T” on page 24-31
• “ReversionMode_T” on page 24-32
• “SwitchData_T” on page 24-32
• “SwitchDataList_T” on page 24-32
• “SwitchReason_T” on page 24-33
Notifications
appropriate.

12
trafficDescriptor Module
Table 12-1. List of Sections - trafficDescriptor

Section Covers
Interfaces • “TrafficDescriptorMgr_I” on page 12-2
• “TrafficDescriptorIterator_I” on page 12-5
Data Types • “ServiceCategory_T” on page 24-34
• TDCreateData_T
• “TrafficDescriptor_T” on page 24-34
• “TrafficDescriptorList_T” on page 24-34
• “TrafficParameterList_T” on page 24-35
Mandatory Provisioning “Mandatory Provisioning Server Object Attributes” on

Server Object Attributes page 12-7

Interfaces
Interfaces
TrafficDescriptorMgr_I
• “createTrafficDescriptor” on page 12-2
• “deleteTrafficDescriptor” on page 12-3
• “getAllTrafficDescriptors” on page 12-3
• “getAllTrafficDescriptorNames” on page 12-4
• “getAssociatedCTPs” on page 12-4
• “getTrafficDescriptor” on page 12-5
Table 12-2. createTrafficDescriptor

Operation createTrafficDescriptor
Status Optional
Supported No
in arguments TDCreateData_T newTDCreateData
out / inout / return TrafficDescriptor_T newTrafficDescriptor

values (see “TrafficDescriptor_T” on page 24-34)

Beta Draft Confidential trafficDescriptor Module
Interfaces
Table 12-3. deleteTrafficDescriptor

Operation deleteTrafficDescriptor
Status Optional
Supported No
in arguments globaldefs::NamingAttributes_T descriptorName

(see “descriptorName” on page 23-9)

values
Table 12-4. getAllTrafficDescriptors

Operation getAllTrafficDescriptors
Status Mandatory
Supported Yes
in arguments • unsigned long how_many
out / inout / return • TrafficDescriptorList_T trafficDescIt

values (see “TrafficDescriptorList_T” on page 24-34)
• TrafficDescriptorIterator_I trafficDescIt
Comments This operation returns the list of all mandatory trafficDescriptors (only
on network.0.0.0.0 level) in TrafficDescriptorList_T.

Interfaces
Table 12-5. getAllTrafficDescriptorNames

Operation getAllTrafficDescriptorNames
Status Mandatory
Supported Yes

values
Comments This operation returns the list of TrafficDescriptors object IDs as

Table 12-6. getAssociatedCTPs

Operation getAssociatedCTPs
Status Mandatory
Supported No
in arguments • globaldefs::NamingAttributes_T TrafficDescriptorName

(see “trafficDescriptorName” on page 23-9)
• in unsigned long how_many


Data Types
Operation getAssociatedCTPs
Table 12-7. getTrafficDescriptor

Operation getTrafficDescriptor
Status Mandatory
Supported Yes
in arguments globaldefs::NamingAttributes_T tdName
out / inout / return TrafficDescriptor_T td

values (see “TrafficDescriptor_T” on page 24-34)
Comments This operation returns the TrafficDescriptor_T object structure

(TrafficDescriptor_T).
TrafficDescriptorIterator_I
Data Types
The data types for trafficDescriptor module are as follows:
• “ServiceCategory_T” on page 24-34
• TDCreateData_T
• “TrafficDescriptor_T” on page 24-34
• “TrafficDescriptorList_T” on page 24-34
• “TrafficParameterList_T” on page 24-35

Notifications
Notifications
appropriate.


The following table lists the mandatory Provisioning Server object attributes.
Table 12-8. Mandatory Object Attributes for TDCreateData_T
Structure Value
CBR TDCreateData_T cvClassOfSrv 5040 Create-Only Values can be between 1

and 16,777,215.
VBRRealTime TDCreateData_T cvClassOfSrv 5040 Create-Only Values can be between 1

and 16,777,215.
VBRNonReal TDCreateData_T cvClassOfSrv 5040 Create-Only Values can be between 1

Time and 16,777,215.
UBR TDCreateData_T cvClassOfSrv 5040 Create-Only Values can be between 1

and 16,777,215.
UnspCBR TDCreateData_T cvClassOfSrv Create-Only
UnspVBRNrt TDCreateData_T cvClassOfSrv Create-Only
UnspBestEffort TDCreateData_T cvClassOfSrv Create-Only
Table 12-9. Mandatory Object Attributes for TrafficParameterList_T
Structure Value
PcrClp0PcrClp01 TrafficParameter
List_T
PcrClp0PcrClp01 TrafficParameter cvClassOfSrv Create-Only

Tag List_T
PcrClp01ScrClp0 TrafficParameter cvClassOfSrv Create-Only
MbsClp0 List_T
MbsClp0Tag List_T
PcrClp01 TrafficParameter cvClassOfSrv Create-Only
List_T

1MbsClp01 List_T
BestEffort TrafficParameter cvClassOfSrv Create-Only
List_T

Table 12-9. Mandatory Object Attributes for TrafficParameterList_T (Continued)
Structure Value
PcrClp0McrClp0 TrafficParameter
List_T
BestEffort TrafficParameter
Tagging List_T

13
transmissionParameters Module
Table 13-1. List of Sections - transmissionParameters

Section Covers
Data Types • “LayeredParameterList_T” on page 24-36
• “LayeredParameters_T” on page 24-36
• “LayerRate_T” on page 24-36
• “LayerRateList_T” on page 24-36

transmissionParameters Module
Data Types
Data Types
The data types for transmissionParameters module are as follows:
• “LayeredParameterList_T” on page 24-36
• “LayeredParameters_T” on page 24-36
• “LayerRate_T” on page 24-36
• “LayerRateList_T” on page 24-36
Note – All Provisioning Server attributes that do not map to TMF 814
transmissionParameters will appear as transmissionParameters input or output to
the API call, where transmissionParameters are used.

14
guiCutThrough Module
Table 14-1. List of Sections - guiCutThrough

Section Covers
Interfaces “GuiCutThroughMgr_I” on page 14-2
Data Types • “GCTProfileInfo_T” on page 24-37
• “GuiCutThroughData_T” on page 24-37
• “GuiCutThroughDataList_T” on page 24-37
• “ServerLaunchCapability_T” on page 24-37

Interfaces
Interfaces
GuiCutThroughMgr_I
• “destroyGCT” on page 14-2
• “getGCTProfileInfo” on page 14-2
• “launchGCT” on page 14-3
Table 14-2. destroyGCT

Operation destroyGCT
Status Optional
Supported No
in arguments string displayAddress

values
Table 14-3. getGCTProfileInfo

Operation getGCTProfileInfo
Status Mandatory
Supported Yes
in arguments None
out / inout / return GCTProfileInfo_T gctProfileInfo

values (see “gctProfileInfo” on page 24-37)
Comments This operation returns the GCTProfileInfo_T object structure.

Beta Draft Confidential guiCutThrough Module
Data Types
Table 14-4. launchGCT

Operation launchGCT
Status Optional
Supported No
in arguments • globaldefs::NamingAttributes_T objectName

• string gctContext
• globaldefs::NVSList_T userInfo
• string displayAddress
• globaldefs::NVSList_T additionalInputInfo
out / inout / return • boolean closingEnabled

values
• globaldefs::NVSList_T additionalOutputInfo
Data Types
The data types for guiCutThrough module are as follows:
• “GCTProfileInfo_T” on page 24-37
• “GuiCutThroughData_T” on page 24-37
• “GuiCutThroughDataList_T” on page 24-37
• “ServerLaunchCapability_T” on page 24-37
Notifications
appropriate.

Notifications

15
maintenanceOps Module
Table 15-1. List of Sections - maintenanceOps

Section Covers
Interfaces • “CurrentMaintenanceOperationIterator_I” on
page 15-2
• “MaintenanceMgr_I” on page 15-2
Data Types • “CurrentMaintenanceOperation_T” on page 24-38
• “CurrentMaintenanceOperationList_T” on page
24-39
• “MaintenanceOperation_T” on pagr 24-39
• “MaintenanceOperationMode_T” on page 24-40

Interfaces
Interfaces
CurrentMaintenanceOperationIterator_I
MaintenanceMgr_I
• “getActiveMaintenanceOperation” on page 15-2
• “performMaintenanceOperation” on page 15-3
Table 15-2. getActiveMaintenanceOperation
Operation getActiveMaintenanceOperation
Status Optional
Supported Yes
in arguments • globaldefs::NamingAttributes_T tpOrMeName

out / inout / return • CurrentMaintenanceOperationList_T currentMaintenance

values OpeationList
(see “CurrentMaintenanceOperationList_T” on page 24-39)
• CurrentMaintenanceOperationIterator_I cmoIt
Comments This operation returns the CurrentMaintenanceOperation_T object

structure.
This operation returns only the list of objects on which the maintenance
operation Operate has been performed. This operation cannot be
performed without performing performMaintenanceOperation.

Beta Draft Confidential maintenanceOps Module
Data Types
Table 15-3. performMaintenanceOperation

Operation performMaintenanceOperation
Status Optional
Supported Yes
in arguments • CurrentMaintenanceOperation_T maintenanceOperation

(see “CurrentMaintenanceOperation_T” on page 24-38)
• MaintenanceOperationMode_T maintenanceOperationMode
(see “MaintenanceOperationMode_T” on page 24-40)

values
Comments This operation returns the CurrentMaintenanceOperation_T object

structure.
Data Types
The data types for maintenanceOps module are as follows:
• “CurrentMaintenanceOperation_T” on page 24-38
• “CurrentMaintenanceOperationList_T” on page 24-39
• “MaintenanceOperation_T” on page 24-39
• “MaintenanceOperationMode_T” on page 24-40
Notifications
appropriate.

Notifications

16
mtnmVersion Module
Table 16-1. List of Sections - mtnmVersion
Section Covers
Interfaces “Version_I” on page 16-2

mtnmVersion Module
Interfaces
Interfaces
Version_I
• “getVersion” on page 16-2
The list of operations for mtnmVersion module is as follows:
Table 16-2. getVersion

Operation getVersion
Status Mandatory
Supported Yes
Exceptions None
in arguments None
out / inout / return This operation returns the version of the interface (string).
values
Comments This service returns the version of the IDL that the corresponding EMS
object supports.
The format of the return string is as follows: Release.Major[.Minor]
where Release, Major and Minor are strings that contain only digits.
For example, 2.1 indicates release 2 and major release 1, 1.3 indicates
release 1 and major release 3, and so on. Note that x.y has the same
meaning as x.y.0 The minor digit is used for bug fixing the major
release. e.g 1.2.1 is a minor release on 1.2. Any changes to any IDL
files must be approved by the Specification Authority.
For TMF 814A version 2.1, the version is "2.1".
This operation is implemented in EmsSessionFactory_I.

17
nmsSession
Table 17-1. List of Sections - nmsSession

Section Covers
Interfaces “NmsSession_I” on page 17-2
Note – This module does not have data types that represent second level objects.
Also, there are no specific notifications associated with this module.
Note – Navis EMS-CBGX uses this module to notify nmsSession. This module
must be implemented by NMS client.

nmsSession
Interfaces
Interfaces
NmsSession_I
• “eventLossCleared” on page 17-2
• “eventLossOccurred” on page 17-2
Table 17-2. eventLossCleared

Operation eventLossCleared
Status Mandatory
Supported Yes
in arguments globaldefs::Time_T endTime

values
Comments Navis EMS-CBGX TMF 814 Adapter uses this function to inform
NMS of any eventLossCleared.
Table 17-3. eventLossOccurred

Operation eventLossOccurred
Status Mandatory
Supported Yes
Exceptions None
in arguments globaldefs::Time_T startTime

• string notificationId

values
Comments Navis EMS-CBGX TMF 814 Adapter uses this function to inform
NMS of any eventLossOccurred.

18
performance Module
Note – performance module is not supported in this release. The details of the
module are available in TMF 814A version 2.1.

performance Module

19
session Module
Table 19-1. List of Sections - session

Section Covers
Interfaces “Session_I” on page 19-2

session Module
Interfaces
Interfaces
Session_I
• “oneway” on page 19-2
• “ping” on page 19-2
• “getAssociatedSession” on page 19-3
Table 19-2. oneway

Operation endSession
Status Mandatory
Supported Yes
Exceptions None
in arguments None

values
Comments None
Table 19-3. ping

Operation ping
Status Mandatory
Supported Yes
Exceptions None
in arguments None

values
Comments None

Beta Draft Confidential session Module
Interfaces
Table 19-4. getAssociatedSession

Operation getAssociatedSession
Status Mandatory
Supported Yes
in arguments None

values
Comments This operation returns the value of the appropriate variable.

session Module
Interfaces

20
globaldefs Module
Table 20-1. List of Sections - globaldefs

Section Covers
Interfaces “NamingAttributesIterator_I” on page 20-2
Data Types • ConnectionDirection_T
• ExceptionType_T
• NameAndStringValue_T
• NamingAttributes_T
• NamingAttributesList_T
• NVSList_T
• Time_T

globaldefs Module
Interfaces
Interfaces
NamingAttributesIterator_I
Data Types
The data types for globaldefs module are as follows:
• ConnectionDirection_T
• ExceptionType_T
• NameAndStringValue_T
• NamingAttributes_T
• NamingAttributesList_T
• NVSList_T
• Time_T

21
notifications Module
Table 21-1. List of Sections - notifications

Section Covers
Interfaces “EventIterator_I” on page 21-2
Data Types • CorrelatedNotificationList_T
• CorrelatedNotifications_T
• EventList_T
• FileTransferStatus_T
• NameAndAnyValue_T
• NotifIDList_T
• NVList_T
• ObjectType_T
• PerceivedSeverity_T
• PerceivedSeverityList_T
• ProbableCauseList_T
• ProposedRepairAction_T
• ProposedRepairActionList_T
• ServiceAffecting_T
• SpecificProblem_T
• SpecificProblemList_T

notifications Module
Interfaces
Interfaces
EventIterator_I
Data Types
The data types for notifications module are as follows:
• CorrelatedNotificationList_T
• CorrelatedNotifications_T
• EventList_T
• FileTransferStatus_T
• NameAndAnyValue_T
• NotifIDList_T
• NVList_T
• ObjectType_T
• PerceivedSeverity_T
• PerceivedSeverityList_T
• ProbableCauseList_T
• ProposedRepairAction_T
• ProposedRepairActionList_T
• ServiceAffecting_T
• SpecificProblem_T
• SpecificProblemList_T

22
common Module
Table 22-1. List of Sections - common

Section Covers
Interfaces “Common_I” on page 22-2
Data Types • “Capability_T” on page 24-41
• “CapabilityList_T” on page 24-41

common Module
Interfaces
Interfaces
Common_I
• “getCapabilities” on page 22-2
• “setNativeEMSName” on page 22-2
• “setOwner” on page 22-3
• “setUserLabel” on page 22-3
Table 22-2. getCapabilities

Operation getCapabilities
Status Mandatory
Supported Yes
in arguments None
out / inout / return CapabilityList_T capabilities (see “Capability_T” on page 24-41)

values
Comments This operation returns the list (CapabilityList_T) of operation names,

with value supported or unsupported for Navis EMS-CBGX TMF 814
Adapter modules.
Table 22-3. setNativeEMSName

Operation setNativeEMSName
Status Optional
Supported No

• string nativeEMSName

values

Beta Draft Confidential common Module
Interfaces
Operation setNativeEMSName
Table 22-4. setOwner

Operation setOwner
Status Optional
Supported No

• string owner

values
Comments Provisioning Server does not allow Customer Name changes (except
LPort and Provisioning Server Circuit object). Since this interface is
optional, it will not be supported in Navis EMS-CBGX TMF 814
Table 22-5. setUserLabel

Operation setUserLabel
Status Optional
Supported No

• string userLabel
• boolean enforceUniqueness

values
Comments Provisioning Server does not allow object Name changes. Since this
interface is optional, it will not be supported in Navis EMS-CBGX
TMF 814 Adapter Release 09.02.00.00.

common Module
Data Types
Data Types
The data types for common module are as follows:
• “Capability_T” on page 24-41
• “CapabilityList_T” on page 24-41
Notifications
appropriate.

23
TMF 814A Object NamingAttributes for
Provisioning Server
This chapter provides the TMF 814A Object NamingAttributes for Provisioning
Server.
This chapter covers these modules:

• “ems” on page 23-2
• “multiLayerSubnetwork” on page 23-2
• “managedElement” on page 23-2
• “equipment Holder” on page 23-3
• “equipment” on page 23-3
• “TPPool” on page 23-4
• “PTP” on page 23-4
• “CTP” on page 23-5
• “topologicalLink” on page 23-6
• “subnetworkConnection” on page 23-7
• “Protection” on page 23-8
• “trafficDescriptor” on page 23-9
• “Other Objects” on page 23-9

TMF 814A Object NamingAttributes for Provisioning Server
ems
ems
Table 23-1. ems - NamingAttributes
Attributes Name/Value and Description
NamingAttributes name="EMS";value="CompanyName/EMSname"
Provisioning Server Navis EMS-CBGX TMF Adapter appears as the EMS to the
NamingAttributes NMS. The EMS name is
name="EMS";value="LucentTechnologies/Provisioning Server"
multiLayerSubnetwork
Table 23-2. multiLayerSubnetwork - NamingAttributes
NamingAttributes • name="EMS";value="CompanyName/EMSname"
• name="MultiLayerSubnetwork";value="SubnetworkName"
Provisioning Server Provisioning Server network maps to TMF

NamingAttributes multiLayerSubnetwork.
For example, if the network.152.148.0.0 is a Provisioning Server
managed network, the TMF name is:
• name="EMS";value="LucentTechnologies/Provisioning
Server"
• name="MultiLayerSubnetwork";value="/network=152.148.0.0"
managedElement
Table 23-3. managedElement NamingAttributes
NamingAttributes • name="EMS"; value="CompanyName/EMSname"
• name="ManagedElement"; value="ManagedElementName"
Provisioning Server Provisioning Server switch object is mapped to TMF

NamingAttributes managedElement. The TMF name for a switch with IP address
130.100.10.2 is:
• name="EMS"; value="Lucent Technologies/Provisioning
Server"
• name="ManagedElement";value="/switch=130.100.10.2"

equipment Holder
equipment Holder
Table 23-4. equipment Holder - NamingAttributes
Naming • name="EMS"; value="CompanyName/EMSname"

Attributes
• name="ManagedElement";value="ManagedElementName"
• name="EquipmentHolder"; value="EquipmentHolderName"
Provisioning Server This TMF object shows a daughter board - mother board
NamingAttributes hierarchy. It is used to model the BIO cards on the Lucent GX 550
MultiService WAN switch.
For example, Switch.130.100.10.3.card.7 represents a BIO in slot
7 of a GX550. The TMF name is:
• name="EMS"; value="LucentTechnologies/Provisioning
Server"
• name="ManagedElement";value="/switch=130.100.10.3"
• name="EquipmentHolder";value="/shelf=1/slot=7"
equipment
Table 23-5. equipment NamingAttributes

Attributes
• name="EquipmentHolder"; value="EquipmentHolderName"
• name="Equipment"; value="EquipmentName"

TPPool
Provisioning Server Provisioning Server card objects (on the Lucent's CBX and
NamingAttributes BSTDX switches) and subcard objects (on the Lucent's GX550
Switch and all cards on the Lucent's GX250 Extended Shelf
Switch are modeled using this TMF object.
EMS and managedElement take the form as shown in equipment
Holder.
• subcard object: Switch.130.100.10.3.card.9.SubCard.31

EquipmentHolderName = "/shelf=1/slot=9/subslot=31
EquipmentName = "1"
• card object: Switch.130.100.10.2.card.5
EquipmentHolderName = "/shelf=1/slot=5
EquipmentName = "1"
TPPool
Navis EMS-CBGX TMF 814 Adapter does not support any corresponding
Provisioning Server object for TPPool.
PTP
Table 23-6. PTP - NamingAttributes
• name="PTP";value="PTPName"
Provisioning Server Provisioning Server PPorts and IMA groups map to TMF PTPs.
NamingAttributes EMS and managedElement naming convention is as described in
“trafficDescriptor” on page 23-9.
PTPName can have the following values:
• For a Provisioning Server pport "Switch.130.100.10.2.card.

9.pport.8", PTPName = "/shelf=1/slot=9/port=8".
• For an Provisioning Server IMA group
"Switch.130.100.10.2.card.11.pport.1.imaGroup.1"
PTPName = "/shelf=1/slot=11/port=1/imaGroup=1".
The IMA Group is actually a Fragment TP.

CTP
CTP
Table 23-7. CTP - NamingAttributes
• name="PTP";value="PTPName"
• name="CTP";value="CTPName"
Provisioning Server Provisioning Server channels, IMA links (fragment CTP), LPorts
NamingAttributes (direct/virtual/opti-trunk/direct-trunk) and ATM addresses (for
offnet circuits, only the destination endpoint ATM addresses
specified) map to CTPs. CTPName can have the following values:
• channel: Switch.130.100.10.2.card.6.pport.1.channel.1:
"/channel=1"
• IMA link: Switch.130.100.10.2.card.11.pport.4.IMALink.1:

"/IMALink=1"
• lport (unchannelized card and some channelized cards where

there is no explicit channel object):
Switch.130.100.10.2.card.11.pport.6.lport.1 : "/lport=1"
• lport (on channelized card):

Switch.130.100.10.2.card.6.pport.1.channel.1.lport.1:
"/channel=1/lport=1"
• lport (on IMA group):

Switch.130.100.10.2.card.11.pport.1.imaGroup.1.lport.1 :
"lport.1"
• offnet ATM Address (offnet CTP): <atmaddress>

name="EMS";value=""
name="ManagedElement";value=""
name="PTP";value=""
name="CTP";value="/remoteaddress=
<atmaddress>"
• For the remote VPI, the VCIs are also specified, the CTP name
is "/remoteaddress=<remoteaddress>/vpi=[1..n]/vci=[1..n]"

topologicalLink
• Example (for other circuit endpoints):

– For ATM PMP root as aEnd
Name=CTP, Value=”/lport=1/PMPCktRoot/vpi=2/vci=222
– For ATM PMP Leaf as zEnd
Name=CTP, Value=”/lport=1/PMPCktLeaf/vpi=2/vci=222
– For Offnet PMP leaf
Name=CTP,
Value=”/lport=1/PMPOffNetCktRoot/vpi=2/vci=222/PMP
OffNetCktLeaf=1
– For PMP SPVC leaf name=CTP,
Value=”/lport=1/PMPSpvcRoot/vpi=2/vci=222/
PMPSpvcLeaf=1
topologicalLink
Table 23-8. topologicalLink NamingAttributes
• name="TopologicalLink";value="TopologicalLinkName"
Provisioning Server Provisioning Server trunks and PNNI links map to TMF
NamingAttributes topologicalLink. With EMS taking values as above,
topologicalLinkName can have any of the following values:
• /Network=130.100.0.0/Trunk=lucent_dt_nbi
(direct / Opti trunks)
• /Switch=181.181.1.51/PnniLink=GAYA:GWALIOR_
PNNI_LINK:GWALIOR:60a01230000000000000000000000
00040fb04e54200

subnetworkConnection
subnetworkConnection
Table 23-9. subnetworkConnection NamingAttributes
• name="MultiLayerSubnetwork"; value="SubnetworkName"
• name="SubnetworkConnection";
value="SubnetworkConnectionName"
Provisioning Server Provisioning Server circuit (pvc, redirectcircuit), offnetcircut,

NamingAttributes pmpoffnetcircuit, activesvc, spvc, pmpcktroot, pmpspvcroot,
pmpcktleaf, pmpspvcleaf map to the same TMF
subnetworkConnection object.
For example, the following is the list of object IDs for the
Provisioning Server objects mentioned above. These strings will
appear in the value="SubnetworkConnectionName"
of the TMF SNC name.
• /Switch=130.100.10.2/shelf=1/slot=9/port=1/lport=1/vpi=
3/vci=787 (ATM PVC/redirect circuit)
• /Switch=130.100.10.2/shelf=1/slot=9/port=1/lport=
1/PMPCktRoot/vpi=2/vci=222 (ATM PMP root)
• /Switch=130.100.10.2/shelf=1/slot=9/port=8/lport=1/
PMPCktLeaf/vpi=2/vci=222 (ATM PMP leaf)
OffNetCircuit/vpi=2/vci=222 (Offnet - pt to pt)
• /Switch= 130.100.10.2/shelf=1/slot=9/port=1/lport=1/
PMPOffNetCktRoot/vpi=2/vci=222 (Offnet PMP root)
• /Switch=130.100.10.2/shelf=1/slot=9/port=1/lport=
1/PMPOffNetCktRoot/vpi=2/vci=222/PMPOffNetCktLeaf=1
(Offnet PMP leaf)
• /Switch=130.100.10.2/shelf=1/slot=9/port=1/lport=1/spvc/vpi=2
/vci=222 (old SPVC prior to Release 09.01.00.00)
• /Switch=130.100.10.2/shelf=1/slot=9/port.=1/lport=1/
PMPSpvcRoot/vpi=2/vci=222 (Old PMP spvc root)
PMPSpvcRoot/vpi=2/vci=222/PMPSpvcLeaf=1
(Old PMP spvc leaf)
• /Switch=130.100.10.2/card=9/port=1/lport=1/activeSvc/vpi=
2/vci=222 (SVC)

Protection
For example, the svc's TMF name will be:
• name="EMS";value="Lucent Technologies/Provisioning
Server"
• name="MultiLayerSubnetwork";value="/network.130.100.0.0"
• name="SubnetworkConnection";value="/Switch=130.100.10.2/
shelf=1/slot=9/port=1/lport=1/activeSvc/vpi=2/vci=222"
Protection
Table 23-10.Protection NamingAttributes
Naming • name="EMS";value="CompanyName/EMSname"
Attributes
• name="PGP";value="ProtectionGroupName"
Provisioning Server Provisioning Server aps and servicename objects are modeled
NamingAttributes using this TMF object. For example:
• aps: Switch.130.100.10.3.card.8.pport.1.Aps
name="EMS";value="Lucent Technologies/Provisioning
Server"
name="ManagedElement";value="/switch=130.100.10.3"
name="PGP";value=""/shelf=1/slot=8/port=1/Aps"
• servicename:Network.130.100.0.0.ServiceName.madhukp_
service_ilmi (both Resilient UNI/NNI and LMI bindings)
name="EMS";value="Lucent Technologies/Provisioning
Server"
name="ManagedElement";value="" (empty string)
name="PGP";value="/Network=130.100.0.0/ServiceName=
madhukp_service_ilmi"

trafficDescriptor
trafficDescriptor
Table 23-11.trafficDescriptor - NamingAttributes

Attributes
• name="TrafficDescriptor";value="TrafficDescriptorName"
Provisioning Server Provisioning Server traffic descriptors map to their TMF

NamingAttributes counterparts. TrafficDescriptorName can have the value of the
objectid of the corresponding Provisioning Server object.
• For example, “Network.130.100.0.0.
TrafficDesc.PMP Rev,Unsp CBR".
Other Objects
Table 23-12. Other Objects NamingAttributes
• name="AID";value="NameOfEntity"

Other Objects

24
Mapping TMF 814A Data Type and
Provisioning Server Attributes
This chapter provides the mapping between the Provisioning Server and the TMF
object. This chapter also describes the attributes of the TMF objects. This chapter
covers the following sections:
• “ems” on page 24-3
• “emssession” on page 24-4
• “multiLayerSubnetwork” on page 24-5
• “managedElement” on page 24-7
• “equipment Holder” on page 24-9
• “equipment” on page 24-12
• “terminationPoint” on page 24-14
• “PTP” on page 24-18
• “CTP” on page 24-20
• “topologicalLink” on page 24-22
• “SubnetworkConnection” on page 24-23
• “SubnetworkConnection” on page 24-23
• “protection” on page 24-29
• “trafficDescriptor” on page 24-34
• “transmissionParameters” on page 24-36
• “guiCutThrough” on page 24-37
• “maintenanceOps” on page 24-38
• “performance” on page 24-41
• “common” on page 24-41

Mapping TMF 814A Data Type and Provisioning Server Attributes
Note – additionalInfo is an attribute-value pair for other attribute names

corresponding to the Provisioning Server CLI attribute names. The attributes which
map directly to the TMF object structure are not included in additionalInfo. For
example, “Location” in managedElement is not included as additionalInfo.
Note – IMA group is not supported in Navis EMS-CBGX TMF 814 Adapter
09.02.00.00.

ems
ems
Table 24-1. ems - Provisioning Server Object Mapping
TMF Object Provisioning Server Object Mapping
ems No corresponding Provisioning Server object
Table 24-2. ems - Attributes

TMF Object Attributes Provisioning Server Object Comments
Attribute
struct EMS_T {
globaldefs::NamingAttributes_Tname; No corresponding Provisioning Name is "LucentTechnologies/

Server attribute Provisioning Server”.
See “ems” on page 23-2 in
“Mapping TMF 814A Data
Type and Provisioning Server
Attributes”
string userLabel; No corresponding Provisioning Empty string is used

Server attribute
string nativeEMSName; No corresponding Provisioning "LucentTechnologies/

Server attribute Provisioning Server”
string owner; owner is the CustomerName Empty string is used
string emsVersion; emsVersion emsVersion is Provisioning

Server version
string type; No corresponding Provisioning Type is “Provisioning”

Server attribute
globaldefs::NVSList_T No corresponding Provisioning additionalInfo is not used

additionalInfo;}; Server attribute

emssession
emssession
Table 24-3. emssession - Provisioning Server Object Mapping
emssession No corresponding Provisioning Server object.
Table 24-4. emssession - Attributes

Attribute
managerNames_T No corresponding Provisioning The list includes:

typedef sequence<string> Server attribute.
• emsMgr
managerNames_T;
• managedElement_Mgr
• EquipmentInventoryMgr
• guiCutThroughMgr
• MaintenanceMgr
• MultiLayerSubnetworkMgr
• PerformanceManagementMgr
• ProtectionMgr
• TrafficDescriptorMgr

Table 24-5. multiLayerSubnetwork - Provisioning Server Object Mapping
multiLayerSubnetwork Provisioning Server Network object
Table 24-6. multiLayerSubnetwork- Attributes

Attribute
struct MultiLayerSubnetwork_T{
globaldefs::NamingAttributes_T name; No corresponding Provisioning See “multiLayerSubnetwork”

Server attribute. on page 23-2 in “Mapping
TMF 814A Data Type and
Provisioning Server
Attributes”.
string userLabel; No corresponding Provisioning Empty string is used.

Server attribute.
string nativeEMSName; No corresponding Provisioning Provisioning Server Network

Server attribute. ObjectID is used
string owner; No corresponding Provisioning Empty string is used.

Server attribute.
Topology_T subnetworkType; No corresponding Provisioning TOPO_MESH is used.

Server attribute.
transmissionParameters::LayerRateList No corresponding Provisioning For ATM: LR_ATM_NI for

_T supportedRates; Server attribute. ATM Network Interfaces (UNI
and NNI), LR_ATM_VP for
ATM Virtual Paths,
LR_ATM_VC for ATM
Virtual Channels,
LR_DS0_64K, DS0 CTP layer
rate.
For FR: LR_FR_NI
See “Mapping TMF 814 Layer
Rates with Provisioning
Server” on page A-1.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning For more information, refer

Server attribute. Provisioning Server Object
};
Attribute Guide.

Table 24-6. multiLayerSubnetwork- Attributes (Continued)

Attribute
EMSFreedomLevel_T No corresponding Provisioning EMSFL_CC_AT_SNC_

Server attribute. LAYER indicates the SNC is
enum EMSFreedomLevel_T
created.
{EMSFL_CC_AT_SNC_LAYER,
EMSFL_TERMINATE_AND_MAP, EMSFL_TERMINATE_AND
EMSFL_HIGHER_ORDER_SNCS, _MAP indicates the SNC is
EMSFL_RECONFIGURATION}; created or deleted.
EMSFL_HIGHER_ORDER_
SNCS and EMSFL_
RECONFIGURATION are not
supported.
SubnetworkList_T No corresponding Provisioning List of Provisioning Server

typedef Server attribute. Network objects in
sequence<MultiLayerSubnetwork_T> MultiLayerSubnetwork_T
SubnetworkList_T; format.
Topology_T No corresponding Provisioning TOPO_MESH describes

enum Topology_T Server attribute. Lucent networks.
{TOPO_SINGLETON,
TOPO_CHAIN, TOPO_PSR,
TOPO_OPEN_PSR, TOPO_SPRING,
TOPO_OPEN_SPRING,
TOPO_MESH };

managedElement
managedElement
Table 24-7. managedElement - Provisioning Server Object Mapping
managedElement Provisioning Server switch object
Table 24-8. managedElement - Attributes

Attribute
struct ManagedElement_T {
globaldefs::NamingAttributes_T No corresponding Provisioning See “trafficDescriptor” on

name; Server attribute. page 23-9.

Server attribute.
string nativeEMSName; No corresponding Provisioning Provisioning Server Switch

Server attribute. ObjectID
string owner; No corresponding Provisioning Empty string is used

Server attribute.
string location; Location Location attribute of the switch
string version; RevisionNo RevisionNo switch attribute
string productName; DefinedType See “Mandatory Provisioning

Server Object Attributes” on
page 7-10.
CommunicationState_T SwManageState SwManageState switch

communicationState; attribute
boolean emsInSyncState; SwSyncState SwSyncState switch attribute

managedElement
Table 24-8. managedElement - Attributes (Continued)

Attribute
transmissionParameters::LayerRate No corresponding Provisioning For ATM:

List_T supportedRates; Server attribute LR_ATM_NI for ATM
Network Interfaces (UNI and
NNI),
LR_ATM_VP for ATM Virtual
Paths,
LR_ATM_VC for ATM
Virtual Channels,
rate.
For FR: LR_FR_NI.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning Name is the mandatory

}; Server attribute attribute
enum CommunicationState_T SwManageState • CS_AVAILABLE for

{CS_AVAILABLE, “Managed”
CS_UNAVAILABLE };
• CS_UNAVAILABLE:for
“Unmanaged”
ManagedElementList_T No corresponding Provisioning List of Provisioning Server

typedef Server attribute objects in ManagedElement_T
sequence<ManagedElement_T> format.
ManagedElementList_T;

equipment Holder
equipment Holder
Table 24-9. equipment Holder - Provisioning Server Object Mapping
equipmentHolder Provisioning Server card objects
Table 24-10.equipment Holder - Attributes

Attribute
struct EquipmentHolder_T {
globaldefs::NamingAttributes_T No corresponding Provisioning See “Other Objects” on

name; Server attribute page 23-9 .

Server attribute
string nativeEMSName; No corresponding Provisioning Card / Subcard ObjectID

Server attribute

Server attribute
boolean alarmReportingIndicator; No corresponding Provisioning FALSE value will fail the

Server attribute operation.
This attribute cannot be
changed.
EquipmentHolderType_T holderType Card
globaldefs::NamingAttributes_T DefinedType See “Mandatory Provisioning

expectedOrInstalledEquipment; Server Object Attributes” on
page 7-10.
EquipmentObjectTypeList_T DefinedType The "Definedtype" in the slot

acceptableEquipmentTypeList; (fetched by SNMP). If this is
not the same as
"expectedOrInstalled
Equipment", the
equipmentHolder is not
synchronized. No further
operations will be allowed until
this state is corrected. See
“Mandatory Provisioning
page 7-10.

equipment Holder
Table 24-10.equipment Holder - Attributes (Continued)

Attribute
HolderState_T holderState; No corresponding Provisioning EMPTY and

Server attribute. INSTALLED_AND_
EXPECTED are supported.
globaldefs::NVSList_T No corresponding Provisioning For more information, see

additionalInfo; }; Server attribute Provisioning Server Object
Attribute Guide.
EquipmentHolderType_T DefinedType of Card Supported Types of equipment

Holders include: "shelf" and
typedef string
"slot". See “Mandatory
EquipmentHolderType_T;
Provisioning Server Object
Attributes” on page 7-10.
EquipmentObjectType_T DefinedType of Subcard Object types in Equipment

typedef string include: "shelf", "slot" and
EquipmentObjectType_T; equipment.
Possible values are listed in
“Mandatory Provisioning
page 7-10.
EquipmentObjectTypeList_T No corresponding Provisioning List of Provisioning Server

typedef Server attribute. objects in
sequence<EquipmentObjectType_T> EquipmentObjectType_T
EquipmentObjectTypeList_T; format.
EquipmentOrHolder_T No corresponding Provisioning An appropriate value as per

union EquipmentOrHolder_T switch Server attribute. TMF814A Version 2.1 will be
(EquipmentTypeQualifier_T) used.
{case 0: Equipment_T equip;
case 1: EquipmentHolder_T holder; }
EquipmentOrHolderList_T No corresponding Provisioning List of Provisioning Server

sequence<EquipmentOrHolder_T> EquipmentOrHolder_T format.
EquipmentOrHolderList_T;
EquipmentTypeQualifier_T No corresponding Provisioning Distinguishes between

enum EquipmentTypeQualifier_T Server attribute. equipment and equipment
{EQT, EQT_HOLDER }; holders.
An appropriate value as per
TMF814A Version 2.1 will be
used.

equipment Holder
Table 24-10.equipment Holder - Attributes (Continued)

Attribute
HolderState_T No corresponding Provisioning The supported values include:

enum HolderState_T Server attribute. EMPTY and
{EMPTY, INSTALLED_AND_
INSTALLED_AND_EXPECTED, EXPECTED.
EXPECTED_AND_NOT_
INSTALLED,
INSTALLED_AND_NOT_
EXPECTED,
MISMATCH_OF_INSTALLED_
AND_EXPECTED,
UNAVAILABLE, UNKNOWN};
ServiceState_T OperStatus /AdminStatus The mapping between this and

enum ServiceState_T OperStatus and AdminStatus is
{IN_SERVICE, OUT_OF_SERVICE, as follows:
OUT_OF_SERVICE_BY_
MAINTENANCE, SERV_NA }; • AdminStatus Up and
OperStatus Up
(IN_SERVICE)
• AdminStatus Up and
OperStatus Down
(OUT_OF_SERVICE)
• AdminStatus Down and

OperStatus Down
(OUT_OF_SERVICE_
BY_MAINTENANCE)

equipment
equipment
Table 24-11.equipment - Provisioning Server Object Mapping
equipment Provisioning Server subcard objects on the GX550 and all

cards on the GX250.
Table 24-12.equipment - Attributes

Attribute
struct Equipment_T {
globaldefs::NamingAttributes_T No corresponding Provisioning See “equipment” on page 23-3.

name; Server attribute

Server attribute
string nativeEMSName; No corresponding Provisioning Subcard ObjectID is used

Server attribute

Server attribute
boolean alarmReportingIndicator; No corresponding Provisioning The value is true, else ignored.

Server attribute
ServiceState_T serviceState; OperStatus / AdminStatus The mapping between this and

OperStatus and AdminStatus is
as follows:
OperStatus Up
(IN_SERVICE)
OperStatus Down
(OUT_OF_SERVICE)
• AdminStatus Down and

OperStatus Down
(OUT_OF_SERVICE_
BY_MAINTENANCE)

equipment
Table 24-12.equipment - Attributes (Continued)

Attribute
EquipmentObjectType_T DefinedType See “Mandatory Provisioning

expectedEquipmentObjectType; Server Object Attributes” on
page 7-10.
EquipmentObjectType_T DefinedType The card type in the slot. See

installedEquipmentObjectType; “Mandatory Provisioning Server
Object Attributes” on page 7-10.
string installedPartNumber; No corresponding Provisioning Empty string is used

Server attribute
string installedVersion; CardVersion Software version of the card is

used.
string installedSerialNumber; No corresponding Provisioning Empty string is used.

Server attribute
globaldefs::NVSList_T No corresponding Provisioning Subcard attributes on the GX

additionalInfo; }; Server attribute 550.
struct EQTCreateData_T {

Server attribute
boolean forceUniqueness; No corresponding Provisioning The value is true, else ignored.

Server attribute

Server attribute
EquipmentObjectType_T DefinedType The card type in the slot. See

expectedEquipmentObjectType; “Mandatory Provisioning Server
Object Attributes” on page 7-10.

equipmentHolderName; Server attribute page 23-9.
globaldefs::NVSList_T No corresponding Provisioning All other attributes not covered

additionalInfo; }; Server attribute above.

terminationPoint
terminationPoint
Table 24-13.terminationPoint - Attributes

Attribute
Directionality_T No corresponding Provisioning D_BIDIRECTIONAL for all

enum Directionality_T Server attribute. objects except LPorts that are
{D_NA, D_BIDIRECTIONAL, part of a PMP connection,
D_SOURCE for PMP root,
D_SOURCE, D_SINK };
D_SINK for PMP leaf. All
Lucent PPorts are
D_BIDIRECTIONAL
TerminationMode_T No corresponding Provisioning All the values are supported.

Server attribute.
enum TerminationMode_T
{TM_TERMINATED_AND_
AVAILABLE_FOR_MAPPING,
TM_NEITHER_TERMINATED_
NOR_AVAILABLE_FOR_MAPPING,
TM_NA};
struct TerminationPoint_T {
globaldefs::NamingAttributes_T name; No corresponding Provisioning See “trafficDescriptor” on

Server attribute. page 23-9 and
“trafficDescriptor” on
page 23-9.

Server attribute.
string nativeEMSName; No corresponding Provisioning PPort, IMA group, Channel,

Server attribute. IMA link and LPort ObjectID
is used
string owner; CustomerName Empty string is used (except

for LPort)
globaldefs::NamingAttributes_T No corresponding Provisioning Empty string is used

ingressTrafficDescriptorName; Server attribute.

egressTrafficDescriptorName; Server attribute.
TPType_T type; No corresponding Provisioning TPT_CTP for CTP, TPT_PTP:

Server attribute.

terminationPoint
Table 24-13.terminationPoint - Attributes (Continued)

Attribute
TPConnectionState_T connectionState; No corresponding Provisioning TPCS_NA for PTPs

Server attribute.
TPCS_BI_Connected for
CTPs
TerminationMode_T tpMappingMode; No corresponding Provisioning • TM_NEITHER_

Server attribute. TERMINATED_NOR_
AVAILABLE_FOR_
MAPPING for LPorts.
These can be used as
circuit endpoints.
TM_TERMINATED_
AND_AVAILABLE_
FOR_MAPPING for
channels and IMA groups
• TM_NA for PPorts
Directionality_T direction; No corresponding Provisioning D_BIDIRECTIONAL

Server attribute.
transmissionParameters::Layered No corresponding Provisioning New attribute "layer rate" will

ParameterList_T transmissionParams; Server attribute. be introduced for port and
IMA group objects.
TPProtectionAssociation_T No corresponding Provisioning If the PPort is not APS

tpProtectionAssociation; Server attribute. enabled, the value is
TPPA_NA, else
TPPA_PSR_RELATED.
TPPA_PSR_RELATED if the
LPort has a service name
binding.
boolean edgePoint; No corresponding Provisioning New attribute "EdgePoint" for

Server attribute. PPort and IMA group objects.
The value will be set to TRUE
if the LPort configured on it is
either an Opti Trunk LPort or
MPLS Direct Trunk or NNI
LPort, else set to FALSE.

terminationPoint

Attribute
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning SigFwdTD, TrunkFwdTD,

}; Server attribute. NodeFwdTD, RCCFwdTD,
CutThroughFwd,
SvcFwdTdParam1 Integer,
SvcFwdTdParam3 Integer
ILMIRevTD, SigRevTD,
TrunkRevTD, NodeRevTD,
RCCRevTD,
SvcBwdTdParam1,
SvcBwdTdParam2,
SvcBwdTdParam3.
All other attributes of PPort
and IMA group apart from
those mentioned above, refer
to Provisioning Server Object
Attribute Guide.
TerminationPointList_T No corresponding Provisioning List of Provisioning Server

Server attribute. objects in TerminationPoint_T
typedef
format.
sequence<TerminationPoint_T>
TerminationPointList_T;
TPConnectionState_T No corresponding Provisioning PTP: TPCS_NA

Server attribute.
enum TPConnectionState_T CTP: For all objects except
{TPCS_NA,TPCS_SOURCE_CONNE LPorts that are part of a PMP
CTED, TPCS_SINK_CONNECTED, connection,
TPCS_BI_CONNECTED, TPCS_BI_CONNECTED,
TPCS_NOT_CONNECTED }; else TPCS_SOURCE_
CONNECTED for PMP root,
TPCS_SINK_CONNECTED
for PMP leaf.
TPProtectionAssociation_T No corresponding Provisioning PTP: If the PPort is not APS

Server attribute. enabled, the value is
enum TPProtectionAssociation_T
TPPA_NA. Otherwise, the
{TPPA_NA, TPPA_PSR_RELATED };
value is
TPPA_PSR_RELATED.
CTP: TPPA_PSR_RELATED
if the LPort has a service name
binding.

terminationPoint

Attribute
TPType_T No corresponding Provisioning • PTP (PPort, IMA):

Server attribute. TPT_PTP
enum TPType_T
{TPT_PTP, TPT_CTP, TPT_TPPool}; • CTP (LPort, IMA link,
Channel): TPT_CTP

PTP
PTP
Table 24-14.PTP - Provisioning Server Object Mapping
PTP Provisioning Server PPorts and IMA groups map to TMF

PTP.
IMA group is not fully supported in Navis
EMS-CBGX TMF 814 Adapter 09.02.00.00.
Table 24-15.PTP - Attributes

Attribute
globaldefs::NamingAttributes_T name; No corresponding Provisioning See “trafficDescriptor” on

Server attribute. page 23-9.
string userLabel; No corresponding Provisioning Not applicable

Server attribute.
string nativeEMSName; No corresponding Provisioning Provisioning Server Object ID

Server attribute for PPort (IMA group)
string owner; No corresponding Provisioning Not applicable

Server attribute
globaldefs::NamingAttributes_T No corresponding Provisioning Empty string is used.


TPType_T type; No corresponding Provisioning TPT_PTP

Server attribute
TPConnectionState_T connectionState No corresponding Provisioning The only supported value is

Server attribute TPCS_NA. Other values are
ignored.
TerminationMode_T tpMappingMode; No corresponding Provisioning TM_NA

Server attribute
Directionality_T direction; No corresponding Provisioning All Lucent PPorts are

Server attribute D_BIDIRECTIONAL
transmissionParameters::LayeredPara No corresponding Provisioning An appropriate value as per

meterList_T transmissionParams; Server attribute. TMF814A Version 2.1 will be
used.

PTP
Table 24-15.PTP - Attributes (Continued)

Attribute
TPProtectionAssociation_T APS If the PPort is not APS

tpProtectionAssociation; enabled, the value is
TPPA_NA, else the value is
TPPA_PSR_RELATED.
boolean edgePoint; No corresponding Provisioning The value will be set to TRUE

Server attribute. if the LPort is the edgePoint.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning All other attributes of

}; Server attribute. PPort/IMA group apart from
those mentioned above.

CTP
CTP
Table 24-16.CTP - Provisioning Server Object Mapping
CTP Provisioning Server channels, IMA links (fragment CTP),

LPorts and ATM addresses (for offnet circuits, only the
destination endpoint ATM addresses specified)
Table 24-17.CTP - Attributes

Attribute
globaldefs::NamingAttributes_T name; No corresponding Provisioning Channel, IMA link, LPort is

Server attribute. used.
string userLabel; Name User Label is LPort name else

empty string is used for
Channel and IMA link.
string nativeEMSName; No corresponding Provisioning Channel, IMA link, LPort is

string owner; CustomerName Default value is PUBLIC
globaldefs::NamingAttributes_ No corresponding Provisioning Empty string is used.

T ingressTrafficDescriptorName; Server attribute.

TPType_T type; No corresponding Provisioning TPT_CTP represents LPort,

Server attribute. IMA link or Channel
depending on ObjectId
TPConnectionState_T connectionState; No corresponding Provisioning For all objects except LPorts

Server attribute. that are part of a PMP
connection,
TPCS_BI_CONNECTED,
else TPCS_SOURCE_
CONNECTED for PMP root,
TPCS_SINK_CONNECTED
for PMP leaf.

CTP
Table 24-17.CTP - Attributes (Continued)

Attribute
TerminationMode_T tpMappingMode; No corresponding Provisioning • TM_NA for PPorts and

Server attribute. IMA group
• TM_NEITHER_
TERMINATED_NOR_
AVAILABLE_FOR_
MAPPING for LPorts.
• TM_TERMINATED_AND_
AVAILABLE_FOR_
MAPPING for channels,
IMA groups.
Directionality_T direction; No corresponding Provisioning D_BIDIRECTIONAL for all

Server attribute. objects except LPorts that are
part of a PMP connection,
D_SOURCE for PMP root,
D_SINK for PMP leaf.

used.
TPProtectionAssociation_T No corresponding Provisioning TPPA_PSR_RELATED if the

tpProtectionAssociation; Server attribute. LPort has a service name
binding.
boolean edgePoint; No corresponding Provisioning The value will be set to TRUE

Server attribute. if the LPort is the edgePoint.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning SigFwdTD, TrunkFwdTD,

}; Server attribute. NodeFwdTD, RCCFwdTD,
CutThroughFwd,
ILMIRevTD, SigRevTD,
TrunkRevTD, NodeRevTD,
RCCRevTD,
SvcBwdTdParam1,
SvcBwdTdParam2,
SvcBwdTdParam3
All other attributes not
included above for
Provisioning Server channel,
LPort, IMA link objects, refer
to Provisioning Server Object
Attribute Guide.

topologicalLink
topologicalLink
Table 24-18.topologicalLink - Provisioning Server Object Mapping
topologicalLink Provisioning Server Trunks and PNNILink
Table 24-19.topologicalLink - Attributes

Attribute
struct TopologicalLink_T {
globaldefs::NamingAttributes_T No corresponding Provisioning See “topologicalLink” on

string userLabel; Name Empty string is used.
string nativeEMSName; No corresponding Provisioning Trunk/PNNI ObjectID

Server attribute.

Server attribute.
globaldefs::ConnectionDirection_T No corresponding Provisioning CD_BI - all Lucent trunks and

direction; Server attribute. PNNI links are bidirectional.
transmissionParameters::LayerRate_T No corresponding Provisioning For ATM: LR_ATM_NI for

rate; Server attribute. ATM Network Interfaces (UNI
ATM Virtual Paths,
LR_ATM_VC for ATM
Virtual Channels,
rate.
For FR: LR_FR_NI
globaldefs::NamingAttributes_T Endpoint 1 See “CTP” on page 23-5.

aEndTP;
globaldefs::NamingAttributes_T Endpoint 2 See “CTP” on page 23-5.

zEndTP; };
TopologicalLinkList_T No corresponding Provisioning List of PNNI / Trunk in

Server attribute. TopologicalLinkList_T
typedef
format.
sequence<TopologicalLink_T>
TopologicalLinkList_T;

SubnetworkConnection
Table 24-20.SubnetworkConnection - Provisioning Server Object Mapping
SubnetworkConnection Provisioning Server circuit (pvc, redirectcircuit),

offnetcircut, pmpoffnetcircuit, activesvc, spvc,
pmpcktroot, pmpspvcroot, pmpcktleaf, pmpspvcleaf
Table 24-21.SubnetworkConnection - Attributes

Attribute
struct SubnetworkConnection_T {
globaldefs::NamingAttributes_T name; No corresponding Provisioning Provisioning Server circuit

Server attribute. name. See
“subnetworkConnection” on
page 23-7.

Server attribute.
string nativeEMSName; No corresponding Provisioning Circuit ObjectID is used.

Server attribute.
SNCState_T sncState; Circuit OperStatus SNCS_ACTIVE is the only

supported value and the other
values are not supported.
globaldefs::ConnectionDirection_T No corresponding Provisioning Values can be CD_UNI,

direction; Server attribute. CD_BI. All circuits are
bidirectional, except
Point-to-Multipoint.

ATM Virtual Paths,
LR_ATM_VC for ATM
Virtual Channels,
rate.
For FR: LR_FR_NI

Table 24-21.SubnetworkConnection - Attributes (Continued)

Attribute
StaticProtectionLevel_T No corresponding Provisioning This attribute is not supported.

staticProtectionLevel; Server attribute. The value will be set to
UNPROTECTED for all
circuits.
SNCType_T sncType; No corresponding Provisioning ST_SIMPLE for Point to point

Server attribute. PVCs and SPVCs (offnet
circuits, SVCS, IP), Point to
Multipoint PVCs and Point to
Multipoint SPVCs.
ST_ADD_DROP_A for
redirecting circuits, PVC with
protection and service naming
binding.
TPDataList_T aEnd; Endpoint 1 See “CTP -

NamingAttributes” on
page 23-5.
TPDataList_T zEnd; Endpoint 2 See “CTP -

NamingAttributes” on
page 23-5.
Reroute_T rerouteAllowed; No corresponding Provisioning RR_YES for all circuit types

Server attribute. (except for SVC, the value is
RR_NO).
NetworkRouted_T networkRouted; No corresponding Provisioning NR_YES indicates that the

Server attribute. route is computed by the
network.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning Mandatory Name/Value pair

}; Server attribute. for additionalInfo: like name,
fwd_qosclass, rev_qosclass,
fwd_zero_cir, rev_zero_cir
GradesOfImpact_T No corresponding Provisioning Not applicable

enum GradesOfImpact_T Server attribute.
{GOI_HITLESS,
GOI_MINOR_IMPACT,
GOI_MAJOR_IMPACT };
NetworkRouted_T No corresponding Provisioning Default value is NR_NA.

enum NetworkRouted_T Server attribute. Other values are ignored.
{NR_NO, NR_NA, NR_YES };


Attribute
ProtectionEffort_T No corresponding Provisioning EFFORT_WHATEVER is the

enum ProtectionEffort_T Server attribute. default value. Other values are
{EFFORT_WHATEVER, ignored.
EFFORT_SAME_OR_BETTER,
EFFORT_SAME_OR_WORSE,
EFFORT_SAME };
Reroute_T No corresponding Provisioning RR_NA is the default value.

enum Reroute_T Server attribute. Other values are ignored.
{RR_NA, RR_NO,RR_YES };
RerouteChangeEvent_T No corresponding Provisioning Not applicable

typedef string RerouteChangeEvent_T; Server attribute.
Resource_T No corresponding Provisioning TMF naming convention is

typedef Server attribute. used for resource (ME, TL,
globaldefs::NamingAttributes_T CTP, PTP, or SNC).
Resource_T;
ResourceList_T No corresponding Provisioning List of Provisioning Server

typedef sequence<Resource_T> Server attribute. objects in Resource_T format.
ResourceList_T;
Route_T No corresponding Provisioning Not applicable

typedef sequence<CrossConnect_T> Server attribute.
Route_T;
struct SNCCreateData_T {
string userLabel; No corresponding Provisioning Circuit Name

Server attribute.
boolean forceUniqueness; No corresponding Provisioning The value is true, else ignored.

Server attribute.
globaldefs::ConnectionDirection_T No corresponding Provisioning Values can be: CD_UNI,

direction; Server attribute. CD_BI. All circuits are
bidirectional, except
Point-to-Multipoint.
StaticProtectionLevel_T No corresponding Provisioning The NMS must specify the

staticProtectionLevel; Server attribute. The values are not requested
supported. staticProtectionLevel as
specified in SNC Types.


Attribute
ProtectionEffort_T protectionEffort; No corresponding Provisioning EFFORT_WHATEVER is

Server attribute. only supported.
Reroute_T rerouteAllowed; No corresponding Provisioning RR_YES for all circuit types

Server attribute. (except for SVC, the value is
RR_NO).
NetworkRouted_T networkRouted; No corresponding Provisioning NR_YES indicates that the

Server attribute. route is computed by the
network.
SNCType_T sncType; No corresponding Provisioning ST_SIMPLE for Point to point

Multipoint SPVCs.
ST_ADD_DROP_A for
redirecting circuits, PVC with
protection and service naming
binding.

layerRate; Server attribute. ATM Network Interfaces (UNI
ATM Virtual Paths,
LR_ATM_VC for ATM
Virtual Channels,
rate.
For FR: LR_FR_NI
CrossConnectList_T ccInclusions; No corresponding Provisioning Not supported.

Server attribute
ResourceList_T neTpInclusions; No corresponding Provisioning Not supported.

Server attribute
boolean fullRoute; No corresponding Provisioning Not supported.

Server attribute
ResourceList_T neTpSncExclusions; No corresponding Provisioning Not supported.

Server attribute


Attribute
globaldefs::NamingAttributesList_T Endpoint 1 See “CTP -

aEnd; NamingAttributes” on
page 23-5.
globaldefs::NamingAttributesList_T Endpoint 2 See “CTP -

zEnd; NamingAttributes” on
page 23-5.
globaldefs::NVSList_T No corresponding Provisioning Mandatory attribute: name,

additionalCreationInfo; }; Server attribute bandwidth,
servicetype,<service>
type for both the endpoints
must be specified. The names
are as follows:
FWD_QOSCLASS,
REV_QOSCLASS,
FWD_ZERO_CIR,
REV_ZERO_CIR,
aEndName,aEndServiceType,
aEnd<service>Type,
aEndBandwidth, zEndName,
zEndServiceType,
zEnd<service>Type and
zEndBandwidth
SNCState_T No corresponding Provisioning SNCS_ACTIVE is the only

enum SNCState_T Server attribute. supported value.
{SNCS_PENDING, SNCS_ACTIVE,
SNCS_PARTIAL,
SNCS_NONEXISTENT };
SNCType_T No corresponding Provisioning ST_SIMPLE for Point to point

enum SNCType_T
{ST_SIMPLE, ST_ADD_DROP_A,
ST_ADD_DROP_Z,
Multipoint SPVCs.
ST_INTERCONNECT,
ST_DOUBLE_INTERCONNECT, ST_ADD_DROP_A for
ST_DOUBLE_ADD_DROP, redirecting circuits, PVC with
ST_OPEN_ADD_DROP, protection and service naming
ST_EXPLICIT }; binding.
StaticProtectionLevel_T No corresponding Provisioning Not supported

Server attribute.
enum StaticProtectionLevel_T
{PREEMPTIBLE, UNPROTECTED,
PARTIALLY_PROTECTED,
FULLY_PROTECTED,
HIGHLY_PROTECTED };


Attribute
SubnetworkConnectionList_T No corresponding Provisioning List of Provisioning Server

typedef Server attribute. circuits in
sequence<SubnetworkConnection_T> SubnetworkConnection_T
SubnetworkConnectionList_T; format.
struct TPData_T { Maps to PPort, IMA group, IMA

link, Channel and LPort.
globaldefs::NamingAttributes_T PPort / LPort See “trafficDescriptor” on

tpName; page 23-9 and
“trafficDescriptor” on
page 23-9.
terminationPoint::TerminationMode_T No corresponding Provisioning TM_NEITHER_

tpMappingMode; Server attribute. TERMINATED_NOR_
AVAILABLE_FOR_
MAPPING for LPorts. This
value can be used as circuit
endpoints. The LPorts cannot
have any other mode.
TM_TERMINATED_AND_
AVAILABLE_FOR_
MAPPING for channels, IMA
groups.
TM_NA for PPorts and IMA
group.

used.
globaldefs::NamingAttributes_Tegress No corresponding Provisioning Empty string is used

TrafficDescriptorName; }; Server attribute.

TPDataList_T No corresponding Provisioning List of Provisioning Server

Server attribute. objects in TPData_T (PPort,
typedef sequence<TPData_T>
IMA group, IMA link,
TPDataList_T;
Channel and LPort) format.

protection
protection
Table 24-22.protection - Provisioning Server Object Mapping
protection Provisioning Server APS and servicename objects
Table 24-23.protection - Attributes

Attribute
struct ProtectionGroup_T {


Server attribute.
string nativeEMSName; No corresponding Provisioning APS/ServiceNameBinding

Server attribute. ObjectID is used

Server attribute.
ProtectionGroupType_T No corresponding Provisioning Only PGT_MSP_1_PLUS_1 is

protectionGroupType; Server attribute. supported on Lucent
equipment.
ProtectionSchemeState_T No corresponding Provisioning • PSS_FORCED_OR_

protectionSchemeState; Server attribute. LOCKED_OUT or
PSS_UNKNOWN will be
used.
• PSS_AUTOMATIC is for
1:N configurations which is
not supported by
Provisioning Server.
ReversionMode_T reversionMode; For aps object "Revertive" attr. For resilient UNI/NNI
serviceNames, the value is
For serviceNames and RLMI
always
bindings, "RLMISwitchOverMode"
RM_NON_REVERTIVE.
attr.

protection
Table 24-23.protection - Attributes (Continued)

Attribute

ATM Virtual Paths,
LR_ATM_VC for ATM Virtual
Channels, LR_DS0_64K, DS0
CTP layer rate.
For FR: LR_FR_NI
globaldefs::NamingAttributesList_T No corresponding Provisioning List of TPs (PTP for aps, CTP

pgpTPList; Server attribute. for serviceName) in the order -
working TP followed by
protection TP.
globaldefs::NVSList_T • SwitchMode - for aps : Provisioning Server supports

pgpParameters; "Direction" attr, for serviceName only 1+1 MSP parameters.
: "DualEnded"
• WtrTime - for aps: "WtrPeriod"

attr, for UNI/NNI bindings "-1"
(not applicable)
• HoldOffTime
globaldefs::NVSList_T No corresponding Provisioning Other attributes of APS or

additionalInfo; }; Server attribute. servicename objects not
included above.

protection

Attribute
ProtectionCommand_T No corresponding Provisioning Maps to the aps commands of

enum ProtectionCommand_T Server attribute. Provisioning Server CLI.
{PC_CLEAR, PC_LOCKOUT,
Refer to Provisioning Server
PC_FORCED_SWITCH,
Object Attribute Reference.
PC_MANUAL_SWITCH,
PC_EXERCISER}; For servicename binding the
commands supported are
• PC_CLEAR maps to
Provisioning Server
ServiceNameBinding
Attribute Primary
• PC_FORCED_SWITCH à
maps to Provisioning
Server
ServiceNameBinding
Attribute Backup.
ProtectionGroupList_T No corresponding Provisioning List of APS and/or

Server attribute. ServiceNameBinding ObjectID
typedef
is used.
sequence<ProtectionGroup_T>
ProtectionGroupList_T;
ProtectionGroupType_T No corresponding Provisioning Provisioning Server supports

Server attribute. only PGT_MSP_1_PLUS_1.
enum ProtectionGroupType_T
{PGT_MSP_1_PLUS_1,
PGT_MSP_1_FOR_N,
PGT_2_FIBER_BLSR,
PGT_4_FIBER_BLSR};
ProtectionSchemeState_T No corresponding Provisioning PSS_FORCED_OR_LOCKED

Server attribute. _OUT or PSS_UNKNOWN
enum ProtectionSchemeState_T
will be used.
{PSS_UNKNOWN,
PSS_AUTOMATIC is for 1:N
PSS_AUTOMATIC,
configurations which is not
PSS_FORCED_OR_LOCKED_OUT
supported by Provisioning
};
Server.
ProtectionType_T No corresponding Provisioning Only PT_MSP_APS is used.

Server attribute.
enum ProtectionType_T {
PT_MSP_APS, PT_SNCP };

protection

Attribute
ReversionMode_T For aps object "Revertive" attribute. For resilient UNI/NNI

For serviceNames and RLMI serviceNames, the value is
enum ReversionMode_T
bindings, "RLMISwitchOverMode" always
{RM_UNKNOWN,
attribute. RM_NON_REVERTIVE.
RM_NON_REVERTIVE,
RM_REVERTIVE};
struct SwitchData_T {
ProtectionType_T protectionType: No corresponding Provisioning PT_MSP_APS

Server attribute.
SwitchReason_T switchReason; No corresponding Provisioning An appropriate value as per

Server attribute. TMF814A Version 2.1 will be
used.

layerRate; Server attribute. ATM Network Interfaces (UNI
ATM Virtual Paths,
CTP layer rate.
For FR: LR_FR_NI

groupName; Server attribute.
globaldefs::NamingAttributes_T No corresponding Provisioning For APS, the working PPort.

protectedTP: Server attribute. For service names, the primary
binding.
globaldefs::NamingAttributes_T No corresponding Provisioning For APS, the working PPort.

switchToTP; Server attribute. For service names, the backup
binding.
globaldefs::NVSList_T No corresponding Provisioning All other Provisioning Server

additionalInfo; }; Server attribute. attributes for APS /
ServiceNameBinding
SwitchDataList_T No corresponding Provisioning List of SwitchData

typedef sequence<SwitchData_T> Server attribute.
SwitchDataList_T;

protection

Attribute
SwitchReason_T No corresponding Provisioning An appropriate value as per

enum SwitchReason_T Server attribute. TMF814A Version 2.1 will be
{SR_SIGNAL_FAIL, used.
SR_SIGNAL_DEGRADE, SR_NA,
SR_RESTORED,
SR_SIGNAL_MISMATCH,
SR_AUTOMATIC_SWITCH,
SR_MANUAL };

trafficDescriptor
trafficDescriptor
Table 24-24.trafficDescriptor - Attributes

Attribute
ServiceCategory_T QosClass
enum ServiceCategory_T
{SC_CBR, SC_VBRRT,
SC_VBRNRT, SC_ABR, SC_UBR,
SC_GFR, SC_NA };
struct TrafficDescriptor_T {
globaldefs::NamingAttributes_T No corresponding Provisioning See “trafficDescriptor -

name; Server attribute. Attributes” on page 24-34.
string userLabel; Name
string nativeEMSName; No corresponding Provisioning “TrafficDesc” ObjectID is


Server attribute.
ServiceCategory_T serviceCategory; QosClass CBR, VBR Real Time, UBR

Non Real Time, UBR, ABR,
Unsp CBR, UnspVBRVrt,
UnspBestEffort
TrafficParameterList_T Type, Param1, Param2 and Param3 PCR, SCR, MBS and MCR are
trafficParameters; are used accordingly available from the database.
CDV and CDVT are LPort
/circuit attributes. These are not
bound to a traffic descriptor in
Provisioning Server "Type"
attribute.
string conformanceDefinition; No corresponding Provisioning UNI 3.1 (default) and 4.0 are
Server attribute. both supported by Provisioning
Server.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning TrafficDescriptor “Name” is

}; Server attribute. mandatory parameter.
TrafficDescriptorList_T No corresponding Provisioning List of Provisioning Server

sequence<TrafficDescriptor_T> TrafficDescriptorList_T
TrafficDescriptorList_T; format.

trafficDescriptor
Table 24-24.trafficDescriptor - Attributes (Continued)

Attribute
TrafficParameterList_T No corresponding Provisioning PCR, SCR, MBS and MCR are

Server attribute. supported values.
typedef globaldefs::NVSList_T
TrafficParameterList_T; For more information about
TrafficDescriptor attributes
(such as
QosClass =UnspVBRNrt,
Type=PcrClp01ScrClp0Mbs
Clp0)

transmissionParameters
Table 24-25.transmissionParameters - Attributes
Attribute
LayeredParameterList_T No corresponding Provisioning List of LayerRate and

typedef Server attribute. Transmission Parameter in
sequence<LayeredParameters_T> LayeredParameterList_T
LayeredParameterList_T; format.
struct LayeredParameters_T {
LayerRate_T layer; No corresponding Provisioning For ATM: LR_ATM_NI for

Server attribute. ATM Network Interfaces (UNI
ATM Virtual Paths,
CTP layer rate.
For FR: LR_FR_NI
globaldefs::NVSList_T List of Provisioning Server LPort

transmissionParams; }; attribute used.
LayerRate_T No corresponding Provisioning For ATM: LR_ATM_NI for

Server attribute. ATM Network Interfaces (UNI
typedef short LayerRate_T;
ATM Virtual Paths,
CTP layer rate.
For FR: LR_FR_NI
LayerRateList_T No corresponding Provisioning List of LayerRate and

Server attribute. Transmission Parameter in
typedef sequence<LayerRate_T>
LayerRateList_T format.
LayerRateList_T;

guiCutThrough
guiCutThrough
Table 24-26.guiCutThrough - Attributes

Attribute
struct GCTProfileInfo_T {
ServerLaunchCapability_T No corresponding Provisioning CLIENT_LAUNCH_ONLY

Server attribute.
serverLaunchCapability;
string gctHostname; No corresponding Provisioning Provisioning Server IP address

Server attribute.
string emsGctPlatform; No corresponding Provisioning Unix

Server attribute.
GuiCutThroughDataList_T No corresponding Provisioning List of GuiCutThroughData_T

guiCutThroughDataList; }; Server attribute.
struct GuiCutThroughData_T {
string gctScope; No corresponding Provisioning EMS

Server attribute.
string gctContext; No corresponding Provisioning TOP_LEVEL

Server attribute.
string gctCommand; No corresponding Provisioning rsh PS_IP_ADDRESS -n

Server attribute. "/opt/NavisXtend/
TMFAdapter/bin/
shellexe.sh <GCTDisplay>”
globaldefs::NVSList_T No corresponding Provisioning None

additionalInfo; }; Server attribute.
GuiCutThroughDataList_T No corresponding Provisioning List of GuiCutThroughData_T

Server attribute.
typedef
sequence<GuiCutThroughData_T>
GuiCutThroughDataList_T;
enum ServerLaunchCapability_T { No corresponding Provisioning CLIENT_LAUNCH_ONLY

Server attribute.
CLIENT_LAUNCH_ONLY,
SERVER_LAUNCH_CAPABLE };

maintenanceOps
maintenanceOps
Table 24-27.maintenanceOps - Attributes

Attribute
struct CurrentMaintenanceOperation_T {
globaldefs::NamingAttributes_T No corresponding Provisioning See “CTP - Attributes” on

tpName; Server attribute. page 24-20.
MaintenanceOperation_T LoopbackType "FACILITY_LOOPBACK"

maintenanceOperation; Far End Loopback,
"TERMINAL_LOOPBACK"
Near End Loopback,
"FACILITY_FORCED_AIS
"Not supported by
Provisioning Server,
"TERMINAL_FORCED_
AIS" Not supported by
Provisioning Server,
"FORCE_RDI"Not supported
by Provisioning Server,
"END_TO_END_LOOPBAC
K_OAM_CELL" (ATM)
PVC-OAM ,
"SEGMENT_LOOPBACK_
OAM_CELL" (ATM)
PVC-OAM
"FACILITY_LOOPBACK",
Far End Loopback,
"TERMINAL_LOOPBACK",
Near End Loopback: only
these maintenanceOperations
operations are supported on a
PTP/CTP but not on a
ManagedElement.
PTPs supported are PPort.
CTPs supported are channel
and LPort.

maintenanceOps
Table 24-27.maintenanceOps - Attributes (Continued)

Attribute
transmissionParameters::LayerRate_T No corresponding Provisioning For ATM:

layerRate; Server attribute. LR_ATM_NI for ATM
Network Interfaces (UNI and
NNI),
LR_ATM_VP for ATM
Virtual Paths,
LR_ATM_VC for ATM
Virtual Channels,
LR_DS0_64K,
DS0 CTP layer rate.
For FR: LR_FR_NI
See “Mapping TMF 814
Layer Rates with
Provisioning Server” on
page A-1.
globaldefs::NVSList_T additionalInfo; No corresponding Provisioning Other Provisioning Server

}; Server attribute. Diagnostics attribute is used.
For more information, refer
the Provisional Server Object
Attribute Guide.
CurrentMaintenanceOperation No corresponding Provisioning List of Diagnostics under

List_T Server attribute. progress.
typedef sequence
<CurrentMaintenanceOperation_T>
CurrentMaintenanceOperationList_T;
MaintenanceOperation_T LoopbackType Valid values are:

"FACILITY_LOOPBACK",
typedef string
"TERMINAL_
MaintenanceOperation_T;
LOOPBACK",
"FACILITY_FORCED_
AIS",
"TERMINAL_FORCED_
AIS", "FORCE_RDI",
"SET_AS_SEGMENT_END
_POINT" (ATM),
"END_TO_END_
LOOPBACK_OAM_CELL"
(ATM),
"SEGMENT_LOOPBACK_
OAM_CELL" (ATM)

maintenanceOps
Table 24-27.maintenanceOps - Attributes (Continued)

Attribute
enum cvstartdiag / cvstopdiag command

MaintenanceOperationMode_T
{MOM_OPERATE,
MOM_RELEASE };

performance
performance
Note – performance module is not supported.
common
Table 24-28.common - Attributes
Attribute
Capability_T No corresponding Provisioning An appropriate value as per

Server attribute. TMF814A Version 2.1 will be
typedef
used.
globaldefs::NameAndStringValue_T
Capability_T;
CapabilityList_T No corresponding Provisioning List of Provisioning Server

Server attribute. objects in Capability_T format.
typedef sequence<Capability_T>
CapabilityList_T;

common

25
Iterators for Provisioning Server TMF
814A Implementation
Iterators are supported as per TMF 814A. The following table provides the iterator
support information for each module:
Table 25-1. Iterators for Provisioning Server TMF 814A Implementation

Module Supported
equipment Yes
globaldefs Yes
maintenanceOps Yes
managedElement Yes
multiLayerSubnetwork Yes
Subnetwork
notifications Yes
performance No
protection Yes
subnetworkConnection Yes
terminationPoint Yes
topologicalLink Yes
trafficDescriptor Yes

Iterators for Provisioning Server TMF 814A Implementation
Note – Navis EMS-CBGX TMF 814 Adapter supports 50 iterators only. Use the
destroy() method once the listing is not required for client usage.

26
Troubleshooting Navis EMS-CBGX TMF
814A Implementation
This chapter provides Navis EMS-CBGX TMF 814 Adapter troubleshooting

information for administrators. This chapter contains:
• “Implementation Problems” on page 26-1
Implementation Problems
• Invalid Attribute name: FwdqosClass. It should be as shown in Provisioning
Server Attribute Guide
Ensure that the attributes follow the conventions specified by Provisioning Server.
For more information about the attributes, see Provisioning Server Object
Attribute Definition User’s Reference documentation.
• CORBA::Unknown exception to client in giving additionalInfo input data
from client to Navis EMS-CBGX TMF 814 Adapter.
For provisioning card, subcard and creating circuits, the input data for Navis
EMS-CBGX TMF 814 Adapter contains additionalInfo structure.
To provide additionalInfo (input data from client to Navis EMS-CBGX TMF 814
Adapter), follow these instructions:
1. additionalInfo should be created with valid length. Sufficient memory should be
allocated.
2. The contents, that is the name and value strings should be empty strings (if
information is not provided). For example,
additionalInfo.name = ""
additionalInfo.value = "".
Otherwise, if the input data for additionalInfo or the contents (name or value) are
null, this results in CORBA::Unknown exception at client side.

Troubleshooting Navis EMS-CBGX TMF 814A Implementation
Implementation Problems

A
Mapping TMF 814 Layer Rates with
Provisioning Server
This appendix covers these sections
• “Transport Technologies” on page A-1
• “ATM CTP Layering” on page A-3
Transport Technologies
The following transport technologies are used in conjunction with TCP/IP model,
where PTP and CTP are created at different layer rate (line rate). These layer rates are
used in PTP/CTP object naming convention of TMF 814.
Figure A-1. Transport Technologies at various layers, and TMF object
Navis EMS-CBGX TMF 814 Adapter Implementation Reference A-1

Mapping TMF 814 Layer Rates with Provisioning Server
Transport Technologies
Figure A-2. MTNM and G.805 Layered Model
Refer layers.pdf (TeleManagement Forum documentation) to know more about G.805

terminology and MTNM modeling.
A-26/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

ATM CTP Layering
ATM CTP Layering

The following table lists the TMF 814 layer rates for ATM.
Table A-1. TMF 814 Layer Rates for ATM

ID Layer Identifier Object Naming Description
String
43 LR_ATM_NI lport, startVpi, or For ATM Network Interfaces (UNI

pport.x.vpi.y and NNI)
44 LR_ATM_VP vpi For ATM Virtual Paths
45 LR_ATM_VC vci For ATM Virtual Channels
Additionally, the following layer rates are applicable:

• The layer rate for ATM UNI/NNI/Direct Trunk/Virtual/ OPT Cell Trunk LPort is
LR_ATM_NI.
• The layer rate for ATM Circuit Endpoint is LR_ATM_VP, LR_ATM_VC.
• The layer rate for FR UNI/NNI/Direct Trunk/Virtual/ OPT Line Trunk LPort is
LR_FR_IF.
• The layer rate for FR Circuit Endpoint is LR_ATM_PVC.
Navis EMS-CBGX TMF 814 implementation maps the layer rate at PTP (PPort,
Channel, ImaGroup) and CTP (ImaLink/LPort). Follow the naming conventions as per
TMF 814A object naming convention as mentioned in “TMF 814A Object
NamingAttributes for Provisioning Server” on page 23-1. Though there are various
layer rates supported at PTP level in Lucent switches, EMS is restricted to configure
and use only few layer rates as illustrated in the following sections using card and
equipment as examples:
• “8 Port DS3 (ATM) Card” on page A-4
• “8 Port E3 (ATM) Card” on page A-5
• “4 Port OC-3c/STM1 Card” on page A-6
• “6 Port FR DS3 Card” on page A-7
• “6 Port FR Channelized DS3 Card (Only 3/1/10)” on page A-8
Note – Layer rate for PTP is not distinguished and input is not considered in Navis
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04A-3

ATM CTP Layering
8 Port DS3 (ATM) Card

PTP/CTP Layering for 8 Port DS3 ATM card is as depicted in the following
illustration:
Figure A-3. 8 Port E3 ATM Card on CBX 500
Note – All LPorts types are possible: ATM UNI/NNI/Direct and

Trunk/Opti-Trunk.
1. CTP at LR_ATM_NI: It can be ATM UNI/NNI LPort on which

Atm-OPTimum-Cell Trunk LPort can be created to carry data to NE other than
Lucent NE.
2. CTP at LR_ATM_NI: It can be ATM UNI/NNI Virtual LPort.
This card has DS3 SONET PPort that carries ATM Cell.
Table A-2. PTP/CTP Naming for Provisioning Server PPort / LPort

Provisioning Server PPort / LPort Layer Rate TMF PTP / CTP Name
Name
PPort.1 LR_DS3_45M /port=1
LPort.1 (Atm UNI/NNI/Direct Trunk) LR_ATM_NI /lport=1
startVpi.1 (Atm Virtual LPort) LR_ATM_NI /startVpi.1

ATM CTP Layering
Name
Vpi.1 (Atm OPT cell Trunk LPort) LR_ATM_NI /vpi.1
LPort.1.vpi.3 circuit endpoint LR_ATM_VP /lport=1/vpi=3
LPort.1.vpi.3.vci.32 (32-4095) ckt LR_ATM_VC /lport=1/vpi=3/vci=32

endpoint
8 Port E3 (ATM) Card

PTP/CTP Layering for 8 Port E3 ATM card is as depicted in the following illustration:
Figure A-4. 8 Port E3 ATM Card on CBX 500
Note – All LPorts types are possible: ATM UNI/NNI/Direct and

Trunk/Opti-Trunk.

Lucent NE.

ATM CTP Layering

Name
PPort.1 LR_E3_34M /port=1
LPort.1 (Atm UNI/NNI/Direct Trunk) LR_ATM_NI /lport=1
startVpi.1 (Atm Virtual LPort) LR_ATM_NI /startVpi.1
Vpi.1 (Atm OPT cell Trunk LPort) LR_ATM_NI /vpi.1
LPort.vpi.3.vci.32 (32-4095) ckt LR_ATM_VC /lport=1/vpi=3/vci=32

endpoint
4 Port OC-3c/STM1 Card

PTP/CTP Layering for 4 Port OC-3c/STM1 card is as depicted in the following
illustration:
Figure A-5. 4 Port OC3c/STM1 ATM Card on CBX 500

ATM CTP Layering
Note – CTP with Layers:

Lucent NE, or it can be used as SNC endpoint.

Provisioning Server PPort / LPort Name Layer Rate TMF PTP / CTP
Name
PPort.1 All mentioned /port=1

above
LPort.1 (Atm Uni/NNI LPort) LR_ATM_NI /lport=1
startVpi.1 (Atm Virtual LPort) LR_ATM_NI /startVpi=1
Vpi.1 (Atm OPT cell Trunk LPort) LR_ATM_NI /vpi=1
LPort.vpi.3.vci.32 (32-4095) ckt endpoint LR_ATM_VC /lport=1/vpi=3/vci=32
6 Port FR DS3 Card

This is non-channelized card and a maximum of one LPort can be created on a PPort.
Each PPORT is DS3, and each direct LPort is DS3.
4 different types of LPorts are possible:

• FR UNI DCE (network side): LPort name is: pport.3.lport.1
• FR UNI DTE(user side):LPort name is: pport.4.lport.1
• FR NNI: LPort name is: pport.lport.1
• FR Optimum PVC Trunk (DLCI 16..991): LPort name is: pport.4.dlci.16 (DLCI
must be 16-991). It can be created on any of the FR UNI/NNI LPort as feeder
LPort.
No virtual LPort is supported on this card.

ATM CTP Layering

Name
PPort.4 LR_DS3_45M /port=4
LPort.1 (FR Uni/NNI LPort) LR_FR_IF /lport=1
Virtual LPort creation not allowed None None
dlci.16[991] (FR OPT cell Trunk LR_FR_IF /dlci=16..991

LPort)
lport.1.dlci.n (FR circuit) LR_FR_PVC /lport=1/dlci=n
6 Port FR Channelized DS3 Card (Only 3/1/10)

PTP/CTP Layering for 6 Port FR Channelized DS3 Card (only 3/1/0) is as depicted in
the following illustration:
Figure A-6. 6 Port FR Channelized DS3 Card

ATM CTP Layering

Provisioning Server PPort / Layer Rate TMF PTP / CTP Name
LPort Name
PPort.4 LR_T3_DS3_45M /port=4
channel.23 LR_FR_IF /channel=23
channel.23.LPort.4 LR_FR_IF /channel=23/lport=4

(FR Uni/NNI LPort)
channel.23.dlci.1 LR_FR_IF /channel=23/dlci=1

(FR Virtual LPort)
channel.23.dlci.16[991] LR_FR_IF /channel=23/dlci=16..991, here

(FR OPT Line Trunk LPort) dlci starts at 16.
channel.23.LPort.4. LR_FR_PVC /channel=23/lport=4/dlci=n

dlci.n (FR circuit) (InUse)

ATM CTP Layering

B
Supported Layer Rates in Navis
EMS-CBGX TMF 814 Adapter
Layer Rates
The following table lists the layer rates supported by Navis EMS-CBGX TMF 814
Adapter:
Table B-1. Supported Layer Rates

Interface Operations / API Mandatory Layer Rate Comments
Module
ManagedElementMgr_I
getContainedCurrentTP Optional LR_ATM_NI, Returns CTPs as

Names LR_FR_IF NamingAttributes
getContainedCurrentTPs Optional LR_ATM_NI, Returns CTPs

LR_FR_IF,
getContainedInUseTPNames Mandatory LR_ATM_NI, Returns PVC endpoint

LR_ATM_VP, object IDs as CTPs
LR_ATM_VC,
LR_FR_IF,
LR_FR_PVC
getContainedInUseTPs Mandatory LR_ATM_NI, Returns PVC endpoint as

LR_ATM_VP, CTPs
LR_ATM_VC,
LR_FR_IF,
LR_FR_PVC
Navis EMS-CBGX TMF 814 Adapter Implementation Reference B-1

Supported Layer Rates in Navis EMS-CBGX TMF 814 Adapter
Layer Rates
Interface Operations / API Mandatory Layer Rate Comments

Module
getContainedPotentialTP Mandatory LR_ATM_NI, Returns CTPs as

Names LR_ATM_VP, NamingAttributes
LR_ATM_VC,
LR_FR_IF,
LR_FR_PVC
getContainedPotentialTPs Mandatory LR_ATM_NI, Returns CTPs

LR_ATM_VP,
LR_ATM_VC,
LR_FR_IF,
LR_FR_PVC
MultiLayerSubnetworkMgr_I
getAllSubnetwork Mandatory LR_ATM_VP, Returns PVC object IDs

ConnectionNames LR_ATM_VC, as
LR_FR_PVC NamingAttributesList_T.
getAllSubnetwork Mandatory LR_ATM_VP, Returns PVCs

Connections LR_ATM_VC,
LR_FR_PVC
getAllSubnetworkConnection Mandatory LR_ATM_VP, Returns PVCs object IDs

NamesWithTP LR_ATM_VC, as
LR_FR_IF NamingAttributesList_T
getAllSubnetwork Mandatory LR_ATM_VP, Returns PVCs

ConnectionsWithTP LR_ATM_VC,
LR_FR_IF
B-26/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Transmission Parameters for Layer Rates

Table B-2. Transmission Paramenters for Layer Rates
Layer Name Value Provisioning Server
Identifier Attribute
LR_ATM_NI ActualMaximum SvcVpiMax

SVCVPI
ActualMinimum SvcVciMax
SVCVCI
ATMNIType UNI ,BICI, BISS -I AtmType
Bandwidth Bandwidth
ILMIVCI Number IlmiVciBits
ILMIVPI Number IlmiVpiBits
MaxVCIBits Number NumOfValidVciBits
MaxVPIBits Number NumOfValidVpiBits
AtmSignalingType AtmProtocol
Note – The transmissionParameters mappings for layer rate LR_FR_IF (Frame

Relay) are not supported in Navis EMS-CBGX TMF 814 Adapter.
Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04B-3

B-46/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Acronyms
This guide uses the following acronyms:
Acronym Description
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
BGP Border Gateway Protocol
CE Circuit Emulation
CAC Connection Admission Control;

Call Admission Control
CLI Command Line Interface
CS Cell Switching
CTP Connection Termination Point
CUG closed user group
DCE data communications equipment
DLCI Data Link Connection Identifier
DS digital service
DTE data terminal equipment
DVMRP Distance Vector Multicast Routing Protocol
DXI Data Exchange Interface
FDL facility data link
FRAD Frame Relay assembler/disassembler
Navis EMS-CBGX TMF 814 Adapter Implementation Reference Acronyms-1

Acronyms
Acronym Description
IGMP Internet Group Multicast Protocol;

Internet Group Management Protocol
IMA Inverse Multiplexing for ATM
IP Internet Protocol
LPort logical port
LSP label switch path
MIB Management Information Base
NHRP Next Hop Resolution Protocol
NMS Network Management System
NNI Network-to-Network Interface
OSPF Open Shortest Path First
Phy physical sublayer; physical interface module
PM performance monitoring
PMP point-to-multipoint
PNNI Private Network-to-Network Interface
PPort physical port
PRAM parameter random access memory
PTP Physical Termination Point
PVC permanent virtual circuit
QoS Quality of Service
RIP Routing Information Protocol
SNC Subnetwork Connection
SNMP Simple Network Management Protocol
SPVC soft permanent virtual circuit
SRN Software Release Notice
SVC switched virtual circuit
TAC Technical Assistance Center
TCA threshold crossing alert/alarm
Acronyms-26/21/04 NavisXtend Provisioning Server CLI User’s Reference

Beta Draft Confidential Acronyms
Acronym Description
TMF TeleManagement Forum
TP Termination Point
NavisXtend Provisioning Server CLI User’s Reference Acronyms-3

Acronyms
Acronyms-46/21/04 NavisXtend Provisioning Server CLI User’s Reference

Index
Index
C equipment module
data types, 7-10
common module EquipmentInventoryMgr_I, 7-2
Common_I, 22-2 notifications, 7-10
data types, 22-4
notifications, 22-4
G
D globaldefs module
data types, 20-2
Data types NamingAttributesIterator_I, 20-2
common module, 22-4 guiCutThrough module
emsMgr module, 2-6 data types, 14-3
emsSession module, 4-3 GuiCutThroughMgr_I, 14-2
equipment module, 7-10 notifications, 14-3
globaldefs module, 20-2
guiCutThrough module, 14-3
maintenanceOps module, 15-3 I
managedElement module, 6-15
multiLayerSubnetwork module, 5-20 Interfaces, 3-2
notifications module, 21-2 Common_I, 22-2
protection module, 11-6 CurrentMaintenanceOperationIterator_I, 15-2
subnetworkConnection module, 10-2 EMSMgr_I, 2-1
terminationPoint module, 8-2 EmsSession_I, 4-2
topologicalLink module, 9-2 EmsSessionFactory_I, 3-2
trafficDescriptor module, 12-5 EquipmentInventoryMgr_I, 7-2
transmissionParameters module, 13-2 EventIterator_I, 21-2
GuiCutThroughMgr_I, 14-2
MaintenanceMgr_I, 15-2
E ManagedElementMgr_I, 6-2
MultiLayerSubnetworkMgr_I, 5-2
emsMgr module NamingAttributesIterator_I, 20-2
data types, 2-6 NmsSession_I, 17-2
EMSMgr_I, 2-1 ProtectionGroupIterator_I, 11-2
notifications, 2-6 Session_I, 19-2
emsSession module SNCIterator_I, 10-2
data types, 4-3 TerminationPointIterator_I, 8-2
emsSession_I, 4-2 TopologicalLinkIterator_I, 9-2
notifications, 4-3 topologicalLinkIterator_I, 9-2, 11-2
EmsSessionFactory module trafficDescriptorMgr_I, 12-2
EmsSessionFactory_I, 3-2 Version_I, 16-2
Navis EMS-CBGX TMF 814 Adapter Implementation Reference Index-1

Index
M overview, 1-1
TMF Objects, 1-4
maintenanceOps module usage information, 1-5
CurrentMaintenanceOperationIterator_I, 15-2 nmsSession module
data types, 15-3 NmsSession_I, 17-2
MaintenanceMgr_I, 15-2 Notifications
notifications, 15-3 common module, 22-4
managedElement module emsMgr module, 2-6
data types, 6-15 emsSession module, 4-3
ManagedElementMgr_I, 6-2 equipment module, 7-10
Notifications, 6-15 guiCutThrough module, 14-3
Modules maintenanceOps module, 15-3
common, 22-1 managedElement module, 6-15
emsMgr, 2-1 multiLayerSubnetwork module, 5-20
emsSession, 4-1 protection module, 11-6
emsSessionFactory, 3-1 trafficDescriptor module, 12-6
equipment, 7-1 notifications module
globaldefs, 20-1 data types, 21-2
guiCutThrough, 14-1 EventIterator_I, 21-2
maintenanceOps, 15-1
managedElement, 6-1
mtnmVersion, 16-1 P
multiLayerSubnetwork, 5-1
nmsSession, 17-1 protection module
notifications, 21-1 data types, 11-6
performance, 18-1 notifications, 11-6
protection, 11-1 ProtectionMgr_I, 11-2
session, 19-1 Provisioning Server
subnetworkConnection Module, 10-1 mandatory object attributes for equipment, 7-10
terminationPoint, 8-1 mandatory object attributes for
topologicalLink, 9-1 TDCreateData_T, 12-7
trafficDescriptor, 12-1 object hierarchy, 1-2
transmissionParameters, 13-1 TMF 814A Object NamingAttributes, 23-1
mtnmVersion module
Version_I, 16-2
multiLayerSubnetwork module Q
data types, 5-20
QoS and Admin Parameters, 1-3
MultiLayerSubnetworkMgr_I, 5-2
notifications, 5-20
R
N Recommendations
General, 1-3
Navis EMS-CBGX TMF 814 Adapter
Requirements
constraints, 1-3
Index-2 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Index
EMS requirements, 1-2
S
session module
Session_I, 19-2
subnetworkConnection module
data types, 10-2
SNCIterator_I, 10-2
T
terminationPoint module
data types, 8-2
TerminationPointIterator_I, 8-2
topologicalLink module
data types, 9-2
TopologicalLinkIterator_I, 9-2, 11-2
TopologicalLinkIterator module
TopologicalLinkIterator_I, 9-2
trafficDescriptor module
data types, 12-5
notifications, 12-6
trafficDescriptorMgr_I, 12-2
data types, 13-2
Navis EMS-CBGX TMF 814 Adapter Implementation Reference Index-3

Index
Index-4 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Navis EMS-CBGX TMF 814 Adapter
Implementation Reference
Customer Comments
Please take time to send us your comments so that we can do our best to meet your
documentation needs. Complete and mail this questionnaire or e-mail your comments to
our Technical Publications Dept. Your opinions are of great value to us!
EMAIL:cspubs@lucent.com
MAILING ADDRESS:
Lucent Technologies
Multiservice Switching
1 Robbins Road Westford, MA 01886
What tasks did you perform using this guide?
Did you install the hardware/software?

If you were having trouble performing a task, were you able to find the
information you needed? Was the index useful?
Were the examples and illustrations helpful for performing tasks? If not, how
can they be improved?
Was there any information you needed that was not in the manual? If so, how
can we best deliver that information to you?
Cut Here
What did you like/not like about the manual?
Do you have any other comments about the manual?
Page Description of Error
Name Company
Mailing Address
Phone E-mail address

Fax No.

86011REV000 - V1 - Navis EMS-CBGX TMF 814 Adapter Implementation Reference Software Release 09.02.00.00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

86011REV000 - V1 - Navis EMS-CBGX TMF 814 Adapter Implementation Reference Software Release 09.02.00.00

Uploaded by

Copyright:

Available Formats

Beta Draft Confidential

Product Code: 86011

Copyright© 2004 Lucent Technologies. All Rights Reserved.

For permission to reproduce or distribute, please contact: Technical Publications,

Trademarks. IP Navigator, Navis, NavisXtend, Navis iEngineer, CBX 3500 and

Limited Warranty. Lucent Technologies provides a limited warranty to this

ii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

LUCENT TECHNOLOGIES END-USER LICENSE AGREEMENT

Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04iii

6. Limitation of Liability. Lucent’s cumulative liability to you or any other party

iv6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

7. Proprietary Rights Indemnification. Lucent shall at its expense defend you

9. Governing Law. This License Agreement shall be construed and governed in

10. Miscellaneous. If any action is brought by either party to this License

Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04v

vi6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Chapter 2 emsMgr Module

Navis EMS-CBGX TMF 814 Adapter Implementation Reference rvii

Chapter 3 emsSessionFactory Module

Chapter 4 emsSession Module

Chapter 5 multiLayerSubnetwork Module

Chapter 6 managedElement Module

Chapter 7 equipment Module

Chapter 8 terminationPoint Module

Chapter 9 topologicalLink Module

viii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Chapter 10 subnetworkConnection Module

Chapter 11 protection Module

Chapter 12 trafficDescriptor Module

Chapter 13 transmissionParameters Module

Chapter 14 guiCutThrough Module

Chapter 15 maintenanceOps Module

Chapter 16 mtnmVersion Module

Navis EMS-CBGX TMF 814 Adapter Implementation Reference ix

Chapter 18 performance Module

Chapter 19 session Module

Chapter 20 globaldefs Module

Chapter 21 notifications Module

Chapter 22 common Module

Chapter 23 TMF 814A Object NamingAttributes for Provisioning Server

x6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Chapter 25 Iterators for Provisioning Server TMF 814A Implementation

Chapter 26 Troubleshooting Navis EMS-CBGX TMF 814A Implementation

Appendix A Mapping TMF 814 Layer Rates with Provisioning Server

Appendix B Supported Layer Rates in Navis EMS-CBGX TMF 814 Adapter

Navis EMS-CBGX TMF 814 Adapter Implementation Reference xi

xii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xiii

Table 6-2. getAllActiveAlarms.........................................................................6-3

xiv6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

Table 12-6. getAssociatedCTPs ........................................................................12-4

Navis EMS-CBGX TMF 814 Adapter Implementation Reference 6/21/04xv

Table 24-9. equipment Holder - Provisioning Server Object Mapping ............24-9

xvi6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

About This Guide

What You Need to Know

To develop a NMS — an application that runs on a workstation in a Lucent network,

Navis EMS-CBGX TMF 814 Adapter Implementation Reference xvii

What’s New in This Guide

Feature or Enhancement Description

New Features in This Release

xviii6/21/04 Navis EMS-CBGX TMF 814 Adapter Implementation Reference

About the Provisioning Server Document Set