alcate 5620 cmip oss interface module release 7.1 technical reference

Alcatel 5620CMIP OSS INTERFACE MODULE | RELEASE 7.1T E C H N I C A L R E F E R E N C E

PRINTED ONRECYCLED PAPER

Alcatel assumes no responsibility for the accuracy of the information presented, which is subject to change without notice.

Alcatel, the Alcatel logo, MainStreet, and Newbridge are registered trademarks of Alcatel. All other trademarks are the property of their respective owners.

Copyright 2006 Alcatel.All rights reserved.

Disclaimers

Alcatel products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, licence or other distribution of the products for any such application without the prior written consent of Alcatel, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel products. Please note that this information is provided as a courtesy to assist you. While Alcatel tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel product and contact the supplier for confirmation. Alcatel assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel products.

However, this does not constitute a representation or warranty. The warranties provided for Alcatel products, if any, are set forth in contractual documentation entered into by Alcatel and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

iii

Alcatel License Agreement

SAMPLE END USER LICENSE AGREEMENT

1. LICENSE1.1 Subject to the terms and conditions of this Agreement, Alcatel grants to

Customer and Customer accepts a non-exclusive, non-transferable license to use any software and related documentation provided by Alcatel pursuant to this Agreement ("Licensed Program") for Customer's own internal use, solely in conjunction with hardware supplied or approved by Alcatel. In case of equipment failure, Customer may use the Licensed Program on a back-up system, but only for such limited time as is required to rectify the failure.

1.2 Customer acknowledges that Alcatel may have encoded within the Licensed Program optional functionality and capacity (including, but not limited to, the number of equivalent nodes, delegate work stations, paths and partitions), which may be increased upon the purchase of the applicable license extensions.

1.3 Use of the Licensed Program may be subject to the issuance of an application key, which shall be conveyed to the Customer in the form of a Supplement to this End User License Agreement. The purchase of a license extension may require the issuance of a new application key.

2. PROTECTION AND SECURITY OF LICENSED PROGRAMS2.1 Customer acknowledges and agrees that the Licensed Program contains

proprietary and confidential information of Alcatel and its third party suppliers, and agrees to keep such information confidential. Customer shall not disclose the Licensed Program except to its employees having a need to know, and only after they have been advised of its confidential and proprietary nature and have agreed to protect same.

2.2 All rights, title and interest in and to the Licensed Program, other than those expressly granted to Customer herein, shall remain vested in Alcatel or its third party suppliers. Customer shall not, and shall prevent others from copying, translating, modifying, creating derivative works, reverse engineering, decompiling, encumbering or otherwise using the Licensed Program except as specifically authorized under this Agreement. Notwithstanding the foregoing, Customer is authorized to make one copy for its archival purposes only. All appropriate copyright and other proprietary notices and legends shall be placed on all Licensed Programs supplied by Alcatel, and Customer shall maintain and reproduce such notices on any full or partial copies made by it.

3. TERM3.1 This Agreement shall become effective for each Licensed Program upon

delivery of the Licensed Program to Customer.

iv

3.2 Alcatel may terminate this Agreement: (a) upon notice to Customer if any amount payable to Alcatel is not paid within thirty (30) days of the date on which payment is due; (b) if Customer becomes bankrupt, makes an assignment for the benefit of its creditors, or if its assets vest or become subject to the rights of any trustee, receiver or other administrator; (c) if bankruptcy, reorganization or insolvency proceedings are instituted against Customer and not dismissed within 15 days; or (d) if Customer breaches a material provision of this Agreement and such breach is not rectified within 15 days of receipt of notice of the breach from Alcatel.

3.3 Upon termination of this Agreement, Customer shall return or destroy all copies of the Licensed Program. All obligations of Customer arising prior to termination, and those obligations relating to confidentiality and non-use, shall survive termination.

4. CHARGES4.1 Upon shipment of the Licensed Program, Alcatel will invoice Customer for all

fees, and any taxes, duties and other charges. Customer will be invoiced for any license extensions upon delivery of the new software application key or, if a new application key is not required, upon delivery of the extension. All amounts shall be due and payable within thirty (30) days of receipt of invoice, and interest will be charged on any overdue amounts at the rate of 1 1/2% per month (19.6% per annum).

5. SUPPORT AND UPGRADES5.1 Customer shall receive software support and upgrades for the Licensed Program

only to the extent provided for in the applicable Alcatel software support policy in effect from time to time, and upon payment of any applicable fees. Unless expressly excluded, this Agreement shall be deemed to apply to all updates, upgrades, revisions, enhancements and other software which may be supplied by Alcatel to Customer from time to time.

6. WARRANTIES AND INDEMNIFICATION6.1 Alcatel warrants that the Licensed Program as originally delivered to Customer

will function substantially in accordance with the functional description set out in the associated user documentation for a period of 90 days from the date of shipment, when used in accordance with the user documentation. Alcatel's sole liability and Customer's sole remedy for a breach of this warranty shall be Alcatel's good faith efforts to rectify the nonconformity or, if after repeated efforts Alcatel is unable to rectify the non-conformity, Alcatel shall accept return of the Licensed Program and shall refund to Customer all amounts paid in respect thereof. This warranty is available only once in respect of each Licensed Program, and is not renewed by the payment of an extension charge or upgrade fee.

v

6.2 ALCATEL EXPRESSLY DISCLAIMS ALL OTHER WARRANTIES, REPRESENTATIONS, COVENANTS OR CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OR REPRESENTATIONS OF WORKMANSHIP, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, DURABILITY, OR THAT THE OPERATION OF THE LICENSED PROGRAM WILL BE ERROR FREE OR THAT THE LICENSED PROGRAMS WILL NOT INFRINGE UPON ANY THIRD PARTY RIGHTS.

6.3 Alcatel shall defend and indemnify Customer in any action to the extent that it is based on a claim that the Licensed Program furnished by Alcatel infringes any patent, copyright, trade secret or other intellectual property right, provided that Customer notifies Alcatel within ten (10) days of the existence of the claim, gives Alcatel sole control of the litigation or settlement of the claim, and provides all such assistance as Alcatel may reasonably require. Notwithstanding the foregoing, Alcatel shall have no liability if the claim results from any modification or unauthorized use of the Licensed Program by Customer, and Customer shall defend and indemnify Alcatel against any such claim.

6.4 Alcatel Products are intended for standard commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The Customer hereby agrees that the use, sale, licence or other distribution of the Products for any such application without the prior written consent of Alcatel, shall be at the Customer's sole risk. The Customer also agrees to defend and hold Alcatel harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the Products in such applications.

7. LIMITATION OF LIABILITY7.1 IN NO EVENT SHALL THE TOTAL COLLECTIVE LIABILITY OF

ALCATEL, ITS EMPLOYEES, DIRECTORS, OFFICERS OR AGENTS FOR ANY CLAIM, REGARDLESS OF VALUE OR NATURE, EXCEED THE AMOUNT PAID UNDER THIS AGREEMENT FOR THE LICENSED PROGRAM THAT IS THE SUBJECT MATTER OF THE CLAIM. IN NO EVENT SHALL THE TOTAL COLLECTIVE LIABILITY OF ALCATEL, ITS EMPLOYEES, DIRECTORS, OFFICERS OR AGENTS FOR ALL CLAIMS EXCEED THE TOTAL AMOUNT PAID BY CUSTOMER TO ALCATEL HEREUNDER. NO PARTY SHALL BE LIABLE FOR ANY INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES, WHETHER OR NOT SUCH DAMAGES ARE FORESEEABLE, AND/OR THE PARTY HAD BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7.2 The foregoing provision limiting the liability of Alcatel's employees, agents, officers and directors shall be deemed to be a trust provision, and shall be enforceable by such employees, agents, officers and directors as trust beneficiaries.

vi

8. GENERAL8.1 Under no circumstances shall either party be liable to the other for any failure to

perform its obligations (other than the payment of any monies owing) where such failure results from causes beyond that party's reasonable control.

8.2 This Agreement constitutes the entire agreement between Alcatel and Customer and supersedes all prior oral and written communications. All amendments shall be in writing and signed by authorized representatives of both parties.

8.3 If any provision of this Agreement is held to be invalid, illegal or unenforceable, it shall be severed and the remaining provisions shall continue in full force and effect.

8.4 The Licensed Program may contain freeware or shareware obtained by Alcatel from a third party source. No license fee has been paid by Alcatel for the inclusion of any such freeware or shareware, and no license fee is charged to Customer for its use. The Customer agrees to be bound by any license agreement for such freeware or shareware. CUSTOMER ACKNOWLEDGES AND AGREES THAT THE THIRD PARTY SOURCE PROVIDES NO WARRANTIES AND SHALL HAVE NO LIABILITY WHATSOEVER IN RESPECT OF CUSTOMER'S POSSESSION AND/OR USE OF THE FREEWARE OR SHAREWARE.

8.5 Alcatel shall have the right, at its own expense and upon reasonable written notice to Customer, to periodically inspect Customer's premises and such documents as it may reasonably require, for the exclusive purpose of verifying Customer's compliance with its obligations under this Agreement.

8.6 All notices shall be sent to the parties at the addresses listed above, or to any such address as may be specified from time to time. Notices shall be deemed to have been received five days after deposit with a post office when sent by registered or certified mail, postage prepaid and receipt requested.

8.7 If the Licensed Program is being acquired by or on behalf of any unit or agency of the United States Government, the following provision shall apply: If the Licensed Program is supplied to the Department of Defense, it shall be classified as "Commercial Computer Software" and the United States Government is acquiring only "restricted rights" in the Licensed Program as defined in DFARS 227-7202-1(a) and 227.7202-3(a), or equivalent. If the Licensed Program is supplied to any other unit or agency of the United States Government, rights will be defined in Clause 52.227-19 or 52.227-14 of the FAR, or if acquired by NASA, Clause 18-52.227-86(d) of the NASA Supplement to the FAR, or equivalent. If the software was acquired under a contract subject to the October 1988 Rights in Technical Data and Computer Software regulations, use, duplication and disclosure by the Government is subject to the restrictions set forth in DFARS 252-227.7013(c)(1)(ii) 1988, or equivalent.

8.8 Customer shall comply with all export regulations pertaining to the Licensed Program in effect from time to time. Without limiting the generality of the foregoing, Customer expressly warrants that it will not directly or indirectly export, re-export, or transship the Licensed Program in violation of any export laws, rules or regulations of Canada, the United States or the United Kingdom.

vii

8.9 No term or provision of this Agreement shall be deemed waived and no breach excused unless such waiver or consent is in writing and signed by the party claimed to have waived or consented. The waiver by either party of any right hereunder, or of the failure to perform or of a breach by the other party, shall not be deemed to be a waiver of any other right hereunder or of any other breach or failure by such other party, whether of a similar nature or otherwise.

8.10This Agreement shall be governed by and construed in accordance with the laws of the Province of Ontario. The application of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded.

viii Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 ixOctober 2006 95-6040-01-00-C

Preface

The 5620 CMIP OSS Interface Module Technical Reference describes how to use the 5620 CMIP with the matching release of the 5620 Network Manager.

The 5620 CMIP conforms to the NMF 038 BME and uses CMIP commands and messages. Some extensions have been made to BME managed objects and these are also described in this technical reference.

Prerequisites and related documentation

This document assumes you are familiar with:

• the 5620 NM• the node types and equipment in your network• CMIS• CMIP • UNIX commands

This document refers you to the following documentation:

• 5620 CMIP OSS Interface Module Installation and Upgrade Guide• 5620 Network Manager User Guide• 5620 Network Manager Installation and Upgrade Guide• Statistics Collector guides• 5620 NM ATM Configuration Reference guide• 5620 NM Advanced Configuration Procedures guide

Contact your technical support representative for information about obtaining any customer documentation.

Preface

x Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Conventions

Table 1 lists the documentation conventions used in this documentation set.

Table 1 Documentation conventions

Special informationThe following are examples of how special information is presented in this document.

Convention Description Examples

Italics Identifies a variable. hostname

— An em dash in a table cell indicates that there is no information or that the category is not applicable.

—

* An asterisk is a wildcard character that means “any character” in a search argument.

Path_analysis.*file

System-supplied text

When screen text is presented, the system-supplied text is in plain Courier.

systemname=sample_system

Commands or text that you must enter

When you are required to enter text, as in a command, the exact key sequence is displayed in bold Courier.

su - root ↵

Text that you must substitute when entering

When what you type depends on your application or purpose, the variable information is displayed in italicized bold text.

cd installdir ↵

Enter or return An arrow (↵) indicates that you press the Enter or Return key. su - root ↵

Danger — The described activity or situation may pose a threat to personal safety.

Warning — The described activity or situation may or will cause equipment damage.

Caution — The described activity or situation may or will cause service interruption.

Note — A note provides important information.

Preface

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xiOctober 2006 95-6040-01-00-C

Procedures with options or substepsWhen there are options in a procedure, they are identified by letters. When there are substeps in a procedure, they are identified by roman numerals.

Procedure 1 Example of options in a procedure

At step 1 you can choose option a or b. At step 2, you must do what the step indicates.

1 This step offers two options. You must choose one of the following:

a This is one option.

b This is another option.

2 You must perform this step.

Procedure 2 Example of substeps in a procedure

At step 1, you must perform a series of substeps within a step. At step 2, you must do what the step indicates.

1 This step has a series of substeps that you must perform to complete the step. You must perform the following substeps:

i This is the first substep.

ii This is the second substep.

iii This is the third substep.

2 You must perform this step.

Measurement conventionsMeasurements in this document are expressed in metric units and follow the Système international d’unités (SI) standard for abbreviation of metric units. If imperial measurements are included, they appear in brackets following the metric unit. Table 2 lists the measurement conventions used in this document but not covered by SI.

Table 2 Bits and bytes conventions

Measurement Symbol

bit b

byte byte

(1 of 2)

Preface

xii Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

dB/m decibels per meter

RU rack unit 1.75 in.

Measurement Symbol

(2 of 2)

Contents

Preface ixPrerequisites and related documentation .............................................................................. ixConventions............................................................................................................................x

Special information ............................................................................................xProcedures with options or substeps ................................................................xiProcedure 1 Example of options in a procedure..............................................xiProcedure 2 Example of substeps in a procedure ...........................................xiMeasurement conventions................................................................................xi

Getting started

1 — 5620 CMIP new and existing features 1-11.1 What’s new or modified for Release 7.1 H3 ...................................................... 1-21.2 What’s new or modified for Release 7.1 H2 ...................................................... 1-41.3 What’s new for Release 7.1 H0 and H1............................................................. 1-81.4 What’s new for previous releases...................................................................... 1-8

Feature list for Release 7.0............................................................................ 1-8Feature list for Release 6.3............................................................................ 1-9Feature list for Release 6.2.......................................................................... 1-10Feature list for Release 6.1.......................................................................... 1-11Feature list for Release 5.3.......................................................................... 1-12Feature list for Release 5.2.......................................................................... 1-13Feature list for Release 5.1.......................................................................... 1-13Feature list for Release 5.0.......................................................................... 1-14Feature list for Release 4.1.......................................................................... 1-14Feature list for Release 4.0.......................................................................... 1-15

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xiiiOctober 2006 95-6040-01-00-C

Contents

2 — Introduction to the 5620 CMIP 2-12.1 5620 CMIP......................................................................................................... 2-22.2 Functional description........................................................................................ 2-2

Gateway Station............................................................................................. 2-3OSS Interface Agent ...................................................................................... 2-4

2.3 Standards conformance..................................................................................... 2-5Architecture layer standards .......................................................................... 2-5Profiles layer standards ................................................................................. 2-5Applications layer standards .......................................................................... 2-6Presentation layer standards ......................................................................... 2-6Session layer standards................................................................................. 2-6Transport layer standards .............................................................................. 2-7Network layer standards ................................................................................ 2-7Link layer standards....................................................................................... 2-7

2.4 5620 CMIP Release 6.3 platform requirements................................................. 2-7Gateway Station hardware............................................................................. 2-7Gateway Station software .............................................................................. 2-7The 5620 NM NetworkStation........................................................................ 2-8Application Key .............................................................................................. 2-8

3 — System configurations 3-13.1 Small systems.................................................................................................... 3-23.2 Basic configuration ............................................................................................ 3-23.3 Multiple OSS access.......................................................................................... 3-3

Procedure 3-1 To increase the number of connected OSSs allowed ........... 3-43.4 Multiple partitions............................................................................................... 3-5

Partitioning with two OSSs............................................................................. 3-5Partitioning with one OSS.............................................................................. 3-6

3.5 5620 CMIP redundancy ..................................................................................... 3-73.6 5620 NM redundancy ........................................................................................ 3-9

4 — Monitoring 5620 CMIP processes 4-14.1 Configuring ELS options .................................................................................... 4-2

Viewing and using the logtool ........................................................................ 4-3Procedure 4-1 To set ELS environment variables ........................................ 4-4Format of the process ELS messages........................................................... 4-4

5 — Starting and stopping the 5620 CMIP 5-15.1 The Gateway Station ......................................................................................... 5-2

5620 CMIP OSS Interface Gateway processes............................................. 5-2Automatic startup of the 5620 CMIP.............................................................. 5-2

5.2 Manually controlling the 5620 CMIP .................................................................. 5-3CE_control process options ........................................................................... 5-3Procedure 5-1 Starting the 5620 CMIP......................................................... 5-4Procedure 5-2 To check the 5620 CMIP status ............................................ 5-4Procedure 5-3 Stopping the 5620 CMIP....................................................... 5-5Procedure 5-4 Stopping the CE_driver and CE_mibmgr processes............. 5-6Procedure 5-5 Starting the CE_driver and CE_mibmgr processes .............. 5-6

xiv Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

Procedure 5-6 Stopping the 5620 CMIP database server ............................ 5-6Procedure 5-7 Starting the 5620 CMIP database server .............................. 5-7

6 — Configuring the CE_driver process 6-16.1 CE_driver process options................................................................................. 6-2

netconfig.CE process file ............................................................................... 6-2CE_driver process entry fields ....................................................................... 6-2Configuring the CE_driver process ................................................................ 6-3Procedure 6-1 To configure CE_driver options............................................. 6-4

7 — Communication 7-17.1 Introduction ........................................................................................................ 7-27.2 Network element communication....................................................................... 7-27.3 Communication between the 5620 CMIP OSS Interface Gateway and

the 5620 NM ............................................................................................. 7-3Partition name and network identification ...................................................... 7-3OSS Interface Agent processes on the 5620 NM NetworkStation................. 7-3

7.4 Communication with the OSS............................................................................ 7-4OSI presentation address .............................................................................. 7-4Association management............................................................................... 7-4

8 — Configuring the 5620 CMIP on the NetworkStation 8-18.1 Communication status ....................................................................................... 8-2

Icon colors...................................................................................................... 8-28.2 Configuring the 5620 CMIP OSS Interface Gateway node................................ 8-28.3 Configuring OSS Interface Agent processes on the NetworkStation................. 8-3

Procedure 8-1 To reconfigure OSS Interface Agent processes.................... 8-4

System administration

9 — MIB management 9-19.1 The 5620 CMIP MIB .......................................................................................... 9-2

Database synchronization.............................................................................. 9-29.2 Deleting and reloading the MIB ......................................................................... 9-29.3 Backing up the MIB............................................................................................ 9-2

Procedure 9-1 To back up the MIB ............................................................... 9-3Procedure 9-2 To export the MIB.................................................................. 9-3

9.4 Restoring the MIB .............................................................................................. 9-4Procedure 9-3 To restore the MIB ................................................................ 9-4Procedure 9-4 To import the MIB.................................................................. 9-5

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xvOctober 2006 95-6040-01-00-C

Contents

10 — CE MIB tool 10-110.1 CE MIB tool...................................................................................................... 10-2

The MIB audit command.............................................................................. 10-2The MIB sync command .............................................................................. 10-3The MIB reload command............................................................................ 10-3The MIB delete command............................................................................ 10-3The MIB size command ............................................................................... 10-4The MIB count command............................................................................. 10-4The MIB status command ............................................................................ 10-4The MIB export command............................................................................ 10-4The MIB import command............................................................................ 10-4The MIB backup command .......................................................................... 10-4The MIB restore command .......................................................................... 10-4

10.2 Running CE MIB tool commands..................................................................... 10-4Procedure 10-1 Manually running a MIB audit, a MIB sync, or a MIB

syncstatus ............................................................................................ 10-5Procedure 10-2 Manually running a MIB reload ......................................... 10-7Procedure 10-3 Manually running a MIB delete.......................................... 10-7Procedure 10-4 To determine the size of the MIB ...................................... 10-8Procedure 10-5 To report on the number of objects in the MIB.................. 10-8Procedure 10-6 To report on the status of the 5620 CMIP database

server ................................................................................................... 10-8

11 — The 5620 CMIP security module 11-111.1 Security file ...................................................................................................... 11-2

Maintaining the security file.......................................................................... 11-2Adding entries to the security file dynamically ............................................. 11-4

11.2 OSS access privilege verification .................................................................... 11-5Screening OSS requests ............................................................................. 11-5Restricting access during critical processing ............................................... 11-5

11.3 Security module commands ............................................................................ 11-5Procedure 11-1 Sample security module subcommand ............................. 11-6

Operations overview

12 — Network object modeling 12-112.1 Modeling overview ........................................................................................... 12-212.2 Network managed objects ............................................................................... 12-2

bMFacility object .......................................................................................... 12-2managedFacilityTP object............................................................................ 12-3bMGroomedCircuit object ............................................................................ 12-3managedGroomedCircuitTP object.............................................................. 12-3managedElement object .............................................................................. 12-4elementExtentions object............................................................................. 12-4equipmentHolder object ............................................................................... 12-4managedPack object ................................................................................... 12-4

xvi Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

managedEquipment object .......................................................................... 12-4managedProfile object ................................................................................. 12-4network object.............................................................................................. 12-4

12.3 Object modeling examples .............................................................................. 12-5

13 — Path management 13-113.1 Overview.......................................................................................................... 13-2

Path-ends..................................................................................................... 13-213.2 Path states....................................................................................................... 13-213.3 Creating paths ................................................................................................. 13-4

Automatic path-end assignment .................................................................. 13-6Unique naming for paths and logical links ................................................... 13-6

13.4 SPVC-interworking paths................................................................................. 13-7Configuration methods................................................................................. 13-7Endpoint modeling ....................................................................................... 13-7Creating SPVC-interworking paths .............................................................. 13-7

13.5 Creating resource links .................................................................................... 13-813.6 Connecting paths............................................................................................. 13-9

Connecting paths using the M-CREATE operation...................................... 13-9Connecting paths using the M-SET operation ............................................. 13-9Connect successful.................................................................................... 13-10Connect failed ............................................................................................ 13-10

13.7 Disconnecting paths ...................................................................................... 13-1113.8 Configuring bMGroomedCircuit object attributes........................................... 13-1113.9 Deleting paths................................................................................................ 13-1113.10 Path maintenance.......................................................................................... 13-12

Path tracing................................................................................................ 13-12Path grooming............................................................................................ 13-12Hitless connection moves .......................................................................... 13-12

13.11 Path recovery................................................................................................. 13-13Fault in connection..................................................................................... 13-13Reroute ...................................................................................................... 13-13Timing outages .......................................................................................... 13-13

14 — Link management 14-114.1 Link management overview ............................................................................. 14-214.2 Physical links ................................................................................................... 14-214.3 Logical links ..................................................................................................... 14-2

Frame relay links.......................................................................................... 14-2MFR links ..................................................................................................... 14-3ATM links ..................................................................................................... 14-4IMA links ...................................................................................................... 14-5PSN links ..................................................................................................... 14-5

14.4 Resource links ................................................................................................. 14-6PNNI links .................................................................................................... 14-6ILMI links...................................................................................................... 14-7Signaling links .............................................................................................. 14-7Creating a resource link using the 5620 CMIP ............................................ 14-8

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xviiOctober 2006 95-6040-01-00-C

Contents

15 — Alcatel 7390 NT management 15-115.1 About 7390 NT management........................................................................... 15-215.2 7390 NT commissioning .................................................................................. 15-2

Message interaction sequence for NT commissioning ................................ 15-215.3 7390 NT replacement ...................................................................................... 15-5

Message interaction sequence for NT replacement .................................... 15-515.4 7390 NT decommissioning .............................................................................. 15-7

Message interaction sequence for NT decommissioning ............................ 15-8

16 — Maintenance and diagnostics 16-116.1 Testing overview.............................................................................................. 16-2

The busyOutTestObject ............................................................................... 16-2The loopBackTestObject.............................................................................. 16-3The oAMCellTestObject............................................................................... 16-3The splitMonitorTestObject .......................................................................... 16-3The testAccessConnectionObject................................................................ 16-3The traceTestObject .................................................................................... 16-4The genericActionObject.............................................................................. 16-4

16.2 The testActionPerformer object ....................................................................... 16-4Initiating and terminating a test request ....................................................... 16-4

16.3 Administering a test on the busyOutTestObject .............................................. 16-6busyOutTestObject test information............................................................. 16-6Performing a test on the busyOutTestObject............................................... 16-6

16.4 Administering a test on the loopBackTestObject ............................................. 16-7loopBackTestObject test information ........................................................... 16-7Performing a test on the loopBackTestObject ............................................. 16-7

16.5 Administering a test on the oAMCellTestObject .............................................. 16-8OAM cell loopback test information ............................................................. 16-8Performing a test on the oAMCellTestObject............................................. 16-12

16.6 Administering a test on the splitMonitorTestObject ....................................... 16-13splitMonitorTestObject test information...................................................... 16-13Performing a test on the splitMonitorTestObject........................................ 16-15

16.7 Administering a test on the testAccessConnectionObject ............................. 16-16testAccessConnectionObject test information ........................................... 16-16Performing a test on the testAccessConnectionObject.............................. 16-18

16.8 Administering a test on the traceTestObject.................................................. 16-19traceTestObject test information ................................................................ 16-19Performing a test on the traceTestObject .................................................. 16-22

16.9 Off-node testing ............................................................................................. 16-22

17 — Event and alarm management 17-117.1 Event management overview .......................................................................... 17-217.2 Event and alarm logging and forwarding ......................................................... 17-2

log object...................................................................................................... 17-2eventForwardingDiscriminator object........................................................... 17-3discriminatorConstruct attribute ................................................................... 17-3Time stamping ............................................................................................. 17-3

xviii Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

17.3 Event and alarm notifications........................................................................... 17-3eventReportArgument.................................................................................. 17-3Event notifications........................................................................................ 17-7Alarm notifications........................................................................................ 17-8

17.4 Event and alarm sources ................................................................................. 17-9Event sources .............................................................................................. 17-9Alarm sources .............................................................................................. 17-9Procedure 17-1 To enable 5620 NM fault management processes ......... 17-10ALMAP AS-IM component ......................................................................... 17-11

17.5 Event and alarm log record objects ............................................................... 17-1117.6 Port alarm suppression.................................................................................. 17-11

18 — Statistics activation and control 18-118.1 Statistics Collector configurations.................................................................... 18-218.2 Statistics collection and the 5620 CMIP .......................................................... 18-2

Configuration requirements.......................................................................... 18-2Statistics Collector and 5620 CMIP interactions .......................................... 18-2

18.3 Activating statistics using the 5620 CMIP........................................................ 18-318.4 Interpreting statistics reports............................................................................ 18-3

Statistics output format (since Release 4.0) ................................................ 18-3Statistics output format (before Release 4.0)............................................... 18-4Mapping between statistics data files and the 5620 CMIP .......................... 18-4

18.5 Collecting real-time statistics ........................................................................... 18-5configureRealTimeStatistics ........................................................................ 18-6collectRealTimeStatistics ............................................................................. 18-6cancelRealTimeStatistics............................................................................. 18-7determineRealTimeStatistics ....................................................................... 18-7Real-time statistics data message format .................................................... 18-7

19 — Interaction sequences 19-119.1 Introduction ...................................................................................................... 19-219.2 Get ................................................................................................................... 19-2

Simple get .................................................................................................... 19-2Scoped M-GET ............................................................................................ 19-5

19.3 Set ................................................................................................................... 19-9Simple M-SET.............................................................................................. 19-9M-SET bMGroomedCircuit AdminState (PathConnect)............................. 19-12

19.4 Event report ................................................................................................... 19-18Simple event report.................................................................................... 19-18M-EVENT-REPORT (node offline)............................................................. 19-19M-EVENT-REPORT (physical link support path fails) ............................... 19-22

19.5 Create ............................................................................................................ 19-29Create DS0 ................................................................................................ 19-29Create path ................................................................................................ 19-37

19.6 Delete ............................................................................................................ 19-52Delete DS0................................................................................................. 19-52

19.7 Action............................................................................................................. 19-57Loopback action......................................................................................... 19-57

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xixOctober 2006 95-6040-01-00-C

Contents

Managed objects

20 — Managed object hierarchy 20-120.1 Introduction to the 5620 CMIP managed objects............................................. 20-2

GDMO and ASN.1 ....................................................................................... 20-420.2 Object class sources........................................................................................ 20-420.3 MIB containment structure............................................................................... 20-6

System branch ............................................................................................. 20-7Network branch............................................................................................ 20-7

20.4 Network modeling examples.......................................................................... 20-10TDM network objects ................................................................................. 20-10Frame relay network .................................................................................. 20-13ATM network.............................................................................................. 20-147390 LMDS wireless network .................................................................... 20-17

Managed objects A to Z

21 — alarmRecord object 21-121.1 Introduction ...................................................................................................... 21-221.2 Supported CMIP operations ............................................................................ 21-221.3 Attributes.......................................................................................................... 21-2

22 — attributeValueChangeRecord object 22-122.1 Introduction ...................................................................................................... 22-222.2 Supported CMIP operations ............................................................................ 22-222.3 Attributes.......................................................................................................... 22-2

23 — bMFacility object 23-123.1 Introduction ...................................................................................................... 23-223.2 Supported CMIP operations ............................................................................ 23-223.3 Event notifications............................................................................................ 23-223.4 Attributes.......................................................................................................... 23-223.5 serverTrailList .................................................................................................. 23-523.6 trmCircuitProfile attribute ................................................................................. 23-6

Common trmCircuitProfile attribute circuitProfile characteristics ................. 23-6trmCircuitProfile attribute circuitProfile characteristics for frame relay

links ...................................................................................................... 23-7trmCircuitProfile attribute characteristics for MFR links ............................. 23-13trmCircuitProfile attribute circuitProfileName characteristics for ATM

VPC links............................................................................................ 23-14trmCircuitProfile attribute circuitProfileName characteristics for

custom attributes................................................................................ 23-21trmCircuitProfile attribute circuitProfile characteristics for TDM/ATM

VCC links ........................................................................................... 23-23

xx Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

trmCircuitProfile attribute circuitProfile characteristics for IMA links .......... 23-26trmCircuitProfile attribute circuitProfile characteristics for full and

fractional links .................................................................................... 23-27trmCircuitProfile attribute circuitProfile characteristics for PSN links ......... 23-29trmCircuitProfile attribute circuitProfile characteristics for subrate links .... 23-30

23.7 currentProblemList attribute........................................................................... 23-35

24 — bMGroomedCircuit object 24-124.1 Introduction ...................................................................................................... 24-224.2 Supported CMIP operations ............................................................................ 24-224.3 Event notifications............................................................................................ 24-224.4 Attributes.......................................................................................................... 24-224.5 administrativeState and operationalState attributes ........................................ 24-524.6 currentProblemList attribute............................................................................. 24-524.7 bMGroomedCircuit object profile attributes ..................................................... 24-924.8 tDMProfile attribute ........................................................................................ 24-1024.9 frameRelayProfile attribute ............................................................................ 24-2124.10 aTMProfile attribute ....................................................................................... 24-27

Setting the PIR on ATM VCC paths with a CE endpoint............................ 24-4124.11 commonProfile attribute................................................................................. 24-4324.12 circuitType attribute ....................................................................................... 24-49

25 — busyOutTestObject 25-125.1 Introduction ...................................................................................................... 25-225.2 Supported CMIP operations ............................................................................ 25-225.3 Event notifications............................................................................................ 25-225.4 Attributes.......................................................................................................... 25-2

26 — elementExtensions object 26-126.1 Introduction ...................................................................................................... 26-226.2 Supported CMIP operations ............................................................................ 26-226.3 Event notifications............................................................................................ 26-226.4 Attributes.......................................................................................................... 26-226.5 elementProfile attribute.................................................................................... 26-326.6 ntCommissioning attribute ............................................................................... 26-526.7 pnniProfile attribute.......................................................................................... 26-526.8 pnniSummaryAddressProfile attribute ............................................................. 26-7

27 — equipmentHolder object 27-127.1 Introduction ...................................................................................................... 27-227.2 Supported CMIP operations ............................................................................ 27-227.3 Event notifications............................................................................................ 27-227.4 Attributes.......................................................................................................... 27-227.5 Programmed versus installed card type .......................................................... 27-3

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xxiOctober 2006 95-6040-01-00-C

Contents

28 — eventForwardingDiscriminator object 28-128.1 Introduction ...................................................................................................... 28-228.2 Supported CMIP operations ............................................................................ 28-228.3 Event notifications............................................................................................ 28-228.4 Attributes.......................................................................................................... 28-2

29 — genericActionObject 29-129.1 Introduction ...................................................................................................... 29-329.2 Supported CMIP actions.................................................................................. 29-429.3 Event notifications............................................................................................ 29-529.4 Attributes.......................................................................................................... 29-529.5 listLinks action ................................................................................................. 29-629.6 listPaths action............................................................................................... 29-12

listPaths action results ............................................................................... 29-1729.7 hitlessConnectionMove action ....................................................................... 29-18

hitlessConnectionMove result messages for cpType 8.............................. 29-2029.8 retrieveActiveAlarms action ........................................................................... 29-2129.9 configureRealTimeStatistics action................................................................ 29-21

configureRealTimeStatistics action results ................................................ 29-2229.10 collectRealTimeStatistics action .................................................................... 29-22

collectRealTimeStatistics action results..................................................... 29-2329.11 cancelRealTimeStatistics action .................................................................... 29-23

cancelRealTimeStatistics action results..................................................... 29-2329.12 determineSupportedStatistics action ............................................................. 29-23

determineSupportedStatistics action results.............................................. 29-2429.13 addChannelsToMux action ............................................................................ 29-2429.14 removeChannelsFromMux action.................................................................. 29-2629.15 listChannelsUsedByMux action ..................................................................... 29-26

listChannelsUsedByMux action results...................................................... 29-2629.16 listCustomAttributeNames action................................................................... 29-26

listCustomAttributeNames action results ................................................... 29-2729.17 retrieveISLInfo action..................................................................................... 29-27

retrieveISLInfo action results ..................................................................... 29-28

30 — log object 30-130.1 Introduction ...................................................................................................... 30-230.2 log object information....................................................................................... 30-230.3 Supported CMIP operations ............................................................................ 30-230.4 Event notifications............................................................................................ 30-330.5 Attributes.......................................................................................................... 30-3

31 — loopBackTestObject 31-131.1 Introduction ...................................................................................................... 31-231.2 Supported CMIP operations ............................................................................ 31-231.3 Event notifications............................................................................................ 31-231.4 Attributes.......................................................................................................... 31-2

xxii Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

32 — managedElement object 32-132.1 Introduction ...................................................................................................... 32-232.2 Supported CMIP operations ............................................................................ 32-232.3 Event notifications............................................................................................ 32-232.4 Attributes.......................................................................................................... 32-2

33 — managedEquipment object 33-133.1 Introduction ...................................................................................................... 33-233.2 Supported CMIP operations ............................................................................ 33-233.3 Event notifications............................................................................................ 33-233.4 Attributes.......................................................................................................... 33-2

34 — managedFacilityTP object 34-134.1 Introduction ...................................................................................................... 34-234.2 Supported 5620 CMIP operations ................................................................... 34-234.3 Event notifications............................................................................................ 34-234.4 Attributes.......................................................................................................... 34-234.5 facilityTPProfile attribute .................................................................................. 34-4

Calculating the cpValue for cpType 28 of facilityTPProfile—IMAResource Port Assignment ................................................................ 34-18

Calculating the cpValue for cpType 35 of facilityTPProfile—MFRresource ............................................................................................. 34-19

Port alarm suppression .............................................................................. 34-1934.6 trmPhysicalInterface attribute ........................................................................ 34-1934.7 cTPId attribute ............................................................................................... 34-27

35 — managedGroomedCircuitTP object 35-135.1 Introduction ...................................................................................................... 35-235.2 Supported CMIP operations ............................................................................ 35-335.3 Event notifications............................................................................................ 35-335.4 Attributes.......................................................................................................... 35-335.5 groomedCircuitTPProfile attribute.................................................................... 35-535.6 trmDataMode attribute ..................................................................................... 35-935.7 trmFunctionalInterface attribute ..................................................................... 35-1135.8 trmVoiceMode attribute.................................................................................. 35-1835.9 tTPId attribute ................................................................................................ 35-2135.10 listFreeVCIs and listUsedVCIs action ............................................................ 35-21

36 — managedPack object 36-136.1 Introduction ...................................................................................................... 36-236.2 Supported CMIP operations ............................................................................ 36-236.3 Event notifications............................................................................................ 36-236.4 Attributes.......................................................................................................... 36-236.5 packProfile attribute ......................................................................................... 36-436.6 Programmed versus installed card type ........................................................ 36-1036.7 Port and resource numbering for SDSL cards............................................... 36-11

Port and resource numbering sequences for an SDSL 16-port card ......... 36-11Port and resource numbering sequences for an SDSL 48-port card ......... 36-12

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xxiiiOctober 2006 95-6040-01-00-C

Contents

36.8 Port and resource numbering for OC3 MS and STM1 MS cards .................. 36-13Port and resource numbering for OC3 MS cards....................................... 36-13Port and resource numbering for STM1 MS cards .................................... 36-15

36.9 listFreeManagedGroomedCircuitTPs andlistUsedManagedGroomedCircuitTPs actions ...................................... 36-18

37 — managedProfile object 37-137.1 Introduction ...................................................................................................... 37-237.2 Supported CMIP operations ............................................................................ 37-237.3 Event notifications............................................................................................ 37-237.4 Attributes.......................................................................................................... 37-237.5 managedProfileID ............................................................................................ 37-3

managedProfileID for a network-level profile ............................................... 37-4managedProfileID for a node-specific profile ............................................... 37-6

37.6 managedProfileProf attribute ........................................................................... 37-8managedProfileProf attribute characteristics for network-level profiles ....... 37-8managedProfileProf attribute characteristics for node-specific profiles ..... 37-13managedProfileProf attribute characteristics for 7300 ASAM, Release

4.1, node-specific profiles .................................................................. 37-14managedProfileProf attribute characteristics for 7300 ASAM, Release

4.2 or later, node-specific profiles ...................................................... 37-17managedProfileProf attribute characteristics for 7300 ASAM, Release

4.5.10 or later, node-specific XDSL service profile ............................ 37-21managedProfileProf attribute characteristics for 7300 ASAM, Release

4.5.10 or later, node-specific XDSL spectrum profile......................... 37-22managedProfileProf attribute characteristics for 7321 RU, Release

2.1 or later, node-specific profiles ...................................................... 37-22

38 — network object 38-138.1 Introduction ...................................................................................................... 38-238.2 Supported CMIP operations ............................................................................ 38-238.3 Attributes.......................................................................................................... 38-2

39 — oAMCellTestObject 39-139.1 Introduction ...................................................................................................... 39-239.2 Supported CMIP operations ............................................................................ 39-239.3 Event notifications............................................................................................ 39-239.4 Attributes.......................................................................................................... 39-2

40 — objectCreationRecord object 40-140.1 Introduction ...................................................................................................... 40-240.2 Supported CMIP operations ............................................................................ 40-240.3 Attributes.......................................................................................................... 40-2

xxiv Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

41 — objectDeletionRecord object 41-141.1 Introduction ...................................................................................................... 41-241.2 Supported CMIP operations ............................................................................ 41-241.3 Attributes.......................................................................................................... 41-2

42 — objectGroup object 42-142.1 Introduction ...................................................................................................... 42-242.2 Supported CMIP operations ............................................................................ 42-242.3 Attributes.......................................................................................................... 42-2

43 — routerTemplate object 43-143.1 Introduction ...................................................................................................... 43-243.2 Supported CMIP operations ............................................................................ 43-243.3 Event notifications............................................................................................ 43-243.4 Attributes.......................................................................................................... 43-243.5 execute action.................................................................................................. 43-443.6 cancelExecute action....................................................................................... 43-443.7 getExecuteResponse action ............................................................................ 43-443.8 discardExecuteResponse action ..................................................................... 43-4

44 — splitMonitorTestObject 44-144.1 Introduction ...................................................................................................... 44-244.2 Supported CMIP operations ............................................................................ 44-244.3 Event notifications............................................................................................ 44-244.4 Attributes.......................................................................................................... 44-2

45 — stateChangeRecord object 45-145.1 Introduction ...................................................................................................... 45-245.2 Supported CMIP operations ............................................................................ 45-245.3 Attributes.......................................................................................................... 45-2

46 — system object 46-146.1 Introduction ...................................................................................................... 46-246.2 Supported CMIP operations ............................................................................ 46-246.3 Attributes.......................................................................................................... 46-2

47 — testAccessConnectionObject 47-147.1 Introduction ...................................................................................................... 47-247.2 Supported CMIP operations ............................................................................ 47-247.3 Event notifications............................................................................................ 47-247.4 Attributes.......................................................................................................... 47-2

48 — testActionPerformer object 48-148.1 Introduction ...................................................................................................... 48-248.2 Supported CMIP operations ............................................................................ 48-2

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xxvOctober 2006 95-6040-01-00-C

Contents

48.3 Attributes.......................................................................................................... 48-248.4 operationalState and proceduralStatus attributes............................................ 48-3

49 — traceTestObject 49-149.1 Introduction ...................................................................................................... 49-249.2 Supported CMIP operations ............................................................................ 49-249.3 Event notifications............................................................................................ 49-249.4 Attributes.......................................................................................................... 49-249.5 traceTestProfile attribute.................................................................................. 49-349.6 traceTestObject action results ......................................................................... 49-4

connectionTrace action results .................................................................... 49-4spvcConnectionTrace action results ............................................................ 49-5spvcPathTrace action results....................................................................... 49-5

Appendixes

A. Card types A-1A.1 Values for holderStatus, acceptableCircuitPackTypeList, and

circuitPackType attributes.........................................................................A-2

B. The 5620 CMIP OIDs arranged by standard B-1B.1 TMF 038 bandwidth management ensemble ....................................................B-2B.2 TMF Library 1 ....................................................................................................B-2B.3 TMF Library 4 ....................................................................................................B-3B.4 ITU-T M.3100.....................................................................................................B-4B.5 ITU-T Q.821.......................................................................................................B-8B.6 ITU-T X.721 .......................................................................................................B-9B.7 ITU-T X.745 .....................................................................................................B-13B.8 Association management extension ................................................................B-15B.9 Fault management extensions.........................................................................B-16B.10 Path management extensions .........................................................................B-19B.11 Test management extensions..........................................................................B-20

C. 5620 CMIP OIDs arranged numerically andalphabetically C-1

C.1 Numerically arranged 5620 CMIP OIDs ............................................................C-2C.2 Alphabetically-arranged 5620 CMIP OIDs.......................................................C-17

D. alarmRecord attribute values arranged by managedObjectClass D-1

D.1 Introduction ........................................................................................................D-2D.2 bMFacility object ................................................................................................D-2D.3 bMGroomedCircuit object ..................................................................................D-4

xxvi Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Contents

D.4 log object ...........................................................................................................D-6D.5 managedElement object ....................................................................................D-6D.6 managedFacilityTP object ...............................................................................D-11

managedFacilityTP object alarms for ATM circuit emulation cards .............D-15D.7 managedPack object .......................................................................................D-16

E. alarmInfo E-1E.1 additionalInformation attribute ...........................................................................E-2E.2 additionalText attribute ......................................................................................E-4E.3 monitoredAttributes............................................................................................E-5E.4 perceivedSeverity attribute ................................................................................E-5E.5 probableCause attribute ....................................................................................E-5E.6 thresholdInfo ......................................................................................................E-6E.7 specificProblems................................................................................................E-7E.8 alarmInfo formats for alarms forwarded by the 5620 NM fault

management system or by the ALMAP AS-IM component ......................E-7

Glossary

Index

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 xxviiOctober 2006 95-6040-01-00-C

Contents

xxviii Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 October 2006 95-6040-01-00-C

Getting started

1 — 5620 CMIP new and existing features

2 — Introduction to the 5620 CMIP

3 — System configurations

4 — Monitoring 5620 CMIP processes

5 — Starting and stopping the 5620 CMIP

6 — Configuring the CE_driver process

7 — Communication

8 — Configuring the 5620 CMIP on the NetworkStation

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 1-1October 2006 95-6040-01-00-C


1.1 What’s new or modified for Release 7.1 H3 1-2

1.2 What’s new or modified for Release 7.1 H2 1-4

1.3 What’s new for Release 7.1 H0 and H1 1-8

1.4 What’s new for previous releases 1-8


1-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

1.1 What’s new or modified for Release 7.1 H3

Table 1-1 describes the new features, feature changes, and documentation changes for the 5620 CMIP, Release 7.1 H3.

Table 1-1 5620 CMIP Release 7.1 H3 features, feature changes, and documentation changes

Feature Description See

New features

1540 Litespan Support for:

• 1540 Litespan, Release 2.5E node with light integration• 1540 Litespan, Release 2.5E node with tight integration• 1540 Litespan, Release 2.1E node with light integration• 1540 Litespan, Release 2.1F node with light integration• 1540 Litespan, Release 2.1F node with tight integration

Table 32-4

Support for MLTS-A, MLTS-B, MLTS-C, MLTS-D, MLTS-E, MLTS-F, MLTS-G, and MLTS-H shelves

—

Support for the following cards:

• AICC-A• ASCC-E1• BSEC-A• LTSC-A • NACC-A, NACC-B, and NACC-C• NBLC-A

Table A-1


• AANC-A and ASCC-S1• E1 ATM port in the PAIC-A• OC-3 port in AANC-A and ASCC-S1• PAIC-A

Tables 34-8 and A-1

Support for:

• LTAC-A, LTAC-B, LTAC-C, and LTAC-D cards on the 1540 Litespan 2.1F or later

• LTAC-D2 and LTAC-F cards on the 1540 Litespan, Release 2.5E or later

• LTSC-A card on the 1540 Litespan 2.1F and 2.5 E or later• SHDSL port in the LTSC-A card• XDSL ports in LT cards

Tables 35-4 and A-1

Support for:

• AICC-A and ASCC-E1 cards• ASCC-AD, ASCC-AE, ASCC-PD, and ASCC-PE cards• E1 ATM port in AICC-A and ASCC-E1 cards• E3 ATM port in the ASCC-AE and ASCC-PE cards• T3 ATM port in the ASCC-AD and ASCC-PD cards

Tables 34-8, 35-4, and A-1

7324 RU Support for the 7324 RU, Release 4.0 Table 32-4

(1 of 3)



Node subtypes Support for the following subtypes for the 7300 ASAM node:

• LVG• FENT• GENT

Support for the following subtypes for the 7302 ISAM node:

• FTTNEU• FTTNUS

Table 32-3

7300 ASAM Support for:

• 7300 ASAM, Release 4.7.20• 7300 ASAM, Release 5.1.40

—

7302 ISAM Support for:

• 7302 ISAM, Release 2.4• 7302 ISAM, Release 2.5

Table 32-4

Support for the SEMS-A shelf —


• EBLT-K and EBLT-L• ECNT-A and ECNT-C• EDSE-A• SATU-A• VSEM-A

Tables 34-8 and A-1

Support for cpType 97 (Transfer Mode) in the facilityTPProfile attribute of XDSL ports in the VSEM-A card

Table 34-2

New values for the facilityType attribute of the bMFacility object created from a lightly integrated 7302 ISAM node

Table 23-1

Feature changes

7300 ASAM, Release 4.7.10 or later


• AACU-D• AATU-C• ACDS-A• ACE1-A• ACE3-A• ADLT-Y• AEXT-A• AFLT-A• ATDS-A• D1NT-C• SHLT-C, SHLT-D, and SHLT-E• SMLT-C, SMLT-D, and SMLT-E• IMA module

Tables 34-8 and A-1

Support for the ANSI version of the ARAM-D shelf —

7300 ASAM, Release 4.7.15 or later

Support for FENT-A running FENT4 software —

7302 ISAM, Release 2.2 or later


• EALT-A• EBLT-A, EBLT-C, EBLT-D, and EBLT-J• EVLT-A, EVLT-C, and EVLT-D

Table A-1


(2 of 3)



1.2 What’s new or modified for Release 7.1 H2

Table 1-2 describes the new features, feature changes, and documentation changes for the 5620 CMIP, Release 7.1 H2.

Table 1-2 5620 CMIP Release 7.1 H2 features, feature changes, and documentation changes

7302 ISAM, Release 2.3 or later


• EBLT-E• EBLT-F

Table A-1

listPaths enhancements Enhancements to the listPaths action of the genericActionObject, including:

• modifying the description of cpType 6 of listPaths actionInfoArg

• adding cpTypes 1000 to 1004 of listPaths actionInfoArg• adding information about listPaths action results

Table 29-3

section 29.6

ISL and SRL Support for ISL and SRL, including a new retrieveISLInfo action on the genericActionObject

section 29.17

“trmCircuitProfile attribute circuitProfile characteristics for subrate links” in chapter 23

Tables 23-1, 23-2, 23-3, 23-14, 29-2, and B-39

Node short name Support for the short name of a node in the userLabel attribute of the managedElement object by the CE_agent, CE_chgsrv, and CE_reload processes

Tables 8-4, 18-2, 32-1, and 32-3

Documentation changes

connectionTrace Clarified the results of the connectionTrace action section 49.6

Modified cpValues Modified the cpValues of the cpType CIR (Source CIR) and cpType 3 (Destination CIR) circuitProfile characteristics of the frameRelayProfile attribute

Table 24-6

Corrections to Procedures 9-1, 9-2, 9-3, and 9-4

Corrected the following procedures:

• To back up the MIB• To export the MIB• To restore the MIB• To import the MIB

Procedures 9-1, 9-2, 9-3, and 9-4


(3 of 3)


New features

(1 of 4)



Custom attributes Support for 10 custom attributes as cpTypes in the trmCircuitProfile attribute of the bmFacility object

Table 23-9

Support for 10 custom attributes as cpTypes in the commonProfile attribute of the bMGroomedCircuit object

Table 24-11

Support for 10 custom attributes as cpTypes in the elementProfile attribute of the elementExtensions object

Table 26-2

Support for listing all custom attribute names, using listCustomAttributeNames, for a given managedObject through an action of the genericActionObject

section 29.16

Support for 10 custom attributes as cpTypes in the facilityTPProfile attribute of the managedFacilityTP object

Table 34-2

Support for 10 custom attributes as cpTypes in the packProfile attribute of the managedPack object

Table 36-2

Support for a new genericActionObject action, listCustomAttributeNames (1.2.124.113537.1.3.44)

section 29.16, and Tables B-39, C-2, and C-4

Pluggable node type Support for:

• pluggable node• custom cards on the pluggable node• custom ports on the custom cards• full links on the custom ports

Table 34-8 for custom cards

1353 NM node Support for:

• 1353 NM node• custom cards in the 1353 NM node• custom ports on the custom cards in the 1353 NM node• full links on the custom ports of the 1353 NM node

Table 32-4

1671 SC node Support for:

• 1671 SC node• forwarding alarms generated by the 1671 SC node• custom cards in the 1671 SC node• custom ports on the custom cards in the 1671 SC node• full links on the custom ports of the 1671 SC node

Table 32-4

MPLS support of pseudo-wires on the MR48 card

Support for the creation of a PSN link when one endpoint contains an MR48 card in the 7670 RSP node, Release 6.2 or later

section 14.3

1:N APS support for the STM1 MS (with or without CRIMA) and the OC3 MS (with or without CRIMA) cards

1:N APS support for the STM1 MS (with or without CRIMA) and the OC3 MS (with or without CRIMA) cards

Table 36-2

Edge services card Support for:

• edge services card (ESC) by the 7670 RSP, Release 6.2 or later

• 8-port OC3 I/O card in the ESC line card

Tables 34-2, 34-3, 34-4, 34-8, 35-4, 36-2, App A-1

7670 RSP, Release 6.1 Support for the 7670 RSP, Release 6.1. —

7670 RSP, Release 6.2 Support for the 7670 RSP, Release 6.2. —


(2 of 4)



NNI 32p CRIMA and OC3/STM1

• For VPC paths with endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and with cpType 20 of the groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to B-ICI/B-ISSI for both endpoints, the valid range is 0 to 4095.

• For VPC paths with endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and with cpType 20 of groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to UNI for both endpoints, the valid range is 0 to 255.

• For VPC paths with alternate endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and cpType 20 of groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to B-ICI/B-ISSI for both endpoints, the valid range is 0 to 4095.

• For VPC paths with alternate endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and cpType 20 of groomedCircuitTPProfile attribue of managedGroomedCircuitTP set to UNI for both endpoints, the valid range is 0 to 255.

• For VCC paths on a CR port in the OC3/STM1 MS card, the valid values are 0 to 255 regardless of the value of cpType 20 of the groomedCircuitTPProfile.

Tables 24-8, 35-2

Feature changes

FENT-A card running FENT3 software

Support for the FENT-A card running FENT3 software Table A-1

7321 RU, Release 2.1 Support for the 7321 RU, Release 2.1 Tables 24-8, and 37-1, 37-15, and “managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, node-specific profiles” in chapter 37

Listing links New listLinks action on the genericActionObject section 29.5

Path trace enhancements New connectionTrace action on the traceTestObject to retrieve the VPI, VCI, or DLCI values of all intermediate endpoints

sections 16.8 and 49.6, and Tables 16-3, C-2, and C-4

Frame relay access rate support

The cpType 23 of the frameRelayProfile attribute of the bMGroomedCircuit object has been modified to represent both the Interface Speed and Access Rate characteristics

Table 24-6

Cell mapping Support for cpType 87 (cell mapping) of the facilityTPProfile attribute of the managedFacilityTP object in DS3 ports on the MR48 line card

Table 34-2

CRC framing enhancement New cpType 96 (CRC framing) of the facilityTPProfile attribute of the managedFacilityTP object

Table 34-2

Enhancement to cpType 4 (source traffic policing option) and cpType 20 (destination traffic policing option)

Enhancement to allow different values for source and destination traffic policing for FRATM symmetrical connections

Table 24-8

Event handling robustness Enhancement to prevent a slow OSS from causing a 5620 NM event and alarm message overflow in the 5620 CMIP process

Tables D-3 and E-1

Frame relay traffic mapping and shaping enhancements

New cpType 51 (Mapping Method) and cpType 52 (Overhead Factor Frame Size) of the frameRelayProfile attribute of the bMGroomedCircuit object.

Table 24-6


(3 of 4)



Changes to cpTypes 49 (Minimum network jitter tolerance at endpoint A) and 50 (Minimum network jitter tolerance at endpoint Z) of tDMProfile attribute

New restrictions have been defined. Table 24-4

Documentation changes

New chapter to describe new and modified features and functionality

Enhancement to provide more visibility of new and modified features and functionality for the latest release

Chapter 1

Early packet discard Removed support for early packet discard from cpType 4 (source traffic policing option) and cpType 20 (destination traffic policing option) of the aTMProfile attribute of the bMGroomedCircuit object

Table 24-8

cpType 28 (IMA resource port assignment) of facilityTPProfile

Corrected the cpType of the IMA Resource Port Assignment, from cpType 22 to cpType 28. Updated the description about how to calculate the cpValue for cpType 28 by replacing “Calculating the cpValue for cpType 22 of facilityTPProfile—IMA Resource” with “Calculating the cpValue for cpType 28 of facilityTPProfile—IMA Resource Port Assignment”.

Table 34-2 and “Calculating the cpValue for cpType 28 of facilityTPProfile—IMA Resource Port Assignment” in Chapter 34

Specified the access for alternateATPId and alternateZTPID

Specified the access as read-write for the commonProfile attribute circuitProfile characteristics, alternateATPID and alternateZTPID

Table 24-11

Profile Type value The value for the ADSL line Profile Type of the managedProfileID structure for a node-specific profile has changed from 50 to 100

Table 37-8

Corrections to Procedures 5-2, 10-1, and 10-6

Corrected the following procedures:

• To check the 5620 CMIP status: In step 3, you must perform CE_control status, not CE_control mib-syncstatus

• Manually running a MIB audit, a MIB sync, or a MIB syncstatus: • Changed the procedure title from, “Manually running a

MIB audit or a MIB sync”• Added step 3c

• To report on the status of the 5620 CMIP database server: In step 2, you must perform CE_control mib-status, not CE_control mib-syncstatus

Procedures 5-2, 10-1, 10-6

Modified configuration parameter name for cpType 20 of the groomedCircuitTPProfile attribute of managedGroomedCircuitTP

Modified the configuration parameter for cpType 20 of the groomedCircuitTPProfile attribute of managedGroomedCircuitTP, from Port Type to Port Type/Resource Type, and modified the description

Table 35-2

Modified description for cpTypes 4 and 5 of the packProfile attribute of managedPack

cpTypes 4 (switching mechanism) and 5 (WTR timer) are valid only for 1:N protection card, not for 1+1 working card.

Table 36-2

Modified description for cpType 41 of the facilityTPProfile attribute of managedFacilityTP

Modified the description for cpType 41 (Protocol Type) of the facilityTPProfile attribute of managedFacilityTP

Table 34-2


(4 of 4)



1.3 What’s new for Release 7.1 H0 and H1

The following new features are supported in the 5620 CMIP, Release 7.1 H0 and H1:

• Solaris 10• enhanced alarm support• Quad OC3/STM1 SFP card on the 7470 MSP, Release 8.0 HLS#2 or later, and

7670 ESE, Release 4.0 HLS#2 or later• point-to-multipoint SPVC VCC and SPVC VPC paths on the 7270 MSC, Release

8.0 HLS#2 or later, 7470 MSP, Release 8.0 HLS#2 or later, and 7670 ESE, Release 4.0 HLS#2 or later

• 7670 RSP, Release 6.0 node• 3-DS3 frame processing card on the 7470 MSP, Release 8.0 HLS#2 or later, and

7670 ESE, Release 4.0 HLS#2 or later• point-to-multipoint VLAN endpoint support• round trip delay measurement

1.4 What’s new for previous releases

This section lists the features that were added to the 5620 CMIP, Releases 7.0, 6.3, 6.2, 6.1, 5.3, 5.2, 5.1, 5.0, 4.1, and 4.0.

Feature list for Release 7.0The following new features are supported in the 5620 CMIP, Release 7.0:

• optimization of scoped gets• migration to Informix database• current alarm list retrieval• bMFacility status• Quad OC3/STM-1 IMA card• OC3/STM-1 NT paths• real-time statistics collection• hitless MIB backup• 802.3ad link aggregation• policy-based routing support for SPVCs• router template support• DSL subscriber activation




• ATM pseudo-wire • point-to-multipoint SPVCs• logical multi-cast PVCs and SPVCs• MDR-8000 nodes• 7670 RSP Control Card 2 • STM-1 Electrical I/O on MR48 cards• OAM-CC/OAM-PM enhancements• 7670 RSP switched services• active connection modify for PVCs• listing bMGroomedCircuit by type• multiple endpoint paths• 7300 ASAM Releases 4.5.10, 4.6, 5.1 Phase 2• maximum frame length• port profile for Conklin FASTmux 2000 nodes




• 32-port T1/E1 MS cards• MR48 cards• GSLC cards• CR/IMA module for 32-port T1/E1 MS cards• 4-port OC3/STM1 CR line module• 8-port E1 CE cards for 7670 ESEs, Release 2.2, and 7470 MSPs, Release 5.0• bi-directional loopbacks for DS3 CCE-2 cards• UBR TACs for 7670 ESE Release 2.2 CR cards• 7300 ASAM, Release 4.5 management• 7300 ASAM, Release 5.0 management• VLAN support for FENT and GELT cards• SPVC connection modifications• RUEM LT card• E1/T1 NTs and 7390 Release 2.4• new actions for listFreeVCIs and listUsedVCIs, and

listFreeManagedGroomedCircuitTPs and listUsedManagedGroomedCircuitTPs• trmCircuitProfile of bMF for full and fractional links• pnniSummaryAddressProfile• eH indication of 7300 ASAM shelf type• documentation support of alarm feeds from the 5620 NM fault management

subsystem• application key enforcement of 5620 CMIP functionality• 36 LG name change support• 7670 ESE name change support• triple port DS3-2 CR cards 1:N APS• switched services support fir 32 Port T1/E1 Multi Service Card and CRIMA

module• multilink frame relay for 16 port T1/E1 multi service card on 7670 ESE, Release

2.2• support for 7670 ESE, Release 2.2• 1:N APS support on 32 port T1/E1 multi service card and CRIMA module• connection trace and ODR adjustments• 7750 SR support




• hitless connection moves using DBR• network call correlation identifier• multi-link frame relay for 16-port T1 and E1 cards• 802.1 Q VLAN on 7670 RSP GigE cards• UBR TACs for CR cards• enhanced HSPVCs• DS3 CR cards on 3600+

• 7470 MSPs and 7270 MSCs, Release 6.0, 7670 ESEs, Release 2.0, and 3600+s, 3600s, 3600 MSSs, and 3660s, Release 8.1

• automatic protection switching for 7770 routers• 7770 router, Release 2.0, backwards compatibility• PNNI address management• SPVC switched connections VBNs enhancements• 7300 ASAM legacy support using AWS• removal support for VPA shaping on VPC paths




• TDM/ATM Interworking for VoFR paths• ILMI channel configuration for ports on the UAI ATM type interfaces (ADSL,

SHDSL, T1 and E1)• 7390 NT, Release 2.3b• 7390 NT commissioning, replacement and decommissioning• VCC link support for 7390 NTs, Release 2.3b• Path management for 7390 CES NT ports, Release 2.3b• 7300 ASAM Release 4.4 node • 7300 ASAM Release 4.4 LP-UD ANSI shelf• 7300 ASAM Release 4.4 XD-Combo ETSI shelf• 7300 ASAM Release 4.4 NT cards (SANT-F, E3NT-C, D3NT-C, E1NT-C)• 7300 ASAM Release 4.4 UD and LIM Cards (SMLT-A, E1LT-B, E3LT-B,

D3LT-A, SALT-A and SALT-B)• 7300 ASAM Release 4.4 Gateway /Server Cards (VALT-A, IPGW-A)• 7300 ASAM Release 4.4 ACU Cards (AACU-C)• 7300 ASAM Release 4.4 48 Port ADSL cards (ADLT-O, ADLT-P, ADLT-Q,

ADLT-R)• 7300 ASAM Release 4.4 Extender Cards (ADSE-B)• 7300 ASAM Release 4.3 NT cards (SANT-F, D3NT-C)• 7300 ASAM Release 4.3 Extender Cards (ADSE-B)• 7300 ASAM Release 4.3 LIM Cards (ADLT-L, ADLT-J, DLIT-B, SHLT-B,

SMLT-A, SMLT-B, SALT-A, SALT-B)• 7300 ASAM Release 4.3 ACU Cards (AACU-C, AATU-B, ATAU-B)• zero port numbering and path management for GDC APEX-NPX node




• 7300 ASAM Release 4.3 node • 7300 ASAM Release 4.3 24-line ADSL/POTS Low Power card (ADLT-LP)• 7300 ASAM Release 4.3 24-line ISDN LT card (ADLT-N)• 7300 ASAM Release 4.2 UD Mini-RAM node• 7300 ASAM Release 4.2 UD ETSI Mini-RAM shelf• 7300 ASAM Release 4.2 12 line ISDN LT card (ADLT-K)• 7300 ASAM Release 4.2 OC3/STM-1 LT cards (SALT-A, SALT-B)• 7300 ASAM Release 4.2 24 port SHDSL LT card (SHLT-B)• 7300 ASAM Release 4.2 SHDSL LT ports• 7300 ASAM Release 4.2 IMA Resources on SHDSL LT cards• 7300 ASAM Release 4.2 OC3/STM-1 NT cards (SANT-D, SANT-E, SANT-F)• 7300 ASAM Release 4.2 DS3 NT cards (D3NT-A, D3NT-B, D3NT-C)• 7300 ASAM Release 4.2 E3 NT cards (E3NT-B, E3NT-C)• 7300 ASAM Release 4.2 ADSL12 POTS lines LT card (ADLT-J)• 7300 ASAM Release 4.2 SHDSL LT cards (SMLT-A, SMLT-B)• 7300 ASAM Release 4.2 IP Gateway card (IPGW-A)• 7300 ASAM Release 4.2 Logical ATM port on IP Gateway card• 7300 ASAM Release 4.2 E3 LT card (E3LT-A)• 7300 ASAM Release 4.2 E1 NT 4-port card (E1NT-C)• 7770 RCP Release 1.3 node• 7770 RCP Release 1.3 16 Port OC3/STM-1 card (IR variant)• 7770 RCP Release 1.3 8 Port OC12/STM-4 card (IR, LR variant)• 7770 RCP Release 1.3 2 Port OC48/STM-16 card (IR, SR, LR variant)• 7770 RCP Release 1.3 1 Port OC192/STM-64 card (IR, SR variant)• 7770 RCP Release 1.3 GigE card (1000BASE-SX, 1000BASE-LX variant)• 5620 installation improvements for NSM Release 5.2 loadset• reload performance enhancements


• 7670 RSP OC3/STM1 A2G card • 155 Mbps CR/IMA Module for OC3/STM1 MS card + IMA 1.1 T1/E1-2 CR card• ASAM 4.2• 1:N APS for 7670 ESE DS3CCE-2 card• 7470/7670 ESE Quad OC3/STM1 card• 7470MSP/7670ESE 8 Port DS3-CR card• 7670 RSP GigE card• asymmetrical configuration of VPCL Admin Weight• query object by name / FindByLabel action




• VP aggregation for 7470 MSP, 7270 MSC, and 7670 RSP• 7670 RSP Release 2.0 node• 7670 RSP Release 2.0 line card • 7670 RSP Release 2.0 path management• 7670 RSP Release 2.0 POS line card• 7670 RSP Release 2.0 diagnostics• Speed Touch PLNT V.35 circuit emulation NIU• eTM module• 7670 RSP ATM/MPLS mediation• 7300 VoDSL (VoATM management)• 36LG R2D signaling• 7670 RSP ESE node (supported in H0-01)• 7670 RSP ESE ECC card (supported in H0-01)• 7670 RSP ESE single-port OC3/STM1 MS card (supported in H0-01)• 36LG DSP5 HCV G3 Fax/Modem card (supported in H0-01)• operator-directed routing for ATM calls (supported in H1-00)


• 27LC3-12 card and 2801 phase II • 48-port SDSL card (initially supported in 4.0 H1-01)• IP service router card• diverse path• 16-port HD T1/E1 frame relay card• 27130 T1/E1 CE NIU• SPVC path and connection trace• TDM/ATM interworking for CSV and frame relay links• 300-32 IDSL card• SPVC and SVC sharing of VPC links• 7670 RSP 1.1 ATM management• 7470 MSP multiport ethernet card• NSM scalability• 7390 DBS and NT• 7300 ASAM• 7300 ASAM SHDSL• IMA link• 8-port DS3 ATM I/O card• 3-port DS3 CCE-2 card• PNNI aggregation token• DPM3 module



7390 DBS and NT support

The 7390 DBS and 7390 NT is supported in the Release 4.1. Release 4.1 does not provide support for the 7390 RBS (radio base station) and the 7390 RT (radio unit).


• 7470 MSP/7270 MSC 16-port PSI frame relay card • 7270 MSC 8-slot shelf • 7350 ASAM node • 7670 RSP—line card, ATM interface card, APS, and diagnostics• OAM-CC and OAM-PM • DMDS • SPVC-interworking • ATM full link bandwidth partitioning • ADSL release 2.0 card • quad T1/E1 CE NIU • 7470 MSP OC3/STM1 card



2.1 5620 CMIP 2-2

2.2 Functional description 2-2

2.3 Standards conformance 2-5

2.4 5620 CMIP Release 6.3 platform requirements 2-7



2.1 5620 CMIP

The 5620 CMIP is a CMIP-based software application that allows an OSS to control a network that the 5620 NM manages. The network can include various transmission technologies, such as TDM, ATM, frame relay, ISDN, ADSL, and wireless.

The 5620 CMIP supports a subset of the functionality of the 5620 NM. In general, the 5620 CMIP is compatible with the same network management software packages and transmission equipment as the 5620 NM. This documentation describes the 5620 CMIP architecture and functionality. For more information about configuring resources, we recommend referencing the 5620 NM documentation and the documentation for the resource in question.

The 5620 CMIP OSS Interface Gateway software is installed on a Sun workstation, known as the Gateway Station. The 5620 CMIP OSS Interface Gateway connects the OSS to the Sun workstation that runs the 5620 NM, known as the 5620 NM NetworkStation. The OSS accesses the 5620 CMIP MIB, which stores network objects that map from the database of the 5620 NM.

Through the 5620 CMIP, the OSS can:

• set up, modify and take down paths, frame relay links, and ATM links• keep an inventory of the network equipment• manage the forwarding and logging of network events• monitor the status of equipment, ports, links, and paths• activate statistics for paths and ports• perform maintenance and diagnostic tests

At the Gateway Station, an operator can:

• operate 5620 CMIP OSS Interface Gateway processes• perform some diagnostics• configure communication between the 5620 CMIP, the OSS, and the 5620 NM• manage the 5620 CMIP MIB• monitor the 5620 CMIP OSS Interface Gateway system and communication

messages

2.2 Functional description

The 5620 CMIP MIB is an important part of the 5620 CMIP. The MIB is a database which stores managed objects that model the components of the network, such as nodes, cards, ports, paths, and links.

The OSS sends CMIP operations to the 5620 CMIP. The 5620 CMIP, through the OSS Interface Agent, passes the requests to the 5620 NM. The OSS Interface Agent implements the changes in the database and the network and informs the 5620 CMIP of the changes. The 5620 CMIP then uses CMIP operations to update the objects in the MIB. The managed objects generate event notifications, which can be passed to the OSS as event or alarm reports by the eventForwardingDiscriminator object and logged as event or alarm log records.



When a 5620 NM operator makes a change in the network, or an event occurs in the network, the 5620 NM informs the 5620 CMIP. The 5620 CMIP then changes the managed objects in its MIB. The managed objects generate event report notifications, which can be passed to the OSS as event or alarm reports and logged as event or alarm log records. Figure 2-1 shows a block diagram of a 5620 CMIP operation.

Figure 2-1 A 5620 CMIP operation

Gateway Station

When the Gateway Station receives CMIP operations from the OSS, the CE_driver process can:

• pass CMIP operations to the OSS Interface Agent on the 5620 NM NetworkStation

• pass CMIP operations to the objects in the MIB• send responses back to the OSS• configure the eventForwardingDiscriminator object to send directed event reports

to the OSS• configure the log object to record event reports in the MIB

When the 5620 CMIP receives updates, responses, or alarms from the OSS Interface Agent on the 5620 NM NetworkStation, the MIB is updated. The CE_driver process can:

• convert responses, updates, and alarms into CMIP operations, which it passes to the objects in the MIB

• send directed event reports to the OSS through the eventForwardingDiscriminator object

• record event reports in the MIB through the log object

In addition, the CE_control process, which is situated on the Gateway Station, allows an operator to start or stop 5620 CMIP OSS Interface Gateway processes.

Operationssupportsystem

5620 CMIPGateway Station

Network

15347

5620 NM NetworkStation

5620 CMIPMIB

Object-orientedCMIS-structured

data store

5620 NMDatabase

Relationaldatabase



Figure 2-2 illustrates the information flow between the OSS, the 5620 CMIP OSS Interface Gateway (running on a Gateway Station), the 5620 NM (running on a 5620 NM NetworkStation), and the network.

Figure 2-2 Information flow between an OSS and a managed network

OSS Interface Agent

Three 5620 CMIP processes automatically load onto the 5620 NM NetworkStation:

• CE_agent process• CE_chgsrv process• CE_reload process

See section 8.3 for information about configuring the 5620 CMIP processes on the 5620 NM NetworkStation.

CE_agent process

This process translates commands and requests from the CE_driver process and passes them into appropriate interfaces for handling by the 5620 NM. The 5620 NM implements the changes in the network and updates its database. The CE_agent process also passes responses to the CE_driver process on the Gateway Station.

CE_chgsrv process

The change server process (CE_chgsrv) monitors all changes in the 5620 NM database, such as trouble tickets and path status change alarms, and passes them to the CE_driver process. The change server process also manages the CE_chgsrv queue. The queue stores 5620 NM database changes when the CE_driver process is either unavailable or unable to keep up with the CE_chgsrv updates. If network activity is high, then large queue count fluctuations will normally occur.

OSSworkstation

eFD = eventForwardingDiscriminator

CE_driver process

5620 CMIPOSS Interface Gateway

Database

Databasechanges

5620 NMNetworkStation

Network

Directed eventnotifications

Commands,responses,and events

15330

CMIPcommands, responses

and errors

q3

CE_agent

CE_chgsrv

CE_reload

Updates

Databaseunload

Database upload

Systemobjects

Networkobjects

Testobjects

LogeFD

Commands &responses

MIB



CE_reload process

The CE_reload process automatically activates whenever the CE_driver or CE_control process sends a MIB reload request. The CE_reload process deactivates once it finishes reloading the MIB.

2.3 Standards conformance

The 5620 CMIP conforms to standards that divide into eight categories:

• architecture layer• profiles layer• applications layer• presentation layer• session layer• transport layer• network layer• link layer

Architecture layer standards

The 5620 CMIP uses the following architecture layer standards:

• ITU-T M.3010 series, Principles for a TMN• ITU-T M.3010, Systems Management Overview• ITU-T X.200, Basic Reference Model• ITU-T X.200, Basic Reference Model, Part 2: Security Architecture• ITU-T X.200, Basic Reference Model, Part 3: Naming and Addressing• ITU-T X.200, Basic Reference Model, Part 4: Management Framework

Profiles layer standards

The 5620 CMIP uses the following profiles layer standards:

• ITU-T Q.811 Lower Layer Protocol for the Q3 Interface• ITU-T Q.812 Upper Layer Protocol for the Q3 Interface• ISO 11183-3 Management Communication Protocols, Part 3: AOM11 - Basic

Management communications



Applications layer standards

The 5620 CMIP uses the following applications layer standards:

• TMF 006, Object Library• ITU-T X.710 Common Management Information Services (CMIS)• ITU-T X.711 Common Management Information Protocol (CMIP)• ITU-T X.712 Protocol Implementation Conformance Statement (PICS)• ITU-T X.219 Remote Operations Service• ITU-T X.229 Remote Operations Protocol• ITU-T X.217 Association Control Service• ITU-T X.227 Association Control Protocol• ITU-T X.720 Management Information Services-Structure of Management

Information, Part 1: Management Information Model• ITU-T X.721 Structure of Management Information, Part 2: Definition of

Management Information• ITU-T X.722 Guidelines for the Definition of Managed Objects (GDMO)• ITU-T X.731 Systems Management, Part 1: Object Management Function• ITU-T X.732 Systems Management, Part 2: State Management Function• ITU-T X.733 Systems Management, Part 3: Attributes for representing

relationships• ITU-T X.734 Systems Management, Part 4: Alarm Reporting Function• ITU-T X.735 Systems Management, Part 5: Event Report Management Function• ITU-T X.736 Systems Management, Part 6: Log Control Function• ITU-T X.745 Test Management Function• ITU-T Q.821 Alarm Surveillance

Presentation layer standards

The 5620 CMIP uses the following presentation layer standards:

• ITU-T X.216 Presentation Service• ITU-T X.226 Presentation Protocol• ITU-T X.208 ASN.1• ITU-T X.209 Basic Encoding Rules (BER)

Session layer standards

The 5620 CMIP uses the following session layer standards:

• ITU-T X.215 Session Service• ITU-T X.215 Amendment 2, Unlimited user data• ITU-T X.215 Amendment 3, Connectionless Mode Session• ITU-T X.225 Session Protocol



Transport layer standards

The 5620 CMIP uses the following transport layer standards:

• ISO 8073: 1988 Connection Mode Transport Protocol• ISO 8073 Add2 Connection Mode Transport Service• RFC 1006 CMOT

Network layer standards

The 5620 CMIP uses the following network layer standards:

• ISO 8473 Protocol for Connectionless Mode Network Service• ISO 8348: 1987, Network Service Definition• ISO 8208 X.25 Packet Layer Protocol• ISO 8878 Use of X.25 to provide the OSI Connection Mode Network Service

Link layer standards

The 5620 CMIP uses the following link layer standards:

• ISO 7776 X.25 LAPB-Compatible DTE Data Link Procedures• ISO 8802-2 Logical Link Control• ISO 8802-3 CSMA/CD

2.4 5620 CMIP Release 6.3 platform requirements

To run the 5620 CMIP Release 6.3, the 5620 CMIP Gateway Station and 5620 NM NetworkStation must meet the following requirements.

Gateway Station hardware

The 5620 CMIP requires a Sun workstation, including a hard disk and a CD-ROM drive. The platform requirements, including disk space and RAM, depend on the size of the network.

See the 5620 CMIP OSS Interface Module Installation and Upgrade Guide for details about the platform requirements.

Gateway Station softwareThe Gateway Station must meet the following software requirements:

• 5620 CMIP Release 6.3, to manage a 5620 NM Release 6.3• Solaris 8• Solstice OSI Release 9.0



The 5620 NM NetworkStation

The 5620 NM NetworkStation must meet the following software requirements:

• Solaris 8• 5620 NM Release 6.3

Application Key

Beginning in Release 6.2, the 5620 CMIP enforces usage of the interface depending on whether the application key purchased allows the functionality through the interface. Restrictions based on the application key purchased means the following functionality may be turned off or turned on:

• alarm fowarding• provisioning• testing functionality• inventory management• 5620 CMIP interface• 5620 CORBA interface

The Application Key activates the OSS Interface Agent. The 5620 NM software supplies the Application Key.

See the 5620 NM documentation for instructions about installing the 5620 NM software and activating the Application Key.



3.1 Small systems 3-2

3.2 Basic configuration 3-2

3.3 Multiple OSS access 3-3

3.4 Multiple partitions 3-5

3.5 5620 CMIP redundancy 3-7

3.6 5620 NM redundancy 3-9



3.1 Small systems

In the small nonredundant system configuration, one OSS connects to one workstation that contains both the 5620 CMIP OSS Interface Gateway software and the 5620 NM software.

Ethernet links the OSS and the 5620 NM/5620 CMIP OSS Interface Gateway workstation. See section 2.4 for detailed platform requirements.

Figure 3-1 illustrates the small system configuration.

Figure 3-1 Small system configuration

3.2 Basic configuration

The basic system configuration consists of one OSS, one 5620 CMIP Gateway Station, and one 5620 NM NetworkStation. This configuration allows a single OSS to manage the entire network.

Ethernet links the OSS and the 5620 CMIP Gateway Station, as well as between the 5620 CMIP Gateway Station and the 5620 NM NetworkStation. See section 2.4 for detailed platform requirements.

Figure 3-2 illustrates the basic system configuration.

Note — This configuration is appropriate for small network development, lab trials, and testing.

5620 NM and 5620 CMIP OSS Interface Gateway

OSS

Network

Ethernet

15338



Figure 3-2 Basic system configuration

3.3 Multiple OSS access

The multiple OSS access configuration consists of several OSSs, one 5620 CMIP Gateway Station, and one 5620 NM NetworkStation. This configuration allows a number of peer OSSs to manage the entire network or one partition of a network. There is no restriction on the number of OSSs that may associate with the 5620 CMIP Gateway Station.


Figure 3-3 illustrates the multiple OSS configuration.

Note — This configuration is appropriate for large network development, lab trials, and testing.


5620 CMIP Gateway Station

OSS

Network

Ethernet

Ethernet

15332

Note — This configuration is appropriate for an environment with multiple OSS applications, such as fault management and provisioning diagnostics, at multiple sites.



Figure 3-3 Multiple OSS access configuration

By default, the 5620 CMIP allows up to 14 OSSs to be connected. Use Procedure 3-1 to increase the number of connected OSSs.

Procedure 3-1 To increase the number of connected OSSs allowed

1 As root on the 5620 CMIP Gateway station, start the OSI administration tool by typing:

/opt/SUNWconn/osinet/bin/ositool ↵

The OSI administration tool opens.

2 Choose the Stack Manager by clicking on the Stack Manager icon.

3 Right-click on the Configuration menu and choose Devices...

The Device Configuration window opens.

4 In the list of devices, select RFC1006 /dev/tcp/tcp

5 Configure the Connection Pool attribute with the number of clients you want to connect to the 5620 CMIP.

OSS COSS A OSS B

Ethernet

Ethernet

15333



Network



3.4 Multiple partitions

The multiple partition configuration consists of one or more OSSs, one or more 5620 CMIP Gateway Stations, one 5620 NM NetworkStation, and a partitioned network. Each OSS is connected to one or more 5620 CMIP Gateway Stations. Each 5620 CMIP Gateway Station accesses its own partition in the 5620 NM NetworkStation database. The MIB of each 5620 CMIP Gateway Station contains only the managed objects that correspond to its partition in the network. The partition is configured when the 5620 CMIP OSS Interface Gateway software is installed.

If an OSS is connected to multiple 5620 CMIP Gateway Stations, the network partition accessed by the OSS depends on the route the OSS selects between itself and the 5620 CMIP Gateway Station.

See the 5620 NM documentation for information about configuring partitions.


Partitioning with two OSSsFigure 3-4 illustrates a multiple partition configuration with two OSSs. Each 5620 CMIP Gateway Station manages a single partition. OSS A connects to 5620 CMIP Gateway Station A and manages Partition A; OSS B connects to 5620 CMIP Gateway Station B and manages Partition B.

Note — To ensure that the 5620 CMIP OSS Interface Gateway receives alarms that are specific to the 5620 NM, each 5620 NM partition that is managed through the 5620 CMIP OSS Interface Gateway must contain the node corresponding to the 5620 NM NetworkStation.

Note — This configuration can be expanded to accommodate more than two 5620 CMIP Gateway Stations and OSSs.



Figure 3-4 Multiple partition configuration with two OSSs

Partitioning with one OSSFigure 3-5 illustrates a multiple partition configuration with one OSS and one 5620 CMIP Gateway Station.

OSS B

5620 CMIPGatewayStation A

5620 CMIPGatewayStation B

OSS A

Partition A

Ethernet

Ethernet

A B

Partition B


15327

Note — The 5620 CMIP OSS Interface Gateway sees the entire network but does not see the partition. For this configuration, the 5620 CMIP OSS Interface Gateway software is installed with a Supply Network partition name.



Figure 3-5 Multiple partition configuration with one OSS

3.5 5620 CMIP redundancy

The 5620 CMIP redundancy configuration consists of a single OSS, two 5620 CMIP Gateway Stations and one 5620 NM NetworkStation that can be accessed by either 5620 CMIP Gateway Station.

In this configuration, both 5620 CMIP Gateway Stations are identical and hot. Should one 5620 CMIP Gateway Station fail, the redundant twin is already running and in communication with the 5620 NM NetworkStation. The OSS must monitor communication with both 5620 CMIP Gateway Stations to determine which 5620 CMIP Gateway Station is considered active. This is fundamentally different from the 5620 NM, where only one machine, the active or standby 5620 NM NetworkStation, can be hot at any given time.

15360

A B5620 NM NetworkStation


OSS

Ethernet

Ethernet

Partition A

Partition B



Some basic recommendations to consider when configuring redundant 5620 CMIP Gateway Stations are:

• the eventForwardingDiscriminator and log information must be configured on both machines to ensure information is preserved if communication is lost

• any changes to the config files (queue size, etc.) of one 5620 CMIP Gateway Station must also be performed on the redundant twin 5620 CMIP Gateway Station

• the CE.security.conf file must be identical on both 5620 CMIP Gateway Stations• any 5620 CMIP configuration changes that are done on the active 5620 NM

NetworkStation must also be done on the standby 5620 NM NetworkStation

Ethernet links the OSS and the 5620 CMIP Gateway Station, as well as the link between the 5620 CMIP Gateway Station and the 5620 NM NetworkStation. See section 2.4 for detailed platform requirements.

Figure 3-6 illustrates the 5620 CMIP redundancy configuration. This architecture will assure that there is a redundant path for messages from the 5620 NM NetworkStation to the OSS. This is also a possible architecture for load sharing across the two 5620 CMIP Gateway Stations.

Figure 3-6 5620 CMIP redundancy configuration

Note — This redundant configuration improves 5620 CMIP system availability in the event of a failure or a malfunction on the 5620 CMIP Gateway Station. This configuration can be used for load balancing.

This configuration can be expanded to accommodate more than two 5620 CMIP Gateway Stations and multiple OSSs.

5620 CMIPGatewayStation B

5620 CMIPGatewayStation A

Network


OSS

Ethernet

15328



3.6 5620 NM redundancy

In the 5620 NM redundancy configuration, one or more OSSs and one or more 5620 CMIP Gateway Stations connect to the active and standby 5620 NM NetworkStations. The standby 5620 NM NetworkStation maintains a duplicate network database and can take control of the network if the active 5620 NM NetworkStation fails.

When an activity switch takes place, the standby 5620 NM NetworkStation becomes the active 5620 NM NetworkStation. All processes then start on the newly activated 5620 NM NetworkStation. This includes processes that are communicating with the 5620 CMIP OSS Interface Gateway.

If there is more than one 5620 CMIP Gateway Station in a 5620 NM redundancy configuration when 5620 CMIP parameters are being configured, the same parameters must be configured on all 5620 CMIP Gateway Stations.


Figure 3-7 shows a single OSS, a single 5620 CMIP Gateway Station and a redundant 5620 NM NetworkStation configuration.

Note — This configuration is appropriate for a production environment that requires high availability of the 5620 NM.



Figure 3-7 Single 5620 CMIP Gateway Station and OSS, redundant 5620 NM NetworkStation configuration

Figure 3-8 depicts a single OSS with a redundant 5620 CMIP Gateway Station and a redundant 5620 NM NetworkStation configuration. Since the 5620 CMIP Gateway Stations and the 5620 NM NetworkStations are in a redundant configuration, the singular point of failure for this configuration is the OSS.

Note — This configuration is appropriate for a production environment that requires high availability of both the 5620 NM and the 5620 CMIP OSS Interface Gateway.

5620 CMIPGateway Station

OSS

Network

Ethernet

Ethernet

Standby5620 NM

NetworkStation

Active5620 NM

NetworkStation

15329



Figure 3-8 Redundant 5620 CMIP Gateway Station and 5620 NM NetworkStation, single OSS configuration

Figure 3-9 shows a redundant 5620 NM NetworkStation, a redundant 5620 CMIP Gateway Station, and a redundant OSS configuration. Since all components have redundant counterparts, there are no singular points of failure in this configuration. This architecture provides the maximum redundancy.

Note — This configuration is typical of most production environments and is the recommended configuration.

This configuration can be expanded to accommodate more than two 5620 CMIP Gateway Stations and multiple OSSs.

Active5620 NM

NetworkStation

Ethernet

15342

5620 CMIPGateway Station A

5620 CMIPGateway Station B

Standby5620 NM

NetworkStation

Network

OSS

Ethernet



Figure 3-9 Redundant 5620 CMIP Gateway Station, 5620 NM NetworkStation and OSS configuration

Active5620 NM

NetworkStation

Ethernet

15343

5620 CMIPGateway Station A

5620 CMIPGateway Station B

Standby5620 NM

NetworkStation

Network

OSS A OSS B

Ethernet



4.1 Configuring ELS options 4-2



4.1 Configuring ELS options

The 5620 CMIP processes, such as CE_control, generate ELS messages that you can view and/or log. Table 4-1 summarizes the relevant display options.

The messages are not passed to the OSS.

Table 4-1 5620 CMIP process ELS message options

Note(1) Table 4-4 describes the message levels.

To access the logged process messages at either the 5620 CMIP Gateway Station or the 5620 NM NetworkStation, use logtool 5620 NM or log 5620 NM. On the 5620 CMIP Gateway Station, the data files are in the /opt/netmgt/conexec/bin/els directory. On the 5620 NM NetworkStation, the data files are in the /opt/netmgt/bin/els directory.

Table 4-2 describes ELS message options.

Table 4-2 5620 CMIP process ELS message options

Table 4-3 describes ELS message level values.

Description ELS process option

Display or log the messages on the Gateway Station -Srstate

Log the messages on another machine -SrIP address

Specify the level of the messages (1) -Sld

Include the UNIX process ID with the message -Sp

Option Description Values Value description Default value

-Sld Specifies the level of process ELS messages to be displayed or logged

d = 1 to 7 See Table 4-3 3

-Srstate Specifies whether the process ELS messages are logged or displayed

state = on or off on sends the messages to the 5620 CMIP logfile; off sends the messages to the window

on

-Srremote Sends the 5620 CMIP process messages to a logfile on another machine

remote = up to the Sun workstation's limit of alphanumeric characters

Identifies the hostname or IP address of the remote logfile

Current host

-Sp Specifies that the 5620 CMIP process messages shall include the UNIX process ID

None — None



Table 4-3 5620 CMIP process ELS message level values

Note(1) The value determines which levels of messages are displayed or logged. For example, a message level value of 6 causes

Fatal error (F) and Sun Logfile (L) messages to be displayed or logged.

Table 4-4 describes ELS message levels.

Table 4-4 5620 CMIP process ELS message levels

Note(1) The message levels that are displayed or logged depend on the message level value used in the -sld option of

Tables 4-1, 4-2, and 8-4. The message level values are described in Table 4-3.

Viewing and using the logtoolYou can use logtool or the log to access the logged process ELS messages. The data files are in the /opt/netmgt/conexec/bin/els directory

Message level value (1)

Level of message to be displayed or logged

Debug

(D)

Database

(U)

Information

(I)

Warning

(W)

Serious error (S)

Fatal error (F)

Sun logfile

(L)

1 ✓ ✓ ✓ ✓ ✓ ✓ ✓

2 ✓ ✓ ✓ ✓ ✓ ✓

3 ✓ ✓ ✓ ✓ ✓

4 ✓ ✓ ✓ ✓

5 ✓ ✓ ✓

6 ✓ ✓

7 ✓

Message level code

Message level (1)

Description of message level

D Debug Debugging information (for example, the name of a routine being executed)

U Database Database activity (for example, a record being written to the database)

I Information Information about transactions (for example, a normal process startup or shutdown)

W Warning Possible problem (for example, when unexpected data on a socket connection must be discarded)

S Serious error

A problem (for example, when an attempt to write a database record fails)

F Fatal error Processing cannot continue (for example, when a process cannot open the database)

L Sun logfile Sun logfile message to the logfile (used for major system control events, such as the 5620 CMIP being started)



Procedure 4-1 To set ELS environment variables

You can set the environment variables to control the display of the ELS tool.

1 Open a command or shell tool.

2 Set the ELSDATAFILEHOME variable.

a When the 5620 NM and the 5620 CMIP are on the same NetworkStations, type:

setenv ELSDATAFILEHOME /installdir/bin/els ↵

where installdir is the installation directory of the 5620 NM

b When the 5620 NM and the 5620 CMIP are on different NetworkStations, type on the Gateway Station:

setenv ELSDATAFILEHOME /installdir/conexec/bin/els ↵

where installdir is the installation directory of the 5620 CMIP

Format of the process ELS messagesTable 4-5 describes the fields that are part of an ELS message format.

Table 4-5 Displayed or logged ELS message formats

Two process ELS message examples are displayed below.

May5 09:33:52.8 D CEDr [tid=19] App performed a successful set

May5 09:33:52.8 I CEAg TCP_Setup Client Socket

Table 4-6 identifies the fields in the above two process ELS message examples.

Field Description

1 The date that the message was generated, in the format: Monthm/dd where Month is the name (Month) and dd is the date

2 The time of day that the message was generated, in the format: hour:minute:second.millisecond

3 Message level code (D, U, I, W, S, F or L) of the displayed message; see Table 4-4

4 First four characters of the process name

5 UNIX process identifier (if the -sp option is selected)

6 The message



Table 4-6 ELS message examples

Field 1 Field 2 Field 3 Field 4 Field 5 Field 6

May5 09:33:52.8 D CEDr tid=19 App performed a successful set

May5 09:33:52.8 I CEAg — TCP_Setup Client Socket



5.1 The Gateway Station 5-2

5.2 Manually controlling the 5620 CMIP 5-3



5.1 The Gateway Station

The Gateway Station must have the 5620 CMIP OSS Interface Gateway software installed and must be connected to the 5620 NM NetworkStation and to the OSS.

The 5620 CMIP will not start on the Gateway Station until the OSS Interface Agent is activated on the 5620 NM NetworkStation through the Application Key, which is supplied as part of the 5620 NM software.

Table 5-1 describes where to find prestartup information.

Table 5-1 Prestartup information

5620 CMIP OSS Interface Gateway processes

The 5620 CMIP OSS Interface Gateway software has several processes on the Gateway Station.

The CE_control process starts or stops 5620 CMIP OSS Interface Gateway processes. See section 5.2 for more information.

The CE_driver process behavior is configurable. See section 6.1 for information about the CE_driver process functions.

The 5620 CMIP OSS Interface Gateway uses Solstice OSI to communicate with other systems. See section 7.4 for information about configuring communication between the 5620 CMIP and the OSS.

See section 8.3 for information about the OSS Interface Agent processes that run on the 5620 NM NetworkStation.

Automatic startup of the 5620 CMIP

At 5620 CMIP startup, communication with the 5620 NM is automatically established. The MIB is then automatically synchronized to the 5620 NM database through the MIB reload function. If the MIB is empty at 5620 CMIP startup, then the 5620 CMIP performs a full MIB reload and the MIB is fully loaded from the 5620 NM database. If the MIB is not empty at the time of 5620 CMIP startup, then the 5620 CMIP performs an update MIB reload.

For information on See

Software installation 5620 CMIP OSS Interface Module Installation and Upgrade Guide

Application Key Appropriate 5620 NM documentation

Communication with the 5620 NM, including 5620 NM partition name and network ID, and the 5620 CMIP on the 5620 NM

Section 7.3

Communication with the OSS Section 7.4

Configuring the CE_driver process Section 6.1



During an update MIB reload, only the changes made to the 5620 NM database during the period of disconnection will be automatically loaded into the MIB. The MIB reload status may be determined by checking the 5620 CMIP status. See section 5.2 for information about checking status.

Table 5-2 lists functions that an can be performed on the 5620 CMIP once it is running.

Table 5-2 Function information

5.2 Manually controlling the 5620 CMIP

The CE_control process provides a command line interface from the 5620 CMIP OSS Interface Gateway.

The following functions can be performed through the CE_control process:

• start• status• warm stop• security

Procedures for CE_control processes start, status, and warm stop are detailed later in this section. Section 11.3 describes the CE_control processes for security.

CE_control process optionsThe CE_control process, along with all 5620 CMIP processes, generates ELS messages. The 5620 CMIP can be configured to display or log these ELS messages. Table 4-2 describes the ELS message options. ELS message options can be chosen as part of procedure 5-1.

Table 4-3 lists the message levels that can be specified through the -Sl option, described in Table 4-2.

When a process ELS message is displayed or logged, it includes a letter code to indicate its message level.

Table 4-4 describes the message level codes and the type of information provided by each message level for a displayed or logged process ELS message.

For Information about See section

Checking 5620 CMIP status 5.2

Configuring CE_driver process options 6.1

Communication with the 5620 NM 7.3

Communication with the OSS 7.4

Configuring 5620 CMIP process options on the 5620 NM

8.3



Procedure 5-1 Starting the 5620 CMIP

1 Log in as root by typing:

su root ↵

2 At the Gateway Station, change to the 5620 CMIP directory by typing:

cd /opt/netmgt/conexec/bin ↵

3 Start the 5620 CMIP.

a To start the 5620 CMIP with the default CE_control ELS process message options described in Table 4-2, type:

CE_control start ↵

b To start the 5620 CMIP with different CE_control ELS process message options, type:

CE_control start option(s) ↵

where option(s) is the desired CE_control message option or string of options, separated by spaces

Procedure 5-2 To check the 5620 CMIP status


su root ↵



3 Type:

CE_control status ↵

The status of the 5620 CMIP system is displayed. Table 5-3 describes the status messages.

Note — The 5620 CMIP is started automatically whenever the Gateway Station is rebooted. See the 5620 CMIP OSS Interface Module Installation and Upgrade Guide for information about rebooting the Gateway Station.



Table 5-3 5620 CMIP status messages

Procedure 5-3 Stopping the 5620 CMIP


su root ↵



3 Type:

CE_control warmstop option(s) ↵

where option(s) is the desired CE_control message option or string of options, separated by spaces

5620 CMIP status Message description

down “5620 CMIP has not been started or is not running”

“could not receive status information from CE_driver”

“could not send status to CE_driver”

“problem obtaining socket to CE_driver”

“CE_driver is in an unknown state”

up “CE_driver is connecting to the agent”

“CE_driver is registering with the agent”

“CE_driver is waiting for the agent to respond to a startup request”

“CE_driver is connecting to the change server”

“CE_driver is registering with the change server”

“CE_driver is waiting for the change server to respond to a startup request”

“CE_driver is starting a reload”

“CE_driver is performing a reload”

“CE_driver is performing node reload”

“CE_driver is running”

“CE_driver is shutting down”

“CE_driver is deleting the MIB in preparation for a reload”

“CE_chgsrv queue has previously overflowed”

“reload has previously failed”

Note — When performing a warm stop to shut down the 5620 CMIP, any changes to the MIB are queued until the 5620 CMIP is restarted.



The 5620 CMIP stops and halts communication with the OSS and the 5620 NM. The CE_chgsvr saves queued messages and queues new messages. The CE_chgsvr transmits these messages when the connection is re-established. See section 7.3 for more information about CE_chgsvr messages.

Procedure 5-4 Stopping the CE_driver and CE_mibmgr processes


su root ↵



3 Type:

CE_control stopce ↵

The 5620 CMIP stops the CE_driver and CE_mibmgr processes, but leaves the 5620 CMIP database server running.

Procedure 5-5 Starting the CE_driver and CE_mibmgr processes


su root ↵



3 Type:

CE_control startce ↵

The 5620 CMIP starts the CE_driver and CE_mibmgr processes.

Procedure 5-6 Stopping the 5620 CMIP database server


su root ↵





3 Type:

CE_control stopdb ↵

The 5620 CMIP database server stops.

Procedure 5-7 Starting the 5620 CMIP database server


su root ↵



3 Type:

CE_control startdb ↵

The 5620 CMIP database server starts.



6.1 CE_driver process options 6-2



6.1 CE_driver process options

The 5620 CMIP operations can be modified by setting various CE_driver process options. These options perform the following functions:

• configure the CE_driver process startup• display and log CE_driver process ELS messages

CE_driver process options can be set through the netconfig.CEprocess file.

netconfig.CE process file

The netconfig.CE process file is installed on the Gateway Station as part of the installation process described in the 5620 CMIP OSS Interface Module Installation and Upgrade Guide. This file contains one configurable entry that provides information about the CE_driver process. The entry in the file can be configured to suit a specific network operation.

An example of the netconfig.CE process file is shown below. For the purpose of illustration, the fields (F#) have been identified.

F1 F2 F3 F4 F5 F6 F7 F8 F9

CE_driver NONE 0 10 - 0 0 0 Sl3

CE_driver process entry fields

Table 6-1 repeats the CE_driver entry from the above example with field identifiers and field descriptions. Fields 2 to 8 configure the CE_driver process startup; field 9 performs other CE_driver process functions.

Table 6-1 CE_driver process entry options

Table 6-2 summarizes the CE_driver process startup configuration options.

Field Number Description Example

1 Process name CE_driver

2 Depend option None

3 Group option 0

4 Wait option 10

5 Class option Not applicable

6 Priority option 0

7 TQ option 0

8 Processor option 0

9 Argument option Sl3



Table 6-2 CE_driver process startup configuration options

Notes(1) See Table 6-1 for the fields to use with the options(2) See Table 6-3 for details(3) See Tables 4-2, 4-3, 4-4, and 4-5 for CE_Driver process ELS message options

Table 6-3 summarizes the CE_driver process MIB reload options.

Table 6-3 CE_driver process MIB reload options

Note(1) See Table 6-1 for the fields to use with the options.

Configuring the CE_driver processProcedure 6-1 describes how to configure the options in Table 6-2.

Option (1) Option description Values Value description

Default value

Depend Starts process after another process has started

Up to the Sun workstation's limit of alphanumeric characters

Name of process

NONE

Group Not configurable 0 Always 0 0

Wait Causes the process to wait before starting

0 to 231-1 Number of seconds before starting

0

Class Not applicable Not applicable Not applicable Not applicable

Priority Sets the priority of the process 0 to 19 Priority value 0

TQ Causes the process to wait before starting

0 to 231-1 Number of seconds before starting

0

Processor Not configurable 0 Always 0 0

Argument MIB reload (2)

Displaying and logging (3) ELS messages

— — —

Option (1) Option description

Values Default value See section

-r Reloads the MIB on subsequent startup

None No reload on start up

9.3

-s Reloads the MIB on startup

0, 1 0 = no

1 = yes

9.3

-e Exit the system if reload fails

None No notifications 9.3



Procedure 6-1 To configure CE_driver options


su root ↵



3 If the 5620 CMIP is running, stop it by typing:

CE_control warmstop ↵

4 Open the netconfig.CEprocess file by typing:

vi netconfig.CEprocess ↵

5 Configure the CE_driver process options by editing the appropriate fields of the CE_driver entry.

6 Start the 5620 CMIP by typing:

CE_control start ↵


7 — Communication

7.1 Introduction 7-2

7.2 Network element communication 7-2

7.3 Communication between the 5620 CMIP OSS Interface Gateway and the 5620 NM 7-3

7.4 Communication with the OSS 7-4

7 — Communication


7.1 Introduction

Communication takes place between:

• 5620 NM and the network (proprietary)• 5620 CMIP OSS Interface Gateway and the 5620 NM (proprietary)• OSS and the 5620 CMIP OSS Interface Gateway (Q3)

Figure 7-1 shows the basic 5620 CMIP configuration.

Figure 7-1 Basic system configuration

7.2 Network element communication

CPSS, a proprietary communication protocol, is used for communication between the network and the 5620 NM. If communication between the 5620 NM and the network is lost, the 5620 NM changes the status of each node in its database to off-line. The 5620 CMIP sets the operationalState attribute value of each node object in its MIB to disabled. The OSS can then only make changes that do not affect the network nodes.

Once communication between the 5620 NM and the network is reestablished, the 5620 CMIP sets the operationalState attribute value of each node object in its MIB to enabled.



OSS

Network

CMIP

TCP/IP

CPSS

15323

7 — Communication


7.3 Communication between the 5620 CMIP OSS Interface Gateway and the 5620 NM

Communication between the 5620 CMIP OSS Interface Gateway software and the 5620 NM software uses TCP/IP standard sockets. If communication between the 5620 CMIP OSS Interface Gateway and the 5620 NM is lost, the 5620 CMIP OSS Interface Gateway sends an alarm to the OSS. In addition, the 5620 NM creates a trouble ticket to notify the 5620 NM operator of the communication loss and the 5620 CMIP icon on the 5620 NM navigation map changes to red. See chapter 21 for details about alarms.

A check of the 5620 CMIP status, using the CE_control status command, indicates that communication has been lost. See section 5.1 for information about the CE_control status command.

While the communication link is down, the 5620 CMIP rejects commands from the OSS that affect configuration management. Any changes made in the network while the communication link is down are stored in the 5620 CMIP change server, known as the CE_chgsrv queue, on the 5620 NM NetworkStation. The CE_chgsrv queue is part of the CE_chgsrv process. See section 8.3 for information about the CE_chgsrv process.

Once the communication link is restored, the MIB is automatically updated according to the contents of the CE_chgsrv queue. If there were too many changes to be recorded in the CE_chgsrv queue, an overflow occurs and the 5620 CMIP sends a change notification queue overflow alarm to the OSS.

To establish the communication link between the 5620 CMIP and the 5620 NM, configure the following:

• 5620 NM partition name and network identification on the 5620 CMIP OSS Interface Gateway

• OSS Interface Agent processes on the 5620 NM NetworkStation

Partition name and network identification

The 5620 NM identification, second-level network name, partition name and the local address (stack name) of the 5620 CMIP are configured through the CE_network.conf file as part of the software installation process. See the 5620 CMIP OSS Interface Module Installation and Upgrade Guide for information about the 5620 CMIP software installation and the CE_network.conf file.

OSS Interface Agent processes on the 5620 NM NetworkStation

Before establishing communication between the 5620 CMIP OSS Interface Gateway and the 5620 NM, install the OSS Interface Agent processes.

See the 5620 CMIP OSS Interface Module Installation and Upgrade Guide for information about the 5620 CMIP software installation and the CE_network.conf file.

7 — Communication


7.4 Communication with the OSS

Communication between the 5620 CMIP OSS Interface Gateway and the OSS uses one of the following protocols:

• RFC 1006 (OSI over TCP/IP)• a full OSI seven-layer stack

If communication between the 5620 CMIP OSS Interface Gateway and the OSS is lost, the 5620 CMIP OSS Interface Gateway continues to accept changes from the 5620 NM and keeps its MIB up-to-date.

The 5620 CMIP OSS Interface Gateway uses a third-party software system (Solstice OSI) to communicate with the OSS.

OSI presentation address

Table 7-1 describes the communication link environment variables and their typical values. See the Solstice manual for information about link environment variables.

Table 7-1 Communication link environment variables

Note(1) This sample value is the NSAP value of 0x08002082F49C01 which is based on an OSS Ethernet address that has a

hexadecimal value of (8:0:20:82:F4:9C).

Association management

The OSS can send an association request with or without an AP-Title.

If the OSS sends an association request without an AP-Title, event notifications cannot be sent to the OSS. All other operations are possible.

An association must exist before the 5620 CMIP can transfer eventReports and alarms to an OSS application. Either the OSS or the 5620 CMIP can initiate an association. The OSS initiates an association between one of its applications and the 5620 CMIP.

Caution — If the OSS is on a different subnetwork than the 5620 CMIP OSS Interface Gateway, then full OSI routers are required. RFC 1006 is commonly used to avoid this requirement.

Environment variable Description Sample value

agent PSEL presentation selector aPs

agent SSEL session selector aSs

agent TSEL transport selector aTs

NSAP network service access point 0x08002082F49C01 (1)

7 — Communication


The 5620 CMIP has the functionality to automatically create an association with the OSS. An association must be established to enable the transfer of eventReports from the 5620 CMIP to the OSS.

The OSS must complete the following steps to configure automatic association:

• create an association with the 5620 CMIP that specifies an AP-Title• create an eventForwardingDiscriminator object in the MIB with a destination

address for the OSS that will receive event reports• create an entry in the CE_security.conf file containing the OSS AP-Title,

permissions and the OSI address

See section 11.1 for information about editing the CE_security.conf file.

Table 7-2 describes the association request parameters.

Table 7-2 Association request parameters

Parameter Access Description

protocolVersion Implicit Bit string, default = 1

application-context-name Required 2.9.0.0.2 = Manager-Agent application context, used to identify the sender

calling-AP-title Optional Any OID, used to identify the sender

implementation-information Implicit Implementation data

user-information Implicit Association information

7 — Communication




8.1 Communication status 8-2

8.2 Configuring the 5620 CMIP OSS Interface Gateway node 8-2

8.3 Configuring OSS Interface Agent processes on the NetworkStation 8-3



8.1 Communication status

Figure 8-1 illustrates how the 5620 CMIP is represented on the 5620 NM network navigation map as a node icon. Unlike most other node icons on the map, it cannot be opened and a link cannot be drawn to it.

Figure 8-1 5620 CMIP Icon

Icon colors

The communication status of the 5620 CMIP is indicated by the color of the icon. Table 8-1 lists the status for each color.

Table 8-1 Icon colors and communication status

8.2 Configuring the 5620 CMIP OSS Interface Gateway node

Table 8-2 lists the 5620 NM operations supported by the 5620 CMIP OSS Interface Gateway node.

See the appropriate 5620 NM documentation for detailed operation instructions.

Table 8-2 Supported 5620 NM operations

3884

Icon color Communication status

Green The 5620 CMIP OSS Interface Gateway and the 5620 NM are currently communicating.

Yellow The 5620 CMIP MIB is currently being reloaded from the 5620 NM NetworkStation.

Red The 5620 CMIP OSS Interface Gateway is not currently communicating with the 5620 NM.

Operation Description

Select→object To display the object, node type, short name, status and release in the selected object panel

Edit→Configure Object To configure the 5620 CMIP node

(1 of 2)



The node short name, CMIS stack name, and the internet address of the 5620 CMIP OSS Interface Gateway node for the 5620 NM can be configured through a configuration form on the NetworkStation. If the node short name is not configured, the 5620 CMIP creates one when communication is established with the 5620 CMIP OSS Interface Gateway.

To access the configuration form, double-click on the 5620 CMIP icon or select the 5620 CMIP icon and choose Edit→Configure Object.

The CMIS stack name is configured by setting the SystemName parameter, which is specified in the CE_network.conf file.

The CMIS stack name and internet address can only be changed when the node is off-line. The short name can be changed at any time.

8.3 Configuring OSS Interface Agent processes on the NetworkStation

Table 8-3 summarizes the three configurable OSS Interface Agent processes that run on the NetworkStation. They are included with the 5620 NM software.

Table 8-3 OSS Interface Agent processes on the 5620 NM NetworkStation

Edit→View Configuration To view the 5620 CMIP node configuration

Edit→Delete To delete the 5620 CMIP node

Tools→Fault Management→Trouble Ticket→New

To create a trouble ticket against the 5620 CMIP node

Tools→Fault Management→Trouble Ticket→List

To list trouble tickets against the 5620 CMIP node

View→Highlight→Object To highlight the 5620 CMIP node

View→Highlight→Trouble Ticket

To highlight trouble tickets

Operation Description

(2 of 2)

OSS Interface Agent process

Description

CE_agent process Interfaces with the 5620 CMIP OSS Interface Gateway

CE_chgsrv process Manages the CE_chgsrv (the CE change server) queue

CE_reload process Manages reloading of the MIB



When you install the OSS Interface Agent software, the CE_agent and CE_chgsrv process files are automatically added into directory where the 5620 NM configuration files are stored. They are activated by the 5620 CMIP application key. The configuration files are XML formatted, and must conform to the provided XML schema. See the 5620 Network Manager User Guide for information about configuration files and application keys. See section 2.2 for information about the functions of the processes.

Procedure 8-1 To reconfigure OSS Interface Agent processes

1 As root or a member of nmsadmin on the NetworkStation, change to the 5620 NM directory by typing:

cd /opt/netmgt/conf/nms ↵

2 Copy 5620.CE_agent.xml and 5620.CE_chgsrv.xml by typing:

cp /opt/netmgt/etc/nms/5620.CE_agent.xml ↵

cp /opt/netmgt/etc/nms/5620.CE_chgsrv.xml ↵

3 Open the 5620.CE_agent.xml and 5620.CE_chgsrv.xml files using a text editor.

4 Configure the 5620 CMIP options:

i For the CE_agent process, edit options in the 5620.CE_agent.xml file.

ii For the CE_chgsrv process, edit options in the 5620.CE_chgsrv.xml file.

Table 8-4 describes the options. See the 5620 Network Manager User Guide for more information about modifying configure files.

5 Open the /etc/inetd.conf file and in the CE_reload entry, configure /opt/netmgt/conexec/bin/CE_reload options according to the options in Table 8-4.

Table 8-4 5620 CMIP process options on the NetworkStation

Note — These processes automatically configure during installation and do not normally require reconfiguration.

Option 5620 CMIP process

Option description Values Value description Default value

depend process

All Starts the process after another has started

process = up to the Sun workstation's limit of alphanumeric characters

Name of other process None

waittime All Causes the process to wait the specified number of seconds before starting

time = 0 to 231-1

Number of seconds 0

(1 of 3)



Displaying and logging ELS messages

All ELS displaying and logging options

— See Tables 4-3, 4-4, and 4-5 —

-qsize CE_chgsrv Size of CE_chgsrv queue that holds entries while the link between the 5620 CMIP Gateway Station and the 5620 NM is down or the MIB is being reloaded

size = 1000 to 1000000

Number of entries 500000

-a CE_agent Allows atomic sets (1) None — None

-a CE_chgsrv and CE_reload

Automatically makes all DS0s associated with termination point objects visible to the OSS

None — None

-e CE_chgsrv Allows forwarding of AWS alarms from the AS tool IM to the OSSI

None — None

-f CE_chgsrv Disables intermediate termination point status change reporting on multihop groomed circuits objects

None — None

-mEUL CE_agent

CE_chgsrv

CE_reload

Displays the short name, full name, or both short name and full name of the node in the userLabel attribute of the managedElement object.

When this option is absent, or is present without the -s or -b parameter, the userLabel attribute of the managedElement object contains the full name of the node.

This option must be configured identically for CE_agent, CE_chgsrv, and CE_reload.

-s Displays the short name of the node in the userLabel attribute of the managedElement object.

String is 1 to 7 characters.

Node full name when this option is absent

-b Displays both the short name and the full name of the node in the userLabel attribute of the managedElement object, with the format:

<full name>’<short name>

String is 23 characters, where the full name is 15 characters, the short name is 7 characters, and the delimiter (‘) is 1 character.

Node full name when this option is absent

-ncci CE_agent Enables the process to create a new record of the NCCI root in the 5620 NM database.

When this option is not present, then SPVC paths creation with an NCCI root not already in the 5620 NM database fails.

None — None



(2 of 3)



Notes(1) An atomic set refers to a CMIP set command that changes the value of an unlocked groomed circuit’s bandwidth; it results

in the groomed circuit being disconnected and then reconnected with its new bandwidth.(2) The -Z option requires that the CE_agent, CE_chgsrv, and CE_reload processes must be confugured with the same value

for the option. If CE_agent is configured wothout the -Z option, CE_chgsrv and CE_reload must akso be configured without the option.

-Proc CE_reload Specifies the number of reload clients the process will spawn during a full reload.

cpu_num: up to the number of CPUs available

Number of CPUs to use for the process

1

-Z (2) CE_reload, CE_chgsrv, CE_agent and CE_reload

Supports port numbering from 0. Some nodes use 0 for the first port number, instead of the default 1. When the -Z option is used, the processes will check for 0 port numbering.

None — None



(3 of 3)


System administration

9 — MIB management

10 — CE MIB tool

11 — The 5620 CMIP security module



9.1 The 5620 CMIP MIB 9-2

9.2 Deleting and reloading the MIB 9-2

9.3 Backing up the MIB 9-2

9.4 Restoring the MIB 9-4



9.1 The 5620 CMIP MIB

The 5620 CMIP MIB is a TMF-based database that uses managed objects to model the components of the network. If the MIB is empty when the 5620 CMIP starts up, it is automatically loaded from the database of the 5620 NM when communication is established.

Database synchronization

When a change is made in the network, the 5620 NM updates its database and informs the 5620 CMIP. The 5620 CMIP updates the objects in the MIB and keeps the MIB in synchronization with the 5620 NM database.

The MIB can, however, become out of synchronization with the 5620 NM database under the following conditions:

• the 5620 CMIP is stopped and the CE change server queue overflows• the communication link between the 5620 CMIP and the 5620 NM is down and

the CE change server queue overflows and cannot fully update the MIB once the communication link is restored

• there are network changes during an activity switch between the active and standby 5620 NM NetworkStations in a 5620 NM redundancy configuration

In these conditions, the 5620 CMIP OSS Interface Gateway passes event reports to inform the OSS that the MIB might be out of synchronization with the database.

To bring the MIB back into synchronization with the database, perform a reload on the MIB. Changes made in the network while the MIB is being reloaded are recorded in the CE change server queue. When the reload is finished, the 5620 CMIP automatically updates the MIB according to the contents of the CE change server queue. The CE change server queue is part of the CE_chgsrv process on the NetworkStation. See section 8.3 for information about the CE_chgsrv process.

9.2 Deleting and reloading the MIB

See chapter 10 for information about deleting and reloading the MIB.

9.3 Backing up the MIB

We recommend backing up the MIB to a backup directory so that, if the MIB becomes corrupted, the backup MIB can be used to restore the MIB. For example, the MIB could become corrupted if the 5620 CMIP is shut down through a forced boot or a hazardous failure. See section 9.4 for information about restoring the MIB.



Procedure 9-1 To back up the MIB

1 As root in the Gateway Station, change to the 5620 CMIP database directory by typing:

cd /opt/netmgt/conexec/db/bin ↵

2 Back up the MIB by typing:

CE_control mib-backup [-d backup_dir] [-c[-o file_name]]

where

backup_dir is the directory to which you are backing up the MIB

file_name is the name of the compressed MIB

Table 9-2 describes the command parameters.

Table 9-1 mib-backup command parameters

Procedure 9-2 To export the MIB

Note 1 — The 5620 CMIP database must be running to perform this procedure.

Note 2 — The backup directory must exist before performing this procedure.

Note 3 — The CE_control mib-backup command saves a copy of the MIB in a backup file that can be recovered using the CE_control mib-restore command.

Parameter Description Default

-d The absolute path to the backup directory where the MIB will be backed up

/opt/netmgt/conexec/db/backup

-c The MIB backup will be compressed inside the backup directory

None

-o The name of the compressed MIB cedb.backup.tar.Z

Note 1 — The CE_driver and CE_mibmgr process must be shut down, and the 5620 CMIP database must be running to perform this procedure. See section 5.2 for more information about stopping and starting 5620 CMIP processes.

Note 2 — The export directory must exist before performing this procedure.

Note 3 — The CE_control mib-export command saves a copy of the MIB in an export file that can be recovered using the CE_control mib-import command.



1 As root in the Gateway Station, change to the 5620 CMIP database directory by typing:

cd /opt/netmgt/conexec/db/bin ↵

2 Export the MIB by typing:

CE_control mib-export [-d export_dir] [-c[-o file_name]]

where

export_dir is the directory to which you are exporting the MIB

file_name is the name of the compressed MIB


Table 9-2 mib-export command parameters

9.4 Restoring the MIB

It is possible for the MIB to become corrupted. For example, the MIB could become corrupted if the 5620 CMIP is shut down through a forced boot or a hazardous failure. In the event of MIB corruption, the backup MIB can be used to restore the MIB. See section 9.3 for information about backing up the MIB.

Procedure 9-3 To restore the MIB

1 As root on the Gateway Station, change to the 5620 CMIP directory by typing:

cd /opt/netmgmt/conexec/db/bin ↵


-d The absolute path to the export directory where the MIB will be exported to


-c The MIB export will be compressed inside the export directory

None

-o The name of the compressed MIB cedb.exp.tar.Z

Note 1 — The 5620 CMIP database must be running to perform this procedure.

Note 2 — The restore directory must exist before performing this procedure.

Note 3 — The CE_control mib-restore command recovers the MIB from a backup file saved using the CE_control mib-backup command.



2 Restore the MIB by typing:

CE_control mib-restore [-d restore_dir] [-c [-i file_name]] ↵

where

restore_dir is the directory where the MIB to be restored is located

file_name is the name of the compressed MIB backup file


Table 9-3 mib-restore command parameters

Procedure 9-4 To import the MIB

1 As root on the Gateway Station, change to the 5620 CMIP directory by typing:

cd /opt/netmgmt/conexec/db/bin ↵

2 Import the MIB by typing:

CE_control mib-import [-d import_dir] [-c [-i file_name]] ↵

where

import_dir is the directory where the MIB to be imported is located

file_name is the name of the compressed MIB export file



-d The absolute path to the directory where the MIB will be restored from


-c The MIB is compressed inside the restore directory None

-o The name of the compressed MIB cedb.backup.tar.Z

Note 1 — The CE_driver and CE_mibmgr process must be shut down, and the 5620 CMIP database must be running to perform this procedure. See section 5.2 for more information about stopping and starting 5620 CMIP processes.

Note 2 — The import directory must exist before performing this procedure.

Note 3 — The CE_control mib-import command recovers the MIB from an export file saved using the CE_control mib-export command.



Table 9-4 mib-import command parameters


-d The absolute path to the directory where the MIB will be imported from


-c The MIB export is compressed inside the import directory

None

-o The name of the compressed MIB cedb.exp.tar.Z


10 — CE MIB tool

10.1 CE MIB tool 10-2

10.2 Running CE MIB tool commands 10-4

10 — CE MIB tool


10.1 CE MIB tool

An operator can use the CE MIB tool to audit, syncstatus, reload, delete, count, import, or export the 5620 CMIP MIB. The CE MIB tool commands are the following:

The MIB audit commandThe MIB audit command performs an audit on the 5620 CMIP MIB by:

• retrieving a list of object identifiers from the 5620 NM database• comparing the object identifiers from the 5620 NM database to object identifiers

in the 5620 CMIP MIB• writing discrepancies to a file

A MIB audit can only retrieve the following types of 5620 CMIP object identifiers from the 5620 NM database:

• connectionId—identifies an instance of a bMFacility object class• trailId—identifies a bMGroomedCircuit object by mapping onto the call Id of the

5620 NM NetworkStation• managedElementId—identifies an instance of a managedElement object

If a MIB audit finds discrepancies by comparing selected object identifiers in the 5620 NM database to selected object identifiers in the 5620 CMIP MIB, then the MIB is out of sync. To put the MIB back in sync, an operator can use the MIB sync command.

• MIB audit• MIB sync• MIB reload• MIB delete• MIB size• MIB count

• MIB syncstatus• MIB export• MIB import• MIB backup• MIB restore• MIB status

Note — The MIB sync command affects OSS access to the 5620 CMIP. See “The MIB sync command” section for more information.

Note — A MIB audit only reports object identifiers that are present in the 5620 NM database but are not present in the 5620 CMIP MIB.

10 — CE MIB tool


The MIB sync commandThe MIB sync command reloads selected objects in the 5620 CMIP MIB. When an operator initiates a MIB sync, the following events occur:

• the 5620 CMIP sends an alarm to the OSS stating that the system is about to begin a MIB sync

• CE_chgsrv maintains the queue of events from the 5620 NM but does not send events to the CE_driver until the CE_driver completes the MIB sync

• the 5620 CMIP icon on the 5620 NM NetworkStation changes to yellow; the 5620 CMIP status is online and CE_reload is busy

• CE_driver enters no access mode (no operations and no connections)• the 5620 CMIP disconnects any connected OSSs

When the 5620 CMIP completes a MIB sync, the following events occur:

• the 5620 CMIP icon on the 5620 NM NetworkStation changes to green • CE_driver returns to full access• if an agent-initiated association is established, the 5620 CMIP sends an alarm to

the OSS stating that the system has completed a MIB sync; otherwise, the OSS does not receive the alarm

The MIB reload commandThe MIB reload command efficiently removes the 5620 CMIP database and issues a full reload.

If CE_driver is running when an operator initiates a MIB reload, the 5620 CMIP performs a warmstop on the CE_driver, empties the CE_chgsrv queue, deletes the MIB, restarts the CE_driver, and performs a full reload.

If CE_driver is not running when an operator initiates a MIB reload, the 5620 CMIP deletes the MIB. When the operator starts up CE_driver, the 5620 CMIP performs a full reload.

The MIB delete commandThe MIB delete command efficiently removes the 5620 CMIP database.

When the CE_driver is not running and an operator initiates a MIB delete, the 5620 CMIP deletes the MIB. When the operator starts up CE_driver, the 5620 CMIP performs a full reload.

Note — A disconnected OSS is responsible for reestablishing a connection, unless an agent-initiated association has been established. See section 7.4 for more information about association management.

Note — You cannot perform a MIB delete if CE_driver is running.

10 — CE MIB tool


The MIB size commandThe MIB size command reports the size of the 5620 CMIP database. When the MIB size command is executed, a message appears displaying the total size, used size and available size of the database in Mb, as well as the percentages of the database sizes.

The MIB count commandThe MIB count command reports the number of objects for each object class in the 5620 CMIP database.

The MIB status commandThe MIB status command reports the status of the 5620 CMIP database. When the MIB status command is executed, the following message is displayed:

The CE MIB database server is status.

where status is Up, Down, or Initializing.

The MIB export commandThe MIB export command exports the 5620 CMIP database to a specified directory for backup purposes.

The MIB import commandThe MIB import command restores the 5620 CMIP database from a previously exported backup file.

The MIB backup commandThe MIB backup command saves the 5620 CMIP database to a specified directory, without stopping the CE_driver and CE_mibmgr processes.

The MIB restore commandThe MIB restore command restores the 5620 CMIP database from a previous backup.

10.2 Running CE MIB tool commands

An operator initiates CE MIB tool commands from the CE_control interface. With the MIB audit and MIB sync commands, CE_driver sends the requests to the CE_reload process on the 5620 NM NetworkStation.

Procedures 10-1 to 10-5 describe how to manually run MIB tool commands through the CE_control interface. See Chapter 9 for more information about backing-up and restoring the 5620 CMIP database.

10 — CE MIB tool


Procedure 10-1 Manually running a MIB audit, a MIB sync, or a MIB syncstatus

1 Log in as root.

2 Change to the 5620 CMIP directory by typing:


3 Perform one of the following commands.

a To initiate a MIB audit, type:

CE_control mib-audit -class list of objectClasses [-file [filename]] ↵

b To initiate a full reload for selected objects, run a MIB sync by typing:

CE_control mib-sync (-class list of objectClasses -id ids) | (-file [filename]) ↵

c To initiate a reload of the status of selected objects, run a MIB syncstatus by typing:

CE_control mib-syncstatus (-class list of objectClasses -id ids) | (-file [filename]) ↵

If you only type the first argument, such as mib-audit or mib-sync, you will receive a usage message.

Options for list of objectClasses

The list of objectClasses argument identifies which objectClasses will be audited or synced. The objectClasses are separated by a space. The following objectClasses are accepted:

• all, ALL• mEl, mElem, managedElement• bMGC, bMGroomedCircuit• bMF, bMFac, bMFacility

• bMF:cable, cable

• bMF:vpcl, vpcl

• bMF:vccl, vccl• bMF:frl, frl

• bMF:mfrl, mfrl

• bMF:psnl, psnl• bMF:imal, imal

10 — CE MIB tool


When you initiate a MIB audit, you must specify -class list of objectClasses. When you initiate a MIB sync or a MIB syncstatus, you must specify -class list of objectClasses only if you do not specify -file.

Options for ids

The ids argument is a list of object Ids or object Id ranges. Separate individual Ids and Id ranges with a comma. Specify Id ranges from low to high and separate them with a dash.

When you initiate a MIB sync or a MIB syncstatus, you must specify -id ids only if you do not specify -file.

Options for filename

For a MIB audit, filename is the name of the file where a MIB audit writes audit results. For a MIB sync, filename is the name of the file that a MIB sync uses to determine which objects require reloading.

The audit report file is created in /opt/netmgt/conexec/logs. If you do not specify a filename, the 5620 CMIP names the file CE_audit.report. If you specify a filename, it must be a valid filename that can be created as /opt/netmgt/conexec/logs/filename.

The operator is responsible for removing audit report files between runs. To remove a file, use the rm command.

Note — The all objectClass represents all supported objectClasses.

The bMFacility objectClass represents the following facility types: physical links, VPC links, frame relay links, MFR links, PSN links, and IMA links.

• The bMF:cable and cable objectClasses only reload physical links.• The bMF:vpcl and vpcl objectClasses only reload VPC links• The bMF:frl and frl objectClasses only reload frame relay links• The bMF:vccl and vccl objectClasses only reload VCC links.• The bMF:mfrl and mfrl objectClasses only reload MFR links• The bMF:psnl and psnl objectClasses only reload PSN links.• The bMF:imal and imal objectClasses only reload IMA links.

Note — When the 5620 CMIP completes a MIB audit, the audit report file receives a “# Audit Complete” message.

10 — CE MIB tool


The following example describes possible audit report file contents. The # character is for comments.

# Audit Started: date as: month/day hh:mm:ss.ms

# The following objects were not found in CE MIB

# objectClass -idid of missing object

managedElement -id 4

bMF:cable -id "Cable: 3"

bMGroomedCircuit -id "5"

bMF:vpcl -id "ATM Link: 7"

bMF:frl -id "FRL: 6"

bMF:mfrl -id "FRL: 8"

...

# Audit Complete

Procedure 10-2 Manually running a MIB reload

1 Log in as root.



3 To initiate a MIB reload, type:

CE_control mib-reload ↵

Procedure 10-3 Manually running a MIB delete

1 Log in as root.



3 Stop the CE_driver by typing:

CE_control warmstop ↵

10 — CE MIB tool


4 To initiate a MIB delete, type:

CE_control mib-delete -del mib ↵

Procedure 10-4 To determine the size of the MIB

1 As root, change to the 5620 CMIP directory by typing:


2 Initiate the mib-size command by typing:

CE_control mib-size ↵

A message displaying information on the size of the MIB appears.

Procedure 10-5 To report on the number of objects in the MIB



2 Perform the mib-count command by typing:

CE_control mib-count ↵

A report of the number of objects for each object class appears.

Procedure 10-6 To report on the status of the 5620 CMIP database server



2 Perform the mib-status command by typing:

CE_control mib-status ↵

A message stating the status of the database server is displayed.



11.1 Security file 11-2

11.2 OSS access privilege verification 11-5

11.3 Security module commands 11-5



11.1 Security file

The 5620 CMIP system administrator enters and controls security permissions for each OSS. The 5620 CMIP security module identifies associations using a numerical OID derived from the AP-title and determines OSS access from the permissions listed in the security file.

Maintaining the security file

The 5620 CMIP security information is stored in the CE_security.conf file located in the /opt/netmgt/conexec/bin directory. This file contains the security access list in text format. The 5620 CMIP administrator can edit this file using any text editor.

The CE_security.conf file contains the OSS AP-Titles, network permissions and optional OSI presentation addresses. Each line must have the following format:

OSS_AP-Title OSS_Permission [OSS_OSI_Address: NSAP PSEL SSEL [TSEL]]

Table 11-1 shows sample CE_security.conf file entries.

Table 11-1 Example CE_security.conf entries

Notes(1) The NSAP value of 0x08002082F49C01 is based on the sample hexadecimal value of the OSS Ethernet address

(8:0:20:82:F4:9C). This value will change from machine to machine.(2) The NSAP value of 0x8A788826 is based on the sample hexadecimal value of the OSS IP address (138.120.136.38).

Note — If an error is detected while reading the security file on initial startup, the 5620 CMIP restarts and attempts to read the security file again. This process is repeated until the security file is read successfully.

Note — The OSI presentation address is optional in the CE_security.conf file. An OSI presentation address must be entered to configure automatic association.

OSS AP-Title

Network permission

Sample OSI presentation address Description

* READ — Undefined OSSs

1:2:3:4:1 READ/ WRITE

— No OSI presentation address

1:2:3:4:2 NONE 0x08002082F49C01 aPs aSs aTs (1) OSS with OSI presentation address

1:2:3:4:3 READ 0x8A788826 tPs tSs (2) OSS with OSI presentation address using RFC 1006



OSS AP-Title

The OSS AP-Title can be represented by either a numerical OID or an asterisk “*” (wildcard). An asterisk “*” in the OSS column signifies “all other application entities”. If an asterisk “*” is entered to represent the OSS AP-Title, an OSI presentation address cannot be entered.

Network permission

The network permission determines what type of access an OSS has to the 5620 CMIP. There are three types of permissions:

• NONE• READ• READ/WRITE

Table 11-2 lists network access permissions for different associations.

Table 11-2 Network access permissions

Notes(1) Read = Get, Event report(2) Write = Create, Delete, Set, Action(3) Write = Create, Delete, Set on eFD and log objects

An asterisk “*” is invalid in the permission parameter and is flagged as a file format error.

The default file contains one entry with an OSS AP-Title of “*” and READ/WRITE permission. In a customized security file, if there is no entry where the OSS AP-Title is specified as “*”, then a permission of NONE is assigned for all associations where the OSS AP-Title that is used does not appear explicitly in the CE_security.conf file.

Note 1 — We strongly recommend that you do not use a wildcard in a production environment.

Note 2 — Each AP-Title must be uniquely configured with OSI by changing the selector values. See Table 11-3 for more information.

Access Network permissions

NONE READ READ/WRITE

Association ✓ ✓

Network objects Read (1) ✓ ✓

Write (2) ✓

System objects Read (1) ✓ ✓

Write (3) ✓ ✓

Test objects Read (1) ✓ ✓

Write (2) ✓



OSI presentation address

The OSI presentation address is an optional entry in the CE_security.conf file. The 5620 CMIP uses the OSI presentation address of the OSS to create an automatic association with the OSS to forward event reports. The 5620 CMIP cannot create an automatic association if an asterisk was entered to represent the OSS AP-Title.

Table 11-3 describes the information the 5620 CMIP administrator must enter into the CE_security.conf file to properly configure the OSI presentation address.

Table 11-3 OSI presentation address information

Notes(1) TSEL is absent when RFC 1006 is being used.(2) The NSAP value of 0x08002082F49C01 is based on the sample hexadecimal value of the OSS Ethernet MAC address

(8:0:20:82:F4:9C). This value will change from machine to machine.(3) The NSAP value of 0x8A788826 is based on the sample hexadecimal value of the OSS IP address (138.120.136.38).

Adding entries to the security file dynamically

The 5620 CMIP security module enables the administrator to add OSSs to the access list while the system is running.

When changes have been made to the security file, the administrator can instruct the 5620 CMIP to update the security information. The CE_control security-read command is used to reload security information. If an error occurs while reading the security file, the old security values are used. An error message is displayed to the 5620 CMIP system administrator.

See Table 11-4 for information about the 5620 CMIP security module commands.

When the updated security information is loaded, the 5620 CMIP security module verifies that all connected OSSs still have sufficient privileges. If the administrator has removed all privileges for a connected OSS, the security module aborts the association to the 5620 CMIP immediately. A message is then sent to the 5620 CMIP system administrator identifying terminated OSSs.

Environment variable

Description Sample full OSI stack value

Sample RFC 1006 value

PSEL Presentation selector tPs tPs

SSEL Session selector tSs tSs

TSEL Transport selector tTs (1)

NSAP Network service address parameter

0x08002082F49C01 (2) 0x8A788826 (3)

Note — No message is sent to the OSS upon termination due to insufficient access privileges.



11.2 OSS access privilege verification

This section describes the procedures that the 5620 CMIP security system uses to verify OSS access to the 5620 CMIP.

Screening OSS requests

When an OSS requests an association, the 5620 CMIP determines if the requesting OSS has access privileges to the system. If the OSS does not have access privileges, access is denied.

When an association has been established between the 5620 CMIP and the OSS, the 5620 CMIP verifies that the OSS has sufficient privileges to perform the requested CMIP operations. If the OSS has insufficient privileges, the CMIP operation requests are denied.

Restricting access during critical processing

Because it requires information to remain unchanged, the 5620 CMIP OSS Interface Gateway enters into a restricted access mode during the following operations:

• full reload• while reestablishing an association to the 5620 NM• persistence reload

The 5620 CMIP administrator can also place the system in restricted access mode using the CE_control security-suspend command. Normal access mode can be restored by using the CE_control security-resume command.

See Table 11-4 for information about the 5620 CMIP security module commands.

11.3 Security module commands

The 5620 CMIP security module contains five commands that the system administrator can use. These commands are:

• CE_control security-read • CE_control security-resume • CE_control security-status • CE_control security-suspend • CE_control security-connected

Table 11-4 describes the security module commands.



Table 11-4 Security module subcommands

Note(1) Subcommand is in the form CE-control subcommand, where subcommand is one of the listed selections.

Procedure 11-1 Sample security module subcommand


su root ↵



CE_control security-read option(s)↵

See Table 4-2 for more information about the 5620 CMIP process ELS message options.

CE_control subcommands (1)

Description

security-read Rereads the security file, causing immediate action with respect to changes in access privileges

All OSSs that have changes to their access privileges, where the access privileges are reduced to none, are immediately disconnected.

security-resume Resumes normal security operational mode

security-status Gets the current status of the security module

security-suspend Places the 5620 CMIP into restricted access mode, forcing the security module to enter read-only mode

security-connected Lists all of the current OSS associations


Operations overview

12 — Network object modeling

13 — Path management

14 — Link management

15 — Alcatel 7390 NT management

16 — Maintenance and diagnostics

17 — Event and alarm management

18 — Statistics activation and control

19 — Interaction sequences



12.1 Modeling overview 12-2

12.2 Network managed objects 12-2

12.3 Object modeling examples 12-5



12.1 Modeling overview

Table 12-1 shows how the 5620 CMIP managed objects map to network equipment and resources.

Table 12-1 Managed objects-to-network equipment mapping

See section 20.4 for additional information about modeling managed objects.

12.2 Network managed objects

This section provides examples of how TDM, frame relay, and ATM network objects are modeled in the MIB.

bMFacility object

Instances of the bMFacility object model the physical links, such as T1, and logical links, such as frame relay or ATM VPC. Figure 12-1 shows how the a-TPInstance and z-TPInstance attribute values of the bMFacility object point to instances of managedFacilityTP objects as A and Z endpoints. See chapter 23 for detailed information about the bMFacility object.

5620 CMIP managed object Network equipment

bMFacility Physical links, such as T1 links, and logical links, such as frame relay links

managedFacilityTP Physical link endpoints, such as T1 ports, and logical link endpoints, such as ATM VPC endpoints

bMGroomedCircuit TDM, frame relay, and ATM paths

managedGroomedCircuitTP Path endpoints, such as DS0s

managedElement Nodes, such as 7470 MSP nodes and 5620 CMIP Gateway Stations

elementExtensions Does not map to any physical object. Contains additional node information.

equipmentHolder Shelves, card slots, power supply slots, and fan slots

managedPack Cards, such as DNIC cards

managedEquipment Nonendpoint network resources, such as DSP resources

managedProfile 5620 NM profiles, such as TCA, SLP, and ASAM

network 5620 NM-managed network and 5620 NM partition



Figure 12-1 bMFacility modeling in the MIB

managedFacilityTP object

Instances of the managedFacilityTP object model the physical link endpoints, such as T1 or E1 ports, and logical link endpoints, such as frame relay link endpoints or ATM VPC link endpoints. See chapter 34 for detailed information about the managedFacilityTP object.

bMGroomedCircuit object

Instances of the bMGroomedCircuit object model the network paths, such as TDM circuits, frame relay paths, and ATM VCC paths. Figure 12-2 shows how the a-TPInstance and z-TPInstance attribute values of the bMGroomedCircuit object point to instances of managedGroomedCircuitTP objects as A and Z endpoints. See chapter 24 for detailed information about the bMGroomedCircuit object.

Figure 12-2 bMGroomedCircuit modeling in the MIB

managedGroomedCircuitTP object

Instances of the managedGroomedCircuitTP object model the path endpoints, such as DS0s on TDM paths and OC3 ports on ATM VCC paths. See chapter 35 for detailed information about the managedGroomedCircuitTP object.

13332

bMFacility

managedFacilityTP managedFacilityTP

a-TPInstance z-TPInstance

8820

bMGroomedCircuit

managedGroomedCircuitTP managedGroomedCircuitTP

a-TPInstance z-TPInstance



managedElement object

Instances of the managedElement object model the physical 5620 NM-managed nodes, such as the 7470 MSP, and 7670 RSP, 5620 CMIP Gateway Stations, 5620 NM NetworkStations, and element-managed nodes, such as the 7300 ASAM. See chapter 32 for detailed information about the managedElement object.

elementExtentions object

Instances of the elementExtensions object contain information specific to 7390 NT commisioning and do not model any physical equipment. See chapter 26 for detailed information about the elementExtensions object.

equipmentHolder object

Instances of the equipmentHolder object model the shelves, card slots, power supply slots, and fan slots. See chapter 27 for detailed information about the equipmentHolder object.

managedPack object

Instances of the managedPack object model the cards, such as T1 and OC3, power supplies, and fans. See chapter 36 for detailed information about the managedPack object.

managedEquipment object

Instances of the managedEquipment object model the nonendpoint network resources, such as DSP resources and FASTbus ports, that are not modeled by the managedElement and managedPack objects, such as HCV and ADPCM. See chapter 33 for detailed information about the managedEquipment object.

managedProfile object

Instances of the managedProfile object model path or logical link configuration profiles, such as TCA, SLP, and ASAM profiles. See chapter 37 for detailed information about the managedProfile object.

network object

Instances of network objects can:

• model a 5620 NM-managed network • model a 5620 NM-managed network partition • contain other objects relating to network configuration

A network object identifies the name of the network or the partition from which the network resources are drawn. See chapter 38 for detailed information about the network object.



12.3 Object modeling examples

Figure 12-3 shows how managed objects can model a TDM node, such as the 3600 MSS.

Figure 12-3 Object modeling of a 3600 MSS node

Figure 12-4 shows how managed objects can model an ATM node, such as the 7470 MSP.

10797

Fan PS

3600 MSS

Shelf

Slot

DS-3 Card

DS-3 Port DS-3 PortDS-3 Port DS-3 Port

Slot

DS-3 Card

DS-3 Cable

managedGroomedCircuitTP

equipmentHolder

managedElement

managedFacilityTP

managedPack

Cross-connects

X

X

X

X

DS1-1

DS1-n

DS1-28DS1-28

DS1-1

DS1-n

DS1-1

DS1-n

DS1-28DS1-28

DS1-1

DS1-n

bMFacility bMFacility

DS-3 Cable

to CPE to the network



Figure 12-4 Object modeling of a 7470 MSP node

15340

7470 MSP Node

Shelf

Slot

DS3 Card

DS3 Port OC3 PortOC3 PortDS3 Port

Slot

OC3 Card

managedFacilityTP (physical link endpoint)

managedPack

Cross-connects

VCC Path

VCC Path

bMFacility(DS3 Cable)

bMFacility(OC3 Cable)

bMFacility(ATM VPC Link)

bMFacility(ATM VPC Link)

VPC LinkDS3 Cable

XX

XXOC3 CableVPC Link

Fan PS

equipmentHolder

managedElement



13.1 Overview 13-2

13.2 Path states 13-2

13.3 Creating paths 13-4

13.4 SPVC-interworking paths 13-7

13.5 Creating resource links 13-8

13.6 Connecting paths 13-9

13.7 Disconnecting paths 13-11

13.8 Configuring bMGroomedCircuit object attributes 13-11

13.9 Deleting paths 13-11

13.10 Path maintenance 13-12

13.11 Path recovery 13-13



13.1 Overview

Paths on the 5620 NM are modeled as bMGroomedCircuit objects in the 5620 CMIP. An OSS application can use CMIS services to request the 5620 CMIP to perform management operations on paths, frame relay links, and ATM logical links. CMIS service requests result in the OSS issuing corresponding CMIP operations to the 5620 CMIP. The 5620 CMIP will accept these messages as CMIP indication messages. An OSS application can request that the 5620 CMIP:

• create paths (M-CREATE) • retrieve configuration data for paths (M-GET)• configure paths (M-SET)• connect paths (M-SET)• trace path topology (M-ACTION)• groom (optimize) path topology (M-ACTION)• disconnect paths (M-SET)• delete paths (M-DELETE)• list paths using the listPaths action, as described in chapter 29

Path-endsAll path-ends that are valid for the 5620 NM are valid for the 5620 CMIP, with the exception of primary subrate path-ends.

Examples of valid path-ends are:

• voice ports• data ports• primary rate DS0s, including super-rate• ATM ports• MJUs

See the 5620 Network Manager User Guide chapters on paths for information about valid path-ends.

13.2 Path states

To better understand the 5620 CMIP path states, you must understand how the 5620 NM models path states. See Table 13-1 for details about how the 5620 CMIP models 5620 NM path states and transitions.

The following events model changes to 5620 NM path states:

• administrativeState stateChange• operationalState stateChange• currentProblemList attributeValueChange• communicationsAlarm



The bMGroomedCircuit object models 5620 NM path status using the following attributes:

• administrativeState• operationalState• currentProblemList

Figure 13-1 describes 5620 NM path states and the transitions between them.

Figure 13-1 5620 NM path state diagram

Table 13-1 lists common 5620 NM path states—the administrativeState, operationalState, and the corresponding path bandwidth allocation.

fault removed &path searchsucceeds

CONNECT [5]& path search

succeeds

faultremoved

path fault& path searchnot performed [4]

NCI Connectto nodes

succeeds [2]

path searchfailed [3]

path searchsucceeds

path searchsucceeds

path fault &path search performed

NEW PATH [1] PATH DELETE [7]

CR

CON

fault removed &path search failed [3]

UPLOAD(NMTI)

RR

WFRp

faultremains

faultremains

pathsearchfailed

NCI Disconnectto nodessucceeds

DR

WFRe

CONNECT &path search

failed [3]

DISCONNECT[6]

DISCONNECT[6]

CD - Connected DownCR - Connect RequestedCON - ConnectedDR - Disconnect RequestedRFC - Ready for ConnectRR - Reroute RequestedWFRe - Waiting for ResourcesWFRp - Waiting for Repair

- 5620 NM operator or OSS requests NEW PATH- The following events are sent to 5620 CMIP: administrativeState stateChange, operationalState stateChange, currentProblemList attributeValueChange, communicationsAlarm- The following events are sent to 5620 CMIP: communicationsAlarm, currentProblemList attributeValueChange- Path search not possible if path is feeder, fault on endpoint, or reroute disabled; the following events are sent to 5620 CMIP: operationalState stateChange, currentProblemList attributeValueChange, communicationsAlarm- 5620 NM operator or OSS requests path connect- 5620 NM operator or OSS requests path disconnect- 5620 NM operator or OSS requests path delete- 5620 NM operator or OSS requests optimize "grooming"

[1][2] [3][4] [5] [6] [7][8]

15359

CD

NCI Connectto nodes failed

OPTIMIZE[8]

RFC



As the path changes from state to state, alarm set and clear messages are emitted. Table 24-3 lists the 5620 CMIP alarms and the status of the path when that alarm is emitted.

Table 13-1 bMGroomedCircuit path states and bandwidth allocation

Note(1) See Table 24-3 for more information about each path state.

13.3 Creating paths

To create a valid bMGroomedCircuit, the OSS must send a bMGroomedCircuit M-CREATE request. See section 24.4 for information about the attributes of the bMGroomedCircuit object.

For every transmission technology type, the M-CREATE operation for a bMGroomedCircuit object must:

• specify the distinguishedName of the second level network object (superior object instance naming)

• include required attribute values; see Table 13-2

Table 13-2 bMGroomedCircuit create operation required attributes

5620 NM path state acronym

5620 NM path state (1) 5620 CMIP administrativeState

5620 CMIP operationalState

Path bandwidth

CD “Connected down” unlocked disabled allocated

CON “Connected” unlocked enabled allocated

CR “Connect requested” unlocked enabled being allocated

DR “Disconnect requested” locked enabled being deallocated

RFC “Ready for connect” locked enabled not allocated

RR “Reroute requested” unlocked enabled being reallocated

WFRe “Waiting for resources” unlocked disabled not allocated

WFRp “Waiting for repair” unlocked disabled not allocated

Note — SPVC-interworking and resource link M-CREATE operations require unique attribute values. See sections 13.4 and 13.5 for more information.

Attribute (1) Description

a-TPInstance and z-TPInstance

Refers to the managedGroomedCircuitTP object at each end of the bMGroomedCircuit

circuitType Describes the mode and type of circuit

(1 of 2)



Note(1) The 5620 CMIP uses defaults for any attribute values that are not included with the create operation.

Figure 13-2 describes the sequence of events during an M-CREATE operation on a bMGroomedCircuit object and illustrates the flow of information between the OSS, the 5620 CMIP, and the 5620 NM as the M-CREATE operation is processed.

Figure 13-2 bMGroomedCircuit M-CREATE request

If the path does not need to be connected immediately, the M-CREATE operation can either omit the administrativeState attribute to accept the default value of locked or set the value to locked so that the 5620 NM path status is set to the “Ready for connect” state.

nameBinding Identifies the kind of name binding used by the bMGroomedCircuit object

objectClass Identifies the object as a bMGroomedCircuit


(2 of 2)

NEW PATH request YY

Y

NN

Y

N

N

return “trailId”

CONNECT request

return “path status”M-EVENT-REPORT“Connected”

[1] required only if M-CREATE (Argument) did not set adminState to “unlocked”

M-EVENT-REPORT“Object Create”

M-EVENT-REPORT“Object Create”

M-CREATE (Argument)

M-CREATE (Result)“invalid create req”

M-CREATE (Result)“valid create req” & “trailId”

M-CREATE (Result)“valid create req” & “trailId”

M-SET-REQadminState=”unlocked” [1]

return“Waiting for Resources”

or“Connected Down”

M-EVENT-REPORT“Waiting for Resources”

or“Connected Down”

validM-CREATE

validPath

request

adminState=unlocked?

CONNECTsucceeded

15341

OSS 5620 CMIP 5620 NM



If the M-CREATE operation includes an administrativeState attribute value of unlocked, the 5620 NM path status will be “Connect requested” and the 5620 NM attempts to connect the path when it creates the bMGroomedCircuit object.

When the 5620 CMIP receives an M-CREATE operation, it passes the request to the 5620 NM. If this validation fails or if the 5620 NM cannot create the path object in its database, the 5620 CMIP returns an error response to the OSS.

If the validation succeeds and if the administrativeState was not specified, or if it was specified as locked, the 5620 NM creates the path in its database in the “Ready for connect” state. The 5620 CMIP does the following:

• sends a CMIP M-CREATE response to the OSS• sets the administrativeState attribute value to locked• sets the operationalState attribute value to enabled• emits an objectCreation M-EVENT REPORT notification• sets the currentProblemList (see Table 13-1)• emits a communicationsAlarm

Automatic path-end assignment

When the OSS application requests the creation of a bMGroomedCircuit object instance, the path-ends—a-TPInstance and z-TPInstance attributes—must usually be present. These attributes point to instances of managedGroomedCircuitTP objects. See Figure 12-2 for an illustration of this relationship.

The 5620 CMIP supports automatic path-end assignment for primary rate ports: T1, E1, T3, or E3. When the OSS specifies a managedFacilityTP object instance as either the a-TPInstance or z-TPInstance attribute values, the 5620 CMIP finds the first available time slot on the port and assigns this to the a-TPInstance or z-TPInstance attribute.

Unique naming for paths and logical links

The 5620 NM can be configured to ensure that each path or logical link has a unique name in the 5620 NM database. When enabled, the unique naming feature of the 5620 NM checks to make sure that all paths and logical links being created, including those created by the 5620 CMIP, have a unique name in the 5620 NM database. If the feature is enabled and the OSS attempts to create a path or logical link with a duplicate name, the 5620 CMIP will fail the operation.

The unique naming feature can be enabled or disabled on the 5620 NM through the unique call option of NW_config; the default is disabled. This feature cannot be enabled or disabled through the 5620 CMIP.

See the 5620 NM Advanced Configuration Procedures guide for information about enabling the unique naming feature.



13.4 SPVC-interworking paths

Using AESA, an ATM-addressing scheme, SPVC-interworking allows for SPVC paths to be created in a network where there are third-party nodes. These nodes could be at the source end of the SPVC, destination end of the SPVC, or in the core network. On an SPVC-interworking path managed by the 5620 CMIP:

• all nodes must support AESA• a 7270 MSC, 7350 ASAM, 7470 MSP, or 7670 RSP node must be at either the

source end or the destination end of the path

Configuration methodsWith SPVC-interworking, there are two possible configuration methods: source-only configuration and dual-endpoint configuration.

With a source-only configuration, the configuration information required by the destination is passed by the source during the call set-up phase.

With a dual-endpoint configuration, the destination is configured prior to the source being requested to set-up a call. To support a dual-endpoint configuration, a 5620 NM-managed node must be at the destination end of the path.

Endpoint modelingWith SPVC-interworking, there are two possible endpoint models: physical and logical.

A physical model for the endpoint specifies the distinguished name of the managedGroomedCircuitTP object (TPInstance).

A logical model for the endpoint specifies the AESA address instead of the TPInstance. See Table 24-7 for a detailed description of an AESA address.

Creating SPVC-interworking pathsTable 13-3 lists the required attributes for create requests/replies in SPVC-interworking. The logical model is also possible if endpoint Z is logical and endpoint A is physical.

Table 13-3 Required attributes for create requests/replies in SPVC-interworking

bMGroomedCircuit attribute Physical modeling attribute values

Logical modeling attribute values (if endpoint A is logical)

aTMProfile (VC application) (1) SPVC

aTMProfile(srcSpecMethod) (2) Physical modeling Logical modeling

aTMProfile(dstSpecMethod) (3) Physical modeling

(1 of 2)



Notes(1) See Table 24-8, cpType 34 for more information.(2) See Table 24-8, cpType 118 for more information.(3) See Table 24-8, cpType 91 for more information.(4) See Table 24-7 for more information.

13.5 Creating resource links

Resource links are specialized links used to carry various types of information between nodes. Resource links include:

• ILMI links• PNNI links• signaling links

The procedure for creating a resource link using the 5620 CMIP is similar to the one for creating a path. Because a resource link and its associated VPC link share the same endpoints, a resource link, like a path, can only be created over an existing bMFacility VPC link. A bMGroomedCircuit object models a resource link.

For resource links, the M-CREATE operation for a bMGroomedCircuit object must:

• specify the distinguishedName of the superior object instance• include the required attributes (see Table 13-4)

aTMProfile(srcAESAAddr) (4) Request-not required; if present, must be correct

Reply-AESA address string for endpoint A if the configuration method is dual-endpoint

AESA address string for endpoint A

aTMProfile(dstAESAAddr) (4) Request-not required; if present, must be correct

Reply-AESA address string for endpoint Z if the configuration method is dual-endpoint

aTMProfile (NCCIRoot and NCCIIndex) (4)

Request-not required; if present, must be correct

Reply-NCCIRoot and NCCIIndex strings for endpoint Z if the configuration method is dual-endpoint

a-TPInstance TP Id for endpoint A Null

z-TPInstance TP Id for endpoint Z


nameBinding Identifies the kind of name binding used by the bMGroomedCircuit object


bMGroomedCircuit attribute Physical modeling attribute values

Logical modeling attribute values (if endpoint A is logical)

(2 of 2)



Table 13-4 Required attributes for resource link bMGroomedCircuit create operations

Notes(1) The 5620 CMIP uses defaults for attribute values that are not included with the create operation.(2) Table 24-8 describes these attributes.(3) These endpoints are identical to the endpoints of the associated bMFacility VPC link.

13.6 Connecting paths

To connect a path, the OSS must configure the administrativeState attribute of the bMGroomedCircuit to the value of unlocked. This may be accomplished either during a bMGroomedCircuit object M-CREATE request or by issuing an M-SET request for the bMGroomedCircuit object.

Connecting paths using the M-CREATE operationTables 13-2, 13-3, and 13-4 list the required attributes for a bMGroomedCircuit object M-CREATE request. To make a bMGroomedCircuit connect request, the M-CREATE request must also specify the administrativeState attribute as unlocked. Once the bMGroomedCircuit object is created, the administrativeState attribute is automatically set to unlocked—illustrated in Figure 13-2. The resulting 5620 NM path status is “Connect requested”. If the path connection cannot be made, the bMGroomedCircuit object remains.

Connecting paths using the M-SET operationThe CMIP M-SET operation is used as a connect request for a path. The M-SET operation must specify:

• the object instance of the bMGroomedCircuit object to be “Connected”• a value of unlocked for the administrativeState attribute


aTMProfile mandatory fields Provides the valid values for the mandatory fields of the aTMProfile attributes (2)

aTMProfile VC application Sets the type of VC application being created, such as signaling link, PNNI or ILMI

a-TPInstance

z-TPInstance

Refers to the managedGroomedCircuitTP object at each end of the bMGroomedCircuit (3)


nameBinding Identifies the kind of name binding used by a bMGroomedCircuit object


serverConnectionList Provides the name of the bMFacility VPCL supporting this bMGroomedCircuit object instance

Note — If the administrativeState attribute is set to locked in an M-CREATE operation, the bMGroomedCircuit object retains the 5620 NM path status of “Ready for connect”.



When the 5620 NM receives a path connection request from the 5620 CMIP, it:

• validates the request• allocates bandwidth for the path• changes the path status to “Connect requested”• informs the 5620 CMIP

If the validation fails or if the 5620 NM cannot process the request, it sends an error message to the 5620 CMIP, which in turn sends a CMIP error response to the OSS.

If the validation succeeds and the 5620 CMIP is informed that the 5620 NM path status is “Connect requested”, it changes the following attributes of the bMGroomedCircuit object:

• administrativeState to unlocked • operationalState to enabled

This indicates that a connection request is outstanding and no further configuration of the bMGroomedCircuit is allowed.

Connect successful

If the path connection succeeds, the 5620 NM changes the path status to “Connected” and the 5620 CMIP emits the following M-EVENT-REPORT notifications:

• operationalState stateChange• currentProblemList attributeValueChange• communicationsAlarm

See chapters 17 and 21 for more information about alarms.

Connect failed

If the 5620 NM does not succeed in connecting the path, it changes the path status to a fault condition and informs the 5620 CMIP, which then emits the following M-EVENT-REPORT notifications:


The administrativeState attribute value remains unlocked because the 5620 NM continuously attempts to connect the path.




13.7 Disconnecting paths

The CMIP M-SET operation is used as a disconnect request for a path that has a status of “Connected”, an administrativeState value of unlocked, or a fault condition. The M-SET operation must specify:

• the object instance of the bMGroomedCircuit object to be disconnected• a value of locked for the administrativeState attribute

When the 5620 NM receives the path disconnect request from the 5620 CMIP, it:

• changes the path status to “Disconnect requested”• changes the administrativeState attribute value to locked• informs the 5620 CMIP• disconnects the path from the network• frees up the bandwidth between the endpoints• changes the path status to “Ready for connect”

The 5620 CMIP then emits the following M-EVENT-REPORT notifications:

• administrativeState stateChange• currentProblemList attributeValueChange• communicationsAlarm


13.8 Configuring bMGroomedCircuit object attributes

Receipt of an M-SET operation from the OSS to the 5620 CMIP results in a request to the OSS Interface Agent and to the 5620 NM for validation. If the validation succeeds, the CMIP M-SET operation results in the modification of the values of bMGroomedCircuit object attributes.

The bMGroomedCircuit object generates an attributeValueChangeRecord M-EVENT REPORT notification when any of its attributes are modified, either through a CMIP operation or through some action of the 5620 NM.

See Table 24-1 for a list of bMGroomedCircuit object attributes.

13.9 Deleting paths

An instance of a bMGroomedCircuit object can only be deleted if the path has been disconnected and is in the 5620 NM “Ready for connect” state. The 5620 CMIP returns an access denied CMIP error message to the OSS if the path has been disconnected and is not in the “Ready for connect” state.

The CMIP M-DELETE operation will delete an instance of a bMGroomedCircuit object only if its administrativeState attribute value is locked and its operationalState attribute value is enabled.



After the 5620 NM removes the path from its database, the 5620 CMIP removes the bMGroomedCircuit object from its MIB and emits an objectDeletion M-EVENT-REPORT notification.

If the path deletion operation fails, the 5620 NM notifies the 5620 CMIP, which returns a processing failure CMIP error to the OSS.

13.10 Path maintenance

The OSS can perform the following path maintenance functionality:

• tracing • grooming

Path tracing

The trmCircuitTrace M-ACTION traces a path through the network and returns a list of all:

• bMFacility objects that the path is routing across• intermediate and terminating managedGroomedCircuitTP objects used by the

path• managedEquipment objects used by the path

Path grooming

The trmCircuitGrooming M-ACTION request causes the 5620 CMIP to attempt to optimize its routing. The 5620 CMIP returns a response indicating whether the path was groomed or not. If a more efficient route is not found, service is not affected.

If the path’s routing changes, the 5620 CMIP emits the following M-EVENT-REPORT notifications:

• administrativeState stateChange• operationalState stateChange• currentProblemList attributeValueChange• communicationsAlarm


Hitless connection moves

The hitlessConnectionMove action of the genericActionObject causes the 5620 CMIP to attempt to optimize the routing of SPVC paths or perform maintenance on the SPVC paths.



If path routing changes, the 5620 CMIP generates the following notifications:

• hcmResult• hcmResultDescription• hcmResponseData

See chapter 29 for more information

13.11 Path recovery

The OSS must configure routing on an individual path basis for 5620 NM path recovery to occur. The commonProfile attribute of bMGroomedCircuit object models the path recovery option. See Table 24-8 for details.

Fault in connection

If a link goes down, the 5620 NM tries to find a new route for each affected path. If the 5620 NM cannot find a new route for a given path, it sets the path status to “Connected down” or “Waiting for resources”. The 5620 CMIP leaves the administrativeState attribute value of the bMGroomedCircuit object as unlocked and emits the following M-EVENT-REPORT notifications:



Reroute

If the 5620 NM finds a new route for a path, it sets the path status to “Reroute requested”. The 5620 CMIP then emits the following M-EVENT-REPORT notifications:

• currentProblemList attributeValueChange• communicationsAlarm

When the 5620 NM has finished rerouting the path, it sets the path status to “Connected”. The 5620 CMIP emits the following M-EVENT-REPORT notifications:

• currentProblemList attributeValueChange• communicationsAlarm

Timing outages

The reroute warning and clear alarms sent by the 5620 CMIP provide the OSS with the information to calculate the outage time of rerouted paths using the eventTime attribute of the communicationsAlarm.




14.1 Link management overview 14-2

14.2 Physical links 14-2

14.3 Logical links 14-2

14.4 Resource links 14-6



14.1 Link management overview

The 5620 CMIP models physical and logical links with the bMFacility object. The 5620 CMIP supports limited configuration of physical links and creation, configuration, and deletion of logical links.

Connection management of frame relay and ATM links is similar to connection management of paths. See section 13.6 for more information.

14.2 Physical links

The 5620 CMIP models physical links, such as T1 and OC3, with instances of bMFacility object. The 5620 CMIP automatically instantiates physical link objects but cannot create or delete them.

14.3 Logical links

There are the following types of logical links:

Frame relay links

The 5620 CMIP supports the creation, configuration, and deletion of 5620 NM frame relay links. Frame relay links are modeled as bMFacility objects and have the following facilityType values:

• hierarchy = 19 (frame relay link)• media = 10 (virtual)

Creating frame relay link bMFacility objects

By providing two valid frame relay logical link endpoints and specifying the correct facilityType attribute values, an OSS can request that the 5620 CMIP create a frame relay link bMFacility instance. Configuration values can be specified upon creation. If configuration values are not specified, default values are assigned.

For frame relay links, the M-CREATE operation for a bMFacility object must:

• specify the distinguishedName of the superior object instance second level network object of the bMFacility object

• include required attributes (see Table 14-1)

• frame relay links• MFR links• ATM links

• VCC links• IMA links• PSN links



Table 14-1 Required attributes for a bMFacility M-CREATE operation

Configuring frame relay link bMFacility objects

The trmCircuitProfile attribute, which can be set by using an M-SET operation, contains the configurable frame relay properties. See section 23.4 for a complete list of the frame relay link bMFacility attributes.

Deleting frame relay link bMFacility objects

An OSS can delete a frame relay link bMFacility by using M-DELETE on the instance. The link must first be disconnected before it can be deleted.

MFR links

The 5620 CMIP supports the creation, configuration, and deletion of 5620 NM MFR links. MFR links are modeled as bMFacility objects and have the following facilityType values:

• hierarchy = 23 (MFR link)• media = 10 (virtual)

Creating MFR link bMFacility objects

The 5620 NM and the OSS can create a MFR link bMFacility instance by providing two valid MFR logical link endpoints and specifying the correct facilityType attribute values. See the 5620 Network Manager User Guide for endpoint configuration information. Configuration information can be specified upon creation. If configuration values are not specified, default values are assigned.

For MFR links, the M-CREATE operation for a bMFacility object must:


• include the required attributes, as described in Table 14-1

Attribute Description

objectClass Identifies the object as a bMFacility

a-TPInstance

z-TPInstance

Refers to the managedFacilityTP object at each end of the bMFacility

facilityType Provides the facility type through a hierarchy field and media field

nameBinding Identifies the kind of name binding used by the bMFacility object



Configuring MFR link bMFacility objects

The trmCircuitProfile attribute, which can be set by using an M-SET operation, contains the configurable MFR link properties. See section 23.4 for a complete list of the MFR link bMFacility attributes.

Deleting MFR link bMFacility objects

An OSS can delete an MFR link bMFacility object by using M-DELETE on the instance.

ATM links

The 5620 CMIP supports the creation, configuration, and deletion of 5620 NM ATM VPC logical links. ATM links are modeled as bMFacility objects and have the following facilityType values:

• hierarchy = 20 (ATM link)• media = 10 (virtual)

Creating ATM link bMFacility objects

The 5620 NM and the OSS can create an ATM link bMFacility instance by providing two valid ATM logical link endpoints and specifying the correct facilityType attribute values. Configuration information, including connection status, can be specified upon creation. If configuration values are not specified, default values are assigned.

For ATM links, the M-CREATE operation for a bMFacility object must:



Configuring ATM link bMFacility objects

The trmCircuitProfile attribute, which can be set by using an M-SET operation, contains the configurable ATM properties. See section 23.4 for a complete list of the ATM link bMFacility attributes.

Deleting ATM link bMFacility objects

An OSS can delete an ATM link bMFacility object by using M-DELETE on the instance. The link must first be disconnected before it can be deleted.



IMA links

The 5620 CMIP supports the creation, configuration, and deletion of 5620 NM IMA logical links. IMA links are modeled as bMFacility objects and have the following facilityType values:

• hierarchy = 21 (IMA link)• media = 10 (virtual)

Creating IMA link bMFacility objects

The 5620 NM and the OSS can create an IMA link bMFacility instance by providing two valid IMA logical link endpoints and specifying the correct facilityType attribute values. Configuration information can be specified upon creation. If configuration values are not specified, default values are assigned.

For IMA links, the M-CREATE operation for a bMFacility object must:



Configuring IMA link bMFacility objects

The trmCircuitProfile attribute, which can be set by using an M-SET operation, contains the configurable IMA link properties. See section 23.4 for a complete list of the IMA link bMFacility attributes.

Deleting IMA link bMFacility objects

An OSS can delete an IMA link bMFacility object by using M-DELETE on the instance.

PSN linksThe 5620 CMIP supports the creation and deletion of 5620 NM PSN logical links. PSN links are modeled as bMFacility objects and have the following facilityType values:

• hierarchy = 24 (PSN link)• media = 10 (virtual)

Note — The administrativeState for an IMA link is always set to unlocked.



Creating PSN link bMFacility objects

The 5620 NM and the OSS can create a PSN link bMFacility instance by providing two valid PSN logical link endpoints and specifying the correct facilityType attribute values. The PSN link can be created between two 7670 RSP nodes. For the 7670 RSP, Release 3.0 to 6.1, both nodes must contain at least one of the following cards:

• MR16 POS• GigE

For the 7670 RSP, Release 6.2 or later, each node must contain at least one of the following cards:

• MR16 POS• GigE• MR48

You can only create one PSN link between two 7670 RSP nodes.

For PSN links, the M-CREATE operation for a bMFacility object must:



Deleting PSN link bMFacility objects

An OSS can delete a PSN link bMFacility object by using M-DELETE on the instance. Any paths that ride the link must be disconnected before the link is deleted.

14.4 Resource links

Resource links are specialized links that are used to carry information between nodes. There are three types of resource links:

• PNNI links• ILMI links• signaling links

This section contains a brief description of each type of resource link. See the 5620 NM ATM Configuration Reference guide for more information.

PNNI links

PNNI links carry network topology and ATM address information between 36160, 7470 MSP, 7270 MSC, and 7670 RSP nodes. The nodes use this information for SVC and SPVC routing. PNNI links use the ATM Forum PNNI routing protocol.



PNNI links are created in association with NNI PVC links only. SPVC VCC and frame relay paths are carried on VPC links configured to carry them. When a VPC link is configured to carry SPVCs, its associated PNNI link must also be configured, unless static PNNI routing tables have been configured using NMTI.

To control a connected PNNI link, use the service cards at the VPC link endpoint nodes.

PNNI link path-ends

PNNI links share their path-ends with the VPC links they traverse.

When PNNI links are created on the 5620 NM, the 5620 NM PNNI link configuration form appears with the appropriate path-end information automatically filled in. When the PNNI link is associated with a VPC link set to SVCs and SPVCs, both path-ends are identical.

ILMI links

ILMI links identify nodes for ATM address retrieval and management across the UNI. ILMI links act like signaling links and are associated with VPC links. VPC links with associated ILMI links can be created on 36035, 36075, 36160, 7470 MSP, 7270 MSC, 7670 RSP, 56020, and ATM Host nodes.

The ILMI link between the user and the network carries status, configuration, and control information about the ILMI link and about the physical layer parameters. The ILMI link also provides address exchange between the user and the network across the UNI. This reduces the manual configuration required to route ILMI links by advising the network of the ATM address of nodes that support the ILMI protocol.

When using 5620 CMIP to configure a VPC link to carry SVCs and SPVCs, its associated PNNI link must be configured, unless a static PNNI routing table was configured using NMTI. A signaling link must be created. Signaling links carry information about the creation and deletion of SVCs and SPVCs between nodes.

ILMI link path-ends

An ILMI link shares the same path-ends as its VPC link.

When ILMI links are created on the 5620 NM, the 5620 NM ILMI link configuration form appears with the appropriate path-end information automatically filled in.

Signaling links

ATM signaling links carry information about the creation and deletion of SVCs and SPVCs between ATM nodes. When ATM signaling links are created on the UNI side, they carry information between ATM nodes and equipment on the customer premises.

SPVC, VCC, and frame relay paths are carried on VPC links specifically configured to carry them. When a VPC link is configured to carry SVCs and SPVCs, its associated ATM signaling link must also be configured. An ATM signaling link is carried on a VPC link and is called an in-band signaling link.



Signaling link profiles

The 5620 NM has signaling link profiles for 36120, 36160, 7470 MSP, 7270 MSC, and 7670 RSP nodes. ATM signaling link profiles are a set of configured attributes that the 5620 NM can send to all nodes of the same type in the network to define the operation of their associated signaling links. A profile can be used by more than one signaling link.

Signaling link profiles cannot be created or deleted; however, signaling link profile attributes can be changed to customize the profiles for a network.

Signaling link profiles can be viewed through the 5620 CMIP using the managedProfile object. The 5620 CMIP can also be used to set the profile parameters using the attribute managedProfileProf of the managedProfile object. See chapter 37 for more information about the managedProfile object.

Signaling link endpoints

In-band ATM signaling links share their path-ends with the VPC links they traverse.

When in-band signaling links are created on the 5620 NM, the 5620 NM signaling link configuration form appears with the appropriate path-end information automatically filled in. When out-of-band signaling links are created on the 5620 NM, the user selects the originating and terminating path-ends and pastes them into the VCC path configuration form.

Creating a resource link using the 5620 CMIP

Resource links are associated with bMFacility VPC links and share the same endpoints. To create a resource link using the 5620 CMIP, there must be an existing bMFacility VPC link. A bMGroomedCircuit create request can then be formed to set up the path that the resource link will traverse. See section 13.5 for detailed instructions.



15.1 About 7390 NT management 15-2

15.2 7390 NT commissioning 15-2

15.3 7390 NT replacement 15-5

15.4 7390 NT decommissioning 15-7



15.1 About 7390 NT management

This chapter describes how to commission, replace, and decommission an 7390 NT unit.

15.2 7390 NT commissioning

Before you commission a 7390 NT, the following mandatory cpTypes for the ntCommissioningProfile attribute must be available:

• NT Serial Number• Radio Link Number• Uplink Number

The configuration of these cpTypes is be done from the elementExtensions object on the 7390 DBS. See section 26.6 for information about the ntCommissioningProfile attribute.

Perform an M-SET on the ntCommissioningProfile attribute of the 7390 DBS elementExtensions object with the "modifyOperator" set to "add" and the above cpTypes specified in the M-SET request. The M-SET response returns the unique NT ID (cpType 4) when the 7390 NT commissioning is successful. The NT ID should be used whenever replacing or deleting an NT.

Message interaction sequence for NT commissioningThe CMIP "SetArgument" for commissioning a 7390 NT is given below. Comment lines begin with "//".

SetArgument SEQ

baseManagedObjectClass CHOICE

globalForm OID 1.2.124.113537.1.1.12

// Object Identifier of elementExtensions Object

baseManagedObjectInstance CHOICE

distinguishedName SEQ OF len=4

[0] SET OF len=1

[0] SEQ

attributeType OID 0.0.13.3100.0.7.30

attributeValue ANY

Note — Prior to Release 5.3, Alcatel 7390 DBS and NT units were modeled as managedElement objects. For Release 5.3 and later, they are modeled as both managedElement and elementExtensions objects. See chapters 20 and 26 for information about the elementExtensions object and the managed object hierarchy.



NameType CHOICE

pString GraphicsString len=15 "Alcatel Network"

[1] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 0

[2] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 10

[3] SET OF len=1

[0] SEQ


// Object Identifier of elementExtensionsId

attributeValue ANY

NameType CHOICE

numericName INT 1

accessControl EXTERNAL absent

synchronization ENUM 0

scope CHOICE

level INT 0

filter CHOICE

and SET OF no space

modificationList SET OF len=1

[0] SEQ

modifyOperator ENUM 1



// "add" modifyOperator

attributeId CHOICE

globalForm OID 1.2.124.113537.1.4.28

// Object Identifier of "ntCommissioningProfile"

attributeValue ANY

NTCommissioningProfile SET OF len=1

[0] SET of len=7

[0] SEQ

type INT 1

value CHOICE

strValue GraphicsString len=7 "NT #121"

[1] SEQ

type INT 2

// Mandatory cpType "NT Serial Number"

value CHOICE

strValue GraphicsString len=12 "555223A232BC"

[2] SEQ

type INT 5

// Mandatory cpType "Radio Link" Number

value CHOICE

intValue INT 2

[3] SEQ

type INT 6

// Mandatory cpType "Uplink" Number

value CHOICE

intValue INT 3

[4] SEQ

type INT 7

value CHOICE

strValue GraphicsString len=15 "Ottawa, Ontario"



[5] SEQ

type INT 8

value CHOICE

intValue INT 0

[6] SEQ

type INT 10

value CHOICE

intValue INT 0

15.3 7390 NT replacement

Before you replace a 7390 NT, the following mandatory cpTypes for the ntCommissioningProfile attribute must be set:

• NT Serial Number• NT ID

The configuration of these cpTypes is be done from the elementExtensions object on the 7390 DBS. See section 26.6 for information about the ntCommissioningProfile attribute.

Perform an M-SET on the ntCommissioningProfile attribute of the 7390 DBS elementExtensions object with the "modifyOperator" set to "replace" and the above cpTypes specified in the M-SET request. The M-SET response returns the unique NT ID (cpType 4) when the 7390 NT replacement is successful.

Message interaction sequence for NT replacementThe CMIP "SetArgument" for replacing a 7390 NT is given below. Comment lines begin with "//".

SetArgument SEQ


globalForm OID 1.2.124.113537.1.1.12

// Object Identifier of elementExtensions Object.



[0] SET OF len=1

[0] SEQ




attributeValue ANY

NameType CHOICE


[1] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 0

[2] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 10

[3] SET OF len=1

[0] SEQ



attributeValue ANY

NameType CHOICE

numericName INT 1



scope CHOICE

level INT 0

filter CHOICE

and SET OF no space


[0] SEQ




// "replace" modifyOperator

attributeId CHOICE

globalForm OID 1.2.124.113537.1.4.28


attributeValue ANY


[0] SET of len=3

[0] SEQ

type INT 1

value CHOICE

strValue GraphicsString len=7 "NT #121"

[1] SEQ

type INT 2

// Mandatory cpType "NT Serial Number" - (new value)

value CHOICE

strValue GraphicsString len=12 "555223A978DA"

[2] SEQ

type INT 4

// Mandatory cpType "NT Id"

value CHOICE

intValue INT 78

15.4 7390 NT decommissioning

Before you decommission a 7390 NT, the NT ID (cpType 4) for the ntCommissioningProfile attribute must be available. Configuration is done from the elementExtensions object on the7390 DBS. See section 26.6 for information about the ntCommissioningProfile attribute.

Perform an M-SET on the ntCommissioningProfile attribute of the 7390 DBS elementExtensions object with the "modifyOperator" set to "delete" and the NT ID (cpType 4) specified in the M-SET request. The M-SET response returns the unique NT ID (cpType 4) when the 7390 NT decommissioning is successful.



After a 7390 NT is decommissioned, the ntCommissioningProfile attribute will be updated and an attributeValueChange event will occur. The 7390 NT information will be removed from the ntCommissioningProfile attribute on the 7390 DBS and the ntCommissioningProfile attribute on the 7390 NT will have no entries. Once the 7390 DBS deletes the 7390 NT, notification will be sent by the 5620 NM to the 5620 CMIP, which will cause the managedElement object and elementExtensions object corresponding to the 7390 NT to be deleted from the mib.

Message interaction sequence for NT decommissioningThe CMIP "SetArgument" for decommissioning a 7390 NT is given below. Comment lines begin with "//".

SetArgument SEQ


globalForm OID 1.2.124.113537.1.1.12

// Object Identifier of elementExtensions Object.



[0] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE


[1] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 0

[2] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE



numericName INT 10

[3] SET OF len=1

[0] SEQ



attributeValue ANY

NameType CHOICE

numericName INT 1



scope CHOICE

level INT 0

filter CHOICE

and SET OF no space


[0] SEQ


// "delete" modifyOperator

attributeId CHOICE

globalForm OID 1.2.124.113537.1.4.28


attributeValue ANY


[0] SET of len=1

[0] SEQ

type INT 4

// Mandatory cpType "NT Id"

value CHOICE

intValue INT 78



16.1 Testing overview 16-2

16.2 The testActionPerformer object 16-4

16.3 Administering a test on the busyOutTestObject 16-6

16.4 Administering a test on the loopBackTestObject 16-7

16.5 Administering a test on the oAMCellTestObject 16-8

16.6 Administering a test on the splitMonitorTestObject 16-13

16.7 Administering a test on the testAccessConnectionObject 16-16

16.8 Administering a test on the traceTestObject 16-19

16.9 Off-node testing 16-22



16.1 Testing overview

Diagnostics support allows the OSS to create, modify, and remove various tests on network paths.

The 5620 CMIP models diagnostics support using the testActionPerformer object, which can create the following types of test objects:

• busyOutTestObject• loopBackTestObject• oAMCellTestObject• splitMonitorTestObject• testAccessConnectionObject• traceTestObject• genericActionObject

Each test object performs different types of tests. To run a test:

• the OSS must perform an M-ACTION request on the testActionPerformer object, which then creates the test object

• the OSS then performs an M-ACTION request on the test object to trigger the diagnostics

For example, when conducting a splitMonitorTestObject test on a particular bMGroomedCircuit, the OSS performs a trmCircuitTrace action on the bMGroomedCircuit. This trmCircuitTrace action result identifies all termination points along the circuit. The OSS then determines, through a series of CMIP get operations, where split-through, split-back, or monitor tests can be performed.

The OSS systematically tests each of these managedGroomedCircuitTPs, splitting or monitoring traffic from the on-node managedGroomedCircuitTP determined from the trmCircuitTrace.

When the splitMonitorTestObject test is completed, the testRelease M-ACTION terminates the test and sets the test object to the not initialized state.

Normally the test object is not deleted from the MIB until the OSS issues a testTerminateAction request on the testActionPerformer object. The splitMonitorTestObject is the only exception to this rule. The testRelease M-ACTION releases the splitMonitorTestObject and deletes it from the MIB.

The busyOutTestObject

The busyOutTestObject administers a busy-out test on physical links, frame relay, and VPC links. The actions of this object are boLink and boRelease. See section 16.3 and chapter 25 for more information.



The loopBackTestObject

The loopBackTestObject administers a loopback test on 36150 Access Switches, 7470 MSP ports, 7670 RSP, and 7670 ESE ports. The actions of this object are lbEquipment, lbLine, and lbRelease. See section 16.4 and chapter 31 for more information.

The oAMCellTestObject

The oAMCellTestObject administers an OAM cell loopback test on VPC links, VPC and VCC paths. The action of this object is oam-cell. See section 16.5 and chapter 39 for more information.

The splitMonitorTestObject

The splitMonitorTestObject administers either a split-back, split-through, or monitor test. The splitMonitorTestObject tests network paths.

The monitor test allows non-intrusive, listen-only access to a connection and is not service-affecting. The split-back and split-through tests reroute traffic through test equipment. Both of these tests are service-affecting. See section 16.6 and chapter 44 for more information.

Table 16-1 lists the splitMonitorTestObject testTypes, based on equipment.

Table 16-1 splitMonitorTestObject testTypes by equipment

See the 5620 Network Manager User Guide chapter on Maintenance connections for a list of connections and speeds that support on-node testing.

The testAccessConnectionObject

The testAccessConnectionObject administers a monitor, split-back, or split-loop test. The testAccessConnectionObject tests ATM equipment in the network.

The monitor test allows non-intrusive, listen-only access to a connection and is not service-affecting. The split-back and split-through tests reroute traffic through test equipment. Both of these tests are service-affecting. Use a testAccessConnectionObject to verify the performance of a data path or to isolate a fault along a data path. The identified circuit indicates the port where the testAccessConnectionObject will connect.

Equipment testTypes supported

5620 NM Both on- and off-node testing on system-created paths

3600 MSS MainStreet nodes Split-through and monitor

3600, 3664, and 3600 MSS MainStreet nodes Split-through, split-back, and monitor



When testing ATM Circuit Emulation equipment, the tacTestProfile provides the data octets and playout buffer values. For cell relay equipment, the tacTestProfile provides the VPI and VCI pathpoints.

Apply a testAccessConnectionObject to a single endpoint of a cross-connect. To test both endpoints, apply a second testAccessConnectionObject to the other endpoint of the target connection while leaving the original testAccessConnectionObject in place. See section 16.7 and chapter 47 for more information.

The traceTestObject

The traceTestObject administers ATM Forum standards-based path and connection tracing for SPVC paths within multivendor interoperable networks. See section 16.8 and chapter 49 for more information.

The genericActionObjectThe genericActionObject supports get and get-replace operations, as well as listPaths and hitlessConnectionMove actions. See chapter 29 for more information.

16.2 The testActionPerformer object

The testActionPerformer object administers the creation and deletion of the test objects. The testActionPerformer object can contain multiple instances of each of the six test object types at any one time. The testAccessConnectionObject and splitMonitorTestObject are limited to 100 concurrent instances.

Initiating and terminating a test request

The testActionPerformer object can perform the following actions, which result in the creation and deletion of test objects:

• testRequestControlledAction (test initiation) • testTerminateAction (test termination)

The testActionPerformer object contains all test objects, regardless of their test type. Figure 20-7 illustrates how these test objects are contained by the testActionPerformer object in the MIB.

Table 16-2 describes the information that the OSS must supply for each object as part of the testRequestControlledAction.

Table 16-2 Required attributes for objects in testRequestControlledAction

Attribute tACO (1) sMTO (2) lBTO (3) bOTO (4) oAMCTO (5) tTO (6)

mORTs Required Required Required Required Required Required

tOClass Required Required Required Required Required Required

(1 of 2)



Notes(1) tACO = testAccessConnectionObject(2) sMTO = splitMonitorTestObject(3) lBTO = loopBackTestObject(4) bOTO = busyOutTestObject(5) oAMCTO = oAMCellTestObject(6) tTO = traceTestObject

The testRequestControlledAction returns the object instance of the test object that was created to administer the test.

Normally the test object is not deleted from the MIB until the OSS issues a testTerminateAction request on the testActionPerformer object. The splitMonitorTestObject is the only exception to this rule. The testRelease M-ACTION releases the splitMonitorTestObject and deletes it from the MIB.

Table 16-3 describes the actions for each test object.

Table 16-3 Test object actions

associated-Objects

Required Required Not required Not required Required Required

initialAttri- buteList

tacTestProfile Test name Test name

Recovery type

Test name

Recovery type

Test name

Return point

traceTestProfile

Attribute tACO (1) sMTO (2) lBTO (3) bOTO (4) oAMCTO (5) tTO (6)

(2 of 2)

Test object Action See section

busyOutTestObject boLink 16.3

boRelease

loopBackTestObject lbEquipment 16.4

lbLine

lbRelease

oAMCellTestObject oam-cell 16.5

splitMonitorTestObject testMonitor 16.6

testRelease

testSplitBack

testSplitThru

testAccessConnectionObject monitorTAC 16.7

releaseTAC

splitBackTAC

splitLoopTAC

(1 of 2)



16.3 Administering a test on the busyOutTestObject

The busyOutTestObject administers a busy-out test. When the test is completed, the boRelease M-ACTION terminates the test and sets the object to the not initialized state. The busyOutTestObject is not deleted from the MIB until a testTerminateAction is issued on the testActionPerformer object. The testActionPerformer object can contain multiple instances of the busyOutTestObject.

busyOutTestObject test informationBusy-out tests can be used to determine where the 5620 NM rerouted traffic, or to view the effect of taking a managedFacilityTP out of service. You can perform busy-out tests on:

• frame relay links• full or fractional ATM links• VPC links

Busy-out tests can be performed on full, fractional, or overlay links to reroute paths affected by a fault in the carrier network.

When performing a busy-out test on a full or fractional link, all path and node management connections and overlay links that are already connected are unaffected. New overlay links or paths cannot be routed over that link.

Performing a test on the busyOutTestObjectTwo actions can be performed on the busyOutTestObject:

• boLink• boRelease

When performing the boLink action, the 5620 CMIP verifies that the selected object supports both the busy-out test and the action specified.

If the busy-out test is not supported, the action fails and returns an error message.

If the test is supported, the action causes the following:

• boTestType attribute is set• boRecoveryType attribute is set• operationalState and proceduralStatus attributes in the busyOutTestObject set to

indicate the object is in a testing state; see Table 48-2 for more information

traceTestObject connectionTrace 16.8

spvcConnectionTrace

spvcPathTrace

Test object Action See section

(2 of 2)



The busyOutTestObject boRelease action causes the following:

• busyOutTestObject operationalState and proceduralStatus attributes set to indicate the object is in a not initialized state; see Table 48-2 for more information

• boTestType attribute sets to boRelease

16.4 Administering a test on the loopBackTestObject

The loopBackTestObject administers a loopback test. When the test is completed, the lbRelease M-ACTION terminates the test and sets the object to the not initialized state. The loopBackTestObject is not deleted from the MIB until a testTerminateAction is issued on the testActionPerformer object. The testActionPerformer object can contain multiple instances of the loopBackTestObject.

loopBackTestObject test informationLoopback tests are applied on ATM ports to isolate faults on paths and overlay links. The following tests are supported:

• ATM line loopback• ATM equipment loopback

To isolate a problem on a path or an overlay link, insert a loopback at progressive points along the link or path. The fault will be between the last successful loopback test and the first unsuccessful loopback test.

Performing a test on the loopBackTestObjectThree actions can be performed on the loopBackTestObject:

• lbEquipment• lbLine• lbRelease

The lbEquipment and lbLine actions are similar, differing only in the type of test that they perform. When performing one of these actions on the loopBackTestObject, the 5620 CMIP verifies that the test is supported for the given object type.

If the test is not supported, the action fails and returns an error message.


• lbTestType attribute is set• lbRecoveryType is set (default is connected-down)• operationalState and proceduralStatus attributes in the loopBackTestObject set to


If an action is performed to change an existing test (for example, performing an lbLine action when the loopBackTestObject is set to lbEquipment) the connections on the node reconfigure for the new lbTestType and change the lbtestType attribute in the loopBackTestObject.



The loopBackTestObject lbRelease action causes the following:

• loopBackTestObject operationalState and proceduralStatus attributes set to indicate the object is in a not initialized state; see section 48.4 for more information

• lbTestType attribute sets to lbRelease

16.5 Administering a test on the oAMCellTestObject

The oAMCellTestObject administers an OAM cell loopback test. When the test is completed, the oAMCellTestObject may be deleted from the MIB if a testTerminateAction is issued on the testActionPerformer object. The testActionPerformer object can contain multiple instances of the oAMCellTestObject.

OAM cell loopback test informationOAM cell loopback tests are used to verify the integrity of all or part of a connected VPC link, VPC path, or VCC path.

During an OAM cell loopback, a single cell is injected at a defined point along the link or path. The cell travels along the connection until it reaches its defined return point, where it is looped back to its injection point. The loopback affects only the OAM cell and has no effect on user traffic.

If the cell is successfully returned to its injection point, the connection between the cell injection point and the return point is live. If the cell is not returned, that part of the connection is faulty.

Figures 16-1 to 16-4 illustrate the possible OAM cell loopback diagnostic tests.

Note — There is no Release action for the oAMCellTestObject.



Figure 16-1 VCC OAM cell loopback - return point specified

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

Loopback return point

Inject point

15441

VCC

VCC

VCC

VCC



Figure 16-2 VCC OAM cell loopback - no return point specified

DS3

OC3

DS3

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3


Inject point

15442

OC3

OC3

VCC



Figure 16-3 VPC OAM cell loopback - return point specified

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

T1

OC3

DS3

OC3

T1

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3


Inject point

15443

VPC

VPC

VPC

VPC



Figure 16-4 VPC OAM cell loopback - no return point specified

Performing a test on the oAMCellTestObjectThe oam-cell action is the only action that can be performed on the oAMCellTestObject.

When performing the oam-cell action, the 5620 CMIP verifies that the selected object supports the OAM cell loopback test.

If the OAM cell loopback test is not supported, the action fails and returns an error message.


• associatedObjects list is set• operationalState and proceduralStatus attributes in the oAMCellTestObject set to

indicate that the object is now in a testing state; see Table 48-2 for more information

• a single cell is injected (specified by the action request); at the end of the test, either the oAMCellTestObject can be deleted from the MIB using the testTerminateAction on the testActionPerformer object or another oam-cell action may be issued

OC3

DS3

DS3

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3


Inject point

15444

OC3

OC3

OC3

DS3

DS3

DS3

7470 MSPNode 1

7470 MSPNode 2

7470 MSPNode 3

OC3

OC3

VPC

VPC



16.6 Administering a test on the splitMonitorTestObject

The splitMonitorTestObject administers a monitor, split-back, or split-through monitor test. The splitMonitorTestObject does not support ATM paths. When the test is completed, the testRelease M-ACTION terminates the test, sets the object to the not initialized state, and then deletes the splitMonitorTestObject from the MIB. The splitMonitorTestObject is also deleted from the MIB if a testTerminateAction is issued on the testActionPerformer object. The testActionPerformer object can contain multiple instances of the splitMonitorTestObject.

splitMonitorTestObject test informationThe splitMonitorTestObject administers either a monitor, split-back, or split-through test. Figure 16-5 shows the traffic flow for each of the test configurations.



Figure 16-5 splitMonitorTestObject testTypes

Node

Network

Testequipment

Testequipment

Targetcircuit 1

Maintenancecircuit 1


Node

Testequipment

Network

Testequipment

Targetcircuit 1



11357

Node

Testequipment

Testequipment

Network

Targetcircuit 1



Monitor Maintenance Connection

Split-back Maintenance Connection

Split-through Maintenance Connection



Monitor testing

Figure 16-5 illustrates a monitor test. A monitor test allows non-intrusive, listen-only access on live connections. The monitored connection is routed to a maintenance managedGroomedCircuitTP without affecting service.

Split-back testing

Figure 16-5 illustrates a split-back test. A split-back test is a non-intrusive service-affecting action that splits a connection, then diverts traffic to a test managedGroomedCircuitTP and back to the target managedGroomedCircuitTP. External equipment can be used to insert and observe test traffic patterns to help isolate the fault. A split-back test causes service interruption during the connection of the test access connection and adds delays in the traffic flow.

Split-through testing

Figure 16-5 illustrates a split-through test. A split-through test is a non-intrusive service-affecting action that splits a connection so that each end of the connection is routed to a test managedGroomedCircuitTP. External equipment can then be used to insert and monitor test patterns to help isolate the fault.

Performing a test on the splitMonitorTestObjectThe following four actions can be performed on the splitMonitorTestObject:

• testSplitThru• testSplitBack• testMonitor• testRelease

The only specified parameter is the object instance of the splitMonitorTestObject.

The testSplitThru, testSplitBack, and testMonitor actions differ only in the type of test performed. When performing one of these actions on the splitMonitorTestObject, the 5620 CMIP creates and connects two bMGroomedCircuit objects in the case of off-node tests. For on-node tests, the 5620 CMIP sets up the appropriate connections on the node for the split-through, split-back, or monitor test. See section 16.9 for more information about off-node testing.

If the 5620 CMIP is unable to connect the two bMGroomedCircuit objects (for example, if the two bMGroomedCircuit objects are waiting for resources) or set up the on-node maintenance connections, the action fails and returns an error message or generates a processing error alarm.

If successful, the action causes the following:

• two test bMGroomedCircuit objects are added to the associatedObjects list• splitMonitorTestObject operationalState and proceduralStatus attributes set to




If an action is performed to change an existing test (for example, performing a split-back action when the splitMonitorTestObject is set to monitor) the connections on the node reconfigure for the new testType and change the testType attribute in the splitMonitorTestObject. The two existing test bMGroomedCircuit objects are not changed.

The testRelease action causes the following:

• the two test bMGroomedCircuit objects disconnect and delete (the system-created paths)

• splitMonitorTestObject operationalState and proceduralStatus attributes set to indicate the object is in a not initialized state; see Table 48-2 for more information

• splitMonitorTestObject attributes of the test bMGroomedCircuit associatedObjects set to Null

• splitMonitorTestObject deletes from the MIB

If the testRelease M-ACTION cannot delete the two test bMGroomedCircuit objects or remove the on-node maintenance connections, an error message is returned.

16.7 Administering a test on the testAccessConnectionObject

The testAccessConnectionObject administers either a monitor, split-back, or split-loop test. When the test is completed, the releaseTAC M-ACTION terminates the test and sets the object to the not initialized state. The testAccessConnectionObject is not deleted from the MIB until a testTerminateAction is issued on the testActionPerformer object. The testActionPerformer object can contain multiple instances of the testAccessConnectionObject.

testAccessConnectionObject test informationThe testAccessConnectionObject administers either a monitor, split-back, or split-loop test. Figure 16-6 shows the traffic flow for each of the test configurations.



Figure 16-6 testAccessConnectionObject tacTestTypes

11359

Node

Testequipment

Network

Testequipment

Targetcircuit 1



Node

Monitor Maintenance Connection

Split-back Maintenance Connection

Split-loop Maintenance Connection

Network

Testequipment

Testequipment

Targetcircuit 1



Node

Testequipment

Network

Testequipment

Targetcircuit 1





Monitor testing

Figure 16-6 illustrates a monitor test. A monitor test allows non-intrusive, listen-only access on live connections. The monitored connection is routed to a maintenance managedGroomedCircuitTP, where test equipment can be connected without affecting service.

Split-back testing

Figure 16-6 illustrates a split-back test. A split-back test is a non-intrusive service-affecting action that splits a connection, then diverts traffic to a test managedGroomedCircuitTP and back to the target managedGroomedCircuitTP. Then external equipment can be used to insert and observe test patterns to help isolate the fault. A split-back test causes service interruption during the connection of the test access connection and adds delays in the traffic flow.

Split-loop testing

Figure 16-6 illustrates a split-loop test. A split-loop test is a non-intrusive service-affecting action that splits a connection and loops the ingress traffic at the selected connection endpoint back as egress traffic at the same port. It then connects a monitor port to the looped back connection. Note that the traffic never reaches the network.

Performing a test on the testAccessConnectionObjectThe following four actions can be performed on the testAccessConnectionObject:

• monitorTAC• splitBackTAC• splitLoopTAC• releaseTAC

When performing a monitor, split-back, or split-loop test on the testAccessConnectionObject, the 5620 CMIP tests a managedGroomedCircuitTP using the appropriate configuration.

If the 5620 CMIP is unable to set up the test or if the selected tacTestType is not supported for the given object type, the action fails and returns an error message or generates a processing error alarm.

If successful, the action causes the following:

• tacTestType attribute sets to a testing state (monitorTAC, splitBackTAC, or splitLoopTAC)

• operationalState and proceduralStatus attributes set to indicate that the object is in a testing state; see Table 48-2 for more information



The releaseTAC action causes the following:

• operationalState and proceduralStatus attributes set to the not initialized state to indicate that the object is not in a testing state; see Table 48-2 for more information

• tacTestType attribute sets to releaseTAC

To change an existing test from one tacTestType to another, set the object to releaseTAC before using an action to initiate the new test with the new tacTestType.

16.8 Administering a test on the traceTestObject

The traceTestObject supports the connectionTrace, spvcPathTrace, and spvcConnectionTrace actions. The spvcPathTrace and spvcConnectionTrace actions provide ATM Forum standards-based trace data for SPVC paths.

When a traceTestObject action is completed, the traceTestObject is not deleted from the MIB until a testTerminateAction is issued on the testActionPerformer object. The testActionPerformer object can contain multiple instances of the traceTestObject.

traceTestObject test informationThe traceTestObject can perform the following actions:

• connectionTrace• spvcPathTrace• spvcConnectionTrace

connectionTrace action

The connectionTrace action retrieves the VPI, VCI, or DLCI values of all the intermediate endpoints. The connectionTrace action includes an ActionInfo argument. This consists of two parts:

• actionType, the OID of the action• actionInfoArg, is of a managedProfile type called connectionTraceInfo, used to

specify the output format for the connectionTrace action

Table 16-4 describes the actionInfoArg options for connectionTrace.

Table 16-4 connectionTrace actionInfoArg options

Characteristic cpType cpValue Description

Results format 1 1 1 = The results format, which includes a list of intermediate path endpoints along with their VPI, VCI, or DLCI values of the chosen path with which the traceTestObject is associated.

See section 49.6 for more information about the connectionTrace results.



spvcPathTrace action

The spvcPathTrace action collects data on new paths and paths that are in the process of being established. See chapter 49 for more information about how to interpret the output of a spvcPathTrace.

The actionReplyInfo attribute is an octet string that contains the trace data from a spvcPathTrace action response. The trace data is not parsed.

Figure 16-7 illustrates spvcPathTrace interaction sequences between an OSS and the 5620 CMIP OSS Interface Gateway.

Figure 16-7 spvcPathTrace interaction sequences

Note — When an spvcPathTrace action is requested on a path that is in a connected state, the path will first change to a disconnected state to allow for the spvcPathTrace action to be performed.

SPVC path createdsuccessfully

SPVC path goes"waiting for resources"

or "SPVC path connected"

testObjectId oftraceTestObject

ATM Forum-basedtrace data

Create theSPVC path

Connect theSPVC path

Create traceTestObjectfor the required mORT

Execute spvcPathTraceon the target SPVC path;

if path is connected,reconnect

M-CREATE request forbMGroomedCircuit object

M-CREATE response

M-SET request on"administrativeState"

M-SET response

testRequestControlledAction ontestActionPerformer object

testRequestControlledActionresponse

spvcPathTrace action request ontraceTestObject

spvcPathTraceaction response

16380

OSS (Manager)5620 CMIP OSS

Interface Gateway



spvcConnectionTrace action

The spvcConnectionTrace action collects data on paths that are in a connected state. See chapter 49 for more information about how to interpret the output of a spvcConnectionTrace.

The actionReplyInfo attribute is an octet string that contains the trace data from an spvcConnectionTrace action response. The trace data is not parsed.

Figure 16-8 illustrates spvcConnectionTrace interaction sequences between an OSS and the 5620 CMIP OSS Interface Gateway.

Figure 16-8 spvcConnectionTrace interaction sequences

SPVC path createdsuccessfully

SPVC path connectedsuccessfully

testObjectId oftraceTestObject

ATM Forum-basedtrace data

Create theSPVC path

Connect theSPVC path

Create traceTestObjectfor the required mORT

Execute spvcConnectionTraceon the target SPVC path

M-CREATE request forbMGroomedCircuit object

M-CREATE response

M-SET request on"administrativeState"

M-SET response

testRequestControlledAction ontestActionPerformer object

testRequestControlledActionresponse

spvcConnectionTraceaction request ontraceTestObject

spvcConnectionTraceaction response

16381

OSS (Manager)5620 CMIP OSS

Interface Gateway



Performing a test on the traceTestObjectThe traceTestObject can perform the following actions:

• connectionTrace• spvcPathTrace• spvcConnectionTrace

If the 5620 CMIP cannot set up an action or if a selected traceTestType is not supported for the given object type, the action fails and returns an error message or generates a processing error alarm.

If successful, an action causes the following:

• traceTestType attribute sets to a testing state (spvcPathTrace or spvcConnectionTrace)

• operationalState and proceduralStatus attributes set to indicate that the object is in a testing state; see Table 48-2 for more information

A completed test causes the following:

• operationalState and proceduralStatus attributes set to the not initialized state to indicate that the object is not in a testing state; see Table 48-2 for more information

• traceTestType attribute sets to trace-none• test results, in the format described in chapter 49, to be returned in a reply

message

16.9 Off-node testing

During off-node testing, when a testSplitThru, testSplitBack, or testMonitor action is performed on a splitMonitorTestObject, the 5620 NM creates two test bMGroomedCircuit objects. These bMGroomedCircuit objects have endpoints that are not cross-connected. They can be data or voice TDM paths that reflect the type of bMGroomedCircuit under test.

The 5620 NM system-created bMGroomedCircuit attributes are the same as the attributes of the bMGroomedCircuit under test, with the following exceptions:

• name (userLabel) is set to system n, where n is a variable that increases with the number of test managedGroomedCircuitTPs

• circuit bandwidths are dictated by the target termination point (circuitBandwidth)• the following components of the (commonProfile) attribute:

• backup bandwidth is not reserved [backup bandwidth]• circuit remains affected until the fault is repaired [reroute]• do not optimize circuit after reroute [cpType 3]

• subrate multiplexing is not used (tDMProfile) [cpType 3]

Note — Round brackets indicate attributes and square brackets indicate cpTypes.



The OSS can connect and disconnect the system-created bMGroomedCircuit objects through normal CMIP operations. However, the OSS can only change the following attributes of these bMGroomedCircuit objects:

• name (userLabel)• fiber routing (trmFiberRouting)• encryption (trmEncryptionRouting)• terrestrial routing (trmTerrestrialRouting)• custom label 4, part of the (commonProfile) attribute [cpType 1]• priority, also part of the (commonProfile) attribute [cpType 2]

Note — Round brackets indicate attributes and square brackets indicate cpTypes.



17.1 Event management overview 17-2

17.2 Event and alarm logging and forwarding 17-2

17.3 Event and alarm notifications 17-3

17.4 Event and alarm sources 17-9

17.5 Event and alarm log record objects 17-11

17.6 Port alarm suppression 17-11



17.1 Event management overview

The 5620 CMIP receives network configuration changes and alarm notifications that occur in the 5620 NM-managed network. The 5620 CMIP can forward and/or store these notifications. To receive these notifications, the OSS must create and configure one or more eventForwardingDiscriminator objects. For the 5620 CMIP to store these notifications, the OSS must create and configure one or more log objects.

The ITU-T standard X.733 defines alarms as specific types of notifications concerning detected faults or abnormal conditions. When the 5620 CMIP detects an alarm, it updates the corresponding managed object in the MIB and generates a CMIP alarm notification. The 5620 CMIP generates alarm notifications as a result of:

• 5620 NM trouble tickets• 5620 NM path status changes• 5620 CMIP internal errors• alarms from the 5620 NM fault management system• alarms from the ALMAP AS-IM component

The OSS can filter specific notifications by configuring the discriminatorConstruct of the eventForwardingDiscriminator and log objects. Notifications are sent by the eventForwardingDiscriminator to the OSS as 5620 CMIP M-EVENT-REPORT messages. Notifications are stored by the log as logRecord objects.

See chapter 28 for information about configuring the eventForwardingDiscriminator object. See chapter 30 for information about configuring the log object.

17.2 Event and alarm logging and forwarding

This section provides an overview of 5620 CMIP event and alarm logging and forwarding. Since these functions conform to standards, these standards should be consulted for more detail. See section 2.3 for more information.

log object

The log object creates logRecords for all notifications that meet its discriminatorConstruct filter criteria. All logRecords are contained by the log object that created them.

As specified in X.733, each instance of a log object contains a discriminatorConstruct attribute. The discriminatorConstruct attribute specifies the characteristics a notification must have in order to be selected for logging. Information that is selected for logging is supplemented with additional information, such as record identifiers and logging time, that is generated as part of the logging process. Each record has an identifier attribute value that is assigned when the record is created. Values are assigned locally in ascending sequential order. The identifier attribute can be used to determine the order of record creation by the log.

See chapter 30 for information about the log object.



eventForwardingDiscriminator object

The eventForwardingDiscriminator object forwards notifications that meet its discriminatorConstruct filter criteria to each OSS that is listed in the destination attribute.

See chapter 28 for information about the eventForwardingDiscriminator object.

discriminatorConstruct attribute

The discriminatorConstruct attribute is a selection mechanism for both the eventForwardingDiscriminator object and the log object.

The discriminatorConstruct attribute specifies the characteristics a notification must have in order to be selected for forwarding; it also specifies the characteristics a notification must have in order to be selected as a logRecord object, which is contained by a log object.

Time stamping

Forwarded and stored notifications are time-stamped in the following manner:

• Alarm notifications originating in the network or on the 5620 NM NetworkStation are stamped with the time the alarm occurred on the 5620 NM NetworkStation.

• Internal 5620 CMIP alarms are stamped with the time they occurred on the 5620 CMIP OSS Interface Gateway.

• All other notifications—objectDeletion, objectCreation, attributeValueChange, and stateChange—are stamped by the 5620 CMIP with the time they were processed by the 5620 CMIP. This time differs from the time these configuration changes actually occurred in the network.

17.3 Event and alarm notifications

Two types of notifications may be generated by the 5620 CMIP: events and alarms. These notifications are transmitted as M-EVENT-REPORT messages. The message argument type is eventReportArgument.

eventReportArgument

Table 17-1 describes the different attributes of the eventReportArgument type.



Table 17-1 eventReportArgument ASN.1 type attributes

Table 17-2 describes the two types of notifications that may be generated by the 5620 CMIP. The eventInfo and eventType fields differentiate events from alarms.

Table 17-2 Notification types

Notes(1) See the GDMO/ASN.1(2) See Appendix E

Table 17-3 describes the possible values of OIDs for the managedObjectClass attribute of the eventReportArgument.

Attribute Description Value description

managedObjectClass Identifies the class of object that generated the notification

Managed Object Class OID; see Table 17-3 for a list of ManagedObjectClasses and OIDs

managedObjectInstance Identifies the object instance that caused the notification to be generated

An objectInstance distinguishedName or sequence of OIDs uniquely identifying the object that generated the notification.

eventTime Identifies the time the event occurred Time

eventType Identifies the type of event An OID describing eventInfo

eventInfo Contains detailed information describing the event

Data defined by eventType; see Table 17-2 for details

Notification type eventType OID eventInfo (1)

Alarm communicationsAlarm 2.9.3.2.10.2 alarmInfo (2); see Table 17-4

environmentalAlarm 2.9.3.2.10.3 alarmInfo (2); see Table 17-4

equipmentAlarm 2.9.3.2.10.4 alarmInfo (2); see Table 17-4

processingErrorAlarm 2.9.3.2.10.10 alarmInfo (2); see Table 17-4

qualityOfServiceAlarm 2.9.3.2.10.11 alarmInfo (2); see Table 17-4

Event attributeValueChange — attributeValueChangeInfo; see Table 17-5

objectCreation — objectInfo; see Table 17-6

objectDeletion — objectInfo; see Table 17-6

stateChange — stateChangeInfo; see Table 17-7



Table 17-3 Managed Object Class OIDs

Note(1) Managed Object Class OID does not apply for events.

Table 17-4 to 17-7 describe the attributes for alarmInfo ASN.1 type, attributeValueChangeInfo, objectInfo, and stateChangeInfo, respectively.

Managed Object Class OID

bMFacility 1.2.124.360501.3.78

bMGroomedCircuit 1.2.124.360501.3.77

busyOutTestObject 1.2.124.113537.1.1.7

Channel (1) 1.3.12.2.1006.69.1.1.1.1.1

elementExtensions 1.2.124.113537.1.1.12

equipmentHolder 0.0.13.3100.0.3.32

eventForwardingDiscriminator 2.9.3.2.3.4

genericActionObject 1.2.124.113537.1.1.13

IpAddrTable (1) 1.3.6.1.3.1.2.1.4.20

Log 2.9.3.2.3.6

loopBackTestObject 1.2.124.113537.1.1.6

Lsp (1) 1.3.6.1.4.1.637.69.2.3.84.1.3

managedElement 0.0.13.3100.0.3.3

managedEquipment 1.2.124.113537.1.1.4

managedFacilityTP 1.2.124.113537.1.1.3

managedGroomedCircuitTP 1.1.124.113537.1.1.2

managedPack 1.2.124.113537.1.1.1

managedProfile 1.2.124.113537.1.1.10

network 0.0.13.3100.0.3.1

oAMCellTestObject 1.2.124.113537.1.1.8

PwVcTable (1) 1.3.6.1.3.123.1.2

splitMonitorTestObject 1.2.124.113537.1.1.5

testAccessConnectionObject 1.2.124.113537.1.1.9

testActionPerformer 2.9.2.12.3.2

traceTestObject 1.2.124.113537.1.1.11



Table 17-4 alarmInfo ASN.1 type attributes

Note(1) Optional fields that are not supported by 5620 CMIP are not listed.

Table 17-5 attributeValueChangeInfo attributes


Attribute (1) Description Value description

additionalInformation Contains the problem code and 5620 NM selected object name

See Appendix E.1 for details

additionalText Textual description of the problem from the node or the 5620 NM, the 5620 NM selected object name, and the user label for the object in the form used by the 5620 NM, for example 13-1-1-1.

There may also be information contained about the subcodes and params from NCI-based node alarms. This information is listed following the - (dash).

See Appendix E.8 and E.2 for details

monitoredAttributes Defines one or more attributes of the managed object and the corresponding values at the time of the alarm


perceivedSeverity Indicates the level of seriousness of the event 0 = indeterminate

1 = critical

2 = major

3 = minor

4 = warning

5 = clear


probableCause Identifies the likely cause of the alarm An OID or an integer that corresponds to a general probable cause specified in X.721 and X.733. The format of the alarm depends on the source of the alarm; see Appendix E.5 for details

thresholdInfo Present when the alarm is a result of crossing a threshold value


specificProblems An OID sequence that describes a specific problem indicated by the alarm.



sourceIndicator Indicates the source that caused the event to occur

0 = resourceOperation

1 = managementOperation

2 = unknown

attributeValueChangeDefinition Lists the attributes that have changed and their values

ASN.1 AttributeValueChangeDefinition



Table 17-6 objectInfo attributes


Table 17-7 stateChangeInfo attributes


Event notificationsThe 5620 CMIP emits event notifications to OSS applications if an appropriate eventForwardingDiscriminator object exists. Event notifications model occurrences, such as:

• the creation or deletion of objects in the 5620 CMIP MIB• a change in the value of any object’s attributes• a change in state of any object’s administrativeState or operationalState attributes

Table 17-8 describes the origin for each event notification type.

Table 17-8 M-EVENT-REPORT event types





2 = unknown

attributeList Lists the attributes and their values ASN.1 attributeList





2 = unknown

stateChangeDefinition Lists the state attributes that have changed and their values

ASN.1 AttributeValueChangeDefinition

Source object class

Event notification type (1) mE (2)

mP (3)

mEq (4)

bMF (5)

mF TP (6)

bMGC (7)

mGCTP (8)

eH (9)

log eFD (10)

objectCreation ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

objectDeletion ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

attributeValue Change ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

stateChange ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓



Notes(1) As defined in ITU-T standard X.721(2) mE = managedElement(3) mP = managedPack(4) mEq = managedEquipment(5) bMF = bMFacility(6) mFTP = managedFacilityTP(7) bMGC = bMGroomedCircuit(8) mGCTP = managedGroomedCircuitTP(9) eH = equipmentHolder(10) eFD = eventForwardingDiscriminator

Alarm notifications

Alarm notifications are forwarded to the OSS by the eventForwardingDiscriminator object. Alarm notifications model fault conditions in the network. Table 17-9 describes the origin for each alarm notification emitted by the 5620 CMIP and from 5620 NM trouble tickets.

For alarms forwarded from the 5620 NM fault management system, the source object class of the alarm and the event notification type depends on the nature of the fault on the node or network resource that generated the alarm.

Table 17-9 M-EVENT-REPORT alarm types for 5620 NM trouble ticket and 5620 CMIP alarms

Notes(1) As defined in ITU-T standard X.721(2) mE = managedElement(3) mP = managedPack(4) mEq = managedEquipment(5) bMF = bMFacility(6) mFTP = managedFacilityTP(7) bMGC = bMGroomedCircuit(8) eH = equipmentHolder(9) eFD = eventForwardingDiscriminator

Source object class

Event notification type (1)

Origin mE (2)

mP (3)

mEq (4)

bMF (5)

mFTP (6)

bMGC (7)

eH (8)

log eFD (9)

SMTO

equipmentAlarm 5620 NM trouble tickets

✓ ✓ ✓ ✓

5620 CMIP ✓

communications Alarm

5620 NM trouble tickets

✓ ✓

5620 NM detected path status change

✓ ✓

processingError Alarm

5620 CMIP ✓ ✓ ✓ ✓



17.4 Event and alarm sources

This section describes the sources that the 5620 CMIP uses to obtain event and alarm information.

Event sourcesThe following are the different event sources in the 5620 CMIP.

objectCreation

An object instance is created in the 5620 CMIP MIB. For example, a new OC3 MMF card is plugged into a 7470 MSP peripheral shelf. This causes the 5620 CMIP to add a managedPack object to its MIB, triggering an objectCreation notification.

objectDeletion

An object instance is deleted from the 5620 CMIP MIB. For example, an STM1 card is removed from a 7470 MSP peripheral shelf. This causes the 5620 CMIP to remove a managedPack object from its MIB, triggering an objectDeletion notification.

attributeValueChange

The 5620 CMIP detects a change in the value of any nonstate attribute in its MIB. For example, the 5620 NM increases the bandwidth on an ATM PVC path. This results in an update to the MIB, triggering an attributeValueChange of the bMGroomedCircuit aTMProfile attribute.

stateChange

The 5620 CMIP detects a change in the value of a state attribute in its MIB. For example, the 5620 NM performs a loopback on a time slot. This results in an update to the MIB, triggering a state change of the managedGroomedCircuitTP administrativeState attribute.

Alarm sources

The following are the sources that trigger 5620 CMIP alarm notifications.

5620 NM trouble tickets

The 5620 NM trouble tickets contain information on faults in network components. A 5620 NM trouble ticket is created when the 5620 NM first recognizes a fault on an object. 5620 NM trouble tickets contain history records that are updated as the status of a fault changes or as new faults occur. The 5620 CMIP is triggered by these history records to generate event reports or alarm record objects against MIB objects.

See the 5620 NM documentation for more information about 5620 NM trouble tickets.



5620 NM path and logical link status changes

Path and logical link status changes in the network are reported to the 5620 CMIP as communicationsAlarms.

5620 CMIP internal errors

The 5620 CMIP internal errors raise alarms against either the managedElement object instance, which models the Gateway Station, or the log object instance. The 5620 CMIP internal errors report on:

• MIB synchronization (managedElement)• communication between the 5620 CMIP and the 5620 NM (managedElement)• MIB reload status (managedElement)• log capacity (log)

5620 NM fault management system

The 5620 CMIP may report alarms that are reported through the 5620 NM fault management system.

The source and type of alarm information that you receive depends on the setting of the X.733 Fault Manager attribute of the 5620 NM entire network configuration form. See the 5620 NM Network Configuration Procedures guide for more information about configuring attributes on the entire network configuration form.

If the X.733 Fault Manager attribute on the entire network configuration form is set to Yes, alarms from 7300 ASAM and 7390 DBS nodes, NCI alarms and 5620 SNMP DM status changes will be reported by the 5620 CMIP

If the X.733 Fault Management attribute on the 5620 NM entire network configuration form is set to No, only alarms from 7300 ASAM and 7390 DBSs will continue to be processed. NCI alarms and 5620 SNMP DM status changes will not be processed. Alarm duplication is thereby reduced. See the 5620 NM Alarm Surveillance Administration guide for more information about fault management processes.

Procedure 17-1 To enable 5620 NM fault management processes

Duplicate alarms may be propagated to the 5620 CMIP if fault management processes are enabled on the 5620 NM.

1 Select the Entire Network icon on the 5620 NM GUI.

Note — Path status changes are also reflected in the bMGroomedCircuit currentProblemList attribute.

Caution — As 5620 NM trouble tickets contain similar information for NCI nodes, and the 5620 CMIP generates alarm record objects based on 5620 NM trouble tickets, alarm duplication may occur if the X.733 Fault Manager attribute on the 5620 NM entire network configuration form is set to Yes.



2 Choose Edit→ Configure Object from the 5620 NM main menu.

The Entire Network configuration form is displayed.

3 Set the X.733 Fault Manager attribute to Yes.

4 Click on the Save button to save the form.

ALMAP AS-IM componentThe 5620 NM may report 5620 DSL EM alarms that are reported through the ALMAP AS-IM component. The 5620 CMIP will report these alarms if the ALMAP AS-IM component has been installed with the 5620 NM and the CE_chgsrv process has been started with the -e option. See table 8-4 for more information.

17.5 Event and alarm log record objects

If an event or an alarm is logged by the 5620 CMIP, it is stored as a separate log record object. Figure 20-4 shows the MIB modeling hierarchy for event and alarm log records. An OSS application can perform M-GET operations on attributes of event and alarm log record objects to retrieve event and alarm information.

Table 17-10 describes the event and alarm log record types.

Table 17-10 Event and alarm log record types

17.6 Port alarm suppression

Using a standard CMIP set command, the OSS can change the port alarm suppression status for a managedFacilityTP. See section 34.5 for more information about port alarm suppression.

The administrativeState, alarmStatus, and operationalState attributes are updated regardless of the alarm suppression setting. The OSS can always get the current object status by querying these attributes.

Event object type Description

objectCreationRecord This record stores objectCreation event notification information; see chapter 40 for more information.

objectDeletionRecord This record stores objectDeletion event notification information; see chapter 41 for more information.

stateChangeRecord This record stores stateChange event notification information; see chapter 45 for more information.

attributeValueChangeRecord This record stores attributeValueChange event notification information; see chapter 22 for more information.

alarmRecord This record stores alarm notification information; see chapter 21 for more information.



When port alarm suppression is enabled, either on the 5620 NM or through the 5620 CMIP, all associated OSSs are affected. Table 34-2 describes the facilityTPProfile attribute settings that refer to port alarm suppression.

Note — The currentProblemList attribute is not updated when port alarm suppression is enabled. A query on this attribute when port alarm suppression is enabled may result in potentially inaccurate data.



18.1 Statistics Collector configurations 18-2

18.2 Statistics collection and the 5620 CMIP 18-2

18.3 Activating statistics using the 5620 CMIP 18-3

18.4 Interpreting statistics reports 18-3

18.5 Collecting real-time statistics 18-5



18.1 Statistics Collector configurations

The Statistics Collector is a statistics collection system for a 5620 NM-managed network. It provides performance statistics that comply with industry standards.

The Statistics Collector stores statistics in a series of ASCII files in a format that is suitable for postprocessing. The format of these files is consistent with standard postprocessing packages.

The Statistics Collector consists of statistics tables, database, aggregate, and collector software.The collector software polls network elements for statistics.

See the 5620 Network Manager Installation and Upgrade Guide for information about installing Statistics Collector software on Database, Collector, and Aggregator NetworkStations.

See the Statistics Collector guide for more information about the Statistics Collector.

18.2 Statistics collection and the 5620 CMIP

The 5620 CMIP can activate and deactivate statistics collection for:

• bMGroomedCircuit objects (paths)• managedFacilityTP objects (ports)

Configuration requirementsActivating statistics collection using the 5620 CMIP requires a 5620 NM NetworkStation with the Statistics Collector installed.

See the 5620 Network Manager Installation and Upgrade Guide for information about installing Statistics Collector software on Database, Collector, and Aggregator NetworkStations.

Statistics Collector and 5620 CMIP interactionsThe 5620 CMIP OSS Interface Gateway communicates with the OSS Interface Agent. The OSS Interface Agent passes on statistics activation requests to the Statistics Collector.

If the appropriate Statistics Collector package is not installed, a CMIP error message is returned when the OSS application attempts to invoke the 5620 CMIP statistics activation feature.

If the appropriate Statistics Collector package is subsequently installed, the 5620 CMIP statistics activation feature is available for use by the OSS application.

Note — The 5620 CMIP can only activate and deactivate statistics collection. The 5620 CMIP cannot perform statistics information retrieval.



18.3 Activating statistics using the 5620 CMIP

The 5620 CMIP can activate or deactivate statistics collection for supported objects. Table 18-1 identifies the attributes that control statistics activation status.

Table 18-1 Locating the statistics activation status

To activate statistics collection on a path or port, the OSS issues an M-SET—set to enabled—on the attributes listed in Table 18-1.

To deactivate statistics collection on a path or port, the OSS issues an M-SET—set to disabled—on the attributes listed in Table 18-1.

To retrieve the statistics activation status on a path or port, the OSS issues an M-GET on the attributes in Table 18-1.

18.4 Interpreting statistics reports

The Statistics Collector stores statistics in a series of 5620 NM-based ASCII files that you can format for postprocessing. Use FTP to retrieve these statistics reports from the Statistics Collector. This section describes how to correlate formatted statistics data with 5620 CMIP objects.

Statistics output format (since Release 4.0)Using ST_customFilter, you can filter Statistics Collector binary files that can then be formatted according to your needs.

ST_customFilter can run in filtering and formatting mode. In filtering mode, the aggregated files are filtered and then saved as binary files. In formatting mode, the aggregated files are filtered and then passed to ST_customFormat for formatting.

ST_customFormat is a process that formats Statistics Collector binary files into text files, based on information within configuration files. The configuration files specify which fields are printed and which formatting options are used. See the 5620 Network Manager User Guide for more information about configuring and interpreting the Statistics Collector output formats.

5620 NM object 5620 CMIP object Attribute

Path bMGroomedCircuit aTMProfile cpType 7 (cpValue 1=disabled; 2=enabled); see Table 24-12 for details

Port managedFacilityTP facilityTPProfile cpType 4 (cpValue 1=disabled; 2=enabled); see Table 34-2 for details



Statistics output format (before Release 4.0)The following output formats are available for the statistics data file from the ST_formatter utility:

• human readable format (contains text strings for statistics type, statistics ID and error code)

• Statistics Collector format (provides numbers to specify statistics type, statistics ID and error code)

• Statistics Reporter format (older format based on a previous statistics software version called the Statistics Reporter)

If you are using ST_formatter to correlate information between the statistics data files and the 5620 CMIP, we recommend that you use the Statistics Collector output format. See the 5620 Network Manager User Guide for more information about configuring and interpreting the Statistics Collector output formats.

Mapping between statistics data files and the 5620 CMIPYou can correlate information in the statistics data files with the information collected in the 5620 CMIP database. To correlate between the statistics output files and the 5620 CMIP, use the Statistics Collector format output files because they contain the fields that can easily map to 5620 CMIP values.

Table 18-2 provides a quick reference of 5620 CMIP objects and attributes that are useful for correlating between the 5620 CMIP and the Statistics Collector format data file. See the 5620 Network Manager User Guide for more information about interpreting the Statistics Collector output format.

Table 18-2 Important 5620 CMIP objects and attributes for interpreting statistics

5620 NM object Object Attribute Description

Node managedElement (1) (2) userLabel Node full name, short name, or both, depending on the value of the -mEUL process start-up option. See Table 8-4 for more information.

vendorName CPSS address

managedElementID Node id

Logical link bMFacility (2) connectionId Logical link id

Path bMGroomedCircuit (3) trailId Path id

(1 of 2)



Notes(1) The 5620 CMIP database does not model the 5620 NM node Short Name.(2) Statistics collection activation for this object is not possible through 5620 CMIP.(3) Statistics collection activation for this object is possible through 5620 CMIP.

18.5 Collecting real-time statistics

You can collect real-time statistics from network objects using the 5620 CMIP. Statistics are collected and written to port 8269 on the 5620 CMIP OSS Interface Gateway the OSS client is connected to, according to the parameters provided.

The 5620 CMIP OSS Interface Gateway provides methods for configuring and collecting real-time statistics on supported network objects using four separate actions on the genericActionObject:

• configureRealTimeStatistics• collectRealTimeStatistics• determineRealTimeStatistics• cancelRealTimeStatistics

The four actions manage real-time statistics functionality for supported network objects.

Port managedFacilityTP (3) cTPId String: “N# S# C# [,#] D# [LE#]”

where N# = node id

where S# = shelf id

where C# = card (or slot) id

where [,#] = subslot id (optional)

where D# = device/resource

where [LE#] = a link endpoint—DS0, SRM, or FSC number (optional)

managedGroomedCircuitTP (2) tTPId String: “N# S# C# [,#] D# [PE#][B#],#”

where N# = node id

where S# = shelf id

where C# = card (or slot) id

where [,#] = subslot id (optional)

where D# = device/resource

where [PE#] = DS0 number for DS0s; SRM number for MJUs; 1 for others

where [B#] = used for MJUs only and gives the branch number (optional)

where # = circuit direction; 1 incoming for DS0s and MJUs and 2 (outgoing) for others

Card managedPack (2) equipmentId Card (or slot) id

5620 NM object Object Attribute Description

(2 of 2)



configureRealTimeStatisticsWhen the configureRealTimeStatistics action is performed, the 5620 CMIP verifies that the selected object is supported. If the object is not supported, the action fails and returns an error message. An error is also returned if there are already 20 configured/collecting statistics sessions on the 5620 CMIP OSS Interface Gateway. If the action is supported and allowed, the following occurs:

• The operationalState and proceduralStatus are set to indicate the testing state.• The configureRealTimeStatistics action returns an integer to indicate the session

ID of the newly configured statistics session.

See section 29.9 for more information.

collectRealTimeStatisticsWhen the collectRealTimeStatistics action is performed, the 5620 CMIP confirms that the supplied session identifier corresponds to a valid, previously configured collection session. The session must also have been configured within one hour before the collect request was sent. Otherwise, the action fails and an error message is returned. If the action is successful, the following occurs:

• The operationalState and proceduralStatus are set to indicate the testing state.• The real-time statistics data are sent to the OSS client on the previously

established TCP connection.


Note — Prior to executing the configureRealTimeStatistics or the collectRealTimeStatistics action, a successful TCP socket connection must be established between the 5620 CMIP Gateway and one OSS Client on the assigned Gateway port (OSS_StatsClient: 8269).

Once the connection is established, you can execute multiple configureRealTimeStatistics and collectRealTime statistics actions, up to a maximum of 20 actions from various OSS clients on the 5620 CMIP OSS Interface Gateway.

Caution — The OSS Client may disconnect its TCP socket connection from the 5620 CMIP OSS Interface Gateway at any time. In doing so, all currently configured sessions on the 5620 CMIP OSS Interface Gateway, including those belonging to another OSS client, will be terminated.

Note — The TCP connection between the OSS client and the Gateway Station are established on the OSS_StatsClient port 8269. Only one OSS client can connect at a time to the 5620 CMIP OSS Interface Gateway on this port. Any subsequent connection requests by other OSS clients are ignored.



cancelRealTimeStatisticsWhen the cancelRealTimeStatistics action is performed, the 5620 CMIP confirms that the provided session ID corresponds to a valid previously-configured, or currently-collecting, session. Otherwise, the action fails, and an error message is returned. If the action is successful, the following occurs:

• The operationalState and proceduralStatus are set to indicate the initializing, testing, and terminating states.

• The specified collection session is terminated.


determineRealTimeStatisticsWhen the determineRealTimeStatistics Action is performed, the 5620 CMIP ensures that the specified object is currently valid for statistics collection, for example, that the object is up and the path is connected. If this is not the case, the action fails, and an error is returned. If the object is valid, the following occurs:

• The operationalState and proceduralStatus are set to indicate the initializing, testing, and terminating states.

• The action returns a list of integers that correspond to the statistics identifiers supported by the selected object. If no statistics are supported on the specified object, the list is empty.


Real-time statistics data message formatThe 5620 CMIP OSS Interface Gateway sends three types of statistics messages to the OSS client. Table 18-3 describes the messages.

Table 18-3 Statistics messages

All messages are in ASCII string format. The first four characters define the length of the message that follows.

Header message

The first message of a collection session is the header message. The message is an ASCII string, with each field separated by the “\” delimiter. The fields of the message follow the format:

Message type Description

header The first message of a collection session containing a summary of the collection criteria

data The messages containing the collected statistics data

status Conveys information about the status of the collection session, for example completed, canceled, object validation failure, or buffer overflow



'SessionIdMessageType(0)\ObjectName\Endpoint\PollingDuration\PollingFrequency\StatisticId1\StatisticId2\...\StatisticId10'

Table 18-4 describes the message fields.

Table 18-4 Message header fields

For example, the header message for session 248, with a criteria of:

• Node 3 contained by partition 5• endpoint is N/A• polling duration is 60 minutes• polling frequency of 30 seconds• collecting statistic identifiers 142 and 34

would appear as:

'02480\0.0.13.3100.0.7.30=(pString)"Alcatel Network"#0.0.13.2100.0.7.20=(number)5#0.0.13.3100.0.7.28=(number)3\\60\30\142\34\0\0\0\0\0\0\0\0'

Field Description

SessionId Specifies the session this message belongs to

MessageType Specifies the type of message this is. For Statistics Header messages, this value is 0.

ObjectName Specifies the distinguished name of the selected managedObject being polled. This field is a string containing OID and value pairs separated by # characters. Together, the full distinguished name of an object instance is described.

The format of the string is:

oid=(basic_type)value#oid(basic_type)value...

where

basic_type is either numericName, pString, number, or string

value is the value of the OID

Endpoint Specifies the value of the endpoint. The values are:

a for endpoint a

z for endpoint z

blank if not applicable

PollingDuration Specifies the length of time in minutes that statistics collection will occur

PollingFrequency Specifies the frequency in seconds that statistics collection will occur

StatisticId1 Specifies the first statistic identifier being collected

StatisticId to StatisticId10 Specifies the remaining statistic identifiers being collected. The values are 0 if not applicable.



Data message

Statistics data collected at each interval of a collection session is sent as a data message. The message is an ASCII string, with each field separated by the delimiter “\”. The fields of the message take following format:

SessionIdMessageType(1)\DateAndTime\ExtraInfo\StatisticsData1\StatisticsData2\...StatisticsData10


Table 18-5 Message header fields

Note(1) When you collect real time rolling statistics, the first value received from the node is used as a

baseline, and then the difference between each polling period is plotted.

For example, the data message for session 248, with a criteria of:

• Polling date of 3:30 p.m., July 15th, 2005• Collecting statistics data on two statistics identifiers, with data 1578.3187 and

992.10

would appear as:

'02481\2005-07-15 15:50:28\\1578.3187\992.10\0.0\0.0\0.0\0.0\0.0\0.0\0.0\0.0'

Field Description


MessageType Specifies the type of message this is. For Statistics Data messages, this value is 1.

DateAndTime Specifies the date and time the statistics data is polled, expressed in GMT. For example: 2005-07-15 15:30:18

ExtraInfo Provides additional information about the collection interval:

• “[Reference Value]” — the reference value of the statistics identifier (1)

• “[Timeout]”— the reference value has been skipped

StatisticsData1 The statistics data gathered at this polling interval for StatisticsId1

StatisticsData2 to StatisticsData10

The statistics data gathered at this polling interval for StatisticsId2 to StatisticsId10. The values are 0.0 if there is no StatisticsId defined.

Note — If an invalid data value is retrieved, the StatisticsData value will be set to “NaN”, meaning “Not a Number.” See “Collecting real time statistics using the Network Performance Monitor” in the 5620 Network Manager User Guide for more information about exceptions with rolling counters and “NaN” errors.



Status message

A status message is sent if any errors are encountered during a statistics collection session. The message is an ASCII string, with each field separated by the delimiter “\”. The fields of the message take following format:

SessionIdMessageType(2)\StatusCode


Table 18-6 Status message header fields

For example, the Status message for session 248, after the cancelRealTimeStatistics action was performed, would appear as:

'02482\2'

Field Description


MessageType Specifies the type of message this is. For Statistics Status messages, this value is 2.

StatusCode Specifies the status information of the collection session. The status codes are:

0 = Successful completion of the collection session

1 = Object validation failure. The object from which statistics are being collected has become invalid, and statistics collection has ceased.

2 = Session canceled. The cancelRealTimeStatistics action was performed on this session prior to completing the possing duration.

3 = Buffer overflow. A message channel overflow has occurred, and there is a possible loss of statistics data. Real time statistics collection will continue.

4 = Terminated. The session has ended as a result of a processing error. Statistics collection ends.




19.2 Get 19-2

19.3 Set 19-9

19.4 Event report 19-18

19.5 Create 19-29

19.6 Delete 19-52

19.7 Action 19-57



19.1 Introduction

Interaction sequences from the 5620 CMIP are detailed examples of CMIP operations and results. Because customers determine the types of CMIP interactions their OSS application will require of the 5620 CMIP, it is not possible to show every type of interaction sequence.

The examples in this chapter address the most common operations and give a low-level view of how CMIP interactions manifest themselves in a running system.

Each interaction is described using a sequence diagram and a CMIP trace.

19.2 Get

Simple get

Figure 19-1 Simple (baseObject) M-GET

TRACE:

Code 19-1: Trace1) Request

GetArgument SEQ baseManagedObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.3 baseManagedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30

15348

OSS (Manager)

M-GET Invocation

M-GET Result

OSS Interface Agent



attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 accessControl EXTERNAL absent synchronization ENUM 0 scope CHOICE level INT 0 filter CHOICE and SET OF no space attributeIdList SET OF absent2) Result

GetResult SEQ managedObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 currentTime GeneralizedTime absent attributeList SET OF len=13 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.6 attributeValue ANY NAlarmStatus ENUM 0 [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.27 attributeValue ANY LocationName GraphicsString no space [2] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.28 attributeValue ANY



NameType CHOICE numericName INT 4 [3] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString len=4 "blah" [4] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.51 attributeValue ANY VendorName GraphicsString len=38 "network name, CPSS address: 1.2" [5] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.52 attributeValue ANY Version GraphicsString len=34 "Node: 36177 Generic: A21614-H0-00" [6] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.5 attributeValue ANY SystemTitle CHOICE oid OID 1.3.6.1.4.1.126.1.1 [7] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 1 [8] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.35 attributeValue ANY OperationalState ENUM 1 [9] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.39 attributeValue ANY UsageState ENUM 1 [10] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 0.0.13.3100.0.6.15 [11] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.65 attributeValue ANY ObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.3 [12] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=7 [0] OID 0.0.13.3100.0.4.32



[1] OID 0.0.13.3100.0.4.17 [2] OID 0.0.13.3100.0.4.34 [3] OID 0.0.13.3100.0.4.33 [4] OID 0.0.13.3100.0.4.4 [5] OID 0.0.13.3100.0.4.10 [6] OID 0.0.13.3100.0.4.28

Scoped M-GETPerformance is optimized for some scoped get requests on a network object with a non-baseObject scope and certain filters. If a request for a scoped get does not meet the conditions required for an optimized scoped get to be performed, the scoped get is performed without optimization.

The following filters are supported:

• an empty set (all objects in scope)• a single objectClass• an OR’d list of one or more objectClasses• an objectClass AND’d with an OR’d list of two or more attributes and filter types• an AND’d list of one or more attributes and filter types• an OR’d list of one or more attribute and filter types• an objectClass AND’d with one or more supported attributes and filter types

Supported attributes include:

• all string type attributes, such as userLabel and typeText• all integer or state type attributes, such as adminState and operationalState• specific berbuf attributes, such as naming attributes

Table 19-1 provides examples of optimized scoped get requests.

Table 19-1 Optimized scoped get request examples

Scoped Get Example

A single objectClass. GetRequest on Partition Network, scope {level wholeSubtree}, filter {objectClass == managedPack}

An OR'd list of any number of objectClasses. GetRequest on Partition Network, scope {level wholeSubtree}, filter {OR objectClass == managedPack, objectClass == bMGroomedCircuit, objectClass == managedEquipment, objectClass == elementExtensions}

A single objectClass AND'ed with an equality match for a single string-type attribute.

GetRequest on Partition Network, scope {level wholeSubtree}, filter {AND objectClass == managedPack, locationName == "Ottawa"}

A single objectClass AND'ed with a subString match for the string-attribute. All three of the subString types, initialString, anyString and finalString, are supported.

GetRequest on Partition Network, scope {level wholeSubtree}, filter {AND objectClass == equipmentHolder, string INITIAL equipmentHolderType "Power"}

A single objectClass AND'ed with a base-type attribute, A base-type attribute is an INTEGER or ENUMERATED type.

GetRequest on Partition Network, scope {level wholeSubtree}, filter {AND objectClass == managedEquipment, operationalState == 1}

(1 of 2)



Figure 19-2 Scoped M-GET

TRACE:

Code 19-2: Scoped M-GET request1) Request

GetArgument SEQ baseManagedObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.3 baseManagedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name"

A single objectClass AND'ed with a greaterOrEqual or lessOrEqual filter match on a base-type attribute.

GetRequest on Partition Network, scope {level wholeSubtree}, filter {AND objectClass == bMGroomedCircuit, nbalarmStatus LEQ 1}

A non-baseObject scope and a filter that consists of a present filter match for a single attributeName.

GetRequest on Partition Network, scope {level wholeSubtree}, filter {present affectedObjectList}

A single string-attribute (name and value). Equality and subString matching are supported.

GetRequest on Top Network, scope {level wholeSubtree}, filter {string ANY userLabel "-ott-"}

GetRequest on Partition Network, scope {basetoNthLevel 5}, filter {equality locationName "ottawa"}

A single base-type-attribute (name and value). Equality, greaterOrEqual and lessOrEqual matching are supported.

GetRequest on Partition Network, scope {level firstLevelOnly}, filter {equality administrativeState 1}

GetRequest on Partition Network, scope {level firstLevelOnly}, filter {lessOrEqual nbalarmStatus 1}

Scoped Get Example

(2 of 2)

15349

OSS (Manager)

M-GET Invocation

M-LINKEDREPLY (Get)

OSS Interface Agent

M-LINKEDREPLY (Get)

M-GET Result



[1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 accessControl EXTERNAL absent synchronization ENUM 0 scope CHOICE individualLevels INT 1 filter CHOICE and SET OF no space attributeIdList SET OF len=1 [0] CHOICE globalForm OID 2.9.3.2.7.66

Code 19-3: Scoped M-GET result2) Result:

i) LinkedReplyArgument CHOICE getResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.13 attributeValue ANY NameType CHOICE pString GraphicsString len=11 "N4 S1 C4 D1" currentTime GeneralizedTime absent



attributeList SET OF len=1 [0] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=5 [0] OID 0.0.13.3100.0.4.4 [1] OID 0.0.13.3100.0.4.10 [2] OID 0.0.13.3100.0.4.30 [3] OID 2.9.3.2.4.17 [4] OID 0.0.13.3100.0.4.28

ii) LinkedReplyArgument CHOICE getResult SEQ managedObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.32 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 currentTime GeneralizedTime absent attributeList SET OF len=1 [0] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=3 [0] OID 0.0.13.3100.0.4.41 [1] OID 0.0.13.3100.0.4.10 [2] OID 0.0.13.3100.0.4.4

iii) LinkedReplyArgument CHOICE getResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2



managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N4 S1 C4 D1 PE1,1" currentTime GeneralizedTime absent attributeList SET OF len=1 [0] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=6 [0] OID 0.0.13.3100.0.4.4 [1] OID 0.0.13.3100.0.4.10 [2] OID 0.0.13.3100.0.4.30 [3] OID 2.9.3.2.4.17 [4] OID 0.0.13.3100.0.4.28 [5] OID 0.0.13.3100.0.4.19

iv) GetResult SEQ managedObjectClass CHOICE absent managedObjectInstance CHOICE absent currentTime GeneralizedTime absent attributeList SET OF absent

19.3 Set

Simple M-SET



Figure 19-3 Simple M-SET UserLabel - success

TRACE:

Code 19-4: Simple M-SET request1) Request

SetArgument SEQ baseManagedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 baseManagedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1 accessControl EXTERNAL absent synchronization ENUM 0 scope CHOICE level INT 0 filter CHOICE

15350

OSS (Manager)

M-SET SetArgument(bMGroomedCircuit)

M-SET SetResult(bMGroomedCircuit)

OSS Interface Agent

M-EVENT-REPORT(attributeValueChange)bMGroomedCircuit

M-EVENT-REPORT(attributeValueChange)bMGroomedCircuit



and SET OF no space modificationList SET OF len=1 [0] SEQ modifyOperator ENUM 0 attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString len=11 "Service XYZ"

Code 19-5: Simple M-SET resultResult

i) SetResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1 currentTime GeneralizedTime absent attributeList SET OF len=1 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString len=11 "Service XYZ"

ii)EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ



attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1 eventTime GeneralizedTime len=19 "19990420110245-0400" eventType CHOICE globalForm OID 2.9.3.2.10.1 eventInfo ANY AttributeValueChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent attributeValueChangeDefinition SET OF len=1 [0] SEQ attributeID CHOICE globalForm OID 0.0.13.3100.0.7.50 oldAttributeValue ANY UserLabel GraphicsString len=11 "Service ABC" newAttributeValue ANY UserLabel GraphicsString len=4 "Service XYZ" notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

M-SET bMGroomedCircuit AdminState (PathConnect)



Figure 19-4 Simple M-SET AdminState

TRACE:

Code 19-6: Simple M-SET AdminState request1) Request

SetArgument SEQ baseManagedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 baseManagedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 accessControl EXTERNAL absent

15351

OSS (Manager)

M-SET SetArgumentbMGroomedCircuit

M-SET SetResultbMGroomedCircuit

OSS Interface Agent

M-EVENT-REPORT(AttributeValueChange)bMGroomedCircuit

M-EVENT-REPORT(communicationsAlarm)bMGroomedCircuit

M-EVENT-REPORT(StateChange)bMGroomedCircuit



synchronization ENUM 0 scope CHOICE level INT 0 filter CHOICE and SET OF no space modificationList SET OF len=1 [0] SEQ modifyOperator ENUM 0 attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 1

Code 19-7: Simple M-GET AdminState result2) Result

i) SetResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 currentTime GeneralizedTime absent attributeList SET OF len=1 [0] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 1

ii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY



NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 eventTime GeneralizedTime len=19 "19990420111149-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=1 [0] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.31 oldAttributeValue ANY AdministrativeState ENUM 0 newAttributeValue ANY AdministrativeState ENUM 1 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

iii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4



[3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N4 S1 C5 D1 PE1,2" eventTime GeneralizedTime len=19 "19990420111154-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=2 [0] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.35 oldAttributeValue ANY OperationalState ENUM 1 newAttributeValue ANY OperationalState ENUM 1 [1] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.39 oldAttributeValue ANY UsageState ENUM 0 newAttributeValue ANY UsageState ENUM 2 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

iv) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1



[0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N4 S1 C5 D1 PE1,2" eventTime GeneralizedTime len=19 "19990420111154-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=2 [0] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.35 oldAttributeValue ANY OperationalState ENUM 1 newAttributeValue ANY OperationalState ENUM 1 [1] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.39 oldAttributeValue ANY UsageState ENUM 0 newAttributeValue ANY UsageState ENUM 2 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

v) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 eventTime GeneralizedTime len=21 "19990420111155.0-0500" eventType CHOICE



globalForm OID 2.9.3.2.10.2 eventInfo ANY AlarmInfo SEQ probableCause CHOICE globalValue OID 2.9.3.2.0.0.6 specificProblems SET OF absent perceivedSeverity ENUM 5 backedUpStatus BOOL absent backUpObject CHOICE absent trendIndication ENUM absent thresholdInfo SEQ absent notificationIdentifier INT absent correlatedNotifications SET OF absent stateChangeDefinition SET OF absent monitoredAttributes SET OF absent proposedRepairActions SET OF absent additionalText GraphicsString len=70 "The groomed circuit is unlocked; bandwidth has been allocated. - --:--" additionalInformation SET OF absent

19.4 Event report

Simple event report

Figure 19-5 Simple M-EVENT-REPORT (5620 NM path name change)

TRACE:

Code 19-8: M-EVENT-REPORT sample 11) Request

NONE (asynchronous operation caused by network)Result

EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE

15352

OSS (Manager) OSS Interface Agent

M-EVENT-REPORT(attributeValueChange)

bMGroomedCircuit userLabel



distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 eventTime GeneralizedTime len=19 "19990420113500-0400" eventType CHOICE globalForm OID 2.9.3.2.10.1 eventInfo ANY AttributeValueChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent attributeValueChangeDefinition SET OF len=1 [0] SEQ attributeID CHOICE globalForm OID 0.0.13.3100.0.7.50 oldAttributeValue ANY UserLabel GraphicsString len=11 "Service ABC" newAttributeValue ANY UserLabel GraphicsString len=11 "Service XYZ" notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

M-EVENT-REPORT (node offline)



Figure 19-6 Simple M-EVENT-REPORT (node offline)

Trace:

Code 19-9: M-EVENT-REPORT sample 21) Request:

NONE (asynchronous operation caused by network)2) Result:i) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 eventTime GeneralizedTime len=19 "19990420113716-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=3 [0] SEQ attributeID CHOICE

15353

OSS (Manager) OSS Interface Agent

M-EVENT-REPORT(equipmentAlarm)

M-EVENT-REPORT(stateChange)managedElement operationalState



globalForm OID 2.9.3.2.7.31 oldAttributeValue ANY AdministrativeState ENUM 1 newAttributeValue ANY AdministrativeState ENUM 1 [1] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.39 oldAttributeValue ANY UsageState ENUM 1 newAttributeValue ANY UsageState ENUM 1 [2] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.35 oldAttributeValue ANY OperationalState ENUM 1 newAttributeValue ANY OperationalState ENUM 0 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

ii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 0.0.13.3100.0.3.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 eventTime GeneralizedTime len=21 "19990420113716.0-0500" eventType CHOICE globalForm OID 2.9.3.2.10.4 eventInfo ANY AlarmInfo SEQ probableCause CHOICE globalValue OID 2.9.3.2.0.0.15 specificProblems SET OF absent perceivedSeverity ENUM 4 backedUpStatus BOOL absent



backUpObject CHOICE absent trendIndication ENUM absent thresholdInfo SEQ absent notificationIdentifier INT absent correlatedNotifications SET OF absent stateChangeDefinition SET OF absent monitoredAttributes SET OF absent proposedRepairActions SET OF absent additionalText GraphicsString len=51 "Received indication that ND5 is offline. - Node ND5" additionalInformation SET OF absent

M-EVENT-REPORT (physical link support path fails)

Figure 19-7 Complex M-EVENT-REPORT (physical link supporting one path fails)

Trace:

Code 19-10: M-EVENT_REPORT sample 31) Request:

NONE (asynchronous operation caused by network)2) Result:

i) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.78 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ

15354

OSS (Manager)

M-EVENT-REPORT(stateChange)

bmFacility operationalState

M-EVENT-REPORT(communicationsAlarm)

bMFacility

M-EVENT-REPORT(communicationsAlarm)

bMGroomedCircuit

M-EVENT-REPORT(stateChange)

bMGroomedCircuit operationState

OSS Interface Agent



attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.12 attributeValue ANY NameType CHOICE pString GraphicsString len=9 "Cable: 19" eventTime GeneralizedTime len=19 "19990422094130-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=2 [0] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.31 oldAttributeValue ANY AdministrativeState ENUM 1 newAttributeValue ANY AdministrativeState ENUM 1 [1] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.35 oldAttributeValue ANY OperationalState ENUM 1 newAttributeValue ANY OperationalState ENUM 0 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

ii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30



attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.13 attributeValue ANY NameType CHOICE pString GraphicsString len=11 "N4 S1 C4 D1" eventTime GeneralizedTime len=19 "19990422094131-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=1 [0] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.35 oldAttributeValue ANY OperationalState ENUM 1 newAttributeValue ANY OperationalState ENUM 0 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

iii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE



numericName INT 3 eventTime GeneralizedTime len=21 "19990422094131.0-0500" eventType CHOICE globalForm OID 2.9.3.2.10.2 eventInfo ANY AlarmInfo SEQ probableCause CHOICE globalValue OID 2.9.3.2.0.0.6 specificProblems SET OF absent perceivedSeverity ENUM 4 backedUpStatus BOOL absent backUpObject CHOICE absent trendIndication ENUM absent thresholdInfo SEQ absent notificationIdentifier INT absent correlatedNotifications SET OF absent stateChangeDefinition SET OF absent monitoredAttributes SET OF absent proposedRepairActions SET OF absent additionalText GraphicsString len=91 "The groomed circuit is unlocked with bandwidth allocated, but it is disabled. - Service XYZ" additionalInformation SET OF absent

iv) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 eventTime GeneralizedTime len=19 "19990422094131-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=2 [0] SEQ attributeID CHOICE



globalForm OID 2.9.3.2.7.31 oldAttributeValue ANY AdministrativeState ENUM 1 newAttributeValue ANY AdministrativeState ENUM 1 [1] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.35 oldAttributeValue ANY OperationalState ENUM 1 newAttributeValue ANY OperationalState ENUM 0 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

v) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 3 eventTime GeneralizedTime len=19 "19990422094131-0400" eventType CHOICE globalForm OID 2.9.3.2.10.1 eventInfo ANY AttributeValueChangeInfo SEQ sourceIndicator ENUM 1 attributeIdentifierList SET OF absent attributeValueChangeDefinition SET OF len=2 [0] SEQ attributeID CHOICE globalForm OID 0.0.13.3100.0.7.6 oldAttributeValue ANY NAlarmStatus ENUM 0 newAttributeValue ANY NAlarmStatus ENUM 1 [1] SEQ attributeID CHOICE



globalForm OID 0.0.13.3100.0.7.17 oldAttributeValue ANY CurrentProblemList SET OF len=1 [0] SEQ problem CHOICE globalValue OID 1.2.124.113537.1.9.7 alarmStatus ENUM 0 newAttributeValue ANY CurrentProblemList SET OF len=1 [0] SEQ problem CHOICE globalValue OID 1.2.124.113537.1.9.23 alarmStatus ENUM 2 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

vi) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.13 attributeValue ANY NameType CHOICE pString GraphicsString len=11 "N4 S1 C4 D1" eventTime GeneralizedTime len=21 "19990422094132.0-0500" eventType CHOICE globalForm OID 2.9.3.2.10.2 eventInfo ANY AlarmInfo SEQ probableCause CHOICE globalValue OID 2.9.3.2.0.0.6 specificProblems SET OF absent perceivedSeverity ENUM 2 backedUpStatus BOOL absent



backUpObject CHOICE absent trendIndication ENUM absent thresholdInfo SEQ absent notificationIdentifier INT absent correlatedNotifications SET OF absent stateChangeDefinition SET OF absent monitoredAttributes SET OF absent proposedRepairActions SET OF absent additionalText GraphicsString len=44 "ND2/3-1 appears to be faulty. - Port ND2/3-1" additionalInformation SET OF absent

vii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.3 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.13 attributeValue ANY NameType CHOICE pString GraphicsString len=11 "N4 S1 C4 D1" eventTime GeneralizedTime len=21 "19990422094132.0-0500" eventType CHOICE globalForm OID 2.9.3.2.10.2 eventInfo ANY AlarmInfo SEQ probableCause CHOICE globalValue OID 2.9.3.2.0.0.6 specificProblems SET OF absent perceivedSeverity ENUM 2 backedUpStatus BOOL absent backUpObject CHOICE absent trendIndication ENUM absent thresholdInfo SEQ absent notificationIdentifier INT absent correlatedNotifications SET OF absent stateChangeDefinition SET OF absent



monitoredAttributes SET OF absent proposedRepairActions SET OF absent additionalText GraphicsString len=63 "Status of 1 path(s) changed to Connected (down). - Port ND2/3-1" additionalInformation SET OF absent

19.5 Create

Create DS0

Figure 19-8 Simple M-CREATE (DS0)

Trace:

Code 19-11: M-CREATE for DS01) Request

CreateArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 instance CHOICE managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ

15355

OSS (Manager)

M-CREATE CreateArgumentmanagedGroomedCircuitTP

M-EVENT-REPORT(objectCreation)managedGroomedCircuitTP

M-CREATE CreateReasultmanagedGroomedCircuitTP

OSS Interface Agent



attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" accessControl EXTERNAL absent referenceObjectInstance CHOICE absent attributeList SET OF len=2 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" [1] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 1.2.124.360501.4.1682) Result

CreateResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ



attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" currentTime GeneralizedTime absent attributeList SET OF len=20 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.6 attributeValue ANY NAlarmStatus ENUM 0 [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.17 attributeValue ANY CurrentProblemList SET OF no space [2] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.19 attributeValue ANY DownstreamConnectivityPointer CHOICE none NULL [3] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.40 attributeValue ANY ObjectList SET OF len=1 [0] CHOICE distinguishedName SEQ OF len=6 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 [4] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY



NameType CHOICE pString GraphicsString len=12 "Card Slot: 1" [5] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 [4] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" [5] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.49 attributeValue ANY ConnectivityPointer CHOICE none NULL [6] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString no space [7] SEQ attributeId CHOICE globalForm OID 1.2.124.113537.1.4.2 attributeValue ANY GroomedCircuitTPProfile SET OF len=1 [0] SEQ type INT 2 value CHOICE realValue REAL 1 [8] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.157 attributeValue ANY TypeText IA5String len=3 "DS0" [9] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.313 attributeValue ANY DataMode CHOICE notApplicable NULL [10] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.317 attributeValue ANY FunctionalInterface CHOICE interface INT 2 [11] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.322 attributeValue ANY VoiceMode CHOICE notApplicable NULL



[12] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.327 attributeValue ANY UserIdentifier GraphicsString no space [13] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 1 [14] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.35 attributeValue ANY OperationalState ENUM 1 [15] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.39 attributeValue ANY UsageState ENUM 0 [16] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.50 attributeValue ANY Allomorphs SET OF len=1 [0] CHOICE globalForm OID 1.2.124.360501.3.75 [17] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 1.2.124.360501.4.168 [18] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.65 attributeValue ANY ObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 [19] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=6 [0] OID 0.0.13.3100.0.4.4 [1] OID 0.0.13.3100.0.4.10 [2] OID 0.0.13.3100.0.4.30 [3] OID 2.9.3.2.4.17 [4] OID 0.0.13.3100.0.4.28 [5] OID 0.0.13.3100.0.4.19

ii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1



[0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" eventTime GeneralizedTime len=19 "19990423155310-0400" eventType CHOICE globalForm OID 2.9.3.2.10.6 eventInfo ANY ObjectInfo SEQ sourceIndicator ENUM 1 attributeList SET OF len=20 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.6 attributeValue ANY NAlarmStatus ENUM 0 [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.17 attributeValue ANY CurrentProblemList SET OF no space [2] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.19 attributeValue ANY DownstreamConnectivityPointer CHOICE none NULL [3] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.40 attributeValue ANY ObjectList SET OF len=1 [0] CHOICE distinguishedName SEQ OF len=6 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE



pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 [4] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE pString GraphicsString len=12 "Card Slot: 1" [5] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 [4] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" [5] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.49 attributeValue ANY ConnectivityPointer CHOICE none NULL [6] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString no space [7] SEQ attributeId CHOICE globalForm OID 1.2.124.113537.1.4.2 attributeValue ANY GroomedCircuitTPProfile SET OF len=1 [0] SEQ type INT 2 value CHOICE realValue REAL 1



[8] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.157 attributeValue ANY TypeText IA5String len=3 "DS0" [9] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.313 attributeValue ANY DataMode CHOICE notApplicable NULL [10] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.317 attributeValue ANY FunctionalInterface CHOICE interface INT 2 [11] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.322 attributeValue ANY VoiceMode CHOICE notApplicable NULL [12] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.327 attributeValue ANY UserIdentifier GraphicsString no space [13] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 1 [14] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.35 attributeValue ANY OperationalState ENUM 1 [15] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.39 attributeValue ANY UsageState ENUM 0 [16] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.50 attributeValue ANY Allomorphs SET OF len=1 [0] CHOICE globalForm OID 1.2.124.360501.3.75 [17] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 1.2.124.360501.4.168 [18] SEQ attributeId CHOICE



globalForm OID 2.9.3.2.7.65 attributeValue ANY ObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 [19] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=6 [0] OID 0.0.13.3100.0.4.4 [1] OID 0.0.13.3100.0.4.10 [2] OID 0.0.13.3100.0.4.30 [3] OID 2.9.3.2.4.17 [4] OID 0.0.13.3100.0.4.28 [5] OID 0.0.13.3100.0.4.19

Create path

Figure 19-9 M-CREATE (bMGroomedCircuit)

Trace:

Code 19-12: M-CREATE for bMGroomedCircuit1) Request:

CreateArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 instance CHOICE superiorObjectInstance CHOICE distinguishedName SEQ OF len=2 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY

15356

OSS (Manager)

M-CREATE CreateArgumentbMGroomedCircuit

OSS Interface Agent

M-EVENT-REPORT(objectCreation)bMGroomedCircuit

M-CREATE CreateReasultbMGroomedCircuit



NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 accessControl EXTERNAL absent referenceObjectInstance CHOICE absent attributeList SET OF len=4 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString len=12 "New ATM Path" [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.1 attributeValue ANY RelatedObjectInstance CHOICE relatedObject CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 6 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N6 S1 C3 D1 PE1,1" [2] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.55 attributeValue ANY RelatedObjectInstance CHOICE relatedObject CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1



[0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N4 S1 C4 D1 PE1,1" [3] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.14 attributeValue ANY CircuitType SEQ mode INT 2 type INT 172) Result

CreateResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1354



currentTime GeneralizedTime absent attributeList SET OF len=23 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.1 attributeValue ANY RelatedObjectInstance CHOICE relatedObject CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 6 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N6 S1 C3 D1 PE1,1" [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.6 attributeValue ANY NAlarmStatus ENUM 0 [2] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.17 attributeValue ANY CurrentProblemList SET OF no space [3] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.18 attributeValue ANY Directionality ENUM 1 [4] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.35 attributeValue ANY SequenceOfObjectInstance SEQ OF no space [5] SEQ attributeId CHOICE



globalForm OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1354 [6] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString len=8 "New path" [7] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.55 attributeValue ANY RelatedObjectInstance CHOICE relatedObject CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N4 S1 C4 D1 PE1,1" [8] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.14 attributeValue ANY CircuitType SEQ mode INT 2 type INT 17 [9] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.157 attributeValue ANY TypeText IA5String len=3 "VCC" [10] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.314



attributeValue ANY Category ENUM 0 [11] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.315 attributeValue ANY Category ENUM 0 [12] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.321 attributeValue ANY Category ENUM 0 [13] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.327 attributeValue ANY UserIdentifier GraphicsString no space [14] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.328 attributeValue ANY CommonProfile SEQ reroute BOOL False backupBandwidth BOOL False circuitProfile SET OF len=3 [0] CHOICE circuitProfile SEQ cpType INT 1 cpValue REAL 0 [1] CHOICE circuitProfile SEQ cpType INT 2 cpValue REAL 3 [2] CHOICE circuitProfile SEQ cpType INT 3 cpValue REAL 1 [15] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.329 attributeValue ANY TDMProfile SEQ bandwidth CHOICE sameBandwidth CHOICE unknownBandwidthValue NULL circuitProfile SET OF len=2 [0] CHOICE circuitProfile SEQ cpType INT 21 cpValue REAL 2 [1] CHOICE circuitProfile SEQ cpType INT 22 cpValue REAL 2 [16] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.340



attributeValue ANY FrameRelayProfile SEQ bc REAL 0 be REAL 0 cir REAL 0 circuitProfile SET OF len=2 [0] CHOICE circuitProfile SEQ cpType INT 20 cpValue REAL 1 [1] CHOICE circuitProfile SEQ cpType INT 27 cpValue REAL 1 dlcia INT 0 dlciz INT 0 useatm BOOL False [17] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.341 attributeValue ANY ATMProfile SEQ vpia INT 0 vpiz INT 0 vcia INT 32 vciz INT 32 sir REAL 1000 pir REAL 1000 alm BOOL False qos INT 2 circuitProfile SET OF len=23 [0] CHOICE circuitProfile SEQ cpType INT 1 cpValue REAL 1 [1] CHOICE circuitProfile SEQ cpType INT 3 cpValue REAL 3 [2] CHOICE circuitProfile SEQ cpType INT 4 cpValue REAL 3 [3] CHOICE circuitProfile SEQ cpType INT 5 cpValue REAL 1000 [4] CHOICE circuitProfile SEQ cpType INT 6 cpValue REAL 250 [5] CHOICE circuitProfile SEQ cpType INT 9 cpValue REAL 1000 [6] CHOICE circuitProfile SEQ



cpType INT 10 cpValue REAL 32 [7] CHOICE circuitProfile SEQ cpType INT 2 cpValue REAL 1 [8] CHOICE circuitProfile SEQ cpType INT 34 cpValue REAL 1 [9] CHOICE circuitProfile SEQ cpType INT 42 cpValue REAL 2 [10] CHOICE circuitProfile SEQ cpType INT 48 cpValue REAL 5 [11] CHOICE circuitProfile SEQ cpType INT 55 cpValue REAL 2 [12] CHOICE circuitProfile SEQ cpType INT 56 cpValue REAL 2 [13] CHOICE circuitProfile SEQ cpType INT 59 cpValue REAL 2 [14] CHOICE circuitProfile SEQ cpType INT 73 cpValue REAL 2 [15] CHOICE circuitProfile SEQ cpType INT 74 cpValue REAL 2 [16] CHOICE circuitProfile SEQ cpType INT 91 cpValue REAL 1 [17] CHOICE circuitProfile SEQ cpType INT 75 cpValue REAL 2 [18] CHOICE circuitProfile SEQ cpType INT 77 cpValue REAL 2 [19] CHOICE circuitProfile SEQ cpType INT 78 cpValue REAL 2 [20] CHOICE circuitProfile SEQ cpType INT 103



cpValue REAL 2 [21] CHOICE circuitProfile SEQ cpType INT 104 cpValue REAL 2 [22] CHOICE circuitProfile SEQ cpType INT 81 cpValue REAL 1 [18] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 0 [19] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.35 attributeValue ANY OperationalState ENUM 1 [20] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 1.2.124.360501.4.170 [21] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.65 attributeValue ANY ObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 [22] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=8 [0] OID 1.2.124.360501.10.127 [1] OID 1.2.124.360501.10.128 [2] OID 1.2.124.360501.10.129 [3] OID 1.2.124.360501.10.130 [4] OID 0.0.13.3100.0.4.10 [5] OID 0.0.13.3100.0.4.4 [6] OID 0.0.13.3100.0.4.28 [7] OID 0.0.13.3100.0.4.303) Event Report

EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 managedObjectInstance CHOICE distinguishedName SEQ OF len=3 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1



[0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1354 eventTime GeneralizedTime len=19 "19990512130724-0400" eventType CHOICE globalForm OID 2.9.3.2.10.6 eventInfo ANY ObjectInfo SEQ sourceIndicator ENUM 1 attributeList SET OF len=23 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.1 attributeValue ANY RelatedObjectInstance CHOICE relatedObject CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 6 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N6 S1 C3 D1 PE1,1" [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.6 attributeValue ANY NAlarmStatus ENUM 0 [2] SEQ



attributeId CHOICE globalForm OID 0.0.13.3100.0.7.17 attributeValue ANY CurrentProblemList SET OF no space [3] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.18 attributeValue ANY Directionality ENUM 1 [4] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.35 attributeValue ANY SequenceOfObjectInstance SEQ OF no space [5] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.47 attributeValue ANY NameType CHOICE numericName INT 1354 [6] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString len=8 "New path" [7] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.55 attributeValue ANY RelatedObjectInstance CHOICE relatedObject CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 4 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE



pString GraphicsString len=17 "N4 S1 C4 D1 PE1,1"

[8] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.14 attributeValue ANY CircuitType SEQ mode INT 2 type INT 17 [9] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.157 attributeValue ANY TypeText IA5String len=3 "VCC" [10] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.314 attributeValue ANY Category ENUM 0 [11] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.315 attributeValue ANY Category ENUM 0 [12] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.321 attributeValue ANY Category ENUM 0 [13] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.327 attributeValue ANY UserIdentifier GraphicsString no space [14] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.328 attributeValue ANY CommonProfile SEQ reroute BOOL False backupBandwidth BOOL False circuitProfile SET OF len=3 [0] CHOICE circuitProfile SEQ cpType INT 1 cpValue REAL 0 [1] CHOICE circuitProfile SEQ cpType INT 2 cpValue REAL 3 [2] CHOICE circuitProfile SEQ cpType INT 3 cpValue REAL 1 [15] SEQ attributeId CHOICE



globalForm OID 1.2.124.360501.1.329 attributeValue ANY TDMProfile SEQ bandwidth CHOICE sameBandwidth CHOICE unknownBandwidthValue NULL circuitProfile SET OF len=2 [0] CHOICE circuitProfile SEQ cpType INT 21 cpValue REAL 2 [1] CHOICE circuitProfile SEQ cpType INT 22 cpValue REAL 2 [16] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.340 attributeValue ANY FrameRelayProfile SEQ bc REAL 0 be REAL 0 cir REAL 0 circuitProfile SET OF len=2 [0] CHOICE circuitProfile SEQ cpType INT 20 cpValue REAL 1 [1] CHOICE circuitProfile SEQ cpType INT 27 cpValue REAL 1 dlcia INT 0 dlciz INT 0 useatm BOOL False [17] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.341 attributeValue ANY ATMProfile SEQ vpia INT 0 vpiz INT 0 vcia INT 32 vciz INT 32 sir REAL 1000 pir REAL 1000 alm BOOL False qos INT 2 circuitProfile SET OF len=23 [0] CHOICE circuitProfile SEQ cpType INT 1 cpValue REAL 1 [1] CHOICE circuitProfile SEQ cpType INT 3 cpValue REAL 3



[2] CHOICE circuitProfile SEQ cpType INT 4 cpValue REAL 3 [3] CHOICE circuitProfile SEQ cpType INT 5 cpValue REAL 1000 [4] CHOICE circuitProfile SEQ cpType INT 6 cpValue REAL 250 [5] CHOICE circuitProfile SEQ cpType INT 9 cpValue REAL 1000 [6] CHOICE circuitProfile SEQ cpType INT 10 cpValue REAL 32 [7] CHOICE circuitProfile SEQ cpType INT 2 cpValue REAL 1 [8] CHOICE circuitProfile SEQ cpType INT 34 cpValue REAL 1 [9] CHOICE circuitProfile SEQ cpType INT 42 cpValue REAL 2 [10] CHOICE circuitProfile SEQ cpType INT 48 cpValue REAL 5 [11] CHOICE circuitProfile SEQ cpType INT 55 cpValue REAL 2 [12] CHOICE circuitProfile SEQ cpType INT 56 cpValue REAL 2 [13] CHOICE circuitProfile SEQ cpType INT 59 cpValue REAL 2 [14] CHOICE circuitProfile SEQ cpType INT 73 cpValue REAL 2 [15] CHOICE circuitProfile SEQ cpType INT 74 cpValue REAL 2 [16] CHOICE



circuitProfile SEQ cpType INT 91 cpValue REAL 1 [17] CHOICE circuitProfile SEQ cpType INT 75 cpValue REAL 2 [18] CHOICE circuitProfile SEQ cpType INT 77 cpValue REAL 2 [19] CHOICE circuitProfile SEQ cpType INT 78 cpValue REAL 2 [20] CHOICE circuitProfile SEQ cpType INT 103 cpValue REAL 2 [21] CHOICE circuitProfile SEQ cpType INT 104 cpValue REAL 2 [22] CHOICE circuitProfile SEQ cpType INT 81 cpValue REAL 1 [18] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 0 [19] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.35 attributeValue ANY OperationalState ENUM 1 [20] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 1.2.124.360501.4.170 [21] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.65 attributeValue ANY ObjectClass CHOICE globalForm OID 1.2.124.360501.3.77 [22] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=8 [0] OID 1.2.124.360501.10.127 [1] OID 1.2.124.360501.10.128 [2] OID 1.2.124.360501.10.129 [3] OID 1.2.124.360501.10.130



[4] OID 0.0.13.3100.0.4.10 [5] OID 0.0.13.3100.0.4.4 [6] OID 0.0.13.3100.0.4.28 [7] OID 0.0.13.3100.0.4.30 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent

19.6 Delete

Delete DS0

Figure 19-10 Simple M-DELETE (DS0)

Trace:

Code 19-13: M-DELETE for DS01) Request:

DeleteArgument SEQ baseManagedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 baseManagedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name"

15357

OSS (Manager)

M-DELETE DeleteArgumentmanagedGroomedCircuitTP

OSS Interface Agent

M-EVENT-REPORT(objectDeletion)managedGroomedCircuitTP

M-DELETE DeleteResultmanagedGroomedCircuitTP



[1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" accessControl EXTERNAL absent synchronization ENUM 0 scope CHOICE level INT 0 filter CHOICE and SET OF no space2) Result

i) DeleteResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" currentTime GeneralizedTime absent



ii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" eventTime GeneralizedTime len=19 "19990423155310-0400" eventType CHOICE globalForm OID 2.9.3.2.10.7 eventInfo ANY ObjectInfo SEQ sourceIndicator ENUM 1 attributeList SET OF len=20 [0] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.6 attributeValue ANY NAlarmStatus ENUM 0 [1] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.17 attributeValue ANY CurrentProblemList SET OF no space [2] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.19 attributeValue ANY DownstreamConnectivityPointer CHOICE none NULL [3] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.40 attributeValue ANY ObjectList SET OF len=1



[0] CHOICE distinguishedName SEQ OF len=6 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 [4] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE pString GraphicsString len=12 "Card Slot: 1" [5] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.20 attributeValue ANY NameType CHOICE numericName INT 1 [4] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C1 D1 PE2,2" [5] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.49 attributeValue ANY ConnectivityPointer CHOICE none NULL [6] SEQ attributeId CHOICE globalForm OID 0.0.13.3100.0.7.50 attributeValue ANY UserLabel GraphicsString no space [7] SEQ attributeId CHOICE globalForm OID 1.2.124.113537.1.4.2



attributeValue ANY GroomedCircuitTPProfile SET OF len=1 [0] SEQ type INT 2 value CHOICE realValue REAL 1 [8] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.157 attributeValue ANY TypeText IA5String len=3 "DS0" [9] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.313 attributeValue ANY DataMode CHOICE notApplicable NULL [10] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.317 attributeValue ANY FunctionalInterface CHOICE interface INT 2 [11] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.322 attributeValue ANY VoiceMode CHOICE notApplicable NULL [12] SEQ attributeId CHOICE globalForm OID 1.2.124.360501.1.327 attributeValue ANY UserIdentifier GraphicsString no space [13] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.31 attributeValue ANY AdministrativeState ENUM 1 [14] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.35 attributeValue ANY OperationalState ENUM 1 [15] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.39 attributeValue ANY UsageState ENUM 0 [16] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.50 attributeValue ANY Allomorphs SET OF len=1 [0] CHOICE globalForm OID 1.2.124.360501.3.75 [17] SEQ



attributeId CHOICE globalForm OID 2.9.3.2.7.63 attributeValue ANY NameBinding OID 1.2.124.360501.4.168 [18] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.65 attributeValue ANY ObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 [19] SEQ attributeId CHOICE globalForm OID 2.9.3.2.7.66 attributeValue ANY Packages SET OF len=6 [0] OID 0.0.13.3100.0.4.4 [1] OID 0.0.13.3100.0.4.10 [2] OID 0.0.13.3100.0.4.30 [3] OID 2.9.3.2.4.17 [4] OID 0.0.13.3100.0.4.28 [5] OID 0.0.13.3100.0.4.19

19.7 Action

Loopback action

Figure 19-11 Simple M-ACTION (loopback)

Trace:

15358

OSS (Manager)

M-ACTION ActionArgumentmanagedGroomedCircuitTP

OSS Interface Agent

M-EVENT-REPORT(stateChange)managedGroomedCircuitTP

M-ACTION ActionReasultmanagedGroomedCircuitTP



Code 19-14: M-ACTION for loopback1) Request:

ActionArgument SEQ baseManagedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 baseManagedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C5 D1 PE1,1" accessControl EXTERNAL absent synchronization ENUM 0 scope CHOICE level INT 0 filter CHOICE and SET OF no space actionInfo SEQ actionType CHOICE globalForm OID 1.2.124.360501.6.15 actionInfoArg ANY absent2) Result

i) ActionResult SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ



attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C5 D1 PE1,1" currentTime GeneralizedTime absent actionReply SEQ actionType CHOICE globalForm OID 1.2.124.360501.6.15 actionReplyInfo ANY LoopSetUp BOOL True

ii) EventReportArgument SEQ managedObjectClass CHOICE globalForm OID 1.2.124.113537.1.1.2 managedObjectInstance CHOICE distinguishedName SEQ OF len=4 [0] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "network name" [1] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.30 attributeValue ANY NameType CHOICE numericName INT 0 [2] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.28 attributeValue ANY NameType CHOICE numericName INT 7 [3] SET OF len=1 [0] SEQ attributeType OID 0.0.13.3100.0.7.48 attributeValue ANY NameType CHOICE pString GraphicsString len=17 "N7 S1 C5 D1 PE1,1" eventTime GeneralizedTime len=19 "19990423162252-0400" eventType CHOICE globalForm OID 2.9.3.2.10.14 eventInfo ANY StateChangeInfo SEQ



sourceIndicator ENUM 1 attributeIdentifierList SET OF absent stateChangeDefinition SET OF len=1 [0] SEQ attributeID CHOICE globalForm OID 2.9.3.2.7.31 oldAttributeValue ANY AdministrativeState ENUM 1 newAttributeValue ANY AdministrativeState ENUM 0 notificationIdentifier INT absent correlatedNotifications SET OF absent additionalText GraphicsString absent additionalInformation SET OF absent


Managed objects

20 — Managed object hierarchy



20.1 Introduction to the 5620 CMIP managed objects 20-2

20.2 Object class sources 20-4

20.3 MIB containment structure 20-6

20.4 Network modeling examples 20-10



20.1 Introduction to the 5620 CMIP managed objects

Network resources are modeled as managed objects in the 5620 CMIP MIB. The 5620 CMIP managed objects are composed of standard BME managed objects, extensions to BME objects and maintenance test objects.

In Volume 5, “Managed objects A to Z”, the objects are organized alphabetically, one chapter for each object.

Table 20-1 summarizes the managed objects used by the 5620 CMIP and shows where to find more information about each object.

Table 20-1 Managed objects summary

Object type Object Description Standard See chapter

System objects

alarmRecord A log record object that stores a CMIP alarm notification

ITU-T X.721 (1) 21

attributeValueChangeRecord A log record object that stores an attributeValueChange event notification

ITU-T X.721 (1) 22

eventForwardingDiscriminator Forwards selected event and alarm notifications to one or more specified OSSs

ITU-T X.721 (1) 28

log Stores selected event and alarm notifications as log record objects

ITU-T X.721 (1) 30

objectCreationRecord A log record object that stores an objectCreation event notification

ITU-T X.721 (1) 40

objectDeletionRecord A log record object that stores an objectDeletion event notification

ITU-T X.721 (1) 41

stateChangeRecord A log record object that stores a stateChange event notification

ITU-T X.721 (1) 45

system Models 5620 CMIP OSS Interface Gateway software on the Gateway Station

ITU-T X.721 (1) 46

(1 of 2)



Notes(1) ITU-T = International Telecommunications Union(2) TMF = TeleManagement Forum(3) Extensions = 5620 CMIP-defined extended managed objects

Network objects

bMFacility Models physical and logical links that are used for carrying a signal

TMF BME OP2 (2) 23

bMGroomedCircuit Models a path in the network TMF BME OP2 (2) 24

elementExtensions Models additional information associated with a node

Extensions (3) 26

equipmentHolder Models a shelf, card slot, power supply slot or fan slot

ITU-T M.3100 (1) 27

managedElement Models a node ITU-T M.3100 (1) 32

managedEquipment Models a resource or port when the resource or port cannot serve as a path or link endpoint

Extensions (3) 33

managedFacilityTP Models a physical or logical link endpoint

Extensions (3) 34

managedGroomedCircuitTP Models a path-end in the network Extensions (3) 35

managedPack Models a card, power supply or fan Extensions (3) 36

managedProfile Models a path or link profile Extensions (3) 37

network Models a 5620 NM-managed network or a partition in a 5620 NM-managed network

ITU-T M.3100 (1) 38

objectGroup Groups routerTemplate objects Extensions (3) 42

routerTemplate Models a router template Extensions (3) 43

Test objects busyOutTestObject Administers a busy-out test Extensions (3) 25

loopBackTestObject Administers a loopback test Extensions (3) 31

oAMCellTestObject Administers an OAM cell loopback test

Extensions (3) 39

splitMonitorTestObject Administers a split-back, split-through, or monitor test

Extensions (3) 44

testAccessConnectionObject Administers a monitor, split-back or split-loop test

Extensions (3) 47

testActionPerformer Administers the creation and deletion of the other test objects

ITU-T X.745 (1) 48

traceTestObject Administers path and connection tracing for SPVC paths

Extensions (3) 49

genericActionObject Administers listPaths and hitlessConnectionMove actions for paths

Extensions (3) 29

Object type Object Description Standard See chapter

(2 of 2)



GDMO and ASN.1

The ASN.1 and GDMO extensions to the BME are defined in the following ASN.1 and GDMO directories:

• /opt/netmgt/conexec/gdmo/asn• /opt/netmgt/conexec/gdmo/mo

Table 20-2 lists the 5620 CMIP ASN.1 and GDMO files.

Table 20-2 ASN.1 and GDMO files

For reference purposes, the BME ASN.1 and GDMO files are also contained in these ASN.1 and GDMO directories.

20.2 Object class sources

The 5620 CMIP object model uses the full service management object model described in the TMF BME, the alarm and event management components of the ITU-T X.721 (Definition of Management Information), and the object model described in X.745 (Test Management Function).

The 5620 CMIP also uses object class extensions to the BME, providing support for 5620 NM functionality that is not addressed by the standards. These extensions allomorph BME objects, ensuring interoperability with OSSs that conform to BME standards.

See section 2.3 for information about the standards to which the 5620 CMIP conforms.

Figures 20-1 and 20-2 illustrate the object model inheritance trees and indicate the standards from which the core and extension BME objects and maintenance test objects are derived.

asn file mo file

ce.asn ce.mo

boto.asn boto.mo

oamto.asn oamto.mo

lbto.asn lbto.mo

smto.asn smto.mo

taco.asn taco.mo

tto.asn tto.mo



Figure 20-1 BME object inheritance structure

15339

terminationPoint(M)

npipe(M)

mE(M)

equipment(M)

network(M)

discriminator(X)

system(X)

mPr(C)

logRecord(X)

log(X)

mP(C)

bMGCTP(B)

bMFacilityTP(B)

mGCTP(C)

mFTP(C)

connectionTerminationPointBidirectional(M)

trailTerminationPointBidirectional(M)

bMF(B)

bMGC(B)

circuitPack(M)

eH(M)

attributeValueChangeRecord(X)

alarmRecord(X)

stateChangeRecord(X)

objectCreationRecord(X)

objectDeletionRecord(X)

trailTerminationPointSink(M)

connectionR1(M)

trailR1(M)

equipmentR1(M)

mEq(C)

eventLogRecord(X)

eFD(X)

connectionTerminationPointSource(M)

connectionTerminationPointSink(M)

trailTerminationPointSource(M)

top(X)

= implemented by 5620 CMIP object mFTP = managedFacilityTP

mE = managedElement

mP = managedPack

bMF = bMFacility

eH = equipmentHolder

mEq = managedEquipment

bMGC = bMGroomedCircuit

bMGCTP = bMGroomedCircuitTP

mGCTP = managedGroomedCircuitTP

mPr = managedProfile

(B) = defined in NMF 038

(C) = defined by 5620 CMIP

(M) = defined in M.3100 by ITU-T

(X) = defined in X.721 by ITU-T



Figure 20-2 Maintenance test object inheritance structure

gAO = genericActionObjecttTO = traceTestObjecttACO = testAccessConnectionObjectoAMCTO = oAMCellTestObjectbOTO = busyOutTestObjectlBTO = loopBackTestObjectsMTO = splitMonitorTestObject

20.3 MIB containment structure

The managed objects are contained in a hierarchical tree structure in the 5620 CMIP MIB.

Figure 20-3 illustrates the root object, which is the base; it has two main branches of containment—the system object and the network object.

Figure 20-3 MIB hierarchical tree

The system object contains objects that the OSS uses to manage the 5620 CMIP event and alarm notification forwarding and logging. See chapter 46 for information about system objects.

The network object contains the objects that model the network, including links and paths. See chapter 38 for information about network objects.

Figures 20-4, 20-6, and 20-7 illustrate the generic containment and naming structure for objects. See volume 5 for detailed descriptions of each object.

16909

testObject(XX)

testActionPerformer(XX)

top(X)

sMTO(C)

gAO(C)

lBTO(C)

bOTO(C)

oAMCTO(C)

= implemented by 5620 CMIPobject

tACO(C)

tTO(C)

(C) = defined by 5620 CMIP

(XX) = defined by X.745

3886

Local root

network objectsystem object



System branch

The system object models the 5620 CMIP OSS Interface Gateway software. The Gateway Station is modeled as a managedElement object contained by the second-level network object.

Figure 20-4 shows the containment structure for the system object, which contains the log object class and the eventForwardingDiscriminator object class. The log object contains event logRecord objects and alarm logRecord objects. Chapter 17 describes events and alarms in detail.

Figure 20-4 The 5620 CMIP system object MIB model

Network branch

The network object branch contains all physical and logical resources in the network.

Figure 20-5 shows the containment for the network branch of the MIB. This branch contains four objects that are permanently instantiated:

• first-level network object• second-level network object (partition)• testActionPerformer object• profile network object

3887

log eventForwardingDiscriminator

objectCreationRecordstateChangeRecord

atributeValueChangeRecordobjectDeletionRecord

= Event logRecord objects

alarmRecord

system



The first-level network object models the entire network and contains both the second-level network object and the testActionPerformer object.

The second-level network object models either a single network partition, as defined by the 5620 NM, or the entire supply network, comprising all partitions. Figure 20-6 shows the network partition MIB containment structure.

The testActionPerformer object initiates and terminates instances of objects that model specific tests, such as split/monitor, loopback, busy-out, and OAM loopback tests. Figure 20-7 shows the testActionPerformer object MIB containment structure.

The profile network object contains managedProfile objects that model 5620 NM link profiles.

Figure 20-5 The 5620 CMIP network object MIB model

Note — When a second-level network object models the entire 5620 NM network, 5620 NM partitions are not modeled.

testActionPerformer

10798

Network

Network(profile)

Network(partition)



Figure 20-6 network (partition) MIB containment structure

1

2

3

4

5

6

7

8

12819


mFTP = managedFacilityTP

mE = managedElement

bMF = bMFacility


Note : This containment tree has been separated for clarity. Both network (partition)and testActionPerformer are part of the same network MIB.


mP = managedPack


mPr = managedProfile

eExts = elementExtensions

testActionPerformer

bMF(link)

network(profile)

mPr(profile)

bMGC(path)

eH(card slot)

eH(ps slot)

eH(fan slot)

mP(card)

mP(power supply)

mP(fan)

network

mFTP(link endpoint)

eExts(additional node information)

eH(shelf)

mEq(resource)

mEq(resource)

network(partition)

mEq(device)

mE(node)

mGCTP(path endpoint)



Figure 20-7 testActionPerformer object MIB containment structure

sMTO = splitMonitorTestObjectlBTO = loopBackTestObjectbOTO = busyOutTestObjectoAMCTO = oAMCellTestObjecttACO = testAccessConnectionObjecttTO = traceTestObjectgAO = genericActionObject

20.4 Network modeling examples

This section details sample TDM, frame relay, and ATM network transmission technologies that are modeled by the 5620 CMIP.

TDM network objects

Figure 20-8 shows a sample TDM network in a T1 environment, consisting of:

• a 5620 NM NetworkStation• two 3600 MainStreet nodes• two T1 cards (one on each node)• a T1 link between the nodes• two LGS cards (one on each node)• two LGS ports (one on each LGS card)• an LGS path from one LGS port to the other, routed across the T1 link

2

1

3

Note : This containment tree has been separated for clarity. Both network (partition)and testActionPerformer are part of the same network MIB.

16908

oAMCTO

testActionPerformer

network

network(partition)

sMTO bOTO tACO tTO gAOlBTO



Figure 20-8 Sample TDM network

Figure 20-9 shows how this sample TDM network is modeled in the MIB.

Figure 20-9 Sample TDM network MIB model

The logical termination points for the LGS groomed circuit correspond to the physical LGS port terminating equipment on the LGS cards. The DS1s are modeled as termination points for both ends of the link.

LG

ST1

3600 MainStreetNode 1

T1

LG

S


T1 link


15331

15334

MFTPT1 link

endpoint

MFTPT1 link

endpoint

bMGroomedCircuit:TDM path



MGCTP :LGS 1 port

MGCTP :LGS 2 port

equipmentHolder :Shelf

equipmentHolder :Shelf

managedElement :OSS Interface

bMFacility :T1 link

managedElement :3600 node 1

managedElement :3600 node 2

Network :Partition

equipmentHolder :card slot




equipmentHolder :power supply

slot

equipmentHolder :power supply

slot

managedPack :T1 card

managedPack :power supply

managedPack :power supply

managedPack :LGS card

managedPack :T1 card

managedPack :LGS card

managedElement :Network Manager

Network :Entire

Network



Sample DS3/E3 TDM MIB

Figure 20-10 shows how the two terminating equipment objects on a DS3 card are modeled in the MIB. Both the DS1 and DS3 terminating equipment objects are contained by the managedElement object that models the DS3 card (the DS2 level is not modeled). The figure also shows how the 3600 MSS SU and 3600 MSS PU that are associated with the 3600 MSS node are modeled.

An E3 card and a DS3 card are similarly modeled.

Figure 20-10 MIB model of a DS3/E3 card

8822

equipmentHolder :shelf

managedFacilityTPDS1 port



equipmentHolder :Card slot

equipmentHolder :power supply slot

managedPackpower supply

managedElement :3645 SU node

managedElement :3645 PU node

Network :Partition

managedElement :3645 HSPS

DS3 card node

managedEquipmentDS2 port




managedPackDS3 card



Frame relay network

Figure 20-11 shows a sample frame relay network in a T1 environment, consisting of:

• a 5620 NM NetworkStation• two 3600 MainStreet nodes• two T1 cards (one in each node)• a T1 link between the nodes• two FRE cards (one in each node)• two FRE ports (one on each FRE)• two X.21 direct connect cards (one on each node)• two X.21 ports (one on each X.21 DCC)• frame relay links between each FRS port and its corresponding X.21 port, and

between the two FRS ports over the T1 link

Figure 20-11 Sample frame relay network

Figure 20-12 shows how this sample frame relay network is modeled in the MIB.

X.2

1

FR

ST1


T1

FR

S

X.2

1


T1 link


15335



Figure 20-12 Sample frame relay network MIB model

ATM network

Figure 20-13 shows a sample ATM network, consisting of:

• a 5620 NM NetworkStation• two 7470 MSP nodes• two OC3 cards (one on each node)• an OC3 link between the nodes• two DS3 cards (one on each node)• two DS3 ports (one on each DS3 card)• an ATM path from one DS3 port to the other using the OC3 link

15336

mFTP:X.21 port

mFTP:T1 link

endpoint

mFTP:X.21 port

mGCTP:X.21 port

mFTP:FSC

eH :card slot

eH :card slot

mGCTP:X.21 port

mFTP:FSC

mFTP:T1 link

endpoint

eH :Shelf

eH :Shelf

eH :card slot

eH :card slot

eH :card slot

eH :card slot

eH :power supply

slot

eH :power supply

slot

mP :T1 card

mP :powersupply

mP :FRS card

mmP :FRS card

mEq :FRS

resources

mEq :FRS

resources

mP :powersupply

mP :X.21 card

mP :T1 card

mP :X.21 card



mE = managedElement

bMF = bMFacility



mP = managedPack


bMGC :FR path

mE :OSS

Interface

bMF :T1 link

mE :3600

node 1

mE :3600

node 2

mE :NetworkManager

bMF :FRL

Network :Partition

Network :Entire

Network



Figure 20-13 Sample ATM network

Figure 20-14 shows how this sample ATM network is modeled in the MIB.

7470 MSPNode 1

7470 MSPNode 2

ATM full link


OC

3

DS

3

DS

3

OC

3

15439

CPE CPE



Figure 20-14 Sample ATM network MIB model

mGCTP:DS3 port

mFTP:DS3 port

bMGC:ATM VCC



mE = managedElement

bMF = bMFacility



mP = managedPack

mGCTP:OC3 port

mFTP:OC3 port

eH :Shelf

mEOSS

Interface

bMF :ATM link

VPC

bMF :ATM

full link

mE7470 MSP

node 1

mE7470 MSP

node 2

Network :Partition

eH :card slot

eH :card slot

eH :Power supply

slot

mP :OC3 card

mP :Power supply

mP :DS3 card

mENetworkManager

Network :Entire

Network

The node 2 containment heirarchyis identical to that of Node 1.

15440



7390 LMDS wireless networkFigure 20-15 shows a sample 7390 LMDS network, consisting of:

• one 5620 NM NetworkStation• one 7470 MSP node containing:

• one OC3 card• one T1CE card

• one 7390 DBS containing:• one ANT card• one AMD card

• three 7390 NTs, each containing:• one AIR port (logical)• one ethernet port• one T1CE port or one E1CE port or one T1 port

• one ATM full link from an OC3 port to an ANT port

Figure 20-15 Sample 7390 LMDS wireless network

Figure 20-16 shows how this sample 7390 LMDS wireless network is modeled in the MIB.

7470 MSP 7390 DBS

ATM full link

ATM VCC

5620 NM /5620 SNMP DMNetworkStation

16799

7390 NT1 7390 NT2 7390 NT3

Ethernetport

TICEport

AIR port(logical)

Ethernetport

EICEport

AIR port(logical)

Ethernetport

TIport

AIR port(logical)

OC3

TICE

AMD

ANT

Wireless fractionallink





Figure 20-16 Sample 7390 LMDS wireless network MIB model

1 2 3 4 5 6 3 4 5 6

Net

wor

k :

Par

titio

n

Net

wor

k :

Ent

ireN

etw

ork

mE

:74

70 M

SP

The

739

0 N

T2

and

7390

NT

3co

ntai

nmen

t hei

rarc

hy is

sim

ilar

to th

at o

f 739

0 N

T1

mE

:73

90 N

T3

mE

:73

90 N

T2

eH:

card

slo

teH

:ca

rd s

lot

eH:

card

slo

teH

:P

ower

sup

ply

slot

mF

TP

:O

C3

port

mF

TP

:T

ICE

por

tm

GC

TP

:T

ICE

por

tm

GC

TP

:O

C3

port

eExt

seH

:sh

elf

mP

:O

C3

card

eH:

card

slo

tm

P:

TIC

E c

ard

mP

:P

ower

sup

ply

eH:

card

slo

teH

:ca

rd s

lot

eH:

card

slo

teH

:ca

rd s

lot

mP

:A

IR c

ard

eH:

card

slo

tm

P:

TIC

E c

ard

mP

:E

ther

net c

ard

mE

:73

90 N

TI

mF

TP

:O

C3

port

mF

TP

:T

ICE

por

tm

FT

P:

Eth

erne

t por

tm

GC

TP

:E

ther

net p

ort

mG

CT

P:

TIC

E p

ort

eExt

seH

:sh

elf

eH:

card

slo

teH

:ca

rd s

lot

eH:

card

slo

t

mP

:A

NT

car

dm

P:

AM

D c

ard

mE

:73

90 D

BS

mF

TP

:A

MD

por

tm

FT

P:

AN

T p

ort

mG

CT

P:

AN

T p

ort

eExt

seH

:sh

elf

mG

CT

P =

man

aged

Gro

omed

Circ

uitT

P

mF

TP

= m

anag

edF

acili

tyT

P

mE

= m

anag

edE

lem

ent

bM

F =

bM

Fac

ility

mP

r =

man

aged

Pro

file

eExt

s =

ele

men

tExt

ensi

ons

bM

GC

= b

MG

room

edC

ircui

t

eH =

equ

ipm

entH

olde

r

mP

= m

anag

edP

ack

mE

q =

man

aged

Equ

ipm

ent

1680

0


Managed objects A to Z

21 — alarmRecord object

22 — attributeValueChangeRecord object

23 — bMFacility object

24 — bMGroomedCircuit object

25 — busyOutTestObject

26 — elementExtensions object

27 — equipmentHolder object

28 — eventForwardingDiscriminator object

29 — genericActionObject

30 — log object

31 — loopBackTestObject

32 — managedElement object

33 — managedEquipment object

34 — managedFacilityTP object

35 — managedGroomedCircuitTP object

36 — managedPack object


37 — managedProfile object

38 — network object

39 — oAMCellTestObject

40 — objectCreationRecord object

41 — objectDeletionRecord object

42 — objectGroup object

43 — routerTemplate object

44 — splitMonitorTestObject

45 — stateChangeRecord object

46 — system object

47 — testAccessConnectionObject

48 — testActionPerformer object

49 — traceTestObject




21.2 Supported CMIP operations 21-2

21.3 Attributes 21-2



21.1 Introduction

The alarmRecord objects are CMIP event notifications logged by the log object. See chapter 30 for information about the log object. When logged, the following event notifications become alarmRecord objects:

• equipmentAlarm• communicationsAlarm• processingErrorAlarm

The alarmRecord object is contained by the log object.

An instance of an alarmRecord object is created for the event notifications listed above if the event notifications match the criteria specified in the discriminatorConstruct attribute of the log object. See Table 30-2 for details about log object attributes.

21.2 Supported CMIP operations

The supported CMIP operations are:

• delete• get• cancel get

21.3 Attributes

Table 21-1 describes the attributes of the alarmRecord object.

Table 21-1 alarmRecord object attributes

Attribute Description Access Value description

additionalInformation Contains the problem code and 5620 NM selected object name

Read See Appendix D and Appendix E for details

additionalText Is a textual description of the problem and 5620 NM selected object name

Read See Appendix D and Appendix E for details

eventTime Is the time the event occurred Read Time

eventType Is the type of event Read One of the following OIDs: communicationsAlarm, processingErrorAlarm, or equipmentAlarm

loggingTime Is the time the event was logged Read Time

logRecordId Naming attribute; unique identifier for an instance of an alarmRecord object

Read Integer assigned by the 5620 CMIP OSS Interface Gateway

managedObjectClass Identifies the class of managed object that generated the alarm

Read Object class OID

(1 of 2)



managedObjectInstance Identifies the object instance that caused the alarm to be generated

Read An ObjectInstance distinguishedName uniquely identifying the alarmed object instance

monitoredAttributes Defines one or more attributes of the managed object and the corresponding values at the time of the alarm

Read See Appendix E.3 for details

nameBinding Identifies the kind of name binding used by an alarmRecord object

Read Name binding

objectClass Indicates the class of object Read Always the OID for alarmRecord

packages Identifies the packages used by the alarmRecord object

Read List of packages; see the GDMO for information

perceivedSeverity Indicates the level of seriousness of the event

Read 0 = indeterminate

1 = critical

2 = major

3 = minor

4 = warning

5 = clear

See Appendix E for details

probableCause Identifies the likely cause of the alarm Read An OID that corresponds to a general probable cause as specified in X.721 and X.733; see Appendix D and Appendix E for details

thresholdInfo Present when the alarm is a result of crossing a threshold value

Read See Appendix E.6 for details


(2 of 2)



22.1 Introduction

The attributeValueChangeRecord object is a CMIP event notification logged by the log object. See chapter 30 for more information about the log object.

An instance of an attributeValueChangeRecord object can only be created for an attributeValueChange notification if the notification matches the criteria specified in the discriminatorConstruct attribute of the log object.


The attributeValueChangeRecord object supports the following CMIP operations:


22.3 Attributes

Table 22-1 describes the attributes of the attributeValueChangeRecord object.

Table 22-1 attributeValueChangeRecord object attributes


attributeValueChangeDefinition Is the OID for the attribute and the old and new values

Read OID, oldAttributeValue, newAttributeValue

eventTime Identifies the time the event occurred

Read Time

eventType Is the type of event Read attributeChange


logRecordId Naming attribute; unique identifier for an instance of attributeValueChangeRecord object


managedObjectClass Identifies the kind of object that generated the event notification

Read Object class

managedObjectInstance Identifies the instance of the object that generated the event notification

Read distinguishedName uniquely identifying the alarm object instance

nameBinding Identifies the kind of name binding used by an attributeValueChangeRecord object

Read Name binding

objectClass Is the kind of object Read Always the OID for attributeValue ChangeRecord

(1 of 2)



packages Identifies the packages used by the attributeValueChangeRecord object



Read 0 = resourceOperation


2 = unknown


(2 of 2)





23.3 Event notifications 23-2


23.5 serverTrailList 23-5

23.6 trmCircuitProfile attribute 23-6

23.7 currentProblemList attribute 23-35



23.1 Introduction

The bMFacility object models physical and logical links. Logical links can be frame relay, MFR links, ATM, and IMA links. HCM links and subrate links are not supported. Both the 5620 NM and the OSS can create logical link bMFacility objects, but only the 5620 NM can create physical link bMFacility objects.

The a-TPInstance attribute is the name of the managedFacilityTP object at one end of the physical or logical link. The z-TPInstance attribute identifies the other end of the bMFacility object. For fractional links, which have DS0s as endpoints, the endpoint names refer to DS1 managedFacilityTP objects and the typeText attribute contains the A-end timeslot, the Z-end timeslot, and the number of timeslots.

The connection behavior of logical link bMFacility objects is identical to the paths modeled by the bMGroomedCircuit. See chapter 13 for details about the bMFacility administrative and operationalState attributes.

The bMFacility object is contained by the partition-level network object.

See chapter 34 for information about the managedFacilityTP object.


The bMFacility object supports the following CMIP operations:

• create• delete• get• cancel get• set• action on the network object — FindByLabel to retrieve the connectionID given

the userLabel

23.3 Event notifications

A bMFacility object can generate the following event notifications:

• objectCreation• objectDeletion• attributeValueChange• communicationsAlarm• stateChange

23.4 Attributes

Table 23-1 describes the bMFacility object attributes.



Table 23-1 bMFacility object attributes


administrativeState Reflects the availability of the bMFacility object, as imposed through management services

Read-write default: logical links = locked

0 = locked

1 = unlocked

Physical links are always unlocked; disconnected logical links are always locked.

alarmStatus Operates as a summary indicator of alarm conditions

Read Tied to operationalState (cleared or activeReportable-Indeterminate)

a-TPInstance Refers to the managedFacilityTP object at one end of a link

Read distinguishedName of managedFacilityTP

circuitBandwidth Indicates the bandwidth available on the physical link

Read Null for logical links and fractional physical links

For full links, the bandwidth available are the standard values for T1, E1, T3, E3, for example.

connectionId Naming attribute: unique identifier for an instance of a bMFacility object class

Read Cable: #

IMA Link: # (1)

FRL: #

MFR Link: #

ATM Link: #

VCC Link: #

PSN Link: #

Subrate link: #

where # is the physical link ID or logical link ID, which is a unique integer assigned by the 5620 NM

currentProblemList Identifies the probableCause of an alarm for a bMFacility object instance

Read The probableCause OID describing the current alarm state for the path; see Table 23-15 for details

directionality Indicates the direction of the link Read Always bidirectional

(1 of 3)



facilityType Models the facility type through a hierarchy field and media field

Read Subrate link:

• hierarchy = 25 (subrate link)• media = 10 (virtual)

Physical cables

• hierarchy = 0 (unspecified) • media = 0 (unspecified)

FRL

• hierarchy = 19 (frame relay) • media = 10 (virtual)

MFR link

• hierarchy = 23 (MFR Link) • media = 10 (virtual)

ATM VPC link

• hierarchy = 20 (ATM) • media = 10 (virtual)

ATM VCC link

• hierarchy = 22 (ATM) • media = 10 (virtual)

IMA link

• hierarchy = 21 (IMA link) • media = 10 (virtual)

PSN link

• hierarchy = 24• media = 10

nameBinding Identifies the kind of name binding used by a bMFacility object

Read Name binding

objectClass Is the kind of object Read The class of object

operationalState Indicates the status of the object in the network

Read 0 = disabled

1 = enabled

packages Identifies the packages used by the bMFacility object


serverTrailList Lists the bMGroomedCircuit and the bMFacility objects that are routed over the bMFacility; see section 23.5 for additional information

Read A list of connected bMFacility and/or bMGroomedCircuit distinguished names

trmCircuitProfile Models detailed characteristics of the bMFacility object; see section 23.6 for additional information

Read-write See section 23.6 for additional information

typeText Is a textual description of the facility; in the case of fractional links, it also describes the number of contiguous DS0s and the A and Z DS0s

Read For links: link type + link name

Type text attribute for primary fractional links:

cable type + A: start DS0 + Z: end DS0 + Size:” number of DS0s

Type text attribute for ATM fractional links:

cable type Bandwidth: speed in kbps


(2 of 3)



Note(1) Supported in 5620 NM Release 4.1 H1; before this release, IMA links are represented as Cable #

23.5 serverTrailList

This attribute lists the bMGroomedCircuit and the bMFacility objects that are routed over the bMFacility.

The MIB does not store or maintain this attribute. Each time an OSS performs an M-GET that includes the serverTrailList attribute, the serverTrailList attribute is regenerated.

Like all other attributes, an M-GET operation includes the serverTrailList attribute in one of two ways:

• attributeList is empty (M-GET retrieves all attributes)• attributeList names the attribute id for the serverTrailList

The serverTrailList for physical bMFacility objects (cables) can include:

• logical bMFacility objects, such as FRLs and VPCLs• bMGroomedCircuit objects

A logical bMFacility only lists the bMGroomedCircuit object that routes over it.

userIdentifier Allows the OSS to assign a label to the link

Read-write default = empty string

String up to 255 characters; only an OSS can modify

This attribute is read only for the 5620 NM.

userLabel Allows the OSS or the 5620 NM operator to assign a name to an object instance

Read-write default = 5620 NM assigned object name

String

This attribute can be set by the OSS or the 5620 NM operator.

If the unique naming feature of the 5620 NM is enabled and the OSS attempts to create a link with a duplicate name, the 5620 CMIP will fail the request. See the 5620 NM Advanced Configuration Procedures guide for more information about enabling the unique naming feature.

z-TPInstance Refers to the managedFacilityTP object at the other end of a link



(3 of 3)

Note — Unlike other attributes maintained by the 5620 CMIP, an M-GET on this attribute causes activity on the 5620 NM. The 5620 NM generates the list of objects included in this attribute. To improve performance, OSS design should ensure that this attribute is queried only when necessary.



23.6 trmCircuitProfile attribute

The standard bMFacility profile, trmCircuitProfile attribute, provides additional information about link characteristics. The attribute may be either a circuitProfile or a circuitProfileName characteristic.

Tables 23-2, 23-3, and 23-7 to 23-12 to describe the trmCircuitProfile attribute circuitProfile characteristics for the different link types, while Table 23-6 describes the trmCircuitProfile attribute circuitProfileName characteristics for ATM VPC links.

Common trmCircuitProfile attribute circuitProfile characteristicsTable 23-2 describes the common trmCircuitProfile attribute circuitProfile characteristics for bMFacility objects.

Table 23-2 Common trmCircuitProfile attribute circuitProfile characteristics

Note 1 — To obtain a complete list of bMGroomedCircuit objects routed over a physical bMFacility object, you must query all serverTrailList attributes of all listed logical bMFacility objects riding over the physical bMFacility object.

Note 2 — During an optimized scoped get operation, the serverTrailList will always be empty for bMFacility managed objects. To get the details in the serverTrailList, perform an individual M-GET for each bMfacility object.


Reroute/Recovery 1 1, 2 1 = do not try to reroute around network failures

2 = try to reroute around network failures (default)

Backup bandwidth/RAPID

2 1, 2 1 = do not reserve backup bandwidth (default)

2 = reserve backup bandwidth

Reroute with facilities matching custom label 4

3 0, 3, 4 0 = do not care (default for all except for IMA links)

3 = matching is required or Yes (default for IMA links)

4 = matching is not required or No

Custom labels may be defined only on the 5620 NM.

Custom label 4 = customer-specified reroute level.

Empty link priority 4 1 to 16, 255

1 = highest priority

16 = lowest priority

255 = minimum priority (default)

(1 of 2)



trmCircuitProfile attribute circuitProfile characteristics for frame relay links

Table 23-3 describes the trmCircuitProfile attribute circuitProfile characteristics for frame relay links.

Table 23-3 trmCircuitProfile attribute circuitProfile characteristics for frame relay links

Priority range minimum

5 1 to 16 default = 16

Identifies the priority range of the path that rides over the subrate link.

Must be less than or equal to the maximum.

Priority range maximum


Identifies the priority range of the path that rides over the subrate link.

Must be greater than or equal to the minimum.


(2 of 2)


Optimize 7 1, 2 1 = do not optimize after reroute

2 = optimize after reroute (default)

Subrate 8 1, 2 1 = do not use subrate multiplexing

2 = use subrate multiplexing (default)

(1 of 6)



Rate adaptation type 9 1 to 4 1 = I.460

2 = X.50

3 = DDS

4 = HCM

5 = HCM/I.460

6 = DDS DS0B 19.2 kb/s


8 = DDS DS0B 4,8 kb/s


Values 1 to 4 are valid for frame relay links.

Values 1, 2, 4 to 9 are valid for subrate links.

When the value of the Rate Adaptation Type is set to 4 (HCM) and when the value of the Speed Range Minimum is greater than the value of the HCM Bandwidth, the value of the Speed Range Minimum is set to the vaue of HCM Bandwidth.

When the value of the Rate Adaptation Type is set to 4 and when the value of the Speed Range Maximum is greater than the value of HCM Bandwidth, the value of the Speed Range Maximum is set to the value of HCM Bandwidth.

When the value of the Rate Adaptation Type is set to 1 or 5 and when the value of the Speed Range Minimum is greater than the value of Transport Bandwidth, the value of the Speed Range Minimum is set to the value of Transport Bandwidth.

When the value of the Rate Adaptation Type is set to 1 or 5 and when the value of the Speed Range Maximum is greater than the value of Transport Bandwidth, the value of the Speed Range Maximum is set to the value of Transport Bandwidth.

See Table 23-4 for more information

Transport bandwidth 10 1 to 8 1 = 8 kb/s

2 = 16 kb/s

3 = 24 kb/s

4 = 32 kb/s

5 = 40 kb/s

6 = 48 kb/s

7 = 56 kb/s

8 = 64 kb/s (default)

Interface speed 11 0 to 2048000 Frame relay link interface speed for either T1 or E1

Up to 2048 kb/s in increments of 8 kb/s

For frame relay links using subrate, the maximum is 64 kb/s; for frame relay links with a timeslot \, interface speed equals the transport bandwidth multiplied by the number of DS0s.

Aggregate position for path-end X

12 1 to 80 Endpoint SRM aggregate data start position (frame)

Table 23-4 describes how this value is mapped to the 5620 NM GUI.

CIR range minimum 13 0 to 1984000 Committed information rate range minimum

Must be less than maximum

CIR range maximum 14 0 to 1984000 Committed information rate range maximum

Must be greater than minimum


(2 of 6)



Best-effort routing booking factor

15 1 to 2000 default = 100

Percentage of FRL used by FRPs

Best-effort reroute booking factor

24 1 to 2000 default = 100

Source best-effort ACT 34 0 to 60000 default = 1280 ms

Actual congestion threshold in milliseconds

Source best-effort SCT 35 default = 1024 ms

Severe congestion threshold in milliseconds

Source best-effort MCT 36 default = 640 ms

Mild congestion threshold in milliseconds

Destination best-effort ACT

37 default = 1280 ms

Actual congestion threshold in milliseconds

Destination best-effort SCT

38 default = 1024 ms

Severe congestion threshold in milliseconds

Destination best-effort MCT

39 default = 640 ms

Mild congestion threshold in milliseconds

Source committed- throughput ACT

40 Actual congestion threshold in milliseconds

Source committed- throughput SCT

41 Severe congestion threshold in milliseconds

Source committed- throughput MCT

42 Mild congestion threshold in milliseconds

Destination committed- throughput ACT


Destination committed- throughput SCT


Destination committed- throughput MCT


Committed-throughput routing booking factor

46 1 to 2000 Frozen if endpoint is configured for X.25 encapsulation

The cpValue range is from 1 to 2000%.

Committed-throughput reroute booking factor

47

Source low-delay ACT 48 0 to 60000 Actual congestion threshold in milliseconds

Source low-delay SCT 49 Severe congestion threshold in milliseconds

Source low-delay MCT 50 Mild congestion threshold in milliseconds

Destination low-delay ACT


Destination low-delay SCT


Destination low-delay MCT


Source low-delay queuing delay

54 1 to 10000 default = 150 ms

Destination low-delay queuing delay

55


(3 of 6)



Low-delay routing booking factor



Low-delay reroute booking factor

57

Source real-time ACT 58 1 to 60000 Actual congestion threshold in milliseconds

Source real-time SCT 59 Severe congestion threshold in milliseconds

Source real-time MCT 60 Mild congestion threshold in milliseconds

Destination real-time ACT


Destination real-time SCT


Destination real-time MCT


Source real-time queuing delay

64 1 to 10000 default = 150 ms

Destination real-time queuing delay

65

Real-time routing booking factor



Real-time reroute booking factor

67

Frame relay application 104 1, 2 Application of frame relay link

1 = PVC

2 = SVC

Only PVC is supported on the 3-DS3 frame processing card.

Source best-effort filtering

113 0, 1 0 = filtered

1 = unfiltered

Best-effort congestion filtering is supported on FRE cards of Release 2.2 or later.

Source best-effort reporting method

114 0 to 2 0 = log alarms

1 = log trouble tickets

2 = no log

Best-effort congestion reporting is supported on FRE cards of Release 2.2 or later and on FRM cards of Release 2.0 or later.

Source best-effort clear time

115 0 to 1440 default = 15 min

Best-effort congestion clear time is supported on FRE cards of Release 2.2 or later.

Source best-effort raise time

116 0 to 255 default: filtered raise time = 5 s

default: unfiltered raise time = 0 s

Best-effort congestion raise time is supported on FRE cards of Release 2.2 or later.

Destination best-effort filtering

117 0, 1 0 = filtered

1 = unfiltered

Best-effort congestion filtering is supported on FRE cards of Release 2.2 or later.


(4 of 6)



Destination best-effort reporting method



2 = no log

Best-effort congestion reporting is supported on FRE cards of Release 2.2 or later and on FRM cards of Release 2.0 or later.

Destination best-effort clear time


Best-effort congestion clear time is supported on FRE cards of Release 2.2 or later.

Destination best-effort raise time



Best-effort congestion raise time is supported on FRE cards of Release 2.2 or later.

Source real-time filtering 121 0, 1 0 = filtered

1 = unfiltered

Real-time congestion filtering is supported on FRE cards of Release 3.1 or later.

Source real-time reporting method



2 = no log

Real-time congestion reporting is supported on FRE cards of Release 3.1 or later and on FRM cards of Release 2.0 or later.

Source real-time clear time


Real-time congestion clear time is supported on FRE cards of Release 3.1 or later.

Source real-time raise time



Real-time congestion raise time is supported on FRE cards of Release 3.1 or later.

Destination real-time filtering

125 0, 1 0 = filtered

1 = unfiltered

Real-time congestion filtering is supported on FRE cards of Release 3.1 or later.

Destination real-time reporting method



2 = no log

Real-time congestion reporting is supported on FRE cards of Release 3.1 or later and on FRM cards of Release 2.0 or later.

Destination real-time clear time


Real-time congestion clear time is supported on FRE cards of Release 3.1 or later.

Destination real-time raise time



Real-time congestion raise time is supported on FRE cards of Release 3.1 or later.


(5 of 6)



Maximum number of best-effort connections

129 0 to 992 0 = unlimited (default)

Maximum number of committed-throughput connections

130

Maximum number of low-delay connections

131

Maximum number of real-time connections

132

May use ATM 137 1, 2 1 = no

2 = yes (default)

Set to 2 for VSC and ATM endpoints

Must use VPC link 138 1, 2 1 = VCC path does not need to be routed over an ATM VPC link (default)

2 = VCC path must be routed over an ATM VPC link

CDVT 139 1 to 2000000 default = 250

Valid for all service categories

CDV 140 250 to 10000 Valid for rt-VBR

CLR 141 1 to 10 nrt–VBR = 1 to 7 (10-1 to 10-7); default = 7

rt–VBR = 1 to 9 (10-1 to 10-9); default = 9

CBR = 1 to 10 (10-1 to 10-10); default = 10

Number of circuit emulation data octets

142 1 to 47 default = 47

Playout buffer time 143 10 to 60 Valid for PRI CE and DS3/E3 CCE cards

This cpValue is a multiple of 0.1 ms.

Frame relay link cross-connected endpoint A

149 1, 2 1 = noncross-connected

2 = cross-connected (default)

Frame relay link cross-connected endpoint B

150

Frame relay link service category

151 1 to 4, 6 1 = CBR (default)

2 = nrt-VBR

3 = ABR

4 = UBR

6 = rt-VBR

Max admin weight mode 152 -1 to 2147483647

default = -1

valid only if VC application is set to May use SPVC

Max admin weight 153 0 to 2147483647

default = 5040

Maximum admin weight

valid only if VC application is set to May use SPVC


(6 of 6)



Table 23-4 Aggregate position for path-end mapping to the 5620 NM GUI

trmCircuitProfile attribute characteristics for MFR linksTable 23-5 describes the trmCircuitProfile attribute circuitProfileName characteristics for MFR links. All MFR link trmCircuitProfile attributes have read-write access.

Table 23-5 trmCircuitProfile attributes for MFR links

Path-end Mapping

HCM 1=F0B7, 2=F0B6, 3=F0B5, ..., 8=F0B0, 9=F1B7, 10=F1B6, ..., 80=F9B7

I.460 1=B7, 2=B6, 3=B5, 4=B4, 5=B3, 6=B2, 7=B1, 8=B0

DDS, X.50 1=1, 2=2, 3=3, ..., 80=80


Custom Label 4 3 1, 2 1 = Yes

2 = No (default)

Priority range minimum 5 1 to 16 The minimum priority range

default = 16

The range must be less than or equal to the Priority range maximum characteristic.

Priority range maximum 6 1 to 16 The maximum priority range

default = 1

The range must be greater than or equal to the Priority range minimum characteristic.

Transport bandwidth (Clear Bandwidth)

10 1 to 8 1 = 8 kb/s

2 = 16 kb/s

3 = 24 kb/s

4 = 32 kb/s

5 = 40 kb/s

6 = 48kb/s

7 = 56kb/s

8 = 64kb/s (default)

Cost 159 0 to 100 The cost to route the MFR link

default = 1

Carrier equipment 160 1, 2 1 = not used (default)

2 = used

Frame Relay Support 23 1, 2 1 = Frame relay not supported

2 = Frame relay supported



trmCircuitProfile attribute circuitProfileName characteristics for ATM VPC links

Table 23-6 describes the trmCircuitProfile attribute circuitProfileName characteristics for ATM VPC links.

Table 23-6 trmCircuitProfile attribute circuitProfileName characteristics for ATM VPC links

Table 23-7 describes the trmCircuitProfile attribute circuitProfile characteristics for ATM VPC links.

Table 23-7 trmCircuitProfile attribute circuitProfile characteristics for ATM VPC links

Characteristic circuitProfileName SimpleNameType String

Description

PNNI Aggregation Token 1 aggToken string Where string takes on valid values for PNNI agg token to a maximum value of FFFFFFFF

Source LSP name A 2 srcLspA string Where string is 16 characters long and describes the Endpoint A Source LSP Name field; default = empty string

Destination LSP name A 3 dstLspA string Where string is 16 characters long and describes the Endpoint A Destination LSP Name field; default = empty string

Source LSP name B 4 srcLspB string Where string is 16 characters long and describes the Endpoint B Source LSP Name field; default = empty string

Destination LSP name B 5 dstLspB string Where string is 16 characters long and describes the Endpoint B Destination LSP Name field; default = empty string


Service category for entire pipe (VPC)

16 1 to 4, 6 1 = CBR service category (default)

2 = nrt-VBR service category

3 = ABR service category

4 = UBR service category

6 = rt-VBR service category

Alarm surveillance 17 1, 2 1 = generate alarm if VP layer connectivity is lost

2 = do not generate alarm if VP layer connectivity is lost (default)

VPC link capacity 18 0 to n Peak data transfer rate in kb/s

VPI at endpoint A 19 0 to 4095 Virtual path identifier for endpoint A

VPI at endpoint Z 20 0 to 4095 Virtual path identifier for endpoint Z

SIR range minimum 21 0 to 149760 Sustained information rate range minimum in kb/s cannot be greater than VPC link capacity.

SIR range maximum 22

Frame relay 23 1, 2 1 = Frame relay not supported


(1 of 8)



VP application 25 1 to 5 1 = VPCL used as a PVC (default)

2 = VPCL used as LAN control data

3 = VPCL used as LAN data

4 = VPCL can carry SVCs and SPVCs

5 = VPCLs used for out of band application

6 = MPLS

Admin weight 26 1 to 65535 default = 5040

VPCI 27 0 to 65535 default = 0

SVC minimum VCI 28 1 to 65535 See the ATM node documentation for further restrictions about the use of VCI values.

SVC maximum VCI 29

FR/ATM SRC VP shaping

31 0, 9, 10 0 = no shaping (default)

9 = group 1 shaping

10 = group 2 shaping

FR/ATM DST VP shaping

32 0, 9, 10 0 = no shaping (default)

9 = group 1 shaping

10 = group 2 shaping

VPCL allow TDM 33 1, 2 1 = no

2 = yes (default)

Source rate increase factor


Valid for ABR service category only

Destination rate increase factor

69

Source rate decrease factor

70

Destination rate decrease factor

71

Source initial information rate

72 0 to SIR default = 1000 Kbps

Value depends on SIR

Destination initial information rate

73

Source VPCL VP/VPA shaping

74 1, 2 1 = enable

2 = disable (default)

Frozen for CBR

Source VPCL PIR 75 0 to n n = maximum VPC link capacity in kb/s

Source VPCL SIR 76 0 to n n = maximum peak information rate of endpoint A in kb/s

Source VPCL MIR 77 0 to n n = maximum peak information rate of endpoint A in kb/s

Source VPCL MBS 78 1 to n where n is the maximum allowable MBS range

Destination VPCL VP/VPA shaping

79 1, 2 1 = enable


Frozen for CBR

Destination VPCL PIR

80 -1, 0 to n n = maximum VPC link capacity in kb/s


(2 of 8)



Destination VPCL SIR

81 -1, 0 to n n = maximum peak information rate of endpoint Z in kb/s

Destination VPCL MIR

82

Destination VPCL MBS

83 1 to n where n is the maximum allowable MBS range

Maximum VPI 84 Device dependant

See the ATM node documentation for further restrictions about the use of VPI values.

Minimum VPI 85

Bandwidth Partition 1 Percentage

86 0 to 999 default = 999

The percentage of the trunk group’s bandwidth allocated to this bandwidth partition.

Bandwidth Partition 1 SPVC (1)

87 0 to 31 A bitmap indicating which service categories are supported in this bandwidth partition for SPVCs.

Bandwidth Partition 1 SVC (1)

88

Bandwidth Partition 2 Percentage (2)

89 0 to 999 The percentage of the trunk group’s bandwidth allocated to this bandwidth partition.




91






94






97






100

VPCL Capacity Mode 101 0, 1 default = 0

A flag used to indicate whether the VPCL capacity is assigned or unassigned.

VCI Range Mode 102 0, 1 default = 0

A flag used to indicate whether the switched VCI range is enabled or not.


(3 of 8)



VPI Range Mode 103 0, 1 default = 1

A flag used to indicate whether the switched VPI range is enabled or not.

Source policing option

105 1, 3 1 = disable (default)

3 = frame discard

Indicates whether traffic policing applies to the source or destination of the VCCs

Destination policing option

106

Source use shaping 107 1 to 4 1 = no shaping (default)

2 = ingress shaping

3 = egress shaping

4 = bidirectional shaping

Indicates whether traffic shaping applies to the source or destination of the VCCs

Destination use shaping

108

Use unlimited bandwidth

109 0, 1 0 = disable (default)

1 = enable

Indicates whether the bandwidth available for the selected VP is limited (only that assigned to the VP) or unlimited (exceed limit up to the entire port bandwidth)

Activity state 111 1, 2, 5 1 = enable (default)

2 = disable

5 = shutdown

The activityState of a VPC link can be either active, shutdown (transition state) or inactive. The activityState of a VCC path can be either active or inactive.

VPCL signaling format

112 0 to 2 0 = VPCL signaling undefined (default)

1 = VPCL signaling UNI

2 = VPCL signaling NNI

OAM-CC cell flow 133 1 to 4 1 = disabled (default)

2 = A to Z

3 = Z to A

4 = bidirectional

OAM-PM cell flow 134

OAM-PM TCA

A to Z direction

135 n The integer value corresponds to the managedProfileID attribute of the managedProfile object.

OAM-PM TCA

Z to A direction

136

PVC/SPVC sharing 144 1, 2 1 = enable


Lower-range minimum PVC/SPVC VCI

145 0, 32 to 65535 0 = not applicable

Minimum VCI value for PVC/SPVC VPCLs

Lower-range maximum PVC/SPVC VCI


Maximum VCI value for PVC/SPVC VPCLs

Higher-range minimum PVC/SPVC VCI


Minimum VCI value for PVC/SPVC VPCLs


(4 of 8)



Higher-range maximum PVC/SPVC VCI


Maximum VCI value for PVC/SPVC VPCLs

VPCL capacity Dst to Src

154 0 to n n = peak data transfer rate (kb/s)

SIR/MIR range minimum: Dst to Src

155 0 to 149760 Cannot be greater than VPCL capacity downstream

SIR/MIR range maximum: Dst to Src

156

Traffic descriptor Profile Src to Dst

157 managedProfileID value

ASAM traffic descriptor profile from source to destination

Traffic descriptor Profile Dst to Src

158 ASAM traffic descriptor profile from destination to source

VPA shaping at source egress

176 1, 2 1 = enable


Enables or disables the VPA shaping of the VPC link at the source endpoint

VPA shaping at destination egress

177 1, 2 1 = enable


Enables or disables the VPA shaping of the VPC link at the destination endpoint

LSP monitoring 178 0, 1 0 = disabled (default)

1 = enabled

When this cpType is enabled and a link is connected, the string cpTypes 2, 3, 4, and 5 in Table 23-6 are frozen.

When this cpType is disabled and a link is connected, the string cpTypes 2 and 4 in Table 23-6 are frozen and cpTypes 3 and 5 in Table 23-6 are hidden.

MPLS interworking 179 0 to 2 0 = cell

1 = frame

2 = auto (default)

When this cpType is set to 0, cpType 180 (Max SDU size) will not be present.

Max SDU size 180 0 to 9192 default = 9192

Holds the maximum SDU size


(5 of 8)



ODR 181 0 to 2 0 = disabled (default)

For this cpValue, the 5620 NM determines the route for the link and the Primary route Id and Alternate route Id attributes are disabled.

1 = route(s) only

For this cpValue, the 5620 NM uses the directed routes you have associated with the link. The 5620 NM first tries to connect the link using the Primary route Id then tries with the Alternate route Id. If the connect fails, the link goes to waiting for resources.

2 = route(s) preferred

For this cpValue, the 5620 NM uses the directed routes you have associated with the link. The 5620 NM first tries to connect the link using the Primary route Id then tries with the Alternate route Id. If the connect fails, the 5620 NM determines any other route.

Primary route Id 182 1 to 2147483647 default = none

Alternate route Id 183 1 to 2147483647 default = none

Statistics Activation Status

185 0, 1 0 = disabled (default)

1 = enabled

External OAM-CC (Endpt A)

219 1 to 4 1 = none (default)

2 = A to external

3 = external to A

4 = bidirectional external

External OAM-CC (Endpt B)


2 = B to external

3 = external to B


OAM-CC Status 221 0, 2, 3, 11 0 = idle (default)

2 = applied

3 = failed

11 = applied NMTI

OAM-PM Status 222 0, 2, 3, 11 0 = idle (default)

2 = applied

3 = failed

11 = applied NMTI

Ne-NSC ID 1 223 0 to 65535 0 = No Ne-NSC value (default)

1 to 65535 = Ne-NSC ID value










(6 of 8)



Rp-NSC 1-1 228 0 to 65535 0 = No Rp-NSC value (default)

1 to 65535 = Rp-NSC ID value

Rp-NSC value associated with Bandwidth partition 1









































(7 of 8)



Notes(1) See Table 23-8 for information about calculating the bitmap value for a service category setting.(2) Each partition is assigned from 0 to 999% of the VPCL bandwidth. The default is to allocate 100% of the bandwidth to

Partition 1, with all the service categories selected. The Bandwidth Percentage for the five partitions does not need to sum to 100%; it will be calculated by the bandwidth allocator software of the 5620 NM, based on the 0 to 999 ranges selected in the five partitions. A value above 100% indicates an overbooking of the partition.

Calculating the bitmap values for ATM service categories

Table 23-8 describes how to calculate the bitmap value for a service category setting.

Table 23-8 Calculating bitmap values for ATM service categories

trmCircuitProfile attribute circuitProfileName characteristics for custom attributes

Table 23-9 describes the trmCircuitProfile attribute circuitProfileName characteristics for custom attributes.




Tagged By All Rp-NSCs

243 0, 1 0 = Tagged By All Rp-NSCs is off (default)

1 = Tagged By All Rp-NSCs is on

Policy Routing Checking

244 0, 1 0 = Policy Routing Checking flag is off (default)

1 = Policy Routing Checking flag is on


(8 of 8)

Bit 4 3 2 1 0

Service category

UBR ABR nrt-VBR rt-VBR CBR



Table 23-9 trmCircuitProfile attribute circuitProfileName characteristics for custom attributes

Characteristic Access circuitProfileName Description

customAttributeValue1 Read-write 10001:ca1 string Where string is up to 254 characters, and contains custom information that is associated with the bMFacility object.

This cpType is specified when the corresponding customAttributeName is configured. A zero-length string is used to delete the value of the characteristic.









(1 of 2)



trmCircuitProfile attribute circuitProfile characteristics for TDM/ATM VCC links

Table 23-10 describes the trmCircuitProfile attribute circuitProfile characteristics for TDM/ATM VCC links.











Characteristic Access circuitProfileName Description

(2 of 2)



Table 23-10 trmCircuitProfile attribute circuitProfile characteristics for TDM/ATM VCC links


Recovery 1 1 or 2 1 = Do not try to reroute around network failures (default)

2 = Try to reroute around network failures

Custom Label 3 0, 3, 4 0 = May use or Avoid (default)

3 = Must Use

4 = Must Avoid

You can not update this value when the VCC link is in connected status.

Empty Link Priority 4 1-16 and 255 1 = Highest Priority

16 = Lowest Priority

255 = Minimum Priority (default)

Minimum Priority 5 1-16 Default = 16

Minimum Priority of CSD to ride this VCC Link

Maximum Priority 6 1-16 Default = 1

Maximum Priority of CSD to ride this VCC Link

Optimize 7 1 or 2 1 = Do not optimize after reroute (default)

2 = Optimize after reroute

Service Category 16 1 (CBR) The value is frozen to CBR and cannot be changed

Allow TDM 33 1,2 1 = no

2 = yes (default)

PIR 75 T1CE: 1544

E1CE: 2048

The default PIR value is the maximum allowed by both endpoints. (Kb/s). The value can not be changed.

Must Use VPC Link 138 1,2 1= VCC Path does not need to be routed over an ATM VPC Link (default)

2= VCC Path does not need to be routed over an ATM VPC Link

CDVT ( us) 139 1- 2000000 Default = 250

Valid for All Service Categories

limited to 250-3625 for VCC Link

Target CDV 140 250-10000 Default = 10000.

The target variance in cell transfer delay (ms).

Not used at endpoints

Target CLR 141 10 Default = 10

The target upper limit for a cross connection, defined as the number of cells lost/the number of cells offered, average over the time. (1.0 E-).

Not used at endpoints

Number of Circuit Emulation Data Octets

142 1-47 Default = 47

Playout Buffer Time (1/10 ms)

143 10-60 Default = 38Valid for PRI CE and DS3/E3 CCE cards and TNT CE cards Limited to 3-38 for TNT VCC Link

(1 of 2)



ODR(Operator Directed Routing)

181 0, 1, 2 Always set to 0 = disabled for VCC Link

Connection Type 186 1,2 1 = Pt-to-Pt Symmetrical (default)

2 = Pt-to-Pt Asymmetrical

Set to Pt-to-Pt Symmetrical and can not be changed

Traffic Descriptor 187 2 2 = PIR_0+1 (default)

Set to PIR_0+1 and can not be changed

Alarm Declaration Time EndPoint - A

188 1-300 Default = 25. (1/10ms)

Alarm Declaration Time EndPoint - B

189 1-300 Default = 25. (1/10ms)

Alarm Clearing Time EndPoint – A

190 1-300 Default = 100. (1/10ms)

Alarm Clearing Time EndPoint - B

191 1-300 Default = 100. (1/10ms)

Output timing/Synchronization Source

192 1,3,4,5 Default = 3

1 = sync residual (SRTS)

3 = adaptive clock recovery

4 = synchronous

5 = SRTS and adaptive clock

This parameter must be identical on both ends

Port Admin State Endpoint A

193 1,2 Default = 11 = Enable2 = DisableSet to Enable and can not be changed

Port Admin State Endpoint B

194 1,2 Default = 11 = Enable2 = DisableSet to Enable and can not be changed

External OAM-CC (Endpt A)


1 = none

2 = A to external

3 = external to A


External OAM-CC (Endpnt B)


2 = A to external

3 = external to A


OAM-CC Status 221 0, 2, 3, 11 0 = idle (default)

2 = applied

3 = failed

4 = applied NMTI

OAM-PM Status 222 0, 2, 3, 11 0 = idle (default)

2 = applied

3 = failed

4 = applied NMTI


(2 of 2)



trmCircuitProfile attribute circuitProfile characteristics for IMA linksTable 23-11 describes the trmCircuitProfile attribute circuitProfile characteristics for IMA links.

Table 23-11 trmCircuitProfile attribute circuitProfile characteristics for IMA links

Note(1) See Table 23-8 for information about calculating the bitmap value for a service category setting.


Cost 159 0 to 100 default = 1

Cost to reroute

Carrier equipment 160 1 to 3 1 = not used (default)

2 = used

3 = ATM switching

Booking factor—routing

161 1 to 10000 default = 100

The cpValue is a percentage value.

Booking factor—rerouting

162

ATM VPC link 163 1, 2 1 = not supported

2 = supported (default)ATM VPC path 164

ATM VCC path 165

Bandwidth partition 1 percentage

166 0 to 100 default = 100

Bandwidth partition 1 (1)

167 0 to 31 Bitmap indicating which service categories are supported in this bandwidth partition


168 0 to 100 default = 100




170 0 to 100 default = 100




172 0 to 100 default = 100




174 0 to 100 default = 100





trmCircuitProfile attribute circuitProfile characteristics for full and fractional links

Table 23-12 describes the trmCircuitProfile attribute circuitProfile characteristics for full and fractional links. All the cpTypes are read/write.

Table 23-12 trmCircuitProfile attribute circuitProfile characteristics for full and fractional links


Custom Label 4 3 1, 2 1 = Yes

2 = No (default)

Minimum Priority 5 1-16 Default = 16

Minimum Priority of CSD to ride this VCC Link

This value must be less than or equal to the Maximum Priority value

Maximum Priority 6 1-16 Default = 1

Maximum Priority of CSD to ride this VCC Link

This value must be greater than or equal to the Ninimum Priority value

Transport bandwidth (Clear Bandwidth)

10 1 to 8 1 = 8 kb/s

2 = 16 kb/s

3 = 24 kb/s

4 = 32 kb/s

5 = 40 kb/s

6 = 48kb/s

7 = 56kb/s

8 = 64kb/s (default)

SIR range minimum 21 0 to 149760 Sustained information rate range minimum in kb/s cannot be greater than VPC link capacity.

SIR range maximum 22

Frame relay 23 1, 2 1 = Frame relay not supported


Circuit-Switched Data and Voice (VPCL Allow TDM)

33 1,2 1 = not supported

2 = supported (default)


Cost to reroute

Carrier equipment 160 1 to 3 1 = not used (default)

2 = used

3 = ATM switching

Booking factor—routing

161 1 to 10000 default = 100

The cpValue is a percentage value.

Booking factor—rerouting

162

ATM VPC link 163 1, 2 1 = not supported

2 = supported (default)ATM VPC path 164

ATM VCC path 165

(1 of 3)




166 0 to 100 default = 100

Bandwidth partition 1 167 0 to 31 Bitmap indicating which service categories are supported in this bandwidth partition


168 0 to 100 default = 100



170 0 to 100 default = 100



172 0 to 100 default = 100



174 0 to 100 default = 100


Data 195 1, 2 1 = not supported


Circuit Switch Data 196 1, 2 1 = not supported


Data and HCV 197 1, 2 1 = not supported


Super-rate 198 1, 2 1 = not supported


ADPCM-Voice 199 1, 2 1 = not supported


Uncompressed Voice 200 1, 2 1 = not supported


Subrate path at 64 Kb/s

201 1, 2 1 = not supported


X.25 and X.75 202 1, 2 1 = not supported


Transport Path 203 1, 2 1 = not supported



(2 of 3)



trmCircuitProfile attribute circuitProfile characteristics for PSN linksTable 23-13 describes the trmCircuitProfile attribute circuitProfile characteristics for PSN links.

Transport Link 204 1, 2 1 = not supported


MPLS Enabled VPC Link

205 1, 2 1 = not supported


ATM VCC Link 206 1, 2 1 = not supported


LAN Control 207 1, 2 1 = not supported


LAN Data 208 1, 2 1 = not supported


Pass-through link 209 1, 2 1 = not supported


Custom Label 1 210 3, 4 3 = Yes (default)

4 = No



4 = No



4 = No


Reroute Hold Timer 213 1, 2 1 = enabled

2 = disabled (default)

Delay reroute time 214 0 to 900 0 (default)

Flailing Link Considered Down

215 1, 2 1 = enabled


Device Failure Evaluation Interval

216 1 to 3600 300 (default)

Device Failure Tolerance

217 1 to 100 2 (default)

Device Up Evaluation Interval

218 1 to 3600 30 (default)


(3 of 3)



Table 23-13 trmCircuitProfile attribute circuitProfile characteristics for PSN links

trmCircuitProfile attribute circuitProfile characteristics for subrate links

Table 23-14 describes the trmCircuitProfile attribute circuitProfile characteristics for subrate links.


Minimum Priority 5 1 to 16 default = 16

Minimum priority of VPC, VCC, and frame relay paths to ride over the PSN link. This value must be less than or equal to the Maximum Priority value.

Maximum Priority 6 1 to 16 default = 1

Maximum priority of VPC, VCC, and frame relay paths to ride over the PSN link. This value must be greater than or equal to the Minimum Priority value.

Frame Relay 23 1, 2 1 = Frame relay not supported

2 = Frame relay supported (default)

Circuit Switched Data and Voice

33 1 1 = not supported (default)


Cost assigned to PSN link

ATM VPC Link 163 1 1 = not supported (default)

ATM VPC Path 164 1, 2 1 = VPC path not supported

2 = VPC path supported (default)

ATM VCC path 165 1, 2 1 = VCC path not supported

2 = VCC path supported (default)

X.25 and X.75 202 1 1 = not supported (default)

ATM VCC Link 206 1 1 = not supported (default)



Table 23-14 trmCircuitProfile attribute circuitProfile characteristics for subrate links


Rate adaptation type 9 1 to 9 1 = I.460

2 = X.50

3 = DDS

4 = HCM

5 = HCM/I.460



8 = DDS DS0B 4,8 kb/s


Values 1 to 4 are valid for frame relay links.

Values 1, 2, 4 to 9 are valid for subrate links.

When the value of the Rate Adaptation Type is set to 4 (HCM) and when the value of the Speed Range Minimum is greater than the value of the HCM Bandwidth, the value of the Speed Range Minimum is set to the vaue of HCM Bandwidth.

When the value of the Rate Adaptation Type is set to 4 and when the value of the Speed Range Maximum is greater than the value of HCM Bandwidth, the value of the Speed Range Maximum is set to the value of HCM Bandwidth.

When the value of the Rate Adaptation Type is set to 1 or 5 and when the value of the Speed Range Minimum is greater than the value of Transport Bandwidth, the value of the Speed Range Minimum is set to the value of Transport Bandwidth.

When the value of the Rate Adaptation Type is set to 1 or 5 and when the value of the Speed Range Maximum is greater than the value of Transport Bandwidth, the value of the Speed Range Maximum is set to the value of Transport Bandwidth.


Transport bandwidth 10 1 to 8 1 = 8 kb/s

2 = 16 kb/s

3 = 24 kb/s

4 = 32 kb/s

5 = 40 kb/s

6 = 48 kb/s

7 = 56 kb/s


Frame relay 23 1, 2 1 = Frame relay is not supported

2 = Frame relay is supported (default)

May Use ATM 137 1, 2 1 = no

2 = yes (default)

(1 of 4)



HCM bandwidth 245 1 to 8 1 = 8 kb/s (default)

2 = 16 kb/s

3 = 24 kb/s

4 = 32 kb/s

5 = 40 kb/s

6 = 48 kb/s

7 = 56 kb/s


This cpType is applicable only when cpType 9 (Rate Adaptation Type) is set to 4 (HCM) or 5 (HCM/I.460).

Frame position 246 1 to 8 Default = 1

identifies the position of the F-bit in an HCM frame, therefore, this cpType is applicable only when cpType 9 (Rate adaptation type) is set to 4 (HCM) or 5 (HCM/I.460).


(2 of 4)



Speed range minimum 247 0 to 15 0 = 0 kb/s

1 = 1.2 kb/s

2 = 2.4 kb/s

3 = 4.8 kb/s

4 = 8 kb/s

5 = 9.6 kb/s

6 = 14.4 kb/s

7 = 16 kb/s

8 = 19.2 kb/s

9 = 24 kb/s

10 = 32 kb/s

11 = 38.4 kb/s

12 = 40 kb/s

13 = 48 kb/s

14 = 56 kb/s

15 = 64 kb/s

The default value depends on the Transport Bandwidth, HCM Bandwidth, port type, and configuration of the card.

The value of the speed range minimum must be less than or equal to the value of the speed range maximum. The values of the speed range minimum and speed range maximum are exchanged when the speed range minimum is greater than the speed range maximum.

When cpType 9 (Rate adapation type) has the value 1 (I.460), 4 (HCM), or 5 (HCM/I.460), and one of the endpoints of the subrate link is on a non-FRS card, the valid values for this cpType are 0, 4, 7, and 9 to 15.

When cpType 9 (Rate adaptation type) has the value 2 (X.50), and one of the endpoints of the subrate link is on a non-FRS card, the valid values for this cpType are 0 to 3, 5, 8, and 13.

When cpType 9 (Rate adaptation type) has the value 6 (DDS DS0B 19.2 kb/s), 7 (DDS DS0B 2.4 kb/s), 8 (DDS DS0B 4.8 kb/s), or 9 (DDS DS0B 9.6 kb/s), and on e of the endpoints of the subrate link is on a non-FRS card, the valid values for this cpType are 0 to 3, 5, and 8.

When cpType 9 (Rate adaptation type) has the value 4 (HCM) or 5 (HCM/I.460), and one of th endpoints of the subrate link is an SRM device on an FRS card, the value values for this cpType are 0 to 3, 5 to 8, and 11.

When cpType 9 (Rate adaptation type) has the value 2 (X.50), and one of the endpoints of the subrate link is an SRM device on an FRS card, the valid vaues for this cpType are 0, 2, 3, 5, and 8.

When cpType 9 (Rate adaptation type) has the value 6 (DDS DS0B 19.2 kb/s), 7 (DDS DS0B 2.4 kb/s), 8 (DDS DS0B 4.8 kb/s), or 9 (DDS DS0 9.6 kb/s), and one of the endpoints of the subrate link is an SRM device on an FRS card, the valid values for this cpType are 0, 2, 3, 5, 8, and 14.


(3 of 4)



Speed range maximum 248 0 to 15 0 = 0 kb/s

1 = 1.2 kb/s

2 = 2.4 kb/s

3 = 4.8 kb/s

4 = 8 kb/s

5 = 9.6 kb/s

6 = 14.4 kb/s

7 = 16 kb/s

8 = 19.2 kb/s

9 = 24 kb/s

10 = 32 kb/s

11 = 38.4 kb/s

12 = 40 kb/s

13 = 48 kb/s

14 = 56 kb/s

15 = 64 kb/s

The default value depends on the Transport Bandwidth, HCM Bandwidth, port type, and configuration of the card.

The value of the speed range minimum must be less than or equal to the value of the speed range maximum. The values of the speed range minimum and speed range maximum are exchanged when the speed range minimum is greater than the speed range maximum.

When cpType 9 (Rate adaptation type) has the value 7 (DDS DS0B 2.4 kb/s), 8 (DDS DS0B 4.8 kb/s), or 9 (DDS DS0B 9.6 kb/s), and one of the endpoints of the subrate link is on a non-FRS card, the valid values for this cpType are 1 to 3, 5, and 8.

When cpType 9 (Rate adaptation type) has the value 1 (I.460), 4 (HCM), or 5 (HCM/I.460), and one of the endpoints of the subrate link is on a non-FRS card, the valid values for this cpType are 0, 4, 7, and 9 to 15.

When cpType 9 (Rate adaptation type) has the value 2 (X.50), and one of the endpoints of the subrate link is on a non-FRS card, the valid values for this cpType are 1 to 3, 5, 8, and 13.

When cpType 9 (Rate adaptation type) has the value 7 (DDS DS0B 2.4 kb/s), 8 (DDS DS0B 4.8 kb/s), or 9 (DDS DS0B 9.6 kb/s), and one of the endponts of the subrate link is an SRM device on an FRS card, the valid values for this cptype are 0, 2, 3, 5, 8 and 14.

When cpType 9 (Rate adaptation type) has the value 2 (X.50), and one of the endpoints of the subrate link is an SRM device on an FRS card, the valid values for this cpType are 1 to 3, 5 to 8, and 11.

When cpType 9 (Rate adaptation type) has the value 2 (X.50), and one of the endpoints of the subrate link is an SRM device on an FRS card, the valid values for this cpType are 0, 2, 3, 5, and 8.

Allow data 249 1, 2 1 = No

2 = Yes (default)

Allow HCV 250 1, 2 1 = No

2 = Yes (default)


(4 of 4)



23.7 currentProblemList attribute

The currentProblemList attribute provides additional alarm information for bMFacility objects. The bMFacility object has two other attributes related to alarms: operationalState and alarmStatus. A path that is working normally has an operationalState of enabled and an alarmStatus of cleared. When the path is under alarm, the operationalState is set to disabled and the alarmStatus is set to activeReportable-Indeterminate. In addition, an alarm event report is sent with a description of the alarm in the additionalText field of the report. The currentProblemList attribute provides a means to retrieve additional information from the object about the alarm.

The information in the currentProblemList attribute is an OID that indicates:

• the last connection state that was raised on the bMFacility object• the condition that caused the bMFacility object to be in that connection state

Although the bMFacility object can only be in one state at a time, several states have multiple conditions that could have caused them. The currentProblemList attribute allows the customer to distinguish between these states by pinpointing the probableCause of the alarm state. Table 23-15 describes the valid OID values and the corresponding probableCauses of the alarms. Performing a get operation on the bMFacility object returns the value of the currentProblemList attribute.

When a new bMFacility object is created, the 5620 CMIP initializes the currentProblemList value to null. The value of the currentProblemList attribute may also be null between states.

When an alarm occurs, the 5620 CMIP generates stateChange and alarmRecord event notifications, updates the value of the currentProblemList attribute and emits an attributeValueChange on the currentProblemList attribute for the affected bMFacility. The currentProblemList attribute is updated automatically after the 5620 CMIP processes an event notification.

Table 23-15 bMFacility alarms and perceived alarm severities

alarm state OID 5620 NM status

probableCause (1) description of alarm state

perceivedSeverity (1)

additionalText (1) (problem description)

1.2.124.113537.1.9.1 Ready for Connect

Disconnected Minor “The groomed circuit has been locked by a network management user.”


Disconnected (timed lock set)

Minor “The groomed circuit has been locked because it had a lock time set.”


Disconnected (disruption by another user)

Major “The groomed circuit has been locked and converted to NMTI connections by a network management user.”

(1 of 4)




Disconnected (none) Minor “The groomed circuit is locked.”


Bumped (higher priority call)

Major “The groomed circuit has been bumped (locked) to free bandwidth for a higher priority call.”

1.2.124.113537.1.9.6 Connected Activated Cleared “The groomed circuit has been successfully unlocked; bandwidth has been allocated.”

1.2.124.113537.1.9.7 Connected Activated (immediately) Cleared “The groomed circuit is unlocked; bandwidth has been allocated.”

1.2.124.113537.1.9.8 Connected Activated (timed unlock) Cleared “The groomed circuit is unlocked as a result of a timed unlock; bandwidth has been allocated.”

1.2.124.113537.1.9.9 Connected Activated (reroute) Cleared “The groomed circuit is unlocked after a reroute; bandwidth has been allocated.”

1.2.124.113537.1.9.10 Connected Activated (recovery) Cleared “The groomed circuit has been recovered, and is now unlocked with bandwidth allocated.”

1.2.124.113537.1.9.11 Connected Activated (bumped) Cleared “The groomed circuit is unlocked after being bumped; bandwidth has been allocated.”

1.2.124.113537.1.9.12 Connected Activated (uploaded) Cleared “The groomed circuit was uploaded from connections; and is unlocked with bandwidth allocated.”

1.2.124.113537.1.9.13 Disconnect Requested

Activated (begin optimizing)

Minor “The groomed circuit is being groomed.”

1.2.124.113537.1.9.14 Connected Activated (optimized) Cleared “The groomed circuit is unlocked after grooming; bandwidth has been allocated.”

1.2.124.113537.1.9.15 Connected Activated (none) Cleared “The groomed circuit is unlocked; bandwidth has been allocated.”

1.2.124.113537.1.9.16 Connected (down)

Down (immediately) Warning “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.”





(2 of 4)



1.2.124.113537.1.9.17 Connected (down)

Down (timed) Warning “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.”

1.2.124.113537.1.9.18 Connected (down)

Down (reroute) Warning “The groomed circuit is unlocked with bandwidth allocated after a reroute but it is disabled.”

1.2.124.113537.1.9.19 Connected (down)

Down (recover) Warning “The groomed circuit is unlocked with bandwidth allocated after a recovery, but it is disabled.”

1.2.124.113537.1.9.20 Connected (down)

Down (upload) Warning The groomed circuit is unlocked with bandwidth allocated after an upload, but it is disabled.”

1.2.124.113537.1.9.21 Connected (down)

Down (bumped) Warning “The groomed circuit is unlocked with bandwidth allocated after being bumped, but it is disabled.”

1.2.124.113537.1.9.22 Connected (down)

Down (optimized) Warning “The groomed circuit is unlocked with bandwidth allocated after grooming, but it is disabled.”

1.2.124.113537.1.9.23 Connected (down)

Down Major “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.”

1.2.124.113537.1.9.24 Interrupted via NMTI

Waiting for Resources

No route to source Major “The groomed circuit has been unlocked, but no bandwidth is allocated, so it is disabled.”


No route to source (bumped)

Major “The groomed circuit has been bumped and now has no bandwidth allocated, so it is disabled.”

1.2.124.113537.1.9.26 Waiting for Resources

No route to source (rerouted)

Major “The groomed circuit has been rerouted, and now has no bandwidth allocated, so it is disabled.”

1.2.124.113537.1.9.27 Waiting for Repairs

Failed Major “The groomed circuit is unlocked but no bandwidth is allocated as the request failed in the network.”





(3 of 4)



Note(1) alarmRecord attribute; see section 21.3 for details


Affected by NMTI Critical “A part of this groomed circuit has been disabled through NMTI.”

1.2.124.113537.1.9.29 Connected Affected by NMTI (cleared)

Cleared “A part of this call, previously disabled through NMTI, is now busy.”

1.2.124.113537.1.9.30 Reroute Requested

Suspect reroute Major “The groomed circuit is being rerouted.”


Atomic set (failed) Major “The groomed circuit is disabled after an unsuccessful bandwidth atomic set.”

1.2.124.113537.1.9.32 Connected Atomic set (connect) Cleared “The groomed circuit has been successfully unlocked after a bandwidth atomic set.”


Atomic set (disconnect) Major “The groomed circuit has been locked as a result of an unsuccessful bandwidth atomic set.”


Atomic set (no route to source)

Major “The groomed circuit has been atomically set and now has no bandwidth allocated, so it is disabled.”

1.2.124.113537.1.9.35 Under Maintenance

Under maintenance Minor “The groomed circuit is under maintenance.”

1.2.124.113537.1.9.36 Connected Under maintenance (cleared)

Cleared “The maintenance diagnostics on this groomed circuit have been released.”

1.2.124.113537.1.9.37 Down and under maintenance

Intrusive maintenance or loopback

Critical “The groomed circuit is disabled due to intrusive diagnostics.”

1.2.124.113537.1.9.38 Connected Intrusive maintenance or loopback (cleared)

Cleared “The groomed circuit, previously disabled due to intrusive diagnostics, is now busy.”

1.2.124.113537.1.9.39 Connected Activated (optimize failed)

Cleared “The groomed circuit is unlocked after grooming; bandwidth has been allocated.”

1.2.124.113537.1.9.40 Connected (down)

Down (optimized failed) Warning “The groomed circuit is unlocked with bandwidth allocated after grooming, but it is disabled.”





(4 of 4)







24.5 administrativeState and operationalState attributes 24-5

24.6 currentProblemList attribute 24-5

24.7 bMGroomedCircuit object profile attributes 24-9

24.8 tDMProfile attribute 24-10

24.9 frameRelayProfile attribute 24-21

24.10 aTMProfile attribute 24-27

24.11 commonProfile attribute 24-43

24.12 circuitType attribute 24-49



24.1 Introduction

The bMGroomedCircuit object models a path in the network. See chapter 13 for information about paths and path management. The bMGroomedCircuit object is contained in a partition-level network object. See chapter 38 for information about network objects.


The bMGroomedCircuit object supports the following CMIP operations:

• create• delete• get• cancel get• set• action

• trmCircuitTrace, trmCircuitGrooming and FindByLabel. The action on the network object, FindByLabel, is used to retrieve the trailID given the userLabel.

See section 13.10 for information about trmCircuitTrace and trmCircuitGrooming.


The bMGroomedCircuit object can generate the following event notifications:

• attributeValueChange• communicationsAlarm• objectCreation• objectDeletion• stateChange

24.4 Attributes

Table 24-1 describes the bMGroomedCircuit object attributes. Additional attribute information is provided after the table. See section 13.3 for information about how to use bMGroomedCircuit object attributes for configuration management and path creation.



Table 24-1 bMGroomedCircuit object attributes


administrativeState Reflects the availability of the bMGroomedCircuit object as imposed through management services

Read-write default: logical links = locked

0 = locked

1 = unlocked

See chapter 13 for more information on path management


Read Tied to operationalState (cleared or activeReportable-Indeterminate); see section 13.2 for more information

aTMProfile Provides the ATM characteristics of bMGroomedCircuit object (1)

Read-write See Tables 24-7 and 24-8 for details

a-TPInstance Refers to the managedGroomedCircuitTP object at one end of a path

Read distinguishedName of managedGroomedCircuitTP


Read See Table 24-13 for details

commonProfile Provides common characteristics of bMGroomedCircuit object

Read-write See Table 24-12 for details

currentProblemList Identifies the probableCause of an alarm for a bMGroomedCircuit object instance

Read The probableCause OID describing the current alarm state for the path; see Table 24-3 for details

directionality Indicates the direction of a path Read 1 = Bidirectional

frameRelayProfile Provides the frame relay characteristics of bMGroomedCircuit object

Read-write See Table 24-6 for details

nameBinding Identifies the kind of name binding used by a bMGroomedCircuit object

Read Name binding

objectClass Is the kind of object Read Always the OID for bMGroomedCircuit

operationalState Is the status of the object in the network

Read 0 = disabled

1 = enabled

packages Identifies the packages used by the bMGroomedCircuit object

Read List of implemented packages; see the GDMO for information

serverConnectionList For resource link bMGroomedCircuits, this attribute provides a list of bMFacilities supporting this bMGroomedCircuit object instance

Read List of bMFacility distinguished names

In all cases of bMGC, except resource links, such as PNNI, signaling, and ILMI bMGCs, this attribute is null. In the case of resource links, this field contains the objectInstance of the ATM VPCL on which the ILMI link rides.

tDMProfile Provides the TDM characteristics of bMGroomedCircuit object

Read-write See Table 24-4

(1 of 2)



Note(1) VPI and VCI values for Frame Relay paths with ATM interworkings are provided by cpTypes 12 and 13 of the

frameRelayProfile attribute.

The following subsections provide information for these attributes:

• administrativeState and operationalState• tDMProfile• frameRelayProfile• aTMProfile• commonProfile• circuitType

trailId Naming attribute; identifies the bMGroomedCircuit by mapping onto the unique call ID of the 5620 NM

Read 5620 NM call_id of the path

A unique integer assigned by the 5620 NM

trmEncryptionRouting Indicates whether an encrypted route is required; corresponds to custom label level 1 of the 5620 NM

Read-write 0 = don't care

3 = required

4 = not required

Custom labels must be configured at the 5620 NM. trmFiberRouting Indicates whether a fiber route is

required; corresponds to custom label level 2 of the 5620 NM

Read-write

trmTerrestrialRouting Indicates whether a terrestrial route is required; corresponds to custom label level 3 of the 5620 NM

Read-write

typeText Provides additional information Read String describing path type

userIdentifier Allows the OSS to assign a label to the path


String up to 255 characters; only an OSS can modify


userLabel Allows the OSS or the 5620 NM operator to assign a name to an object instance

Read-write default = 5620 NM-assigned object name

This attribute is a string up to 33 characters that can be set by the OSS or the 5620 NM operator

If the unique naming feature of the 5620 NM is enabled and the OSS attempts to create a path with a duplicate name, the 5620 CMIP will fail the request. See the 5620 NM Advanced Configuration Procedures guide for more information about enabling the unique naming feature.

z-TPInstance Refers to the managedGroomedCircuitTP object at the other end of a path

Read distinguishedName of managedGroomedCircuitTP


(2 of 2)



24.5 administrativeState and operationalState attributes

Table 24-2 describes the administrativeState and operationalState attributes, that work together to set the path status. See section 13.1 for information about how the path status is used in path management.

Table 24-2 administrativeState and operationalState attribute values and path status

Notes(1) Attribute value combinations not shown in the table are not supported.(2) See chapter 13 for a description of these states.(3) This is a fault condition.

24.6 currentProblemList attribute

The currentProblemList attribute provides additional alarm information for bMGroomedCircuit objects. The bMGroomedCircuit object has two other attributes related to alarms: operationalState and alarmStatus. A path that is working normally has an operationalState of enabled and an alarmStatus of cleared. When the path is under alarm, the operationalState is set to disabled and the alarmStatus is set to activeReportable-Indeterminate. In addition, an alarm event report is sent with a description of the alarm in the additionalText field of the report. The currentProblemList attribute provides a means to retrieve additional information from the object about the alarm.

Although the bMGroomedCircuit object can only be in one state at a time, several states have multiple conditions that could have caused them. The currentProblemList attribute allows the customer to distinguish between these states by pinpointing the probableCause of the alarm state. Table 24-3 describes the valid OID values and the corresponding probableCauses of the alarms. Performing a get operation on the bMGroomedCircuit object returns the value of the currentProblemList attribute.

When a new bMGroomedCircuit object is created, the 5620 CMIP initializes the currentProblemList value to null. The value of the currentProblemList attribute may also be null between states.

administrativeState attribute value (1)

operationalState attribute value (1)

Possible network path status (2)

Corresponding bandwidth allocation

unlocked disabled “Connected down” (3) allocated

unlocked disabled “Waiting for resources” (3) not allocated

unlocked disabled “Waiting for repair” (3) not allocated

unlocked enabled “Connect requested” being allocated

unlocked enabled “Reroute requested” being changed

unlocked enabled “Connected” allocated

locked enabled “Ready for connect” not allocated

locked enabled “Disconnect requested” being deallocated



When an alarm occurs, the 5620 CMIP generates stateChange and alarmRecord event notifications, updates the value of the currentProblemList attribute and emits an attributeValueChange on the currentProblemList attribute for the affected bMGroomedCircuit. The currentProblemList attribute is updated automatically after the 5620 CMIP processes an event notification.

Table 24-3 bMGroomedCircuit alarms and perceived alarm severities






Disconnected Minor “The groomed circuit has been locked by a network management user.”


Disconnected (timed lock set)

Minor “The groomed circuit has been locked because it had a lock time set.”


Disconnected (disruption by another user)

Major “The groomed circuit has been locked and converted to NMTI connections by a network management user.”


Disconnected (none) Minor “The groomed circuit is locked.”


Bumped (higher priority call)

Major “The groomed circuit has been bumped (locked) to free bandwidth for a higher priority call.”

1.2.124.113537.1.9.6 Connected Activated Cleared “The groomed circuit has been successfully unlocked; bandwidth has been allocated.”

1.2.124.113537.1.9.7 Connected Activated (immediately) Cleared “The groomed circuit is unlocked; bandwidth has been allocated.”

1.2.124.113537.1.9.8 Connected Activated (timed unlock) Cleared “The groomed circuit is unlocked as a result of a timed unlock; bandwidth has been allocated.”

1.2.124.113537.1.9.9 Connected Activated (reroute) Cleared “The groomed circuit is unlocked after a reroute; bandwidth has been allocated.”

1.2.124.113537.1.9.10 Connected Activated (recovery) Cleared “The groomed circuit has been recovered, and is now unlocked with bandwidth allocated.”

(1 of 4)



1.2.124.113537.1.9.11 Connected Activated (bumped) Cleared “The groomed circuit is unlocked after being bumped; bandwidth has been allocated.”

1.2.124.113537.1.9.12 Connected Activated (uploaded) Cleared “The groomed circuit was uploaded from connections; and is unlocked with bandwidth allocated.”

1.2.124.113537.1.9.13 Disconnect Requested

Activated (begin optimizing)

Minor “The groomed circuit is being groomed.”

1.2.124.113537.1.9.14 Connected Activated (optimized) Cleared “The groomed circuit is unlocked after grooming; bandwidth has been allocated.”

1.2.124.113537.1.9.15 Connected Activated (none) Cleared “The groomed circuit is unlocked; bandwidth has been allocated.”

1.2.124.113537.1.9.16 Connected (down)

Down (immediately) Warning “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.”

1.2.124.113537.1.9.17 Connected (down)

Down (timed) Warning “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.”

1.2.124.113537.1.9.18 Connected (down)

Down (reroute) Warning “The groomed circuit is unlocked with bandwidth allocated after a reroute but it is disabled.”

1.2.124.113537.1.9.19 Connected (down)

Down (recover) Warning “The groomed circuit is unlocked with bandwidth allocated after a recovery, but it is disabled.”

1.2.124.113537.1.9.20 Connected (down)

Down (upload) Warning The groomed circuit is unlocked with bandwidth allocated after an upload, but it is disabled.”

1.2.124.113537.1.9.21 Connected (down)

Down (bumped) Warning “The groomed circuit is unlocked with bandwidth allocated after being bumped, but it is disabled.”

1.2.124.113537.1.9.22 Connected (down)

Down (optimized) Warning “The groomed circuit is unlocked with bandwidth allocated after grooming, but it is disabled.”





(2 of 4)



1.2.124.113537.1.9.23 Connected (down)

Down Major “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.”


Waiting for Resources

No route to source Major “The groomed circuit has been unlocked, but no bandwidth is allocated, so it is disabled.”


No route to source (bumped)

Major “The groomed circuit has been bumped and now has no bandwidth allocated, so it is disabled.”


No route to source (rerouted)

Major “The groomed circuit has been rerouted, and now has no bandwidth allocated, so it is disabled.”


Failed Major “The groomed circuit is unlocked but no bandwidth is allocated as the request failed in the network.”


Affected by NMTI Critical “A part of this groomed circuit has been disabled through NMTI.”

1.2.124.113537.1.9.29 Connected Affected by NMTI (cleared)

Cleared “A part of this call, previously disabled through NMTI, is now busy.”

1.2.124.113537.1.9.30 Reroute Requested

Suspect reroute Major “The groomed circuit is being rerouted.”


Atomic set (failed) Major “The groomed circuit is disabled after an unsuccessful bandwidth atomic set.”

1.2.124.113537.1.9.32 Connected Atomic set (connect) Cleared “The groomed circuit has been successfully unlocked after a bandwidth atomic set.”


Atomic set (disconnect) Major “The groomed circuit has been locked as a result of an unsuccessful bandwidth atomic set.”


Atomic set (no route to source)

Major “The groomed circuit has been atomically set and now has no bandwidth allocated, so it is disabled.”





(3 of 4)



Note(1) alarmRecord attribute; see section 21.3 for details

24.7 bMGroomedCircuit object profile attributes

The bMGroomedCircuit object profile attributes—tDMProfile, frameRelayProfile, aTMProfile, and commonProfile—provide additional information about path characteristics.

Figure 24-1 describes the ASN.1 definition for CircuitProfile, which can have either of the following characteristics:

• circuitProfile• circuitProfileName

A circuitProfile provides profile characteristics through two components: cpType and cpValue. All of the bMGroomedCircuit object profile attributes—tDMProfile, frameRelayProfile, aTMProfile, and commonProfile—have circuitProfile values.

A circuitProfileName which only aTMProfile attribute uses, provides profile characteristics through the SimpleNameType choice. Figure 24-1 describes the SimpleNameType, which can be either a number or a string.

Table 24-7 describes the circuitProfileName values for aTMProfile attribute. Tables 24-4, 24-6, 24-8, and 24-12 describe the circuitProfile values for all of the bMGroomedCircuit object profile attributes.

1.2.124.113537.1.9.35 Under Maintenance

Under maintenance Minor “The groomed circuit is under maintenance.”

1.2.124.113537.1.9.36 Connected Under maintenance (cleared)

Cleared “The maintenance diagnostics on this groomed circuit have been released.”

1.2.124.113537.1.9.37 Down and under maintenance

Intrusive maintenance or loopback

Critical “The groomed circuit is disabled due to intrusive diagnostics.”

1.2.124.113537.1.9.38 Connected Intrusive maintenance or loopback (cleared)

Cleared “The groomed circuit, previously disabled due to intrusive diagnostics, is now busy.”

1.2.124.113537.1.9.39 Connected Activated (optimize failed)

Cleared “The groomed circuit is unlocked after grooming; bandwidth has been allocated.”

1.2.124.113537.1.9.40 Connected (down)

Down (optimized failed) Warning “The groomed circuit is unlocked with bandwidth allocated after grooming, but it is disabled.”





(4 of 4)



Figure 24-1 ASN.1 definition for CircuitProfile

24.8 tDMProfile attribute

Table 24-4 describes the tDMProfile attribute circuitProfile characteristics for voice and data paths, including voice compression, fax, and modem.

Table 24-4 tDMProfile attribute circuitProfile characteristics for voice and data paths

CircuitProfile(1) ::= SET OF CHOICE {

circuitProfileName [0] SimpleNameType,

circuitProfile [1] SEQUENCE {

cpType Integer,

cpValue REAL

}

}

where SimpleNameType is defined as:

SimpleNameType(1) ::= CHOICE {

number INTEGER,

string GraphicString

}

Note1. CircuitProfile is defined in the GDMO in file nmfvol4.asn. SimpleNameType is defined

in the GDMO in the file smi.asn.

15346


Bandwidth

Bandwidth bandwidth depends on path type

For a data circuit, indicates the amount of usable digital bandwidth; for a voice or fax circuit, indicates the minimum amount of digital bandwidth required

Bandwidth is in Kb/s.

From FORUM-ASN1-1

(1 of 10)



Rate adaption

Rate adaption 1 1 to 4 1 = transparent rate adaption (I.460)

2 = CCITT X.50 subrate multiplexing

3 = AT&T DDS subrate multiplexing

4 = proprietary subrate multiplexing (HCM) (default)

Not applicable for VSC endpoints

Compression

Compression 2 1 to 142 As of Release 5.0, any application development that would normally use cpType 2 should instead use cpTypes 63 to 67. The cpTypes 63 to 67 have replaced cpType 2, which will not be developed beyond cpValue 142.

Existing applications that use cpType 2 require no changes but they may be modified to use cpTypes 63 to 67, since the functionality provided by cpTypes 63 to 67 fully implements the functionality provided by cpType 2.

1 = no voice compression (default)

2 = standard 32 kb/s voice compression (Delta ADPCM)

3 = proprietary 16 kb/s compression (HCV 16)

4 = proprietary 8 kb/s compression (HCV 8)

5 = 9.6 kb/s G3 Fax encoding into 16 kb/s bandwidth




9 = transitional ADPCM compression

10 = unused

11 = unused

12 = unused

13 = unused

14 = unused

15 = unused

16 = ACELP, 8 kb/s voice compression

17 = LDCELP, 16 kb/s voice compression

18 = ACELP 8 kb/s, G3 Fax 4.8k



21 = LDCELP 16 kb/s, G3 Fax 4.8k



24 = ACELP 8 kb/s, modem 4.8k






(2 of 10)



Compression 2 1 to 142 29 = LDCELP 16 kb/s, modem 4.8k

30 = LDCELP 16 kb/s, modem 7.2k




34 = ACELP 8 kb/s, G3 Fax 4.8k, modem 4.8k















49 = LDCELP 16 kb/s, G3 Fax 4.8k, modem 4.8k















64 = ACELP-A 8 kb/s


(3 of 10)



Compression 2 1 to 142 65 = ACELP-A 8 kb/s, G3 Fax 4.8k

66 = ACELP-A 8 kb/s, G3 Fax 9.6k

67 = ACELP-A 8 kb/s, G3 Fax 14.4k

68 = ACELP-A 8 kb/s, modem 4.8k





73 = ACELP-A 8 kb/s, G3 Fax 4.8k, modem 4.8k















88 = ACELP/ACELP-A 8 kb/s

89 = ACELP/ACELP-A 8 kb/s, G3 Fax 4.8k



92 = ACELP/ACELP-A 8 kb/s, modem 4.8k





97 = ACELP/ACELP-A 8 kb/s,G3 Fax 4.8k, modem 4.8k





(4 of 10)



Compression 2 1 to 142 101 = ACELP/ACELP-A 8 kb/s,G3 Fax 4.8k, modem 14.4k











112 = NetCoder 8 kb/s

113 = NetCoder 9.6 kb/s

114 = G.723.1 Dual Rate Speech Coder 5.3 kb/s

115 = G.723.1 Dual Rate Speech Coder 6.3 kb/s

116 = Clear Channel 64 kb/s

117 = ACELP-A 8 kb/s, Fax 2.4 kb/s

118 = ADPCM 32 kb/s, Fax 2.4 kb/s




122 = NetCoder 8 kb/s, Fax 2.4 kb/s




126 = NetCoder 9.6 kb/s, Fax 2.4 kb/s




130 = G.723.1 Dual Rate Speech Coder 5.3 kb/s, Fax 2.4 kb/s








138 = G.726 ADPCM 32 kb/s

139 = G.711, Fax 2.4 kb/s

140 = G.711, Fax 4.8 kb/s

141 = G.711, Fax 9.6 kb/s

142 = G.711, Fax 14.4 kb/s

Data paths

Routing 3 1, 2 1 = circuits are routed full DS (default)

2 = circuits are routed over subrate link


(5 of 10)



Voice and data

Signaling 4 1, 2 1 = signaling is not required

2 = signaling is required (default)

For data paths, control leads are transmitted. For voice paths, the voice signaling is transmitted.

Voice

Companding 5 1, 2 Set to 1 for voice over frame relay paths or VSC endpoints to indicate that companding is automatically controlled by the 5620 NM.

1 = companding is not required

2 = companding is required

This attribute applies to T1 and E1 interfaces. The ATM G.711 Transport Law attribute setting determines whether the speech is transported over the ATM network in Mµ-law or A-law format.

Voice signaling for endpoint A

6 253, 254 Set to 253 for non-CAS VSC endpoints

253 = no signaling

254 = signaling

See Table 24-5 for more information about voice signaling types.

Voice signaling for endpoint Z

7

HCV and G3 FAX

Echo cancellation endpoint A

8 1, 2 1 = disable echo cancellation for endpoint

2 = enable echo cancellation for endpoint (default)

Can be configured while the call is connectedEcho cancellation endpoint Z

9

Nonlinear suppression endpoint A

10 1, 2 1 = disable nonlinear suppression for endpoint

2 = enable nonlinear suppression for endpoint (default)

Can be configured while the call is connected

Valid only if echo cancellation is enabled.Nonlinear suppression endpoint Z

11

G3 FAX

Fax transmit level for endpoint A

12 –300 to –30 When Auto Adjust Transmit Level for Endpoint A is enabled, the value will be rounded up or down to within the –165 to 35 range for VSC endpoints. When Auto Adjust Transmit Level for Endpoint A is disabled, the path will be set to WFR if the value is out of range.

Fax transmit level for endpoint Z

13 –300 to –30 When Auto Adjust Transmit Level for Endpoint Z is enabled, the value will be rounded up or down to within the –165 to 35 range for VSC endpoints. When Auto Adjust Transmit Level for Endpoint Z is disabled, the path will be set to WFR if the value is out of range.

Automatic adjusting of modem module endpoint A

14 1, 2 1 = enable modem module endpoint transmit level (default)

2 = disable modem module endpoint transmit level

Automatic adjusting of modem module endpoint Z

15


(6 of 10)



Data (DDS only)

Error correction 16 1 to 3 1 = do not use EC (error correction)

2 = use only EC resources

3 = use EC resources where available (default)

Other

Protection 17 0 to 2 0 = do not protect (default)

1 = may protect

2 = must protect

Switching mechanism 18 0, 1 0 = nonrevertive (default)

1 = revertive

WTR timer 19 0 to 60 default = 5

Hold off timer 20 0 to 100 default = 0

Cross-connected endpoint A

21 2 Set to 2

2 = uses cross-connected endpoints

Cross-connected endpoint Z

22

Primary ISDN 23 0 to 3 0 = must avoid (default)

1 = use if necessary

2 = may use

3 = must use

Alternate ISDN 24

Verification 25 1, 2 1 = enabled

2 = disabled

ISDN dialing mode A 26 1, 2 1 = dial

2 = answerISDN dialing mode B 27

AC15A 28 1, 2 1 = disabled

2 = enabled

Not supported for VSC endpointsAC15Z 29

EC loss level for endpoint A

30 0 to 120 default = 60

Valid only if echo cancellation is enabled

Can be configured while the call is connected

When "Auto Adjust EC Loss Level" is enabled, the value will be rounded up or down to 3 or 6 dBm0 for VSCs. When "Auto Adjust EC Loss Level" is disabled, the path will be set to WFR if the value is not within the range.

EC loss level for endpoint Z

31

Nonlinear suppression threshold for endpoint A

32 –50 to –10 default = –40

Nonlinear suppression threshold for endpoint Z

33

Super Tandem HCV endpoint A (TDM voice)

34 2, 3 2 = must use

3 = may use or avoid (default)

Not supported for VSC endpointsSuper Tandem HCV endpoint Z (TDM voice)

35


(7 of 10)



Compressed voice 36 2, 3 2 = must use


Silence detection for endpoint A

37 1, 2 1 = enabled (default)

2 = disabled

Valid only for VSC endpoints

For symmetrical connections, the source and destination endpoints must have the same value for this attribute.

Silence detection for endpoint Z

38

Silence breaktime for endpoint A

39 80 to 300000 default = 100

Time in ms

Not valid for VSC endpointsSilence breaktime for endpoint Z

40

Transmission muting for endpoint A

41 1, 2 1 = disabled (default)

2 = enabled

Valid for VSC endpoints configured for CAS

For symmetrical connections, the source and destination endpoints must have the same value for this attribute.

Transmission muting for endpoint Z

42

EC tail length for endpoint 1

43 1 to 3 1 = normal (12 ms)

2 = extended (32 ms)

3 = normal or Extended

Not valid for VSC endpointsEC tail length for endpoint 2

44

Auto adjust EC loss level at endpoint A

45 1, 2 1 = enable


Auto adjust EC loss level at endpoint Z

46

Post/High Pass Filter at endpoint A

47 1, 2 1 = enable (default)

2 = disable


Can be updated while call is connectedPost/High Pass Filter at endpoint Z

48

Minimum network jitter tolerance at endpoint A

49 1 to 130 default = 10

Value in ms

Can be updated while call is connected

The cpTypes 49 and 50 are valid only when all of the following conditions are met:

• the endpoint is on a T1/E1 VSC• the path is a voice path• cpType 5 (May Use ATM) of the commonProfile attribute

of the bMGroomedCircuit object is set to 2 (Yes)• cpType 6 (Use Frame Relay) of the commonProfile

attribute of the bMGroomedCircuit object is set to 2 (Disable)

Minimum network jitter tolerance at endpoint Z

50

Fax/Modem Bypass 51 1, 2 1 = enable


Bypass Coder 52 46, 51 default = 46

46 = G.711 32 kb/s

51 = G.726 32 kb/s

Valid only when Fax/Modem Bypass is enabled


(8 of 10)



Ingress CAS Idle Suppression Code at endpoint A

53 A 4-bit bitmap consisting of 0 and 1

Valid only when transmission muting is enabled

Ingress CAS code at one endpoint must match egress CAS code at the other endpoint.

Ingress CAS Idle Suppression Code at endpoint Z

54

Egress CAS Idle Suppression Code at endpoint A

55

Egress CAS Idle Suppression Code at endpoint Z

56

Ingress CAS Idle Suppression Code Mask at endpoint A

57 default = 1111

0 = do care

1 = don’t care

Valid only when transmission muting is enabledIngress CAS Idle Suppression Code Mask at endpoint Z

58

Egress CAS Idle Suppression Code Mask at endpoint A

59

Egress CAS Idle Suppression Code Mask at endpoint Z

60

Compress In 61 0, 1 0 = TDM

1 = ATM

Enables voice compression in either TDM or ATM

Frozen to TDM if May Use ATM is set to no; frozen to TDM for T1CE interface; for T1VS interface, can be either TDM or ATM

Facility handling 62 1, 2 1 = passing

2 = blocking

Valid only when Compression cpType 2 sets to G3 Fax/Modem related values


(9 of 10)



Table 24-5 describes voice signaling types for cpTypes 6 and 7 of tDMProfile attribute.

Compression type 63 0 to 11 As of Release 5.0, any application development that would normally use cpType 2 should instead use cpTypes 63 to 67. The cpTypes 63 to 67 have replaced cpType 2, which will not be developed beyond cpValue 142.

Existing applications that use cpType 2 require no changes but they may be modified to use cpTypes 63 to 67, since the functionality provided by cpTypes 63 to 67 fully implements the functionality provided by cpType 2.

0 = None (G.711)

1 = Delta ADPCM

2 = Transitional ADPCM

3 = HCV

4 = ACELP (G.729)

5 = LDCELP

6 = ACELP (G.729A)

7 = ACELP/ACELPA

8 = None (Clear Channel)

9 = ADPCM (G.726)

10 = Netcoder

11 = Dual Rate Speech Coder (G.723.1)

Compression rate 64 5300 to 32000 5300 b/s

6300 b/s

8000 b/s

9600 b/s

16000 b/s

32000 b/s

Rate depends on the Compression type, cpType 63

G3 Fax/Modem 65 0 to 3 0 = None

1 = Modem

2 = G3 Fax

3 = G3 Fax/Modem

Rate depends on the Compression type, cpType 63

Fax rate 66 2400 to 14400 2400 b/s

4800 b/s

9600 b/s

14400 b/s

Rate depends on the G3 Fax/Modem, cpType 65

Modem rate 67 4800 to 14400 4800 b/s

7200 b/s

9600 b/s

12000 b/s

14400 b/s

Rate depends on the G3 Fax/Modem, cpType 65


(10 of 10)



Table 24-5 Voice signaling types

Enumeration Voice signaling types Description

203 EM EandM

204 CEPTEM EandM for E1

205 T1EM EandM for T1

206 LGSMRD LGS Manual Ring Down

207 T1MRD Manual Ring Down in T1

208 CEPT_LGELCDC LGE Loop Calling Disconnect Clear for E1

209 CEPT_LGSLCDC LGS Loop Calling Disconnect Clear for E1

210 CEPT_LGEEC LGE Earth Calling for E1

211 CEPT_LGSEC LGS Earth Calling for E1

212 CEPT_LGSPLAR LGS Private Line Automatic Ring for E1

213 CEPT_LGSCBW LGS Central Battery Working for E1

214 CEPT_LGERE LGE Remote Extension for E1

215 CEPT_LGSRE LGS Remote Extension for E1

216 CEPT_BYPASSNOSIG No signaling for E1

217 T1_BYPASSSIG Signaling for T1

218 T1_BYPASSNOSIG No Signaling for T1

219 T1_LGSPLARD3 T1 LGS Private Line Automatic Ring - D3

220 T1_LGSLS LGS Loop Start for T1

221 T1_LGELS LGE Loop start for T1

222 T1_LGSGS LGS Ground Start for T1

223 T1_LGEGS LGE Ground Start for T1

224 T1_LGSPLAR LGS Private Line Automatic Ring for T1

225 R2D_LGS_PLAR LGS R2D Private Line Automatic Ring

226 R2D_LGS_LCDC LGS R2D Loop Calling Disconnect Clear

227 R2D_LGE_LCDC LGE R2D Loop Calling Disconnect Clear

228 R2D_CEPT_LGS_PLAR E1 LGS R2D Private Line Automatic Ring

229 R2D_CEPT_LGE_LCDC E1 LGE R2D Loop Calling Disconnect Clear

230 R2D_CEPT_LGS_LCDC E1 LGS R2D Loop Calling Disconnect Clear

231 R2D_CEPT_PLAR R2D Private Line Automatic Ring for E1

232 R2D_CEPT_LCDC R2D Loop Calling Disconnect Clear for E1

233 R2DEM R2D in EandM

234 LGSPLARD3 LGS Private Line Automatic Ring - D3

235 LGSDPO LGS Dial Pulse Originating

236 LGEDPT LGE Dial Pulse Terminate

237 LGELCDC LGE Loop Calling Disconnect Clear

(1 of 2)



24.9 frameRelayProfile attribute

Table 24-6 describes the frameRelayProfile attribute circuitProfile characteristics.

Table 24-6 frameRelayProfile attribute circuitProfile characteristics

238 LGSLCDC LGS Loop Calling Disconnect Clear

239 LGEEC LGE Earth Calling

240 LGSEC LGS Earth Calling

241 LGSPLAR LGS Private Line Automatic Ring

242 LGSCBW LGS Central Battery Working

243 LGEGS LGE Ground Start

244 LGSGS LGS Ground Start

245 LGSGSEM LGS Ground Start EandM

246 LGSLSEM LGS Loop Start EandM

247 LGELS LGE Loop Start

248 LGSLS LGS Loop Start

249 LGERE LGE Remote Extension

250 LGSRE LGS Remote Extension

251 LGEINTL1 LGE International 1

252 LGSINTL1 LGS International 1

253 BYPASSNOSIG No signaling

254 CEPT_BYPASSSIG Signaling for E1

255 UNKNOWN Unknown

Enumeration Voice signaling types Description

(2 of 2)


Frame Relay

Source Bc (1) (2) [Bc] 0 to 483.647 Source committed burst rate (kb)

Source Be (1) (2) [Be] Source excess burst rate (kb)

Source CIR (1) (2) [CIR] 0 to 4421 Source committed information rate (kb/s)

Dlcia (1) (2) [dlcia] 16 to 1007, 1022 Frame relay virtual endpoint A

Dlciz (1) (2) [dlciz] Frame relay virtual endpoint Z

Use ATM (1) [useatm] TRUE or FALSE TRUE = try to route over ATM link

FALSE = do not try to route over ATM link

Destination Bc (2) 1 0 to 2147483.647 Destination committed burst rate (kb)

Destination Be (2) 2 Destination excess burst rate (kb)

(1 of 6)



Destination CIR (2) 3 0 to 4421 Destination committed information rate (kb/s)

Frame Relay over ATM

DE/CLP mapping

(frame relay to ATM)

4 3 to 5 3 = DE (CLP)

4 = 0 (CLP)

5 = 1 (CLP)

DE/CLP mapping

(ATM to frame relay)

5 1, 2, 6, 7 1 = CLP (DE)

2 = FR–SSCS (DE)

6 = 0 (DE)

7 = 1 (DE)

Source VC shaping group 6 0 to 8 Indicates the group used by the source node

0 = off


2 = 32 kb/s

3 = 64 kb/s

4 = 128 kb/s

5 = 256 kb/s

6 = 512 kb/s

7 = 1024 kb/s

8 = 2048 kb/s

Destination VC shaping group 7

ATM protocol 8 0, 10 0 = none

10 = annex A bidirectional (default)

ATM heartbeat polling cycle 9 60 to 3600 default = 180 (seconds)

ATM status message rate 10 1 1 = in pols (default)

ATM message timeout 11 60 to 3600 default = 200 (seconds)

VPI 12 0 to 255 For ATM endpoints

See the ATM node documentation for further restrictions about the use of VPI and VCI values.

VCI 13 1 to 4096

Source pacing 14 0, 1 0 = source pacing off (default)

1 = source pacing on

Interworking 15 2, 3 2 = network (default)

3 = service

SIW protocol 16 0, 1 Set to 0

0 = transparent

1 = translated

EFCI 17 0, 1 default = 1 for FR/ATM over ABR

default = 0 for all other path types

0 = EFCI equals FECN

1 = EFCI equals 0

Frame relay encapsulation 19 0 to 5 0 = none

1 = RFC 1490 external

2 = Annex G external

3 = Annex G internal (default)

4 = RFC 1490 internal

5 = XFR


(2 of 6)



Connection type 20 1, 2 1 = symmetrical (default)

2 = asymmetrical

Destination pacing 21 0, 1 0 = destination pacing off

1 = destination pacing on

HDLC encapsulation 22 0 to 3 0 = no encapsulation

1 = encapsulation at both ends

2 = encapsulation at endpoint A only

3 = encapsulation at endpoint Z only

For setting HDLC encapsulation for endpoint A or Z, set the corresponding mandatory but dependant attribute dlci correctly.

Interface speed 23 0 to 1 984 000 b/s When this cpType signifies the Interface Speed, it is used for paths other than frame relay.

Access Rate 23 1 to 44 210 000 b/s default = 64000 b/s

When this cpType signifies the Access Rate, it is used for SPVC frame relay paths with physical source and logical destination endpoints.

Max HDLC frame length 24 2 to 8192 default = 1598

The maximum is 8192 when the:

• source and destination endpoints of the frame relay path are circuits contained within 3-DS3 frame processing cards, and the HDLC encapsulation is set to 1

• source endpoint of the frame relay path is a circuit contained within a 3-DS3 frame processing card, and the HDLC encapsulation is set to 2

• destination endpoint of the frame relay path is a circuit contained within a 3-DS3 frame processing card and HDLC encapsulation is set to 3

In all other cases, the maximum is 4472.

Max packet length 25 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096

default = 512


(3 of 6)



FR application 27 1 to 8, 10 1 = PVC (default)

2 = SPVC

3 = signaling link

4 = PNNI link

5 = SVC

6 = interim link management interface

7 = CPSS

8 = out-of-band signaling link

10 = may use SPVC

For frame relay paths with the source endpoint terminating on a basic VLAN, the valid values of cpType 34 are 1 and 10.

For frame relay paths with the destination endpoint terminating on a basic VLAN, the valid values of cpType 34 are 1, 2, and 10.

For frame relay paths terminating on a port or circuit of a 3-DS3 frame processing card, the valid values are 1, 2, and 10.

Max admin weight mode 28 –1 to 2147483647 default = –1

Max admin weight 29 0 to 214483647 Maximum admin weight

FR Service Category 30 1 to 4 1 = best effort

2 = committed-throughput

3 = low delay

4 = real-time (default)

SLP endpoint A (3) 33 1 to n Signaling link profile to use at endpoint A

See section 37.5 for the SLP managedProfileID

SLP endpoint Z (3) 34 Signaling link profile to use at endpoint Z

See section 37.5 for the SLP managedProfileID

Associated call ID 35 call id Call ID of associated SVC carrying the frame relay link

Fragmentation mode for endpoint A

38 0 to 3 0 = disabled

1 = reassemble

2 = fragment only

3 = fragment and reassemble

Fragmentation size for endpoint A

39 32, 34, 82, 128 or 130 default = 82

Size in bytes

Fragmentation mode for endpoint Z

40 0 to 3 0 = disabled

1 = reassemble

2 = fragment only

3 = fragment and reassemble

Fragmentation size for endpoint Z

41 32, 34, 82, 128 or 130 default = 82

Size in bytes

VSVD closed loop congestion control

42 1, 2 1 = enabled


Source closed loop congestion control information rate

43 1 to (CIR + EIR) default = 32

EIR = (source be x source CIR) / source Bc

Note: If source Bc = 0, then EIR = source Be


(4 of 6)



Destination closed loop congestion control information rate

44 1 to (CIR + EIR) default = 32

EIR = (destination Be x destination CIR) / destination Bc

Note: If destination Bc = 0, then EIR = destination Be

DTMF detection 45 1, 2 1 = enabled (default)

2 = disabled

Valid only for the following VSC endpoints:

• G723.1, 5.3 or 6.3 kb/s• G729A, 8 kb/s• NetCoder, 8 or 9.6 kb/s

DTMF bandwidth optimization 46 1, 2 1 = enabled (default)

2 = disabled

Valid only if DTMF detection is enabled

alternateDLCIa 47 16 to 1007, 1022 Frame relay virtual endpoint A for alternate endpoint.

This cpType is applicable when the circuitProfileName 1:alternateATPId of the commonProfile attribute is set to a value other than NULL.

alternateDLCIz 48 16 to 1007, 1022 Frame relay virtual endpoint Z for alternate endpoint.

This cpType is applicable when the circuitProfileName 1:alternateZTPId of the commonProfile attribute is set to a value other than NULL.

alternateVPI 49 0 to 255 For alternate ATM endpoint.

This cpType is applicable when the circuitProfileNames 1:alternateATPId or 2:alternateZTPId of the commonProfile attribute of the bMGroomedCircuit is set to a value other than NULL.

alternateVCI 50 0 to 4096 For alternate ATM endpoint.


(5 of 6)



Notes(1) This cpType is always present in the attribute.(2) If only one endpoint is frame relay; the other must be ATM.(3) The variable X changes depending on the release supported. SLPs are managed by the 5620 NM. Each 5620 NM can

manage 20 SLPs for 7470 MSP nodes, 10 SLPs for 36120 nodes, and 4 SLPs for 36160 switches. The 7470 MSP nodes prior to Release 3.1 support only 10 SLPs. Release 3.1 of the 7470 MSP can support 20 SLPs with an extended range of signaling protocols. See the 7470 MSP and 5620 NM documentation for further details.

Mapping Method 51 1 to 3 default = system-wide mapping method value, which is configured using NW_config, when the source or destination endpoint is from a supported node

1 = FRATM/B-ICI method (default when the source or destination endpoint is from an unsupported node)

2 = B-ICI method 2: PIR prop. to AR

3 = B-ICI method 2: PIR prop to CIR

The options are 1, 2, and 3 when the node types for the frame relay path endpoints are:

• TDM - TDM• TDM - ATM (supported)• ATM (supported) - TDM• ATM (supported) - ATM (supported)

The option is 1 when the node types for the frame relay path endpoints are:

• TDM - ATM (unsupported)• ATM (unsupported) - TDM• ATM (supported) - ATM (unsupported)• ATM (unsupported) - ATM (supported)• ATM (unsupported) - ATM (unsupported)

This cpType is read-only when the frame relay path is connected.

Supported nodes are:

• 7270 MSC, Release 8.0 HLS#3.0 or later • 7470 MSP, Release 8.0 HLS#3.0 or later• 7670 ESE, Release 4.0 HLS#3.0 or later• TDM nodes with valid frame relay path

endpoints

Overhead Factor Frame Size 52 20 to 4472 default = system-wide overhead factor frame size value, which is configured using NW_config, when the source or destination endpoint is from a supported node

default = 99, when the source or destination endpoint is from an unsupported node

The number of octets in frames.

This cpType is read-only when:

• cpType 51 (Mapping Method) is set to 1 (FRATM/B-ICI method)

• the frame relay path is connected

Supported nodes are:

• 7270 MSC, Release 8.0 HLS#3.0 or later • 7470 MSP, Release 8.0 HLS#3.0 or later• 7670 ESE, Release 4.0 HLS#3.0 or later


(6 of 6)



24.10 aTMProfile attribute

The aTMProfile attribute of the bMGroomedCircuit object has been implemented using both circuitProfile and circuitProfileName. Table 24-7 describes the aTMProfile attribute circuitProfileName characteristics. Table 24-8 describes the aTMProfile attribute circuitProfile characteristics. See section 24.7 for more information.

Table 24-7 aTMProfile attribute circuitProfileName characteristics

Notes(1) Available only for ATM Point-To-Multipoint path.(2) Available only for SPVC paths with dual endpoints.(3) An AESA value identifies the logical endpoint of an SPVC path. Each character represents a hex nibble. To calculate the

AESA for a physical endpoint, use the following definition:AA-AAAA-AAAAAAAAAAAAAAAAAAAA-BBBBBB-CCCC-DD-EEA = the Internal Switch Subscriber Prefix for the node (26 characters)B = the OUIC = shelf and slot informationD = port numberE = contains either the DS1 channel number (for circuit emulation cards) or is zero for all other card typesIf an OSS request for a 5620 NM-managed node contains the AESA address, it must satisfy the above representation (including hyphens); otherwise, the 5620 CORBA may fail the request.

(4) Available for ATM VCC and VPC SPVCs and HSPVCs, and frame relay, voice, TDM, and voice over frame relay paths with the ATM segment being SPVC or HSPVC. The 5620 NM uses the AESA-based NCCI format which combines the NCCI Root and NCCI Index, for example, a12-3456-78901234567890123456-008021-0023-0100;1234567890ABCdef

Characteristic circuitProfileName SimpleNameType String

Description

IP multicast address (1) ipmcAddrstring Where string is a valid Class D IP address, which is within the range of 224.0.0.3 to 239.255.255.255

Source AESA address (2) srcAESAAddr string Where string is 40 characters; each character can take the values (0 to 9), (a to f) and (A to F) (3)

default = undefinedDestination AESA address (2) dstAESAAddr string

NCCIRoot (4) 9:NCCIRoot string Where string is 47 characters; each character can take the values (a + 40 hex + 5 hyphens + 1 null character)

NCCIIndex (4) 10:NCCIIndex string Where string is 17 characters; each character can take the values (0 to 9 and a to f/A to F, 16 hex characters + 1 null character)

Associated VLANs 11:assocVlanIds string Where string is a list of VLAN IDs which are assigned to the virtual ATM port. The string is a sequence of numbers separated by commas.

For example, the string 1,234, 4091 represents VLAN IDs 1, 234, and 4091.

The values of VLAN IDs are 1-4094, and 4096. VLAN ID 4095 is reserved.

default = NULL



Table 24-8 aTMProfile attribute circuitProfile characteristics


Vpia (1) (2) [vpia] 0 to 4095 Vpia = virtual path endpoint A

Vpiz = virtual path endpoint Z

Range is 0 to 15 for VPC paths.

Not valid for VSC endpoints

The cell relay endpoint type determines the value for cell relay endpoints.

For VCC paths with endpoints on 7390 NT OC3/STM-1 ports, the range is 0 to 255.

For VCC paths with endpoints on Quad T1/E1 IMA ports, the values are 0 to 127.

For VCC paths on a CR port in the OC3/STM1 MS card, the values are 0 to 255 regardless of the value of cpType 20 of the groomedCircuitTPProfile.

For VPC paths with endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and with cpType 20 of the groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to B-ICI/B-ISSI for both endpoints, the range is 0 to 4095.

For VPC paths with endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and with cpType 20 of groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to UNI for both endpoints, the range is 0 to 255.

See the ATM node documentation for additional restrictions about the use of VPI and VCI values.

Vpiz (1) (2) [vpiz]

Vcia (1) (2) [vcia] 1 to 65535 Vcia = virtual circuit endpoint A

Vciz = virtual circuit endpoint Z

Not valid for VSC endpoints

For VCC paths with endpoints on 7390 NT OC3/STM-1 ports, the valid values are 4, 32 to 159.

For VCC paths with endpoints on Quad T1/E1 IMA cards, the valid values are 4, 32 to 1023.

The cell relay endpoint type determines the value for cell relay endpoints.

See the ATM node documentation for further restrictions about the use of VPI and VCI values.

Vciz (1) (2) [vciz]

Source SIR/MIR (1) [sir] -1, 0, or 1 to n Where n is the maximum allowable bandwidth of endpoints; rates are in kb/s

For 7300 ASAM nodes, -1 indicates that the values must be configured from traffic descriptor profiles; see chapter 37 for more information.

For Conklin FASTmux 2000 nodes, the default is 64000 for ADSL profiles 1, 5, 9, and 13; 128000 for all other ADSL profile

For all other nodes, -1 = don’t care; the create response will identify the default values

Source PIR (1) (9) [pir]

Alarm (1) [alm] TRUE or FALSE

TRUE = generate alarm if VP layer connectivity is lost

FALSE = do not generate alarm if VP layer connectivity is lost (default)

Set to FALSE for SPVCs

(1 of 13)



QOS (1) [qos] 1 to 4, 6 1 = CBR service category; default depends on endpoint type

2 = nrt-VBR (non-real-time VBR) service category

3 = ABR service category

4 = UBR service category

6 = rt-VBR (real-time VBR) service category

For 7300 ASAM Release 4.1, the service category is read-only and is either CBR or UBR, depending on the QOS configured on the port.

For 7300 ASAM Release 4.2 or later, the service category is read-only, and may be CBR, UBR, rt-VBR, or nrt-VBR, depending on the QOS configured on the port.

For 7321 RU, Release 2.1 or later, the service category is read-only, and may be CBR, nrt-VBR, UBR, or rt-VBR.

For VCC, VPC, and frame relay paths riding a PSN link, this cpType is applicable when cpType 164 is set to 2, and cpType 165 is set to 9, 10, 12, or 13.

For AAL2 VoP multiplexer endpoints, the values are 1 and 6.

For AAL1 VoP multipexer endpoints, the value is 1.

Must use VPC link 1 1, 2 default = 1 for PVCs; 2 for SPVCs and cannot be changed

1 = no; VCC path does not need to be routed over an ATM VPC link

2 = yes; VCC path must be routed over an ATM VPC link

SPVCs must use VPC links.

If cpType 164 is set to 2, the attribute is set to 1.

Connection type (3) 2 1, 2, 3 1 = symmetrical (default)

2 = asymmetrical

3 = multipoint

cpValue 3 is not supported for paths riding a PSN link.

Source traffic descriptor (4) 3 1 to 5 Default depends on service category

1 = tag all cells

2 = PIR 0+1

3 = PIR 0+1/SIR 0+1

4 = PIR 0+1/SIR 0

5 = PIR_0+1/MIR_0+1

Source traffic policing option (4) (5) (6)

4 1 to 7 1 = disable (default)

2 = tag

3 = discard

5 = tag all

6 = enabled

7 = use signalled

Not valid for VoFR paths

Source PIR 0+1 (7) (9) 5 0 to n where n is the lower of the maximum endpoint port speeds

For Conklin FASTmux 2000 nodes, the default is 64000 for ADSL profiles 1, 5, 9, and 13; 128000 for all other ADSL profiles

Source CDVT (4) 6 1 to 2000000 default = 250


For Conklin FASTmux 2000 nodes, the default is 250, and the range is 1 to 190000


(2 of 13)



Source SIR 0 (4) (7) (8) (10) 7 0 to n where n is the lower of the maximum endpoint port speeds

Source MBS 0 (4) (7) (10) 8 1 to n where n is the maximum allowable MBS range

Source SIR/MIR 0+1 (4) (7) (11) 9 0 to n where n is the lower of the maximum endpoint port speeds

Source MBS 0+1 (4) (7) (11) 10 1 to 255 default = 32

Source SIR_1 11 0 to n where n is the lower of the maximum endpoint port speeds

Value must be less than or equal to the source PIR 0+1 value.

Source MBS_1 12 1 to 210 default = 32

Source Q_Factor mode 13 0, 1 0 = auto (default)

1 = manual

Source Q_Factor 14 1 to 199 default = 50

Source horizontal resolution 15 0, 1 0 = full (default)

1 = half

Source police discard 16 0, 1 0 = field discard (default)

1 = frame discard

Destination traffic descriptor (4) 19 1 to 5 Default depends on service category

1 = tag all cells

2 = PIR 0+1

3 = PIR 0+1/SIR 0+1

4 = PIR 0+1/SIR 0

5 = PIR_0+1/MIR_0+1

Destination traffic policing option (4) (5) (6)

20 1 to 7 1 = disable

2 = tag

3 = discard

5 = tag all

6 = enabled

7 = use signalled

Not valid for VoFR paths

Destination PIR 0+1 (7) 21 0 to n where n is the lower of the maximum endpoint port speeds

Destination CDVT (4) 22 1 to 2000000 default = 250


Destination SIR 0 (4) (7) (10) 23 0 to n where n is the lower of the maximum endpoint port speeds

Destination MBS 0 (4) (7) (10) 24 1 to n where n is the maximum allowable MBS range

Destination SIR/MIR 0+1 (4) (7) (11)

25 0 to n where n is the lower of the maximum endpoint port speeds

Destination MBS 0+1 (4) (7) (11) 26 1 to 255 default = 32

Destination SIR_1 27 0 to n where n is the lower of the maximum endpoint port speeds

Value must be less than or equal to the destination PIR 0+1 value

Destination MBS_1 28 1 to 210 default = 32

Destination Q_Factor mode 29 0, 1 0 = auto (default)

1 = manual

Destination Q_Factor 30 1 to 199 default = 50


(3 of 13)



Destination horizontal resolution

31 0, 1 0 = full (default)

1 = half

Destination police discard 32 0, 1 0 = field discard (default)

1 = frame discard

VC application (3) 34 1 to 8, 10 1 = PVC (default)

2 = SPVC

3 = Signaling link

4 = PNNI link

5 = SVC

6 = Interim link management interface

7 = CPSS

8 = out-of-band signaling link

10 = may use SPVC

For VCC paths terminating on a Basic or Enhanced VLAN endpoint, the valid values are 1, 2, and 10.

For VCC paths with a VoP multiplexer on one endpoint, the valid values are 1, 2, and 10.

Max admin weight mode 35 –1 to 214748647

default = –1

Max admin weight 36 1 to 2147483647

Not applicable

Source SLP ID 37 n See Table 37-2 for details

Destination SLP ID 38

Circuit emulation data octets 43 1 to 47 default = 47

Circuit emulation playout buffer (time)

44 10 to 320 For E3CCE2 cards, element-managed devices, and circuit emulation endpoints on pre-release 4.0 of the 7670 RSP, 7670 RSP ESE, 7470 MSP, and 7270 MSC:

default = 145; cpValue = 10 to 320

For circuit emulation NIUs:


For all other cases:


Source circuit map 45 0 to 2147483647

default = 0

Used for bit masking

0xFFFFFF hex value

Destination circuit map 46 0 to 2147483647

default = 0

Used for bit masking

0xFFFFFF hex value

Source cell delay variance (4) 47 250 to 10000 Valid for rt-VBR and CBR

Source cell loss ratio (4) 48 1 to 10 nrt–VBR = 1 to 7 (10-1 to 10-7); default = 7


CBR = 1 to 10 (10-1 to 10-10); default = 10

Destination cell delay variance (4)

49 250 to 10000 Valid for rt-VBR and CBR


(4 of 13)



Destination cell loss ratio (4) 50 1 to 10 nrt–VBR = 1 to 7 (10-1 to 10-7); default = 7


CBR = 1 to 10 (10-1 to 10-10); default = 10

Source rate increase factor (12) 51 0 to 15 default = 0

Destination rate increase factor (12)

52

Source rate decrease factor (12) 53 0 to 15 default = 15

Destination rate decrease factor (12)

54

Source special study for VCC/VPC path-ends (13)

55 1, 2 default = 2

Destination special study for VCC/VPC path-ends (13)

56

Source initial information rate 57 n bits/s

Where n >= Source SIR 0+1 and n <= Source PIR 0+1

Destination initial information rate

58 n bits/s

Where n >= Destination SIR 0+1 and n <= Destination PIR 0+1

Source frame discard (4) 59 1, 2 1 = enable


Not valid for rt-VBRDestination frame discard (4) 60

Source administrative state 61 1, 2 1 = DS1 port status enabled

2 = DS1 port status disabledDestination administrative state

62

Source framing 63 1 to 4 1 = DS3/E3 CCE framing - ESF

2 = DS3/E3 CCE framing - SF

3 = DS3/E3 CCE framing - transparent

4 = DS3/E3 CCE framing - basic

Destination framing 64

Output timing/synchronization source

65 1, 3 to 5 1 = sync residual (SRTS)

3 = adaptive clock recovery

4 = synchronous

5 = SRTS and adaptive clock

Source FDL mode 66 34, 35 or 38 34 = DS3 CCE FDL mode - ignore FDL

35 = DS3 CCE FDL mode - 54016

38 = DS3 CCE FDL mode -T1.403Destination FDL mode 67

Playout buffer time 68 10 to 320 For E3CCE2 cards, element-managed devices, and circuit emulation endpoints on pre-release 4.0 of the 7670 RSP, 7670 RSP ESE, 7470 MSP, and 7270 MSC:


For circuit emulation NIUs:


For all other cases:



(5 of 13)



Source alarm declaration time 69 1 to 300 Alarm declaration time

Destination alarm declaration time

70

Source alarm clearing time 71 1 to 300 Alarm clearing time

Destination alarm clearing time 72

Source endpoint connection type

73 1 to 3 1 = endpoint that is not cross-connected

2 = cross-connected endpoint (default)

3 = terminated endpointDestination endpoint connection type

74

Source use default CDVT (4) 75 1, 2 1 = enable


Indicates whether the default CDVT from the node tables gets used or not


Destination use default CDVT (4)

76

Source use shaping ingress 77 1, 2 1 = enable

2 = disable

Indicates whether traffic policing applies to the source/destination of the VCCs

Destination use shaping ingress

78

Source cell tagging 79 1, 2 1 = disable

2 = enableDestination cell tagging 80

Admin State 81 1 Set to 1

1 = enable

Interworking type 82 3, 4 3 = unframed

4 = framed

Sequence number 83 0 to 1 0 = slow (default)

1 = fast

clpBit 85 0 clpBit

Source accounting 86 0 to 3 0 = ATM account (none)

1 = ATM account A

2 = ATM account B

3 = ATM account (both)

Destination accounting 87

Source link type 88 0, 1 0 = national (default)

1 = internationalDestination link type 89

Source network border 90 0, 1 0 = intranetwork (default)

1 = Internetwork

Destination specification method for SPVC paths

91 1, 2 1= physical termination point (default)

2 = logical termination point

Source endpoint type 92 1, 2 1 = UNI access ID

2 = SPVC custom ID

Source SPVC custom ID 93 n ID must be a numeric value.

Source UNI access ID 94

Source directory number pointer

95 n Directory number pointer must be a numeric value.


(6 of 13)



Source VPCI 96 0 to 65535 Source VPCI

Destination VPCI 97 Destination VPCI

Source retry interval 98 0 to 3600 In seconds

Destination network border 99 0, 1 0 = intranetwork (default)

1 = internetwork

Source use shaping egress 103 1, 2 1 = enable

2 = disable

Indicates whether traffic policing applies to the source/destination of the VCCs

Destination use shaping egress

104

ILMI application for source 105 11, 12 11 = VP service (default)

12 = port serviceILMI application for destination 106

Source profile ID for AAL1 performances

107 n Identifies a profile ID

Destination profile ID for AAL1 performances

108

Speech packing factor 109 n Value depends on the compression type used

See Table 24-9

Bypass packing factor 110 n Valid only when Bypass Coder is enabled; valid values depend on the bypass coder type

See Table 24-9 for details

Clear channel bypass packing Factor


OAM-CC cell flow 112 1 to 4 1 = disabled (default)

2 = A to Z

3 = Z to A

4 = bidirectional

When the path endpoint is a VoP multiplexer, the cpType is set to 1 and cannot be changed.

Multinetwork segment 113 1, 2 default = 1

1 = no

2 = yes

OAM-PM cell flow 114 1 to 4 1 = disabled (default)

2 = A to Z

3 = Z to A

4 = bidirectional

When the path endpoint is a VoP multiplexer, the cpType is set to 1 and cannot be changed.

OAM-PM TCA

A to Z direction

115 n The integer value corresponds to the managedProfileID attribute of the managedProfile object.

OAM-PM TCA

Z to A direction

116 n Integer value corresponds to the managedProfileID attribute of the managedProfile object.

DMDS 117 1, 2 1 = enable


Source specification method for SPVC paths

118 1, 2 1= physical termination point (default)

2 = logical termination point


(7 of 13)



Logical endpoint type 119 1, 2 1 = ATM (default)

2 = frame relay

Reroute on LOC 120 1, 2 1 = disabled (default)

2 = enabled

This cpType is set to 1 and cannot be changed when the path endpoint is a VoP multiplexer and cpType 34 is set to 2.

sourceRerouteLoc 121 2, 3 2 = enable at UNI (default)

3 = enable at NNIdestinationRerouteLoc 122

Src traffic descriptor profile upstream

123 managedProfileID value

See section 37.5 for information about managedProfileID values.

managedProfileID value for traffic descriptor profile of path endpoint A

Dst traffic descriptor profile upstream

124 managedProfileID value for traffic descriptor profile of path endpoint Z

Src traffic descriptor profile downstream

125 managedProfileID value for traffic descriptor profile of path endpoint A

Dst traffic descriptor profile downstream

126 managedProfileID value for traffic descriptor profile of path endpoint Z

Src traffic descriptor profile upstream (hub ASAM)

127 managedProfileID value for traffic descriptor profile of path endpoint A (hub ASAM)

Dst traffic descriptor profile upstream (hub ASAM)

128 managedProfileID value for traffic descriptor profile of path endpoint Z (hub ASAM)

Src traffic descriptor profile downstream (hub ASAM)

129 managedProfileID value for traffic descriptor profile of path endpoint A (hub ASAM)

Dst traffic descriptor profile downstream (hub ASAM)

130 managedProfileID value for traffic descriptor profile of path endpoint Z (hub ASAM)

cpType 131 131 — Reserved

cpType 132 132 — Reserved

Path end A ingress label 133 131073 to 1048575

Ingress label on node A

Path end B ingress label 134 131073 to 1048575

Ingress label on node B

Interworking mode 135 0, 1 0 = cell

1 = frame

Holds the interworking mode

Trunk group index A 136 0 to 255 Holds the trunk group index, which contains the values of the TGI at endpoint A of the VPCL

Trunk group index B 137 0 to 255 Holds the trunk group index, which contains the values of the TGI at endpoint Z of the VPCL

Source GCAC Bandwidth 138 1 to 2147483647

Indicates the source GCAC bandwidth of an SPVC path, in Kb/s.

default = 1

Destination GCAC Bandwidth 139 1 to 2147483647

Indicates the destination GCAC bandwidth of an SPVC path, in Kb/s.

default = 1


(8 of 13)



Encapsulation at Endpoint A 140 1 to 4 1 = Snap IP

2 = Snap Bridged (default)

3 = Mux IP

4 = Mux Bridged

When cpType 154 is set to 4, the valid values are 2, 4.

Encapsulation at Endpoint Z 141 1 to 4 1 = Snap IP

2 = Snap Bridged (default)

3 = Mux IP

4 = Mux Bridged

When cpType 155 is set to 4, the valid values are 2, 4.

Ingress VLAN Option at Endpoint A

142 1, 2 This cpType is applicable if cpType 154 is set to 1

1 = Strip

2 = Keep

The default is 1

Ingress VLAN Option at Endpoint Z


1 = Strip

2 = Keep

The default is 1

Egress VLAN Option at Endpoint A


1 = Stack

2 = Translate

The default is 1.

Egress VLAN Option at Endpoint Z


1 = Stack

2 = Translate

The default is 1.

Profile Id at Endpoint A 146 1 to 100 The ID of the first profile encountered in the 5620 NM with COS1.

If the profile does not exist, the default is 1.

When cpType 154 is set to 4, this cpType is not applicable.

Profile Id at Endpoint Z 147 1 to 100 The ID of the first profile encountered in the 5620 NM with COS1.

If the profile does not exist, the default is 1.


Default COS at Endpoint A 148 1 to 8 1 = COS1

2 = COS2

3 = COS3

4 = COS4

5 = COS5

6 = COS6

7 = COS7

8 = COS8

The default is 8.



(9 of 13)



Default COS at Endpoint Z 149 1 to 8 1 = COS1

2 = COS2

3 = COS3

4 = COS4

5 = COS5

6 = COS6

7 = COS7

8 = COS8

The default is 8.


Bandwidth Mode at Endpoint A 150 1, 2 1 = Shared

2 = Reserved

The default t is 1.


Bandwidth Mode at Endpoint Z 151 1, 2 1 = Shared

2 = Reserved

The default is 1.


Bandwidth Reserved at Endpoint A

152 0 to the GigE port line rate

The line rate of the GigE port.

If cpType 150 is set to 1, the cpType is set to 0. If cpType 150 is set to 2, the cpType is set to the SIR of the destination endpoint. The default is 1000.


Bandwidth Reserved at Endpoint Z

153 0 to the GigE port line rate

The line rate of the GigE port.

If cpType 151 is set to 1, the cpType is set to 0. If cpType 151 is set to 2, the cpType is set to the SIR of the source endpoint. The default is 1000.


Interface Type at Endpoint A 154 17, 1, 4 17 = port interface

1 = VLAN interface

4 = none

If the GigE port is configured as Tag Unaware, the cpType is set to 17.

Interface Type at Endpoint Z 155 17, 1, 4 17 = port interface

1 = VLAN interface

4 = none

If the GigE port is configured as Tag Unaware, the cpType is set to 17.

VLAN Id at Endpoint A 156 1 to 4094 The VLAN Id.

If the GigE port is configured as Tag Unaware, the cpType is not used.

VLAN Id at Endpoint Z 157 1 to 4094 The VLAN Id.

If the GigE port is configured as Tag Unaware, the cpType is not used.

VLAN Tag Mode 158 1, 2 1 = Tagged (default)

2 = Untagged

Specifies the VLAN tagging mode of the virtual ATM port.


(10 of 13)



External OAM CC (Endpnt A) 159 1 to 4 1 = none (default)

2 = A to External

3 = External to A

4 = Bidirectional External

External OAM CC (Endpnt B) 160 1 to 4 1 = none (default)

2 = B to External

3 = External to B

4 = Bidirectional External

OAM-CC Status 161 0, 2, 3, 11 0 = Idle (default)

2 = Applied

3 = Failed

11 = Applied NMTI

OAM-PM Status 162 0, 2, 3, 11 0 = Idle (default)

2 = Applied

3 = Failed

11 = Applied NMTI

12 = Failed (Limit Exceeded)

SPVC LOC Status 163 0, 2, 3, 11 0 = Idle (default)

2 = Applied

3 = Failed

11 = Applied NMTI

May Use PSNL 164 1, 2 1 = no (default)

2 = yes

If cpType 34 is set to 5 or 10, the cpType is set to 1.

PW Encap Type 165 2, 9, 10, 13, 14 2 = SDU (for VCC and frame relay path only)

9 = N:1 VC (default for VCC and frame relay paths only)

10 = N:1 VP (default for VPC path only)

12 = 1:1 VC

13 = 1:1 VP (for VPC path only)

14 = PDU (for VCC and frame relay path only)

Cell Concatenation 166 1 to 3 1 = enable (default)

2 = disable

3 = frame aware

This cpType is applicable if cpType 164 is set to 1 and cpType 165 is set to 9, 10, 12, or 13.

Auto Generate PW Id 167 1, 2 1 = no

2 = yes (default)

If this cpType is set to 2, then a unique PW Id is generated across the PSN link and within the endpoint PEs.

PW Id 168 1 to 4294967295

0 = invalid value (default)

This cpType is applicable when cpType 167 is set to 1. You must enter a unique PW Id value.

MTU 169 576 to 9192 default = 4470

Provides the size of the MTU.

This cpType is applicable when cpType 164 is set to 1, and cpType 165 is set to 12 or 2.


(11 of 13)



alternateVPIa 170 0 to 4095 Virtual endpoint A for the alternate source endpoint.

This cpType is applicable when the circuiteProfileName 1:alternateATPId of the commonProfile attribute of the bMGrommedCricuit object is set to a vaule other than NULL.

For VPC paths with alternate endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and cpType 20 of groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to B-ICI/B-ISSI for both endpoints, the valid range is 0 to 4095.

For VPC paths with alternate endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and cpType 20 of groomedCircuitTPProfile attribue of managedGroomedCircuitTP set to UNI for both endpoints, the valid range is 0 to 255.

alternateVPIz 171 0 to 4095 Virtual path endpoint Z for the alternate destination endpoint.

This cpType is applicable when the cricuitProfileName 2:alternateZTPId of the commonProfile attribute of the bMGrommedCircuit object is set to a value other than NULL.

For VPC paths with alternate endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and cpType 20 of groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to B-ICI/B-ISSI for both endpoints, the valid range is 0 to 4095.

For VPC paths with alternate endpoints on a CR port/IMA resource in the OC3/STM1 MS or T1/E1 CR card, and cpType 20 of groomedCircuitTPProfile attribute of managedGroomedCircuitTP set to UNI for both endpoints, the valid range is 0 to 255.

alternateVCIa 172 1 to 65535 Virtual circuit endpoint A for the alternate source endpoint.

This cpType is applicable when the circuitProfileName 1: alternateATPId of the commonProfile attribute is set to a value other than NULL.

alternateVCIz 173 1 to 65535 Virtual circuit endpoint Z for the alternate destination endpoint.

This cpType is applicable when the circuitProfileName 2: alternateZTPId of the commonProfile attribute is set to a value other than NULL.

Policy Constraint (14) 174 0 to 800 0 = No Policy Constraint Index associated with the path (default)

1 to 800 = The Policy Constraint Index associated with the path

Interface Type at Alternate Endpoint A

175 1, 4, 17 1 = VLAN interface

4 = None (default)

17 = Port interface

For a GigE path endpoint, this characteristic must be the same as Interface Type at Endpoint A (cpType 154) of aTMProfile.

Interface Type at Alternate Endpoint Z

176 1, 4, 17 1 = VLAN interface

4 = None (default)

17 = Port interface

For a GigE path endpoint, this characteristic must be the same as Interface Type at Endpoint Z (cpType 155) of aTMProfile.


(12 of 13)



Notes(1) This cpType is always present in the attribute.(2) VPI and VCI values for Frame Relay paths with ATM interworking are provided by cpTypes 12 and 13 of the

frameRelayProfile attribute.(3) When the connection type is set to multipoint and the VC application is set to SPVC, point-to-multipoint SPVC VCC and

SPVC VPC paths are supported on the 7270 MSC, Release 8.0 HLS#2 or later, the 7470 MSP, Release 8.0 HLS#8 or later, the 7670 ESE, Release 4.0 HLS#2 or later, and the 7670 RSP, Release 3.0 HLS#1 or later.

(4) For symmetrical connections, the source and destination endpoints must have the same value for this attribute.(5) For VCC paths with endpoints on 7390 NT OC3/STM-1, or Quad T1/E1 IMA ports, the valid values are 1 to 3.(6) For FRATM symmetrical connections, the source and destination traffic policing may have different values.(7) Defaults to an appropriate value based on a calculation that takes into account compression type, fax/modem rate, Bypass

Coder value, and Clear Channel Packing FactorsCan be increased beyond the default value but cannot be decreased

(8) The Source SIR and Source SIR 0+1 must have the same value for both attributes.(9) The Source PIR and the Source PIR 0+1 must have the same value for both attributes. (10) Valid for rt-VBR or nrt-VBR with traffic descriptor PIR_0+1/SIR 0(11) Valid for rt-VBR or nrt-VBR with traffic descriptor PIR_0+1/SIR_0+1(12) The Initial Information Rate, Rate Increase Factor, and Rate Decrease Factor fields are only configurable when the service

category of the path is set to ABR and VSVD is enabled on the corresponding endpoint port. (13) The special study field is only applicable if there is a Multiservice Traffic Shaping Module (MTSM) installed at the

corresponding endpoint. Once the special study field is enabled for an endpoint, then the MTSM special study statistics can be collected and plotted. There can be only one special study statistic active on a given MTSM.

(14) This cpType is only supported if both link endpoints are on 7270 MSC, 7470 MSP nodes, Release 8.0 or later, or on 7670 ESE, 7670 RSP nodes, Release 4.0 or later.

Table 24-9 describes compression type values for cpType 109—Speech Packing Factor.

Table 24-9 Packing factor cpValues

VLAN Id at Alternate Endpoint A

177 1 to 4094 default = 1

This characteristic is not applicable when:

• the Tag Mode characteristic of the facilityTPProfile (cpType 37) is set to 2 (Tag Unaware)

• the Interface Type at Alternate Endpoint A characteristic (cpType 175) of aTMProfile is set to 17 (Port interface)

VLAN Id at Alternate Endpoint Z

178 1 to 4094 default = 1

This characteristic is not applicable when:

• the Tag Mode characteristic of the facilityTPProfile (cpType 37) is set to 2 (Tag Unaware)

• the Interface Type at Alternate Endpoint Zcharacteristic (cpType 176) of aTMProfile is set to 17 (Port interface)


(13 of 13)

Compression type Packing factor Default cpValue

G.711 Mu-law and A-law Speech 2 1 to 4

1 = 64 kb/s

2 = 128 kb/s

3 = 192 kb/s

4 = 256 kb/s

Bypass 4

(1 of 2)



Setting the PIR on ATM VCC paths with a CE endpoint

When you create ATM VCC paths that terminate on CE endpoints, the path bandwidth is determined by the number of timeslots assigned to each CE endpoint. The number of timeslots is determined by the source circuit map (cpType 45) and destination circuit map (cpType 46) characteristics of aTMProfile. In addition to the number of timeslots, the CE data octets (cpType 43) is also a factor in a formula to determine the correct PIR value for the path. Call creation is successful when the PIR set in aTMProfile matches the internally-calculated PIR value.

Table 24-10 lists the PIR values for each timeslot count and signaling type on T1 and E1 ports, when cpType 43 is set to the default value of 47.

G.723.1 Speech 3 1 to 3

1 = 6.3 kb/s

2 = 12.6 kb/s

3 = 18.9 kb/s

G.723.1 Speech 4 1 to 4

1 = 5.3 kb/s

2 = 10.6 kb/s

3 = 15.9 kb/s

4 = 21.2 kb/s

G.726 Speech 4 1 to 9

1 = 32 kb/s

.

.

9 = 288 kb/s

Bypass

G.729A Speech 3 1 to 8

1 = 8 kb/s

.

.

8 = 64 kb/s

NetCoder Speech 3 1 to 5

1 = 9.6 kb/s

.

.

5 = 48 kb/s

Speech 4 1 to 6

1 = 8 kb/s

.

.

6 = 48 kb/s

Compression type Packing factor Default cpValue

(2 of 2)



Table 24-10 Valid PIR values for each timeslot and signaling type (CAS or BASIC) on T1 and E1 ports

Number of timeslots

T1 E1

CAS (kb/s) Basic (kb/s) CAS (kb/s) Basic (kb/s)

1 76 73 77 73

2 149 146 150 146

3 225 219 228 219

4 298 292 301 292

5 374 365 378 365

6 447 437 451 437

7 523 510 529 510

8 596 583 602 583

9 671 656 679 656

10 744 729 752 729

11 820 802 829 802

12 893 875 902 875

13 969 948 980 948

14 1042 1021 1053 1021

15 1118 1094 1130 1094

16 1191 1167 1203 1167

17 1267 1240 1281 1240

18 1340 1313 1354 1313

19 1416 1386 1431 1386

20 1489 1458 1504 1458

21 1565 1531 1582 1531

22 1638 1604 1654 1604

23 1714 1677 1732 1677

24 1787 1750 1805 1750

25 N/A N/A 1882 1823

26 N/A N/A 1955 1896

27 N/A N/A 2033 1969

28 N/A N/A 2106 2042

29 N/A N/A 2183 2115

30 N/A N/A 2256 2188

31 N/A N/A N/A 2261



24.11 commonProfile attribute

Table 24-11 describes the commonProfile attribute characteristics.



Table 24-11 commonProfile attribute circuitProfileName characteristics

Characteristic Access circuitProfileName SimpleNameType String

Description

alternateATPId Read-write 1:alternateATPId:string Where string is up to 250 characters in the following format:

Nid_1 Sid_2 Cid_3 [,id_4] Did_5 PEid_6[Bid_7], id_8

where

id_1 is the parent node of the managedElement

id_2 is the parent shelf equipmentId

id_3 is the parent card equipmentId

id_4 is the sub-slot number (when applicable)

id_5 is the parent port equipmentId

id_6 is the DS0 number for DS0s, the SRM number for MJUs, and 1 for others

id_7 is used only for MHUs and gives the branch number (optional)

id_8 gives the circuit direction; it is always 2 (outgoing) for DS0s and MJUs, and 1 (incoming) for others

This string uniquely describes the alternate source endpoint.

When the a-TPInstance represents a GigE endpoint, alternateATPId must also represent a GigE endpoint. Both endpoints must have the same value for the Tag Mode characteristic of the facilityTPProfile (cpType 37).

alternateZTPId Read-write 2:alternateZTPId:string Where string is up to 250 characters in the following format:

Nid_1 Sid_2 Cid_3 [,id_4] Did_5 PEid_6[Bid_7], id_8

where

id_1 is the parent node of the managedElement



id_4 is the sub-slot number (when applicable)


id_6 is the DS0 number for DS0s, the SRM number for MJUs, and 1 for others

id_7 is used only for MHUs and gives the branch number (optional)

id_8 gives the circuit direction; it is always 2 (outgoing) for DS0s and MJUs, and 1 (incoming) for others

This string uniquely describes the alternate destination endpoint.

When the z-TPInstance represents a GigE endpoint, alternateZTPId must also represent a GigE endpoint. Both endpoints must have the same value for the Tag Mode characteristic of the facilityTPProfile (cpType 37).

(1 of 3)



customAttributeValue1 Read-write 10001:ca1 string Where string is up to 254 characters, and contains custom information that is associated with the bMGroomedCircuit object.















Description

(2 of 3)



Table 24-12 describes the commonProfile attribute circuitProfile characteristics.

Table 24-12 commonProfile attribute circuitProfile characteristics








Description

(3 of 3)


Reroute [reroute] TRUE or FALSE default = TRUE for SPVC applications; otherwise, default = FALSE

FALSE = do not try to reroute around network failures

TRUE = try to reroute around network failures

This cpType is always present in the attribute.

backupBandwidth (1) [backupBandwidth] TRUE or FALSE TRUE = reserve backup bandwidth

FALSE = do not reserve backup bandwidth (default)

RAPID is not supported.

This cpType is always present in the attribute.

Reroute with facilities matching custom label 4

1 0, 3, 4 Set to 0 for SPVCs


3 = matching is required

4 = matching is not required

Custom labels must be configured on the 5620 NM. Custom label 4 is a customer specified reroute level. See Table 23-2 for details about custom labels 1 through 3.

(1 of 4)



Priority 2 1 to 16 default = 3

1 = highest priority

16 = lowest priority

Optimize 3 1, 2 Set to 1 for SPVCs

1 = do not optimize circuit after reroute (default)

2 = optimize circuit after reroute

Valid for paths riding subrate or Delta ADPCM links only

Transport Bandwidth 4 1 to 8 1 = 8 kb/s

2 = 16 kb/s

3 = 24 kb/s

4 = 32 kb/s

5 = 40 kb/s

6 = 48 kb/s

7 = 56 kb/s

8 = 64 kb/s

May use ATM 5 1, 2 1 = no

2 = yes (default)

Read only and set to 2 for:

• VSC ATM endpoints• voice paths on the 3-DS3 frame

processing card

Use frame relay 6 1, 2 1 = yes (default)

2 = no

Statistics activation status 7 1, 2 1 = disabled

2 = enabled

CAS bandwidth optimization 8 1, 2 1 = enabled (default)

2 = disabled

Available only for VSC endpoints configured for CAS

CAS endpoints are E1 ports configured for CAS or T1 channels with RBS on.

LOC Monitoring 9 1, 2 1 = enabled (default)

2 = disabled


Pulse Dialing 10 1, 2 1 = enabled


Valid only for VSC endpoints configured for CAS

CAS endpoints are E1 ports configured for CAS or T1 channels with RBS on.

ATM G.711 Transport Law for Speech Coder (2)

11 0, 1 0 = Mµ-law (default)

1 = A-law

Sub channel Id 12 4 to 255 default = 4

ATM G.711 Transport Law for Bypass Coder (2)

13 0, 1 0 =Mµ-law (default)

1 = A-law


(2 of 4)



Diverse path 14 trailId The 5620 NM call_id of the path

The trailId attribute of the specified bMGroomedCircuit will act as a diverse path.

ODR 15 0 to 2 0 = disabled (default)

For this cpValue, the 5620 NM determines the route for the link and the Primary route Id and Alternate route Id attributes are disabled.

1 = route(s) only

For this cpValue, the 5620 NM uses the directed routes you have associated with the link. The 5620 NM first tries to connect the link using the Primary route Id then tries with the Alternate route Id. If the connect fails, the link goes to waiting for resources.

2 = route(s) preferred

For this cpValue, the 5620 NM uses the directed routes you have associated with the link. The 5620 NM first tries to connect the link using the Primary route Id then tries with the Alternate route Id. If the connect fails, the 5620 NM determines any other route.

For earlier releases, this attribute was read-only when the path was connected. For release 6.2 or later, this cpType is configurable for connected SPVCs if not set to 0.

Primary route Id 16 1 to 2147483647 —

Alternate route Id 17 1 to 2147483647 —

Node VBN 18 0 to 64 0 = Node VBN disabled (default)

1 to 64 refer to the VBN partition number.

MPLS status 19 0 to 2 0 = No MPLS segment (default)

1 = MPLS up

2 = MPLS down

mEPEnable 20 1 to 2 1 = No (default)

2 = Yes

When the cpType is set to 1, MEP is disabled.

When the cpType is set to 2, MEP is enabled.

alternateAactive 21 0 to 1 0 = Alternate source MEP endpoint is active, and used a source endpoint when a path is connected.

1 = Alternate source MEP is inactive, and not used a a source endpoint when a paoth is connected.

This cpType is applicable when cpType 20 of the commonProfile attribute is set to 2.


(3 of 4)



Notes(1) For VCC, VPC, and frame relay paths riding PSN links, this cpType is set to FALSE.(2) When voice compression is G.711 (no compression), the speech coder configured on the node is determined by ATM G.711

Transport Law. If ATM G.711 Transport Law is set to Mµ-law, the speech coder selected is G.711 Mµ-law. If ATM G.711 Transport Law is set to A-law, the speech coder selected is G.711 A-law.

24.12 circuitType attribute

The circuitType attribute describes the mode and type of circuit. The mode is always equal to 2 (dedicated); Table 24-13 describes the enumerations for the type values.

alternateZactive 22 0 to 1 0 = Alternate destination MEP endpoint is active, and used as a destination endpoint when a path is connected.

1 = Alternate destination MEP enpoint is inactive, and not used as a destination endpoint when a path is connected.

This cpType is applicable when cpType 20 of the commonProfile attribute is set to 2.

Round Trip Delay (RTD) Configuration

25 1 to 3 1 = None (default)

2 = Standard Frequency

3 = High Frequency

This cpType is not applicable when the circuitType attribute is set to 12 (digital voice path) or 13 (digital data path) and when cpType 5 of the commonProfile attribute is set to 2 (Yes).

This cpType is read-only and set to None when:

• cpType 118 of aTMProfile is set to 2 (logical termination point)

• cpType 2 of aTMProfile is set to 3 (multipoint)

• cpType qos of aTMProfile is set to 4 (UBR)

Round Trip Delay (RTD) Status 26 1 to 5 1 = Not configured (default when Round Trip Delay (RTD) Configuration is set to 1 (None)

2 = Enabled (default when Round Trip Delay (RTD) Configuration is set to 2 (standard frequency) or 3 (high frequency)

3 = Failed to launch RTD test

4 = Failed to retrieve RTD value

5 = Successfully completed

Values 3, 4, and 5 are only applicable when Round Trip Delay (RTD) Configuration is set to 2 (standard frequency) or 3 (high frequency).


(4 of 4)



Table 24-13 circuitType attribute type values

Type value description Enumeration

digitalVoice 12

digitalData 13

frameRelay 15

atmVPC 16

atmVCC 17



25.1 Introduction

The busyOutTestObject is created to administer the busy-out test. It is deleted at the end of the test. The busyOutTestObject is contained by the testActionPerformer object; multiple instances of the busyOutTestObject can be contained by the testActionPerformer object.

See the 5620 NM Fault Management guide for more information about the busy out diagnostic.


The busyOutTestObject supports the following CMIP operations:

• get• cancel get• set• action—boRelease and boLink


The busyOutTestObject can generate the following CMIP event notifications:

• attributeValueChange• objectCreation• objectDeletion• stateChange

25.4 Attributes

Table 25-1 describes the attributes of the busyOutTestObject.

Table 25-1 busyOutTestObject attributes


boRecoveryType Indicates how to treat the affected link or path

Read-write 0 = none

1 = connected-down

2 = reroute

3 = disconnect

boTestName Is the test field for naming test

Read-write Any text

boTestType Indicates the type of test being performed

Read 0 = boRelease

1 = boLink

(1 of 2)



mORTs Is the object instance of the managed object where the busy-out test is to occur.

Read distinguishedName of bMFacility

nameBinding Identifies the kind of name binding used by an object

Read Name binding

objectClass Indicates the kind of object Read OID of the busyOutTestObject

operationalState Identifies the operational status of the object

Read 0 = disabled

1 = enabled


packages Identifies the packages used by the object

Read List of implemented packages; see the GDMO for more information

proceduralStatus Indicates the procedural status of the object

Read 1 = not initialized

2 = initializing

3 = reporting

4 = terminating


testInvocationID Provides the distinguishedName of the busyOutTestObject

Read distinguishedName as an attribute

testObjectID Provides a unique identifier Read Naming attribute


(2 of 2)







26.5 elementProfile attribute 26-3

26.6 ntCommissioning attribute 26-5

26.7 pnniProfile attribute 26-5

26.8 pnniSummaryAddressProfile attribute 26-7



26.1 Introduction

An elementExtensions object is used to manage features that are not supported by the standards-based managedElement object, such as 7390 NT commissioning and the PNNI routing protocol for managing ATM switched services addresses.

The elementExtensions object is contained within the managedElement object. See chapter 20 for more information about the managed object hierarchy.


The elementExtensions object supports the following CMIP operations:

• get• cancel get• set


The elementExtensions object can generate the following event notifications:

• attributeValueChange• objectCreation• objectDeletion

26.4 Attributes

Table 26-1 describes the elementExtensions attributes.

Table 26-1 elementExtensions attributes

Attribute Description Access Value Description

elementExtensionsId Naming attribute, Is a unique identifier for an instance of elementExtensions object

Read Always set to 1

elementProfile A multi-valued attribute that provides the node configuration parameters


nameBinding Identifies the type of name binding

Read elementExtensions - managedElement

ntCommissioning Profile A multi-valued attribute that provides the 7390 NT commissioning Information

See Table 26-3 See Table 26-3

This attribute is empty for all nodes, except the 7390 NT.

(1 of 2)



26.5 elementProfile attribute

Table 26-2 lists the characteristics of elementProfile.

Table 26-2 elementProfile attribute characteristics

objectClass Identifies the type of object

Read Always the OID for elementExtensions

packages Identifies the packages used by the elementExtensions object

Read attributeValueChange NotificationPackage, createDeleteNotificationPackage

pnniProfile A multi-valued attribute that provides ATM switched services addressing information for ATM nodes

See Tables 26-4 and 26-5

See Tables 26-4 and 26-5

pnniSummaryAddressProfile A multi-valued attribute that provides PNNI summary address information for ATM nodes

See Table 26-6 See Table 26-6


(2 of 2)

Configuration item Access cpType cpValue Description

customAttributeValue1 Read-write 10001 string Where string is up to 254 characters, and contains custom information that is associated with the managedElement object.






(1 of 2)





customAttributeValue5 Read-write 10005 string Where string up to 254 characters, and contains custom information that is associated with the managedElement object.


customAttributeValue6 Read-write 10006 string Where string up to 254 characters, and contains custom information that is associated with the managedElement object.











(2 of 2)



26.6 ntCommissioning attribute

Table 26-3 lists the characteristics of ntCommissioningProfile.

Table 26-3 ntCommissioningProfile attribute characteristics

26.7 pnniProfile attribute

Tables 26-4 and 26-5 lists the cpTypes of the pnniProfile attribute. Each profile is built using a combination of cpTypes, along with the attributes for that hierarchical level, based on the attributes in Table 26-5.

Table 26-4 cpTypes for pnniProfile attribute


NT Name Read-write 1 string String can be up to 36 characters

e.g.: NT #210

NT Serial Number Read-write 2 string String can be up to 16 characters

e.g.: 555223A232BC

Associated DBS Read 3 integer Integer is the managedElementId of the 7390 DBS

NT Id Read 4 2 to 4001 Unique identifier of NT Commissioning information for a 7390 DBS

Radio Link Read 5 1 to n Radio Link (AMD) the NT is assigned to

n = 4 for Co-Pol 7390 DBS

n = 8 for X-Pol 7390 DBS

Uplink Read 6 1 to 4 Uplink the NT is assigned to

NT Location Read-write 7 string String can be up to 100 characters

e.g., "Ottawa, Ontario"

Terminal Station Link Read-write 8 0 to 9999 ID of Terminal Station (TS)

Default = 0

0 = TS is unknown

IP address Read 9 string IP Address of the NT, which is the same as the IP Address of the 7390 DBS

String can be up to 15 characters long

Link Creation Read 10 0, 1 Wireless Fractional Link Auto-Creation

Default = 0

0 = enabled

1 = disabled

cpType Description

1 to 999 Reserved for future use

1000 to 1999 cpTypes for PNNI hierarchy level 1

(1 of 2)



Table 26-5 describes the pnniProfile attribtues. See Table 26-4 for the associated cpTypes.

1000 PNNI Node Level

1001 Peer Group ID

1002 PGL Priority

1003 Node Administrative Weight

1004 PGL Status

1005 PNNI Node ID

1006 Node ATM Address

1007 PNNI Restricted Transit



2001 Peer Group ID

2002 PGL Priority


2004 PGL Status

2005 PNNI Node ID





3001 Peer Group ID

3002 PGL Priority


3004 PGL Status

3005 PNNI Node ID



3008 LGN in use

cpType Description

(2 of 2)



Table 26-5 pnniProfile attribute characteristics

26.8 pnniSummaryAddressProfile attribute

Table 26-6 lists the cpTypes of the pnniSummaryAddressProfile attribute. The attribute holds an array of summary addresses for ATM nodes. Each node can have up to X entries, where X is the maximum number of PNNI summary addresses that are supported by each node

Table 26-6 describes the pnniSummaryAddressProfile attributes.

Configuration item Configuration parameter

cpType cpValue Description

PNNI Node Level Read Table 26-4 1 to 104 Represents the level of a logical node in the hierarchy. The lower the number, the higher the node in the PNNI hierarchy. The default is 96 for the lower level node.

Peer Group ID Read Table 26-4 string Indicates the 31-character string Peer Group ID that the LGN is part of.

The string is in alphanumeric format, such as 18-12-1234-12345678901234567890

PGL Priority Read Table 26-4 0 to 255 Indicates the node peer group leadership priority, used by nodes in a peer group to determine which node in the peer group is PGL A. A cpValue of 0 means the node never becomes peer group leader.

Node Administrative Weight Read Table 26-4 0 to 16775215

Indicates the node radius administrative weight of the LGN and is used to alter the cost of traversing the node. The default is 5040.

PGL Status Read Table 26-4 0, 1 0 indicates the node is not acting as peer group leader for this PNNI Node Level.

1 indicates this node is acting as peer group leader for this PNNI Node Level.

PNNI Node ID Read Table 26-4 String Indicates the PNNI Node ID, used to differentiate nodes uniquely in a PNNI network.

The string is 57 characters long, such as 18-a0-12-1234-123456-789012345678-02:40:80:21:83:f5:00:00

Node ATM Address Read Table 26-4 String Indicates the node ATM address. The string is 49 characters long, such as 12-1234-12345678901234567802-40:80:21:83:f5:00-00

PNNI Restricted-Transit Read

Write

Table 26-4 0, 1 0 indicates that restricted transit is disabled for the node.

1 indicates that restricted transit is enabled for the node. 0 is the default.

LGN in use Read

Write

Table 26-4 String Indicates the name of the LGN with which this node is associated at PNNI hierarchy levels 2 and 3, where string is 32 charachters long. Default = none



Table 26-6 pnniSummaryAddressProfile attribute characteristics



PNNI Hierarchy Level (1) Read-Only 1 1 to 3 Represents the PNNI hiearchy level to which the summary address belongs:

1 = PNNI hierarchy level 1



Summary Address Number Read-Only 2 1 to 1000 The ID number of the PNNI summary address

System Prefix Read-Only 3 string value For PNNI hierarchy 1 nodes, where string is up to 26 characters long

Address Read-Only 4 string value The digits making up the address, where string is up to 19 bytes long

Address Summary Type Read-Only 5 0 (default), 1 0 = an internal address

1 = an external address

Advertisement Policy Type Read-Only 6 1 to 4 (default) 1 = summarizing

2 = suppressing

3 = exception

4 = default summary

Aggregate Read-Only 7 0, 1 Determines if Advertisement Policy Type and Address Summary Type are in aggregate mode. This only applies to summary address configured on LGNs.

0 = no

1 = yes

Administrative Weight Read-Only 8 0 to 16777215 or string

Determines bias when selecting paths in the network to multi-homed summary addresses. This indicates the cost to reach subscribers.

Default = Aggregate for LGNs; 0 for lowest level

(1 of 2)



Note(1) Only level 1 summary addresses are referenced in the node. Summary addresses belonging to levels 2 and 3 are referenced

using the LGN with which the node is associated.

Scope Read-Only 9 0 to 104 or string

Determines address reachability policy at higher levels in the hierarchy. Address with scope string or X can be advertised up the hierarchy to level X

Default = Aggregate for LGNs; 0 for lowest level

Status Read-Only 10 1 to 12 Status of the summary address on the node or the LGN:

1 = deleted

2 = unknown

3 = advertising

4 = idle

5 = summarizing

6 = suppressing

7 = excepting

8 = propagated

9 = PGL for SVCC

10 = always advertising

11 = always idle

12 = ILMI_Reg



(2 of 2)







27.5 Programmed versus installed card type 27-3



27.1 Introduction

An equipmentHolder object models a shelf, card slot, power supply slot, or shelf module slot.

The equipmentHolder object is contained by a managedElement object or by another equipmentHolder object.

See Appendix A for a list of the available card types.


The equipmentHolder object supports the following CMIP operations:

• get• cancel get


The equipmentHolder object can generate the following event notifications:

• objectCreation• objectDeletion• attributeValueChange

27.4 Attributes

Table 27-1 describes the equipmentHolder attributes.

Table 27-1 equipmentHolder attributes


acceptableCircuitPackTypeList Is the programmed card type

Read String describing the programmed card type

See Table 27-3

equipmentHolderAddress Is the physical location of the resource

Read Always null

equipmentHolderType Is the type of equipment holder

Read Either shelf X, slot, or shelf module, where X is the installed shelf type

equipmentId Naming attribute; unique identifier for an instance of an equipmentHolder object

Read Integer or a string (1)

holderStatus Is the installed card type Read String describing the installed card type

See Table 27-3

(1 of 2)



Note(1) For a shelf: integer-5620 NM shelf id; for a slot: string: -Card Slot: #, or Power Supply Slot: #; for Shelf Module Slot: Z (Z is

the corresponding module type; see Table 27-2 for more information)

Table 27-2 identifies the 7670 RSP ESE shelf module equipment that is supported by the 5620 CMIP. Each module type is modeled by one equipmentHolder object and one managedPack object.

Table 27-2 Shelf module equipment for 7670 RSP ESE

Note(1) See equipmentId attribute in Table 27-1 for more information

27.5 Programmed versus installed card type

Table 27-3 compares programmed versus installed card type modeling. The left side of the table describes the 5620 NM state and indicates whether the card is programmed or installed. The right side of the table describes the 5620 CMIP objects and attributes that correspond to each state.

nameBinding Identifies the kind of name binding used by an equipmentHolder object

Read Name binding

objectClass Is the kind of object Read Always the OID for equipmentHolder

packages Identifies the packages used by the equipmentHolder object


replaceable Indicates replaceability of equipmentHolder object instance

Read Always no

serialNumber Represents the serial number of the object

Read A string up to 16 characters

subordinateCircuitPack SoftwareLoad

Not used at this time Read Always empty

supportedByObjectList Not used at this time Read Always empty


(2 of 2)

Module type (Z) (1)

Shelf module equipment

1 Alarm card

2 ECCI card

3 Cooling unit

4 Power module B

5 Power module B



The holderStatus attribute of the equipmentHolder object describes the installed card type. This attribute indicates whether the card installed in the slot is on the list of acceptable cards and provides the card string of the installed card.

The circuitPackType attribute of the managedPack object and the acceptableCircuitPackTypeList attribute of the equipmentHolder object describe the programmed card type.

Table 27-3 Programmed versus installed card type modeing

Notes(1) This string describes the installed card. See Table App A-1 for a list of card types.(2) This string describes the programmed card type. See Table App A-1 for a list of card types.

Note 1 — The installed and programmed card types must match for the card to be operational. See Table App A-1 for a list of card types.

Note 2 — For 5620 NM and 5620 SNMP DM managed nodes, the holderStatus and acceptableCircuitPackTypeList attributes will be populated with the card string if an actual card is installed and configured. If a card is just programmed then only the acceptableCircuitPackList attribute gets populated.

5620 NM state 5620 CMIP

equipmentHolder managedPack

Programmed Installed Match (GUI status)

holderStatus

acceptableCircuitPackTypeList

circuitPackType

operationalState

N N NA (red) This state cannot occur in the 5620 CMIP.

This state cannot occur in the 5620 CMIP.

N Y NA (red) This state cannot occur in the 5620 CMIP.


Y N NA (red) notInThe AcceptedList card string (1)

for example Null Card

card string (2)

for example STM1

card string (2)

for example STM1

disabled

Y Y N (red) notInThe AcceptedList card string (1)

for example LGS

card string (2)

for example OC3

card string (2)

for example OC3

disabled

Y Y Y (green) inThe AcceptedList card string (1)

for example EandM

card string (2)

for example EandM

card string (2)

for example EandM

enabled



28.1 Introduction

The eventForwardingDiscriminator object sends selected event reports to a specified destination. The event reports that are sent are CMIP EventReportArguments.

Objects generate event notifications in response to changes in the objects or to alarms received from the OSS Interface Agent. The notifications are selected by the discriminatorConstruct attribute of the eventForwardingDiscriminator object and are sent to the destination(s) specified in the destination attribute.

The system object contains the eventForwardingDiscriminator object.


The eventForwardingDiscriminator object supports the following CMIP operations:

• create• delete• get• cancel get• set


The eventForwardingDiscriminator object can generate the following event notifications:


28.4 Attributes

Table 28-1 describes the eventForwardingDiscriminator object attributes.



Table 28-1 eventForwardingDiscriminator object attributes


administrativeState Reflects the availability of an eventForwardingDiscriminator object

Read-write default = 1

0 = locked

1 = unlocked

destination Tells the eventForwardingDiscriminator where to send the notification if it satisfies the discriminatorConstruct criteria

Read-write default = address of originating OSS

Address is an OID representing the AP-title of the destination OSS; the OID must be specified using AE-title-form2.

discriminatorConstruct Selects the event notifications to be sent to the destination address

Read-write default = forward all events

Value of filter as described in Annex 2 of CMIP IS 9596 and, if required, the value of the event notification

discriminatorID Is a unique identifier for an instance of the eventForwardingDiscriminator object class

Read String or integer

When the creation method is managedObjectInstance, the OSS supplies the integer or string identifier

When the creation method is superiorObjectInstance, the integer is automatically assigned by the 5620 CMIP OSS Interface Gateway

nameBinding Identifies the kind of name binding used by the eventForwardingDiscriminator object

Read Name binding

objectClass Is the kind of object Read Always the OID for eventForwardingDiscriminator

operationalState Is the status of the object in the network Read Always enabled

0 = disabled

1 = enabled

packages Identifies the packages used by the eventForwardingDiscriminator object





29.2 Supported CMIP actions 29-4



29.5 listLinks action 29-6

29.6 listPaths action 29-12

29.7 hitlessConnectionMove action 29-18

29.8 retrieveActiveAlarms action 29-21

29.9 configureRealTimeStatistics action 29-21

29.10 collectRealTimeStatistics action 29-22

29.11 cancelRealTimeStatistics action 29-23

29.12 determineSupportedStatistics action 29-23

29.13 addChannelsToMux action 29-24

29.14 removeChannelsFromMux action 29-26

29.15 listChannelsUsedByMux action 29-26



29.16 listCustomAttributeNames action 29-26

29.17 retrieveISLInfo action 29-27



29.1 Introduction

The genericActionObject administers the CMIP operations listed in section 29.2.



29.2 Supported CMIP actions

The genericActionObject supports the following CMIP operations:

• get• get-replace• action—addChannelsToMux

Use the addChannelsToMux action to add channels to the endpoints of the bMGroomedCircuit when the mORTs attribute is a bMGroomedCircuit, and the endpoint to which channels are to be added is a multiplexer on the OC3/STM1 VoP or 16-port T1/E1 cards.

• action—cancelRealTimeStatisticsUse the configureRealTimeStatistics action to cancel real time collection of statistics

• action—collectRealTimeStatisticsUse the collectRealTimeStatistics action to begin real time collection of statistics

• action—configureRealTimeStatisticsUse the configureRealTimeStatistics action to configure real time collection of statistics

• action—determineSupportedStatisticsUse the determineSupportedStatistics action to specify the supported statistics identifier for an object

• action—hitlessConnectionMoveUse the hitlessConnectionMove action to move a path or a segment of a path to another path while eliminating the loss of data across the path.

• action—listChannelsUsedByMuxUse the listChannelsUsedByMux action to list the channels from the endpoints of the bMGroomedCircuit when the mORTs attribute is a bMGroomedCircuit objectInstance, and the endpoint for the channels is a multiplexer on the OC3/STM1 VoP or 16/32 port T1/E1 VoP card.

• action—listCustomAttributeNamesUse the listCustomAttributeNames action to list the custom attribute names and their associated characteristics identifier and the managedObject class on which it is supported.

• action—listPathsUse the listPaths action to get a list of distinguishedNames of paths from the 5620 NM that meet certain filtering criteria, including SPVC paths.

• action—removeChannelsFromMuxUse the addChannelsToMux action to remove channels from the endpoints of the bMGroomedCircuit when the mORTs attribute is a bMGroomedCircuit, and the endpoint to which channels are to be added is a multiplexer on the OC3/STM1 VoP or 16-port T1/E1 cards.

• action—retrieveActiveAlarmsUse the retrieveActiveAlarms action to retrieve all the active alarms in the aggregator database for all network objects.

• action—retrieveISLInfoUse the retrieveISLInfo action to list the inter-shelf link information in the



shelves of the 7470 MSP, 7670 ESE, 7350 ASAM, and the 7270 MSC nodes.


The genericActionObject can generate the following CMIP event notifications:


Result messages for a hitlessConnectionMove are available, as described in “hitlessConnectionMove result messages for cpType 8” in section 29.7.

29.4 Attributes

Table 29-1 describes the attributes of the genericActionObject.

Table 29-1 genericActionObject attributes


actionName Text string indicating the action name.

Read-write Name of the action

actionProfile Profile attribute that contains configuration parameters

Read reserved

actionType Indicates the type of genericActionObject to be performed

Read default = 0

0 = none

mORTs Indicates the object instance of the managed object where the genericActionObject is to occur

Read-write default = none

bMGroomedCircuit object instance for the hitlessConnectionMove action

The target object instances for the listPaths action are:

• network (partition level only)• managedElement• equipmentHolder• managedPack• managedFacilityTP• managedGroomedCircuitTP• bMFacility• managedEquipment

The target object instances for the listLinks action are:

• network (partition level only)• managedElement• managedPack• managedFacilityTP (physical)• managedFacilityTP (logical)

(1 of 2)



29.5 listLinks action

The 5620 CMIP supports an action on the GAO object to list links. Use the listLinks action to create a filter and return a list of distinguishedNames. Actions must include an ActionInfo argument. This consists of two parts:

• actionType, which is the OID of the action• actionInfoArg, which is of a ManagedProfile type called ListLinksInfo, and is

used to set the filter criteria for the listLinks action

The listLinks action returns the distinguishedName of all links that terminate on the specified managedObject with which the genericActionObject is associated, and also match the filter defined by the actionInfoArg. Use Table 29-2 to create the arguments that create the filter.

If actionInfoArg options are not specified, the value of the options is assumed to be the default value identified, and the distinguishedNames of the links which meet those options, and which terminate on the chosen managed object with which the genericActionObject is associated, are returned. Table 29-2 describes the actionInfoArg options for the listLinks option.

nameBinding Identifies the type of name binding used by an object

Read testActionPerformer-genericActionObject

objectClass Indicates the kind of object Read genericActionObject


Read default = 1

0 = disabled

1 = enabled

See Table 29-3

Packages Identifies the packages used by the object.

AttributeValueChange

NotificationPackage, createDeleteNotificationPackage, stateChangeNotificationPackage


proceduralStatus Indicates the procedural status of the genericActionObject

Read default = not initialized

1 = not initialized

2 = initializing

3 = reporting

4 = terminating

See Table 48-2 details

testInvocationId Provides the distinguishedName of the genericActionObject


testObjectID Provides a unique identifier for an instance of a genericActionObject

Read 1 to n

Naming attribute


(2 of 2)



Table 29-2 listLinks actionInfoArg options


User Label 1 Valid string of 0 to 34 characters

If specified, is used to match any sub-string of the name of the link. Default is an empty string, which matches all values.

Link Type 2 1, 2, 3, 6, 7, 10 1 = Full link (default)

2 = Fractional link

3 = Full or fractional link

4 = Subrate link

6 = Frame Relay link

7 = ATM VPC link

10 = ATM VCC link

(1 of 6)



Type 3 1 to 12, 14, 16 to 22, 24 to 28, 39, 45, 46, 49 to 55, 57 to 74, 76 to 79, 83, 85, 86, 999

Specifies the cable or call type.

999 = Any (default)

1 = Data

2 = Voice

3 = T1

4 = E1

5 = Ethernet

6 = SC

7 = X.21 Aggregate

8 = V.35 Aggregate

9 = Custom

10 = Custom RS232

11 = X.21 Primary

12 = V.35 Primary

14 = Mixed end points

16 = DS3

17 = Drop

18 = LAN Segment

19 = FASTBus

20 = E3

21 = G703

22 = STM1

24 = LATM (140 mb/s)

25 = T3ATM

26 = OC3

27 = LATM (100 mb/s)

28 = E3ATM

39 = STS1

45 = E1ATM

46 = T1 ATM

49 = PVC

50 = SVC

51 = Audio

52 = NTSC Video

53 = PAL Video

54 = SMDS

55 = T3 CE

57 = SONET/SDH Cables

58 = ISDN Access

59 = ISDN


(2 of 6)



60 = OC12

61 = STM4

62 = MPEG

63 = IMA

64 = RS-530 Primary

65 = RS-449 Primary

66 = TT2CM

67 = SVCs and SPVCs

68 = DDS Aggregate

69 = DS3 UFR

70 = E3 UFR

71 = HSSI FR

72 = SVCs/SPVCs (out-of-band signaling)

73 = DCS SONET/SDH Cables

74 = MPLS

76 = ADSL

77 = SDSL

78 = OC48

79 = STM16

85 = MFR link

86 = PSN link

When the Link Type characteristic of listLinksInfo is 1 (Full link) or 3 (Full or fractional link), the cpValues that are valid for the Type characteristic are 999, 1 to 12, 14, 16 to 22, 24 to 28, 39, 45, 46, 51 to 55, 57 to 66, 68 to 71, 73, 76 to 79, 85, and 86.

When the Link Type characteristic of listLinksInfo is 2 (Fractional link), the cpValues that are valid for the Type characteristic are 999, 1 to 4, 7 to 9, 11, 12, 14, 21, 22, 24 to 28, 45, 46, 57, 60, 61, 61, 63 to 65, 78, 79, 85, and 86.

When the Link Type characteristic of listLinksInfo is 4 (Subrate link), the cpValues that are valid for the Type characteristic are 999, 13, 23, 29, 30, 31, 32, 35, 36, 37, 38, and 44.

When the Link Type characteristic of listLinksInfo is 6 (Frame Relay link), the cpValues that are valid for the Type characteristic are 999, 49, and 50.

When the Link Type characteristic of listLinksInfo is 7 (ATM VPC link), the cpValues that are valid for the Type characteristic are 999, 49, 67, 72, ad 74.

When the Link Type characteristic of listLinksInfo is 10 (ATM VCC link), the cpValues that are valid for the Type characteristic are 999 and 49.


(3 of 6)



Status 4 1 to 33, 999 Specifies the status of bMFacility.

999 = Any (default)

1 = Ready for Connect

2 = Up

3 = Connected

4 = Connected (RAPID)

5 = Connected (down)

6 = Waiting for resources

7 = Waiting for repairs

8 = Interrupted via NMTI

9 = Connect requested

10 = Disconnect requested

11 = Connected (Protocol OOS)

12 = Connected (RAPID down)

13 = Connected (Protocol P.OOS)

15 = Under Maintenance

16 = NMTI or Under Maint

17 = Down

18 = Busied out

19 = Down and Under Maintenance

20 = Connected (ISDN Pending)

21 = Connected (ISDN Failed)

22 = Connected (RAPID ISDN Pending)

23 = Connected (RAPID ISDN Failed)

24 = Unknown status

25 = Logically busied out

26 = Broken

27 = Link is active on the FASTBus

28 = Link is standby on the FASTBus

29 = FASTBus cable is disabled

30 = FASTBus cable is becoming active

31 = Partially protected

32 = IMA/MFR link bandwidth reduced

33 = Debounce

When the Link Type characteristic of listLinksInfo is 1 (Full link), 2 (Fractional link), or 3 (Full or fractional link), the cpValues that are valid for the Status characteristic are: 999, 2, 17, 18, and 24 to 33.

When the Link Type characteristic of listLinksInfo is 4 (Subrate link), the cpValues that are valid for the Status characteristic are 999, 1, 3 to 10, 12, 14 to 16, and 20 to 23.

When the Link Type characteristic of listLinksInfo is 6 (Frame Relay link), the cpValues that are valid for the Status characteristic are: 999, 1, 3 to 13, 15, 16, and 19 to 23.

When the Link Type characteristic of listLinksInfo is 7 (ATM VPC link) or 10 (ATM VCC link), the cpValues that are valid for the Status characteristic are: 999, 1, 3, and 5 to 10.


(4 of 6)



Cost From 5 0 to 100 Default = 0

This cpType is applicable when the Link Type characteristic of listLinksInfo is set to 1 (Full link), 2 (Fractional link), or 3 (Full or fractional link).

The value of this cpType must be less than or equal to the value of the Cost To cpType. The values of Cost From and Cost To are exchanged if the Cost From value is greater than the Cost To value.

Cost To 6 0 to 100 Default = 0

This cpType is applicable when the Link Type characteristic of listLinksInfo is set to 1 (Full link), 2 (Fractional link), or 3 (Full or fractional link).

The value of this cpType must be greater than or equal to the value of the Cost From cpType. The values of Cost From and Cost To are exchanged if Cost From value is greater than the Cost To value.

Path Attribute 7 1, 2 1 = Can carry paths/links (default)

2 = Are carrying paths/links

This cpType is applicable if the Link Type characteristic of listLinksInfo is set to 4 (Subrate link), 6 (Frame Relay link), 7 (ATM VPC link), or 10 (ATM VCC link)

Path Priority 8 1 to 16, 999 Default = 999

This cpType is applicable when the LinkType characteristic of listLinksInfo set to 4 (Subrate link), 6 (Frame Relay link), 7 (ATM VPC link), or 10 (ATM VCC link).

Optimize 9 2, 999 999 = Any (default)

2 = Rerouted since connected/optimized

This cpType is applicable when:

• The Link Type characteristic of listLinksInfo is set to 4 (Subrate link), 6 (Frame Relay link), 7 (ATM VPC link), or 10 (ATM VCC link).

• The Status characteristic of listLinksInfo is set to 3 (Connected), 4 (Connected (RAPID)), 5 (Connected (down)), 11 (Connected (Protocol OOS)), 12 (Connected (RAPID down)), 13 (Connected (Protocol P.OOS)), 20 (Connected (ISDN Pending)), 21 (Connected (ISDN Failed)), 22 (Connected (RAPID ISDN Pending)), or 23 (Connected (RAPID ISDN Failed).

Empty Link Priority 10 1 to 16, 255, 999 999 = Any (default)

1 = Highest Priority

16 = Lowest Priority

255 = Minimum Priority

This cpType is applicable if the Link Type characteristic of listLinkInfo is set to 4 (Subrate link), 6 (Frame Relay link), 7 (ATM VPC link), or 10 (ATM VCC link).


(5 of 6)



29.6 listPaths action

Use the listPaths action to create a filter and return a list of path distinguishedNames. Actions must include an ActionInfo argument. This consists of two parts:

• actionType, the OID of the action (1.2.124.113537.1.3.19 for listPaths)• actionInfoArg (path data options that are listed for listPaths)

The listPaths action returns the distinguishedName of all paths which terminate on the chosen managedObject that the genericActionObject is associated with. Use Table 29-3 to create the arguments that create the filter. If no actionInfoArgs are chosen from Table 29-3, the distinguishedNames of all paths which terminate on the chosen managed object that the genericActionObject is associated with are returned.

Table 29-3 describes the actionInfoArg options for the listPaths action. All the cpTypes have read-write access.

Table 29-3 listPaths actionInfoArg options

OAM CC Status 13 0, 2, 3, 11, 999 Specifies the OAM-CC Status filtering criteria.

999 = Any (default)

0 = Not Configured

2 = Applied

3 = Failed

11 = Applied NMTI

This cpType is applicable when the Link Type characteristic of listLinksInfo is set to 4 (Subrate link), 6 (Frame Relay link) or 7 (ATM VPC link).

OAM PM Status 14 0, 2, 3, 11 Specifies the OAM-PM Status filtering criteria.

0 = Not Configured

2 = Applied

3 = Failed

11 = Applied NMTI

This cpType is applicable when the Link Type characteristic of listLinksInfo is set to 4 (Subrate link), 6 (Frame Relay link) or 7 (ATM VPC link).


(6 of 6)


userLabel 1 Valid string of 1 to 33

The name of the path to be listed, in text string format

Priority 2 0 to 16 default = 0 (any priority)

Indicates the priority value of the paths to be listed, where 1 is the highest priority and 16 is the lowest priority.

(1 of 5)



circuitType 3 0, 1, 2, 6, 8, 9

Indicates the type of paths to be listed.

0 = any (default)

1 = circuit-switched voice

2 = circuit-switched data

6 = frame relay

8 = VPC

9 = VCC

SubType 4 0, 1, 2, 3, 4, 6, 10

Indicates the subtype of the paths to be listed. This cpType can be used when cpType 3 is not set to 0.

0 = any (default)

1 = PVC

2 = SPVC

3 = signaling

4 = PNNI

6 = ILMI

10 = may use SPVC

When cpType 3 is set to 0, the options are 1 (PVC), 2 (SPVC), 3 (Signaling), 4 (PNNI), 6 (ILMI), or 10 (May Use SPVC)

When cpType 3 is set to 1, the options are 1 (PVC), 2 (SPVC), or 10 (May Use SPVC)


When cpType 3 is set to 6, the options are 1 (PVC), 2 (SPVC), 3 (Signaling), or 10 (May Use SPVC)


When cpType 3 is set to 9, the options are 1 (PVC), 2 (SPVC), 3 (Signaling), 4 (PNNI), 6 (ILMI), or 10 (May Use SPVC)


(2 of 5)



Status 5 0 to 24 The status of the paths to be listed.

default = 0

0 = any status

1 = Ready for Connect

3 = Connected


5 = Connected (Down)

6 = Waiting for Resources

7 = Waiting for Repairs

8 = Interrupted via NMTI

9 = Connect Requested

10 = Disconnect Requested

11 = Connected (ILMI Down)

12 = Connected (RAPID Down)

13 = Connected (RAPID ILMI Down)

14 = Reroute Requested


16 = NMTI or Under Maint

18 = Connected (MEP)






24 = Connected (Resized)

listNCCI 6 0 to 7 Indicates the options for listing NCCI information for SPVC paths.

0 = no NCCI list, and no bMGroomedCircuit IDs are listed

1 = local NCCIs only, and no bMGroomedCircuit IDs are listed

2 = foreign NCCIs only, and no bMGroomedCircuit IDs are listed

3 = all NCCIs, and no bMGroomedCircuit IDs are listed

4 = list only bMGroomedCircuit IDs (default)

5 = bMGroomedCircuit IDs contain distnguishedNames, and local NCCIs

6 = bMGroomedCircuit IDs contain distinguishedNames, and foreign NCCIs

7 = bMGroomedCircuit IDs contain distinguishedNames, and all NCCIs

If a 1000-series cpType is not specified, and cpType 6 is 0, the listPaths action result is empty.

Riding Criteria 7 1 to 3 Indicates the riding criteria for SPVCs when the tested object is managedElement.

default = 1

1 = Source Only

2 = Destination Only

3 = Tandem


(3 of 5)



GCAC Bandwidth 8 0 to 2 Indicates the GCAC bandwidth filtering criteria.

default = 0

0 = no filtering is performed on GCAC bandwidth

1 = the OSS is expected to input the bandwidth at or above which which the output list will be constrained.

2 = the OSS is expected to input the bandwidth at or below which the output list will be constrained.

GCAC Bandwidth value 9 1 to 2147483674

Indicates the line rate, in kb/s. This cpType can be used when cpType 8 is not set to 0.

default = 1

Reroute Type 10 2 Indicates the type of reroute to be listed. This cpType can be used when cpType 5 is set to 3.

2 = rerouted since connected or optimized

When this cpType is not specified, the type of reroute is any route.

OAM-CC Status 11 0, 2, 3, 11, 999

default = 999

0 = not configured

2 = applied

3 = failed

11 = applied via NMTI

999 = any

OAM-PM Status 12 0, 2, 3, 11, 999

default = 999

0 = not configured

2 = applied

3 = failed

11 = applied via NMTI

999 = any

Connection Type 13 0 to 2 Indicates the connection type filtering criteria.

default = 0

0 = any connection type

1 = point to point

2 = point to multipoint

MPLS Status 14 0 to 2 default = 0

0 = no MPLS segment

1 = MPLS up

2 = MPLS down

Indicates the MPLS status of the paths to be listed.

Policy Constraint 15 0 to 3 default = 0

0 = all

1 = all paths that support policy based routing but do not have policy constraints

2 = all paths that support polict based routing and have policy constraints

This cpType is only supported if both link endpoints are on 7270 MSC, 7470 MSP nodes, Release 8.0 or later, or on 7670 ESE, 7670 RSP nodes, Release 4.0 or later.


(4 of 5)



Policy Constraint Index 16 1 to 800 A valid policy constraint index between 1 and 800.

This cpType is only applicable when cpType 15 is set to 2.

This cpType is only supported if both link endpoints are on 7270 MSC, 7470 MSP nodes, Release 8.0 or later, or on 7670 ESE, 7670 RSP nodes, Release 4.0 or later.

Automatic RTD 17 0 to 3 0 = Any (default)

1 = None

2 = Standard Frequency

3 = High Frequency

This cpType is applicable when:

• cpType 3 (circuitType) of the actionInfoArg attribute of listPaths action is set to 0 (any), 6 (frame relay), 8 (VPC) or 9 (VCC)

• cpType4 (subType) of actionInfoArg attribute of listPaths action is set to 0 (any), 1 (PVC), 2 (SPVC), or 10 (may use SPVC)

pathDataTrailId Present 1000 0, 1 0 = Excludes the trailId in the pathDataList result of the listPaths action (default)

1 = Includes the trailId in the pathDataList result of the listPaths action

If a 1000-series cpTypeis not specified, and cpType 6 is 0, the listPaths action result is empty.

pathDataPathName Present 1001 0, 1 0 = Excludes the userLabel in the pathDataList result of the listPaths action (default)

1 = Includes the userLabel in the pathDataList result of the listPaths action


pathDataPathStatus Present 1002 0, 1 0 = Excludes the Status in the pathDataList result of the listPaths action (default)

1 = Includes the Status in the pathDataList result of the listPaths action


pathDataLocalNCCI Present 1003 0, 1 0 = Excludes the local NCCI in the pathDataList result of the listPaths action (default)

1 = Includes the local NCCI in the pathDataList result of the listPaths action


pathDataForeignNCCI Present 1004 0, 1 0 = Excludes the foreign NCCI in the pathDataList result of the listPaths action (default)

1 = Includes the foreign NCCI in the pathDataList result of the listPaths action



(5 of 5)



listPaths action resultsThe result of the listPaths action is a list with the following fields:

• bMGroomedCircuitIdList• NCCIList• pathDataList (optional)

The bMGroomedCircuitIdList is a set of distinguishedName of the paths controlled by the listNCCI (cpType 6) of actionInfoArg of listPaths action.

The NCCIList is a set of GraphicString of the paths controlled by listNCCI (cpType 6) of actionInfoArg of listPaths action.

The pathDataList is a set of managedProfile controlled by the 1000-series of cpTypes. If a 1000-series cpType of listPaths actionInfoArg is not specified, the pathDataList field of the listPaths action result is not created.

Table 29-4 describes the pathDataList options.

Table 29-4 pathDataList options

Characteristic cpType cpValue Descripton

trailId 1 integer 5620 NM call_id of the path

A unique integer assigned by the 5620 NM

localNCCI 2 string A unique string that is a combiation of the NCCI root and index, which uniquely identify a path

foreignNCCI 3 string A string that is a combination of NCCI root and index, which uniquely identify a path

(1 of 2)



29.7 hitlessConnectionMove action

Actions must include an ActionInfo argument. This consists of two parts:

• actionType, the OID of the action (1.2.124.113537.1.3.20 for hitlessConnectionMoves)

• actionInfoArg (hitless connection move options that are listed for hitlessConnectionMoves)

The hitlessConnectionMove action returns the information as described in Table 29-5. Events and alarms are reported as the action progresses and completes.

userLabel 4 string The name of the path to be listed, in text string format

status 5 1 to 24 1 = Ready for Connect

2 = Waiting for Setup Time

3 = Connected


5 = Connected (Down)

6 = Waiting for Resources

7 = Waiting for Repairs

8 = Interruped via NMTI

9 = Connect Requested

10 = Disconnect Requested

11 = Connected (ILMI Down)

12 = Connected (RAPID Down)

13 = Connected (RAPID ILMI Down)

14 = Reroute Requested


16 = NMTI or Under Maintenance

17 = NMTI and Under Maintenance

18 = Connected (MEP)






24 = Connected (Resized)

Characteristic cpType cpValue Descripton

(2 of 2)



Table 29-5 hitlessConnectionMove action information

Table 29-6 describes the actionInfoArg options for the hitlessConnectionMove action. All the cpTypes have read-write access.

Table 29-6 hitlessConnectionMove actionInfoArg options

Result Description

hcmResult Represents whether the action is a Success or Failure

hcmResultDescription Optionally contains the descriptive details about the result of the action for the selected bMGroomedCircuit. See Table 29-6 for more information.

The presence of this information is controlled by the CollectResult actionInfoArg option.

hcmResponseData Optionally contains actual HCM result data. The presence of this information is controlled by the PathTrace actionInfoArg option, if the CollectResult actionInfoArg option is set to 2.


Request Name 1 Valid string of 1 to 52

Indicates the name of the request.

Default = {}

OperationType 2 1, 2 Indicates the type of hitless connection move.

1 = OptimizeMove

2 = MaintenanceMove

Default = 1

MinPnniPathCostImprovement 3 1 to 4294967295

Valid when cpType 2 = 1

Indicates the accumulative cost decrease that rerouting connections must demonstrate over the current path to be considered an improvement. The SPVC path is switched over when the current cost minus the new path cost is less than or equal to this cpType value.

Default = 1

Allow Break Before Make 4 1, 2 Indicates what happens to the SPVC is the optimization is unsuccessful.

1 = No, when cpType 5 is set to 3 and the cpType 6 value range is 1 to 4294987295

2 = Yes, when cpType 5 is set to 4

Default = 1

MaxPnniPathCostDelta 5 4, 3 Indicates that there are constraints to the accumulative cost increase of rerouting paths compared to the current path.

default = 4

4 = UnLimited

3 = Limited

PnniPathCostDeltaValue 6 1 to 4294967295

Indicates the cost degradation of allowing a rerouting path to be considered as a replacement route for the current path. Valid when cpType 5 is set to 3.

default = 1

(1 of 2)



hitlessConnectionMove result messages for cpType 8When the cpType 8 option is set to 2, detailed messages about the status of the action are returned in the hcmResultDescription field of the actionReplyInfo.

When you set cpType 8 for hitlessConnectionMove to 1, success and failure code result messages about the status of the action are displayed using actionReplyInfo. Table 29-7 describes the messages.

Table 29-7 hitlessConnectionMove messages

PathTrace 7 1, 2 Indicates whether a path trace should be performed as part of the hitless connection move.

default = 2

1 = enable path trace

2 = disable path trace

CollectResults 8 1, 2 Indicates whether the OSS is informed that the hitless connection move was successful, or whether details of the action are sent. See “hitlessConnectionMove result messages for cpType 8” for more information.

default = 1

1 = disable, only information about the successful initiation of the hitless connection move is sent to the OSS

2 = enable, information about the result of the hitless connection move is sent to the OSS


(2 of 2)

Result message For operation type Description

Out of DBR Resources OptimizeMove and MaintenanceMove

The maximum number of SPVC DBR hitless connection move attempts that can be performed at the same time was exceeded.

Attempt Failed OptimizeMove and MaintenanceMove

Failed because of reasons not related to rerouting, such as the SPVC is an on-node SPVC.

Equipment Overload OptimizeMove and MaintenanceMove

The operation was stopped because of an equipment overload, such as numerous SPVC reroutes.

Cost Too High OptimizeMove and MaintenanceMove

The cost of switching the SPVC route was too high based on local policy.

Activity Switch OptimizeMove and MaintenanceMove

Activity on the node Control card prevented the reroute.

Not Connected OptimizeMove and MaintenanceMove

The SPVC was not connected or no attempt was made to connect the SPVC.

Not Present OptimizeMove and MaintenanceMove

The source of the SPVC is not on the node.

PNNI Not Supported OptimizeMove and MaintenanceMove

PNNI is not enabled on the source SPVC node.

Internal Error OptimizeMove and MaintenanceMove

—

In-Progress OptimizeMove and MaintenanceMove

The operation is still proceeding.

(1 of 2)



29.8 retrieveActiveAlarms action

Use the retrieveActiveAlarms action to retrieve all the active alarms in the Fault Manager aggregator database for all network objects. Only one request can be made at a time for all 5620 CMIP and 5620 CORBA gateways.

Only active alarms received by the 5620 CMIP from the 5620 NM are resent. Active alarms that were generated internally by the 5620 CMIP are not resent.

When you invoke the retrieveActiveAlarms action, a warning alarm is generated to indicate the action has begun. Upon completion, an alarm is sent to indicate the action has been completed.

29.9 configureRealTimeStatistics action

Use the configureRealTimeStatistics action to configure the realtime collection of statistics. Actions must include an ActionInfo argument. This consists of two parts:

• actionType, the OID of the action (1.2.124.113537.1.3.26 for configureRealTimeStatistics)

• actionInfoArg (statistics collection options that are listed for configureRealTimeStatistics)

Table 29-8 describes the actionInfoArg options for the configureRealTimeStatisticsInfo action. All the cpTypes have read-write access.

Reroute-In-Progress OptimizeMove and MaintenanceMove

Another operation was already in progress when this request was made.

Success OptimizeMove and MaintenanceMove

The operation was successful and the SPVC is rerouting over a path that matches the routing policy.

SuccessNoP OptimizeMove and MaintenanceMove

The SPVC was already on the optimum route.

SuccessAndActivated OptimizeMove and MaintenanceMove

The SPVC was rerouted successfully and DBR services were activated.

Improve Cost OptimizeMove A lesser cost route was chosen for the SPVC.

Optimize to an ODR OptimizeMove The SPVC optimized was an ODR.

Move within Max. Cost Delta MaintenanceMove The maintenance move operation was within the cost delta.

Unavailable OptimizeMove and MaintenanceMove

The SPVC route was not changed or was rerouted since the last operation attempt.

Result message For operation type Description

(2 of 2)



Table 29-8 configureRealTimeStatisticsInfo actionInfoArg options

configureRealTimeStatistics action resultsThe result of the configureRealTimeStatistics action contains the collection criteria that have successfully created a new statistics session, and is given a session identifier.

When successfully created, the statistics session remains valid for one hour. During this time, a collectRealTimeStatistics action can be performed on this session to commence statistics collection, or a cancelRealTimeStatistics action to remove this session. See section 29.10 for information about the collectRealTimeStatistics action. See section 29.11 for information about the cancelRealTimeStatistics action.

29.10 collectRealTimeStatistics action

Use the collectRealTimeStatistics action to begin the real time collection of statistics.

• actionType, the OID of the action (1.2.124.113537.1.3.27 for collectRealTimeStatistics)

• actionInfoArg (statistics collection options that are listed for collectRealTimeStatistics)

Table 29-8 describes the actionInfoArg options for the configureRealTimeStatistics action. All the cpTypes have read-write access.


endPointInfo 1 “a”, “z” Default = a

a = endpoint a collection

z = endpoint z collection

If the mORTs attribute does not identify a bMGroomedCircuit or a bMFacility object, any value provided for this option will be ignored.

pollingDuration 2 1 to 10080

Default = 60

Specifies the polling duration in minutes

pollingFrequency 3 4 to 3600

Default = 4

Specifies the polling frequency in seconds

statisticsId 4 up to 256 characters

Multiple statistics identifiers are separated with a comma. A maximum of 10 statistics identifiers are supported per comfigureRealTimeStatistics action.

To see a list of supported statistics identifiers for the object, execute the determineSupportedStatistics action.

This cpType is mandatory.



Table 29-9 configureRealTimeStatistics actionInfoArg options

collectRealTimeStatistics action resultsThe collectRealTimeStatistics action does not return any data. Instead, data resulting from all collectRealTimeStatistics is written to port 8269 on the 5620 CMIP OSS Interface Gateway.

29.11 cancelRealTimeStatistics action

Use the cancelRealTimeStatistics action to cancel the realtime collection of statistics.

• actionType, the OID of the action (1.2.124.113537.1.3.28 for cancelRealTimeStatistics)

• actionInfoArg (statistics collection options that are listed for configureRealTimeStatisticsInfo)

Table 29-8 describes the actionInfoArg options for the configureRealTimeStatisticsInfo action. All the cpTypes have read-write access.

Table 29-10 configureRealTimeStatisticsInfo actionInfoArg options

cancelRealTimeStatistics action resultsThe cancelRealTimeStatistics action does not return any data. Instead, it cancels an existing collectRealTimestatistics session.

29.12 determineSupportedStatistics action

Use the determineSupportedStatistics action to list the supported statistics identifiers for a selected managedObject.

• actionType, the OID of the action (1.2.124.113537.1.3.29 for determineSupportedStatistics)

• actionInfoArg (statistics collection options that are listed for determineSupportedStatistics)


sessionIdentifier 1 [session identifier]

The session identifier of a successfully configured collection session.


sessionIdentifier 1 [session identifier]

The session identifier of a successfully configured collection session.



Table 29-8 describes the actionInfoArg options for the determineSupportedStatistics action. All the cpTypes have read-write access.

Table 29-11 determineSupportedStatistics actionInfoArg options

determineSupportedStatistics action resultsThe determineSupportedStatistics action returns a list of integers representing the statistics identifiers supported by the selected managedObject. An empty list indicates that there are no supported statistics for the selected managedObject.

See the Statistics Collected - Part 2 guide in the 5620 Network Manager User Guide for all statistics identifier descriptions.

29.13 addChannelsToMux action

Use the addChannelsToMux action to add channels to the endpoints of the bMGroomedCircuit when the mORTs attribute is a bMGroomedCircuit, and the endpoint to which channels are to be added is a multiplexer on the OC3/STM1 VoP or 16-port T1/E1 cards. Table 29-12 describes the actionInfoArg objects for the addChannelsToMux action.


endPointInfo 1 “a”, “z” Default = a

a = endpoint a collection

z = endpoint z collection

If the mORTs attribute does not identify a bMGroomedCircuit or a bMFacility object, any value provided for this option will be ignored.



Table 29-12 actionInfoArg objects for addChannelsToMux


endPtAChannelInfo 1 string When the aTPInstance or the zTPInstance identifies a multiplexer, the DS0 channel is identified by a string in the form:

N# S# C#,[#] D#,#

where

# is a number

D#,# identifies the port and DS0 channel in the port

When the aTPInstance or zTPInstance identifies a cell relay endpoint, a DS0 channel cannot be specified. This is denoted with an empty string.

This characteristic is mandatory.

endPtZChannelInfo 2 string When the aTPInstance or the zTPInstance identifies a multiplexer, the DS0 channel is identified by a string in the form:

N# S# C#,[#] D#,#

where

# is a number

D#,# identifies the port and DS0 channel in the port

When the aTPInstance or zTPInstance identifies a cell relay endpoint, a DS0 channel cannot be specified. This is denoted with an empty string.

This characteristic is mandatory.

Assignment mode 3 0,1 0 = AUTO_ASSIGNED (default)

1 = USER_ASSIGNED

When the multiplexer type characteristic of the groomedCircuitTPProfile is set to AAL1, this characteristic is not applicable.

Count 4 1 to 248 default = 1

Specifies the total numer of contiguous channels assigned to an endpoint multiplexer.

When the multiplexer type characteristic of the groomedCircuitTPProfile is AAL1, the value of this characteristic is 1.

Starting CID 5 8 to 255 Specifies the numeric ID of the channel assigned to an endpoint multiplexer when the mORTs attribute identifies a bMGroomedCircuit object with at least one endpoint as a multiplexer.

When the multiplexer type characteristic of the groomedCircuitTPProfile is AAL1 or the asignment mode characteristic is -, this characteristic is not applicable,

When the assignment mode characteristic is 1, this characteristic is mandatory.



29.14 removeChannelsFromMux action

Use the removeChannelsFromMux action to remove channels from the endpoints of the bMGroomedCircuit when the mORTs attribute is a bMGroomedCircuit, and the endpoint from which channels are to be removed is a multiplexer on the OC3/STM1 VoP or 16-port T1/E1 card. Table 29-13 describes the actionInfoArg objects for the removChannelsFromMux action.

Table 29-13 actionInfoArg objects for removeChannelsFromMux

29.15 listChannelsUsedByMux action

Use the listChannelsUsedByMux action to list the channels from the endpoints of the bMGroomedCircuit when the mORTs attribute is a bMGroomedCircuit objectInstance, and the endpoint for the channels is a multiplexer on the OC3/STM1 VoP or 16/32 port T1/E1 VoP card.

listChannelsUsedByMux action resultsThe listChannelsUsedByMux action returns a list of information to identify each channel used by a multiplexer. Each channel used by a multiplexer is identified by its CID, the DS0 of the aTPInstance, and the DS0 of the zTPInstance. This information is repeated for each channel, because the DS0 information may be different for each CID.

29.16 listCustomAttributeNames action

The listCustomAttributeNames action lists the custom attribute names and their associated characteristics identifier, and the managedObject class on which it is supported, when the mORTs attribute is a network object instance.


Starting CID 1 8 to 255 Specifies the numeric ID of the channel assigned to an endpoint multiplexer when the mORTs attribute identifies a bMGroomedCircuit object with at least one endpoint as a multiplexer.

When the multiplexer type characteristic of the groomedCircuitTPProfile is AAL1 or the asignment mode charateristic is -, this characteristic is not applicable,

When the assignment mode characteristic is 1, this characteristic is mandatory.

Count 2 1 to 248 default = 1

Specifies the total numer of contiguous channels assigned to an endpoint multiplexer.

When the multiplexer type characteristic of the groomedCircuitTPProfile is AAL1, the value of this characteristic is 1.



listCustomAttributeNames action resultsThe listCustomAttributeNames action returns a set sequence defined as three fields:

• OID of the managedObjectClass in which customAttribute is supported• OID of the profile attribute in which customAttribute is defined• characteristic identifier of the customAttribute and its associated

customAttributeName pair. The characteristic identifier is either a cpType or a circuitProfileName prefix, depending on the profile attribute that defines them. The cpType is an integer, for example, 10 001. The circuitProfileName prefix is a string, for example, 10001:ca1. The associated customAttributeName is a string.

The output is listed only for the custom attribute names that are defined.

29.17 retrieveISLInfo action

The 5620 CMIP supports the retrieveISLInfo action on the genericActionObject, which lists the inter-shelf link information in the shelves of the 7470 MSP, 7670 ESE, 7350 ASAM, and the 7270 MSC nodes. The input for retrieveISLInfo is the mORT shelf number.

Table 29-14 describes the information that the retrieveISLInfo action returns.

Table 29-14 retrieveISLInfo action information


ISL Number 1 Integer Indicates the ISL number

ISL Level 2 Integer Indicates the ISL level

X Cable Number 3 Integer Indicates the cable ID that connects the hub to the X fabric

Y Cable Number 4 Integer Indicates the cable ID that connects the hub to the Y fabric

ISL Port 5 Integer Indicates the ISL port number on the shelf

Attach Mode 6 Integer Indicates the attach mode of the ISL to the ISL port

(1 of 2)



retrieveISLInfo action resultsTable 29-15 describes the information that is returned by the retrieveISLInfo action.

X Cable Status 7 1 to 14 indicates the status of the X cable

1 = Link is up and running

2 = Link is completely down

3 = Link is degraded

4 = Link has been busied out

5 = Unknown status

6 = Link has been logically busied out

7 = Link has been broken by a configuration change

8 = Cable is active

9 = Cable is in a standby state

10 = Cable has been disabled

11 = Cable is connecting to the fastbus

12 = One or more fibres is down

13 = Underlying link is down, but service is not affected

14 = Link is down but routable

This cpType is applicable only for the shelves in the 7470 MSP node.

Y Cable Status 8 1 to 14 indicates the status of the X cable

1 = Link is up and running

2 = Link is completely down

3 = Link is degraded

4 = Link has been busied out

5 = Unknown status

6 = Link has been logically busied out

7 = Link has been broken by a configuration change

8 = Cable is active

9 = Cable is in a standby state

10 = Cable has been disabled

11 = Cable is connecting to the fastbus

12 = One or more fibres is down

13 = Underlying link is down, but service is not affected

14 = Link is down but routable

This cpType is applicable only for the shelves in the 7470 MSP node.


(2 of 2)



Table 29-15 retrieveISLInfo action results

Result Description

retrieveISLInfoResponse A sequence of managedProfiles, with each managedProfile representing information related to one ISL on the shelf identified by the mORTSs.

The number of managedProfiles in the retrieveISLInfoResponse depends on the type of shelf in the node:

• 7270 MSC contains one managedProfile• 7470 MSP:

• single peripheral shelf: contains one managedProfile• dual peripheral shelf: contains two managedProfiles• high-speed peripheral shelf: contains one to eight managedProfiles• 7350 ASAM access shelf contains two managedProfiles

• 7670 ESE contains four managedProfiles


30 — log object


30.2 log object information 30-2




30 — log object


30.1 Introduction

The log object stores selected notifications as log record objects. The notifications to be logged are selected by the discriminatorConstruct attribute of the log object.

The selected notifications contained by the log are:

• alarmRecord object• attributeValueChangeRecord object• objectCreationRecord object• objectDeletionRecord object• stateChangeRecord object

The system object contains the log object.

30.2 log object information

Table 30-1 contains references to information about the log object.

Table 30-1 log object information


The log object supports the following CMIP operations:

• create• delete• get• cancel get• set

For information about See chapter

alarmRecord object 21

attributeValueChangeRecord object 22

objectCreationRecord object 40

objectDeletionRecord object 41

stateChangeRecord object 45

30 — log object



The log object can generate the following event notifications:

• attributeValueChange• objectCreation• objectDeletion• processingErrorAlarm• stateChange

30.5 Attributes

Table 30-2 describes the log object attributes.

Table 30-2 log object attributes


administrativeState Reflects the log state Read-write default = 1

0 = locked (no further records may be written to the log)

1 = unlocked (notifications may be written and retrieved from the log)

availabilityStatus Qualifies the operational state of the log

Read 8 = logFull

The 5620 CMIP will not report logFull unless the logFullAction attribute is set to halt.

capacityAlarmThreshold Indicates a percentage of capacity where an alarm is generated to indicate that a log full or log wrap condition is approaching


Integer

currentLogSize Reflects the current size of the log measured in octets

Read Current log size

discriminatorConstruct Selects the event notifications to be sent to the destination address

Read-write default = forward all events

Value of filter as described in Annex 2 of CMIP IS 9596 and, if required, the value of the event notification

intervalsOfDay Defines the list of time intervals (interval-start and interval-end times of day) for the logging-on conditions of the log

Read-write default = single interval encompassing the 24 hour period of the day

User specified

logId Is a unique identifier for an instance of the log object class

Read Integer or string; assigned by the OSS (set by create) and read only thereafter

(1 of 2)

30 — log object


logFullAction Determines what action takes place when the log becomes full


0 = wrap

1 = halt

When the log is full and halt is selected, the creation of log records is halted. When wrap is selected and the log fills, a number of records are deleted to free space for new log records to be recorded.

The number of records to be deleted is a configurable parameter (DRIVER_LOG_MAX_RECORDS) and may be specified in the file /opt/netmgt/conexec/bin/netconfig.CEenv. The default number of records to be deleted is 100 records.

maxLogSize Indicates the maximum size of the log in octets

Read-write default = 200 kbytes

0 to n, where

0 = unlimited

The maximum log size is a configurable parameter (DRIVER_LOG_MAX_BYTES) and may be specified in the file /opt/netmgt/conexec/bin/netconfig.CEenv. The maxLogSize attribute of the log object defines the size in octets of the log. If the value of the maxLogSize attribute is set to 0, the log has no maximum size restiction.

nameBinding Identifies the kind of name binding used by a log object

Read Name binding

numberOfRecords Specifies the number of records contained by the log

Read Integer representing the current number of records by the log

objectClass The kind of object Read Always the OID for log

operationalState Status of the object Read 0 = disabled

1 = enabled

packages Identifies the packages used by the log object


startTime Defines the date and time when an unlocked and enabled managed object starts logging

Read-write default = time of creation of the managed object

User specified

stopTime Defines the date and time when an unlocked and enabled managed object stops logging

Read-write default = continual

User specified


(2 of 2)



31.1 Introduction

The loopBackTestObject is created to administer the loopback test. It is deleted at the end of the test. The loopBackTestObject is contained by the testActionPerformer object; multiple instances of the loopBackTestObject can be contained by the testActionPerformer object.

See the 5620 NM Fault Management guide for more information about the loopback diagnostic.


The loopBackTestObject supports the following CMIP operations:

• get• cancel get• set• action—lbRelease, lbEquipment, and lbLine


The loopBackTestObject can generate the following CMIP event notifications:


31.4 Attributes

Table 31-1 describes the attributes of the loopBackTestObject.

Table 31-1 loopBackTestObject attributes


lbRecoveryType Indicates how to treat the affected link or path

Read-write 1 = connected-down

2 = reroute

3 = disconnect

lbTestName Is a text field for naming test Read-write Any text

lbTestType Identifies the type of test being performed

Read 0 = lbRelease

1 = lbLine

2 = lbEquipment

mORTs Is the object instance of the managed object where the loopback test is to occur.


(1 of 2)




Read Name binding

objectClass Indicates the kind of object Read OID of the loopBackTestObject

operationalState Indicates the operational status of the object

Read 0 = disabled

1 = enabled






2 = initializing

3 = reporting

4 = terminating


testInvocationID Provides the distinguishedName of the loopBackTestObject




(2 of 2)



32.1 Introduction

The managedElement object models a node and is contained by a partition-level network object.


The managedElement object supports the following CMIP operations:

• get• cancel get• set• action on the network object—FindByLabel to retrieve the managedElementID

given the userLabel


The managedElement object can generate the following event notifications:

• attributeValueChange• equipmentAlarm• objectCreation• objectDeletion• stateChange

32.4 Attributes

Table 32-1 describes the attributes of the managedElement object.

Table 32-1 managedElement object attributes


administrativeState Reflects the availability of the managedElement object

Read Always unlocked


Read Tied to operationalState (cleared or active Reportable–indeterminate)

locationName Describes the location of the equipment Read-write default = null

Only an OSS can assign a value to this attribute.

managedElementID Is a unique identifier for an instance of the managedElement object

Read Integer-node_id

nameBinding Is the kind of name binding Read Name binding

objectClass Is the kind of object Read Always the OID for managedElement

(1 of 2)



Table 32-2 describes the mapping between equipment vendor and the vendorName attribute.

Table 32-2 Mappings between equipment vendor and vendorName attribute

Table 32-3 describes the mapping of equipment to the version attribute for nodes.

Table 32-3 Mappings between equipment and the version attribute

operationalState Is the status of the object in the network Read 0 = disabled

1 = enabled

packages Is a package used by object Read List of packages; see the GDMO for information

systemTitle Identifies the 5620 CMIP OSS Interface Gateway

Read 5620 CMIP-defined OID

usageState Indicates whether a managedElement object is in use

Read Always active

userLabel Allows a 5620 NM operator or an OSS to assign a name to a node

Read-write Holds a node full name, short name, or both, depending on the value of the -mEUL process start-up option. See Table 8-4 for more information.

version Indicates node type and generic Read Holds node type and generic; see Table 32-3 for details

vendorName Holds the CPSS or IP address Read See Table 32-2 for details


(2 of 2)

Equipment vendor vendorName attribute

Alcatel [Alcatel Networks, CPSS address: domain.major] There is one space before CPSS; domain.major represents a numerical value.

or

[Alcatel Networks, IP address: IPaddress] where IP address represents a numerical value in the form nnn.nnn.nnn.nnn

CrossKeys CrossControl Proxy Agent [Other Vendor, CPSS address: domain.major] There is one space before CPSS; domain.major represents a numerical value.

or

[Other Vendor, IP address: IPaddress] where IP address represents a numerical value in the form nnn.nnn.nnn.nnn

Equipment name Version attribute (1)

Custom node type generic Node: Custom Generic

CrossControl Proxy Agent Node: DCS Proxy Agent Generic

1630SX Node: 1630 SX Generic: 1630-SX-00-00

DACS II Node: DACS II Generic: via Proxy Agent

DSC DEX CS1L Node: DEX CS1L Generic: via Proxy Agent

(1 of 2)



Notes(1) [Node: Node name Generic: software generic] There are two spaces between Node name and Generic.(2) See Table 32-4 for a list of Alcatel Node name variables.

Table 32-4 lists the Alcatel Node name variables for 5620 CMIP, Release 5.2 or later.

DSC DEX CS1VL Node: DEX CS1VL Generic: via Proxy Agent

T::DAX Node: 3/1 DCS TDAX Generic: TDAX-00-00

T::DAX 100 Node: 3/1 DCS TDAX 100 Generic: TDAX-00-00

Element-managed node

Node: Node name Generic: Element Managed

Node: Node name Generic: software generic Element Managed

Valid for the 7300 ASAM node.

Node: LVG Generic: software generic Element Managed

Valid for the 7300 ASAM node with voice gateway module.

The hardware type of the node remains the same, but the 5620 DSL EM, Release 7.0 or later, identifies the node as LVG when the node contains a VALT card.

Node: FENT Generic: software generic Element Managed

Valid for the 7300 ASAM node with a FENT NT controller.

The hardware type of the node remains the same, but the 5620 DSL EM, Release 7.0 or later, identifies the node as FENT when the node contains a FENT card.

Node: GENT Generic: software generic Element Managed

Valid for the 7300 ASAM node with a GENT NT controller.

The hardware type of the node remains the same, but the 5620 DSL EM, Release 7.0 or later, identifies the node as GENT when the node contains a GENT card.

Node: FTTNEU Generic: software generic Element Managed

Valid for the 7302 ISAM node (ETSI standard) with remote shelf configuration.

The hardware type of the node remains the same, but the 5620 DSL EM, Release 7.0 or later, identifies the node as FTTNEU when the node contains an ARAM shelf as the first shelf, and the node standard is ETSI.

Node: FTTNUS Generic: software generic Element Managed

Valid for the 7302 ISAM node (ANSI standard) with remote shelf configuration.

The hardware type of the node remains the same, but the 5620 DSL EM, Release 7.0 or later, identifies the node as FTTNUS when the node contains an ARAM shelf as the first shelf, and the node standard is ANSI.

Node: Node subtype string Generic: software generic Element Managed

For the 1540 Litespan node, the node subtype strings that are supported are MLSA and MLSB.

For the 7300 ASAM node, the node subtype strings that are supported are LAEU, LAUS, MAEU, MAUS, LVG, FENT, and GENT.

For the 7302 ISAM node, the node subtype strings that are supported are LEEU, LEUS, FTTNEU, and FTTNUS.

Alcatel (2) Node: Node name Generic: software generic

Equipment name Version attribute (1)

(2 of 2)



Table 32-4 Alcatel Node name variables

Node name Description

1353 NM 1353 NM node

1540 1540 Litespan node

1671 SC 1671 SC node

2902 2902 node

3600 3600 node

3600+ 3600+ node

3612 3612 node

3620 3620 node

3624 3624 node

3630 3630 node

3660 3660 node

3664 3664 node

4200 4200 router

4400 4400 router

4500 4500 router

5601 5601

5610 5610

36110-8 36110 8-port node

36110-20 36110 20-port node

36111-24 36111 24-port node

36111-80 36111 80-port node

36120 FASTbus node

36130 36130 node

36150 36150 node

36160 36160 node

3606(Data) 3606 data-only variant

3606(Voice/Data) 3606 voice-data variant

3606/iDSU 3606/iDSU DDS node

3620 Router 3620 router

3600 MSS DS3 3600 MSS DS3

3600 MSS E3 E3 node

3600 MSS SE3 3600 MSS SE3

5620 OSS Gateway OSS Interface Gateway Station

7270MSC 7270 MSC node

7300ASAM 7300 ASAM node

(1 of 2)



7302 7302 ISAM node

7324 7324 RU node

7350ASAM 7350 ASAM node

7390DBS 7390 DBS node

7390NT 7390 NT

7470MSP 7470 MSP node

7670RSP 7670 RSP node

7670ESE 7670 ESE node

9400AWY 9400 AWY node

9600USY 9400 USY node

Amazon Amazon router

ASAM ASAM node (element-managed)

ATM Host ATM-attached host node

ATM Workgroup Switch ATM workgroup switch

Danube Danube router

Danube Hub Danube hub router

Element Manager Element manager node

FRATM FRATM node

Generic DCS DCS manager

Hub ASAM Hub ASAM node (element-managed)

ISDN Access ISDN access node

MDR8000 MDR 8000 node

Nile Nile router

NileT NileT router

Ridge-attached Host Ridge-attached host

Stats aggregate ST aggregate node

Stats collector Stats collector node

Subtended ASAM Subtended ASAM node (element-managed)

TAP —

Yellow Ridge Yellow ridge node

Node name Description

(2 of 2)



33.1 Introduction

The managedEquipment object models a resource or port when the resource or port cannot serve as a path or link endpoint, including:

The managedEquipment object class is a subclass of, and allomorphs, the M.3100 equipment object class. It indicates, through the managedEquipmentType attribute, the type of equipment an instance models.

See Figure 20-5 for an illustration of how equipment objects are contained in different networks.


The managedEquipment object supports the following CMIP operations:



The managedEquipment object can generate the following CMIP event notifications:

• attributeValueChange• communicationsAlarm• objectCreation• objectDeletion• stateChange

33.4 Attributes

Table 33-1 describes the attributes of the managedEquipment object.

• DSP3 and DSP4 resources • endpoint SRMs • FASTbus ports • FRE/FRS ports • HCVs

• MJUs • SRMs • SRSs • T1/E1 resources



Table 33-1 managedEquipment object attributes

Table 33-2 describes the value descriptions for all types of managedEquipment objects.

Table 33-2 Value description for managedEquipmentType attribute


administrativeState Reflects the availability of an object as imposed through management services

Read normal = unlocked

loopback status = locked

affectedObjectList Is a list of affected path ends; not present for power supplies and fans

Read List of distinguishedNames (can be empty)

allomorphs Allows the managedEquipment object to resemble one or more object classes

Read Always managedEquipment

equipmentId Name binding; unique identifier for an instance of the managedEquipment object

Read Integer; 5620 NM device id, circuit id, or channel unit id.

locationName Allows the OSS to specify a location label for the equipment

Read/write default = null

String with a buffer size is 255 bytes

Not present for power supplies and fans

managedEquipmentType Describes the type of equipment

Read String describing equipment type


nameBinding Identifies the kind of name binding used by a managedEquipment object

Read Name binding

objectClass Is the class of object Read Always the OID for managedEquipment


Read 0 = disabled

1 = enabled

packages Identifies the packages used by the managedEquipment object


replaceable Indicates replaceability of managedEquipment object instance

Read Always no

Type of equipment

Value description Example

Channel Unit Channel Unit: type Channel Unit: 2B1Q

(1 of 2)



Device Device: type Device: SRM

Circuit Resource: type Resource: VT1.5

Type of equipment

Value description Example

(2 of 2)




34.2 Supported 5620 CMIP operations 34-2



34.5 facilityTPProfile attribute 34-4

34.6 trmPhysicalInterface attribute 34-19

34.7 cTPId attribute 34-27



34.1 Introduction

The managedFacilityTP object models physical and logical link endpoints. It is contained by a managedElement object and is equivalent to the physical and logical link endpoints of the 5620 NM.

The managedFacilityTP object class is a subclass of and allomorphs the BME bMFacilityTP object class. It models extra link endpoint configuration functionality not present in its parent object class. Table 34-2 describes the extra link endpoint configuration functionality, which is handled in the facilityTPProfile attribute.

34.2 Supported 5620 CMIP operations

The managedFacilityTP object supports the following 5620 CMIP operations:



The managedFacilityTP object can generate the following event notifications:

• attributeValueChange• communicationsAlarm• equipmentAlarm• objectCreation• objectDeletion• stateChange

34.4 Attributes

Table 34-1 describes the attributes of the managedFacilityTP object. Additional attribute information is provided after the table.



Table 34-1 managedFacilityTP object attributes


administrativeState Reflects the availability of the managedFacilityTP object.

You can lock or unlock an ADSL port using the administrativeState attribute.

Read-write for ADSL, XDSL, and SHDSL on 7300 ASAM nodes.

Read for all other ports.

0 =locked

1 = unlocked (default)


Updated when port alarm suppression is enabled

Read Tied to operationalState (cleared or activeReportable– Indeterminate)

allomorphs Allows the managedFacilityTP object to resemble one or more object classes

Read Always bMFacilityTP

cTPId Naming attribute; unique identifier for an instance of managedFacilityTP object class

Read String is N# S# C# [,#] D# [LE#]

See section 34.7 for information

currentProblemList Identifies the probable cause of an alarm; not implemented for all card types

Currently implemented for the following cards: OC3, STM1, OC12, STM4, DS3 CCE, E1CE, T3, and E3

Not updated when port alarm suppression is enabled

Read The probableCause OID describing the alarm; see Table App D-5 for details

downstreamConnectivity Pointer


facilityTPProfile Is a multivalued attribute for further endpoint configuration

See Table 34-2 See Table 34-2 for details

nameBinding Identifies the kind of name binding used by a managedFacilityTP object

Read Name binding

objectClass Is the kind of object Read Always the OID for managedFacilityTP

operationalState Is the status of the object in the network; updated when port alarm suppression is enabled

Read 0 = disabled

1 = enabled

packages Identifies the packages used by the managedFacilityTP object

Read List of packages; see the GDMO for details

supportedByObjectList Lists the supporting objects Read Distinguished name of the supporting managedEquipment or managedPack object

trmFunctionalInterface Identifies the logical interface supported by the managedFacilityTP object

Read Null unless an instance can be a logical link endpoint.


trmPhysicalInterface Identifies the physical interface supported by the managedFacilityTP object

Read Null unless an instance can be a physical link endpoint; see Table 34-8

typeText Contains a description of the device type

Read Describes a port type, such as an OC3 or a DS0 (1)

(1 of 2)



Note(1) The value for ABLT-S2/T2 cards is ABLT. The value for ADLT-S2-T2 cards is ADLT.

34.5 facilityTPProfile attribute

Table 34-2 describes the characteristics of the facilityTPProfile attribute of the managedFacilityTP object.

Table 34-2 facilityTPProfile attribute characteristics

upstreamConnectivity Pointer


userIdentifier Allows the OSS to assign a label to the link


String of up to 255 characters; only an OSS can modify

This attribute is read only for the 5620 NM

userLabel Allows the OSS or the 5620 NM operator to assign a name for an object instance.


String

This attribute can be set by the OSS or the 5620 NM operator


(2 of 2)

Characteristic Access cpType cpValue Description

Gender Read-write 1 1, 2 1 = DCE

2 = DTE (default)

Link protocol type Read-write 2 0 to 10, 12 0 = none

1 = LMI user

2 = LMI network

3 = LMI network extended

4 = LMI NNI

5 = Annex D user

6 = Annex D network

7 = Annex D bidirectional

8 = Annex A user

9 = Annex A network

10 = Annex A bidirectional

12 = LMI auto detect

Port alarm suppression Read-write 3 0, 1 0 = disabled

1 = enabled

Statistics activation status

Read-write 4 1, 2 1 = disabled (default)

2 = enabled

1+1 Working port

1+1 Protection port

Read 5 0, 1 0 = 1+1 working port

1 = 1+1 protection port

(1 of 10)



1+1 Mate port Read 6 n The device number of the mate port; valid only in 1+1 APS

Switching mechanism Read 7 0, 1 0 = nonrevertive

1 = revertive

Valid only for the protection port in 1+1 APS

WTR timer Read 8 1 to 60 Valid only when the switching mechanism is revertive

Switching direction Read 9 0 Unidirectional; valid only for the protection port in 1+1 APS

Protection group status Read 10 1 to 5 1 = up

2 = down

3 = testing

4 = unknown

5 = dormant

1+1 Mate shelf Read 11 n The shelf number of the mate port; valid only in 1+1 APS

1+1 Mate slot Read 12 n The slot number of the mate port; valid only in 1 + 1 APS

Frame type Read-write 13 1, 2, 3, 4, 8 Default and valid values depend on the card or device type. See Table 34-3.

1 = D4

2 = Extended Super Frame

3 = Transparent

4 = T1 Unframed

8 = HD T1 FR Unframed

Valid only for T1, DS1, CE, HD T1 FR, T1 ATM device types.

1, 2, 3, 4, 7, 9 Default and valid values depend on the card or device type. See Table 34-3.

1 = CAS

2 = CCS

3 = X.21 Network Termination Unit

4 = 31 Channel Signaling

7 = E1 Unframed

9 = HD E1 FR Unframed

Valid only for E1, E1 CE, HD E1 FR device types.

Stream mode Read 14 1, 2 1 = CFR

2 = UFR

Valid for HD T1 FR and HD E1 FR cards, and for the DS3 FR and DS1 FR ports on the 3-DS3 frame processing card.

NTU type Read 15 1 to 4 1 = frame relay

2 = T1 CE

3 = E1 CE

4 = V.35 CE


(2 of 10)



TNT port configuration state

Read 16 0 to 4 0 = not configured

1 = not structured

2 = structured

3 = structured SF

4 = structured ESF

Quality of Service Read 17 1, 4, 7 1 = CBR

4 = UBR

7 = BiQOS

CAC incoming profile Read-write 18 managed- ProfileID value

See section 37.5 for information about managedProfileID values.

For ports on NT cards, these cpTypes describe the managedProfileID value of the ASAM NT CAC Profile.

For ports on LT cards, these cpTypes describe the managedProfileID value of the ASAM LT CAC Profile.

CAC outgoing profile 19

Access profile 20 For ports on NT cards this cpType describes the managedProfileID value of the ASAM NT Access Profile.

For ports on LT cards, this cpType describes the managedProfileID value of the ASAM LT Access Profile.

ADSL profile 21 Valid only for ADSL ports. Describes the managedProfileID value of the ADSL Profile.

Profile Type Read 22 0 to 4 0 = none

1 = node predefined (default)

2 = node user

3 = NMS predefined

4 = NMS user

Port profile number Read-write 23 1 to 880 default = 1

This cpType gives the profile number for ADSL ports on the 7350 ASAM node.

For Conklin FASTmux 2000 nodes, this cpType specifies the Interleave/Fast profile number. The valid values are 1 to 16 (default = 16)

AAL Service Type Read-write 24 1 to 5 Default and valid values depend on the card or device type. See Table 34-4.

1 = unchannelized

2 = unchannelized monitored

3 = channelized basic

4 = channelized CAS

5 = channelized


(3 of 10)



Interface Type

(7300 ASAM Release 4.2 and later)

Read 25 7 to 12 7 = Network Termination (NT) (default for NT ports)

8 = Access to Access Interface (AAI)

9 = User to Access Interface (UAI)

10 = Internal Server Interface (ISI)

11- NS = Not Supported (default for LT ports)

12 = ATM Server Interface (ASI)

For XDSL ports, the Interface Type can only have values 9 or 11.

Ngcr Admin Weight

(7300 ASAM Release 4.2 and later)

Read-write 26 1 to 1000000 1 to 100 for ADSL and XDSL ports

1 for NT ports

Only applicable for IQ LT cards

Service Type Read 27 2 to 3 2 = CE (default)

3 = CR

This cpType gives the service type of the T1/E1 ports on the OC3/STM1 MS card.

IMA Resource Port Assignment

Read-write for IMA resources managed by the 5620 NM

Read for EM- managed IMA resources

28 0, FFFFFFFFFFFFFFFFFFFFFF

default = 0

String of up to 22 hexadecimal characters.

This cpType describes the CR ports assigned to IMA resources.

For more information, see the subsection, “Calculating the cpValue for cpType 28 of facilityTPProfile—IMA Resource Port Assignment” in this chapter.

Wire Mode (2-wire or 4-wire)

Read-write 29 2, 4 2 = 2-wire mode (default)

4 = 4-wire mode

Power Spectral Density (PSD) (symmetric or asymmetric)

Read 30 2, 4 2 = symmetric (default)

4 = asymmetric

Regional Settings Read-write 31 0,1 0 = Annex A (default)

1 = Annex B

Minimum Data Rate Read-write 32 192 kbps to 4608 kbytes

The data rate depends on the choice of Wire Mode, Power Spectral Density, and Regional Settings.

Maximum Data Rate Read-write 33 192 kbps to 4608 kbytes

The data rate depends on the choice of Wire Mode, Power Spectral Density, and Regional Settings.

ILMI Channel status Read-Write 34 0, 1 0 = Disabled

1 = Enabled

Configured Access Rate Read-write 35 0 to 8X1544 for T1 rates

0 to 8X2048 for E1 rates

The access rate of the T1 or E1 card.

MFR Bundle ports map Read-write 36 0 (default) to 255 Used to assign T1/E1 FR ports to MFR resource objects. The default is 0.

See Table 34-7 for more information about assigning ports to MFR resources.


(4 of 10)



Tag Mode Read-write 37 1, 2 Specifies whether the GigE port is VLAN tagged.

1 = Tag Aware

2 = Tag Unaware

The default is 2.

Ingress Filtering Read-write 38 1, 2 Specifies the options to filter ingress traffic on the GigE card.

1 = Allow All (default)

2 = Discard Tagged

CAC Profile Incoming (7300 ASAM Release 5.0 and later)

Read-write 39 managed - ProfileID value

For ports on NT cards, specifies the NT CAC profile managedProfileID value.

For ports on LT cards, specifies the LT CAC profile managedProfileID value.

CAC Profile Outgoing Profile (7300 ASAM Release 5.0 and later)

Read-write 40 managed - ProfileID value

For ports on NT cards, specifies the NT CAC profile managedProfileID value.

For ports on LT cards, specifies the LT CAC profile managedProfileID value.

Protocol Type Read 41 0 to 2 Specifies the protocol type for channels on MR48 I/O cards and OC3 clear/DS1 CR channels on the OC3 I/O card of the ESC.

0 = none (default)

1 = ATM

2 = POS

Only 0 and 1 are applicable to the OC3 clear/DS1 CR channels on the OC3 I/O card of the ESC.

Auto Negotiation Read 42 1, 2 1 = enabled (default)

2 = disabled

Rx Flow Control Read 43 1, 3 1 = enabled


Duplex Mode Read 44 1 1 = full duplex mode

Line Rate Read 45 1000 1000 = line rate in Mb/s

Link Aggregation Type Read 46 0 to 2 0 = none (default)

The port is not added to any LAG.

1 = primary

The port is the primary port of a LAG.

2 = secondary

The port is the secondary port of a LAG.


(5 of 10)



Link Aggregation Mate Read 47 0 to 4 0 = none (default)

No secondary port has been attached with the primary port.

1 = 1-1

The secondary or primary port assigned is the first port on the first GigE I/O card.

2 = 1-2

The secondary or primary port assigned is the second port on the first GigE I/O card.

3 = 2-1

The secondary or primary port assigned is the first port on the second GigE I/O card.

4 = 2-2

The secondary or primary port assigned is the second port on the second GigE I/O card.

LAG Status Read 48 3, 4 3 = LAG status is Up (default)

4 = LAG status is Down

Jumbo Frames Read 49 1, 2 1 = enabled (default)

The port allows packets larger than 1519 octets.

2 = disabled

Packets larger than 1519 octets are flagged and discarded

XDSL Service Profile Read-write 50 managedProfileID value

For NT ports, this cpType describes the 7300 ASAM NT XDSL Service Profile managedProfileId value.

For LT ports, this cpType describes the 7300 ASAM LT XDSL Service Profile managedProfileId value.

XDSL Spectrum Profile Read-write 51 managedProfileID value

For LT ports, this cpType describes the 7300 ASAM LT XDSL Spectrum Profile managedProfileId value.

Link Aggregation Name Read 72 1 to 16 characters Indicates the name of the Link Aggregation group.

This cpType is applicable to 7670 RSP nodes, Release 2.2 HLS#3 or later.

LACP Mode Read 73 0 to 2 0 = LACP mode is passive

1 = LACP mode is active

2 = LACP mode is disabled (default)

This cpType is applicable to 7670 RSP nodes, Release 2.2 HLS#3 or later.

This cpType is disabled for 7670 RSP nodes, Release 2.2 HLS#3 and Release 3.0.

LACP Timeout Read 74 0 to 1 0 = LACP timeout value is long

1 = LACP timeout value is short (default)

This cpType is applicable to 7670 RSP nodes, Release 4.0 or later.


(6 of 10)



Load Balance Read 75 1, 2 1 = disabled (default for 7670 RSP nodes, Release 2.2 HLS#3 and Release 3.0)

2 = enabled (default for 7670 RSP nodes, Release 4.0 or later)

LACP System Priority Read 76 1 to 65535 default = 1

Unique short integer value for each 7670 RSP node, Release 4.0 or later

LACP Operational Key Read 77 1 to 65536 default = 1

Short integer value for 7670 RSP nodes, Release 4.0 or later

LACP Port Status Read 78 0 to 3 0 = OK (default)

1 = OutofSync

2 = LoopbackDetected

3 = RxMachineExpired

This cpType is applicable to 7670 RSP nodes, Release 4.0 or later.

LACP Partner System Priority

Read 79 1 to 65535 default = 1

Unique short integer value for each 7670 RSP node.

This cpType is applicable for 7670 RSP nodes, Release 4.0 or later, and when cpType 73 is 0 or 1.

LACP Partner System MAC

Read 80 1 to 18 characters MAC address of the partner system.


LACP Partner Operational Key


Short integer value.


Number of Configured Links

Read 82 0 to the maximum number of ports on the card

default = 0

The number of ports assigned to the IMA resource.

Minimum number of Active links

Read 83 1 to the maximum number of configured links

The minimum number of active links that are part of an IMA resource to be present in order to keep the IMA resource status up.

IMA mode Read 84 0, 1 Refers to the IMA CAC behavior exhibited by the IMA group.

0 = Standard IMA behavior; uses the minimum number of active links of an IMA resource to calculate the CAC bandwidth on the resource (default)

1 = Non standard IMA CAC behavior; uses the number of configured links of an IMA resource to calculate the CAC bandwidth on the resource.


(7 of 10)



Maximum Frame Length Read-write 85 16 to 4472 for normal FSC Objects;

166 to 4472 for MFR Bundle FSC object

default =1600

This cpType is not applicable if cpType 86 is set to any value other than “Frame Relay Switching.”

This cpType is read-only for FSCs assigned to an MFR Bundle FSC.

Changing the value of this cpType in an MFR Bundle FSC will automatically change the value in all the FSC objects that are assigned to the MFR Bundle FSC.

Frame Stream Application

Read 86 1 to 4, 6 to 12 1 = CPSS Routing

2 = Ethernet Bridging

3 = Token Ring Bridging

4 = Frame Relay Switching (default)

6 = Rate Adaption

7 = ISDN Application

8 = Encapsulation in frame relay

9 = Direct Access (FRE/PE only)

10 = Transparent HDLC Frame Forwarding

11 = Translated Frame Forwarding

12 = FR-UNI

Cell Mapping Read-write 87 1, 2 1 = PLCP (default for the 3/8 port DS3 card)

2 = direct (default for the E3 card)

This cpType is read-only when:

• the transport module is configured on the parent card

• the aTPInstance or zTPInstance of bMGroomedCircuitObject specifies a managedGroomedCircuitTP object that is associated with the managedFacilityTP (physical) object where this cpType is specified

• the aTPInstance or zTPInstance of bMGroomedCircuitObject forms a cross-connection associated with the managedFacilityTP (physical) object where this cpType is specified

• the aTPInstance or zTPInstance of a bMFacility object representing a full or fractional link specifies a managedFacilityTP (physical) object where this cpType is specified.

On the 7470 MSP node, this cpType is applicable for physical ports on the 3/8 DS3 and E3 cards.

On the 7670 RSP node, this cpType is applicable to physical ports on the DS3 channels of the OC12 and OC48 I/O cards in the MR48 ATM line card when the Protocol Type of the DS3 channel is configured as ATM.

AESA address Read 90 string default = undefined

The address is 40 characters; each character is 0 to 9, a to f, or A to F. (1)


(8 of 10)



Port Variant Read 91 1 to 4 1 = short reach (default)

2 = intermediate reach

3 = long reach

4 = electrical reach

Valid only when the card variant is SFP. This cpType is applicable for ATM ports on the Quad OC3/STM1 SFP CR card on the following nodes:

• 7470 MSP, Release 8.0 HLS#2 or later• 7670 ESE, Release 4.0 HLS#2 or later

DS3 application Read-write 95 2, 4 2 = M23 application

4 = C-bit parity (default)

This cpType is applicable for the DS3 FR port on the 3-DS3 frame processing card.

CRC Framing Read-write 96 1, 2 1 = on

2 = off

Transfer Mode Read-write 97 1, 2 1 = ATM (default)

2 = PTM

This cpType is applicable for XDSL ports on VDSL2 card types.

customAttributeValue1 Read-write 10001 string Where string is up to 254 characters, and contains custom information that is associated with the managedFacilityTP object.









(9 of 10)
















(10 of 10)



Note(1) An AESA value identifies the logical endpoint of an SPVC path. Each character represents a hex nibble. To calculate the

AESA for a physical endpoint, use the following definition:AA-AAAA-AAAAAAAAAAAAAAAAAAAA-BBBBBB-CCCC-DD-EEA = the Internal Switch Subscriber Prefix for the node (26 characters)B = the OUIC = shelf and slot informationD = port numberE = contains the DS0 channel number for circuit emulation cards or is 0 for all other card typesIf an OSS request for a 5620 NM-managed node contains the AESA, it must match the above representation (including hyphens); otherwise, the 5620 CMIP may fail the request.

Table 34-3 Default and valid values for the Frame Type characteristic (cpType 13) of the facilityTPProfile attribute

Card Device Valid values Dependency

32E1MS CEPT 1 = CAS

4 = 31-Channel (default)

Frame Type (cpType 13) is not formed when AAL Service Type is set to 1.

32T1MS T1 1 = super Frame

2 = Ext Super Frame (default)


DS3CCE DS1 CES 1 = super Frame


3 = Transparent


DS3CCE2 T1 1 = super Frame


—

DS3 CFR T1 2 = ESF (default) —

E1 CEPT 1 = CAS (default)

2 = CCS

3 = X.21 Network Termination Unit

4 = 31-Channel

—

E1 CE 75 CEPT 1 = CAS

4 = 31-Channel

See Table 34-4

E1 CE 120 CEPT 1 = CAS

4 = 31-Channel

See Table 34-4

E1CFR75 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

E1CFR120 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

E1D CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

E1D2 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

(1 of 3)



E1FR CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

9 = HD E1FR Unframed

Stream Mode (cpType 14) is set to UFR (2) and cannot be changed when Frame Type is 9. When Frame Type is 1, 2, or 4, Stream Mode can be set to CFR (1) or UFR (2).

E1UFR75 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

E1UFR120 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

E3 CCE E1 UCE 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

E3 CCE2 CEPT 1 = CAS (default)

4 = 31-Channel

—

ESC OC3 I/O T1 ATM 1 = super Frame


—

OC3MS T1 1 = super Frame


—

OC3 VOP T1 1 = super Frame


—

OE1 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

OT1 T1 1 = super Frame (default)

2 = Ext Super Frame

—

SE3 CEPT 1 = CAS (default)

2 = CCS

4 = 31-Channel

—

STM1MS CEPT 1 = CAS


—

STM1 VOP CEPT 1 = CAS


—

T1 T1 1 = super Frame (default)

2 = Ext Super Frame

—

T1 ASC1 T1 1 = super Frame (default)

2 = Ext Super Frame

—

T1 ASC1/5 T1 1 = super Frame (default)

2 = Ext Super Frame

—

T1 ATM T1 ATM 1 = super Frame


—

T1 CE T1 1 = super Frame

2 = Ext Super Frame

See Table 34-4


(2 of 3)



Table 34-4 Default and valid values for the AAL Service Type characteristic (cpType 24) of the facilityTPProfile attribute

T1CFR T1 1 = super Frame


—

T1D T1 1 = super Frame (default)

2 = Ext Super Frame

—

T1D2 T1 1 = super Frame (default)

2 = Ext Super Frame

—

T1FR T1 1 = super Frame


8 = HD T1FR Unframed

Stream Mode (cpType 14) is set to UFR (2) and cannot be changed when Frame Type is 8. When Frame Type is 1 or 2, Stream Mode can be set to CFR (1) or UFR (2).

TT1 T1 1 = super Frame (default)

2 = Ext Super Frame

—

T1UFR T1 1 = super Frame


—

T1VS T1 1 = super Frame


—


32E1MS CEPT 1 = Unchannelized

2 = Unchannelized Monitored

3 = Channelized Basic (default)

4 = Channelized CAS


When AAL Service Type is set to 2 or 3, Frame Type is set to 4.

When AAL Service Type is set to 4, Frame Type is set to 1.

32T1MS T1 1 = Unchannelized



4 = Channelized CAS


When AAL Service Type is set to 2, 3, or 4, Frame Type is set to 2.

DS3 CCE2 T1 1 = Unchannelized



4 = Channelized CAS

Frame Type (cpType 13) is not formed when AAL Service Type is set to 1 or 2.

When AAL Service Type is set to 3 or 4, Frame Type is set to 2.

DS3 CCE2 DS3 1 = Unchannelized


5 = Channelized

—

(1 of 2)


(3 of 3)



E1 CE 75 CEPT 1 = Unchannelized (default)


3 = Channelized Basic

4 = Channelized CAS





E1 CE 120 CEPT 1 = Unchannelized (default)



4 = Channelized CAS





E3 CCE2 CEPT 1 = Unchannelized



4 = Channelized CAS





ESC OC3 OC3 port 0 = Unconfigured (default)

1 = Channelized

2 = Unchannelized

—

OC3MS T1 1 = Unchannelized



4 = Channelized CAS

Frame Type (cpType 13) is not formed when AAL Service Type is set to 1 or 2. When AAL Service Type is set to 3 or 4, Frame Type is set to 2.

OC3 VOP T1 3 = Channelized Basic (default) —

STM1MS CEPT 1 = Unchannelized



4 = Channelized CAS



When AAL Service Type is set to 3, Frame Type is sset to 4.


STM1 VOP CEPT 3 = Channelized Basic (default) —

T1 CE T1 1 = Unchannelized (default)



4 = Channelized CAS


When AAL Service Type is set to 2, 3, or 4, Frame Type is set to 2.


(2 of 2)



Calculating the cpValue for cpType 28 of facilityTPProfile—IMA Resource Port Assignment

The assignment of physical ports to an IMA resource is represented in the cpValue of cpType 28 of facilityTPProfile (IMA Resource Port Assignment) by a bit mask formatted as a hexadecimal character string. Up to 88 ports can be assigned to an IMA resource, depending on the type of IMA resource. The cpValue can be 1 to 22 hexadecimal characters. Each hexadecimal character represents four physical ports. Physical ports 1 to 4 are represented by the first (left-most) hexadecimal character, with port 1 represented by that character’s most significant bit and port 4 by the least significant bit. Ports 5 to 8 are represented by the next hexadecimal character, and so on. Trailing 0 characters are optional when you write the cpValue, and are truncated when the cpValue is read.

Table 34-5 provides an example of a cpValue where ports 3, 4, 6, 9, and 10 are assigned to an IMA resource. When you write this cpValue, the 34C0 or 34C string can be used. When reading this cpValue, the 34C string is returned.

Table 34-5 Sample cpValue bitmask for cpType 28 of facilityTPProfile—IMA resource

Table 34-6 provides another example of a cpValue where ports 5, 6, and 7 are assigned to an IMA resource. When you write this cpValue, the 0E0 or 0E string can be used. When you read this cpValue, the 0E string is returned.

Table 34-6 Sample cpValue for cpType 28 of facilityTPProfile—IMA resource

Physical port

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Bit mask 0 0 1 1 0 1 0 0 1 1 0 0 0 0 0 0

Hexadecimal 3 4 C 0

String 34C0

Truncated string 34C

Physical port

1 2 3 4 5 6 7 8 9 10 11 12

Bit mask 0 0 0 0 1 1 1 0 0 0 0 0

Hexadecimal 0 E 0

String 0E0

Truncated string 0E



Calculating the cpValue for cpType 35 of facilityTPProfile—MFR resource

Table 34-7 illustrates a sample cpValue bitmask for cpType 35 of facilityTPProfile attribute. The cpValue identifies the physical port assignments for MFR port objects by using a 16-bit hexadecimal number. A one in a bit indicates that a port has been assigned to the resource, while a zero in a bit indicates that a port has not been assigned to the resource. In the example, ports 4, 6, and 7 are assigned to an MFR resource. Therefore, the cpValue of the bitmask is the decimal number 104.

Table 34-7 Sample cpValue bitmask for cpType 35 of facilityTPProfile—MFR resource

Port alarm suppressionThe OSS can change the port alarm suppression status for a managedFacilityTP using a standard 5620 CMIP set command. Table 34-2 describes the facilityTPProfile attribute settings that refer to port alarm suppression.

When alarm suppression is enabled, the OSS Interface Agent software prevents alarms from reaching the 5620 CMIP OSS Interface Gateway. The administrativeState, alarmStatus, and operationalState attributes continue to be updated regardless of the alarm suppression setting. The OSS is always able to get the current object status by querying these attributes.

If there is more than one OSS connected to the 5620 CORBA OSS Interface Gateway and the port alarm suppression settings are changed, either from the 5620 CMIP or from the 5620 NM interface, the change affects every linked OSS.

34.6 trmPhysicalInterface attribute

The trmPhysicalInterface attribute identifies the physical interface supported by the card or port type. Table 34-8 describes the supported interfaces.

Note — Port numbering for HD T1/E1 cards in Release 6.1 and later have been changed to accommodate MFR logical ports and MFR resource groups. Ports 1 to 16 are for T1/E1 ports, ports 17 to 24 are for MFR logical ports, ports 25 to 40 are for resource groups, and ports 41 to 48 are for MFR resource groups.

Port 16

Port 15

Port 14

Port 13

Port 12

Port 11

Port 10

Port 9

Port 8

Port 7

Port 6

Port 5

Port 4

Port 3

Port 2

Port 1

0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 0

Note — The currentProblemList attribute is not updated when port alarm suppression is enabled. Querying this attribute when port alarm suppression is enabled does not provide valid data.



Table 34-8 trmPhysicalInterface attribute values

Card or port type Attribute value Enumeration

27130 Frame Relay Resource Port X.21

27130 User Port X.21

3612 X.21 Narrow Aggregate

7470 MSP/7270 MSC PSI Frame Relay (V.11 interface only)

DTU 1121 (X.21)

DTU 2602 (X.21)

DTU 2602 ANM

DTU 2602 BERT

DTU 2702/2702 ANM (X.21)

DTU 2752/2752E (X.21)

DTU 2801 (X.21)

GSLC (X.21)

Multiport Aggregate Card

Single X.21 Primary Rate Card

X.21 DCC 4/6 Circuits

X.21 Direct Connect Module

X.21 Frame Relay Resource Port

X.21 Low Overhead Primary Rate Card

X.21 User Port

X.21 Virtual Channel Protocol Card

V.11 1

27130 User Port V.35

3612 V.35 Narrow Aggregate


3620 Ethernet Hub Router

3620 Ethernet Router

3620 Token Ring Router

DTU 1135 (V.35)

DTU 2603 (V.35)

DTU 2603 ANM

DTU 2603 BERT

DTU 2613 (V.35)

DTU 2703/2703 ANM (V.35)

DTU 2715–odd port (V.35)

DTU 2753/2753E (V.35)

DTU 2801 (V.35)

GSLC (V.35)

V.35 DCC 3/6 Circuits

V.35 Direct Connect Module

V.35 EDCM

V.35 Primary Rate Card

V.35 PSI Frame Relay

V.35 Virtual Channel Protocol Card

V.35 2

3624/3620 EM (4 wire transmit only)

36LG 12 port 4WTO

4WTO Channel Unit

X4WTO 3

(1 of 8)



3624/30/20 LGS, A-law, Type 2

3624/30/20 LGS, A-law, Type 3

3624/30/20 LGS, A-law, Type 6

3624/30/20 LGS, Mu-law, Type 1






LGS Channel Unit

LGS International, 8 ports, A-law

LGS NA6, 6 ports Mu-law

LGS North America, Mu-law

LGS UK, A-law

LGS UK10, 10 ports, A-law

LGS 4

LGE24 NA1

LGE24 NA2

LGE24 UK1

LGE24 UK2

LGE24 UK3

LGE Channel Unit

LGE International, 8 ports, A-law

LGE North America, 12 ports, Mu-law

LGE UK, 12 ports, A-law

LGE UK6, 6 ports, A-law

LGE NA6, 6 ports, Mu-law

LGE 5

3612 Manual Ring Down Module

3630 MRD A-law Card

MRD channel unit

MRD 6

DS0 Data Port Channel Unit

Office Channel Unit - Data Port

Office Channel Unit - Data Port v2

OCU-DP (TR-TSY-0083) 7

3624/30/20 EandM A-law Type 1



3624/30/20 EandM Mu-law Type 1

3624/30/20 EandM Mu-law Type 3

4WDX Channel Unit

EandM Channel Unit

EandM North America, Mu-law

EandM UK, A-law

EandM 8

GSLC (RS422) RS422 231

STM1 A2G card

OC3 A2G card

AAL1_AAL2 232

ECNT-C card

GigE card types

MPLS 233


(2 of 8)




V.28 234

AIR ATM card

AMD card

Fractional OC3/STM1 NIU

OC3 NT

Quad T1/E1 + single Ethernet NIU

Quad T1/E1 IMA

STM1 NT

T-ARIC card

Wireless 235

DDS Aggregate DDS 236

GSLC (RS530) RS530 237

27130 user port (V.36 interface only)

27130 FR resource port (V.36 interface only)

DTU 2801 (V.36, RS449)

V.36 238

36150 HSSI SMDS HSSI SMDS DXI 239

36150 T1 ATM CSU

36150 T3 Circuit Emulation

7300 ASAM (IMA module)

7470 MSP E1 ATM - 75 ohm

7470 MSP E1 ATM - 120 ohm

7470 MSP T1 ATM

8-port DS3 cell relay card

AICC-A

ASCC-AD

ASCC-AE

ASCC-E1

ASCC-PD

ASCC-PE

DS3-ATM

E1 ATM

E1/T1 MS (CR/IMA Module)

E3 ATM

E3 ATM UNI

OC3/STM1 MS (CR/IMA Module)

PAIC-A

T1-ATM

T3 ATM

T3 ATM PLCP

T3 ATM UNI

Unchannelized 240


(3 of 8)



1-Port OC12 I/O

1-Port OC48 I/O

1-Port STM4 I/O

1-Port STM16 I/O

4-Port OC3 I/O

4-Port STM1 I/O

8-Port OC3 I/O

AANC-A

ANT card (OC3 variant)

ANT card (STM1 variant)

ASCC-S1

MR48 OC/STM I/O

OC3

OC3 ATM Intermediate Range

OC3 ATM Long Range

OC3 ATM UNI Intermediate Range

OC3 ATM UNI Long Range

OC3 ATM UNI Short Range

OC3 Cell Relay

OC3 LT

OC12 Intermediate Range

OC12 Long Range

OC12 ATM MMF

OC12 Short Range

OC48 Short Range


OC192 Short Range


Quad OC3 ATM Intermediate Range

Quad OC3 ATM MMF

Quad OC3 ATM UTP

Quad OC3 SFP

Quad STM1 SFP

SANT-G (STM-1/OC-3 NT)

SALT-C (4 X STM-1/OC-3 LT on HCL)

SBNT-A (STM-4/OC-12 NT)

SBLT-A (STM-4/OC-12 LT)

SSDH STM-1

STM-1 ATM Intermediate Range

STM-1 ATM Long Range

STM-1 ATM MMF

STM-1 Cell Relay

STM-1 LT

STM-1 NT

STM-4 Intermediate Range

STM-4 Long Range

STM-4 Short Range

STM-16 Short Range

STM-16 Intermediate Range

SONET/SDH 241


(4 of 8)



LATM 100 (100 Mb/s multimode)


LATM 140 (140 Mb/s single mode)

LATM 140 (140 Mb/s single mode long reach)

OC3/STM1 LT card

TAXI 242

10/100 Base TX card

1000 Base FX/TX card

12-Port Line ISDN LT card

24-Port SHDSL LT card

27130 Network Port

48-port SDSL card

7470 MSP Service

7270 MSC Multiport Ethernet

7470 MSP SDSL

ADLT-J

ADLT-K

ADLT-L

ADLT-N

ADLT-O

ADLT-P

ADLT-Q

ADLT-R

ADLT-S

ADLT-T

ADSL port

ADSL-2

ADSL/8 Port

ADSL/16 Port

GSLC line card

EBLT-K

EBLT-L

ENET

Ethernet

RUEM LT

SDSL

SHLT-B

SMLT-A

SMLT-B

TALT-B

TALT-C

VSEM-A

XDSL

AAL5 243


(5 of 8)



36150 MPEG Composite Analog

36150 MPEG Composite Decoder

36150 MPEG Composite Encoder/Decoder

36150 MPEG Digital

7470 MSP DS3 CES

7270 MSC DS3 CCE

8-Port OC3 I/O

D1LT-B

D3LT-A

D3NT-A

D3NT-B

D3NT-C

E1LT-B

E1NT-C

E1 MS

E1 TDM

E3LT-A

E3LT-B

E3NT-B

E3NT-C

GELT-A

GENT-A

IPGW-A

JPEG

T1 MS

T1 TDM

Triple-port DS3 CCE-2

OC3/STM1 MS

VALT-A

AAL1 244

E1 ATM port

IMA port

TE1-IA

Unchannelized 244

DCP

DTU 1124 (RS232)

DTU 2601 (RS232)

DTU 2601 ANM

DTU 2601 BERT

DTU 2606 (RS232)

DTU 2608/2608 MS

DTU 2612 (RS232)

DTU 2701/2701 ANM (RS232)

DTU 2715–even port (V.24, RS232)

DTU 2751/2751E (RS232)

RS-422 DCC

RS-232 Direct Connect Module

RS-232 Sync/Async DCC

RS-232-C 246

3600 2B1Q Card T1-601 248


(6 of 8)



16-port TNT card (T1/E1)

16-port T1/E1 FR card

16-port T1/E1 card

1630 node

3600 Test Card

3612 SBRI DCM

3612 S/T BRI Aggregate Module

3-DS3 frame processing card

7470 MSP T1 Circuit Emulation, -75, and -120

7470 MSP DS3 Unchannelized Frame Relay

7470 MSP E3 Unchannelized Frame Relay

ANT card (DS3 variant)

ANT card (E3 variant)

CEPT2 and CEPT2 CRC

Channelized OE1

DACS II DDC and DPC

DACS II MMFG

DEX CS1L DC and DC3

DS1 FR port

DS3

DS3 FR port

Dual 1.544 Mb/s T1 and T1-2

Dual 2.048 Mb/s E1 and E1-2

E1 Channelized Frame Relay - 75 ohm

E1 Channelized Frame Relay - 120 ohm

E1 Unchannelized Frame Relay - 75 ohm

E1 Unchannelized Frame Relay - 120 ohm

E3 Slot on E3 Node

G.703 Codirectional DCM

GFC3 Card

HD T1 FR

HD E1 FR

HSSI FR

IDSL port

Single 1.544 Mb/s T1

Single 2.048 Mb/s E1

T1-CE

T1 Channelized Frame Relay

T1 SAM

T1 Unchannelized Frame Relay

T::DAX

T::DAX 100

Tributary E1 Card

Tributary T1 Card

TTC2M Card

TU-12 Mapper Card

VT-1.5 Mapper Card

G.703 balanced 250


(7 of 8)



34.7 cTPId attribute

The cTPId attribute uniquely identifies an instance of the managedFacilityTP object class. It has the format:

Nid_1 Sid_2 Cid_3 [,id_4] Did_5 [LEid_6]

where

id_1 is the parent node managedElement



id_4 is the subslot number (optional)


id_6 is the DS0 number for DS0s, the SRM number for MJUs, the FSC number for FSCs (1 to 62), and 1 for all other types of logical link endpoints (not present for other types of link endpoints)

28LC

7670 2.0 POS line card

custom port

custom card

DNIC3

DNIC6

DNIC12

DNIC24

DTU 2610

DTU 2614 (FRAD)

DTU 2704/2704 ANM (V.110)

HSMR LC

GFR Trunk

GSLC (V.36)

MDR node line port

MDR node RF port

Multi-Rate LC

OC48/STM16 LC

Other

X.22 Primary Rate Card

X.25

Unknown 255


(8 of 8)







35.5 groomedCircuitTPProfile attribute 35-5

35.6 trmDataMode attribute 35-9

35.7 trmFunctionalInterface attribute 35-11

35.8 trmVoiceMode attribute 35-18

35.9 tTPId attribute 35-21

35.10 listFreeVCIs and listUsedVCIs action 35-21



35.1 Introduction

The managedGroomedCircuitTP object models a path-end in the network. A managedGroomedCircuitTP specifies each end of a bMGroomedCircuit object. Some examples of valid endpoints are:

• data ports• voice ports• DS0s• MJUs• ATM line cards• ATM service cards

For TDM, the managedGroomedCircuitTP objects modeling DS0s are not instantiated by default. They are instantiated in the following cases:

• the DS0 serves as a terminating endpoint for a bMGroomedCircuit• the OSS explicitly creates the managedGroomedCircuitTP with an M-CREATE• an OSS performs a trace action on a bMGroomedCircuit object; intermediate

path-point DS0s are instantiated

The managedGroomedCircuitTP object class is a subclass of and allomorphs the BME bMGroomedCircuitTP object class. The managedGroomedCircuitTP object is contained by a managedElement object. It supports extra path endpoint configuration functionality not present in its parent object class. Table 35-2 describes the extra path endpoint configuration functionality, which is handled in the groomedCircuitTPProfile attribute.

Note — DS0s configured for subrate endpoints are not supported.

Note — With DS0 visibility default behavior, DS0 managedGroomedCircuitTP objects are only deleted when the OSS performs an explicit delete operation.




The managedGroomedCircuitTP object supports the following CMIP operations:

• create (on DS0 managedGroomedCircuitTP objects only)• delete (on DS0 managedGroomedCircuitTP objects only)• get• cancel get• set• action—trmAbort, trmLocalLoop, and trmGetStatus• action—listFreeVCIs

Use the listFreeVCIs action to generate a list of free VCIs — VCIs that do not have paths terminating on them — available for a selected VPI. See section 35.10 for more information.

• action—listUsedVCIsUse the listUsedVCIs action to generate a list of used VCIs — VCIs that have paths terminating on them — available for a selected VPI. See section 35.10 for more information.


The managedGroomedCircuitTP object can generate the following event notifications:


35.4 Attributes

Table 35-1 describes the attributes of the managedGroomedCircuitTP object.

Table 35-1 managedGroomedCircuitTP object attributes


administrativeState Indicates the managed status of the object

Read 0 = locked

1 = unlocked

Loopback is locked; otherwise always unlocked


Read Tied to operationalState— cleared or activeReportable-Indeterminate

(1 of 3)



allomorphs Allows the managedGroomedCircuitTP object to resemble one or more object classes

Read Always bMGroomedCircuitTP

currentProblemList Not used at this time Read Always an empty list

downstreamConnectivity Pointer


groomedCircuitTPProfile Holds path endpoint configuration information


nameBinding Identifies the kind of name binding used by a managedGroomedCircuitTP object

Read Name binding

objectClass Indicates the kind of object Read Always the OID for managedGroomedCircuitTP


The value of the operationalState attribute supersedes that of the usageState attribute; therefore, if operationalState = 0 and usageState = busy, the termination point is out of service, not busy

Read 0 = disabled

1 = enabled

packages Identifies the packages used by the managedGroomedCircuitTP object

Read List of packages; see the GDMO for details

supportedByObjectList Lists the supporting objects Read Distinguished name of supporting managedEquipment or managedPack object

trmDataMode Identifies the data characteristics of the managedGroomedCircuitTP

Read-write See section 35.6 for details

trmFunctionalInterface Identifies the protocol used by the managedGroomedCircuitTP object

Read See section 35.7 for details

trmVoiceMode Identifies the voice characteristics of the managedGroomedCircuitTP

Read-write See section 35.8 for details

tTPId Naming attribute; unique identifier for an instance of managedGroomedCircuitTP object class

Read String: N# S# C# [,#] D# PE#[ B#],#

See section 35.9 for details

typeText Provides the name of the managedGroomedCircuitTP object

Read A string that describes the 5620 NM selected object name, such as an OC3 or a DS0


(2 of 3)



The following subsections provide additional information for these attributes:

• groomedCircuitTPProfile• trmDataMode• trmFunctionalInterface• trmVoiceMode• tTPId

35.5 groomedCircuitTPProfile attribute

Table 35-2 lists the characteristics of groomedCircuitTPProfile.

upstreamConnectivity Pointer


usageState Describes whether or not a managed object is in use

The value of the operationalState attribute supersedes that of the usageState attribute; therefore, if 0 = operationalState and busy = usageState, the termination point is out of service, not busy.

The usageState for frame relay path endpoints will have the value busy if there is a frame relay path or link connected through it.

Read idle = no path connected (TDM only)

active = the physical port or ATM circuit is available (ATM only)

busy = a path is connected (TDM only)

userIdentifier Allows the OSS to assign a label to the path endpoint


String up to 254 characters which only the OSS can modify


userLabel Allows the OSS to assign a name to an object instance


String

The OSS or the 5620 NM operator can set this attribute.


(3 of 3)



Table 35-2 groomedCircuitTPProfile attribute characteristics



T1 timeslot Robbed Bit Signaling

1 1, 2 default = 1

1 = enabled

2 = disabled

Not valid for E1 connections

Inversion 2 1, 2 1 = enabled

2 = disabled

OCU-DP channel unit port Secondary Channel

3 0, 1 0 = unused

1 = used

Fault Signal 4 1, 2 1 = idle

2 = seized

4WTO channel unit port Sealing Current 5 1, 2 1 = disabled

2 = enabled

(1 of 4)



7470 MSP and 7270 MSC voiceband services cards

Trunk Conditioning

6 1, 2, 5 default = 1

1 = idle

2 = seized

5 = disabled

Trunk Conditioning Code 1

7 0x0 to 0xf default = 0x0 for T1 and 0xd for E1

Applied for the duration of the failure if Trunk Conditioning is Idle

Applied for 2.5 s if Trunk Conditioning is seized

Not valid if Trunk Conditioning is disabled

Trunk Conditioning Code 2

8 0x0 to 0xf default = 0x0 for T1 and 0xd for E1

Valid only when Trunk Conditioning is seized

Applied for 2.5 seconds after the onset of the failure and continued for the duration of the failure

Trunk Conditioning Data

9 26, 127 or 213, 255

default = 127 or 213

26 = MUX-OOS

127 = idle (T1 only)

213 = idle (E1 only)

255 = user-defined

Not valid when Trunk Conditioning is disabled

Trunk Conditioning Data Value

10 0x00 to 0xff default = 0xff

Valid only when Trunk Conditioning Data is user-defined

Ingress Gain 11 –16 to 16 default = 0

Value in dB

Not applicable when the channel is configured for clear channel

Egress Gain 12 –16 to 16 default = 0

Value in dB

Not applicable when the channel is configured for clear channel

DS0 unit Signaling Information

13 See Table 35-6

See Table 35-6

FENT-A ports System Mode 14 1, 2 1 = CrossConnect (default)

2 = Residential Bridge

When configured in CrossConnect mode, a VLAN can only belong to 1 PVC. One PVC can belong to 1 or multiple VLANs depending on the tagging mode of the virtual ATM port. If the virtual ATM port is untagged, there is 1 PVC to 1 VLAN. If the virtual ATM port is tagged, there is 1 PVC to n VLANs.



(2 of 4)



FENT-A ports Port Tagging Mode

15 1, 2 1 = Tagged (default)

2 = Mixed

When the port is set to 1, the port belongs to n VLANs and the port only sends and accepts VLAN tagged frames.

When the port is set to 2, the port belongs to many VLANs and sends and accepts untagged, priority tagged, and VLAN tagged frames. Frames belonging to VLAN 4096 are not sent.

7270 MSC, 7470 MSP, and 7670 ESE ports

Characteristic CBR shaping direction


2 = egress

3 = ingress

4 = bi-directional

Characteristic rt-VBR shaping direction


2 = egress

3 = ingress

4 = bi-directional

Characteristic nrt-VBR shaping direction


2 = egress

3 = ingress

4 = bi-directional

Characteristic UBR shaping direction


2 = egress

3 = ingress

4 = bi-directional

VCC

VPC

Port Type/ Resource Type

20 4 to 6 4 = UNI (default)

5 = B_ICI

6 = B_ISSI

Read-only for:

• CR port/IMA resource in the OC3/STM1 MS card, before Release 5.0

• T1/E1 CR card, before Release 5.0.

Read-only when:

• There are connections on the IMA group.

• The CR port is assigned to the IMA group.

• There are connections on the CR port.

• DS1 CR channels and IMA resources are on the ESC OC3 I/O.

7270 MSC, 7470 MSP, 7670 ESE, and 7670 RSP ports

AESA information

21 string A fixed format string with 47 characters. Each character can be 0 to 9, a to f, -, or A to F. (1)



(3 of 4)



Notes(1) An AESA value identifies the logical endpoint of an SPVC path. Each character represents a hex nibble. To calculate the

AESA for a physical endpoint, use the following definition:AAA-AAAA-AAAAAAAAAAAAAAAAAAAA-BBBBBB-CCCC-DD-EE where:A= The Internal Switch Subscriber prefix for the node (26 characters)B= The OUI C= Shelf and slot informationD= Port numberE= Contains either the DS0 channel number (for CE cards) or is 0 for all other card types.

(2) The Profile Type is derived from different multiplexer profile ID ranges:Profile ID Range Profile Type1-20, 101-160 1 1001-1020, 1101-1120 22001-2020, 2101-2238 33001-3300 4

35.6 trmDataMode attribute

The trmDataMode attribute identifies whether a data path-end object operates in the synchronous or asynchronous device mode. If the trmDataMode attribute is set to sync or async, the 5620 CMIP sets the trmVoiceMode attribute to null.

If the managedGroomedCircuitTP object is a voice circuit, the trmDataMode attribute is set to null.

Figure 35-1 shows the trmDataMode attribute, which has components for bandwidth, asynchronous and synchronous parameters.

Profile Type (2) Read 22 0 to 4 default = 1

0 = none

1 = node predefined

2 = node user

3 = NMS predefined

4 = NMS user

Multiplexer Profile ID Read-write 23 1 to 20

101 to 160

1001 to 1020

2001 to 2020

2101 to 2238

3001 to 3300

default = 1 for AAL1

default = 5 for AAL2

Identifies the type of profile for the multiplexer

Multiplexer type Read-write 24 1, 2 default = 2

1 = AAL1

2 = AAL2

Maximum total channels Read-write 25 1 to 248 default = 1

Limits the number of channels that can be assigned to the multiplexer. If cpType 24 is set to 1, this characteristic becomes is set to 1 and cannot be changed.



(4 of 4)



Figure 35-1 Bandwidth components for trmDataMode attribute

Table 35-3 describes the trmDataMode attribute parameters.

Table 35-3 trmDataMode attribute parameters

9085

dataFormat.

rate

rate

digitalBandwidthValue

rate

analogBandwidthValue

unknownBandwidthValue

incoming

outgoing

format

async

characterSize

sync

parity

stopbits

frameFormat.

characterSet

notApplicable

digitalBandwidthValue (real kbps)

analogBandwidthValue (real KHz)


digitalBandwidthValue (real kbps)

analogBandwidthValue (real KHz)


Attribute component Modifiable by OSS Value description

digitalBandwidthValue yes Maximum value is 231-1

analogueBandwidthValue

analogueBandwidthValue (real KHz)

digitalBandwidthValue (real kb/s)


no Not used

characterSize yes 0 = unspecified

5 = five

6 = six

7 = seven

8 = eight

9 = nine

(1 of 2)



35.7 trmFunctionalInterface attribute

The trmFunctionalInterface attribute identifies the protocol used by the managedGroomedCircuitTP object. Table 35-4 shows the protocol, which depends on the card or port type.

parity yes 0 = odd

1 = even

2 = mark

3 = space

4 = none

stopbits yes 0 = x1

2 = x2

frameFormat no 0 = unspecified

characterSet no 0 = unspecified

notApplicable no Voice ports and DS0s

Attribute component Modifiable by OSS Value description

(2 of 2)



Table 35-4 trmFunctionalInterface attribute values

Card or port type Attribute value description Enumeration

3-DS3 frame processing card


16-port T1/E1 FR card

16-port T1/E1 card

27130 Frame Relay Resource Port

27130 User Port V.35

27130 User Port X.21

3600 Test

3612 SBRI DCM

3612 S/T BRI Aggregate Module

7470 MSP DS3 Unchannelized Frame Relay

7470 MSP E3 Unchannelized Frame Relay

7470 MSP/7270 MSC PSI Frame Relay (V.11, V.28 and V.35 interfaces)

7470 MSP T1 Circuit Emulation

7470 MSP T1 Circuit Emulation-75

7470 MSP T1 Circuit Emulation-120

1630

CEPT2

CEPT2 CRC

Channelized OE1

DACS II DDC

DACS II DPC

DACS II MMFG

DEX CS1L DC

DEX CS1L DC3

DS0

DS1 FR port

DS3 FR port

Dual 1.544 Mb/s T1

Dual 1.544 Mb/s T1-2

Dual 2.048 Mb/s E1

Dual 2.048 Mb/s E1-2

E1 Aggregate

E1 Channelized Frame Relay-120 ohm

E1 Channelized Frame Relay-75 ohm

E1 Unchannelized Frame Relay-120 ohm

E1 Unchannelized Frame Relay-75 ohm

Frame stream circuit

G.703 Codirectional DCM

GFC3 Card

HD T1 FR

HD E1 FR

HSSI FR

IDSL port

Single 1.544 Mb/s T1

Single 2.048 Mb/s E1

G703_G704 2

(1 of 7)



SSDH OC-3

SSDH STM-1

T::DAX

T::DAX 100

T1 Channelized Frame Relay

T1 SAM

T1 Unchannelized Frame Relay

Tributary T1

Tributary E1

TTC2M

TU-12 Mapper

VT-1.5 Mapper

V.35 Frame Relay Resource Port

V.35 User Port

X.21 Frame Relay Resource Port

X.21 User Port

G703_G704 2

AIR ATM card

AMD card

OC3 NT

Fractional OC3/STM1 NIU

STM1 NT

Quad T1/E1 + single ethernet NIU

Quad T1/E1 IMA

T-ARIC

LMDS 244

DDS Aggregate DDS 245

X.25 Access Application X.25 246

X.25 Gateway Application X.25 Gateway 247

X.75 Gateway Application X.75 Gateway 248

GFR Trunk GFR Trunk 249


(2 of 7)



1-Port OC12 I/O

1-Port OC48 I/O

1-Port STM4 I/O

1-Port STM16 I/O

27130 Network Port

36150 T1 ATM CSU

4-Port OC3 I/O

4-Port STM1 I/O

48-port SDSL card

7270 MSC Multiport Ethernet

7470 MSP ADSL/8 Port

7470 MSP ADSL/16 Port

7470 MSP T1 ATM

7470 MSP E1 ATM-75 ohm

7470 MSP E1 ATM-120 ohm

7470 MSP SDSL

7470 MSP STM4 Short Range

7470 MSP STM4 Intermediate Range

7470 MSP STM4 Long Range

ADLT-J

ADLT-K

ADLT-L

ADLT-LP

ADLT-N

ADLT-O

ADLT-P

ADLT-Q

ADLT-R

ADLT-S

ADLT-T

ADSL

ADSL-2

DS3-ATM

E1 ATM

IMA

LTAC-A

LTAC-B

LTAC-C

LTAC-D

LTAC-D2

LTAC-F

LTSC-A

OC3

PAIC-A

SHDSL

T1-ATM

T1-CE

XDSL

ATM

CE_IF_FX_ATM

250


(3 of 7)



12-Port Line ISDN LT card

24-Port SHDSL LT card

8-port DS3 Cell Relay

8-port OC3 I/O

AICC-A

ANT card (OC3 variant)

ANT card (STM1 variant)

ANT card (DS3 variant)

ANT card (E3 variant)

ASCC-AD, ASCC-AE, ASCC-E1, ASCC-PD, ASCC-PE

E1 ATM

E3 ATM

E3 ATM UNI

FENT-A

GSLC line card



LATM 140 (140 Mb/s single mode)

LATM 140 (140 Mb/s single mode long reach)

MR48 OC/STM

OC3

OC3 ATM Intermediate Range

OC3 ATM Long Range

OC3 ATM UNI Intermediate Range

OC3 ATM UNI Long Range

OC3 ATM UNI Short Range

OC3 Cell Relay

OC3 LT

OC12 Short Range


OC12 Long Range

OC12 MMF

Quad OC3 ATM MMF

Quad OC3 ATM Intermediate Range

Quad OC3 ATM UTP

Quad OC3 SFP

Quad STM1 SFP

RUEM LT

SANT-G, SALT-C, SBNT-A, SBLT-A

SHLT-B

SMLT-A

SMLT-B

STM-1 ATM MMF

STM-1 ATM Intermediate Range

STM-1 ATM Long Range

STM-1 Cell Relay

STM-1 LT

STM-1 NT

T3 ATM

ATM 250


(4 of 7)



36150 MPEG Composite Analog

36150 MPEG Composite Decoder

36150 MPEG Composite Encoder/Decoder

36150 MPEG Digital

7270 MSC DS3 CCE

7470 MSP DS3 CES

7470 MSP/7270 MSC Voiceband Services

8-Port OC3 I/O

D1LT-B

D3LT-A

DS3

D3NT-A

D3NT-B

D3NT-C

E1LT-B

E1 MS

E1 MS (CR/IMA Module)

E1NT-C

E1 TDM

E3LT-A

E3LT-B

E3NT-B

E3NT-C

Ethernet

GELT-A

GENT-A

IPGW-A

JPEG

T1 MS

T1 MS (CR/IMA Module)

T1 TDM

Triple-port DS3 CCE-2

VSC

OC3/STM1 MS

OC3/STM1 A2G

VALT-A

ATM AAL 251

DS0 Data Port Channel Unit

Office Channel Unit-Data Port

Office Channel Unit-Data Port v2

OCU DP (TR-TSY-0077) 252


(5 of 7)



3612 V.35 Narrow Aggregate

3620 Ethernet Hub Router

3620 Ethernet Router

3620 Token Ring Router

DCP

DTU 1121 (X.21)

DTU 1124 (RS232)

DTU 1135 (V.35)

DTU 2601 (RS232)

DTU 2601 ANM

DTU 2601 BERT

DTU 2602 (X.21)

DTU 2602 ANM

DTU 2602 BERT

DTU 2603 (V.35)

DTU 2603 ANM

DTU 2603 BERT

DTU 2606 (RS232)

DTU 2608/2608 MS

DTU 2612 (RS232)

DTU 2613 (V.35)

DTU 2701/2701 ANM (RS232)

DTU 2702/2702 ANM (X.21)

DTU 2703/2703 ANM (V.35)

DTU 2715–odd port (V.35)

DTU 2715–even port (V.24, RS232)

DTU 2751/2751E (RS232)

DTU 2752/2752E (X.21)

DTU 2753/2753E (V.35)

DTU 2801 (V.35 and X.21)

GSLC (V.35)

GSLC (RS422)

GSLC (RS530)

RS-232 Direct Connect Module

RS-232 Sync/Async DCC

Single V.35 PRI

V.35 DCC 3/6 circuits

V.35 Direct Connect Module

V.35 EDCM

V.35 Virtual Channel Protocol

V.24 253

3612 X.21 Narrow Aggregate

GSLC (X.21)

X.21 DCC 4/6 circuits

X.21 Direct Connect Module

X.21 Low Overhead Primary Rate

X.21 Primary Rate

X.21 Virtual Channel Protocol

X.24 254


(6 of 7)



35.8 trmVoiceMode attribute

The trmVoiceMode attribute identifies whether a voice path-end object operates as a digital or analog circuit.

If the managedGroomedCircuitTP object is a data circuit, the 5620 CMIP sets the trmVoiceMode attribute to null.

Figure 35-2 shows the trmVoiceMode attribute, which has components for voice transmission parameters set by the 5620 CMIP.

10/100 Base TX card

1000 Base FX/TX card

27130 user port (V.36 interface only)

27130 FR resource port (V.36 interface only)

DTU 2610

DTU 2614 (FRAD)

DTU 2704/2704 ANM (V.110)

DTU 2801 (V.36, RS449)

GigE card types

GSLC (V.36)

Quad T1/E1 IMA card

Unknown 255

7670 2.0 POS line card

HSMR LC

MDR node line port

MDR node RF port

Other

— null


(7 of 7)



Figure 35-2 Voice transmission parameter components for trmVoiceMode attribute

Table 35-5 describes the trmVoiceMode attribute parameters.

Table 35-5 trmVoiceMode attribute parameters

voiceMode

companding

minVariation

minVariation

channelAssociation

txLevel

digital

encoding

notApplicable

echoCancellation

voiceCompression

mode

analog

connection

signalling

rxLevel

nominal

maxValue

minValue

nominal

maxValue

minValue

9086

Attribute component Description

compounding notApplicable, g711mulaw, g711Alaw

echoCancellation Configurable in NMTI only

Specified for each endpoint by using the bMGroomedCircuit tDMProfile attribute.

voiceCompression unspecified

x8k

x16k

x32k

x64k

You can specify voice compression on path set up as per echoCancellation

Specified for each endpoint by using the bMGroomedCircuit tDMProfile attribute.

analog Voice ports

(1 of 2)



Table 35-6 provides the voice signaling types for the signaling component described in Table 35-5.

Table 35-6 Voice signaling types

connection x2wire or x4wire; you must set connection for the card, not for the individual ports.

signaling Set on path setup in bMGroomedCircuit tDMProfile; specifies signaling type used; set on path setup in bMGroomedCircuit circuitProfile, where the DS0 signaling is also specified

rxLevel nominal Receive gain value

rxLevel maxValue Receive maximum gain

rxLevel minValue Receive minimum gain

rxLevel minVariation Receive gain variation

txLevel nominal Transmit gain value

txLevel maxValue Transmit maximum gain

txLevel minValue Transmit minimum gain

txLevel minVariation Transmit gain variation

digital encoding Not used

digital channelAssociation Not used

notApplicable Data ports, DS0s

Attribute component Description

(2 of 2)

Type of voice signaling Description Enumeration

4WTO 4-Wires Transmit Only voice channel unit 1

eMI EandM Type 1 (signaling or no signaling) 3

eMII EandM Type 2 4

eMIII EandM Type 3 5

eMIV EandM Type 4 6

eMV EandM Type 5 7

LGSMRD Manual Ring Down 22

LGEDPT LGE Dial Pulse Terminate 236

LGELCDC LGE Loop Calling Disconnect Clear 237

LGSLCDC LGS Loop Calling Disconnect Clear 238

LGEEC LGE Earth Calling 239

LGSEC LGS Earth Calling 240

LGSPLAR LGS Private Line Automatic Ring 241

LGSCBW LGS Central Battery Working 242

LGEGS LGE Ground Start 243

(1 of 2)



35.9 tTPId attribute

The tTPId attribute uniquely identifies an instance of the managedGroomedCircuit object class. It has the format:

Nid_1 Sid_2 Cid_3 [,id_4] Did_5 PEid_6[ Bid_7], id_8

where

id_1 is the parent node managedElement



id_4is the sub-slot number (optional)


id_6 is the DS0 number for DS0s, the SRM number for MJUs and 1 for others

id_7 is used only for MJUs and gives the branch number (optional)

id_8 gives the circuit direction; it is always 2 (outgoing) for DS0s and MJUs and 1 (incoming) for others

35.10 listFreeVCIs and listUsedVCIs action

Table 35-7 describes the characteristics of the listFreeVCIs and listUsedVCIs action parameters . The OID for these actions are 1.2.124.113537.1.3.23 for the listFreeVCIs action and 1.2.124.113537.1.3.24 for the listUsedVCIs action.

LGSGS LGS Ground Start 244

LGSGSEM LGS Ground Start EandM 245

LGSLSEM LGS Loop Start EandM 246

LGELS LGE Loop Start 247

LGSLS LGS Loop Start 248

LGERE LGE Remote Extension 249

LGSRE LGS Remote Extension 250

LGEINTL1 LGE International 1 251

LGSINTL1 LGS International 1 252

BYPASSNOSIG No signaling (for CEPT and T1 timeslots) 253

BYPASSSIG Signaling (for CEPT and T1 timeslots) 254

Unknown Unknown 255

Type of voice signaling Description Enumeration

(2 of 2)



Table 35-7 listFreeVCIs and listUsedVCIs action parameters

Table 35-8 lists the results for the actions.

Table 35-8 listFreeVCIs and listUsedVCIs results

Note — Use as small a range of VCIs as possible, to ensure that the action does not take a long time.

Action parameter Description Access Value description

targetVPI The target VPI on the selected managedGroomedCircuitTP object

Read number to indicate the target VPI to search

searchRangeMinVCI The lowest VCI number from which you want to start searching

Read number to indicate the lowest VCI number to start searching from

For example, 0 to 100 for the minimum and maximum value would search from VCI 0 to VCI 100.

Use a valid range to return correct results

searchRangeMaxVCI The highest VCI number at which you want to stop searching

Read number to indicate the highest VCI number to stop searching

For example, 0 to 100 for the minimum and maximum value would search from VCI 0 to VCI 100.

Use a valid range to return correct results

Characteristic Description

searchRangeMinVCI The lowest VCI number from which you started the search.

searchRangeMaxVCI The highest VCI number at which you stopped the search.

listOfVCIs An array of numbers, ordered from lowest to highest, of the VCIs available or used VCIs within the range specified.







36.5 packProfile attribute 36-4

36.6 Programmed versus installed card type 36-10

36.7 Port and resource numbering for SDSL cards 36-11

36.8 Port and resource numbering for OC3 MS and STM1 MS cards 36-13

36.9 listFreeManagedGroomedCircuitTPs and listUsedManagedGroomedCircuitTPs actions 36-18



36.1 Introduction

The managedPack object models a card, power supply, or fan. It is contained by an equipmentHolder object.

The managedPack object class is a subclass of and allomorphs the M.3100 circuitPack object class. It supports extra configuration functionality not present in its parent object class. The extra configuration is handled in the packProfile attribute, which holds various card configuration profiles. See Table 36-2 for information about the packProfile attribute.

See Appendix A for a list of the available card types.


The managedPack object supports the following CMIP operations:

• get• cancel get• set• action—listFreeManagedGroomedCircuitTPs

Use the listFreeManagedGroomedCircuitTPs action to generate a list of full distiguishedNames for managedGroomedCircuitTP objects that do not have any bMGroomedCircuit objects terminating on them. See section 36.9 for more information.

• action—listUsedManagedGroomedCircuitTPsUse the listUsedManagedGroomedCircuitTPs action to generate a list of full distinguishedNames for managedGroomedCircuitTP objects that have any bMGroomedCircuit objects terminating on them. See section 36.9 for more information.


The managedPack object can generate the following CMIP event notifications:

• attributeValueChange• equipmentAlarm• objectCreation• objectDeletion

36.4 Attributes

Table 36-1 describes the attributes of the managedPack object.

Note — The managedPack object also models shelf module equipment on the 7670 RSP ESE node. See Table 27-2 for more information.



Table 36-1 managedPack object attributes


administrativeState Reflects the availability of an object as imposed through management services

Read Always 1 = unlocked

affectedObjectList Is a list of affected path ends; not present for power supplies and fans

Read List of distinguishedNames (can be empty; for example, null for cards with no endpoints)

alarmSeverity AssignmentProfilePointer



Read Tied to operationalState (cleared or activeReportable- Indeterminate)

allomorphs Allows managedPack object to resemble one or more object classes

Read Allomorphs circuitPack

availabilityStatus Qualifies the operational state of the managedPack object

Read Either notInstalled or empty set

circuitPackType Is the programmed card type Read String describing the programmed card type

See Table 36-3

currentProblemList Not used at this time Read Always empty

equipmentId (1) Naming attribute; a unique identifier for an instance of a managedPack object

Read Integer 5620 NM card id or power supply id

Always 1 for fans

locationName Allows the OSS to specify a location label for the equipment

Read-write default = null

String with a buffer size is 255 bytes

Not present for power supplies and fans

nameBinding Identifies the kind of name binding used by a managedPack object

Read Name binding

objectClass Is the kind of object Read Always the OID for managedPack


Read 0 = disabled

1 = enabled

packages Identifies the packages used by the managedPack object


packProfile Is a multivalued attribute that provides 5620 NM-specific circuitPack configuration and support

See Table 36-2


replaceable Indicates replaceability of managedPack object instance

Read Always yes

serialNumber Represents the serial number of the card plug-in unit

Read A string up to 16 characters

e.g. BJN993212345

(1 of 2)



Note(1) For 7470 MSP single and dual peripheral shelves, the 5620 CMIP maps 5620 NM GUI card ids with an offset of 1. In the

5620 NM database and 5620 CMIP MIB, card id 1 identifies Hub X on a 7470 MSP. Card slot 1 on the 5620 NM GUI is card id 2 in the 5620 NM database. For the 5620 CMIP, 7470 MSP Hub X (P1-HX) = id 1, slot 1 (P1-1) = id 2......slot 12 (P1-12) = id 13, Hub Y (P1-HY) = id 14.

The following sections provide additional information for:

• packProfile attribute• programmed versus installed card type

36.5 packProfile attribute

The packProfile attribute can be used to manage various card-specific configuration values.

Table 36-2 describes the packProfile attribute of the managedPack object class.

Table 36-2 packProfile attribute characteristics

supportedByObjectList

Identifies object instances capable of affecting a managedPack object instance

Read A shelf

version Indicates card generic Read String-card generic or null


(2 of 2)

Card Configuration parameter

Access ppType ppValue Description

Configuring wire audio cards

EandM Wire Audio Read-write 1 1, 2 1 = cards configured as 4 wire

2 = cards configured as 2 wire

Configuring 1+1 and 1:N card protection on the 7470 MSP and 7670 ESE

8-port OC3 I/O

CC2G

ESC

E3CCE-2

OC-N

MR48 line card

STM-N

1+1 working card

1+1 protection card

Read 2 1, 2 1 = working card

2 = protection card

The slot pairs used for 1+1 redundancy are slots 1 and 2, 3 and 4, 5 and 6, and so on. The odd card in the pair is the working card.

(1 of 6)



DS3 CCE (DS3 CES)

E1 CE

E1 MS (and CRIMA)

E3 CCE, T1 MS (and CRIMA)

OC3 MS (and CRIMA)

STM1 MS (and CRIMA)

T1 CE

1:N working card

1:N protection card

N can be in range from 1 to 11.

Read 2 3, 4 3 = working card

4 = protection card

E3CCE-2

MR48 line card

OC-N

STM-N

1+1 mate card slot

Read 3 Slot number of mate card

The slot pairs used for 1+1 redundancy are slots 1 and 2, 3 and 4, 5 and 6, and so on. The odd card in the pair will be the working card.

The working card contains a pointer to the protection card that is guarding it.

DS3 CCE (DS3 CES)

E1 CE

E3 CCE

T1 CE

1:N card slot of the protecting card

The slot number of mate card is not valid for 1:N protection cards.

Read 3 Slot number of protection card

The protection card does not contain a pointer to the cards it is protecting.

Support for APS on the 7670 RSP



(2 of 6)



8-port OC3 I/O

DS3 CCE

E3 CCE

OC-N

STM-N

Switching mechanism

Read 4 0, 1 0 = nonrevertive (default)

1 = revertive

Valid only for 1:N protection card

WTR timer Read 5 0 to 60 default = 5

Valid only for 1:N protection card when the switching mechanism is revertive

Switching direction

Read 6 0, 1 0 = unidirectional

1 = bidirectional

Valid only for 1:N protection card

Protection group status

Read 7 1 to 5 1 = up

2 = down

3 = testing

4 = unknown

5 = dormant

Protected by Read 8 n n = slot number of the card, which is protecting this card; valid only for 1:N APS and only for the working card

Working cards Read 9 n n = 32 bit bitmask; each bit corresponds to the slot number. It is switched on if the card in that slot is a working card and belongs to the same protection group as this card.

Valid for both 1:N and protection cards.

Support for 7470 MSP, 7670 ESE, and 7670 RSP cards

1-port OC12

1-port OC48

1-port STM4

1-port STM16

1-port OC3 MS

1-port STM1 MS

1-port OC3 A2G

1-port STM A2G

10/100 Base TX

4-port OC3

4-port STM1

8-port OC3 I/O

Control card

GigE

MR48 OC/STM

Quad OC3/STM1 CR

Smart Trunk

Card reach/variant

Read 10 0 to 5, 8 to 10

0 = no subtype

1 = short reach (default)

2 = intermediate reach

3 = long reach

4 = extra long reach

5 = electrical reach

8 = short wavelength

9 = long wavelength

10 = long haul

11 = small form factor (SFP) pluggable

Support for the 7390 DBS cards



(3 of 6)




TNT card mode Read-write 11 1, 2 default = 1

1 = HDB3 mode

2 = ATM mode

Support for 7670 ESE MS cards

OC3/STM1 MS Service option Read 12 1 default = 2

2 = CE

This ppType gives the service option of the OC3/STM1 card.

Support for card version number

DS3-1, E3-1

OC3, STM1

OC12, STM4

T1ATM, E1ATM

Card version number


1 = OC3-1, STM1-1, DS3-1, E3-1, OC12-1, STM4-1, T1ATM-1, E1ATM-1

2 = OC3-2, STM1-2, DS3-2, E3-2, OC12-2, STM4-2, T1ATM-2, E1ATM-2

3 = OC3-2M, STM1-2M

Support for 7300 ASAM cards

All 7300 ASAM cards

Card Engineering Part Number

Read 14 String 12 characters

For example, 3CC11656AAAA

7300 ASAM LT cards

BusInfo Read 15 0, 1 1 = HCL bus

2 = IQ bus

Support for CR/IMA modules

OC3, STM1

E1, T1 MS

Module type Read 16 1, 44 1 = no module

44 = CR/IMA module

Support for 3-DS3 frame processing card on the 7470 MSP and 7670 ESE

3-DS3 frame processing

Severe Congestion Threshold

Read-write 19 1 to 100 Default = 80%

When the congestion level reaches the default value, there is severe congestion. The Severe Congestion Threshold value must be greater than the Mild Congestion Threshold value.

Mild Congestion Threshold

Read-write 20 0 to 100 Default = 50%

When the congestion level reaches the default value, there is mild congestion. The Mild Congestion Threshold value must be less than the Severe Congestion Threshold value.

Configuring custom attributes



(4 of 6)



All cards customAttributeValue1

Read-write 10001 string Where string is up to 254 characters, and contains custom information that is associated with the managedPack object.
















(5 of 6)




















(6 of 6)



36.6 Programmed versus installed card type

Table 36-3 compares programmed versus installed card type modeling. The left side of the table shows the 5620 NM state and indicates whether the card is programmed or installed. The right side of the table shows the 5620 CMIP objects and attributes that correspond to each state.



Table 36-3 Programmed versus installed card type modeling

Notes(1) This string describes the installed card. See Table App A-1 for a list of card types.(2) This string describes the programmed card type. See Table App A-1 for a list of card types.

Note — The installed and programmed card types must match for the card to be operational. See Table App A-1 for a list of card types.

5620 NM state 5620 CMIP

equipmentHolder managedPack

Programmed Installed Match (GUI status)

holderStatus

acceptableCircuitPackTypeList

circuitPackType

operationalState

N N NA (red) This state cannot occur in the 5620 CMIP.


N Y NA (red) This state cannot occur in the 5620 CMIP.


Y N NA (red) notInThe AcceptedList card string (1)

for example Null Card

card string (2)

for example STM1

card string (2)

for example STM1

disabled

Y Y N (red) notInThe AcceptedList card string (1)

for example LGS

card string (2)

for example OC3

card string (2)

for example OC3

disabled

Y Y Y (green) inThe AcceptedList card string (1)

for example EandM

card string (2)

for example EandM

card string (2)

for example EandM

enabled



36.7 Port and resource numbering for SDSL cards

Resources that connect to SDSL cards follow specific device numbering sequences. Device numbers are required when you create frame relay links, frame relay paths, or ATM VCC paths on SDSL cards.

Figure 36-1 illustrates how a sample NTU connects to an SDSL card and how 5620 CMIP managed objects map onto the connection.

Figure 36-1 NTU connection to an SDSL card

Port and resource numbering sequences for an SDSL 16-port cardFigure 36-2 illustrates the port and resource numbering sequences for an SDSL 16-port card. Numbering sequences begin at port 1. The SDSL port numbering sequence is 1, 9, 17, 25...121. The network port numbering sequence is 2, 10, 18, 26...122. The user port numbering sequence is 3, 11, 19, 27...123. The resource port numbering sequence is 4, 12, 20, 28...124.

SDSL port 1

SDSL port 2

SDSL port 16

15447

Networkport

managedEquipmentobject

managedFacilityTPobject

managedGroomedCircuitTPobject

Userport

27130 NTU

managedFacilityTPobject

(contains NTU type cpType)

managedGroomedCircuitTPobject



Figure 36-2 Port and resource numbering sequences for an SDSL 16-port card

Port and resource numbering sequences for an SDSL 48-port cardFigure 36-3 illustrates the port and resource numbering sequences for an SDSL 48-port card. Numbering sequences begin at port 1. The SDSL port numbering sequence is 1, 5, 9, 13...189. The network port numbering sequence is 2, 6, 10, 14...190. The user port numbering sequence is 3, 7, 11, 15...191. The resource port numbering sequence is 4, 8, 12, 16...192.

Networkport

(2)

Networkport

(10)

SDSLport

(1)

SDSLport

(9)

Networkport

(18)

SDSLport

(17)

User port

(3)

Resource port

(4)

User port

(11)

Resource port

(12)

User port

(19)

Resource port

(20)

15446

SDSL ports NTU ports



Figure 36-3 Port and resource numbering sequences for an SDSL 48-port card

36.8 Port and resource numbering for OC3 MS and STM1 MS cards

This section lists the port and resource numbering sequences for OC3 MS and STM1 MS cards.

Port and resource numbering for OC3 MS cardsTables 36-4 and 36-5 list the port and resource numbering sequences for OC3 MS cards.

Table 36-4 managedFacilityTP object Ids and managedGroomedCircuit object Ids for OC3 MS cards

Networkport

(2)

Networkport

(6)

SDSLport

(1)

SDSLport

(5)

Networkport

(10)

SDSLport

(9)

User port

(3)

Resource port

(4)

User port

(7)

Resource port

(8)

User port

(11)

Resource port

(12)

15445

SDSL ports NTU ports

Port type managedFacilityTP object Id (cTPId) (1) managedGroomedCircuit object Id (tTPId) (1)

DS3 Nx Sy Cz D1

Nx Sy Cz D2

Nx Sy Cz D3

Nx Sy Cz D1 PE1,1

Nx Sy Cz D2 PE1,1

Nx Sy Cz D3 PE1,1

DS1 Nx Sy Cz D4

..................

..................

Nx Sy Cz D87

Nx Sy Cz D4 PE1,1

..................

..................

Nx Sy Cz D87 PE1,1

OC3 MS Nx Sy Cz D88 Nx Sy Cz D88 PE1,1



Note(1) x is the node id; y is the shelf id; z is the card id

Table 36-5 managedEquipment object Ids for OC3 MS cards


Figure 36-4 illustrates the 5620 CMIP modeling of an STS-1 configuration on an OC3 MS card.

Resource managedEquipment object Id (1)

5620 NM first-level resources

First STS1 Nx Sy Cz 2

Second STS1 Nx Sy Cz 3

Third STS1 Nx Sy Cz 4

5620 NM second-level resources for first STS1 VT group managedEquipment object Ids

VT Group 1 Nx Sy Cz 5







5620 NM second-level resources for second STS1 VT group managedEquipment object Id








5620 NM second-level resources for third STS1 VT group managedEquipment object Id










Figure 36-4 5620 CMIP modeling of an STS-1 configuration on an OC3 MS card

Port and resource numbering for STM1 MS cardsTables 36-6 and 36-7 list the port and resource numbering sequences for STM1 MS cards.

DS3

Port 1

STS1

managedEquipment

16520

managedEquipment

managedEquipment

managedFacilityTPmanagedGroomedCircuitTP

managedFacilityTPmanagedGroomedCircuitTP

VT Group

1

1T1 VT1.5

1 2 3

Names:1. STS-1 BulkPayload2. STS-1 VTGs3. STS-1 VTGs

Resource Names (T1 Port):1. T1Port2.3.4.

OC3SRMS

Port 1

2

7

2 3 4



Table 36-6 managedFacilityTP object Ids and managedGroomedCircuit object Ids for STM1 MS cards


Table 36-7 managedEquipment object Ids for STM1 MS cards

Port type managedFacilityTP object Id (cTPId) (1) managedGroomedCircuit object Id (tTPId) (1)

STM1 MS Nx Sy Cz D1 Nx Sy Cz D1 PE1,1

E1 Nx Sy Cz D2

..................

..................

Nx Sy Cz D64

Nx Sy Cz D2 PE1,1

..................

..................

Nx Sy Cz D64 PE1,1


5620 NM first-level resources

AU4 Nx Sy Cz 2

First AU3 Nx Sy Cz 3

Second AU3 Nx Sy Cz 4

Third AU3 Nx Sy Cz 5

First TUG3 Nx Sy Cz 6

Second TUG3 Nx Sy Cz 7

Third TUG3 Nx Sy Cz 8

5620 NM second-level resource managedEquipment object Ids; STM1 MS port configured for AU4 mode

First TUG3 - TUG2 managedEquipment object Id




Fourth TUG2 Nx Sy Cz 12

Fifth TUG2 Nx Sy Cz 13

Sixth TUG2 Nx Sy Cz 14

Seventh TUG2 Nx Sy Cz 15

Second TUG3 - TUG2 managedEquipment object Id








(1 of 2)




Third TUG3 - TUG2 managedEquipment object Id








5620 NM second-level resource managedEquipment object Id; STM1 MS port configured for AU3 mode

First AU3 - TUG2 managedEquipment object Id








Second AU3 - TUG2 managedEquipment object Id








Third AU3 - TUG2 managedEquipment object Id









(2 of 2)



36.9 listFreeManagedGroomedCircuitTPs and listUsedManagedGroomedCircuitTPs actions

There are no parameters for the listFreeManagedGroomedCircuitTPs and listUsedManagedGroomedCircuitTPs actions. The OIDs for these actions are 1.2.124.113537.1.3.21 for listFreeManagedGroomedCircuitTPs and 1.2.124.113537.1.3.22 for listUsedManagedGroomedCircuitTPs. Table 36-8 lists the results for the actions.

Table 36-8 listFreeManagedGroomedCircuitTPs and listUsedManagedGroomedCircuitTPs results

Characteristic Description

Unsorted array of distinguished full names

Each distinguished name represents a free or used managedGroomedCircuitTP on the indicated managedPack object.







37.5 managedProfileID 37-3

37.6 managedProfileProf attribute 37-8



37.1 Introduction

The managedProfile object models the following profile types:

• network-level profiles, such as TCA, SLP, and policy and policy constraint profiles

• node-specific profiles for nodes, such as ASAM

The managedProfile object is an extended managed object that is contained in the network object. The various instances of managedProfile class are not created or deleted by system management protocol. Network-level profiles are created during network initialization. Node-specific profiles are created or deleted when the node is created or deleted on the 5620 NM.

A set request is allowed on the managedProfileProf attribute of network-level profiles so that an OSS can configure the various profile parameters.

A set request is rejected on the managedProfileProf attribute of node-specific profiles, because all profile parameters are read-only.


The managedProfile object supports the following CMIP operations:

• get• cancel get• set• action on the network object — FindByLabel to retrieve the managedProfileID

given the managedProfileName


The managedProfile object can generate the following event notifications:

• attributeValueChange• objectCreation• objectDeletion

37.4 Attributes

Table 37-1 describes the attributes of the managedProfile object.



Table 37-1 managedProfile object attributes

37.5 managedProfileID

The managedProfileID attribute of the managedProfile object consists of an integer derived from a combination of values. Two distinct structures are defined. The format of the structure is identified by the value of the Profile Identifier Format field of the managedProfileID.

Table 37-2 describes the managedProfileID structure for the network-level profiles. Table 37-3 shows a sample managedProfileID bitmask illustration for a network-level profile.


managedProfileID Distinguished name of the managedProfile object

Read An integer bitmask that is calculated from a combination of values; see Tables 37-2 and 37-6 for more information

managedProfileName Name of the profile Read A string of up to 32 characters

managedProfileProf All configurable parameters Read-write for network-level profiles

Read for node-specific profiles

The profile table is a generic table used by different profile types. See section 37.6 for more information.

managedProfileTransPending

State of the record in the database and the network

Read 0 = Not applicable

1 = Record has been added to database and is up-to-date on all relevant network elements

2 = Record has been added to database but has not yet been distributed to all relevant network elements

3 = Record has been configured and is up-to-date on all relevant network elements

4 = Record has been configured but has not yet been distributed to all relevant network elements

5 = Record has been deleted but has not yet been distributed to all network elements

managedProfileType Profile type Read 1 = SLP

2 = TCA

3 = ADSL

4 = 7321 RU local

13 = Policy

14 = Policy constraint

nameBinding Name binding used by the managedProfile object

Read —

objectClass Type of object Read OID for managedProfile

packages Packages used by the managedProfile object

Read List of packages. See the GDMO for more information.



Table 37-6 describes the managedProfileID structure for the node-specific profiles. See Table 37-7 for a sample managedProfileID bitmask illustration for a node-specific profile.

managedProfileID for a network-level profile

Table 37-2 describes the managedProfileID structure for the network-level profiles.

Table 37-2 managedProfileID structure for the network-level profile

Calculating a managedProfileID value for a network-level profile

Table 37-3 provides a sample managedProfileID bitmask for a network-level profile, in this case, an AAL1 performance TCA profile. The decimal value for the entire bitmask is 1 048 737. The bitmask identifies the following managedProfileID fields:

• Profile Identifier Format = 0 (network-level profile)• Profile Category = 16 (AAL1 performance)• Profile Number = 5 (AAL1 performance profile 5)• Profile Period = 1 (15 min)

Table 37-3 Sample managedProfileID bitmask for a network-level profile

Field Bit offset Bit allocation Value

Profile Period 0 5 0 to 4

Profile Number 5 11 1 to N

A Profile Number identifies a profile within a Profile Category. Table 37-5 identifies the number of profiles within each Profile Category. See the 5620 Network Manager User Guide for more information.

Profile Category 16 14 See Table 37-5 for more information.

Profile Identifier Format

30 2 0x00 for network-level profiles

The Profile Identifier Format specifies the format used for forming the value of the managedProfileID attribute.

Value Profile Identifier FormatBits 30, 31

Profile CategoryBits 16 to 29

Profile NumberBits 5 to 15

Profile PeriodBits 0 to 4

Binary 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 1

Decimal 0 16 5 1



The following sub-subsections provide more information about the fields of the managedProfileID for a network-level profile:

• Profile Period• Profile Number• Profile Category• Profile Identifier Format

Profile Period

The Profile Period identifies the period for the record. A period is a time span during which the parameter values in the record apply. Table 37-4 describes the Profile Period values for network-level profiles.

Table 37-4 Profile Period values for a network-level profile

Profile Number

The Profile Number identifies a profile within a profile category. There can be many different profiles within a profile category. Each profile is identified by a Profile Number. Table 37-5 lists the number of profiles within each profile category. See the 5620 Network Manager User Guide for more information about the different profile types within each profile category.

Profile Category

The Profile Category specifies the category to which the profile belongs. Table 37-5 describes the Profile Category values.

Table 37-5 Profile Category values for network-level profiles

Profile Period Description

0 Not applicable

1 15 min

2 1 h

3 24 h sliding window

4 24 h from midnight

Profile Category

Description Number of profiles

1 Signaling link profile for 7470 MSP


20

2 OC12/STM4 physical layer-section 4

3 OC12/STM4 physical layer-line 4

4 OC12/STM4 physical layer-path 4

5 OC3/STM1 physical layer-section 4

(1 of 2)




The Profile Identifier Format identifies the structure to be used to interpret the remainder of the fields in the managedProfileID. For network-level profiles, the value is always 0.

managedProfileID for a node-specific profile

Table 37-6 describes the managedProfileID structure for the node-specific profiles.

6 OC3/STM1 physical layer-line 4

7 OC3/STM1 physical layer-path 4

8 DS3/E3 physical layer-line 4

9 DS3/E3 physical layer-path 4

10 DS3/E3-PLCP 4

11 Frame relay card congestion 4

12 Frame relay stream congestion 8

13 OFRT —

14 DS1 physical 4

15 E1 physical 4

16 AAL1 performance


8

17 SMDS170 DXI stream —

18 ADSL line threshold 4

19 ADSL channel threshold 4

22 ATM layer OAM-PM


8

23 OC48/STM16 physical layer section 4

24 OC48/STM16 physical layer line 4

25 OC48/STM16 physical layer path 4

32 IDSL physical link


32

10000 Signaling link profile for 36120


10

10001 Signaling link profile for 36160


8

15001 Policy 800

15002 Policy Constraint 800

Profile Category

Description Number of profiles

(2 of 2)



Table 37-6 managedProfileID structure for a node-specific profile

Calculating a managedProfileID value for a node-specific profile

Table 37-7 provides a sample managedProfileID bitmask for a node-specific profile. The decimal value for the entire bitmask is 1 074 174 081. The bitmask identifies the following managedProfileID fields:

• Profile Identifier Format = 0 (node-specific profile)• Node Id = 211• Profile Type = 1• Profile Number = 1

Table 37-7 Sample managedProfileID bitmask for a node-specific profile

The following sub-subsections provide more information about the fields of the managedProfileID for a node-specific profile:

• Profile Number• Profile Type• Node Id• Profile Identifier Format

Profile Number

Profile Number identifies a profile with the profile type. There can be many different profiles within a Profile Type, and each is identified by a Profile Number. Table 37-8 identifies the number of profiles within each profile type that is supported for any one node.

Field Bit offset Bit allocation Value

Profile Number 0 7 1 to N

A Profile Number identifies a profile within a Profile Type for the node identified by Node ID.

Profile Type 7 4 See Table 37-8

Node Id 11 19 Node ID


30 2 0x01 for node-specific profiles

The Profile Identifier Format specifies the format used for forming the value of the managedProfileID attribute.

Value Profile Identifier FormatBits 30, 31

Node IdBits 11 to 29

Profile TypeBits 7 to 10

Profile NumberBits 0 to 6

Binary 01 0000 0000 0001 1010 011 0001 0000001

Decimal 1 211 1 1



Profile Type

Profile Type identifies the type of profile. Table 37-8 describes the Profile Type values.

Table 37-8 Profile Type values

Node Id

The Node Id has the value of the managedElementId attribute of the managedElement object that represents the specific node to which this profile belongs.


Profile Identifier Format identifies the structure that is to be used in intepreting the remainder of the fields in the managedProfileID. In the case of node-specific profiles, the value is always 1.

37.6 managedProfileProf attribute

Each profile type has unique characteristics (parameters) that are represented as different cpTypes of managedProfileProf attribute. The number of cpTypes that are present with managedProfileProf attribute depends on the profile type.

managedProfileProf attribute characteristics for network-level profiles

Tables 37-9 to 37-14 describe the characteristics for network-level profiles.

Profile Type Description Number of profiles

1 CAC 20

2 ADSL line 100

3 Access 20

4 Traffic descriptor 100

5 XDSL service 128

6 XDSL spectrum 128



Table 37-9 managedProfile attribute characteristics for AAL1 performance TCA profile (Profile Category field of the managedProfileID = 16)

Table 37-10 managedProfile attribute characteristics for OAM-PM TCA profile (Profile Category field of the managedProfileID = 22)

Characteristic cpType cpValue Access Description

AAL1 Header Errors 1 1, 2, 10, 3695400 or 354758400

Read-write For a 15-min period, the values are: default = 2, minimum = 1, maximum = 3695400.

For a 24-h period, the values are: default = 10, minimum = 1, maximum = 354758400.

Lost Cells 2 1,10, 25, 3695400 or 354758400



Buffer Underflows 3 1, 3, 10, 3695400 or 354758400



Underflow Seconds 4 1, 3, 10, 3695400 or 354758400



Buffer Overflows 5 1, 3, 10, 3695400 or 354758400



Pointer Parity Errors 6 1, 3, 10, 3695400 or 354758400



AAL1 Pointer Reframes 7 1, 3, 10, 3695400 or 354758400




Severely Errored Cell Blocks (SECB)

1 1, 20, 200,

2000000 or 192000000



Impaired Blocks 2 1, 20, 200, 2000000 or 192000000



Total Lost 0 + 1 User Information Cells

3 1, 50, 500 or 2000000000



(1 of 2)



Table 37-11 managedProfile attribute characteristics for IDSL profile (Profile Category field of the managedProfileID = 32)

Table 37-12 managedProfile attribute characteristics for policy profile (Profile Category field of the managedProfileID = 15001)

Total Lost 0 User Information Cells

4 1, 20, 200, 2000000000



Cell Loss Ratio 0 + 1 5 1, 1000 or 1000000000

Read-write For a 15-min period, the values are: default = 1 000, minimum = 1, maximum = 1000000000.


Cell Loss Ratio 0 6 1, 10 or 1000000000



Profile parameter cpType Default threshold Threshold valid range Subcode alarm text

15-min 24-h 15-min 24-h

Errored seconds 1 60 300 0 to 900 0 to 86400 ES

Severely errored seconds 2 60 300 0 to 900 0 to 86400 SES

CRC error count 3 60 300 0 to 900000 0 to 86400000 CEC


Administrative Status 1 1, 2 Read default = 1

1 = enabled

2 = disabled

Require Ne-NSC list operator

2 1, 2 Read default = 1

1 = the Require Ne-NSC list operator is Logical_Or

2 = the Requre Ne-NSC list operator is Logical_And

Requre Ne-NSC list 3 1 to 23 characters

Read A string containing a maximum of 4 Ne-NSC IDs, separated by “,”

Require Rp-NSC list operator


1 = the Require Rp-NSC list operator is Logical_Or

2 = the Requre Rp-NSC list operator is Logical_And

Requre Ne-NSC list 5 1 to 23 characters

Read A string containing a maximum of 4 Rp-NSC IDs, separated by “,”

(1 of 2)


(2 of 2)



Table 37-13 managedProfile attribute characteristics for policy constraint profile (Profile Category field of the managedProfileID = 15002)

Table 37-14 managedProfile attribute characteristics for SLP (VPCL and FRL) profile (Profile Category field of the managedProfileID = 1, 10000 or 10001)

Must Avoid Ne-NSC list operator


1 = the Must Avoid Ne-NSC list operator is Logical_Or

2 = the Must Avoid Ne-NSC list operator is Logical_And

Must Avoid Ne-NSC list 7 1 to 23 characters

Read A string containing a maximum of 4 Ne-NSC IDs, separated by “,”


Administrative Status 1 1, 2 Read default = 1

1 = enabled

2 = disabled

Ordered list of policies 2 1 to 23 characters

Read Default = [empty string]

A string containing six Policy Index values, separated by a “,”


Protocol 1 1 to 13 Read-write 1 = ATM Forum UNI 3.1 network

2 = ATM Forum IISP 1.0 network

3 = ATM Forum IISP 1.0 user

4 = ITU Q.2931 network

5 = PNNI symmetrical

6 = AINI symmetrical

7 = ATM Forum UNI 4.0

8 = ITU X.36 network

9 = FRF.4 network

10 = ITU X.76 network

Enhanced Routing 2 1, 2 Read-write 1 = routing off

2 = routing on

(1 of 3)


(2 of 2)



SAAL cc timer 3 100 to 4000

Read-write Value in milliseconds

SAAL poll timer 4 100 to 4000

Read-write

SAAL keep alive timer 5 100 to 8000

Read-write

SAAL idle timer 6 100 to 20000

Read-write

SAAL no response timer 7 200 to 30000

Read-write

SAAL max cc 8 1 to 10 Read-write

SAAL max pdu 9 5 to 2120 Read-write

SAAL max stat 10 3 to 1021 Read-write

DSS2 timer 301 11 180 to 600 Read-write Value in seconds

DSS2 timer 303 12 2 to 60 Read-write



DSS2 timer 310 15 2 to 60 or

30 to 120

Read-write Value in seconds

For PNNI, the value range is 30 to 120 s






34 to 124


For PNNI, the value range is 34 to 124 s

Assigning 21 1 to 3 Read-write 1 = disable

2 = enable

3 = auto


1 to 600


For the 36120, the value range is 1 to 500. For the 7470 MSP, the value range is 1 to 600.

DSS1 timer 305 23 Read-write





q922 max returns 28 1 to 30 Read-write —

q922 max octets 29 16 to 4472 or 260 to 4472

Read-write For the 36120 the value range is 16 to 4472. For the 7470 MSP the value range is 260 to 4472.


(2 of 3)



managedProfileProf attribute characteristics for node-specific profiles

Table 37-15 describes the profile subtype (cpType 100) characteristic for the node-specific CAC and traffic descriptor profiles.





DSS2 timer recon 34 1 to 60 Read-write

q922 timer 200 35 1 to 3000 or

100 to 3000

Read-write Value in milliseconds

For the 36120, the value range is 1 to 3000. For the 7470 MSP, the value range is 100 to 3000.

q922 timer 203 36 1000 to 500000

Read-write —

Address format 37 1 to 3 Read-write 1 = AESA

2 = native

3 = as received


(3 of 3)



Table 37-15 managedProfileProf attribute profile subtype characteristic for node-specific CAC and traffic descriptor profiles

managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, node-specific profiles

Tables 37-16 to 37-22 describe the characteristics for 7300 ASAM, Release 4.1, node-specific profiles.

Table 37-16 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, access profile (Profile Type field of the managedProfileID = 3)


Profile subtype 100 1 to 6 Read 1 = nt_cac

2 = cbr_cac /biqos_cac

3 = ubr_cac

Valid only for ASAM 4.1 CAC profiles (Profile Type field of managedProfileID attribute = 1)

1 = CBR

2 = UBR

Valid only for ASAM 4.1 traffic descriptor profiles (Profile Type field of managedProfileID attribute = 4)

0 = undefined

Valid only for ASAM 4.2 or later CAC profiles (Profile Type field of managedProfileID attribute = 1)

1 = CBR

2 = UBR

3 = rt-VBR

4 = nrt-VBR1

5 = nrt-VBR2

6 = nrt-VBR3

Valid only for ASAM 4.2 or later, and 7321 RU 2.1 or later, traffic descriptor profiles (Profile Type field of managedProfileID attribute = 4)


Max number of VPCs 1 — Read The maximum number of VPCs (PVCs and SVCs) that are supported with this ATM interface.

Max number of VCCs 2 — Read The maximum number of VCCs (PVCs and SVCs) that are supported with this ATM interface.

Max active VPI bits 3 — Read The maximum number of active VPI bits that are configured for use with this ATM interface.

Max active VCI bits 4 — Read The maximum number of active VCI bits that are configured for use with this ATM interface.



Table 37-17 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, NT CAC profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 1)

Table 37-18 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, CAC CBR profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 2)

Table 37-19 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, CAC UBR profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 3)


Admissible load factor for GCR

1 0 to 1000 Read default = 950


Admissible load factor for CBR



Overbooking factor for UBR



Admissible load factor for UBR MCR



UBR connection limitation at bus level



Aggregate load factor 6 0 to 1000 Read default = 1000



Buffer size in cells 1 16 Read Not supported

Admissible load factor for bit rate



Security factor for burst size



CBR connection limitation


Maximum number of UBR connections



Buffer size in cells 1 16 Read Not supported

Peak cell rate limitation for line rate



Overbooking factor for UBR



(1 of 2)



Table 37-20 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, CBR traffic descriptor profile (Profile Type field of the managedProfileID = 4 and cpType 100 = 1)

Table 37-21 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, UBR traffic descriptor profile (Profile Type field of the managedProfileID = 4 and cpType 100 = 2)

Table 37-22 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.1, ADSL line profile (Profile Type field of the managedProfileID = 2)

Admissible load factor for UBR MCR



UBR connection limitation



Peak cell rate for CLP 1 1 to 353207 Read cpValue = 0+1 traffic (cells/s)

CDVT 2 1 to 1000000 Read default = 0

Value in ms


Peak cell rate for CLP 1 1 to 353207 Read cpValue = 0+1 traffic (cells/s)

Minimum cell rate for CLP

2 1 to 353207 Read cpValue = 0+1 traffic (cells/s)


Minimum downstream bit rate


Minimum bit rate for the interleaved downstream data flow; expressed in kb/s

Minimum upstream bit rate


Minimum bit rate for the interleaved upstream data flow; expressed in kb/s

Maximum downstream bit rate


Maximum bit rate for the interleaved downstream data flow; expressed in kb/s

Maximum upstream bit rate


Maximum bit rate for the interleaved upstream data flow; expressed in kb/s


(2 of 2)



managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, node-specific profiles

Tables 37-23 to 37-34 describe the characteristics for 7300 ASAM, Release 4.2 or later, node-specific profiles.

Table 37-23 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, access profile (Profile Type field of the managedProfileID = 3)

Table 37-24 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, access line CAC CBR profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 0)

Table 37-25 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, access line CAC rt-VBR profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 0)


Max number of VPCs 1 0 to 4000 Read The maximum number of VPCs (PVCs and SVCs) that are supported with this ATM interface.

Max number of VCCs 2 0 to 10368 Read The maximum number of VCCs (PVCs and SVCs) that are supported with this ATM interface.

Max active VPI bits 3 1 to 12 Read The maximum number of active VPI bits that are configured for use with this ATM interface.

Max active VCI bits 4 6 to 16 Read The maximum number of active VCI bits that are configured for use with this ATM interface.

GFC mode 5 UNI, NNI Read default = UNI

Police mode 6 None, VC-only, all

Read default = ALL


Max number of CBR Ltps


CBR load factor 2 0 to 100 Read default = 100

CBR burst size factor 3 0 to 1000 Read default = 100

Max number of UBR Ltps


UBR MCR load factor 5 0 to 100 Read default =100


Max number of rt-VBR Ltps


rt-VBR load factor 7 0 to 100 Read default = 100

(1 of 2)



Table 37-26 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, access line CAC nrt-VBR profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 0)

Table 37-27 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, access line CAC GFR profile (Profile Type field of the managedProfileID = 1 and cpType 100 = 0)

rt-VBR burst size factor 8 0 to 1000 Read default = 100

rt-VBR NGCR guaranteed factor


rt-VBR overbooking factor



Max number of nrt-VBR Ltps


nrt-VBR load factor 12 0 to 100 Read default = 100

nrt-VBR burst size factor


nrt-VBR NGCR guaranteed factor


nrt-VBR overbooking factor



Max number of GFR Ltps


GFR load factor 17 0 to 100 Read default = 100

GFR burst size factor 18 0 to 1000 Read default = 100

GFR overbooking factor


Aggregate load factor 20 0 to 100 Read default = 100

Aggregate GCR load factor



(2 of 2)



Table 37-28 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, CBR traffic descriptor profile (Profile Type field of the managedProfileID = 4 and cpType 100 = 1)

Table 37-29 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, UBR traffic descriptor profile (Profile Type field of the managedProfileID = 4 and cpType 100 = 2)

Table 37-30 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, rt-VBR traffic descriptor profile (Profile Type field of the managedProfileID = 4 and cpType 100 = 3)

Table 37-31 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, nrt-VBR1 traffic descriptor profile (Profile Type field of the managedProfileID = 4 and cpType 100 = 4)


Peak cell rate for CLP = 0+1 traffic

1 0 to 149759 Read Value in kb/s

CDVT 2 0 to 1000000 Read Value 0.1 ms increments




Minimum cell rate for CLP = 0+1 traffic


CDVT 3 0 to 1000000 Read Value 0.1 ms increments




Sustainable cell rate for CLP= 0+1 traffic


Max burst size 3 1 to 10000 Read Value in cells

CDVT 4 0 to 1000000

Read Value in 0.1 ms

Frame discard 5 1, 2 Read 1 = enable

2 = disable







(1 of 2)





Tables 37-23 to 37-34 describe the characteristics for 7300 ASAM, Release 4.2 or later, node-specific profiles.

Table 37-34 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.2 or later, ADSL line profile (Profile Type field of the managedProfileID = 2)

CDVT 4 0 to 1000000



2 = disable







CDVT 4 0 to 1000000



2 = disable


(2 of 2)


adslInterleavedPlannedBitrateDownstream 1 0 to 65535 Read ADSL interleaved planned bit rate downstream data flow

Value in kb/s

adslInterleavedPlannedBitrateUpstream 2 0 to 65535 Read ADSL interleaved planned bit rate upstream data flow

Value in kb/s

adslInterleavedMaxBitrateDownstream 3 0 to 65535 Read ADSL interleaved max bit rate downstream data flow

Value in kb/s

adslInterleavedMaxBitrateUpstream 4 0 to 65535 Read ADSL interleaved max bit rate upstream data flow

Value in kb/s

(1 of 2)



managedProfileProf attribute characteristics for 7300 ASAM, Release 4.5.10 or later, node-specific XDSL service profile

Table 37-35 describes the characteristics for 7300 ASAM, Release 4.5.10 or later, node-specific XDSL service profile.

Table 37-35 managedProfileProf attribute characteristics for 7300 ASAM, Release 4.5.10 or later, XDSL service profile (Profile Type field of the managedProfileID = 5)

adslFastPlannedBitrateDownstream 5 0 to 65535 Read ADSL fast planned bit rate downstream data flow

Value in kb/s

adslFastPlannedBitrateUpstream 6 0 to 65535 Read ADSL fast planned bit rate upstream data flow

Value in kb/s

adslFastMaxBitrateDownstream 7 0 to 65535 Read ADSL fast max bit rate downstream data flow

Value in kb/s

adslFastMaxBitrateUpstream 8 0 to 65535 Read ADSL fast max bit rate upstream data flow

Value in kb/s

adslInterleavedMinBitrateDownstream 9 0 to 65535 Read ADSL interleaved min bit rate downstream data flow

Value in kb/s

adslInterleavedMinBitrateUpstream 10 0 to 65535 Read ADSL interleaved min bitrate upstream data flow

Value in kb/s

adslFastMinBitrateDownstream 11 0 to 65535 Read ADSL fast min bit rate downstream data flow

Value in kb/s

AdslFastMinBitrateUpstream 12 0 to 65535 Read ADSL fast min bit rate upstream data flow

Value in kb/s


(2 of 2)


Planned Bitrate Down 1 0 to 65535 Read Value in kb/s

Planned Bitrate Up 2 0 to 65535 Read Value in kb/s

Max Bitrate Down 3 0 to 65535 Read Value in kb/s

Max Bitrate Up 4 0 to 65535 Read Value in kb/s

Min Bitrate Down 5 0 to 65535 Read Value in kb/s

Min Bitrate Up 6 0 to 65535 Read Value in kb/s

(1 of 2)



managedProfileProf attribute characteristics for 7300 ASAM, Release 4.5.10 or later, node-specific XDSL spectrum profile

Table 37-36 describes the characteristics for 7300 ASAM, Release 4.5.10 or later, node-specific XDSL spectrum profile.

Table 37-36 managedProfileProf attribute characteristics for the XDSL spectrum profile (Profile Type field of the managedProfileID = 6)

managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, node-specific profiles

Table 37-37 describes the characteristics for 7321 RU, Release 2.1 or later, node-specific profiles.

Line RA Mode Down 7 1 to 3 Read 1 = operatorControlledRateAdaptive

2 = automaticRateAdaptiveAtStartup

3 = dynamicRateAdaptive

Line RA Mode Up 8 1 to 3 Read 1 = operatorControlledRateAdaptive

2 = automaticRateAdaptiveAtStartup

3 = dynamicRateAdaptive


(2 of 2)


Line Min Noise Margin Down

1 0 to 31 Read Value in dB

Line Min Noise Margin Up


Line Max Noise Margin Down


Line Max Noise Margin Up


Line Target Noise Margin Down


Line Target Noise Margin Up




Table 37-37 managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, ADSL profile


Interleaved MaxTxRateAtuC

1 32 to 8064 kb/s

Read Configured maximum transmit rate for interleave channels. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Interleaved Max TxRateAtuR

2 32 to 1024 kb/s

Read Configured maximum transmit rate for interleave channels. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Interleaved Min TxRateAtuC

3 32 to 8064 kb/s

Read Configured minimum transmit rate for interleave channels. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Interleaved MinTxRateAtuR

4 32 to 1024 kb/s

Read Configured minimum transmit rate for interleave channels. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Interleaved Max DelayAtuC

5 0 to 255 ms Read Configured maximum interleave delay for this channel. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Interleaved Max DelayAtuR

6 0 to 255 ms Read Configured maximum interleave delay for this channel. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Fast MaxTxRateAtuC 7 32 to 8064 kb/s

Read Configured maximum transmit rate for fast channels. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Fast MaxTxRateAtuR 8 32 to 1024 kb/s

Read Configured maximum transmit rate for fast channels. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Fast MinTxRateAtuR 9 32 to 8064 kb/s

Read Configured minimum transmit rate for fast channels. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Fast MinTxRateAtuR 10 32 to 1024 kb/s

Read Configured minimum transmit rate for fast channels. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Line Min Noise Margin AtuC

11 0 to 31 dB Read Configured minimum acceptable signal/noise margin. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Line Max Noise Margin AtuC

12 0 to 31 dB Read Configured maximum acceptable signal/noise margin. Data flows from the central office to the remote end.

If the noise margin is greater than the configured maximum acceptable signal/noise margin, the modem attempts to reduce its power output to optimize its operation. This cpType is for downstream connectivity.

(1 of 3)



Line Target Noise Margin AtuC

13 0 to 31 dB Read Configured target signal/noise margin. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Ths is the noise margin that the modem must achieve with a BER of 10-7 or better to successfully complete initialization.

Line Target Noise Margin AtuR

14 0 to 31 dB Read Configured target signal/noise margin. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Ths is the noise margin that the modem must achieve with a BER of 10-7 or better to successfully complete initialization.

Minimum Downshift TimeAtuC

15 0 to 16383 s

Read Minimum time that the current margin is less than the downshiftSnrMgnAtuC before a downshift occurs. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Minimum Downshift TimeAtuR

16 0 to 16383 s

Read Minimum time that the current margin is less than the downshiftSnrMgnAtuR before a downshift occurs. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Minimum Upshift TimeAtuR

17 0 to 16383 s

Read Minimum time that the current margin is greater than the upshiftSnrMgnAtuC before an upshift occurs. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

Minimum Upshift TimeAtuR

18 0 to 16383 s

Read Minimum time that the current margin is greater than the upshiftSnrMgnAtuR before an upshift occurs. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Upshift SNR Mgn AtuC 19 0 to 31 dB Read Configured signal/noise margin for rate upshift. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

If the noise margin is greater than the specified level, the modem attempts to increase its trasmit rate.

Upshift SNR Mgn AtuR 20 0 to 31 dB Read Configured signal/noise margin for rate upshift. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

Downshift SNRMgn AtuC

21 0 to 31 dB Read Configured signal/noise margin for rate downshift. This cpType is for downstream connectivity. Data flows from the central office to the remote end.

If the noise margin is less than the specified level, the modem attempts to decrease its transmit rate.


(2 of 3)



Table 37-38 managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, traffic descriptor profile

Downshift SNRMgn AtuR

22 0 to 31 dB Read Configured signal/noise margin for rate downshift. This cpType is for upstream connectivity. Data flows from the remote end to the central office.

If the noise margin is less than the specified level, the modem attempts to decrease its transmit rate.

adslLineType 23 1 to 5 Read Defines the ADSL physical line entity that exists by indicating whether and how the line is channelized.

1 = noChannel

2 = fastOnly

3 = interleavedOnly

4 = fastOrInterleaved

5 = fastAndInterleaved

Only 2 and 3 are supported.


(3 of 3)


Profile 100 1 to 6 Read The following values apply to the ASAM 4.1 CAC profiles:

1 = nt_cac

2 = cbr_cac/biqos_cac

3 = ubr_cac

The following values apply to the ASAM 4.1 traffic descriptor profiles:

1 = CBR

2 = UBR

The following values apply to the 7321 RU and ASAM 4.2 or later traffic descriptor profiles:

1 = CBR

2 = UBR

3 = rt-VBR

4 = nrt-VBR1

5 = nrt-VBR2

6 = nrt-VBR3



Table 37-39 managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, CBR traffic descriptor profile

Table 37-40 managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, UBR traffic descriptor profile

Table 37-41 managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, rtVBR traffic descriptor profile


Peak Cell Rate 1 0 to 353207 cells/s

Read The value of this object identifies the Peak Cell Rate (PCR)

Cell Delay Variation Tolerance

2 0 to 1000000 µs

Read The value of this object identifies Cell Delay Variation Tolerance (CDVT)

Frame Discard 3 1, 2 Read The value of this object identifies the Boolean value for Frame Discard.

1 = True

2 = False



Read The value of this object identifies the Peak Cell Rate (PCR).

Minimum Cell Rate 2 0 to 353207 cells/s

Read The value of this object identifies the Minimum Cell Rate (MCR).


1 = True

2 = False




Sustainable Cell Rate 2 0 to 353207 cells/s

Read The value of this object identifies the Sustainable Cell Rate (SCR).

Maximum Burst Size 3 1 to 10000 cells

Read The value of this object identifies the Maximum Burst Size (MBS).

(1 of 2)



Table 37-42 managedProfileProf attribute characteristics for 7321 RU, Release 2.1 or later, nrtVBR1 traffic descriptor profile



4 0 to 1000000 µs

Read The value of this object identifies the Cell Delay Variation Tolerance (CDVT).


1 = True

2 = False


(2 of 2)









4 0 to 1000000 µs

Read The value of this object identifies the Cell Delay Variation Tolerance (CDVT)


1 = True

2 = False









4 0 to 1000000 µs



1 = True

2 = False












4 0 to 1000000 µs



1 = True

2 = False



38.1 Introduction

Instances of network objects can:

• model a 5620 NM-managed network • model a 5620 NM-managed network partition • contain other objects relating to network configuration

A network object identifies the name of the network or the partition from which the network resources are drawn.


The network object supports the following CMIP operations:

• get• cancel get• action — FindByLabel

38.3 Attributes

Table 38-1 describes the attributes of the network object.

Table 38-1 network object attributes


networkId Naming attribute; unique identifier for an instance of an object class

Read An integer or a string

top-level network: a user specified string

second-level network: partition id

third-level network: profile network

objectClass Is the class of object Read Always the OID for network

nameBinding Is the kind of name binding Read Name binding

The network object has three possible name binding levels. See section 20.3 for more information.

packages Is the package used by the object


userLabel Is a supply network name or a partition name

Read default = partition name



39.1 Introduction

The oAMCellTestObject is created to administer the OAM cell loopback test. It is deleted at the end of the test. The oAMCellTestObject is contained by the testActionPerformer object; multiple instances of the oAMCellTestObject can be contained by the testActionPerformer object.

See the 5620 NM Fault Management guide for more information about the OAM cell test diagnostic.


The oAMCellTestObject object supports the following CMIP operations:

• get• cancel get• set• action—oam-cell


The oAMCellTestObject can generate the following CMIP event notifications:


39.4 Attributes

Table 39-1 describes the attributes of the oAMCellTestObject.

Table 39-1 oAMCellTestObject attributes


associatedObjects Provides a sequence of object identifiers

Read The two associated objects are the injection point (mFTP or mGCTP) and the optional cell return point (mE or mGCTP).

mORTS Is the object instance of the managed object where the OAM cell loopback test is to occur

Read The distinguishedName of bMGroomedCircuit or bMFacility


Read Name binding

(1 of 2)



oAMReturnPointType Indicates how to determine the loopback return point

Read-write 0 = end-point

1 = none

2 = user-specified

the user must specify a node.

oAMTestName Is a test field for naming a test

Read-write Any text

objectClass Indicates the kind of object Read OID of the oAMCellTestObject

operationalState Indicates the operational status of the object

Read 0 = disabled

1 = enabled

Always enabled

See Table 48-2 for more information.





2 = initializing

3 = reporting

4 = terminating

See Table 48-2 for more information.

testInvocationID Provides the distinguishedName of the oAMCellTestObject

Read The distinguishedName of the parent testActionPerformer object



(2 of 2)



40.1 Introduction

The objectCreationRecord object is a CMIP event notification logged by the log object. See chapter 30 for more information about the log object.

You can only create an instance of the objectCreationRecord object for the event notification if it matches the criteria specified in the discriminatorConstruct attribute of the log object.


The objectCreationRecord object supports the following CMIP operations:


40.3 Attributes

Table 40-1 describes the attributes of the objectCreationRecord object.

Table 40-1 objectCreationRecord object attributes


eventTime Identifies the time the event occurred Read Time

eventType Is the type of event Read Object creation


logRecordId Is an identifier created when an event notification becomes an objectCreationRecord object



Read Object class

managedObjectInstance Identifies the object instance that generated the event notification


attributeList Identifies all created attributes and values for managedObjectInstance

Read All created attributes and values for managedObjectInstance

nameBinding Identifies the kind of name binding used by the objectCreationRecord object

Read Name binding

objectClass Is the kind of object Read Always the OID for objectCreationRecord

packages Identifies the packages used by the objectCreationRecord object





2 = unknown



41.1 Introduction

The objectDeletionRecord object is a CMIP event notification logged by the log object. See chapter 30 for more information about the log object.

You can only create an instance of an objectDeletionRecord object for an event notification if it matches the criteria specified in the discriminatorConstruct attribute of the log object.


The objectDeletionRecord object supports the following CMIP operations:


41.3 Attributes

Table 41-1 describes the attributes of the objectDeletionRecord object.

Table 41-1 objectDeletionRecord object attributes



eventType Is the type of event Read Object deletion

loggingTime Is the time that the event was logged Read Time

logRecordId Is an identifier created when an event notification becomes an objectDeletionRecord object



Read Object class

managedObjectInstance Identifies the object instance object that generated the event notification


attributeList Identifies all deleted attributes and values for managedObjectInstance

Read All deleted attributes and values for managedObjectInstance

nameBinding Identifies the kind of name binding used by the objectDeletionRecord object

Read Name binding

objectClass Is the kind of object Read Always the OID for objectDeletionRecord

packages Identifies the packages used by the objectDeletionRecord object

Read List of packages; see the GDMO for more information




2 = unknown



42.1 Introduction

The objectGroup object is used to group routerTemplate objects.


The objectGroup object supports the following CMIP operations:


42.3 Attributes

Table 42-1 describes the attributes of the network object.

Table 42-1 objectGroup attributes


groupId Specifies the naming attribute of the objectGroup

Read 1

nameBinding Identifies the kind of name binding used by the objectGroup

Read network-object Group

objectClass Indicates the kind of object Read Always the OID of the objectGroup


Read —

typeText Additional information Read templateGroup







43.5 execute action 43-4

43.6 cancelExecute action 43-4

43.7 getExecuteResponse action 43-4

43.8 discardExecuteResponse action 43-4



43.1 Introduction

The routerTemplate object is used to allow the creation, configuration, deletion, and execution of a router template on a managedElement. The routerTemplate object only exists on the 5620 CMIP gateway on which it was created, and is not propagated to other 5620 CMIP gateways.


The routerTemplate object supports the following CMIP operations:

• create-subordinate• get• set• delete• cancel-get• action

• execute• action

• cancelExecute• action

• getExecuteResponse• action

• discardExecuteResponse


The routerTemplate object can generate the following event notifications:

• objectCreation• objectDeletion• attributeValueChange• stateChangeEvent

43.4 Attributes

Table 43-1 describes the attributes of the routerTemplate object.



Table 43-1 routerTemplate attributes


administrativeState Specifies the administrative state of the router template

Read Unlocked

associatedObjects Contains a list of distinguished names for the managedElements where the router template is to be executed

Read The value of the associatedObjects attribute is restricted to a single managedElement.

When the managedElement object referenced is deleted from the network, the routerTemplate object and its attributes remain unchanged.

executeOperationState

Represents the current routerTemplate execution operation state

Read 0 = not ready

1 = ready

2 = executing

3 = response ready

A stateChangeEvent is raised when the executeOperationState attribute changes.

executeStatus Represents the current routerTemplate execution status

Read 0 = not started

1 = in progress

2 = successful

3 = failed

A stateChangeEvent is raised when the executeOperationState attribute changes.

routerTemplateProfile

Reserved for future use Read —

nameBinding Specifies the nameBinding Read objectGroup-routerTemplate OID

objectClass Specifies the objectClass Read routerTemplate OID

packages Lists the packages used by the routerTemplate

Read List of packages

parameterList Specifies the parameters associated with the template requested by the templateName attribute

Read-write A sequence of parameters.

The valueString for each parameter is initially filled with the default value for each parameter, or is empty if the default is not set. It can only be overwritten by a SET-REPLACE operation.

The nameString of the parameter is defined by the associated template, and should not be changed.

routerTemplateId The unique routerTemplate instance name

Read This attribute is automatically generated and is unique among all gateways.

(1 of 2)



43.5 execute action

Use the execute action to execute the routerTemplate on the managedElement. There are no attributes for the execute action.

43.6 cancelExecute action

Use the cancelExecute action to cancel the execution of a routerTemplate on a managedElement. There are no attributes for this action.

43.7 getExecuteResponse action

Use the getExecuteResponse action to get the execution response and return it to the requester. There are no attributes for this action.

43.8 discardExecuteResponse action

Use the discardExecuteResponse action to discard the execution response. There are no attributes for this action.

tempateName Specifies the name of the template in the 5620 NM

Read-write Up to 255 characters.

This attribute is mandatory, and can only be set when the object is created.

templateVersion Specifies the version of the template associated with the routerTemplate

Read-write String up to 255 characters.

This attribute is mandatory, and can only be set when the object is created.

userLabel Specifies the user label of the routerTemplate object

Read-write Up to 255 characters.


(2 of 2)



44.1 Introduction

The splitMonitorTestObject is created to administer either a split-through, split-back or monitor test and is deleted at the end of the test. The splitMonitorTestObject is contained by the testActionPerformer object; multiple instances of the splitMonitorTestObject can be contained by the testActionPerformer object. The 5620 CMIP can support a maximum of 100 splitMonitorTestObjects at one time.

See the 5620 NM Fault Management guide for more information about the type of diagnostics.


The splitMonitorTestObject supports the following CMIP operations:

• get• cancel get• set• action—testSplitThru, testSplitBack, testMonitor, testRelease


The splitMonitorTestObject can generate the following CMIP event notifications:

• attributeValueChange• objectCreation• objectDeletion• stateChange• processingErrorAlarm

44.4 Attributes

Table 44-1 describes the attributes of the splitMonitorTestObject.



Table 44-1 splitMonitorTestObject attributes


associatedObjects Provides a sequence of associated objects including:

a) two groomed circuit object instances created for the test—set to null if test is on-node

b) the TP object instance where the split is to be done

Read Sequence of distinguishedNames

mORTs Is the object instance of the managed object where the split-monitor test is to occur

Read distinguishedName of bMGroomedCircuit

nameBinding Identifies the kind of name binding used by a splitMonitorTestObject

Read Name binding

objectClass Indicates the kind of object Read Always the OID for splitMonitorTestObject


Disabled if the test groomed circuit gets disconnected or fails; otherwise the operationalState is enabled

Read 0 = disabled

1 = enabled




proceduralStatus Indicates the procedural status of the splitMonitorTestObject


2 = initializing

3 = reporting

4 = terminating


testInvocationID Provides the distinguishedName of the splitMonitorTestObject


testName Is the text field for naming the test

Read- write

Any text

testObjectId Is not used at this time Read Always 0

testObjectName Is a unique identifier for the instance of the splitMonitorTestObject

Read Instance of the splitMonitorTestObject

testType Indicates the type of test being performed

Read 0 = release

1 = monitor

2 = split-through

3 = split-back



45.1 Introduction

The stateChangeRecord object is a CMIP event notification logged by the log object. See chapter 30 for more information about the log object.

You can only create an instance of an event record object for an event notification if it matches the criteria specified in the discriminatorConstruct attribute of the log object.


The stateChangeRecord object supports the following CMIP operations:


45.3 Attributes

Table 45-1 describes the attributes of the stateChangeRecord object.

Table 45-1 stateChangeRecord object attributes



eventType Is the type of event Read attribute ChangeRecord notification

loggingTime Is the time that event was logged Read Time

logRecordId Is an identifier created when an event notification becomes a stateChangeRecord object



Read Object class

managedObjectInstance Identifies the object instance that generated the event notification


nameBinding Identifies the kind of name binding used by the stateChangeRecord object

Read Name binding

objectClass Is the kind of object Read Always the OID for stateChangeRecord

packages Identifies the packages used by the stateChangeRecord object


stateChangeDefinition Indicates the old and new values Read List of values



46.1 Introduction

The system object represents the 5620 CMIP OSS Interface Gateway on the Gateway Station. It is contained directly under the local root.

The system object ID value identifies an 5620 CMIP OSS Interface Gateway system. It allows a customer with one OSS and multiple 5620 CMIP OSS Interface Gateways to differentiate between them at the system-managed object level. The object ID value is user-configurable.

Alarms affecting the 5620 CMIP are handled by the managedElement object that represents the 5620 CMIP Gateway Station, rather than by the system object. See chapter 32 for information about the managedElement object.


The system object supports the following CMIP operations:


46.3 Attributes

Table 46-1 describes the attributes of the system object.

Table 46-1 system object attributes


nameBinding Identifies the kind of name binding used by the system object

Read Name binding

objectClass Is the kind of object Read Always the OID for system

operationalState Is the status of the object in the network Read Always enabled

0 = disabled

1 = enabled

packages Identifies the packages used by the system object


systemId Is a unique identifier for an instance of a system object

Read User-defined integer or string specified in the file CE_network.conf used at initial systems startup

systemTitle Identifies the 5620 CMIP OSS Interface Gateway

Read 5620 CMIP-defined OID

usageState Indicates if a system object instance is in use Read Always active



47.1 Introduction

The testAccessConnectionObject is created to administer either a monitor, split-back, or split-loop test. The testAccessConnectionObject is contained by the testActionPerformer object; multiple instances of the testAccessConnectionObject can be contained by the testActionPerformer object.

When the test is completed, the action Release terminates the test and sets the object to the state Not Initialized. The testAccessConnectionObject is not deleted from the MIB until a testTerminate command is issued on the testActionPerformer object that contains the testAccessConnectionObject.

See the 5620 NM Fault Management guide for more information about the test access connection diagnostic.


The testAccessConnectionObject supports the following CMIP operations:

• get• cancel get• set• action—releaseTAC, monitorTAC, splitBackTAC, splitLoopTAC


The testAccessConnectionObject can generate the following CMIP event notifications:


47.4 Attributes

Table 47-1 describes the attributes of the testAccessConnectionObject.

Note — There may be node limitations for the number of TACs supported. See the node documentation for more information.



Table 47-1 testAccessConnectionObject attributes


associatedObjects Provides an ordered sequence of associated objects

Read The sequence of distinguishedNames is target and then test.

mORTs Is the object instance of the managed object where the test access connection test is to occur

Read distinguishedName of bMGroomedCircuit


Read Name binding

objectClass Indicates the kind of object Read OID of the testAccessConnectionObject


Read 0 = disabled

1 = enabled

See Table 48-2



proceduralStatus Indicates the procedural status of the testAccessConnectionObject


2 = initializing

3 = reporting

4 = terminating


tacTestProfile Provides four numbers: cpType, cpValue, cpType, cpValue

The cpType data will occur in pairs. The valid pairs are: 1 and 2 for VPI/VCI information; 3 and 4 for playout buffer and data octet information. No other combinations of these values are applicable.

Read 1 = VPI

2 = VCI

3 = Playout Buffer

4 = Data Octet

See Table 24-8 for the range of cpValues which correspond to these cpTypes

tacTestType Indicates the type of test being performed

Read 0 = releaseTAC

1 = monitorTAC

2 = splitBackTAC

3 = splitLoopTAC

testInvocationID Provides the distinguishedName of the testAccessConnectionObject


testObjectID Provides a unique identifier for an instance of a testAccessConnectionObject

Read Naming attribute






48.4 operationalState and proceduralStatus attributes 48-3



48.1 Introduction

The testActionPerformer is a unique object in the MIB that is permanently represented by an instance. It is contained in the top-level network layer and exists exclusively to receive test actions.


The testActionPerformer object supports the following CMIP operations:

• get• cancel get• action—testRequestControlledAction (test initiation) and testTerminateAction

(test termination); these actions result in the creation and deletion of test objects

48.3 Attributes

Table 48-1 describes the attributes of the testActionPerformer object.

Table 48-1 testActionPerformer object attributes



Read Name binding

objectClass Indicates the kind of object Read OID of the testActionPerformer object


Read List of packages; see the GDMO for more information

supportedTOClasses Indicates the types of tests supported

Read List of OID values representing the supported test objects:

• busyOutTestObject• loopBackTestObject• oAMCellTestObject• splitMonitorTestObject• testAccessConnectionObject• traceTestObject• genericActionObject

testActionPerformerID Provides a unique identifier for the instance of the testActionPerformer object

Read Always 1



48.4 operationalState and proceduralStatus attributes

Table 48-2 describes the various combinations of operationalState and proceduralStatus for the testAccessConnectionObject, splitMonitorTestObject, loopBackTestObject, busyOutTestObject, oAMCellTestObject, traceTestObject, and genericActionObject.

Table 48-2 Test state mapping

Test state operationalState proceduralStatus

not initialized—indicates that either no test action was performed or that the last action was release

1 = enabled 1 = not initialized

initializing—indicates the test is being set up 1 = enabled 2 = initializing

testing 1 = enabled 3 = reporting

terminating 1 = enabled 4 = terminating

disabled—indicates that one or more test bMGroomedCircuit objects are disconnected or disabled

0 = disabled Any value







49.5 traceTestProfile attribute 49-3

49.6 traceTestObject action results 49-4



49.1 Introduction

The traceTestObject administers ATM Forum standards-based path and connection tracing for SPVC paths within multivendor interoperable networks.

See the 5620 NM Fault Management guide for more information about the path and connection trace diagnostic.


The traceTestObject supports the following CMIP operations:

• get• get-replace• action

• connectionTraceUse the connectionTrace action to retrieve the VPI, VCI, or DLCI values of all the intermediate path endpoints.

• spvcPathTraceUse the spvcPathTrace action to determine where new paths can connect

• spvcConnectionTraceUse the spvcConnectionTrace action to collect information about established connections.


The traceTestObject can generate the following CMIP event notifications:


49.4 Attributes

Table 49-1 describes the attributes of the traceTestObject.

Table 49-1 traceTestObject attributes


mORTs Is the object instance of the managed object where the traceTestObject is to occur

Read default = none

distinguishedName of bMGroomedCircuit


Read Name binding

(1 of 2)



49.5 traceTestProfile attribute

Table 49-2 describes the characteristics of the traceTestProfile attribute of the traceTestObject.

objectClass Indicates the kind of object Read OID of the traceTestObject


Read default = 1

0 = disabled

1 = enabled

See Table 48-2



proceduralStatus Indicates the procedural status of the traceTestObject

Read default = not initialized

1 = not initialized

2 = initializing

3 = reporting

4 = terminating


testInvocationID Provides the distinguishedName of the traceTestObject

Read default = none

distinguishedName of the traceTestObject

testObjectID Provides a unique identifier for an instance of a traceTestObject

Read default = none

Naming attribute

traceTestName Is a text field for naming the test

Read default = none

Any text—31 characters

traceTestProfile Provides information on four trace flags

Read See Table 49-2 for more information

traceTestType Indicates the type of trace being performed

Read default = 0

0 = trace-none

1 = spvcPathTrace

2 = spvcConnectionTrace

3 = connectionTrace


(2 of 2)



Table 49-2 traceTestProfile attribute characteristics

49.6 traceTestObject action results

The results of traceTestObject actions are described in this section.

connectionTrace action resultsThe connectionTrace action returns a list of intermediate path endpoints along with their VPI, VCI, or DLCI values of the chosen path with which the traceTestObject is associated. In most cases, the connectionTrace result does not list the endpoints that are not present in the 5620 CE MIB. However, in some cases, such as when a timeslot is used by an NNI frame relay link, the endpoint is listed in the connectionTrace result, but not in the 5620 CE MIB.

The following displays the output format:

{objectInstance{

{<distinguishedName of the endpoint>}{vpi{}}{vci{}}{dlci{}}

}{

{<distinguishedName of the endpoint>}{vpi{}}{vci{}}{dlci{}}

}... ... ...}


C flag 1 0, 1 default = 1

0 = disable

1 = enable

Valid only for spvcPathTrace action

X flag 2 0, 1 default = 0

0 = disable

1 = enable

Valid only for spvcPathTrace action; always set to 0

V flag 3 0, 1 default = 1

0 = disable

1 = enable

A flag 4 0, 1 default = 1

0 = disable

1 = enable



spvcConnectionTrace action resultsThe output of the spvcConnectionTrace and spvcPathTrace actions may be difficult to interpret. Table 49-3 lists the fields that appear in the return trace for an spvcConnectionTrace.

Table 49-3 spvcConnectionTrace return trace format

spvcPathTrace action resultsTable 49-4 lists the fields that appear in the return trace for an spvcPathTrace.

Table 49-4 spvcPathTrace return trace format

Note — The format of the spvcPathTrace action results is determined by the node. This format may vary for different nodes and different releases of nodes. See the node documentation for more details.

Byte offset Length Description

0 1 Release number

1 1 Version number

2 1 Trace status:

• 0 = trace in progress• 1 = trace completed• 2 = trace incomplete• 3 = trace exceeded length limitations• 4 = trace exceeded message length limit

3 1 Destination endpoint type describing the VPI, VCI, DCLI, or stream:

• 1 = ATM• 2 = frame relay

4 2 Destination VPI or stream

6 4 Destination VCI or DLCI

10 4 Destination PNNI port ID

For release 2.2 and later 7X70 nodes, the bits include details on channels.

14 12 Trace completion timestamp


0 1 Release number

1 1 Version number

2 1 Trace status:

• 0 = trace in progress• 1 = trace completed• 2 = trace incomplete• 3 = trace exceeded length limitations• 4 = trace exceeded message length limit

(1 of 2)



3 1 Length of diagnostics message, in bytes

4 4 Call failure cause. A 0 is used if the call is successful.

8 17 Call failure diagnostic. A 0 is used 17 times if the call is successful.

25 1 Type of connection:

• 1 = point to point• 2 = point to multipoint

26 1 Type of connection:

• 1 = SVC• 6 = SPVC

27 1 Service category:

• 1 = CBR• 2 = nrt-VBR• 3 = ABR• 4 = UBR• 5 = ABR/UBR• 6 = rt-BVR

28 4 Source interface index

32 4 Destination interface index

36 4 Destination PNNI port ID

For release 2.2 and later 7X70 nodes, the bits include details on channels.

40 1 Routing table descriptor. A 0 is used if the path is not the DTL originator or entry border

41 1 Destination endpoint type describing the VPI, VCI, DCLI, or stream:

• 1 = ATM• 2 = frame relay

42 2 Destination VPI or stream

44 4 Destination VCI or DLCI

48 34 Calling party address

82 34 Called party address

116 12 Trace completion timestamp

128 4 Forward peak cell rate, in cells per second

132 4 Backward peak cell rate, in cells per second

136 4 Forward sustained cell rate, in cells per second

140 4 Backward sustained cell rate, in cells per second

144 4 Forward minimum cell rate, in cells per second

148 4 Backward minimum cell rate, in cells per second

152 4 GCAC, in Kb/s


(2 of 2)


Appendixes

A. Card types

B. The 5620 CMIP OIDs arranged by standard

C. 5620 CMIP OIDs arranged numerically and alphabetically

D. alarmRecord attribute values arranged by managedObjectClass

E. alarmInfo

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 A-1October 2006 95-6040-01-00-C

A. Card types

A.1 Values for holderStatus, acceptableCircuitPackTypeList, and circuitPackType attributes A-2

A. Card types

A-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

A.1 Values for holderStatus, acceptableCircuitPackTypeList, and circuitPackType attributes

This appendix lists the available values for the holderStatus, acceptableCircuitPackTypeList, and circuitPackType attributes. These values represent card types.



See chapters 27 and 36 for more information about these attributes.

Table App A-1 lists the available values for the holderStatus, acceptableCircuitPackTypeList, and circuitPackType attributes. These values are listed numerically and alphabetically.

Table A-1 Values for holderStatus, acceptableCircuitPackTypeList, and circuitPackType attributes

String Description

27LC3 27LC3 12-port card

28LC 28LC card (2 or 6 line)

2B1Q 2B1Q card

2WTO 2WTO module

3-DS3 FP 3-DS3 frame processing card

3/1 DS1 TDM DS1 unchannelized card (for example, T::DAX LDS1)

3/1 DS3 TDM DS3 channelized to T1 level (for example, T::DAX AMX)

3/1 E1 TDM E1 unchannelized card (for example, T::DAX PE1)

3/1 E3 TDM E3 channelized to E1 level (for example, T::DAX EAMX)

3/3 DS3 TDM DS3 unchannelized card

3/3 E3 TDM E3 unchannelized card

336 DMB DMB card on DEX_CS1

3TOKEN 3-port token ring card

4601A Terminal port

4ENET 4-port ethernet card

4WTO 4WTO card

5620 NM Terminal port

A4SC1 4x4 switching card

A4SC2 4x4 switching card with priority

A4SC2E 2E switching card with priority

(1 of 14)

A. Card types


A4SC3 74-cell 4x4 switching card

A4SC4 Switching card

A8SC 8x8 switching card

AACU-A ADSL Alarm Control Unit A card

AACU-B ADSL Alarm Control Unit B card

AACU-C ADSL Alarm Control Unit C card

AACU-D ADSL Alarm Control Unit D card

AANC-A AANC-A card

AATU-B ASAM Alarm Control Unit B card

AATU-C ASAM Alarm Control Unit C card

ABLT-A ABLT-A LT card

ABLT-B ABLT B LT card

ABLT-D ABLT D LT card

ABLT-E ABLT E LT card

ABLT-F ABLT F LT card

ABLT-G ABLT G LT card

ABLT-H ABLT H LT card

ABLT-J ABLT J LT card

ACDS-A ACDS-A card

ACE1-A ACE1-A card

ACE3-A ACE3-A card

ADLT-E ADSL E LT card (4 lines)

ADLT-F ADSL F LT card (ISDN Support, 4 lines)

ADLT-J ADSL J LT card (12 lines)

ADLT-K ADSL K LT Card (ISDN support, 12 lines)

ADLT-L ADSL L LT card (6 lines, active splitter)

ADLT-LP ADSL/POTS Low Power card

ADLT-M ADSL M LT card

ADLT-N 24-port ADSL ISDN LT card

ADLT-O ADSL O LT card

ADLT-P ADSL P LT card

ADLT-Q ADSL Q LT card

ADLT-R ADSL R LT card

ADLT-S ADSL S LT card

ADLT-S2 ADSL S2 LT card

ADLT-T ADSL T LT card

ADLT-T2 ADSL T2 LT card

String Description

(2 of 14)

A. Card types


ADLT-U ADSL U LT card

ADLT-W ADSL W LT card

ADLT-Y ADSL Y LT card

ADSE-A ADSL Serial Extender version A

ADSE-B ADSL Serial Extender version B

ADSE-C ADSL Serial Extender version C

ADSE-D ADSL Serial Extender version D

ADSL ADSL 8 or 16-port card

ADSL/32 port ADSL 32-port card



AEXT-A AEXT-A card

AFLT-A AFLT-A card

AICC-A AICC-A card

Alarm 36200 Alarm card

ALM 36150 Alarm card

AMX TDAX

AMD AMD card

ANT ANT card (OC3/STM1 variant)

AR1 1 agg or 1

AR2 1 agg and 1

ASAM Card on a partially integrated 7300 ASAM node

ASCC-AD ASCC-AD card

ASCC-AE ASCC-AE card

ASCC-E1 ASCC-E1 card

ASCC-PD ASCC-PD card

ASCC-PE ASCC-PE card

ASCC-S1 ASCC-S1 card

ATAU-B ASAM Alarm Control Unit card

ATDS-A ATDS-A card

BRI 4 or 8-port S/T BRI interface card

BRI A S/T BRI aggregate module

BSEC-A BSEC-A card

Carrier CARRIER

CC1 Control card X

CC2 Control card Y

CIC A CIC A I/O card

String Description

(3 of 14)

A. Card types


CIC B CIC B I/O card

CLK Clock card on SU

COMMS —

CPC Call processing card

CPSS CPSS module

CSM Agent CSM server control card

CSU CSU card

CTL Control card

CTL2 Control card 2B

CTL3 Control card 3

CTL A GEN2 Control card A 2nd generation

CTL B GEN2 Control card B 2nd generation

CUST Custom card

D1LT-A (Quad) DS1 (IMA) LT version A

D1LT-B (Quad) DS1 (IMA) LT version B

D1NT-A (Quad) DS1 (IMA) NT card version A

D1NT-B (Quad) DS1 (IMA) NT card version B

D1NT-C (Quad) DS1 (IMA) NT card version C

D3LT-A DS3 A LT card version A

D3NT-A DS3 A NT card version A

D3NT-B DS3 B NT card version B

D3NT-C DS3 C NT card version C

DC1 DEX_CS1L

DC3 DC3 card

DCM2 Two DCM modules

DCM4 Four DCM

DCP DCP card

DDC DACS_II dual-T1

DDS DDS card

DDS2 DDS tone2 module

DEM —

DFIC 7670 RSP dual fabric interface card

DHUB Dual-hub card

DLIT-B ASAM line interface module card version B

DMB DMB card

DMLB DMLB card on DEX_CS1L

DMM DSP multimodule

String Description

(4 of 14)

A. Card types


DNIC DNIC card

DOC3 WS dual-OC-3 card

DPC DACS_II dual-E1

DRX Dual-receiver card

DS0 DS0 test module on test card

DS3 DS3 card

DS3CE2 3-port DS3CCE-2 card

DS3CFR DS-3 CFR card

DS3CR 8-port DS-3 cell relay card

DS3 CR DS3 CR card on 3600+

DS3UFR DS-3 UFR card

DSC Dual-switching card

DSI 1630_SX—DS1 card

DSP DSP module

DSP1 DSP1 card

DSP2 DSP 2 card

DSP3 DSP 3 card

DSP4 DSP 4 card

DSP5H DSP-5 card

DSPM DSPM card

DSTM1 WS dual-STM-1 card

E1 E1 card

E1A E1 aggregate

E1ASC E1ASC card

E1ATM E1 ATM card

E1CE E1CE card

E1CFR Channelized E1FR card

E1D E1 2-port type 1 card

E1D2 E1 2-port type 2 card

E1LT-A (Quad) E1 (IMA) LT card version A

E1LT-B (Quad) E1 (IMA) LT card version B

E1NT-A (Quad) E1 (IMA) NT card version A

E1NT-B (Quad) E1 (IMA) NT card version B

E1NT-C (Quad) E1 (IMA) NT card version C

E1SMDS E1 channelized SMDS card

E1 MS E1 MS card

E1TDM1 E1 TDM card

String Description

(5 of 14)

A. Card types


E1TDM2 E1 TDM-2 card

E1UFR Unchannelized E1FR card

E1VS E1 voiceband service card

E2 E2 slot on E3 node

E2CCE E3 circuit emulation card

E3 E3 card

E3ATM E3 ATM UNI card

E3ATM2 E3 ATM PLCP/G.804 card

E3CCE2 E3 CE dual-port card

E3LT-A E3 A LT card version A

E3NT-A E3 A NT card version A

E3LT-B E3 B LT card version B

E3NT-B E3 B NT card version B

E3NT-C E3 C NT card version C

E3UFR E3 UFR card type

EALT-A EALT-A card

EAMX TDAX

EandM EandM card

EandM1 EandM type 1 card



EBLT-A EBLT-A card

EBLT-C EBLT-C card

EBLT-D EBLT-D card

EBLT-E EBLT-E card

EBLT-F EBLT-F card

EBLT-J EBLT-J card

EBLT-K EBLT-K card

EBLT-L EBLT-L card

ECC 7670 ESE ECC card

ECNT-A ECNT-A card

ECNT-C ECNT-C card

EDSE-A EDSE-A card

EI 1630_SX—E1 card

Element Mgr Element manager card

EMPTY No card

ENET Ethernet card

String Description

(6 of 14)

A. Card types


ESC Edge services card

ETHER HUB Ethernet hub router card

Ethernet Element-managed ethernet adapter card

ETHERNET Ethernet router card

EVLT-A EVLT-A card

EVLT-C EVLT-C card

EVLT-D EVLT-D card

EXP Default EXP 6+6—2 shelves

Fabric 7670 ESE fabric card

FAC NA FAC I/O card

Fax Fax/HCV module

FDDI FDDI card

FENT-A FENT-A card

FIC FIC card

FNIC Forum ATM NIC card, 1 port

FRATM E3ATM FRATM—E3 variant (see FRATM T3ATM

FRATM T3ATM Invisible FRATM card used to combine all the devices on the node face-plate—T3 variant

FRE FASTbus interface processor (aka PTE & FRE)

FRM FRM card

FRS Frame relay switch

G703 G.703 64k codirectional card

G703D G703 codirectional DCM

GELT-A Gigabit Ethernet line server module

GENT-A GENT-A card

GIGE LH Gigabit Ethernet long hall card

GIGE LX Gigabit Ethernet long extension card

GIGE SX Gigabit Ethernet short extension card

GFC GFC card

GFC3 GFC type 3 card

GSLC12 GSLC12 line card

GSLC16 GSLC16 line card

HCV HCV module

HDE1FR HDE1FR card

HDT1 HDT1 or HDT1P card

HDT1FR HDT1FR card

HFIC 7670 RSP HS fabric interface card

String Description

(7 of 14)

A. Card types


HMU 1630_SX—HMU card

HSC 7670 RSP HSPS shelf controller card

HSMR HSPS HSMR line card

HSSIFR HSSI FR card type

HSSMDS HSSI SMDS card

HUB WS hub card

ICON 7670 RSP ICON management line card

ICON EXP I/O 7670 RSP ICON expansion I/O card

ICON I/O 7670 RSP ICON I/O card

IDSL IDSL card

IEB Integral Ethernet Bridge

IMA 7390 DBS Quad E1/T1 IMA card

IMC Inverse-multiplexing card

Internal Internal link card

IPGW-A IP Gateway card

ISAM Card on a 7302 ISAM node

ISC IP-service router card

ISC CSR ISC card

ISL1 WS ISL receiver card

ISL2 WS ISL transmitter card

ITB Integral token-ring bridge

JPEG JPEG NTSC video card

JPEG P PAL video card

LATM1 LATM card-100Mb multimode

LATM2 LATM card-140Mb multimode

LATM3 LATM card-140Mb single-mode

LATM4 LATM card-140Mb single-mode long reach intermediate reach

LGE LGE card

LGE1 LGS, A-law, type 6

LGE2 LGS type 6

LGE3 —

LGS LGS card

LGS1 LGS1 card

LGS2 LGS type 2

LGS3 LGS type 3

LGS4 LGS, Mu-law, type 4

LGS5 LGS, Mu-law, type 5

String Description

(8 of 14)

A. Card types


LGS6 LGS type 6

LINE MDR node line card

LSHUB HUB card for multishelf

LTAC-A LTAC-A card

LTAC-B LTAC-B card

LTAC-C LTAC-C card

LTAC-D LTAC-D card

LTAC-D2 LTAC-D2 card

LTAC-F LTAC-F card

LTSC-A LTSC-A card

LSSHUB HUB card for standalone shelf

MACU-C MiniRAM ACU version C

MJU MJU card

MJU 1 DEX_CS1L

MJU 2A DEX_CS1L

MMFG DACS_II DS3

MPA MPA card

MPEGCD MPEG comp decoder

MPEGCE MPEG comp encoder/decoder

MPEGCO MPEG composite analog card

MPEGD1 MPEG D1 digital card type

MR16 ATM High-speed multirate line card

MR16 POS 7670 RSP multirate16 POS line card

MR8 ATM IP Multirate line card

MRD MRD card

MTM Metallic test module on test card

MVNM ATM ATM card (for example, Passport 3pds3A, 1pOC-3S)

NACC-A NACC-A card

NACC-B NACC-B card

NACC-C NACC-C card

NBLC-A NBLC-A card

NEW Unsupported cards; unknown

NIC ATM NIC card, 1 port

NULL Null

OC12 OC-12 I/O card and 7670 ESE OC12 Aggregate card

OC12 IR Intermediate range OC-12 card

OC12 LR Long range OC-12 card

String Description

(9 of 14)

A. Card types


OC12 MMF OC-12 MMF card

OC12 SR Short range OC-12 card

OC12 XLR OC-12 XLR card

OC3 8-port OC-3 I/O card

OC3 VoP 7670 RSP ESE OC3 voice over packet card

OC3CR OC-3 cell relay card

OC3 EL Electrical OC-3 card

OC3 I/O IR OC3 I/O IR card

OC3 I/O LR OC3 I/O LR card

OC3 I/O SR OC3 I/O SR card

OC3 IR Intermediate-range OC-3 card

OC3IR1 Intermediate-range OC-3 ATM card

OC3IR2 Intermediate-range OC-3 ATM UNI card

OC3 LR Long-range OC-3 card

OC3LR1 Long-range OC-3 ATM card

OC3LR2 Long-range OC-3 ATM UNI card

OC3MM Short-range OC-3 card

OC3MMF Quad OC-3 MMF card

OC3MS 7670 ESE OC3 MS

OC3 SR Short-range OC3 card

OC3UTP Quad OC-3 UTP card

OC3 XLR Extended long-range OC3 card

OC48 OC-48 card

OC48 IR OC48 intermediate range card

OC48 LR OC48 long range card

OC48 SR OC48 short range card

OC48 XLR OC48 XLR card

OC48 XR OC48 XR card

OC48 STM16 OC-48/STM16 line card

OCU3 OCU DP3 module

OE1 Octal E1 card

OT1 Octal T1 card

P.Mgr 5610 card w/ 8 RS232 ports

PE Packet engine = FRE + X.25

PAIC-A PAIC-A card

PIC A 7670 RSP peripheral interconnect card

PIC B 7670 RSP peripheral interconnect card

String Description

(10 of 14)

A. Card types


Proxy Agent Proxy agent card

PRT 1630_SX—PRT card

PS Power supply card

PSC A 7670 RSP peripheral shelf controller

PSC B 7670 RSP peripheral shelf controller

PSIFR PSIFR card

Quad OC3 Quad OC3 SFP card

Quad STM1 Quad STM1 SFP card

QFIC 7670 RSP quad fabric interface card

RD RD card

RDCM RS232 direct connect module

RESERVED DEX_CS1L RSVD card

RESV Super-rate use, reserved slot

RF MDR node RF card

RUEM LT RUEM LT card

RUEM-B RUEM B LT card

SAC 7670 RSP switching access card

SATU-A SATU-A card

SBRI SBRI DCM card

SALT-A OC3 or STM-1 LT card version A

SALT-B OC3 or STM-1 LT card version B

SALT-C OC3 or STM-1 LT card version C

SANT-D OC3 or STM-1 NT card version D

SANT-E OC3 or STM-1 NT card version E

SANT-F OC3 or STM-1 NT card version F

SANT-G OC3 or STM-1 NT card version G

SANT-H OC3 or STM-1 NT card version H

SBLT-A OC12 or STM-4 LT line termination unit card (HCL based) version A

SBNT-A SONET network termination unit card (GANT-C based OC12) version A

SBNT-B SONET network termination unit card (GANT-C based OC12) version B

SC HSM—SC on SU

SCH 7670 RSP switching scheduler card

SD3CCE DS-3 circuit emulation card

SDSL SDSL card

SHLT-B 24 port SHDSL LT card version B

String Description

(11 of 14)

A. Card types


SHLT-C 24 port SHDSL LT card version C

SHLT-D 24 port SHDSL LT card version D

SHLT-E 24 port SHDSL LT card version E

SHUB Single-shelf hub card

SI HSE—SIC on PU

SALT-A OC3 or STM1 LT card version A

SALT-B OC3 or STM1 LT card version B

SMLT-A SHDSL SMLT-A card

SMLT-B SHDSL SMLT-B card

SMLT-C SHDSL SMLT-C card

SMLT-D SHDSL SMLT-D card

SMLT-E SHDSL SMLT-E card

SMX 7670 RSP switching matrix card

SNU TDAX

SPI Serial port interchange

SRDM DEX_CS1L

SRM SRM card

SRV SERVICE card

SSC 7670 RSP switching shelf controller

STM1 STM-1 card

STM1 STM-1 I/O card

STM1 VoP 7670 RSP ESE STM1 AAL2 Gateway Card

STM16 IR STM-16 intermediate-range card

STM16 LR STM-16 long-range card

STM16 SR STM-16 short-range card

STM16 XLR STM-16 XLR card

STM16 XR STM-16 XR card

STM1CR STM-1 cell relay card

STM1 EL STM-1 electrical card


STM1 LR STM-1 long-range card

STM1MM STM-1 MMF card

STM1MS 7670 ESE STM1 MS card

STM1 SR STM1 short range card

STM1 XLR STM1 XLR card

STM1 XR STM1 extended range card

String Description

(12 of 14)

A. Card types


STM4 STM-4 I/O, high-speed STM4 I/O, and 7670 ESE STM4 Aggregate card


STM4 LR STM-4 long-range card type

STM4 SR STM-4 short-range card type

STM4 XLR STM-4 XLR card

STM4 XR STM-4 extended long reach card

SUP Super-rate module

SW X Switch X card

SW Y Switch Y card

T1 T1 card

T1ASC T1 ASC card

T1ATM T1 ATM card

T1ATMC T1 ATM CSU card

T1CE T1 CE card

T1CFR Channelized T1FR card

T1D T1D 2-port type 1 card

T1D2 DT1-2

T1 MS T1 MS card

T1TDM T1 TDM card

T1UFR Unchannelized T1FR card

T1VS T1 voiceband service card

T3 CE T3 circuit emulation module

T3ATM1 T3 ATM PLCP card

T3ATM2 T3 ATM UNI card

TALT-B TALT-B card

TALT-C TALT-C card

T-ARIC T-ARIC card on node

TC Terminating card

TDM STS1 STS-1 access card (for example, T::DAX SAMX)

TDM STS1U STS-1 unchannelized access card

TE1 Tributary E1 card

TE1-IA NT TE1-IA NT card

TEST Test card

TGM Tone generation module

Timing Timing card

TM Timing card

String Description

(13 of 14)

A. Card types


TMCU TDAX

TNT 16-port TNT card (T1/E1)

TOKEN RING Token ring router card

Token-ring Element-managed token ring adapter card

TONE Tone generator—goes in DSP slot

TRM Tone/ringer generator module

TT1 Tributary T1 card

TTC2M TTC2M card

TU12MP TU-12 mapper card

TU12MP 32-port TU12 mapper card

UC3 UC3 or UC3P card

UCS Universal interface card

V35 V.35 3 or 6-port card

V35 Frame Relay V.35 frame relay card

V35A V.35 narrow aggregate

V35AM V.35 AIMM

V35D V.35 direct connect module

V35E V.35 EDCM

V35P Primary V.35 1-port card

V35VC V.35 virtual channel protocol card

VALT-A Voice over DSL (A) card

VDLT-A VDLT A LT card

VCM VCM module

VDSL VDSL 16-port card

VSEM-A VSEM-A card

VT15MP VT-1.5 mapper card

VT15MP 32-port VT15 mapper card

X21 X.21 4 or 6-port card

X21 Frame Relay X.21 frame relay card

X21A X.21 narrow aggregate

X21D X.21 direct connect module

X21P X.21 primary rate card

X21P2 X.21 low overhead primary rate card

X21VC X.21 virtual channel protocol card

X22P X.22 primary rate card

YELRID Yellow ridge card, 12 ethernet & 1 OC-3

String Description

(14 of 14)

A. Card types


Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 B-1October 2006 95-6040-01-00-C


B.1 TMF 038 bandwidth management ensemble B-2

B.2 TMF Library 1 B-2

B.3 TMF Library 4 B-3

B.4 ITU-T M.3100 B-4

B.5 ITU-T Q.821 B-8

B.6 ITU-T X.721 B-9

B.7 ITU-T X.745 B-13

B.8 Association management extension B-15

B.9 Fault management extensions B-16

B.10 Path management extensions B-19

B.11 Test management extensions B-20


B-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

B.1 TMF 038 bandwidth management ensemble

These OID values are based on the TMF standard 038. Table App B-1 lists the OID values for attributes, Table App B-2 lists the OID values for managed objects, and Table App B-3 lists the OID values for name bindings.

Table B-1 TMF 038 OID values—attributes

Table B-2 TMF 038 OID values—managed objects

Table B-3 TMF 038 OID values—name bindings

B.2 TMF Library 1

Table App B-4 shows the attribute OID value that is based on the TMF standard Library 1.

OID Name Type

1.2.124.360501.1.327 userIdentifier Attribute

1.2.124.360501.1.328 commonProfile Attribute

1.2.124.360501.1.329 tDMProfile Attribute

1.2.124.360501.1.340 frameRelayProfile Attribute

1.2.124.360501.1.341 aTMProfile Attribute

OID Name Type

1.2.124.360501.3.75 bMGroomedCircuitTP Managed object

1.2.124.360501.3.76 bMFacilityTP Managed object

1.2.124.360501.3.77 bMGroomedCircuit Managed object

1.2.124.360501.3.78 bMFacility Managed object

OID Name Type

1.2.124.360501.4.168 bMGroomedCircuitTP-managedElement Name binding

1.2.124.360501.4.169 bMFacilityTP-managedElement Name binding

1.2.124.360501.4.170 bMGroomedCircuit-network Name binding

1.2.124.360501.4.171 bMFacility-network Name binding



Table B-4 TMF Library 1 OID values—attributes

B.3 TMF Library 4

These OID values are based on the TMF standard Library 4. Table App B-5 lists the OID values for actions, Table B-6 lists the OID value for notifications, and Table App B-7 lists the OID values for attributes.

Table B-5 TMF Library 4 OID values—actions

Table B-6 TMF Library 4 OID value—notifications

Table B-7 TMF Library 4 OID values—attributes

OID Name Type

1.2.124.360501.1.157 typeText Attribute

OID Name Type

1.2.124.360501.6.11 trmAbort Action

1.2.124.360501.6.12 trmCircuitGrooming Action

1.2.124.360501.6.13 trmCircuitTrace Action

1.2.124.360501.6.14 trmGetStatus Action

1.2.124.360501.6.15 trmLocalLoop Action

OID Name Type

1.2.124.360501.5.14 trmCircuitGroomed Notification

OID Name Type

1.2.124.360501.1.10 circuitBandwidth Attribute

1.2.124.360501.1.14 circuitType Attribute

1.2.124.360501.1.45 facilityType Attribute

1.2.124.360501.1.312 trmCircuitProfile Attribute

1.2.124.360501.1.313 trmDataMode Attribute

1.2.124.360501.1.314 trmEncryptionRouting Attribute

1.2.124.360501.1.315 trmFiberRouting Attribute

1.2.124.360501.1.317 trmFunctionalInterface Attribute

1.2.124.360501.1.319 trmPhysicalInterface Attribute

(1 of 2)



B.4 ITU-T M.3100

These OID values are based on the ITU-T standard M.3100. Tables App B-8 to App B-13 list the OID values for actions, attributes, name bindings, objects, packages, and parameters, respectively.

Table B-8 ITU-T M.3100 OID values—actions

Table B-9 ITU-T M.3100 OID values—attributes

1.2.124.360501.1.321 trmTerrestrialRouting Attribute

1.2.124.360501.1.322 trmVoiceMode Attribute

OID Name Type

(2 of 2)

OID Name Type

0.0.13.3100.0.9.3 allowAudibleVisualLocalAlarm Action

0.0.13.3100.0.9.6 inhibitAudibleVisualLocalAlarm Action

OID Name Type

0.0.13.3100.0.7.1 a-TPInstance Attribute

0.0.13.3100.0.7.2 affectedObjectList Attribute

0.0.13.3100.0.7.5 alarmSeverityAssignmentProfilePointer Attribute

0.0.13.3100.0.7.6 alarmStatus Attribute

0.0.13.3100.0.7.7 channelNumber Attribute

0.0.13.3100.0.7.8 characteristicInformation Attribute

0.0.13.3100.0.7.10 clientTrail Attribute

0.0.13.3100.0.7.12 connectionId Attribute

0.0.13.3100.0.7.13 cTPId Attribute

0.0.13.3100.0.7.16 crossConnectionObjectPointer Attribute

0.0.13.3100.0.7.17 currentProblemList Attribute

0.0.13.3100.0.7.18 directionality Attribute

0.0.13.3100.0.7.19 downstreamConnectivityPointer Attribute

0.0.13.3100.0.7.20 equipmentId Attribute

0.0.13.3100.0.7.21 externalTime Attribute

0.0.13.3100.0.7.27 locationName Attribute

0.0.13.3100.0.7.28 managedElementId Attribute

0.0.13.3100.0.7.30 networkId Attribute

(1 of 2)



Table B-10 ITU-T M.3100 OID values—name bindings

0.0.13.3100.0.7.31 networkLevelPointer Attribute

0.0.13.3100.0.7.32 protected Attribute

0.0.13.3100.0.7.34 replaceable Attribute

0.0.13.3100.0.7.35 serverConnectionList Attribute

0.0.13.3100.0.7.36 serverTrailList Attribute

0.0.13.3100.0.7.39 supportableClientList Attribute

0.0.13.3100.0.7.40 supportedByObjectList Attribute

0.0.13.3100.0.7.41 systemTimingSource Attribute

0.0.13.3100.0.7.47 trailId Attribute

0.0.13.3100.0.7.48 tTPId Attribute

0.0.13.3100.0.7.49 upstreamConnectivityPointer Attribute

0.0.13.3100.0.7.50 userLabel Attribute

0.0.13.3100.0.7.51 vendorName Attribute

0.0.13.3100.0.7.52 version Attribute

0.0.13.3100.0.7.53 clientConnectionList Attribute

0.0.13.3100.0.7.54 circuitPackType Attribute

0.0.13.3100.0.7.55 z-TPInstance Attribute

0.0.13.3100.0.7.56 equipmentHolderAddress Attribute

0.0.13.3100.0.7.57 equipmentHolderType Attribute

0.0.13.3100.0.7.58 acceptableCircuitPackTypeList Attribute

0.0.13.3100.0.7.59 holderStatus Attribute

0.0.13.3100.0.7.60 subordinateCircuitPackSoftwareLoad Attribute

0.0.13.3100.0.7.69 serialNumber Attribute

OID Name Type

0.0.13.3100.0.6.3 connectionTerminationPointSource-trailTerminationPointSource

Name binding

0.0.13.3100.0.6.4 connectionTerminationPointSource-trailTerminationPointBidirectional

Name binding

0.0.13.3100.0.6.5 connectionTerminationPointSink-trailTerminationPointSink

Name binding

0.0.13.3100.0.6.6 connectionTerminationPointSink-trailTerminationPointBidirectional

Name binding

0.0.13.3100.0.6.9 equipment-managedElement Name binding

0.0.13.3100.0.6.10 equipment-equipment Name binding

0.0.13.3100.0.6.11 eventForwardingDiscriminator-managedElement Name binding

(1 of 2)

OID Name Type

(2 of 2)



Table B-11 ITU-T M.3100 OID values—object classes

0.0.13.3100.0.6.15 managedElement-network Name binding

0.0.13.3100.0.6.17 network-network Name binding

0.0.13.3100.0.6.23 trailTerminationPointSource-managedElement Name binding

0.0.13.3100.0.6.24 trailTerminationPointSink-managedElement Name binding

0.0.13.3100.0.6.25 connectionR1-network Name binding

0.0.13.3100.0.6.26 trailR1-network Name binding

0.0.13.3100.0.6.30 network-rootNB Name binding

0.0.13.3100.0.6.31 equipmentHolder-equipmentHolder Name binding

0.0.13.3100.0.6.32 circuitPack-equipmentHolder-autoCreated Name binding

0.0.13.3100.0.6.33 circuitPack-equipmentHolder-explicitlyCreated Name binding

OID Name Type

0.0.13.3100.0.3.1 network Object class

0.0.13.3100.0.3.2 equipment Object class

0.0.13.3100.0.3.3 managedElement Object class

0.0.13.3100.0.3.5 connectionTerminationPointBidirectional Object class

0.0.13.3100.0.3.6 connectionTerminationPointSink Object class

0.0.13.3100.0.3.7 connectionTerminationPointSource Object class

0.0.13.3100.0.3.8 terminationPoint Object class

0.0.13.3100.0.3.9 trailTerminationPointBidirectional Object class

0.0.13.3100.0.3.10 trailTerminationPointSink Object class

0.0.13.3100.0.3.11 trailTerminationPointSource Object class

0.0.13.3100.0.3.23 connectionR1 Object class

0.0.13.3100.0.3.24 npipe Object class

0.0.13.3100.0.3.25 trailR1 Object class

0.0.13.3100.0.3.28 equipmentR1 Object class

0.0.13.3100.0.3.30 circuitPack Object class

0.0.13.3100.0.3.32 equipmentHolder Object class

OID Name Type

(2 of 2)



Table B-12 ITU-T M.3100 OID values—packages

OID Name Type

0.0.13.3100.0.4.2 affectedObjectListPackage Package

0.0.13.3100.0.4.3 alarmSeverityAssignmentPointerPackage Package

0.0.13.3100.0.4.4 attributeValueChangeNotificationPackage Package

0.0.13.3100.0.4.5 audibleVisualLocalAlarmPackage Package

0.0.13.3100.0.4.6 channelNumberPackage Package

0.0.13.3100.0.4.7 characteristicInformationPackage Package

0.0.13.3100.0.4.9 clientTrailPackage Package

0.0.13.3100.0.4.10 createDeleteNotificationsPackage Package

0.0.13.3100.0.4.11 crossConnectionPointerPackage Package

0.0.13.3100.0.4.12 ctpInstancePackage Package

0.0.13.3100.0.4.13 currentProblemListPackage Package

0.0.13.3100.0.4.14 environmentalAlarmPackage Package

0.0.13.3100.0.4.16 externalTimePackage Package

0.0.13.3100.0.4.17 locationNamePackage Package

0.0.13.3100.0.4.18 networkLevelPackage Package

0.0.13.3100.0.4.19 operationalStatePackage Package

0.0.13.3100.0.4.21 processingErrorAlarmPackage Package

0.0.13.3100.0.4.22 protectedPackage Package

0.0.13.3100.0.4.23 resetAudibleAlarmPackage Package

0.0.13.3100.0.4.24 serverConnectionListPackage Package

0.0.13.3100.0.4.25 serverTrailListPackage Package

0.0.13.3100.0.4.27 supportableClientListPackage Package

0.0.13.3100.0.4.28 stateChangeNotificationPackage Package

0.0.13.3100.0.4.29 systemTimingSourcePackage Package

0.0.13.3100.0.4.30 tmnCommunicationsAlarmInformationPackage Package

0.0.13.3100.0.4.31 ttpInstancePackage Package

0.0.13.3100.0.4.32 userLabelPackage Package

0.0.13.3100.0.4.33 vendorNamePackage Package

0.0.13.3100.0.4.34 versionPackage Package

0.0.13.3100.0.4.35 clientConnectionListPackage Package

0.0.13.3100.0.4.36 environmentalAlarmR1Package Package

0.0.13.3100.0.4.39 processingErrorAlarmR1Package Package

0.0.13.3100.0.4.41 subordinateCircuitPackPackage Package



Table B-13 ITU-T M.3100 OID values—parameters

B.5 ITU-T Q.821

These OID values are based on the ITU-T standard Q.821. Tables App B-14 to App B-20 list the OID values for actions, attributes, name bindings, notifications, objects, packages, and parameters, respectively.

Table B-14 Q.821 OID values—actions

Table B-15 Q.821 OID values—attributes

OID Name Type

0.0.13.3100.0.5.1 alarmEffectOnServiceParameter Parameter

0.0.13.3100.0.5.2 createErrorParameter Parameter

OID Name Type

0.0.17.821.0.9.1 retrieveCurrentAlarmSummary Action

0.0.17.821.0.9.2 resetAudibleAlarm Action

OID Name Type

0.0.17.821.0.7.1 affectedObjectClass Attribute

0.0.17.821.0.7.2 affectedObjectInstances Attribute

0.0.17.821.0.7.3 alarmStatusList Attribute

0.0.17.821.0.7.4 beginTime Attribute

0.0.17.821.0.7.5 currentAlarmSummaryControlId Attribute

0.0.17.821.0.7.6 destinationAddress Attribute

0.0.17.821.0.7.7 endTime Attribute

0.0.17.821.0.7.8 interval Attribute

0.0.17.821.0.7.9 objectList Attribute

0.0.17.821.0.7.10 perceivedSeverityList Attribute

0.0.17.821.0.7.11 probableCauseList Attribute

0.0.17.821.0.7.12 scheduleId Attribute



Table B-16 Q.821 OID values—name bindings

Table B-17 Q.821 OID values—notifications

Table B-18 Q.821 OID values—object classes

Table B-19 Q.821 OID values—packages

Table B-20 Q.821 OID values—parameters

B.6 ITU-T X.721

These OID values are based on the ITU-T standard X.721. Tables App B-21 to App B-25 list the OID values for attributes, name bindings, notifications, objects, and packages, respectively.

OID Name Type

0.0.17.821.0.6.1 currAlarmSumControl-managedElement Name binding

0.0.17.821.0.6.2 managementOperationsSchedule-managedElement

Name binding

OID Name Type

0.0.17.821.0.10.1 currentAlarmSummaryReport Notification

OID Name Type

0.0.17.821.0.3.1 currentAlarmSummaryControl Object class

0.0.17.821.0.3.2 managementOperationsSchedule Object class

OID Name Type

0.0.17.821.0.4.1 managementOperationsScheduleOperationalStatePkg

Package

OID Name Type

0.0.17.821.0.5.1 logRecordIdParameter Parameter

0.0.17.821.0.5.2 correlatedRecordNameParameter Parameter

0.0.17.821.0.5.3 suspectObjectListParameter Parameter



Table B-21 ITU-T X.721 OID values—attributes

OID Name Type

2.9.3.2.7.1 discriminatorId Attribute

2.9.3.2.7.2 logId Attribute

2.9.3.2.7.3 logRecordId Attribute

2.9.3.2.7.4 systemId Attribute

2.9.3.2.7.5 systemTitle Attribute

2.9.3.2.7.6 additionalInformation Attribute

2.9.3.2.7.7 additionalText Attribute

2.9.3.2.7.8 attributeIdentifierList Attribute

2.9.3.2.7.9 attributeList Attribute

2.9.3.2.7.10 attributeValueChangeDefinition Attribute

2.9.3.2.7.11 backedUpStatus Attribute

2.9.3.2.7.12 correlatedNotifications Attribute

2.9.3.2.7.13 eventTime Attribute

2.9.3.2.7.14 eventType Attribute

2.9.3.2.7.15 monitoredAttributes Attribute

2.9.3.2.7.16 notificationIdentifier Attribute

2.9.3.2.7.17 perceivedSeverity Attribute

2.9.3.2.7.18 probableCause Attribute

2.9.3.2.7.19 proposedRepairActions Attribute

2.9.3.2.7.20 relationshipChangeDefinition Attribute

2.9.3.2.7.21 securityAlarmCause Attribute

2.9.3.2.7.22 securityAlarmDetector Attribute

2.9.3.2.7.23 securityAlarmSeverity Attribute

2.9.3.2.7.24 serviceProvider Attribute

2.9.3.2.7.25 serviceUser Attribute

2.9.3.2.7.26 sourceIndicator Attribute

2.9.3.2.7.27 specificProblems Attribute

2.9.3.2.7.28 stateChangeDefinition Attribute

2.9.3.2.7.29 thresholdInfo Attribute

2.9.3.2.7.30 trendIndication Attribute

2.9.3.2.7.31 administrativeState Attribute

2.9.3.2.7.33 availabilityStatus Attribute

2.9.3.2.7.34 controlStatus Attribute

2.9.3.2.7.35 operationalState Attribute

2.9.3.2.7.36 proceduralStatus Attribute

(1 of 2)



Table B-22 ITU-T X.721 OID values—name bindings

2.9.3.2.7.39 usageState Attribute

2.9.3.2.7.40 backUpObject Attribute

2.9.3.2.7.49 activeDestination Attribute

2.9.3.2.7.50 allomorphs Attribute

2.9.3.2.7.51 backUpDestinationList Attribute

2.9.3.2.7.52 capacityAlarmThreshold Attribute

2.9.3.2.7.53 confirmedMode Attribute

2.9.3.2.7.54 currentLogSize Attribute

2.9.3.2.7.55 destination Attribute

2.9.3.2.7.56 discriminatorConstruct Attribute

2.9.3.2.7.57 intervalsOfDay Attribute

2.9.3.2.7.58 logFullAction Attribute

2.9.3.2.7.59 loggingTime Attribute

2.9.3.2.7.60 managedObjectClass Attribute

2.9.3.2.7.61 managedObjectInstance Attribute

2.9.3.2.7.62 maxLogSize Attribute

2.9.3.2.7.63 nameBinding Attribute

2.9.3.2.7.64 numberOfRecords Attribute

2.9.3.2.7.65 objectClass Attribute

2.9.3.2.7.66 packages Attribute

2.9.3.2.7.67 schedulerName Attribute

2.9.3.2.7.68 startTime Attribute

2.9.3.2.7.69 stopTime Attribute

2.9.3.2.7.70 supportedFeatures Attribute

2.9.3.2.7.71 weekMask Attribute

OID Name Type

2.9.3.2.6.1 discriminator-system Name binding

2.9.3.2.6.2 log-system Name binding

2.9.3.2.6.3 logRecord-log Name binding

OID Name Type

(2 of 2)



Table B-23 ITU-T X.721 OID values—notifications

Table B-24 ITU-T X.721 OID values—object classes

Table B-25 ITU-T X.721 OID values—packages

OID Name Type

2.9.3.2.10.1 attributeValueChange Notification

2.9.3.2.10.2 communicationsAlarm Notification

2.9.3.2.10.3 environmentalAlarm Notification

2.9.3.2.10.4 equipmentAlarm Notification

2.9.3.2.10.6 objectCreation Notification

2.9.3.2.10.7 objectDeletion Notification

2.9.3.2.10.10 processingErrorAlarm Notification

2.9.3.2.10.11 qualityOfServiceAlarm Notification

2.9.3.2.10.14 stateChange Notification

OID Name Type

2.9.3.2.3.1 alarmRecord Object class

2.9.3.2.3.2 attributeValueChangeRecord Object class

2.9.3.2.3.3 discriminator Object class

2.9.3.2.3.4 eventForwardingDiscriminator Object class

2.9.3.2.3.5 eventLogRecord Object class

2.9.3.2.3.6 log Object class

2.9.3.2.3.7 logRecord Object class

2.9.3.2.3.8 objectCreationRecord Object class

2.9.3.2.3.9 objectDeletionRecord Object class

2.9.3.2.3.10 relationshipChangeRecord Object class

2.9.3.2.3.11 securityAlarmReportRecord Object class

2.9.3.2.3.12 stateChangeRecord Object class

2.9.3.2.3.13 system Object class

2.9.3.2.3.14 top Object class

OID Name Type

2.9.3.2.4.1 specificProblemsPackage Package

2.9.3.2.4.2 backedUpStatusPackage Package

2.9.3.2.4.3 backUpObjectPackage Package

(1 of 2)



B.7 ITU-T X.745

These OID values are based on the ITU-T standard X.745. Tables App B-26 to App B-30 list the OID values for actions, attributes, objects, packages, and parameters, respectively.

2.9.3.2.4.4 trendIndicationPackage Package

2.9.3.2.4.5 thresholdInfoPackage Package

2.9.3.2.4.6 stateChangeDefinitionPackage Package

2.9.3.2.4.7 monitoredAttributesPackage Package

2.9.3.2.4.8 proposedRepairActionsPackage Package

2.9.3.2.4.9 backUpDestinationListPackage Package

2.9.3.2.4.10 modePackage Package

2.9.3.2.4.11 eventTimePackage Package

2.9.3.2.4.12 finiteLogSizePackage Package

2.9.3.2.4.13 logAlarmPackage Package

2.9.3.2.4.14 administrativeStatePackage Package

2.9.3.2.4.15 supportedFeaturesPackage Package

2.9.3.2.4.16 packagesPackage Package

2.9.3.2.4.17 allomorphicPackage Package

2.9.3.2.4.18 additionalInformationPackage Package

2.9.3.2.4.19 additionalTextPackage Package

2.9.3.2.4.20 attributeIdentifierListPackage Package

2.9.3.2.4.21 attributeListPackage Package

2.9.3.2.4.22 availabilityStatusPackage Package

2.9.3.2.4.23 correlatedNotificationsPackage Package

2.9.3.2.4.24 notificationIdentifierPackage Package

2.9.3.2.4.25 dailyScheduling Package

2.9.3.2.4.26 duration Package

2.9.3.2.4.27 externalScheduler Package

2.9.3.2.4.28 sourceIndicatorPackage Package

2.9.3.2.4.29 weeklyScheduling Package

OID Name Type

(2 of 2)



Table B-26 X.745 OID values—actions

Table B-27 X.745 OID values—attributes

Table B-28 X.745 OID values—object classes

Table B-29 X.745 OID values—packages

OID Name Type

2.9.2.12.9.1 testRequestControlledAction Action

2.9.2.12.9.2 testSuspendResumeAction Action

2.9.2.12.9.3 testTerminateAction Action

2.9.2.12.9.4 testRequestUncontrolledAction Action

OID Name Type

2.9.2.12.7.3 associatedObjects Attribute

2.9.2.12.7.6 mORTs Attribute

2.9.2.12.7.7 supportedTOClasses Attribute

2.9.2.12.7.8 supportedUncontrolledTests Attribute

2.9.2.12.7.9 testActionPerformerId Attribute

2.9.2.12.7.10 testInvocationId Attribute

2.9.2.12.7.11 testObjectId Attribute

2.9.2.12.7.12 testOutcome Attribute

2.9.2.12.7.13 testSessionId Attribute

OID Name Type

2.9.2.12.3.2 testActionPerformer Object class

2.9.2.12.3.3 testObject Object class

OID Name Type

2.9.2.12.4.2 associatedObjectsPackage Package

2.9.2.12.4.3 controlledTestRequestPackage Package

2.9.2.12.4.5 mORTsPackage Package

2.9.2.12.4.7 supportedTOClassesPackage Package

2.9.2.12.4.8 supportedUncontrolledTestsPackage Package

2.9.2.12.4.12 testOutcomePackage Package

(1 of 2)



Table B-30 X.745 OID values—parameters

B.8 Association management extension

Table App B-31 lists the OID value in the association management extension.

Table B-31 Association management extensions OID values—alarms

2.9.2.12.4.14 testSessionPackage Package

2.9.2.12.4.16 testSuspendResumePackage Package

2.9.2.12.4.17 testTerminatePackage Package

2.9.2.12.4.18 tOControlStatusPackage Package

2.9.2.12.4.19 uncontrolledTestRequestPackage Package

OID Name Type

2.9.2.12.5.1 associatedObjectNotAvailable Parameter

2.9.2.12.5.2 independentTestInvocationError Parameter

2.9.2.12.5.3 invalidTestOperation Parameter

2.9.2.12.5.4 mistypedTestCategoryInformation Parameter

2.9.2.12.5.5 mORTNotAvailable Parameter

2.9.2.12.5.6 noSuchAssociatedObject Parameter

2.9.2.12.5.7 noSuchMORT Parameter

2.9.2.12.5.8 noSuchTestInvocationId Parameter

2.9.2.12.5.9 noSuchTestSessionId Parameter

2.9.2.12.5.10 relatedTOError Parameter

2.9.2.12.5.11 testSuspendResumeError Parameter

2.9.2.12.5.12 testTerminateError Parameter

OID Name Type

(2 of 2)

OID Name Type

2.9.0.0.2 Manager - Agent application context name, used to identify the sender

Application context



B.9 Fault management extensions

These OID values are extensions to the ITU-T standards X.721 and X.736. Table App B-32 lists the probableCause OID values for alarms. Table App B-33 lists the extensions for bMGroomedCircuit object alarms. Table App B-34 lists the extensions for ATM circuit emulation card managedFacilityTP object alarms. Table B-35 lists the extensions for alarm attributes.

Table B-32 Fault management extensions OID values—alarms

Notes(1) Applies to bMFacility, managedFacilityTP and bMGroomedCircuit objects(2) Applies to managedElement and managedPack objects(3) Applies to managedElement objects modeling the 5620 CMIP(4) From securityAlarmCause; defined in ITU-T X.721 and X.736(5) Applies to managedFacilityTP object(6) Applies to log object

Table B-33 Fault management extensions OID values—bMGroomedCircuit alarms

OID Name Type

2.9.3.2.0.0.6 (1) Communications subsystem failure ProbableCause

2.9.3.2.0.0.15 (2) Equipment malfunction ProbableCause

2.9.3.2.0.0.28 (5) Loss of frame ProbableCause

2.9.3.2.0.0.29 (5) Loss of signal ProbableCause

2.9.3.2.0.0.39 (3) Queue size exceeded ProbableCause

2.9.3.2.0.0.46 (3) Software error ProbableCause

2.9.3.2.0.0.47 (3) Software program abnormally terminated ProbableCause

2.9.3.2.0.0.49 (6) Storage capacity problem ProbableCause

2.9.3.2.0.0.56 (3) Underlying resource unavailable ProbableCause

2.9.3.2.0.1.9 (3) (4) Information out of sequence Alarm

OID Name Type

1.2.124.113537.1.9.1 Disconnected ProbableCause

1.2.124.113537.1.9.2 Disconnected (timed lock set) ProbableCause

1.2.124.113537.1.9.3 Disconnected (disruption by another user) ProbableCause

1.2.124.113537.1.9.4 Disconnected (none) ProbableCause

1.2.124.113537.1.9.5 Bumped (higher priority call) ProbableCause

1.2.124.113537.1.9.6 Activated ProbableCause

1.2.124.113537.1.9.7 Activated (immediately) ProbableCause

1.2.124.113537.1.9.8 Activated (timed unlock) ProbableCause

1.2.124.113537.1.9.9 Activated (reroute) ProbableCause

(1 of 2)



1.2.124.113537.1.9.10 Activated (recovery) ProbableCause

1.2.124.113537.1.9.11 Activated (bumped) ProbableCause

1.2.124.113537.1.9.12 Activated (uploaded) ProbableCause

1.2.124.113537.1.9.13 Activated (begin optimizing) ProbableCause

1.2.124.113537.1.9.14 Activated (optimized) ProbableCause

1.2.124.113537.1.9.15 Activated (none) ProbableCause

1.2.124.113537.1.9.16 Down (immediately) ProbableCause

1.2.124.113537.1.9.17 Down (timed) ProbableCause

1.2.124.113537.1.9.18 Down (reroute) ProbableCause

1.2.124.113537.1.9.19 Down (recover) ProbableCause

1.2.124.113537.1.9.20 Down (upload) ProbableCause

1.2.124.113537.1.9.21 Down (bumped) ProbableCause

1.2.124.113537.1.9.22 Down (optimized) ProbableCause

1.2.124.113537.1.9.23 Down ProbableCause

1.2.124.113537.1.9.24 No route to source ProbableCause

1.2.124.113537.1.9.25 No route to source (bumped) ProbableCause

1.2.124.113537.1.9.26 No route to source (rerouted) ProbableCause

1.2.124.113537.1.9.27 Failed ProbableCause

1.2.124.113537.1.9.28 Affected by NMTI ProbableCause

1.2.124.113537.1.9.29 Affected by NMTI (cleared) ProbableCause

1.2.124.113537.1.9.30 Suspect reroute ProbableCause

1.2.124.113537.1.9.31 Atomic set (failed) ProbableCause

1.2.124.113537.1.9.32 Atomic set (connect) ProbableCause

1.2.124.113537.1.9.33 Atomic set (disconnect) ProbableCause

1.2.124.113537.1.9.34 Atomic set (no route to source) ProbableCause

1.2.124.113537.1.9.35 Under maintenance ProbableCause

1.2.124.113537.1.9.36 Under maintenance (cleared) ProbableCause

1.2.124.113537.1.9.37 Intrusive maintenance or loopback ProbableCause

1.2.124.113537.1.9.38 Intrusive maintenance or loopback (cleared) ProbableCause

1.2.124.113537.1.9.39 Activated (optimize failed) ProbableCause

1.2.124.113537.1.9.40 Down (optimized failed) ProbableCause

OID Name Type

(2 of 2)



Table B-34 Fault management extensions OID values—ATM circuit emulation card managedFacilityTP alarms

OID Name Type

1.2.124.113537.1.8.1 Receive Remote Device Indication Failure ProbableCause

1.2.124.113537.1.8.2 Transmit Remote Device Indication Failure ProbableCause

1.2.124.113537.1.8.3 Receive Alarm Indication Signal ProbableCause

1.2.124.113537.1.8.4 Transmit Alarm Indication Signal ProbableCause

1.2.124.113537.1.8.5 Loopback State ProbableCause

1.2.124.113537.1.8.6 Test Code ProbableCause

1.2.124.113537.1.8.7 Other Failure ProbableCause

1.2.124.113537.1.8.8 Idle ProbableCause

1.2.124.113537.1.8.9 Far End Equipment Failure ProbableCause

1.2.124.113537.1.8.10 Far End Alarm Indication Signal ProbableCause

1.2.124.113537.1.8.11 Far End Loss Of Frame ProbableCause

1.2.124.113537.1.8.12 Far End Loss Of Signal ProbableCause

1.2.124.113537.1.8.13 ALC mismatch ProbableCause

1.2.124.113537.1.8.14 Ingress Alarm Indication Signal ProbableCause

1.2.124.113537.1.8.15 Ingress RAI ProbableCause

1.2.124.113537.1.8.16 Ingress Starvation ProbableCause

1.2.124.113537.1.8.17 Ingress Overflow ProbableCause

1.2.124.113537.1.8.18 Ingress Loss Of Frame ProbableCause

1.2.124.113537.1.8.19 Egress Alarm Indication Signal ProbableCause

1.2.124.113537.1.8.20 Egress RAI ProbableCause

1.2.124.113537.1.8.21 Egress Starvation ProbableCause

1.2.124.113537.1.8.22 Egress Overflow ProbableCause

1.2.124.113537.1.8.23 Egress Loss Of Frame ProbableCause

1.2.124.113537.1.8.24 Egress Other Failure ProbableCause

1.2.124.113537.1.8.25 Line Alarm Indication Signal ProbableCause

1.2.124.113537.1.8.26 Line Remote Device Indication ProbableCause

1.2.124.113537.1.8.27 Section Loss Of Signal ProbableCause

1.2.124.113537.1.8.28 Section Loss Of Frame ProbableCause

1.2.124.113537.1.8.29 Path Synchronous Transport Signal Loss Of Pointer

ProbableCause

1.2.124.113537.1.8.30 Path Synchronous Transport Signal Alarm Indication Signal

ProbableCause

1.2.124.113537.1.8.31 Path Synchronous Transport Signal Remote Device Indication

Alarm

1.2.124.113537.1.8.32 Path Unequipped Alarm

1.2.124.113537.1.8.33 Path SLM Alarm

(1 of 2)



Table B-35 Fault management extensions OID values—attributes

B.10 Path management extensions

These OID values are extensions to TMF standard 038 and ITU-T standard M.3100. Table App B-37 lists the OID values for attributes and Table App B-38 lists the OIDs for objects.

Table B-36 Pathmanagement extensions OID values—actions

Table B-37 Path management extensions OID values—attributes

1.2.124.113537.1.8.34 Loss Of Cell Deletion Alarm

1.2.124.113537.1.8.35 Loss of Frame Alarm

1.2.124.113537.1.8.36 Control framing error Alarm

OID Name Type

1.2.124.113537.1.7.1 additionalAlarmInformationType Attribute

OID Name Type

(2 of 2)

OID Name Type

1.2.124.113537.1.3.21 listFreeManagedGroomedCircuitTPs Action

1.2.124.113537.1.3.22 listUsedManagedGroomedCircuitTPs Action

1.2.124.113537.1.3.23 listFreeVPIs Action

1.2.124.113537.1.3.24 listUsedVCIs Action

OID Name Type

1.2.124.113537.1.4.1 packProfile Attribute

1.2.124.113537.1.4.2 groomedCircuitTPProfile Attribute

1.2.124.113537.1.4.3 facilityTPProfile Attribute

1.2.124.113537.1.4.4 managedEquipmentType Attribute

1.2.124.113537.1.4.18 managedProfileId Attribute

1.2.124.113537.1.4.19 managedProfileType Attribute

1.2.124.113537.1.4.20 managedProfileName Attribute

1.2.124.113537.1.4.21 managedProfileTranspending Attribute

1.2.124.113537.1.4.22 managedProfileProf Attribute

1.2.124.113537.1.4.30 pnniProfile Attribute

(1 of 2)



Table B-38 Path management extensions OID values—object classes

B.11 Test management extensions

These OID values are extensions to the ITU-T standard X.745. Tables App B-39 to App B-44 list the OID values for actions, attributes, name bindings, objects, parameters, and modules respectively.

Table B-39 Test management extensions OID values—actions

1.2.124.113537.1.4.34 pnniSummaryAddressProfile Attribute

1.2.124.113537.1.4.26 elementExtensionsId Attribute

1.2.124.113537.1.4.27 elementProfile Attribute

1.2.124.113537.1.4.28 ntCommissioningProfile Attribute

OID Name Type

1.2.124.113537.1.1.1 managedPack Object class

1.2.124.113537.1.1.2 managedGroomedCircuitTP Object class

1.2.124.113537.1.1.3 managedFacilityTP Object class

1.2.124.113537.1.1.4 managedEquipment Object class

1.2.124.113537.1.1.10 managedProfile Object class

1.2.124.113537.1.6.8 elementExtensions Object class

OID Name Type

(2 of 2)

OID Name Type

1.2.124.113537.1.3.1 testRelease Action

1.2.124.113537.1.3.2 testMonitor Action

1.2.124.113537.1.3.3 testSplitThru Action

1.2.124.113537.1.3.4 testSplitBack Action

1.2.124.113537.1.3.5 lbRelease Action

1.2.124.113537.1.3.6 lbLine Action

1.2.124.113537.1.3.7 lbEquipment Action

1.2.124.113537.1.3.8 boRelease Action

1.2.124.113537.1.3.9 boLink Action

1.2.124.113537.1.3.10 oam-cell Action

1.2.124.113537.1.3.11 releaseTAC Action

1.2.124.113537.1.3.12 monitorTAC Action

(1 of 2)



Table B-40 Test management extensions OID values—attributes

1.2.124.113537.1.3.13 splitBackTAC Action

1.2.124.113537.1.3.14 splitLoopTAC Action

1.2.124.113537.1.3.15 spvcPathTrace Action

1.2.124.113537.1.3.16 spvcConnectionTrace Action

1.2.124.113537.1.3.17 findByLabel Action

1.2.124.113537.1.3.19 listPaths Action

1.2.124.113537.1.3.20 hitlessConnectionMove Action

1.2.124.113537.1.3.25 retrieveActiveAlarms Action

1.2.124.116537.1.3.26 configureRealTimeStatistics Action

1.2.124.113537.1.3.27 collectRealTimeStatistics Action

1.2.124.113537.1.3.28 cancelRealTimeStatistics Action

1.2.124.113537.1.3.29 determineSupportedStatistics Action

1.2.124.113537.1.3.39 addChannelsToMux Action

1.2.124.113537.1.3.40 removeChannelsFromMux Action

1.2.124.113537.1.3.41 listChannelsUsedByMux Action

1.2.124.113537.1.3.42 listLinks Action

1.2.124.113537.1.3.43 connectionTrace Action

1.2.124.113537.1.3.44 listCustomAttributeNames Action

1.2.124.113537.1.3.45 retrieveISLInfo Action

OID Name Type

1.2.124.113537.1.4.5 testType Attribute

1.2.124.113537.1.4.6 testName Attribute

1.2.124.113537.1.4.7 testObjectName Attribute

1.2.124.113537.1.4.8 lbTestType Attribute

1.2.124.113537.1.4.9 lbTestName Attribute

1.2.124.113537.1.4.10 lbRecoveryType Attribute

1.2.124.113537.1.4.11 boTestType Attribute

1.2.124.113537.1.4.12 boTestName Attribute

1.2.124.113537.1.4.13 boRecoveryType Attribute

1.2.124.113537.1.4.14 oAMTestName Attribute

1.2.124.113537.1.4.15 oAMReturnPointType Attribute

1.2.124.113537.1.4.16 tacTestType Attribute

1.2.124.113537.1.4.17 tacTestProfile Attribute

(1 of 2)

OID Name Type

(2 of 2)



Table B-41 Test management extensions OID values—name bindings

Table B-42 Test management extensions OID values—objects

Table B-43 Test management extensions OID values—parameters

1.2.124.113537.1.4.23 traceTestName Attribute

1.2.124.113537.1.4.24 traceTestType Attribute

1.2.124.113537.1.4.25 traceTestProfile Attribute

1.2.124.113537.1.4.29 oAMCellAssociatedObjectInfo Attribute

1.2.124.113537.1.4.31 actionName Attribute

1.2.124.113537.1.4.32 actionType Attribute

1.2.124.113537.1.4.33 actionProfile Attribute

OID Name Type

1.2.124.113537.1.2.5 testActionPerformer-network Name binding

1.2.124.113537.1.2.6 splitMonitorTestObject-testActionPerformer Name binding

1.2.124.113537.1.2.7 loopBackTestObject-testActionPerformer Name binding

1.2.124.113537.1.2.8 busyOutTestObject-testActionPerformer Name binding

1.2.124.113537.1.2.9 oAMCellTestObject-testActionPerformer Name binding

1.2.124.113537.1.2.10 testAccessConnectionObject-testActionPerformer Name binding

1.2.124.113537.1.2.13 traceTestObject-testActionPerformer Name binding

OID Name Type

1.2.124.113537.1.1.5 splitMonitorTestObject Object

1.2.124.113537.1.1.6 loopBackTestObject Object

1.2.124.113537.1.1.7 busyOutTestObject Object

1.2.124.113537.1.1.8 oAMCellTestObject Object

1.2.124.113537.1.1.9 testAccessConnectionObject Object

1.2.124.113537.1.1.11 traceTestObject Object

1.2.124.113537.1.1.13 genericActionObject Object

OID Name Type

1.2.124.113537.1.5.1 connsFailure Parameter

1.2.124.113537.1.5.2 lbNotSupportedTest Parameter

(1 of 2)

OID Name Type

(2 of 2)



Table B-44 Test management extensions OID values—modules

1.2.124.113537.1.5.3 boNotSupportedTest Parameter

1.2.124.113537.1.5.4 oAMNotSupportedTest Parameter

1.2.124.113537.1.5.5 tacNotSupportedTest Parameter

OID Name Type

1.2.124.113537.1.6.10 genericActionObject Module

OID Name Type

(2 of 2)

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 C-1October 2006 95-6040-01-00-C


C.1 Numerically arranged 5620 CMIP OIDs C-2

C.2 Alphabetically-arranged 5620 CMIP OIDs C-17


C-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

C.1 Numerically arranged 5620 CMIP OIDs

This section lists all the 5620 CMIP OIDs numerically. Table App C-1 lists the OIDs that begin with 0; Table App C-2 lists the OIDs that begin with 1; Table App C-3 lists the OIDs that begin with 2.

See Appendix B for lists of OIDs arranged in accordance with the standards to which they adhere.

Table C-1 OIDS beginning with 0

OID Name

0.0.13.3100.0.3.X—Object classes

0.0.13.3100.0.3.1 network

0.0.13.3100.0.3.2 equipment

0.0.13.3100.0.3.3 managedElement

0.0.13.3100.0.3.5 connectionTerminationPointBidirectional

0.0.13.3100.0.3.6 connectionTerminationPointSink

0.0.13.3100.0.3.7 connectionTerminationPointSource

0.0.13.3100.0.3.8 terminationPoint

0.0.13.3100.0.3.9 trailTerminationPointBidirectional

0.0.13.3100.0.3.10 trailTerminationPointSink

0.0.13.3100.0.3.11 trailTerminationPointSource

0.0.13.3100.0.3.23 connectionR1

0.0.13.3100.0.3.24 npipe

0.0.13.3100.0.3.25 trailR1

0.0.13.3100.0.3.28 equipmentR1

0.0.13.3100.0.3.30 circuitPack

0.0.13.3100.0.3.32 equipmentHolder

0.0.13.3100.0.4.X—Packages

0.0.13.3100.0.4.2 affectedObjectListPackage

0.0.13.3100.0.4.3 alarmSeverityAssignmentPointerPackage

0.0.13.3100.0.4.4 attributeValueChangeNotificationPackage

0.0.13.3100.0.4.5 audibleVisualLocalAlarmPackage

0.0.13.3100.0.4.6 channelNumberPackage

0.0.13.3100.0.4.7 characteristicInformationPackage

0.0.13.3100.0.4.9 clientTrailPackage

0.0.13.3100.0.4.10 createDeleteNotificationsPackage

0.0.13.3100.0.4.11 crossConnectionPointerPackage

0.0.13.3100.0.4.12 ctpInstancePackage

(1 of 5)



0.0.13.3100.0.4.13 currentProblemListPackage

0.0.13.3100.0.4.14 environmentalAlarmPackage

0.0.13.3100.0.4.16 externalTimePackage

0.0.13.3100.0.4.17 locationNamePackage

0.0.13.3100.0.4.18 networkLevelPackage

0.0.13.3100.0.4.19 operationalStatePackage

0.0.13.3100.0.4.21 processingErrorAlarmPackage

0.0.13.3100.0.4.22 protectedPackage

0.0.13.3100.0.4.23 resetAudibleAlarmPackage

0.0.13.3100.0.4.24 serverConnectionListPackage

0.0.13.3100.0.4.25 serverTrailListPackage

0.0.13.3100.0.4.27 supportableClientListPackage

0.0.13.3100.0.4.28 stateChangeNotificationPackage

0.0.13.3100.0.4.29 systemTimingSourcePackage

0.0.13.3100.0.4.30 tmnCommunicationsAlarmInformationPackage

0.0.13.3100.0.4.31 ttpInstancePackage

0.0.13.3100.0.4.32 userLabelPackage

0.0.13.3100.0.4.33 vendorNamePackage

0.0.13.3100.0.4.34 versionPackage

0.0.13.3100.0.4.35 clientConnectionListPackage

0.0.13.3100.0.4.36 environmentalAlarmR1Package

0.0.13.3100.0.4.39 processingErrorAlarmR1Package

0.0.13.3100.0.4.41 subordinateCircuitPackPackage

0.0.13.3100.0.5.X—Parameters

0.0.13.3100.0.5.1 alarmEffectOnServiceParameter

0.0.13.3100.0.5.2 createErrorParameter

0.0.13.3100.0.6.X—Name bindings

0.0.13.3100.0.6.3 connectionTerminationPointSource-trailTerminationPointSource

0.0.13.3100.0.6.4 connectionTerminationPointSource-trailTerminationPointBidirectional

0.0.13.3100.0.6.5 connectionTerminationPointSink-trailTerminationPointSink

0.0.13.3100.0.6.6 connectionTerminationPointSink-trailTerminationPointBidirectional

0.0.13.3100.0.6.9 equipment-managedElement

0.0.13.3100.0.6.10 equipment-equipment

0.0.13.3100.0.6.11 eventForwardingDiscriminator-managedElement

0.0.13.3100.0.6.15 managedElement-network

0.0.13.3100.0.6.17 network-network

0.0.13.3100.0.6.23 trailTerminationPointSource-managedElement

OID Name

(2 of 5)



0.0.13.3100.0.6.24 trailTerminationPointSink-managedElement

0.0.13.3100.0.6.25 connectionR1-network

0.0.13.3100.0.6.26 trailR1-network

0.0.13.3100.0.6.30 network-rootNB

0.0.13.3100.0.6.31 equipmentHolder-equipmentHolder

0.0.13.3100.0.6.32 circuitPack-equipmentHolder-autoCreated

0.0.13.3100.0.6.33 circuitPack-equipmentHolder-explicitlyCreated

0.0.13.3100.0.7.X—Attributes

0.0.13.3100.0.7.1 a-TPInstance

0.0.13.3100.0.7.2 affectedObjectList

0.0.13.3100.0.7.5 alarmSeverityAssignmentProfilePointer

0.0.13.3100.0.7.6 alarmStatus

0.0.13.3100.0.7.7 channelNumber

0.0.13.3100.0.7.8 characteristicInformation

0.0.13.3100.0.7.10 clientTrail

0.0.13.3100.0.7.12 connectionId

0.0.13.3100.0.7.13 cTPId

0.0.13.3100.0.7.16 crossConnectionObjectPointer

0.0.13.3100.0.7.17 currentProblemList

0.0.13.3100.0.7.18 directionality

0.0.13.3100.0.7.19 downstreamConnectivityPointer

0.0.13.3100.0.7.20 equipmentId

0.0.13.3100.0.7.21 externalTime

0.0.13.3100.0.7.27 locationName

0.0.13.3100.0.7.28 managedElementId

0.0.13.3100.0.7.30 networkId

0.0.13.3100.0.7.31 networkLevelPointer

0.0.13.3100.0.7.32 protected

0.0.13.3100.0.7.34 replaceable

0.0.13.3100.0.7.35 serverConnectionList

0.0.13.3100.0.7.36 serverTrailList

0.0.13.3100.0.7.39 supportableClientList

0.0.13.3100.0.7.40 supportedByObjectList

0.0.13.3100.0.7.41 systemTimingSource

0.0.13.3100.0.7.47 trailId

0.0.13.3100.0.7.48 tTPId

0.0.13.3100.0.7.49 upstreamConnectivityPointer

OID Name

(3 of 5)



0.0.13.3100.0.7.50 userLabel

0.0.13.3100.0.7.51 vendorName

0.0.13.3100.0.7.52 version

0.0.13.3100.0.7.53 clientConnectionList

0.0.13.3100.0.7.54 circuitPackType

0.0.13.3100.0.7.55 z-TPInstance

0.0.13.3100.0.7.56 equipmentHolderAddress

0.0.13.3100.0.7.57 equipmentHolderType

0.0.13.3100.0.7.58 acceptableCircuitPackTypeList

0.0.13.3100.0.7.59 holderStatus

0.0.13.3100.0.7.60 subordinateCircuitPackSoftwareLoad

0.0.13.3100.0.7.69 serialNumber

0.0.13.3100.0.9.X—Actions

0.0.13.3100.0.9.3 allowAudibleVisualLocalAlarm

0.0.13.3100.0.9.6 inhibitAudibleVisualLocalAlarm


0.0.17.821.0.3.1 currentAlarmSummaryControl

0.0.17.821.0.3.2 managementOperationsSchedule

0.0.17.821.0.4.X—Packages

0.0.17.821.0.4.1 managementOperationsScheduleOperationalStatePkg

0.0.17.821.0.5.X—Parameters

0.0.17.821.0.5.1 logRecordIdParameter

0.0.17.821.0.5.2 correlatedRecordNameParameter

0.0.17.821.0.5.3 suspectObjectListParameter

0.0.17.821.0.6.X—Name bindings

0.0.17.821.0.6.1 currAlarmSumControl-managedElement

0.0.17.821.0.6.2 managementOperationsSchedule-managedElement

0.0.17.821.0.7.X—Attributes

0.0.17.821.0.7.1 affectedObjectClass

0.0.17.821.0.7.2 affectedObjectInstances

0.0.17.821.0.7.3 alarmStatusList

0.0.17.821.0.7.4 beginTime

0.0.17.821.0.7.5 currentAlarmSummaryControlId

0.0.17.821.0.7.6 destinationAddress

0.0.17.821.0.7.7 endTime

0.0.17.821.0.7.8 interval

0.0.17.821.0.7.9 objectList

OID Name

(4 of 5)



Table C-2 OIDs beginning with 1

0.0.17.821.0.7.10 perceivedSeverityList

0.0.17.821.0.7.11 probableCauseList

0.0.17.821.0.7.12 scheduleId

0.0.17.821.0.9.X—Actions

0.0.17.821.0.9.1 retrieveCurrentAlarmSummary

0.0.17.821.0.9.2 resetAudibleAlarm

0.0.17.821.0.10.X—Notifications

0.0.17.821.0.10.1 currentAlarmSummaryReport

OID Name


1.2.124.113537.1.1.1 managedPack

1.2.124.113537.1.1.2 managedGroomedCircuitTP

1.2.124.113537.1.1.3 managedFacilityTP

1.2.124.113537.1.1.4 managedEquipment

1.2.124.113537.1.1.5 splitMonitorTestObject

1.2.124.113537.1.1.6 loopBackTestObject

1.2.124.113537.1.1.7 busyOutTestObject

1.2.124.113537.1.1.8 oAMCellTestObject

1.2.124.113537.1.1.9 testAccessConnectionObject

1.2.124.113537.1.1.10 managedProfile

1.2.124.113537.1.1.11 traceTestObject

1.2.124.113537.1.1.12 elementExtensions

1.2.124.113537.1.1.13 genericActionObject

1.2.124.113537.1.1.16 objectGroup

1.2.124.113537.1.1.17 routerTemplate

1.2.124.113537.1.2.X—Name bindings

1.2.124.113537.1.2.5 testActionPerformer-network

1.2.124.113537.1.2.6 splitMonitorTestObject-testActionPerformer

1.2.124.113537.1.2.7 loopBackTestObject-testActionPerformer

1.2.124.113537.1.2.8 busyOutTestObject-testActionPerformer

1.2.124.113537.1.2.9 oAMCellTestObject-testActionPerformer

1.2.124.113537.1.2.10 testAccessConnectionObject-testActionPerformer

1.2.124.113537.1.2.13 traceTestObject-testActionPerformer

(1 of 7)

OID Name

(5 of 5)



1.2.124.113537.1.2.18 network-objectGroup

1.2.124.113537.1.2.19 objectGroup-routerTemplate

1.2.124.113537.1.3.X—Actions

1.2.124.113537.1.3.1 testRelease

1.2.124.113537.1.3.2 testMonitor

1.2.124.113537.1.3.3 testSplitThru

1.2.124.113537.1.3.4 testSplitBack

1.2.124.113537.1.3.5 lbRelease

1.2.124.113537.1.3.6 lbLine

1.2.124.113537.1.3.7 lbEquipment

1.2.124.113537.1.3.8 boRelease

1.2.124.113537.1.3.9 boLink

1.2.124.113537.1.3.10 oam-cell

1.2.124.113537.1.3.11 releaseTAC

1.2.124.113537.1.3.12 monitorTAC

1.2.124.113537.1.3.13 splitBackTAC

1.2.124.113537.1.3.14 splitLoopTAC

1.2.124.113537.1.3.15 spvcPathTrace

1.2.124.113537.1.3.16 spvcConnectionTrace

1.2.124.113537.1.3.17 findByLabel

1.2.124.113537.1.3.19 listPaths

1.2.124.113537.1.3.20 hitlessConnectionMove

1.2.124.113537.1.3.21 listFreeManagedGroomedCircuitTPs

1.2.124.113537.1.3.22 listUsedManagedGroomedCircuitTPs

1.2.124.113537.1.3.23 listFreeVCIs

1.2.124.113537.1.3.24 listUsedVCIs

1.2.124.113537.1.3.25 retrieveActiveAlarms

1.2.124.113537.1.3.26 configureRealTimeStatistics

1.2.124.113537.1.3.27 collectRealTimeStatistics

1.2.124.113537.1.3.28 cancelRealTimeStatistics

1.2.124.113537.1.3.29 determineSupportedStatistics

1.2.124.113537.1.3.35 execute

1.2.124.113537.1.3.36 cancelExecute

1.2.124.113537.1.3.37 getExecuteResponse

1.2.124.113537.1.3.38 discardExecuteResponse

1.2.124.113537.1.3.39 addChannelsToMux

1.2.124.113537.1.3.40 removeChannelsFromMux

OID Name

(2 of 7)



1.2.124.113537.1.3.41 listChannelsUsedByMux

1.2.124.113537.1.3.42 listLinks

1.2.124.113537.1.3.43 connectionTrace

1.2.124.113537.1.3.44 listCustomAttributeNames

1.2.124.113537.1.3.45 retrieveISLInfo

1.2.124.113537.1.4.X—Attributes

1.2.124.113537.1.4.1 packProfile

1.2.124.113537.1.4.2 groomedCircuitTPProfile

1.2.124.113537.1.4.3 facilityTPProfile

1.2.124.113537.1.4.4 managedEquipmentType

1.2.124.113537.1.4.5 testType

1.2.124.113537.1.4.6 testName

1.2.124.113537.1.4.7 testObjectName

1.2.124.113537.1.4.8 lbTestType

1.2.124.113537.1.4.9 lbTestName

1.2.124.113537.1.4.10 lbRecoveryType

1.2.124.113537.1.4.11 boTestType

1.2.124.113537.1.4.12 boTestName

1.2.124.113537.1.4.13 boRecoveryType

1.2.124.113537.1.4.14 oAMTestName

1.2.124.113537.1.4.15 oAMReturnPointType

1.2.124.113537.1.4.16 tacTestType

1.2.124.113537.1.4.17 tacTestProfile

1.2.124.113537.1.4.18 managedProfileId

1.2.124.113537.1.4.19 managedProfileType

1.2.124.113537.1.4.20 managedProfileName

1.2.124.113537.1.4.21 managedProfileTranspending

1.2.124.113537.1.4.22 managedProfileProf

1.2.124.113537.1.4.23 traceTestName

1.2.124.113537.1.4.24 traceTestType

1.2.124.113537.1.4.25 traceTestProfile

1.2.124.113537.1.4.26 elementExtensionsId

1.2.124.113537.1.4.27 elementProfile

1.2.124.113537.1.4.28 ntCommissioningProfile

1.2.124.113537.1.4.29 oAMCellAssociatedObjectInfo

1.2.124.113537.1.4.30 pnniProfile

1.2.124.113537.1.4.31 actionName

OID Name

(3 of 7)



1.2.124.113537.1.4.32 actionType

1.2.124.113537.1.4.33 actionProfile

1.2.124.113537.1.4.34 pnniSummaryAddressProfile

1.2.124.113537.1.4.40 executeOperationState

1.2.124.113537.1.4.41 executeStatus

1.2.124.113537.1.4.42 groupId

1.2.124.113537.1.4.43 parameterList

1.2.124.113537.1.4.44 routerTemplateId

1.2.124.113537.1.4.45 templateName

1.2.124.113537.1.4.46 templateVersion

1.2.124.113537.1.4.47 routerTemplateProfile

1.2.124.113537.1.5.X—Parameters

1.2.124.113537.1.5.1 connsFailure

1.2.124.113537.1.5.2 lbNotSupportedTest

1.2.124.113537.1.5.3 boNotSupportedTest

1.2.124.113537.1.5.4 oAMNotSupportedTest

1.2.124.113537.1.5.5 tacNotSupportedTest

1.2.124.113537.1.6.X—Modules

1.2.124.113537.1.6.8 elementExtensions

1.2.124.113537.1.6.10 genericActionObject

1.2.124.113537.1.6.13 ASN1ObjectGroupModule

1.2.124.113537.1.6.14 ASN1RouterTemplateModule

1.2.124.113537.1.7.X—Attributes

1.2.124.113537.1.7.1 additionalAlarmInformationType

1.2.124.113537.1.8.X—Probable Causes

1.2.124.113537.1.8.1 Receive Remote Device Indication Failure

1.2.124.113537.1.8.2 Transmit Remote Device Indication Failure

1.2.124.113537.1.8.3 Receive Alarm Indication Signal

1.2.124.113537.1.8.4 Transmit Alarm Indication Signal

1.2.124.113537.1.8.5 Loopback State

1.2.124.113537.1.8.6 Test Code

1.2.124.113537.1.8.7 Other Failure

1.2.124.113537.1.8.8 Idle

1.2.124.113537.1.8.9 Far End Equipment Failure

1.2.124.113537.1.8.10 Far End Alarm Indication Signal

1.2.124.113537.1.8.11 Far End Loss Of Frame

1.2.124.113537.1.8.12 Far End Loss Of Signal

OID Name

(4 of 7)



1.2.124.113537.1.8.13 ALC Mismatch

1.2.124.113537.1.8.14 Ingress Alarm Indication Signal

1.2.124.113537.1.8.15 Ingress RAI

1.2.124.113537.1.8.16 Ingress Starvation

1.2.124.113537.1.8.17 Ingress Overflow

1.2.124.113537.1.8.18 Ingress Loss Of Frame

1.2.124.113537.1.8.19 Egress Alarm Indication Signal

1.2.124.113537.1.8.20 Egress RAI

1.2.124.113537.1.8.21 Egress Starvation

1.2.124.113537.1.8.22 Egress Overflow

1.2.124.113537.1.8.23 Egress Loss Of Frame

1.2.124.113537.1.8.24 Egress Other Failure

1.2.124.113537.1.8.25 Line Alarm Indication Signal

1.2.124.113537.1.8.26 Line Remote Device Indication

1.2.124.113537.1.8.27 Section Loss Of Signal

1.2.124.113537.1.8.28 Section Loss Of Frame

1.2.124.113537.1.8.29 Path Synchronous Transport Signal Loss Of Pointer

1.2.124.113537.1.8.30 Path Synchronous Transport Signal Alarm Indication Signal

1.2.124.113537.1.8.31 Path Synchronous Transport Signal Remote Device Indication

1.2.124.113537.1.8.32 Path Unequipped

1.2.124.113537.1.8.33 Path SLM

1.2.124.113537.1.8.34 Loss Of Cell Deletion

1.2.124.113537.1.8.35 Loss of Frame

1.2.124.113537.1.8.36 Control framing error

1.2.124.113537.1.9.X—Probable Causes

1.2.124.113537.1.9.1 Disconnected

1.2.124.113537.1.9.2 Disconnected (timed lock set)

1.2.124.113537.1.9.3 Disconnected (disruption by another user)

1.2.124.113537.1.9.4 Disconnected (none)

1.2.124.113537.1.9.5 Bumped (higher priority call)

1.2.124.113537.1.9.6 Activated

1.2.124.113537.1.9.7 Activated (immediately)

1.2.124.113537.1.9.8 Activated (timed unlock)

1.2.124.113537.1.9.9 Activated (reroute)

1.2.124.113537.1.9.10 Activated (recovery)

1.2.124.113537.1.9.11 Activated (bumped)

1.2.124.113537.1.9.12 Activated (uploaded)

OID Name

(5 of 7)



1.2.124.113537.1.9.13 Activated (begin optimizing)

1.2.124.113537.1.9.14 Activated (optimized)

1.2.124.113537.1.9.15 Activated (none)

1.2.124.113537.1.9.16 Down (immediately)

1.2.124.113537.1.9.17 Down (timed)

1.2.124.113537.1.9.18 Down (reroute)

1.2.124.113537.1.9.19 Down (recover)

1.2.124.113537.1.9.20 Down (upload)

1.2.124.113537.1.9.21 Down (bumped)

1.2.124.113537.1.9.22 Down (optimized)

1.2.124.113537.1.9.23 Down

1.2.124.113537.1.9.24 No route to source

1.2.124.113537.1.9.25 No route to source (bumped)

1.2.124.113537.1.9.26 No route to source (rerouted)

1.2.124.113537.1.9.27 Failed

1.2.124.113537.1.9.28 Affected by NMTI

1.2.124.113537.1.9.29 Affected by NMTI (cleared)

1.2.124.113537.1.9.30 Suspect reroute

1.2.124.113537.1.9.31 Atomic set (failed)

1.2.124.113537.1.9.32 Atomic set (connect)

1.2.124.113537.1.9.33 Atomic set (disconnect)

1.2.124.113537.1.9.34 Atomic set (no route to source)

1.2.124.113537.1.9.35 Under maintenance

1.2.124.113537.1.9.36 Under maintenance (cleared)

1.2.124.113537.1.9.37 Intrusive maintenance or loopback

1.2.124.113537.1.9.38 Intrusive maintenance or loopback (cleared)

1.2.124.113537.1.9.39 Activated (optimize failed)

1.2.124.113537.1.9.40 Down (optimized failed)

1.2.124.360501.1.X—Attributes

1.2.124.360501.1.10 circuitBandwidth

1.2.124.360501.1.14 circuitType

1.2.124.360501.1.45 facilityType

1.2.124.360501.1.157 fTGTypeText

1.2.124.360501.1.312 trmCircuitProfile

1.2.124.360501.1.313 trmDataMode

1.2.124.360501.1.314 trmEncryptionRouting

1.2.124.360501.1.315 trmFiberRouting

OID Name

(6 of 7)



Table C-3 OIDs beginning with 2

1.2.124.360501.1.317 trmFunctionalInterface

1.2.124.360501.1.319 trmPhysicalInterface

1.2.124.360501.1.321 trmTerrestrialRouting

1.2.124.360501.1.322 trmVoiceMode

1.2.124.360501.1.327 userIdentifier

1.2.124.360501.1.328 commonProfile

1.2.124.360501.1.329 tDMProfile

1.2.124.360501.1.340 frameRelayProfile

1.2.124.360501.1.341 aTMProfile

1.2.124.360501.3.X—Managed objects

1.2.124.360501.3.75 bMGroomedCircuitTP

1.2.124.360501.3.76 bMFacilityTP

1.2.124.360501.3.77 bMGroomedCircuit

1.2.124.360501.3.78 bMFacility

1.2.124.360501.4.X—Name bindings

1.2.124.360501.4.168 bMGroomedCircuitTP-managedElement

1.2.124.360501.4.169 bMFacilityTP-managedElement

1.2.124.360501.4.170 bMGroomedCircuit-network

1.2.124.360501.4.171 bMFacility-network

1.2.124.360501.5.X—Notifications

1.2.124.360501.5.14 trmCircuitGroomed

1.2.124.360501.6.X—Actions

1.2.124.360501.6.11 trmAbort

1.2.124.360501.6.12 trmCircuitGrooming

1.2.124.360501.6.13 trmCircuitTrace

1.2.124.360501.6.14 trmGetStatus

1.2.124.360501.6.15 trmLocalLoop

OID Name

2.9.0.0.X—Application context

2.9.0.0.2 Manager - Agent application context name, used to identify the sender

2.9.2.12.3.X—Object classes

2.9.2.12.3.2 testActionPerformer

2.9.2.12.3.3 testObject

(1 of 6)

OID Name

(7 of 7)



2.9.2.12.4.X—Packages

2.9.2.12.4.2 associatedObjectsPackage

2.9.2.12.4.3 controlledTestRequestPackage

2.9.2.12.4.5 mORTsPackage

2.9.2.12.4.7 supportedTOClassesPackage

2.9.2.12.4.8 supportedUncontrolledTestsPackage

2.9.2.12.4.12 testOutcomePackage

2.9.2.12.4.14 testSessionPackage

2.9.2.12.4.16 testSuspendResumePackage

2.9.2.12.4.17 testTerminatePackage

2.9.2.12.4.18 tOControlStatusPackage

2.9.2.12.4.19 uncontrolledTestRequestPackage

2.9.2.12.5.X—Parameters

2.9.2.12.5.1 associatedObjectNotAvailable

2.9.2.12.5.2 independentTestInvocationError

2.9.2.12.5.3 invalidTestOperation

2.9.2.12.5.4 mistypedTestCategoryInformation

2.9.2.12.5.5 mORTNotAvailable

2.9.2.12.5.6 noSuchAssociatedObject

2.9.2.12.5.7 noSuchMORT

2.9.2.12.5.8 noSuchTestInvocationId

2.9.2.12.5.9 noSuchTestSessionId

2.9.2.12.5.10 relatedTOError

2.9.2.12.5.11 testSuspendResumeError

2.9.2.12.5.12 testTerminateError

2.9.2.12.7.X—Attributes

2.9.2.12.7.3 associatedObjects

2.9.2.12.7.6 mORTs

2.9.2.12.7.7 supportedTOClasses

2.9.2.12.7.8 supportedUncontrolledTests

2.9.2.12.7.9 testActionPerformerId

2.9.2.12.7.10 testInvocationId

2.9.2.12.7.11 testObjectId

2.9.2.12.7.12 testOutcome

2.9.2.12.7.13 testSessionId

2.9.2.12.9.X—Actions

2.9.2.12.9.1 testRequestControlledAction

OID Name

(2 of 6)



2.9.2.12.9.2 testSuspendResumeAction

2.9.2.12.9.3 testTerminateAction

2.9.2.12.9.4 testRequestUncontrolledAction

2.9.3.2.0.X.X—Probable Causes

2.9.3.2.0.0.6 communicationsSubsystemFailure

2.9.3.2.0.0.15 equipmentMalfunction

2.9.3.2.0.0.28 lossOfFrame

2.9.3.2.0.0.29 lossOfSignal

2.9.3.2.0.0.39 queueSizeExceeded

2.9.3.2.0.0.46 softwareError

2.9.3.2.0.0.47 softwareProgramAbnormallyTerminated

2.9.3.2.0.0.49 storageCapacityProblem

2.9.3.2.0.0.56 underlyingResourceUnavailable

2.9.3.2.0.1.9 InformationOutOfSequence

2.9.3.2.3.X—Object classes

2.9.3.2.3.1 alarmRecord

2.9.3.2.3.2 attributeValueChangeRecord

2.9.3.2.3.3 discriminator

2.9.3.2.3.4 eventForwardingDiscriminator

2.9.3.2.3.5 eventLogRecord

2.9.3.2.3.6 log

2.9.3.2.3.7 logRecord

2.9.3.2.3.8 objectCreationRecord

2.9.3.2.3.9 objectDeletionRecord

2.9.3.2.3.10 relationshipChangeRecord

2.9.3.2.3.11 securityAlarmReportRecord

2.9.3.2.3.12 stateChangeRecord

2.9.3.2.3.13 system

2.9.3.2.3.14 top

2.9.3.2.4.X—Packages

2.9.3.2.4.1 specificProblemsPackage

2.9.3.2.4.2 backedUpStatusPackage

2.9.3.2.4.3 backUpObjectPackage

2.9.3.2.4.4 trendIndicationPackage

2.9.3.2.4.5 thresholdInfoPackage

2.9.3.2.4.6 stateChangeDefinitionPackage

2.9.3.2.4.7 monitoredAttributesPackage

OID Name

(3 of 6)



2.9.3.2.4.8 proposedRepairActionsPackage

2.9.3.2.4.9 backUpDestinationListPackage

2.9.3.2.4.10 modePackage

2.9.3.2.4.11 eventTimePackage

2.9.3.2.4.13 logAlarmPackage

2.9.3.2.4.12 finiteLogSizePackage

2.9.3.2.4.14 administrativeStatePackage

2.9.3.2.4.15 supportedFeaturesPackage

2.9.3.2.4.16 packagesPackage

2.9.3.2.4.17 allomorphicPackage

2.9.3.2.4.18 additionalInformationPackage

2.9.3.2.4.19 additionalTextPackage

2.9.3.2.4.20 attributeIdentifierListPackage

2.9.3.2.4.21 attributeListPackage

2.9.3.2.4.22 availabilityStatusPackage

2.9.3.2.4.23 correlatedNotificationsPackage

2.9.3.2.4.24 notificationIdentifierPackage

2.9.3.2.4.25 dailyScheduling

2.9.3.2.4.26 duration

2.9.3.2.4.27 externalScheduler

2.9.3.2.4.28 sourceIndicatorPackage

2.9.3.2.4.29 weeklyScheduling


2.9.3.2.6.1 discriminator-system

2.9.3.2.6.2 log-system

2.9.3.2.6.3 logRecord-log


2.9.3.2.7.1 discriminatorId

2.9.3.2.7.2 logId

2.9.3.2.7.3 logRecordId

2.9.3.2.7.4 systemId

2.9.3.2.7.5 systemTitle

2.9.3.2.7.6 additionalInformation

2.9.3.2.7.7 additionalText

2.9.3.2.7.8 attributeIdentifierList

2.9.3.2.7.9 attributeList

2.9.3.2.7.10 attributeValueChangeDefinition

OID Name

(4 of 6)



2.9.3.2.7.11 backedUpStatus

2.9.3.2.7.12 correlatedNotifications

2.9.3.2.7.13 eventTime

2.9.3.2.7.14 eventType

2.9.3.2.7.15 monitoredAttributes

2.9.3.2.7.16 notificationIdentifier

2.9.3.2.7.17 perceivedSeverity

2.9.3.2.7.18 probableCause

2.9.3.2.7.19 proposedRepairActions

2.9.3.2.7.20 relationshipChangeDefinition

2.9.3.2.7.21 securityAlarmCause

2.9.3.2.7.22 securityAlarmDetector

2.9.3.2.7.23 securityAlarmSeverity

2.9.3.2.7.24 serviceProvider

2.9.3.2.7.25 serviceUser

2.9.3.2.7.26 sourceIndicator

2.9.3.2.7.27 specificProblems

2.9.3.2.7.28 stateChangeDefinition

2.9.3.2.7.29 thresholdInfo

2.9.3.2.7.30 trendIndication

2.9.3.2.7.31 administrativeState

2.9.3.2.7.33 availabilityStatus

2.9.3.2.7.34 controlStatus

2.9.3.2.7.35 operationalState

2.9.3.2.7.36 proceduralStatus

2.9.3.2.7.39 usageState

2.9.3.2.7.40 backUpObject

2.9.3.2.7.49 activeDestination

2.9.3.2.7.50 allomorphs

2.9.3.2.7.51 backUpDestinationList

2.9.3.2.7.52 capacityAlarmThreshold

2.9.3.2.7.53 confirmedMode

2.9.3.2.7.54 currentLogSize

2.9.3.2.7.55 destination

2.9.3.2.7.56 discriminatorConstruct

2.9.3.2.7.57 intervalsOfDay

2.9.3.2.7.58 logFullAction

OID Name

(5 of 6)



C.2 Alphabetically-arranged 5620 CMIP OIDs

Table App C-4 lists all the 5620 CMIP OIDs alphabetically.

See Appendix B for lists of OIDs arranged in accordance with the standards to which they adhere.

Table C-4 Alphabetically-arranged OIDS

2.9.3.2.7.59 loggingTime

2.9.3.2.7.60 managedObjectClass

2.9.3.2.7.61 managedObjectInstance

2.9.3.2.7.62 maxLogSize

2.9.3.2.7.63 nameBinding

2.9.3.2.7.64 numberOfRecords

2.9.3.2.7.65 objectClass

2.9.3.2.7.66 packages

2.9.3.2.7.67 schedulerName

2.9.3.2.7.68 startTime

2.9.3.2.7.69 stopTime

2.9.3.2.7.70 supportedFeatures

2.9.3.2.7.71 weekMask

2.9.3.2.10.X—Notifications

2.9.3.2.10.1 attributeValueChange

2.9.3.2.10.2 communicationsAlarm

2.9.3.2.10.3 environmentalAlarm

2.9.3.2.10.4 equipmentAlarm

2.9.3.2.10.6 objectCreation

2.9.3.2.10.7 objectDeletion

2.9.3.2.10.10 processingErrorAlarm

2.9.3.2.10.11 qualityOfServiceAlarm

2.9.3.2.10.14 stateChange

OID Name

(6 of 6)

Name OID

a-TPInstance 0.0.13.3100.0.7.1

acceptableCircuitPackTypeList 0.0.13.3100.0.7.58

actionName 1.2.124.113537.1.4.31

(1 of 15)



actionProfile 1.2.124.113537.1.4.32

actionType 1.2.124.113537.1.4.33

Activated 1.2.124.113537.1.9.6

Activated (begin optimizing) 1.2.124.113537.1.9.13

Activated (bumped) 1.2.124.113537.1.9.11

Activated (immediately) 1.2.124.113537.1.9.7

Activated (none) 1.2.124.113537.1.9.15

Activated (optimized) 1.2.124.113537.1.9.14

Activated (recovery) 1.2.124.113537.1.9.10

Activated (reroute) 1.2.124.113537.1.9.9

Activated (timed unlock) 1.2.124.113537.1.9.8

Activated (uploaded) 1.2.124.113537.1.9.12

activeDestination 2.9.3.2.7.49

addChannelsToMux 1.2.124.113537.1.3.39

additionalAlarmInformationType 1.2.124.113537.1.7.1

additionalInformation 2.9.3.2.7.6

additionalInformationPackage 2.9.3.2.4.18

additionalText 2.9.3.2.7.7

additionalTextPackage 2.9.3.2.4.19

administrativeState 2.9.3.2.7.31

administrativeStatePackage 2.9.3.2.4.14

Affected by NMTI 1.2.124.113537.1.9.28

Affected by NMTI (cleared) 1.2.124.113537.1.9.29

affectedObjectClass 0.0.17.821.0.7.1

affectedObjectInstances 0.0.17.821.0.7.2

affectedObjectList 0.0.13.3100.0.7.2

affectedObjectListPackage 0.0.13.3100.0.4.2

alarmEffectOnServiceParameter 0.0.13.3100.0.5.1

alarmRecord 2.9.3.2.3.1

alarmSeverityAssignmentPointerPackage 0.0.13.3100.0.4.3

alarmSeverityAssignmentProfilePointer 0.0.13.3100.0.7.5

alarmStatus 0.0.13.3100.0.7.6

alarmStatusList 0.0.17.821.0.7.3

ALC mismatch 1.2.124.113537.1.8.13

allomorphicPackage 2.9.3.2.4.17

allomorphs 2.9.3.2.7.50

allowAudibleVisualLocalAlarm 0.0.13.3100.0.9.3

Name OID

(2 of 15)



ASN1ObjectGroupModule 1.2.124.113537.1.6.13

ASN1RouterTemplateModule 1.2.124.113537.1.6.14

associatedObjectNotAvailable 2.9.2.12.5.1

associatedObjects 2.9.2.12.7.3

associatedObjectsPackage 2.9.2.12.4.2

aTMProfile 1.2.124.360501.1.341

Atomic set (connect) 1.2.124.113537.1.9.32

Atomic set (disconnect) 1.2.124.113537.1.9.33

Atomic set (failed) 1.2.124.113537.1.9.31

Atomic set (no route to source) 1.2.124.113537.1.9.34

attributeIdentifierList 2.9.3.2.7.8

attributeIdentifierListPackage 2.9.3.2.4.20

attributeList 2.9.3.2.7.9

attributeListPackage 2.9.3.2.4.21

attributeValueChange 2.9.3.2.10.1

attributeValueChangeDefinition 2.9.3.2.7.10

attributeValueChangeNotificationPackage 0.0.13.3100.0.4.4

attributeValueChangeRecord 2.9.3.2.3.2

audibleVisualLocalAlarmPackage 0.0.13.3100.0.4.5

availabilityStatus 2.9.3.2.7.33

availabilityStatusPackage 2.9.3.2.4.22

backedUpStatus 2.9.3.2.7.11

backedUpStatusPackage 2.9.3.2.4.2

backUpDestinationList 2.9.3.2.7.51

backUpDestinationListPackage 2.9.3.2.4.9

backUpObject 2.9.3.2.7.40

backUpObjectPackage 2.9.3.2.4.3

beginTime 0.0.17.821.0.7.4

bMFacility 1.2.124.360501.3.78

bMFacility-network 1.2.124.360501.4.171

bMFacilityTP 1.2.124.360501.3.76

bMFacilityTP-managedElement 1.2.124.360501.4.169

bMGroomedCircuit 1.2.124.360501.3.77

bMGroomedCircuit-network 1.2.124.360501.4.170

bMGroomedCircuitTP 1.2.124.360501.3.75

bMGroomedCircuitTP-managedElement 1.2.124.360501.4.168

boLink 1.2.124.113537.1.3.9

Name OID

(3 of 15)



boNotSupportedTest 1.2.124.113537.1.5.3

boRecoveryType 1.2.124.113537.1.4.13

boRelease 1.2.124.113537.1.3.8

boTestName 1.2.124.113537.1.4.12

boTestType 1.2.124.113537.1.4.11

Bumped (higher priority call) 1.2.124.113537.1.9.5

busyOutTestObject 1.2.124.113537.1.1.7

busyOutTestObject-testActionPerformer 1.2.124.113537.1.2.8

cancelExecute 1.2.124.113537.1.3.36

cancelRealTimeStatistics 1.2.124.113537.1.3.28

capacityAlarmThreshold 2.9.3.2.7.52

channelNumber 0.0.13.3100.0.7.7

channelNumberPackage 0.0.13.3100.0.4.6

characteristicInformation 0.0.13.3100.0.7.8

characteristicInformationPackage 0.0.13.3100.0.4.7

circuitBandwidth 1.2.124.360501.1.10

circuitPack 0.0.13.3100.0.3.30

circuitPack-equipmentHolder-autoCreated 0.0.13.3100.0.6.32

circuitPack-equipmentHolder-explicitlyCreated 0.0.13.3100.0.6.33

circuitPackType 0.0.13.3100.0.7.54

circuitType 1.2.124.360501.1.14

clientConnectionList 0.0.13.3100.0.7.53

clientConnectionListPackage 0.0.13.3100.0.4.35

clientTrail 0.0.13.3100.0.7.10

clientTrailPackage 0.0.13.3100.0.4.9

collectRealTimeStatistics 1.2.124.113537.1.3.27

configureRealTimeStatistics 1.2.124.116537.1.3.26

commonProfile 1.2.124.360501.1.328

communicationsAlarm 2.9.3.2.10.2

communicationsSubsystemFailure 2.9.3.2.0.0.6

confirmedMode 2.9.3.2.7.53

connectionId 0.0.13.3100.0.7.12

connectionR1 0.0.13.3100.0.3.23

connectionR1-network 0.0.13.3100.0.6.25

connectionTerminationPointBidirectional 0.0.13.3100.0.3.5

connectionTerminationPointSink 0.0.13.3100.0.3.6

connectionTerminationPointSink-trailTerminationPointBidirectional 0.0.13.3100.0.6.6

Name OID

(4 of 15)



connectionTerminationPointSink-trailTerminationPointSink 0.0.13.3100.0.6.5

connectionTerminationPointSource 0.0.13.3100.0.3.7

connectionTerminationPointSource-trailTerminationPointBidirectional 0.0.13.3100.0.6.4

connectionTerminationPointSource-trailTerminationPointSource 0.0.13.3100.0.6.3

connectionTrace 1.2.124.113537.1.3.43

connsFailure 1.2.124.113537.1.5.1

controlFramingError 1.2.124.113537.1.8.36

controlledTestRequestPackage 2.9.2.12.4.3

controlStatus 2.9.3.2.7.34

correlatedNotifications 2.9.3.2.7.12

correlatedNotificationsPackage 2.9.3.2.4.23

correlatedRecordNameParameter 0.0.17.821.0.5.2

createDeleteNotificationsPackage 0.0.13.3100.0.4.10

createErrorParameter 0.0.13.3100.0.5.2

crossConnectionObjectPointer 0.0.13.3100.0.7.16

crossConnectionPointerPackage 0.0.13.3100.0.4.11

cTPId 0.0.13.3100.0.7.13

ctpInstancePackage 0.0.13.3100.0.4.12

currAlarmSumControl-managedElement 0.0.17.821.0.6.1

currentAlarmSummaryControl 0.0.17.821.0.3.1

currentAlarmSummaryControlId 0.0.17.821.0.7.5

currentAlarmSummaryReport 0.0.17.821.0.10.1

currentLogSize 2.9.3.2.7.54

currentProblemList 0.0.13.3100.0.7.17

currentProblemListPackage 0.0.13.3100.0.4.13

dailyScheduling 2.9.3.2.4.25

destination 2.9.3.2.7.55

destinationAddress 0.0.17.821.0.7.6

determineSupportedStatistics 1.2.124.113537.3.29

directionality 0.0.13.3100.0.7.18

discardExecuteResponse 1.2.124.113537.1.3.38

Disconnected 1.2.124.113537.1.9.1

Disconnected (disruption by another user) 1.2.124.113537.1.9.3

Disconnected (none) 1.2.124.113537.1.9.4

Disconnected (timed lock set) 1.2.124.113537.1.9.2

discriminator 2.9.3.2.3.3

discriminator-system 2.9.3.2.6.1

Name OID

(5 of 15)



discriminatorConstruct 2.9.3.2.7.56

discriminatorId 2.9.3.2.7.1

Down 1.2.124.113537.1.9.23

Down (bumped) 1.2.124.113537.1.9.21

Down (immediately) 1.2.124.113537.1.9.16

Down (optimized) 1.2.124.113537.1.9.22

Down (recover) 1.2.124.113537.1.9.19

Down (reroute) 1.2.124.113537.1.9.18

Down (timed) 1.2.124.113537.1.9.17

Down (upload) 1.2.124.113537.1.9.20

downstreamConnectivityPointer 0.0.13.3100.0.7.19

duration 2.9.3.2.4.26

Egress Alarm Indication Signal 1.2.124.113537.1.8.19

Egress Loss Of Frame 1.2.124.113537.1.8.23

Egress Other Failure 1.2.124.113537.1.8.24

Egress Overflow 1.2.124.113537.1.8.22

Egress RAI 1.2.124.113537.1.8.20

Egress Starvation 1.2.124.113537.1.8.21

elementExtensions 1.2.124.113537.1.1.12

elementExtensionsId 1.2.124.113537.1.4.26

elementProfile 1.2.124.113537.1.4.27

endTime 0.0.17.821.0.7.7

environmentalAlarm 2.9.3.2.10.3

environmentalAlarmPackage 0.0.13.3100.0.4.14

environmentalAlarmR1Package 0.0.13.3100.0.4.36

equipment 0.0.13.3100.0.3.2

equipment-equipment 0.0.13.3100.0.6.10

equipment-managedElement 0.0.13.3100.0.6.9

equipmentAlarm 2.9.3.2.10.4

equipmentHolder 0.0.13.3100.0.3.32

equipmentHolder-equipmentHolder 0.0.13.3100.0.6.31

equipmentHolderAddress 0.0.13.3100.0.7.56

equipmentHolderType 0.0.13.3100.0.7.57

equipmentId 0.0.13.3100.0.7.20

equipmentMalfunction 2.9.3.2.0.0.15

equipmentR1 0.0.13.3100.0.3.28

eventForwardingDiscriminator 2.9.3.2.3.4

Name OID

(6 of 15)



eventForwardingDiscriminator-managedElement 0.0.13.3100.0.6.11

eventLogRecord 2.9.3.2.3.5

eventTime 2.9.3.2.7.13

eventTimePackage 2.9.3.2.4.11

eventType 2.9.3.2.7.14

execute 1.2.124.113537.1.3.35

executeOperationState 1.2.124.113537.1.4.40

executeStatus 1.2.124.113537.1.4.41

externalScheduler 2.9.3.2.4.27

externalTime 0.0.13.3100.0.7.21

externalTimePackage 0.0.13.3100.0.4.16

facilityTPProfile 1.2.124.113537.1.4.3

facilityType 1.2.124.360501.1.45

Failed 1.2.124.113537.1.9.27

Far End Alarm Indication Signal 1.2.124.113537.1.8.10

Far End Equipment Failure 1.2.124.113537.1.8.9

Far End Loss Of Frame 1.2.124.113537.1.8.11

Far End Loss Of Signal 1.2.124.113537.1.8.12

findByLabel 1.2.124.113537.1.3.17

finiteLogSizePackage 2.9.3.2.4.12

frameRelayProfile 1.2.124.360501.1.340

fTGTypeText 1.2.124.360501.1.157

genericActionObject 1.2.124.113537.1.1.13

getExecuteResponse 1.2.124.113537.1.3.37

groomedCircuitTPProfile 1.2.124.113537.1.4.2

groupId 1.2.124.113537.1.4.42

hitlessConnectionMove 1.2.124.113537.1.3.20

holderStatus 0.0.13.3100.0.7.59

Idle 1.2.124.113537.1.8.8

independentTestInvocationError 2.9.2.12.5.2

informationOutOfSequence 2.9.3.2.0.1.9

Ingress Alarm Indication Signal 1.2.124.113537.1.8.14

Ingress Loss Of Frame 1.2.124.113537.1.8.18

Ingress Overflow 1.2.124.113537.1.8.17

Ingress RAI 1.2.124.113537.1.8.15

Ingress Starvation 1.2.124.113537.1.8.16

inhibitAudibleVisualLocalAlarm 0.0.13.3100.0.9.6

Name OID

(7 of 15)



interval 0.0.17.821.0.7.8

intervalsOfDay 2.9.3.2.7.57

Intrusive maintenance or loopback 1.2.124.113537.1.9.37

Intrusive maintenance or loopback (cleared) 1.2.124.113537.1.9.38

invalidTestOperation 2.9.2.12.5.3

lbEquipment 1.2.124.113537.1.3.7

lbLine 1.2.124.113537.1.3.6

lbNotSupportedTest 1.2.124.113537.1.5.2

lbRecoveryType 1.2.124.113537.1.4.10

lbRelease 1.2.124.113537.1.3.5

lbTestName 1.2.124.113537.1.4.9

lbTestType 1.2.124.113537.1.4.8

Line Alarm Indication Signal 1.2.124.113537.1.8.25

Line Remote Device Indication 1.2.124.113537.1.8.26

listChannelsUsedByMux 1.2.124.113537.1.3.41

listCustomAttributeNames 1.2.124.113537.1.3.44

listFreeManagedGroomedCircuitTPs 1.2.124.113537.1.3.21

listFreeVCIs 1.2.124.113537.1.3.23

listLinks 1.2.124.113537.1.3.42

listPaths 1.2.124.113537.1.3.19

listUsedManagedGroomedCircuitTPs 1.2.124.113537.1.3.22

listUsedVCIs 1.2.124.113537.1.3.24

locationName 0.0.13.3100.0.7.27

locationNamePackage 0.0.13.3100.0.4.17

log 2.9.3.2.3.6

log-system 2.9.3.2.6.2

logAlarmPackage 2.9.3.2.4.13

logFullAction 2.9.3.2.7.58

loggingTime 2.9.3.2.7.59

logId 2.9.3.2.7.2

logRecord 2.9.3.2.3.7

logRecord-log 2.9.3.2.6.3

logRecordId 2.9.3.2.7.3

logRecordIdParameter 0.0.17.821.0.5.1

Loopback State 1.2.124.113537.1.8.5

loopBackTestObject 1.2.124.113537.1.1.6

loopBackTestObject-testActionPerformer 1.2.124.113537.1.2.7

Name OID

(8 of 15)



Loss Of Cell Deletion 1.2.124.113537.1.8.34

lossOfFrame 2.9.3.2.0.0.28

lossOfFrame 1.2.124.113537.1.8.35

lossOfSignal 2.9.3.2.0.0.29

managedElement 0.0.13.3100.0.3.3

managedElement-network 0.0.13.3100.0.6.15

managedElementId 0.0.13.3100.0.7.28

managedEquipment 1.2.124.113537.1.1.4

managedEquipmentType 1.2.124.113537.1.4.4

managedFacilityTP 1.2.124.113537.1.1.3

managedGroomedCircuitTP 1.2.124.113537.1.1.2

managedObjectClass 2.9.3.2.7.60

managedObjectInstance 2.9.3.2.7.61

managedPack 1.2.124.113537.1.1.1

managedProfile 1.2.124.113537.1.1.10

managedProfileId 1.2.124.113537.1.4.18

managedProfileName 1.2.124.113537.1.4.20

managedProfileProf 1.2.124.113537.1.4.22

managedProfileTranspending 1.2.124.113537.1.4.21

managedProfileType 1.2.124.113537.1.4.19

managementOperationsSchedule 0.0.17.821.0.3.2

managementOperationsSchedule-managedElement 0.0.17.821.0.6.2

managementOperationsScheduleOperationalStatePkg 0.0.17.821.0.4.1

Manager - Agent application context name, used to identify the sender 2.9.0.0.2

maxLogSize 2.9.3.2.7.62

mistypedTestCategoryInformation 2.9.2.12.5.4

modePackage 2.9.3.2.4.10

monitoredAttributes 2.9.3.2.7.15

monitoredAttributesPackage 2.9.3.2.4.7

monitorTAC 1.2.124.113537.1.3.12

mORTNotAvailable 2.9.2.12.5.5

mORTs 2.9.2.12.7.6

mORTsPackage 2.9.2.12.4.5

nameBinding 2.9.3.2.7.63

network 0.0.13.3100.0.3.1

network-network 0.0.13.3100.0.6.17

network-objectGroup 1.2.124.113537.1.2.18

Name OID

(9 of 15)



network-rootNB 0.0.13.3100.0.6.30

networkId 0.0.13.3100.0.7.30

networkLevelPackage 0.0.13.3100.0.4.18

networkLevelPointer 0.0.13.3100.0.7.31

No route to source 1.2.124.113537.1.9.24

No route to source (bumped) 1.2.124.113537.1.9.25

No route to source (rerouted) 1.2.124.113537.1.9.26

noSuchAssociatedObject 2.9.2.12.5.6

noSuchMORT 2.9.2.12.5.7

noSuchTestInvocationId 2.9.2.12.5.8

noSuchTestSessionId 2.9.2.12.5.9

notificationIdentifier 2.9.3.2.7.16

notificationIdentifierPackage 2.9.3.2.4.24

npipe 0.0.13.3100.0.3.24

ntCommissioningProfile 1.2.124.113537.1.4.28

numberOfRecords 2.9.3.2.7.64

oam-cell 1.2.124.113537.1.3.10

oAMCellAssociatedObjectInfo 1.2.124.113537.1.4.29

oAMCellTestObject 1.2.124.113537.1.1.8

oAMCellTestObject-testActionPerformer 1.2.124.113537.1.2.9

oAMNotSupportedTest 1.2.124.113537.1.5.4

oAMReturnPointType 1.2.124.113537.1.4.15

oAMTestName 1.2.124.113537.1.4.14

objectClass 2.9.3.2.7.65

objectCreation 2.9.3.2.10.6

objectCreationRecord 2.9.3.2.3.8

objectDeletion 2.9.3.2.10.7

objectDeletionRecord 2.9.3.2.3.9

objectGroup 1.2.124.113537.1.1.16

objectGroup-routerTemplate 1.2.124.113537.1.2.19

objectList 0.0.17.821.0.7.9

operationalState 2.9.3.2.7.35

operationalStatePackage 0.0.13.3100.0.4.19

Other Failure 1.2.124.113537.1.8.7

packages 2.9.3.2.7.66

packagesPackage 2.9.3.2.4.16

packProfile 1.2.124.113537.1.4.1

Name OID

(10 of 15)



parameterList 1.2.124.113537.1.4.43

Path SLM 1.2.124.113537.1.8.33

Path Synchronous Transport Signal Alarm Indication Signal 1.2.124.113537.1.8.30

Path Synchronous Transport Signal Loss Of Pointer 1.2.124.113537.1.8.29

Path Synchronous Transport Signal Remote Device Indication 1.2.124.113537.1.8.31

Path Unequipped 1.2.124.113537.1.8.32

perceivedSeverity 2.9.3.2.7.17

perceivedSeverityList 0.0.17.821.0.7.10

pnniProfile 1.2.124.113537.1.4.30

pnniSummaryAddressProfile 1.2.124.113537.1.4.34

probableCause 2.9.3.2.7.18

probableCauseList 0.0.17.821.0.7.11

proceduralStatus 2.9.3.2.7.36

processingErrorAlarm 2.9.3.2.10.10

processingErrorAlarmPackage 0.0.13.3100.0.4.21

processingErrorAlarmR1Package 0.0.13.3100.0.4.39

proposedRepairActions 2.9.3.2.7.19

proposedRepairActionsPackage 2.9.3.2.4.8

protected 0.0.13.3100.0.7.32

protectedPackage 0.0.13.3100.0.4.22

queueSizeExceeded 2.9.3.2.0.0.39

Receive Alarm Indication Signal 1.2.124.113537.1.8.3

Receive Remote Device Indication Failure 1.2.124.113537.1.8.1

relatedTOError 2.9.2.12.5.10

relationshipChangeDefinition 2.9.3.2.7.20

relationshipChangeRecord 2.9.3.2.3.10

releaseTAC 1.2.124.113537.1.3.11

removeChannelsFromMux 1.2.124.113537.1.3.40

replaceable 0.0.13.3100.0.7.34

resetAudibleAlarm 0.0.17.821.0.9.2

resetAudibleAlarmPackage 0.0.13.3100.0.4.23

retrieveActiveAlarms 1.2.124.113537.1.3.25

retrieveCurrentAlarmSummary 0.0.17.821.0.9.1

routerTemplate 1.2.124.113537.1.1.17

routerTemplateId 1.2.124.113537.1.4.44

routerTemplateProfile 1.2.124.113537.1.4.47

scheduleId 0.0.17.821.0.7.12

Name OID

(11 of 15)



schedulerName 2.9.3.2.7.67

Section Loss Of Frame 1.2.124.113537.1.8.28

Section Loss Of Signal 1.2.124.113537.1.8.27

securityAlarmCause 2.9.3.2.7.21

securityAlarmDetector 2.9.3.2.7.22

securityAlarmReportRecord 2.9.3.2.3.11

securityAlarmSeverity 2.9.3.2.7.23

serialNumber 0.0.13.3100.0.7.69

serverConnectionList 0.0.13.3100.0.7.35

serverConnectionListPackage 0.0.13.3100.0.4.24

serverTrailList 0.0.13.3100.0.7.36

serverTrailListPackage 0.0.13.3100.0.4.25

serviceProvider 2.9.3.2.7.24

serviceUser 2.9.3.2.7.25

softwareError 2.9.3.2.0.0.46

softwareProgram AbnormallyTerminated 2.9.3.2.0.0.47

sourceIndicator 2.9.3.2.7.26

sourceIndicatorPackage 2.9.3.2.4.28

specificProblems 2.9.3.2.7.27

specificProblemsPackage 2.9.3.2.4.1

splitBackTAC 1.2.124.113537.1.3.13

splitLoopTAC 1.2.124.113537.1.3.14

splitMonitorTestObject 1.2.124.113537.1.1.5

splitMonitorTestObject-testActionPerformer 1.2.124.113537.1.2.6

spvcConnectionTrace 1.2.124.113537.1.3.16

spvcPathTrace 1.2.124.113537.1.3.15

startTime 2.9.3.2.7.68

stateChange 2.9.3.2.10.14

stateChangeDefinition 2.9.3.2.7.28

stateChangeDefinitionPackage 2.9.3.2.4.6

stateChangeNotificationPackage 0.0.13.3100.0.4.28

stateChangeRecord 2.9.3.2.3.12

stopTime 2.9.3.2.7.69

storageCapacityProblem 2.9.3.2.0.0.49

subordinateCircuitPackPackage 0.0.13.3100.0.4.41

subordinateCircuitPackSoftwareLoad 0.0.13.3100.0.7.60

supportableClientList 0.0.13.3100.0.7.39

Name OID

(12 of 15)



supportableClientListPackage 0.0.13.3100.0.4.27

supportedByObjectList 0.0.13.3100.0.7.40

supportedFeatures 2.9.3.2.7.70

supportedFeaturesPackage 2.9.3.2.4.15

supportedTOClasses 2.9.2.12.7.7

supportedTOClassesPackage 2.9.2.12.4.7

supportedUncontrolledTests 2.9.2.12.7.8

supportedUncontrolledTestsPackage 2.9.2.12.4.8

Suspect reroute 1.2.124.113537.1.9.30

suspectObjectListParameter 0.0.17.821.0.5.3

system 2.9.3.2.3.13

systemId 2.9.3.2.7.4

systemTimingSource 0.0.13.3100.0.7.41

systemTimingSourcePackage 0.0.13.3100.0.4.29

systemTitle 2.9.3.2.7.5

tacNotSupportedTest 1.2.124.113537.1.5.5

tacTestProfile 1.2.124.113537.1.4.17

tacTestType 1.2.124.113537.1.4.16

tDMProfile 1.2.124.360501.1.329

templateName 1.2.124.113537.1.4.45

templateVersion 1.2.124.113537.1.4.46

terminationPoint 0.0.13.3100.0.3.8

Test Code 1.2.124.113537.1.8.6

testAccessConnectionObject 1.2.124.113537.1.1.9

testAccessConnectionObject-testActionPerformer 1.2.124.113537.1.2.10

testActionPerformer 2.9.2.12.3.2

testActionPerformer-network 1.2.124.113537.1.2.5

testActionPerformerId 2.9.2.12.7.9

testInvocationId 2.9.2.12.7.10

testMonitor 1.2.124.113537.1.3.2

testName 1.2.124.113537.1.4.6

testObject 2.9.2.12.3.3

testObjectId 2.9.2.12.7.11

testObjectName 1.2.124.113537.1.4.7

testOutcome 2.9.2.12.7.12

testOutcomePackage 2.9.2.12.4.12

testRelease 1.2.124.113537.1.3.1

Name OID

(13 of 15)



testRequestControlledAction 2.9.2.12.9.1

testRequestUncontrolledAction 2.9.2.12.9.4

testSessionId 2.9.2.12.7.13

testSessionPackage 2.9.2.12.4.14

testSplitBack 1.2.124.113537.1.3.4

testSplitThru 1.2.124.113537.1.3.3

testSuspendResumeAction 2.9.2.12.9.2

testSuspendResumeError 2.9.2.12.5.11

testSuspendResumePackage 2.9.2.12.4.16

testTerminateAction 2.9.2.12.9.3

testTerminateError 2.9.2.12.5.12

testTerminatePackage 2.9.2.12.4.17

testType 1.2.124.113537.1.4.5

thresholdInfo 2.9.3.2.7.29

thresholdInfoPackage 2.9.3.2.4.5

tmnCommunicationsAlarmInformationPackage 0.0.13.3100.0.4.30

tOControlStatusPackage 2.9.2.12.4.18

top 2.9.3.2.3.14

traceTestName 1.2.124.113537.1.4.23

traceTestObject 1.2.124.113537.1.1.11

traceTestObject-testActionPerformer 1.2.124.113537.1.2.13

traceTestType 1.2.124.113537.1.4.24

traceTestProfile 1.2.124.113537.1.4.25

trailId 0.0.13.3100.0.7.47

trailR1 0.0.13.3100.0.3.25

trailR1-network 0.0.13.3100.0.6.26

trailTerminationPointBidirectional 0.0.13.3100.0.3.9

trailTerminationPointSink 0.0.13.3100.0.3.10

trailTerminationPointSink-managedElement 0.0.13.3100.0.6.24

trailTerminationPointSource 0.0.13.3100.0.3.11

trailTerminationPointSource-managedElement 0.0.13.3100.0.6.23

Transmit Alarm Indication Signal 1.2.124.113537.1.8.4

Transmit Remote Device Indication Failure 1.2.124.113537.1.8.2

trendIndication 2.9.3.2.7.30

trendIndicationPackage 2.9.3.2.4.4

trmAbort 1.2.124.360501.6.11

trmCircuitGroomed 1.2.124.360501.5.14

Name OID

(14 of 15)



trmCircuitGrooming 1.2.124.360501.6.12

trmCircuitProfile 1.2.124.360501.1.312

trmCircuitTrace 1.2.124.360501.6.13

trmDataMode 1.2.124.360501.1.313

trmEncryptionRouting 1.2.124.360501.1.314

trmFiberRouting 1.2.124.360501.1.315

trmFunctionalInterface 1.2.124.360501.1.317

trmGetStatus 1.2.124.360501.6.14

trmLocalLoop 1.2.124.360501.6.15

trmPhysicalInterface 1.2.124.360501.1.319

trmTerrestrialRouting 1.2.124.360501.1.321

trmVoiceMode 1.2.124.360501.1.322

tTPId 0.0.13.3100.0.7.48

ttpInstancePackage 0.0.13.3100.0.4.31

uncontrolledTestRequestPackage 2.9.2.12.4.19

Under maintenance 1.2.124.113537.1.9.35

Under maintenance (cleared) 1.2.124.113537.1.9.36

underlyingResourceUnavailable 2.9.3.2.0.0.56

upstreamConnectivityPointer 0.0.13.3100.0.7.49

usageState 2.9.3.2.7.39

userIdentifier 1.2.124.360501.1.327

userLabel 0.0.13.3100.0.7.50

userLabelPackage 0.0.13.3100.0.4.32

vendorName 0.0.13.3100.0.7.51

vendorNamePackage 0.0.13.3100.0.4.33

version 0.0.13.3100.0.7.52

versionPackage 0.0.13.3100.0.4.34

weeklyScheduling 2.9.3.2.4.29

weekMask 2.9.3.2.7.71

z-TPInstance 0.0.13.3100.0.7.55

Name OID

(15 of 15)

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 D-1October 2006 95-6040-01-00-C


D.1 Introduction D-2

D.2 bMFacility object D-2

D.3 bMGroomedCircuit object D-4

D.4 log object D-6

D.5 managedElement object D-6

D.6 managedFacilityTP object D-11

D.7 managedPack object D-16


D-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

D.1 Introduction

This appendix identifies the possible values for the following alarmRecord attributes for alarm generated from 5620 NM trouble tickets:

• managedObjectClass• perceivedSeverity• additionalText—the value of the problem description• additionalInformation—the value for the problemCode• probableCause

The value of the additionalText problem description is a string, which is denoted in the tables in this section by quotation marks, such as “problem description”. In some cases, a clarification is added and denoted by enclosing it in parentheses, such as (clarification). The clarification is not part of the value for the additionalText problem description string.

D.2 bMFacility object

When the managedObjectClass is set to bMFacility object, other selected alarmRecord attributes and values are:

• perceivedSeverity; described in Table App D-1• additionalText problem description; described in Table App D-1 • additionalInformation problemCode; described in Table App D-1• probableCause; set as communicationsSubsystemFailure (2.9.3.2.0.0.6)

Table D-1 alarmRecord attribute values for bMFacility object managedObjectClass

Note — See chapter 17 and Appendix E for more information about alarmRecord formats for alarms generated by the 5620 NM fault management system.

perceivedSeverity

additionalText (problem description) problemCode

critical “A part of this facility has been disabled through NMTI.” 7004

critical “The facility is disabled due to intrusive diagnostics.” 7004

critical “The facility is OOS due to end point LMI status.” 7004

major “[name] appears to be faulty.” 1007

major “24 hour link availability threshold exceeded on device [name]. ^Monitoring suspended for 24 hours.”

1007

major “Cable [name] has degraded.” 1007

major “Cable [name] is unusable (please delete it).” 1007

cleared “Status of [name] changed to Connected (down).” 1007

(1 of 3)



cleared “Status of [name] changed to Connected (up).” 1007

major “The facility has been atomically set and now has no bandwidth allocated, so it is disabled.”

7004

major “The facility has been bumped and now has no bandwidth allocated, so it is disabled.”

7004

major “The facility has been locked as a result of an unsuccessful bandwidth atomic set.”

7004

major “The facility has been locked by a network management user.” 7004

major “The facility has been rerouted and now has no bandwidth allocated, so it is disabled.”

7004

major “The facility has been unlocked, but no bandwidth is allocated, so it is disabled.” 7004

major “The facility is being rerouted.” 7004

major “The facility is disabled after an unsuccessful bandwidth atomic set.” 7004

major “The facility is unlocked but no bandwidth is allocated as the request failed in the network.”

7004

minor “The facility is being groomed.” 7004

minor “The facility is under maintenance.” 7004

warning “[name] has been busied out.” 1007

warning “[name] has its bandwidth reduced” 1007

warning “[name] is normal.” 1007

warning “The facility is unlocked with bandwidth allocated after a recovery, but it is disabled”

7004

warning “The facility is unlocked with bandwidth allocated after a reroute, but it is disabled.”

7004

warning “The facility is unlocked with bandwidth allocated after an upload, but it is disabled.”

7004

warning “The facility is unlocked with bandwidth allocated after grooming, but it is disabled.”

7004

warning “The facility is unlocked with bandwidth allocated, but it is disabled.” 7004

cleared “A part of this call, previously disabled through NMTI, is now busy.” 7004

cleared “The facility has been recovered, and is now unlocked with bandwidth allocated.”

7004

cleared “The facility has been successfully unlocked after a bandwidth atomic set.” 7004

cleared “The facility is unlocked after a reroute; bandwidth has been allocated.” 7004

cleared “The facility is unlocked after grooming; bandwidth has been allocated.” 7004

cleared “The facility is unlocked as a result of a timed unlock; bandwidth has been allocated.”

7004

cleared “The facility is unlocked; bandwidth has been allocated.” 7004

cleared “The facility was uploaded from connections; and is unlocked with bandwidth allocated.”

7004

cleared “The facility, previously disabled due to intrusive diagnostics, is now busy.” 7004

perceivedSeverity


(2 of 3)



D.3 bMGroomedCircuit object

When the managedObjectClass is set to bMGroomedCircuit object, other selected alarmRecord attributes and values are:

• perceivedSeverity; described in Table App D-2• additionalText problem description; described in Table App D-2 • additionalInformation problemCode; described in Table App D-2• probableCause; set to communicationsSubsystemFailure (2.9.3.2.0.0.6)

Table D-2 alarmRecord attribute values for bMGroomedCircuit object managedObjectClass

cleared “The facility, previously OOS due to endpoint LMI status is now normal.” 7004

cleared “The maintenance diagnostics on this facility have been released.” 7004

— user provided text - text content unknown 4001

perceivedSeverity


(3 of 3)

perceivedSeverity


critical “A part of this groomed circuit has been disabled through NMTI.” 7004

critical “The groomed circuit is disabled due to intrusive diagnostics.” 7004

major “The groomed circuit has been atomically set and now has no bandwidth allocated, so it is disabled.”

7004

major “The groomed circuit has been bumped and now has no bandwidth allocated, so it is disabled.”

7004

major “The groomed circuit has been locked as a result of an unsuccessful bandwidth atomic set.”

7004

major “The groomed circuit has been locked by a network management user.” 7004

major “The groomed circuit has been rerouted, and now has no bandwidth allocated, so it is disabled.”

7004

major “The groomed circuit has been unlocked, but no bandwidth is allocated, so it is disabled.”

7004

major “The groomed circuit is being rerouted.” 7004

major “The groomed circuit is disabled after an unsuccessful bandwidth atomic set.” 7004

major “The groomed circuit is unlocked but no bandwidth is allocated as the request failed in the network.”

7004

major “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.” 7004

minor “The groomed circuit is being groomed.” 7004

minor “The groomed circuit is under maintenance.” 7004

warning “The groomed circuit is unlocked with bandwidth allocated after a recovery, but it is disabled.”

7004

(1 of 2)



warning “The groomed circuit is unlocked with bandwidth allocated after a reroute, but it is disabled.”

7004

warning “The groomed circuit is unlocked with bandwidth allocated after an upload, but it is disabled.”

7004

warning “The groomed circuit is unlocked with bandwidth allocated after being bumped, but it is disabled.”

7004

warning “The groomed circuit is unlocked with bandwidth allocated after grooming, but it is disabled.”

7004

warning “The groomed circuit is unlocked with bandwidth allocated, but it is disabled.” 7004

cleared “A part of this call, previously disabled through NMTI, is now busy.” 7004

cleared “The groomed circuit has been recovered, and is now unlocked with bandwidth allocated.”

7004

cleared “The groomed circuit has been successfully unlocked after a bandwidth atomic set.”

7004

cleared “The groomed circuit is unlocked after a reroute; bandwidth has been allocated.”

7004

cleared “The groomed circuit is unlocked after grooming; bandwidth has been allocated.”

7004

cleared “The groomed circuit is unlocked as a result of a timed unlock; bandwidth has been allocated.”

7004

cleared “The groomed circuit is unlocked; bandwidth has been allocated.” 7004

cleared “The groomed circuit was uploaded from connections; and is unlocked with bandwidth allocated.”

7004

cleared “The groomed circuit, previously disabled due to intrusive diagnostics, is now busy.”

7004

cleared “The maintenance diagnostics on this groomed circuit have been released.” 7004

perceivedSeverity


(2 of 2)



D.4 log object

When the managedObjectClass is set to log object, other selected alarmRecord attributes and values are:

• perceivedSeverity; if the capacityAlarmThreshold attribute for the log object is 100, then perceivedSeverity is set to critical; otherwise perceivedSeverity is set to warning

• additionalText is set to null• additionalInformation is set to null• probableCause is set to storageCapacityProblem (2.9.3.2.0.0.49)• thresholdInfo is set to the following:

• triggeredThreshold is set to capacityAlarmThreshold (2.9.3.2.7.52)• observedValue is taken from the log configuration• thresholdLevel is set to null• armTime is set to null

• monitoredAttributes is set to the following:• attributeId is set to maxLogSize (2.9.3.2.7.62)• attributeValue is taken from the log configuration

D.5 managedElement object

When the managedObjectClass is set to managedElement object, other selected alarmRecord attributes and values are:

• perceivedSeverity; described in Table App D-3• additionalText problem description; described in Table App D-3 • additionalInformation problemCode; described in Table App D-3• probableCause; described in Table App D-3

Table D-3 alarmRecord attribute values for managedElement object managedObjectClass

perceivedSeverity


In the following list, the probableCause is set to equipmentMalfunction (2.9.3.2.0.0.15)

major “[callName] failed due to internal error.” 1015

major “[callName] has been bumped.” 1015

major “[callName] has been connected.” 1015

major “[callName] has been rerouted.” 1015

major “[callName] is being rerouted to become optimal.” 1015

major “[callName] is waiting for repairs.” 1015

major “[callName] is waiting for resources. Recovery information may not be displayed in this ticket.”

1015

major “[count] RAPID paths were affected.” 1015

(1 of 6)



major “[name] accounting disable failed.” 1015

major “[name] accounting enable failed.” 1015

major “[name] accounting has been disabled.” 1015

major “[name] accounting has been enabled.” 1015

major “[name] has been activated.” 1015

major “[name] has been deactivated.” 1015

major “Activation from shutdown state has failed for [callName]” 1015

major “Activation from the ”Inactive” state has failed for [callName]” 1015

major “Active Proxy Agent cannot communicate with node [CPSS address]. [deviceID]”

1015

major “ADPCM links contained [count] path(s).” 1015

major “ATM VPC links contained [count] PVC path(s).” 1015

major “Attempted to reroute [count] ADPCM link(s).” 1015

major “Attempted to reroute [count] frame relay link(s).” 1015

major “Attempted to reroute [count] Pass-Through link(s).” 1015

major “Attempted to reroute [count] path(s).” 1015

major “Attempted to reroute [count] subrate link(s).” 1015

major “Attempted to reroute [count] transport link(s).” 1015

major “Authentication trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] ^Variable Bindings: [variable bindings]”

6003

major “Authentication trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003

major “Cannot monitor database, please investigate.” 1015

major “change server queue overflow” 7005

major “Cold Start trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003

major “Cold Start trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community]. Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Communications failure between [domain].[major number] and proxy agent. Reconcile unit [deviceID] now.”

1015

major “Continuity check disable failed for path [callName].” 1015

major “Continuity check enable failed for path [callName].” 1015

major “Could not open Path Status Log file.” 4002

major “Deactivation from shutdown state has failed for [callName]” 1015

major “Deactivation from the ”Active” state has failed for [callName]” 1015

major “DMDS IP Multicast Address for call [callID] doesn’t match with node [node ID}.” 4002

major “DMDS IP Multicast entry for call [callID] has been deleted on node [node ID].” 4002

major “DMDS Traffic descriptor for call [callID] doesn’t match with node [node ID].” 4002

perceivedSeverity


(2 of 6)



major “DMLB unit seems to be in service” 1015

major “DMLB unit seems to be out of service” 1015

major “EGP Neighbour Loss trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “EGP Neighbour Loss trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003

major “Enterprise Specific trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^Specific Type [specific trap type] ^ Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Enterprise Specific trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ̂ Specific Type: [specific trap type] ^ Enterprise: [enterprise]”

6003

major “File write error as path status logging has been disabled.” 4002

major “Frame relay links contained [count] path(s).” 1015

major “HAPA error [HAPA name] has occurred. Activity switch taking place. ^[nodeName] assuming a standby role.”

1015

major “HAPA error [HAPA name] has occurred. Activity switch taking place.^[nodeName] assuming an active role.”

1015

major “Link Down trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Link Down trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community]^ Enterprise: [enterprise]”

6003

major “Link Up trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Link Up trap received:Ât Uptime: [up time]IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003

major “Lost communication with alarm printer auto printing has been disabled. To restart logging: 1) Re-enable the alarm printer.2) Wakeup the NL_alarm process.Contact the TAC center for assistance with this operation.”

1015

major “New NMTI Created SPVC with following attribute: [property name] = [property value]”

4002

major “NMTI Affected SPVC with following changed attribute: [property name] was [old property value] and now is [new property value]”

4002

major “NMTI Change to VP Shaping Groups, VPCL affected” 4002

major “Node [node short name] failed to respond in the middle of a reconcile.” 1016

major “Node software version [generic number] for CPSS node [CPSS address], is not network manageable. You must upgrade the node software to use this node in a 5620 NM environment. The node will not be reconciled.”

1015

major “Node software version [generic number] for CPSS node [CPSS address], is not supported. Newbridge recommends that you upgrade your node software.”

1015

major “Node with CPSS address [CPSS address] cannot be added because it will exceed the Licensed Number of Nodes or Workstations.”

1015

major “Pass-Through links contained [count] call(s).” 1015

perceivedSeverity


(3 of 6)



major “Received notification of System table change:Ât UpTime: [time] ^New:Ôbject: [newID] ^Descr: [new description] Înterface Count: [new interface count] Ôld:Ôbject: [old ID] ^Descr: [old description] Înterface Count: [old interface count]^”

6001

major “Reconcile of local ([node name]) from remote failed.” 1016

major “Shutdown has failed for [callName]” 1015

major “Standby Proxy Agent cannot communicate with node [domain][major number]” 1015

major “Status of [callName] changed to Connected (down).” 1015

major “Status of [callName] changed to Connected (up).” 1015

major “Status of [count] ADPCM link(s) changed to Connected (down).” 1015

major “Status of [count] ADPCM link(s) changed to Connected (up).” 1015

major “Status of [count] ATM VPC link(s) set to Connected (down).” 1015

major “Status of [count] ATM VPC link(s) set to Connected (up).” 1015

major “Status of [count] frame relay link(s) set to Connected (down).” 1015

major “Status of [count] frame relay link(s) set to Connected (up).” 1015

major “Status of [count] Pass-Through link(s) changed to Connected (down).” 1015

major “Status of [count] Pass-Through link(s) changed to Connected (up).” 1015

major “Status of [count] path(s) changed to Connected (down).” 1015

major “Status of [count] path(s) changed to Connected (up).” 1015

major “Status of [count] subrate link(s) changed to Connected (down).” 1015

major “Status of [count] subrate link(s) changed to Connected (up).” 1015

major “Status of [count] transport link(s) changed to Connected (down).” 1015

major “Status of [count] transport link(s) changed to Connected (up).” 1015

major “Subrate links contained [count] path(s).” 1015

major “SVC and SPVC paths may have been affected.” 1015

major “SVC paths may have been affected.” 1015

major “The RAPID path [callName] was affected.” 1015

major “The RAPID path [callName] was switched to alternate.” 1015

major “The RAPID path [callName] was switched to primary.” 1015

major “Transport link contained [count] call(s).” 1015

major “Unknown trap type received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community ^ Generic type: [generic trap type] Specific Type: [specific trap type]Ênterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Unknown trap type received:Ât Uptime: [up time]ÎP Address: [IP address] Trap Community: [trap community] ^ Generic type: [generic trap type] Specific Type: [specific trap type]Ênterprise: [enterprise]”

6003

major “WarmStart trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] Variable Binding: [variable bindings]”

6003

perceivedSeverity


(4 of 6)



major “WarmStart trap received:^At Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003

warning “Configured Access Group [nodeName].” 1015

warning “Configured node [node short name].” 1015

warning “Created Access Group [nodeName].” 1015

warning “Created node [node short name].” 1015

warning “Mini reconcile of remote ([node short name]) has started.” 1016

warning “Mini reconciling remote from local ([node short name]).” 1016

warning “Received indication that [nodeName] is offline.” 1015

warning “Received indication that [nodeName] is online.” 1015

warning “Reconcile at EMS ([waiting for proxy])([node short name])” 1016

warning “Reconcile Configs of remote ([node short name]) has started.” 1016

warning “Reconcile Connects of remote ([node short name]) has started.” 1016

warning “Reconcile of local ([node name]) from remote complete.” 1016

warning “Reconcile of remote ([node short name]) has started.” 1016

warning “Reconciling Configs and Connects of remote ([node short name]) has started.” 1016

warning “Reconciling Configs and Connects remote from local ([node short name]) “ 1016

warning “Reconciling Configs remote from local ([node short name]).” 1016

warning “Reconciling Connects remote from local ([node short name]).” 1016

warning “Reconciling local ([node short name]) from remote.” 1016

warning “Reconciling remote from local ([node short name]).” 1016

warning “Reloading MIB ([node name]) from 5620 NM database.” 1016

warning “Still reconciling local ([node short name]) from remote.” 1016


In the following list, the probableCause is set to softwareProgramAbnormallyTerminated (2.9.3.2.0.0.47)

major “Connection between 5620 CMIP and 5620 NM has been lost. [mElement name]”

3001

major “MIB reload terminated abnormally” 7008

cleared “Alarm Cleared” 3001

perceivedSeverity


(5 of 6)



D.6 managedFacilityTP object

When the managedObjectClass is set to managedFacilityTP object, other selected alarmRecord attributes and values are:

• perceivedSeverity; described in Table App D-4• additionalText problem description; described in Table App D-4 • additionalInformation problemCode; described in Table App D-4• probableCause; set to communicationsSubsystemFailure (2.9.3.2.0.0.6)

Table D-4 alarmRecord attribute values for managedFacilityTP object managedObjectClass

In the following list, the probableCause is set to queueSizeExceeded (2.9.3.2.0.0.39)

critical “5620 NM change server queue overflow - MIB out of sync with 5620 NM database reload should be performed”

7005


critical “The association from this OSS appears to be performing poorly, causing an overflow in the gateway congestion queue for this OSS. All <#> event and alarm messages in the congested gateways congestion queue have been removed. This OSS is now out-of-sync with the events and alarms it had been receiving. Subsequent event and alarm reports shall be forwarded normally.”

7015


In the following list, the probableCause is set to underlyingResourceUnavailable (2.9.3.2.0.0.56)

minor “MIB reload has started.” 7003

minor “MIB sync has started.” 7012



perceivedSeverity


(6 of 6)

perceivedSeverity


major “[ ]has degraded.”(1) 1004

major “[ ]is down.”(1) 1004

major “[ ]is up.”(1) 1004

major “[ ]was removed.”(1) 1004







(1 of 4)




1004

major “[card name] has no call control group.” 1004

major “[cardID] appears to be in faulty.” 1004

major “[cardID] appears to be in service.” 1004

major “[circuit name][circuitID] appears to be faulty.” 1004

major “[circuit name][circuitID] appears to be in service.” 1004

major “[count] RAPID path(s) were affected.” 1004

major “[DTU name] LineStatus BER Alert Exceeded” 1004

major “[DTU name] LineStatus BER Caution Exceeded” 1004

major “[DTU name] LineStatus Gain of Sync” 1004

major “[DTU name] LineStatus Loss of Connectivity to an intermediate element.” 1004

major “[DTU name] LineStatus Loss of Sync” 1004

major “[DTU name] LineStatus Open Circuit and Power Failure” 1004

major “[DTU name] LineStatus Open Circuit” 1004

major “[DTU name] LineStatus Power Failure” 1004

major “[DTU name] LineStatus Short Circuit and Power Failure” 1004

major “[DTU name] LineStatus Short Circuit” 1004

major “[DTU name] LineStatus Unknown” 1004







major “24 Hour Link Availability Threshold Exceeded on Device[deviceName][deviceID].^ENG Monitoring suspended for 24 hours.”

1004

major “Activation from ”Inactive” state has failed for [callName]” 1004



major “ARIC Device [deviceName][deviceID] - NIU [NUI (circuit) ID] appears to be in the network.”

1004

major “ARIC Device [deviceName][deviceID] - NIU [NUI (circuit) ID] appears to be out of the network.”

1004

major “ATM Rx X Clock” (ATM Received X Clock) 1004



major “Attempted to reroute [count] ATM VPC link(s).” 1004

perceivedSeverity


(2 of 4)








major “Communications failure between [CPSS address]. [nodeName] and proxy agent. Reconcile unit [deviceID] now.”

1004



major “CPC index [deviceID]-[circuitID]-|[circuit index] has been disabled due to ISDN call failure.”

1004

major “Deactivation from ”Active” state has failed for [callName]” 1004


major “DMLB unit seems to be in service” 1004

major “DMLB unit seems to be out of service” 1004

major “DSP failure” 1004

major “DSP healthy” 1004

major “ENG Monitoring suspended for 24 hours.” 1004


major “HAPA error [HAPA name] has occurred. Activity switch taking place.^ [nodeName] assuming a standby role.”

1004

major “HAPA error [HAPA name] has occurred. Activity switch taking place.^ [nodeName] assuming an active role.”

1004

major “ISDN call initiated by CPC index [device name]-[device index]-|[device name] has failed.”

1004

major “Link Down trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Link Down trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003

major “Link Up trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise] Variable Bindings: [variable bindings]”

6003

major “Link Up trap received:Ât Uptime: [up time] IP Address: [IP address] Trap Community: [trap community] ^ Enterprise: [enterprise]”

6003



major “Standby Proxy Agent cannot communicate with node [CPSS address]. [deviceID]”

1004



perceivedSeverity


(3 of 4)



Note(1) One of the following strings represents [ ]:

“tty link #linknum linkdesc”“modem link #linknum linkdesc”“ip link #linknum to linkdesc”“tcp link #linknum to linkdesc”“tcp-atm link #linknum to linkdesc”“nm212 link #linknum to linkdesc”where linknum is the link number and linkdesc is the link description


















major “The current config speed is less than the service group bandwidth.” 1004

major “The current config speed is less than the sum of bandwidth” 1004





cleared “Alarm Cleared” (All managedFacilityTP reasons cleared) 1004


perceivedSeverity


(4 of 4)



managedFacilityTP object alarms for ATM circuit emulation cardsThe values in Table App D-5 apply to ATM circuit emulation cards. They describe the signaled values for alarms on managedFacilityTP object when:

• managedObjectClass is set to managedFacilityTP• perceivedSeverity is set to major• additionalText problem description is set to null• additionalInformation problemCode is set to null• probableCause is set as described in Table App D-5

These values apply to ATM circuit emulation cards.

Table D-5 managedFacilityTP object alarms for ATM circuit emulation cards

OID probableCause

1.2.124.113537.1.8.1 “Receive Remote Device Indication Failure”

1.2.124.113537.1.8.2 “Transmit Remote Device Indication Failure”

1.2.124.113537.1.8.3 “Receive Alarm Indication Signal”

1.2.124.113537.1.8.4 “Transmit Alarm Indication Signal”

1.2.124.113537.1.8.5 “Loopback State”

1.2.124.113537.1.8.6 “Test Code”

1.2.124.113537.1.8.7 “Other Failure”

1.2.124.113537.1.8.8 “Idle”

1.2.124.113537.1.8.9 “Far End Equipment Failure”

1.2.124.113537.1.8.10 “Far End Alarm Indication Signal”

1.2.124.113537.1.8.11 “Far End Loss Of Frame”

1.2.124.113537.1.8.12 “Far End Loss Of Signal”

1.2.124.113537.1.8.13 “ALC mismatch”

1.2.124.113537.1.8.14 “Ingress Alarm Indication Signal”

1.2.124.113537.1.8.15 “Ingress RAI”

1.2.124.113537.1.8.16 “Ingress Starvation”

1.2.124.113537.1.8.17 “Ingress Overflow”

1.2.124.113537.1.8.18 “Ingress Loss Of Frame”

1.2.124.113537.1.8.19 “Egress Alarm Indication Signal”

1.2.124.113537.1.8.20 “Egress RAI”

1.2.124.113537.1.8.21 “Egress Starvation”

1.2.124.113537.1.8.22 “Egress Overflow”

1.2.124.113537.1.8.23 “Egress Loss of Frame”

1.2.124.113537.1.8.24 “Egress Other Failure”

1.2.124.113537.1.8.25 “Line Alarm Indication Signal”

(1 of 2)



D.7 managedPack object

When the managedObjectClass is set to managedPack object, other selected alarmRecord attributes and values are:

• perceivedSeverity; described in Table App D-6• additionalText problem description; described in Table App D-6 • additionalInformation problemCode; described in Table App D-6• probableCause; set to equipmentMalfunction (2.9.3.2.0.0.15)

Table D-6 alarmRecord attribute values for managedPack object managedObjectClass

1.2.124.113537.1.8.26 “Line Remote Device Indication”

1.2.124.113537.1.8.27 “Section Loss of Signal”

1.2.124.113537.1.8.28 “Section Loss of Frame”

1.2.124.113537.1.8.29 “Path Synchronous Transport Signal Loss Of Pointer”

1.2.124.113537.1.8.30 “Path Synchronous Transport Signal Alarm Indication Signal”

1.2.124.113537.1.8.31 “Path Synchronous Transport Signal Remote Device Indication”

1.2.124.113537.1.8.32 “Path Unequipped”

1.2.124.113537.1.8.33 “Path SLM”

1.2.124.113537.1.8.34 “Loss of Cell Deletion”

1.2.124.113537.1.8.35 “Loss of Frame”

1.2.124.113537.1.8.36 “Control framing error”

2.9.3.2.0.0.28 “Loss of Frame”

2.9.3.2.0.0.29 “Loss of Signal”

OID probableCause

(2 of 2)

perceivedSeverity









1005

major “[cardID] appears to be faulty.” 1005

(1 of 3)



major “[cardID] appears to be in service.” 1005

major “[cardName][cardID] has no call control group.” 1005

major “[cardName][cardID] has no control group.” 1005

major “[count] RAPID paths were affected.” 1005







major “A fan has failed.” 1001

major “A power supply is failed.” 1001


major “Activation from the “Inactive” state has failed for [callName]” 1005












major “Deactivation from the “Active” state has failed for [callName]” 1005


major “LMI [down] on FSC [resource name][circuit number].” 1005


major “Power supply status has changed to unknown.” 1001







perceivedSeverity


(2 of 3)




















major “The status of the fan is unknown.” 1001


major “Wrong module on card [cardID].” 1005

warning “A fan problem has been corrected.” 1001

warning “Fan is not present.” 1001

warning “One of the following is true: ^A rail voltage is out of tolerance.” 1001

warning “Power supply is not present.” 1001

warning “Power supply problem has been corrected.” 1001


perceivedSeverity


(3 of 3)

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 E-1October 2006 95-6040-01-00-C

E. alarmInfo

E.1 additionalInformation attribute E-2

E.2 additionalText attribute E-4

E.3 monitoredAttributes E-5

E.4 perceivedSeverity attribute E-5

E.5 probableCause attribute E-5

E.6 thresholdInfo E-6

E.7 specificProblems E-7

E.8 alarmInfo formats for alarms forwarded by the 5620 NM fault management system or by the ALMAP AS-IM component E-7

E. alarmInfo

E-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

E.1 additionalInformation attribute

The additionalInformation attribute contains:

• a problemCode, assigned by the 5620 CMIP, for alarms generated by 5620 NM trouble tickets, or,

• the value is absent for alarms reported through the 5620 NM fault management system or through the ALMAP AS-IM component

Figure E-1 provides an ASN.1 fragment that describes the additionalInformation attribute, which is part of the set of ManagementExtension defined in ITU-T standard X.721. This fragment shows how problemCode and selected ObjectName are provided in the additionalInformation attribute. The 5620 CMIP uses the Information field to hold extra values, thereby extending the usefulness of this parameter.

Figure E-1 ASN.1 definition-additionalInformation attribute for trouble ticket alarms

Values for the problemCode field are computed using the following formula:

problemCode = (5620 NM trouble fault type × 1000) + (5620 NM fault number)

Table App E-1 lists some of the possible 5620 NM trouble ticket fault types and 5620 NM fault numbers and provides the computed 5620 CMIP problemCode. Not all of these fault types and fault numbers are supported by the 5620 CMIP. See Appendix D.1 for details.

Note 1 — additionalInformation attribute formats differ for alarms generated from trouble tickets, and for alarms generated by the 5620 NM fault management processes.

Note 2 — The additionalInformation attribute is set to null for ATM circuit emulation card managedFacilityTP alarms and log alarms

Notes

1. The problemCode field contains an integer (value range 0 to 8003).

2. The name of the alarm object for paths is the 5620 NM GUI path name.For all other objects it is the 5620 NM GUI object name.

Information ANY DEFINED BY SEQUENCE {

problemCode (1)

selectedObjectName (2)

}

15344

E. alarmInfo


Table E-1 Examples of some 5620 CMIP trouble ticket problemCode values

Problem type 5620 NM trouble fault type

Fault description 5620 NM fault number

5620 CMIP problemCode

hardware 1 power supply failure 1 1001

wrong card in slot 2 1002

wrong module on card 3 1003

device failure 4 1004

card failure 5 1005

tail end circuit gone 6 1006

cables busted 7 1007

ringing generator failure 8 1008

modem is busted 9 1009

slot is empty 10 1010

NVM integrity error 11 1011

RAM integrity error 12 1012

ROM integrity error 13 1013

activity switch 14 1014

node 15 1015

reconcile 16 1016

device 17 1017

cable 18 1018

transfer database 19 1019

software 2 alarm queue overflow 1 2001

unsupported card 2 2002

unsupported module 3 2003

not configured locally 4 2004

unsupported status 5 2005

alarm 6 2006

busied out 7 2007

TT max hops 8 2008

software download 9 2009

communications 3 cannot talk to node 1 3001

trouble ticket 4 created by user 1 4001

created by system 2 4002

custom node 5 GFC alarm 1 5001

custom node log 2 5002

(1 of 2)

E. alarmInfo


E.2 additionalText attribute

The additionalText attribute is a string, limited to 256 characters, consisting of the following subfields:

• the problem description string• the name of the alarmed object, which can be a user label

The subfields are separated by the string “space hyphen space” (for example, “ - ”).

The problem description subfield provides a textual description of the alarm condition. For alarms forwarded by the 5620 NM fault management system, the additionalText attribute displays the same information contained in the additionalText field of the AS tool USM alarm.

The problem description subfield is null for ATM Circuit Emulation port alarms and log alarms. Instead, a description of these ATM Circuit Emulation alarms is provided by the probableCause attribute. See Table App D-5 for more information.

LAN node 6 system table 1 6001

interface row 2 6002

LAN trap 3 6003

circuit group 4 6004

LAN path 5 6005

5620 CMIP 7 MIB out of sync 1 7001

no reload 2 7002

reload started 3 7003

path 4 7004

change server queue overflow 5 7005

abnormal shutdown 6 7006

node status reload started 7 7007

reload abort 8 7008

device failure 9 7009

start-up problem 10 7010

MIB sync started 12 7012

update reload started 13 7013

driver/OSS association congestion queue overflow

15 7015

administration 8 password violation 1 8001

license violation 2 8002

invalid license key 3 8003

Problem type 5620 NM trouble fault type

Fault description 5620 NM fault number

5620 CMIP problemCode

(2 of 2)

E. alarmInfo


The name of the alarmed object for bMGroomedCircuit objects is the 5620 NM GUI path name; for all other objects, the name of the alarmed object is the 5620 NM user label.

E.3 monitoredAttributes

This attribute is only reported when the capacityAlarmThreshold attribute is exceeded on a log. See Appendix D.4 for more information.

E.4 perceivedSeverity attribute

The perceivedSeverity attribute is assigned by the 5620 CMIP to provide a ranking of the severity of an alarm. Table App E-2 describes the perceivedSeverity attribute values.

Table E-2 perceivedSeverity attribute values

E.5 probableCause attribute

probableCause attribute values depend on the source of the node or network object emitting the alarm. Depending of the source of the alarm, you can receive an integer or an OID value.

Use the specificProblems file on the 5620 NM in the /opt/netmgt/ALMAP/as/conf/repository/locale/C.ISO-8859-1 directory to determine the OID to text translation of the local or global value of the probableCause.

Table App E-3 describes probableCause attribute values for alarmRecords resulting from 5620 NM trouble tickets.

perceivedSeverity Value Description

Indeterminate 0 Indicates that the severity level cannot be determined

Critical 1 Indicates that a service-affecting condition has occurred and immediate corrective action is required

Major 2 Indicates that a service-affecting condition has developed and an urgent corrective action is required

Minor 3 Indicates the existence of a fault condition that is not service-affecting; take corrective action to prevent a more serious fault

Warning 4 Indicates the detection of a potential or impending service affecting fault before any significant effect occurred; you should take action to further diagnose and correct the problem to prevent it from becoming a more serious service-affecting fault

Cleared 5 Indicates the clearing of one or more reported alarms

E. alarmInfo


Table E-3 probableCause values resulting from trouble tickets

Table App E-4 describes the probableCause attribute values for alarmRecords resulting from the 5620 CMIP Gateway Station faults.

Table E-4 probableCause values signaled by the 5620 CMIP

Notes(1) alarmRecord managedObjectClass set to managedElement(2) alarmRecord managedObjectClass set to log

There are a set of defined probableCause attribute values that are specific to ATM circuit emulation cards and are signaled only for managedFacilityTP objects. If the alarmRecord managedObjectClass attribute is a managedFacilityTP and the additionalText attribute value is null, the alarm reason is provided by the probableCause attribute OID. See Table App D-5 for details.

E.6 thresholdInfo

This attribute is reported only when:

• the capacityAlarmThreshold attribute is exceeded on a log. See Appendix D.4 for more information.

• there is threshold information in the alarm, for example TCAs. The OID representing the attribute that exceeded the threshold, and the value of the attribute that exceeded the threshold is reported as -1, which indicates that the value of the attribute was not available when the alarm was reported.

OID Description

2.9.3.2.0.0.6 Communications subsystem failure applicable to bMFacility, bMGroomedCircuit and managedFacilityTP objects

2.9.3.2.0.0.15 Equipment malfunction applicable to managedElement and managedPack objects

OID Description

2.9.3.2.0.0.39 (1) Queue size exceeded

2.9.3.2.0.0.46 (1) Software error

2.9.3.2.0.0.47 (1) Software program abnormally terminated

2.9.3.2.0.0.49 (2) storageCapacityProblem

2.9.3.2.0.0.56 (1) Underlying resource unavailable

2.9.3.2.0.1.9 (1) Information out of sequence; from securityAlarmCause as defined in ITU-T X.721 and X.736

E. alarmInfo


E.7 specificProblems

The specificProblem attribute may contain a short description of the alarm in OID format. The description can be used for troubleshooting.

specificProblems are ITU-T, ISO, and vendor-specific definitions of problems related to the alarms. A list of specific problems and matching OIDs is available in the specificProblem file in the /opt/netmgt/ALMAP/as/conf/repository/locale/C.ISO-8859-1 directory on the 5620 NM.

E.8 alarmInfo formats for alarms forwarded by the 5620 NM fault management system or by the ALMAP AS-IM component

The following is an example of an alarm received by the 5620 NM fault management system.

EventReportArgument SEQ

managedObjectClass CHOICE

globalForm OID 1.2.124.113537.1.1.1

managedObjectInstance CHOICE


[0] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

pString GraphicString len=7 "Alcatel"

[1] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 0

[2] SET OF len=1

[0] SEQ

E. alarmInfo



attributeValue ANY

NameType CHOICE

numericName INT 1

[3] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

numericName INT 1

[4] SET OF len=1

[0] SEQ


attributeValue ANY

NameType CHOICE

pString GraphicString len=2 "B3"

eventTime GeneralizedTime len=19 "20031203150611-0500"

eventType CHOICE

globalForm OID 2.9.3.2.10.11

eventInfo ANY

AlarmInfo SEQ

probableCause CHOICE

localValue INT 51

specificProblems SET OF len=1

[0] CHOICE

D_Name0 OID 1.3.12.2.1006.69.1.1.1.11.441

perceivedSeverity ENUM 1

backedUpStatus BOOL absent

backUpObject CHOICE absent

trendIndication ENUM absent

E. alarmInfo


thresholdInfo SEQ absent

notificationIdentifier INT absent

correlatedNotifications SET OF absent

stateChangeDefinition SET OF absent

monitoredAttributes SET OF absent

proposedRepairActions SET OF absent

additionalText GraphicString len=47 "BER Caution Exceeded;B3;5,0 -

Card toady/S1-B3\00"

additionalInformation SET OF absent

[0] SEQ

identifier OID 2.4.5.1.2.0.7.100

significance BOOL True

information ANY

Boolean BOOL True

All alarms are ITU-T X.721 compliant. However, the values of the attributes in a specific alarm report may differ between alarms that are reported through 5620 NM trouble tickets, the 5620 NM fault management system, and the ALMAP AS-IM component. The differences between the types of alarms are:

• for alarms reported through the 5620 NM fault management system only, the values for the managed object class and managed object instance fields may refer to objects not representd in the MIB

• the value of OIDs used in alarms are based on ITU-T X.733 and on vendor specific valies; the value of OIDs used in alarms can be found in the source identified in Table E-5

• the problemCode that appears in the additionalInformation field is only available for alarms reported through the 5620 NM trouble tickets

Table E-5 describes how to interpret the information displayed in the alarmInfo format for alarms generated by the 5620 NM fault management system and the ALMAP AS-IM component. See the remaining sections in this chapter for information about some of the alarm fields.

E. alarmInfo


Table E-5 alarmInfo format fields for alarms reported 5620 NM fault management system and the ALMAP AS-IM component

Field Explanation

managedObjectClass For a complete list of managed object classes, see the ClassIDs file in the /opt/netmgt/ALMAP/as/conf/repository/locale/C.ISO-8859-1 directory on the 5620 NM.

managedObjectInstance Represents the full distinguishedName for the instance raising the alarm.

For a complete list of potential naming attributes, see the registrationIds file in the /opt/netmgt/ALMAP/as/conf/repository/locale/C.ISO-8859-1 directory on the 5620 NM.

eventTime Represents the time that the alarm was raised on the node.

eventType Represents the ITU standard event type

eventInfo A sequence of information that contains the rest of the alarm information fields within it.

probableCause Probable cause is configuration or customization error. For alarms reported through the 5620 NM fault management system, the integer values for probable causes are mapped based on ISO-8859-1 standards.

For alarms reported through the ALMAP AS-IM component, the OID values are based on ISO-8959-1 standards.

For a complete list of probable causes, see the probableCause file in the /opt/netmgt/ALMAP/as/conf/repository/locale/C.ISO-8859-1 directory on the 5620 NM.

specificProblems The specific problems column may contain a short description specifically describing the event or alarm. The description can be used for troubleshooting. Not all alarms contain specific problems.

Specific problems are ITU-T, ISO, and vendor-specific definitions of problems related to the alarm. A list of specific problem text and matching OIDs is in the /opt/netmgt/ALMAP/as/conf/repository/locale/C.ISO-8859-1 directory on the 5620 NM.

perceivedSeverity The standard is taken from ITU-T X.721.

additionalText Information sent from the node. This is the alarm text field from legacy alarm files, when the alarm is from an NCI-based node. This is displayed as user label in the AS tool USM.

additionalText fields also show data supplied by the node in the alarm, or appended by the fault manager, or both.

The friendly name or selected object name of the object against which the alarm has been raised appears after the – (dash)

Subcode and param information is shown for NCI-based alarms, separated by a semi-colon. They appear even if empty.

additionalInformation The value of this field is “absent”.


Glossary

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 GL-1October 2006 95-6040-01-00-C

Glossary

2B1Q two binary, one quarternary

2B1Q is a BRI ISDN line encoding technique that uses two bits to represent four variations in amplitude and polarity.

4WTO 4-wire transmission only

4WTO is a voice channel unit supported on 3600, 3600+, 3664, and 3600 MSS nodes that is similar to an EandM. 4WTO is in an “always off-hook” condition. It passes traffic over a 4-wire local loop.

5523 AWS See 5620 DSL EM.

5620 CMIP OSS Interface Gateway

The 5620 CMIP OSS Interface Gateway is the 5620 CMIP software that runs on the 5620 CMIP Gateway Station.

5620 DSL EM 5620 Digital Subscriber Line Element Manager

The 5620 DSL EM manages network elements, such as ASAMs and ISAMs.


A NetworkStation is a Sun workstation running or communicating with the 5620 NM Network Manager software. There are several types of NetworkStations: active, standby, Operator Server NetworkStation, and Operator Position NetworkStation. Typically, the active, standby, and Operator Server NetworkStations are operated by the service provider. An Operator Position NetworkStation is used by service users.

AAL1 ATM adaptation layer - type 1

AAL1 is a specific type of ATM adaptation intended for constant bit rate service applications.

Glossary

GL-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

ABR available bit rate

ABR is an ATM Forum service category defined to support both connectionless and connection-oriented services. It is used for applications that have unpredictable bandwidth requirements. All ABR connections share resources fairly and receive as much bandwidth as is available on an as-needed basis.

ABR provides guaranteed low cell loss but does not specify an upper limit on delay. ABR is primarily intended for LAN emulation services.

ACELP algebraic code excited linear prediction

ACELP is an ITU-T standard algorithm that compresses voice transmission to 8 kb/s.

ACSE Protocol Association Control Service Element Protocol

ACSE is the OSI protocol for the application service element responsible for association establishment and release.

ADPCM adaptive differential pulse code modulation

ADPCM is a voice compression technique that reduces the bandwidth requirements of a voice path to 32 kb/s. There are two types of ADPCM signaling: delta and transitional.

ADSL asymmetrical digital subscriber line

ADSL is a digital telecommunications protocol designed for an upstream data flow (client-to-server) that is a fraction of the downstream data flow (server-to-client). The upstream data flow is measured in kilobits while the downstream data flow is measured in megabits.

AESA ATM end system address

The AESA is a 20-byte ATM address that identifies one or more ATM endpoints for switched virtual connections.

AIS alarm indication signal

An AIS is a code sent downstream in a digital network to indicate that a traffic-related defect has been detected. It is also known as an RAI or yellow alarm.

alarm An alarm is a node-generated message created as a result of an event, such a path status change.

ANSI American National Standards Institute

ANSI is a nonprofit organization that develops and publishes standards, and represents the U.S. in some international standards groups.

APDU application protocol data unit

The APDU is a PDU that operates at the application layer of the OSI reference model.

Glossary


API application programming interface

An API is a set of programming functions and routines that act as an interface to the network for application programs. APIs translate high-level program code into low-level computer instructions that run the network. Thus, application programs (for example, word processors) can communicate with low-level programs handling network data traffic.

Application Key The Application Key is a software security code used to activate authorized software features and products during startup. It also verifies network limitations with respect to the number of nodes and workstations.

APS automatic protection switching

A protocol defined for SONET/SDH that provides switching amongst redundant interfaces.

ASCII American Standard Code for Information Interchange

ASCII defines codes for a character set in binary (on/off) bits. Out of a total of 128 characters, 96 are assigned to the alphabet, numbers, punctuation marks, and other symbols. The remaining characters are assigned to control functions.

ASN.1 Abstract Syntax Notation

ASN.1 is used by the 5620 CMIP to describe and define data types.

ATM asynchronous transfer mode

ATM is a multiplexing and switching technique in which information is organized into fixed-length cells, with each cell consisting of an identification header field and an information field. ATM is asynchronous in the sense that the use of the cells depends on the required or instantaneous bit rate.

Atomic set Atomic set refers to a CMIP set command that changes the value of an unlocked groomed circuit's bandwidth; it results in the groomed circuit being disconnected and then reconnected with its new bandwidth.

Bc committed burst rate

The Bc is the maximum number of bits of user data that the network commits to transfer over the committed rate measurement interval (Tc), under normal circumstances.

Be excess burst rate

The Be is the maximum number of bits of uncommitted user data in excess of Bc that the network attempts to transfer over the committed rate measurement interval (Tc).

BME Bandwidth Management Ensemble

Glossary


BRI basic rate interface

BRI is an ISDN interface for homes and small businesses that consists of two 64Kbps B channels for voice or data and one 16Kbps D channel for signaling.

CAS channel associated signaling

CAS is a type of E1 link in which 4 bits of signaling per timeslot are multiplexed into timeslot 16.

CBR constant bit rate

CBR is an ATM service or traffic class that carries traffic. It is characterized by a service bit rate specified by a constant value and an evenly spaced cell stream.

CCE channelized circuit emulation

CCITT Consultative Committee International on Telephones and Telegraphy

CCS common channel signaling

CCS is a type of E1 link where time-slot 16 is used for message-oriented signaling, such as ISDN primary rate access.

CDV cell delay variation

CDV is a measure of cell clumping, or how much more closely cells are spaced than the nominal interval.

CDVT cell delay variation tolerance

CDVT is the upper limit of allowable cell delay variation. When cells from two or more ATM connections are multiplexed, cells of an ATM connection may be delayed while cells of another ATM connection are inserted at the output of the multiplexer. Similarly, some cells may be delayed while physical layer overhead or OAM cells are inserted.

CE circuit emulation

See circuit emulation.

CE_agent process The CE_agent process resides on the 5620 NM NetworkStation. The CE_agent process translates commands and requests from the CE_driver process and passes them to the 5620 NM database. The 5620 NM implements the changes in the network and updates its database. The CE_agent process also passes responses to the CE_driver process.

CE_chgsrv process The change server process (CE_chgsrv) monitors changes in the 5620 NM database and manages the CE_chgsrv queue. The queue stores changes during a MIB reload or during periods when the link between the CE_agent process and the CE_driver process is down. The CE_chgsrv process also passes 5620 CMIP alarms, along with trouble ticket and path status change alarms, to the CE_driver process. The CE_chgsrv process receives events from the 5620 NM database and passes them to the CE_driver process as updates.

Glossary


CE_control process The CE_control process is a set of commands that run from the 5620 CMIP Gateway Station. They allow the operator to stop or start 5620 CMIP processes. They also provide status information.

CE_driver process The CE_driver process runs on the Gateway Station and manages the system object, the MIB, and the information flow between the 5620 CMIP OSS Interface Gateway and the OSS and between the 5620 CMIP OSS Interface Gateway and the 5620 NM. It has options that allow it to be configured by the operator.

CE_reload process The CE_reload process manages MIB reloads. This process automatically activates whenever a MIB reload request is received from either the CE_driver or CE_control process. The CE_reload process deactivates once the MIB reload is complete.

CES circuit emulation services

CFR channelized frame relay

circuit emulation Circuit emulation allows the connection of TDM circuits to ATM networks so that TDM traffic can be routed over ATM networks.

class An object class is the kind (or type) of object. There can be many instances of an object class.

CLCC closed loop congestion control

CLP cell loss priority

CLP is a one-bit field in the ATM cell header that indicates the loss priority of an individual cell.

CLR cell loss ratio

The CLR is the ratio of discarded cells to cells that are successfully transmitted.

CMIP Common Management Information Protocol

The 5620 CMIP uses CMIP commands and messages to interface with the OSS and to manage the MIB. It defines how information is exchanged, modified and stored.

CMIS Common Management Information Service

CMIS is the service-level definition of CMIP.

CMISE common management information service element

CMISE is the application service element responsible for carrying network management semantics.

CMOT CMIS/CMIP Over TCP/IP

CMOT is the name given to OSI management protocols running over the TCP/IP protocol stack. The protocols are used to manage a TCP/IP or mixed TCP/IP and OSI network.

Glossary


CODEC coder/decoder

CODEC equipment converts voice signals from analog to digital form, for use with digital PBXs and other digital transmission systems. The digital signals are then converted back to their original analog form.

CPSS control packet switching system

CPSS is a proprietary network protocol for communication between vendor equipment. Similar to X.25, CPSS is a packet-switched system used to transfer configuration and status information between nodes.

CRC cyclic redundancy check

A CRC is an error-detection scheme for bit-oriented data communications protocols wherein the integrity of a received frame is checked using a polynomial algorithm based on the content of the frame, and then matched with the result performed by the sender and included in a field appended to the frame.

DCE data communications equipment

DCE refers to the gender of the interface on a data device, such as a modem. The pinout wiring is such that pin 2 receives data and pin 3 transmits data. It must be connected to a DTE device.

DCS digital cross-connect system

DCS is a digital switching device for routing and switching lines and portions of lines among multiple ports. It performs like a normal switch, except that connections are typically set up in advance of the call, not together with the call, as in most normal low-bandwidth communications such as voiceband voice and data.

DDS dataphone digital service

DDS is a rate adaption service provided by AT&T for the transmission of data through an all-digital network using DS-0-A and DS-0-B formats. The ITU-T version of DDS is the X.50 Standard.

DE discard eligibility

DE is a bit in the frame relay header that, when set, tags the frame as eligible for discard should there be congestion.

DLC data link connection

DLC represents a virtual circuit segment between an end-user device and a network frame relay device or between one network frame relay device and another.

DMDS digital media distribution service

DMDS is an IP multicast solution that uses ADSL to provide integrated delivery of IP-based media sources (such as video channels and music channels), high-speed Internet access, and voice traffic over a reliable, point-to-multipoint ATM connection infrastructure.

Glossary


DNIC data network interface circuit

DNIC line cards and modules are supported on all 3600 MainStreet Family Bandwidth Managers. They support high-modularity connections from a great variety of remote data devices to the nodes via the 2600 MainStreet series DTUs. The 2B1Q line cards connect the nodes to data devices via the 2700 MainStreet series of DTUs.

DS-0 digital signal level 0

DS-0 is a worldwide standard for PCM digitized voice. It operates at 64 kb/s.

DS-3 digital service, level 3

DS-3 is the equivalent of 28 T1 time slots (T3), each operating at 44.736 Mbps.

DSI digital speech interpolation

DSP digital signal processor

A DSP is a microprocessor that is optimized for signal-processing applications.

DSPM digital signal processor module

The DSPM on 3660 and 3612 nodes provides two resources that support voice compression, G3Fax/modem and VoFR.

DTE data terminal equipment

DTE refers to the gender of the interface on a data device, such as a PC. The pinout wiring is such that pin 2 transmits data and pin 3 receives data. The DTE must be connected to a DCE device.

DTMF dual tone multifrequency

Dual tone multifrequency address signaling is a method of signaling using the voice transmission path. This method employs 16 distinct signals, each composed of two voiceband frequencies These 16 tones may also be called Touch-Tone signals.

E1 European digital signal level 1

E1 is a level 1 digital trunk operating at 2.048 Mbps that is used outside of North America and Japan. E1 is made up of 32 DS-0 channels. Channel 0 is reserved for framing and alarm information and channel 16 is usually used for signaling, leaving 30 channels to carry data.

E3 European digital signal level 3

E3 is the European standard used instead of DS3. E3 is equivalent to 16 E1 timeslots and operates at 34.368 Mb/s.

Glossary


EandM ear and mouth

EandM is a colloquial term for receive and transmit. It is an analog interface. EandM is a trunk arrangement used for two-way switch-to-switch or switch-to-network connections. EandM is also frequently used for computer telephony systems to switch connections.

EC error correction

EFCI explicit forward congestion indication

EIR excess information rate

ELS event logging system

ELS is the graphical-based log tool used by network management products to record events.

ESC Edge services card

The ESC line card provides a high-speed, packet-based interface that processes ATM packets. You can use the ESC card to:

• create an edge switch with high-density cell relay UNI services• allow ATM and FR raffic aggregation down to DS1• provide IMA transmission protocol over DS1 cell relay links. This IMA

functionality is different from the basic IMA protocol because it does not work on physical links but on tributary channels configured as cell relay links

• allow mobile operators to aggregate cells into a single managed platform, which entails reduced costs and ease of management and maintenance

ESF extended super frame

ESF is a DS-1 framing format in which 24 DS-0 time slots plus a coded framing bit are organized into a frame that is repeated 24 times to form a superframe.

Ethernet Ethernet is a data link layer protocol for interconnecting computer equipment into LANs, jointly developed by Xerox, Digital Equipment Corporation, and Intel. This standard forms the basis for IEEE 802.3.

The Ethernet protocol specifies how data is placed on and retrieved from a common transmission medium. It is used as the underlying transport vehicle by several upper-level protocols, including TCP/IP and UDP/IP.

ETSI European Telecommunications Standards Institute

ETSI is the primary telecommunications standards organization in Europe.

FASTBus frame relay adaptive switching and transport bus

FASTBus is a 100 Mbps bus used to interconnect 36120 FASTBus products (FRE, PE, and FRATM).

Glossary


FDL facilities data link

An FDL is a 4000 bits/s communication path between the two ends of a T1 ESF link that uses a message protocol to send information in 12 of the 24 framing bits in a superframe.

FECN forward explicit congestion notification

FRE frame relay engine

An FRE is a frame-switching card that resides within the 3600, 3600 MSS and 36120 MainStreet node environment. The FRE switches frames between 3600, 3600 MSS and 36120 MainStreet nodes, WAN interfaces, and the FASTbus.

FRL frame relay link

FRP frame relay path

An FRP is an end-to-end logical frame relay connection, equivalent to a PVC. Valid endpoints are ports and timeslots.

FRS frame relay switch

An FRS is a frame-switching card that resides within the 3600, 3600 MSS and 36120 MainStreet node environment. The FRS switches frames between 3600, 3600 MSS, and 36120 MainStreet node WAN interfaces.

FSC frame stream circuit

An FSC is a circuit on an FRS or FRE card that switches frame relay traffic. It is the endpoint of a frame stream.

FTP file transfer protocol

FTP is the Internet standard protocol for transferring files from one computer to another.

Fully distinguishedName

A fully distinguishedName is a unique identification of a managed object. A fully distinguishedName reflects a hierarchical organization of managed objects and, typically, the organization of the MIB, since it allows for a very efficient object lookup mechanism.

An fully distinguishedName is composed of a set of relative distinguishedNames. A relative distinguishedNames is a name-value pair where the name is referred to as a distinguishing name. A distinguishing name corresponds to a class of names in object-oriented terminology. A relative distinguishedName value is unique within its parent context.

Gateway Station The 5620 CMIP Gateway Station is the Sun workstation that runs the 5620 CMIP OSS Interface Gateway software. The Gateway Station must be connected to both the 5620 NM NetworkStation and the OSS workstation. The CE_control and CE_driver processes run on the Gateway Station.

GDMO Guidelines for the Definition of Managed Objects

GDMO is the object definition language developed by ISO for use with CMIP-based systems.

Glossary


GFC generic flow control

GFC is a field in the ATM header that provides local flow control. It has local significance only and the value encoded in the field is not carried end-to-end.

GRF trunk A GFR trunk is a communication channel that carries X.25 encapsulated in frame relay frames between trunk circuits forming the X.25 backbone.

GUI graphical user interface

A GUI is a computer user interface that incorporates graphics to make software easier to use.

HCM high capacity multiplexing

HCM is a proprietary rate adaption scheme used to format low-speed data streams. It is employed by the 3600 series bandwidth management products. HCM uses a data framing technique that formats data into an 8x10 matrix, where each element represents 800 b/s. This framing technique may be used with SRMs to improve network bandwidth utilization.

HCV high capacity voice

HCV is a proprietary voice compression technique that reduces the bandwidth requirement for voice paths from 64 kb/s to either 8 kb/s or 16 kb/s.

HDLC high-level data link control

HDLC is an ISO standard for serial data communication. It is a family of bit-oriented protocols providing frames of information with address, control and frame check sequence fields. It is considered a superset of several other protocols such as SDLC, LAP, LAPB, LAPD.

I.460 I.460 is a transparent data protocol using (n x 8) kb/s divisions, where n is a number from one to eight.

icon An icon is a graphical symbol that represents an object or function.

ILMI integrated local management interface

ILMI is an ATM Forum interim specification for network management functions between an end user and a public or private network, and between a public network and a private network. ILMI is based on a limited subset of SNMP capabilities.

A 5620 NM-managed network uses ILMI links for ATM address retrieval, local management of cell relay interfaces, and 5620 NM autodiscovery of end-user nodes.

instance An instance is an individual occurrence of an object in a class. For example, a network of twenty nodes could have a power supply in each node; each of these power supplies would be an instance of the equipment managed object class.

intermediate termination point

An intermediate termination point is any DS-0 pathpoint that has physical links associated with it on the 5620 NM user interface.

Glossary


ISDN integrated services digital network

ISDN is a technology that allows telephone voice connections and digital data network services to be carried over the same line. The standards are specified by the ITU-T (formerly the CCITT).

ISL inter-shelf link

An ISL is the 800 Mb/s transmission link used between access shelf and switching shelf connections. ISL is cabling that carries traffic between the switching shelf and each peripheral shelf. Each ISL has up to two bundled MMF fiber optic cables that create an Up ISL and a Down ISL between shelves.

ISO International Organization for Standardization

The ISO is an official body responsible for standards, including network management standards.

ITU-T International Telecommunications Union-Telecommunications

The ITU-T is the telecommunications standardization sector of the ITU. It is an advisory committee established under the United Nations to recommend international telecommunications standards.

LAN local area network

LAPB link access procedure balanced

LAPB is the most common data link control protocol used to interface X.25 DTEs. It is a full-duplex, point-to-point bit-synchronous protocol used in packet-switched networks.

LDCELP low delay code excited linear prediction

LDCELP is an ITU-T standard algorithm that compresses voice transmissions to 16 kb/s.

LGE loop start/ground start–exchange

LGE is the exchange-end voice interface that supports loop start and ground start signaling.

LGS loop start/ground start–subscriber

LGS is the subscriber-end voice interface that supports loop start and ground start signaling.

LMI local management interface

LMI is a frame relay link management protocol defined by Digital Equipment Corporation, Nortel, Cisco, and Stratacom.

LOC loss of continuity

LOS loss of signal

LOS indicates that no valid signal can be detected at the transmission interface.

Glossary


managed object A managed object is an object that is a view of one or more network components. These components may exist independently or may support the management of other components. A managed object may also represent a relationship between components.

MBS maximum burst size

MBS is a traffic parameter that specifies the maximum number of cells in a burst that can be transmitted at the peak rate. In the signaling message, the burst tolerance is conveyed through the MBS, which is coded as a number of cells.

MIB management information base

The MIB is an object-oriented database that stores objects representing the components of the network. It is managed by the 5620 CMIP through CMIP commands.

MIR minimum information rate

MIR is the minimum data transfer rate for a frame relay, VPC, or VCC path.

MJU multijunction unit

An MJU is a type of SRM that functions as a multidrop data bridge. Its inputs and output are formatted for DS-0-A.

MORTs managed object referring to test

MORTs is a managed object that is used to refer to the functionalities that are being tested. It is defined by the ITU-T in the standard X.745.

MORTS Package MORTS Package is a standard attribute’s package as defined by the ITU-T in the standard X.745.

MTSM multiservice traffic shaping module

The MTSM enhances traffic management functionality on UCS-2 cards within 7470 MSP nodes, Release 3.1 or later, and 7670 RSP nodes. The MTSM provides traffic shaping in both ingress and egress directions on a per-port basis for each service category of VPC and VCC paths, and dynamic shaping for ABR connections using VSVD.

NIU network interface unit

An NIU is a device that performs interface functions, such as code conversion, protocol conversion, and buffering, required for communications to and from a network. NIUs reside at the subscriber site and contain radio modems, interfaces to the subscriber equipment, and software to interface a wireless signal to the ATM network.

NMF Network Management Forum

NMF is the former name of the TMF.

Glossary


NMTI node management terminal interface

An NMTI is a node management interface on a network node that is used for configuration and maintenance functions. NMTI sessions are initiated through a VT-100 terminal or a PC with VT-100 emulation software.

NNI network-network interface

An NNI is the interface between two networks that operate under different administrative domains.

nrt-VBR nonreal-time variable bit rate

The nrt-VBR is an ATM service category that guarantees low cell loss and low delay for applications such as video and frame relay, that are characterized by an on/off source with known, predictable transmission patterns. During the on period, cells are transmitted at the peak information rate. No cells are transmitted during the off period.

nrt-VBR is a variant of the VBR service category that is available only for VPC and VCC paths. The other variant of VBR available for these paths is rt-VBR. The 3600 MainStreet family bandwidth managers treat nrt-VBR and rt-VBR identically for routing and rerouting purposes and use both to calculate the total VBR bandwidth utilization.

NVM non-volatile memory

NVM is battery-powered memory that does not lose its contents when a system is turned off.

OAM operations, administration, and maintenance

object Objects are representations in the MIB of components of the network. Objects are represented by the 5620 CMIP in accordance with OSI and TMF standards for managed objects. There are classes and instances of objects.

OC-12 optical carrier-level 12

OC-12 is an optical SONET signal at 622.08 Mb/s.

OC-3 optical carrier-level 3

OC-3 is an optical SONET signal at 155.52 Mb/s.

OID object identifier description

An OID is a unique identifier for an object. Each OID is composed of a sequence of integers known as subidentifiers. The numbers 1.2.124.360501.1.341 are a sample OID. These numbers, when read from left to right, define the location of the object in the MIB tree structure. OIDs and other objects are defined using ASN.1.

OMNIPoint Open Management Interoperability Point

OMNIPoint is a network management standard produced and collated by the TMF.

Glossary


operator A 5620 CMIP operator monitors the 5620 CMIP Gateway Station. The 5620 CMIP operator can:

• control and operate the 5620 CMIP• configure communication between the 5620 CMIP, the OSS, and the

5620 NM• manage the 5620 CMIP MIB• monitor the Gateway Station system and communication messages

An OSS operator monitors an OSS workstation. Through the 5620 CMIP, the OSS operator can:

• configure some network objects• manage events• maintain an inventory of network equipment

A 5620 NM operator monitors and manages a 5620 NM NetworkStation.

OSI open systems interconnection

OSI is a family of ISO standards that define interconnection between systems. Areas covered include systems management, directory, and transaction processing.

OSS operations support system

OSS comprises the methods and procedures that directly support the daily operation of the telecommunications infrastructure.

OSS Interface Agent The OSS Interface Agent is the interface between the 5620 CMIP OSS Interface Gateway software and the 5620 NM software. The OSS Interface Agent resides on the 5620 NM NetworkStation. The CE_agent, which is one of the OSS Interface Agent processes, is not a TMF-compliant agent.

OUI organizationally unique identifier

PCI protocol control information

PDU protocol data unit

PDU is the unit of data in the OSI reference model. It contains both protocol-control information and user data from the layer above and is used by two processes to coordinate their interactions.

PID profile identifier/identification

PIR peak information rate

PIR is the peak data transfer rate for a frame relay, VPC, or VCC path.

PLL phase locked loop

PLL refers to a circuit used to regenerate the far-end clock from the incoming high-capacity multiplexing stream.

Glossary


pluggable node A pluggable node is a node for which the type is defined by a software plug-in. A plug-in is installed using a 5620 NM package for each pluggable node type. After a plug-in is installed, 5620 NM users can create nodes using the type defined by the plug-in.

PNNI private network node interface

PNNI is a protocol that is used between private ATM switches. PNNI includes a protocol for distributing topology information between switches and clusters of switches that is used to compute paths through the network, and a signaling protocol that is used to establish point-to-point or point-to-multipoint connections across the ATM network. The signaling protocol is based on ATM Forum UNI signaling, with extensions to support PNNI functions.

PPDU presentation protocol data unit

The PPDU is a PDU that operates at the presentation layer of the OSI protocol.

Presentation protocol The presentation protocol is the protocol used by the presentation layer of the OSI seven-layer reference model for protocols and interfaces.

PRI Primary rate interface cards terminate the channelized network links that interconnect one 3600, 3600 MSS, 3664, or 36120 MainStreet node to another across the network.

process A process is a software application that produces a specific result. The 5620 CMIP has a number of processes, two of which are CE_control and CE_driver. Some 5620 CMIP processes run on the Gateway Station and some run on the NetworkStation.

PSI programmable serial interface

PSN Link packet switched network link

PSN links are logical links between two PE nodes, representing the MPLS connectivity.

PU peripheral unit

PVC permanent virtual circuit

PVC is a link with a static route defined in advance, usually by manual setup. From an ATM perspective, a PVC is an end-to-end logical ATM path. A PVC can be a VCC or a VPC.

Q3 Q3 is a management interface that is part of the ITU-T TMN architecture.

RBS robbed bit signaling

RBS is a signaling technique used in T1 that steals the least significant bit of a channel every few frames to use as a signaling bit.

RDI remote defect indication

RDI is a signal returned to the transmitting equipment upon detection of certain defects on the incoming signal.

Glossary


redundancy With the 5620 CMIP, redundancy means having two Gateway Stations connected to the OSS. Redundancy allows one 5620 CMIP to take over in the event that the other's communication fails.

With the 5620 NM, redundancy means having two 5620 NM NetworkStations—an active and a standby. Redundancy allows notification and recovery from 5620 NM and related failures. At any point the standby can become active through a manual activity switch or an automatic switch performed by the 5620 NM.

RFC request for comments

The euphemism for standards in the Internet (formerly ARPANET) environment. These documents define IP, TCP, and the related application layer protocols.

rt-VBR real-time variable bit rate

An ATM service category that guarantees very low cell loss and very low delay, rt-VBR is used for time-sensitive applications such as voice and video, which are characterized by unpredictable, bursty transmission patterns.

rt-VBR is a variant of the VBR service category that is only available for VPC and VCC paths. nrt-VBR is the other variant of VBR available for these paths.

SDSL symmetric digital subscriber line

service category The service category determines the priority an ATM connection receives when using connection bandwidth. The possible service categories, from highest to lowest priority, are CBR, VBR, ABR, and UBR.

SES severely errored seconds

An SES is a second (other than a failed second) with either a bit error rate that exceeds 10 -3 or a loss of frame alignment.

session protocol The session protocol is a protocol used by the session layer of the OSI seven-layer reference model.

SF superframe format

SF is a framing format for T1 links that provides a 12 frame multi-frame with 24 kb/s channels per frame. SF is also known as D4.

signaling link This term can be used in two ways:

• an end-to-end logical connection that can be established between two ATM nodes to exchange information related to SPVCs and SVCs that are passing between the nodes; in the 5620 NM, signaling links are a type of VCC path

• a PVC that carries information about the creation and deletion of SVCs between ATM switches in the 5620 NM-managed ATM network

Glossary


SIR sustained information rate

SIR is the long-term average data transfer rate for a frame relay, VPC, or VCC path.

SLP signaling link profile

A signaling link profile is a set of preconfigured attributes that can be sent to all 5620 NM-managed ATM nodes in the network to define the operation of their associated signaling links.

SMA service management application

SNMP simple network management protocol

SPDU session protocol data unit

The SPDU is a PDU that operates at the session layer of the OSI model.

SPVC soft permanent virtual circuit

An SPVC is a signaled, end-to-end network connection established as the result of an operator command. The user defines the endpoint at the source UNI and the system dynamically establishes the network connections and maintains them for the duration of the call.

SRL subrate link

An SRL is a connection between a pair of devices that is intended for use as a carrier for subrate data calls. It is a logical link that has path-like qualities in that it can be connected, disconnected, and protected by AAR and RAPID. The endpoint devices can be any combination of SRMs, SRS inputs, and appropriately-configured primary rate DS0s. SRLs, along with an associated primary rate communication channel, form a set of subrate communication channels.

Subrate paths travel along previously-configured SRLs. SRLs are restrictive in their rate adaption type and, as a consequence, are restrictive in their path usage.

SRM subrate multiplexer

SRM is a device that allows data and compressed voice to be multiplexed together and put on a single DS-0.

SRS subrate switch

An SRS is a logical device that is used to switch subrate paths.

SSCS service specific convergence sublayer

SSCS is the portion of the convergence sublayer that is dependent upon the type of traffic that is being converted.

STM-1 synchronous transport module-level 1

STM-1 is an SDH signal that carries data at the rate of 155.52 Mbps.

Glossary


STM-4 synchronous transport module-level 4

STM-4 is an SDH signal that carries data at the rate of 622.08 Mbps.

STS synchronous transport signal

STS is an electrical variant of the SONET OC signal. The basic rate is 51.84 Mb/s; higher rates are direct multiples of the base rate.

SU switching unit

SVC switched virtual circuit

An SVC is a signaled, end-to-end network connection. The user defines the endpoint at the source UNI and the system dynamically establishes the network connections and maintains them for the duration of the call.

T1 transmission signal level 1

T1 is the first level of the digital transmission hierarchy commonly used in North America and Japan. T1 operates at a link speed of 1.544 Mb/s.

T3 transmission signal level 3

T3 is the third level of the digital transmission hierarchy commonly used in North America. T3 operates at a link speed of 44.736 Mb/s.

TARR test action request receiver

TARR is a term used to identify the ability of a managed object to act upon a test request. In addition to those required as a TARR, the managed object may also have other attributes, operations and notifications.

Tc committed rate measurement interval

The Tc is the time interval over which the user may transfer Bc bits of committed data, or Bc + Be bits of uncommitted data. It is calculated as Tc= Bc/CIR.

TCA threshold crossing alarm

TCA profiles are used by the system to combine several statistics counters. When a user-defined threshold for any one of the statistics in the profile has been exceeded, an alarm is generated. Several statistics counters can therefore be monitored using a single profile.

TDM time division multiplexing

TMF TeleManagement Forum

The TMF is a nonprofit global organization that provides leadership, strategic guidance and practical solutions to improve the management and operation of communications services. It was formerly known as the NMF.

TMN Telecommunications Management Network

A TMN is an industry-standard model defined by the ITU-T for the layering of management functionality for telecommunications networks.

Glossary


TO test object

A TO is a managed object that exists only for a controlled test invocation and has attributes, operations, and notifications that pertain to that instance of the test.

Token ring Token ring is a network with a ring topology that uses the token-passing procedure. See IEEE 802.5 and Ring topology.

trouble ticket Trouble tickets are generated by the 5620 NM in order to keep track of node-generated event failures and operator responses to those failures.

UBR unspecified bit rate

UBR is an ATM service category that does not specify traffic-related service guarantees. Specifically, UBR does not include the notion of a per-connection negotiated bandwidth. No numerical commitments are made with respect to the cell loss ratio experienced by a UBR connection, or as to the cell transfer delay experienced by cells on the connection.

UFR unchannelized frame relay

UI user interface

The UI is what the user sees on a computer or terminal screen. It changes in response to inputs from the keyboard and mouse. The UI is sometimes referred to as the man–machine interface (MMI), human–machine interface (HMI) or the graphical user interface (GUI).

UNI user–network interface

UNI is the interface point between ATM end users and a private ATM switch, or between a private ATM switch and the public carrier ATM network. It is defined by physical and protocol specifications per ATM Forum UNI documents. It is the standard adopted by the ATM Forum to define connections between users or end stations and a local switch.

UNIX UNIX is a computer operating system first developed by Bell Labs and now used on mainframes, workstations, and personal computers. UNIX is the basis of Solaris, the operating system used by Sun workstations.

VBR variable bit rate

VBR is an ATM service category that provides guaranteed low cell loss and low delay for applications, such as video and frame relay, that are characterized by an on/off source with known, predictable transmission patterns. During the on period, cells are transmitted at the PIR. No cells are transmitted during the off period.

VCC virtual channel connection.

A VCC is the series of cross-connections used to traverse an ATM network end-to-end. The endpoints of a VCC are the points where the ATM cell payload is passed to or received from the users of the ATM layer.

Glossary


VCI virtual channel identifier

A VCI is a unique numerical tag as defined by a 16-b field in the ATM cell header that identifies a virtual channel, over which the cell is to travel.

VoFR voice-over-frame relay

A VoFR communication channel consolidates voice and fax traffic with frame relay data traffic across frame relay networks.

VPC virtual path connection

A VPC has end-to-end significance. It is a concatenation of VP links that extends between the points where the ATM service users access the ATM layer. A long-term VPC is known as a PVPC.

VPI virtual path identifier

An 8-b field in the ATM cell header that indicates the virtual path over which the cell should be routed.

VSC voice services card

VSVD virtual source virtual destination

VSVD divides ABR connections into two or more distinct ABR loops. Each ABR loop, except the first, is sourced by a virtual source that implements the behavior of an ABR source endpoint. Backwards RM cells received by a virtual source are removed from the connection. Each ABR loop, except the last, is terminated by a virtual destination that assumes the behavior of an ABR destination endpoint. Forward RM cells are turned around and not forwarded to the next segment of the connection. VSVD provides earlier feedback.

WTR wait to restore

WTR is the timer that is used in revertive ring or 1+1 protected interfaces that must elapse before connections revert to the working card, following failure and recovery of the working card.

X.21 X.21 is the ITU-T standard for high speed synchronous data interface with balanced transmission of all signals.

X.25 X.25 is the ITU-T standard that defines the standard protocol for communication between packet switched public data networks and user devices in the packet switched mode.

X.50 X.50 is the ITU-T standard comparable to DDS. It uses 20 subframes, each with a 2.4 kbps data rate; transmission rates faster than this occupy consecutive subframes.


Index

Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1 IN-1October 2006 95-6040-01-00-C

Index

Numbers

5620 CMIPconfiguring processes on the

NetworkStation, 8-3functional description, 2-2MIB audit, 10-5MIB delete, 10-7MIB reloading, 10-7MIB sync, 10-5MIB syncstatus, 10-5new features, 1-4, 1-2process options on the NetworkStation, 8-4reconfiguring processes, 8-4stopping, 5-5supported operations, 8-2

5620 NM5620 CMIP operations, 8-2

7321 RU profile parameters, 37-227390 DBS and NT support, 1-157670 RSP ESE

shelf module equipment, 27-3

A

actionListFreeVCIs, 34-2ListUsedVCIs, 34-2

administrativeState attribute, 24-5

Agent; See OSS Interface Agentalarm

forwarding, 17-2log record objects, 17-11logging, 17-2notifications, 17-8outage time, 13-13sources, 17-9

alarmInfo attributes, 17-6alarmRecord object

attributes, 21-2description, 21-1

Application Keyrequirements, 2-8

ASAM profile parameters, 37-17ASN.1

managed objects, 20-4association request, 7-4ATM

representation in the MIB, 20-14ATM link

configuring, 14-4deleting, 14-4

ATM VCC pathssetting PIR, 24-41

aTMProfile attribute, 24-27attributeValueChange, 17-9attributeValueChangeInfo attributes, 17-6

Index

IN-2 Alcatel 5620 CMIP OSS Interface Module Technical Reference, Release 7.1October 2006 95-6040-01-00-C

attributeValueChangeRecord objectattributes, 22-2description, 22-1

B

bMFacility objectattributes, 23-2description, 12-2, 23-1event notifications, 23-2logical links, 14-2physical links, 14-2

bMGroomedCircuit objectaTMProfile attribute, 24-27attributes, 24-2circuitType attribute, 24-49commonProfile attribute, 24-43configuring, 13-11creating, 13-4description, 12-3, 24-1event notifications, 24-2frameRelayProfile attribute, 24-21path status, 24-5profile attributes, 24-9statistics activation, 18-2tDMProfile attribute, 24-10

busyOutTestObjectadministering a test, 16-6attributes, 25-2description, 16-2, 25-1event notifications, 25-2

C

CE MIB tool, 10-1, 10-2CE_agent process

configuring, 8-3description, 2-4

CE_chgsrv processconfiguring, 8-3description, 2-4

CE_control processdescription, 5-3status of 5620 CMIP, 5-4

CE_driver processconfiguring, 6-2displaying and logging messages, 6-2entry fields, 6-2functions, 6-2MIB reload options, 6-3

CE_reload processconfiguring, 8-3description, 2-5

circuitProfile, 24-9circuitProfileName, 24-9circuitType attribute, 24-49commands

security module, 11-5commonProfile attribute, 24-43communication

configuring, 7-3link environment variables, 7-4status on the 5620 NM, 8-2with the OSS, 7-4

configuring5620 CMIP node, 8-25620 NM identification, 7-3local address, 7-3partition name, 7-3second-level network name, 7-3

conformanceapplications layer, 2-6architecture layer, 2-5link layer, 2-7network layer, 2-7presentation layer, 2-6profiles, 2-5session layer, 2-6standards, 2-5transport layer, 2-7

containment5620 CMIP in the MIB, 20-7network in the MIB, 20-6

CPSS, 7-2creating

ATM link bMFacility objects, 14-4IMA link bMFacility objects, 14-5MFR link bMFacility objects, 14-3PSN link bMFacility objects, 14-6

attributeValueChangeRecord object — creating

Index


cTPld attribute, 34-27

D

diagnosticsmonitor testing, 16-15, 16-18split-back testing, 16-15, 16-18split-loop testing, 16-18split-through testing, 16-15

discriminatorConstruct attribute, 17-3

E

elementExtensions objectattributes, 26-2description, 12-4, 26-1

ELS optionsconfiguring, 4-2

equipmentHolder objectattributes, 27-2description, 12-4, 27-1event notifications, 26-2, 27-2

eventforwarding, 17-2log record objects, 17-11log record types, 17-11logging, 17-2sources, 17-9

event managementgeneral description, 2-2overview, 17-2

event notificationsalarms, 17-3events, 17-3types, 17-4

event typesM-EVENT_REPORT, 17-7

eventForwardingDiscriminator objectattributes, 28-2description, 28-1event notifications, 28-2overview, 17-3

eventReportArgument, 17-3

F

facilityTPProfile attribute, 34-4features

existing, 1-8, 1-8new, 1-4, 1-2

frame relayrepresentation in the MIB, 20-13

frame relay linksconfiguring, 14-3deleting, 14-3

frameRelayProfile attribute, 24-21

G

Gateway Stationoperations, 2-3requirements, 2-7restricting access, 11-5

GDMOmanaged objects, 20-4

genericActionObjectattributes, 29-5description, 29-1

groomedCircuitTPProfile attribute, 35-5

H

hitlessConnectionMove actionoptions, 29-18

I

iconcolors, 8-2configuring, 8-2description, 8-2

IMA link, 14-5configuring, 14-5deleting, 14-4, 14-5

installed card type, 27-3, 36-10

L

linkATM, 14-4creating frame relay links, 14-2

cTPld attribute — link

Index


frame relay, 14-2ILMI, 14-7IMA, 14-5MFR, 14-3PNNI, 14-6signaling, 14-7

link managementoverview, 14-2

listLinks actionoptions, 29-6

listPaths actionoptions, 29-12

log objectattributes, 30-3description, 30-1event notifications, 30-3overview, 17-2

logical linksbMFacility object, 14-2modeling, 14-2

loopBackTestObjectadministering a test, 16-7attributes, 31-2description, 16-3, 31-1event notifications, 31-2

M

M-EVENT_REPORTalarm types, 17-8event types, 17-7

managed objectASN.1, 20-4containment, 20-6GDMO, 20-4general description, 20-2

managedElement objectattributes, 32-2description, 12-4, 32-1event notifications, 32-2

managedEquipment objectattributes, 33-2description, 12-4, 33-1event notifications, 33-2value description, 33-3

managedFacilityTP objectattributes, 34-2cTPld attribute, 34-27description, 12-3, 34-1event notifications, 34-2facilityTPProfile attribute, 34-4statistics activation, 18-2supported actions, 34-2supported methods, 34-2trmPhysicalInterface attribute, 34-19

managedGroomedCircuitTP objectattributes, 35-3description, 12-3, 35-1event notifications, 35-3groomedCircuitTPProfile attribute, 35-5trmDataMode attribute, 35-9trmFunctionalInterface attribute, 35-11trmVoiceMode attribute, 35-18tTPId attribute, 35-21

managedPack objectattributes, 36-2description, 12-4, 36-1event notifications, 36-2packProfile attributes, 36-4

managedProfile objectattributes, 37-2description, 12-4, 37-1event notifications, 37-2managedProfileID attribute, 37-3managedProfileProf attribute, 37-8Profile Identifier Format, 37-6

managedProfileID attribute, 37-3calculating for a network-level profile,

37-4calculating for a node-specific profile, 37-7for network-level profile, 37-4for node-specific profile, 37-6

MFR link, 14-3configuring, 14-4

MIB5620 CMIP representation, 20-7ATM network representation, 20-14audit, 10-5backing up, 9-2CE MIB tool, 10-1

link (continued) — MIB

Index


delete, 10-7deleting, 9-2frame relay network representation, 20-13functional description, 2-2managing, 9-2network branch, 20-7network object representation, 20-6reloading, 9-2, 10-7restoring, 9-4structure, 20-6sync, 10-5syncstatus, 10-5system branch, 20-7system object representation, 20-6TDM network representation, 20-10

MIB synchronization with the database, 9-2

modelingphysical links, 14-2

monitor testing, 16-15, 16-18multiple partition

configuration, 3-5

N

netconfig.CEprocess file, 6-2network

containment in the MIB, 20-6representation in the MIB, 20-6

network element communication, 7-2network object

attributes, 38-2description, 12-4, 38-1

NetworkStationrequirements, 2-8

O

oAMCellTestObjectadministering a test, 16-8attributes, 39-2description, 16-3, 39-1event notifications, 39-2

objectalarmRecord, 21-1attributeValueChangeRecord, 22-1

bMFacility, 12-2, 23-1bMGroomedCircuit, 12-3, 24-1busyOutTestObject, 16-2, 25-1class sources, 20-4elementExtensions, 26-1equipmentHolder, 12-4, 12-4, 27-1eventForwardingDiscriminator, 17-3, 28-1genericActionObject, 29-1log, 17-2, 30-1loopBackTestObject, 16-3, 31-1managed objects, 20-2managedElement, 12-4, 32-1managedEquipment, 12-4, 33-1managedFacilityTP, 12-3, 34-1managedGroomedCircuitTP, 12-3, 35-1managedPack, 12-4, 36-1managedProfile, 12-4, 37-1modeling, 12-2modeling examples, 12-5network, 12-4, 38-1oAMCellTestObject, 16-3, 39-1objectCreationRecord, 40-1objectDeletionRecord, 41-1objectGroup, 42-1, 42-2routerTemplate, 43-1splitMonitorTestObject, 16-3, 44-1stateChangeRecord, 45-1system, 46-1testAccessConnectionObject, 16-3, 47-1testActionPerformer, 48-1traceTestObject, 16-4, 49-1

objectCreationRecord objectattributes, 40-2description, 40-1

objectDeletionRecord objectattributes, 41-2description, 41-1

objectGroup, 42-2attributes, 42-2description, 42-1

objectInfo attributes, 17-7OC3 MS and STM1 MS cards

port and resource numbering, 36-13operationalState attribute, 24-5, 48-3

MIB (continued) — operationalState attribute

Index


operations5620 CMIP, 2-25620 NM, 8-2

OSSaccess privilege, 11-5increasing the number of allowed, 3-4multiple access configuration, 3-3screening requests, 11-5

OSS Interface Agentoverview, 2-4

P

packProfile attributes, 36-4path

automatic path-end assignment, 13-6connecting, 13-9connection fault, 13-13connection request, 13-9creating, 13-4creating resource links, 13-8deleting, 13-11disconnecting, 13-11failed connect, 13-10grooming, 13-12hitless connection moves, 13-12maintenance, 13-12management, 13-2outage time, 13-13recovery, 13-13rerouting, 13-13SPVC-interworking, 13-7states, 13-2successful connect, 13-10tracing, 13-12unique naming, 13-6

path-end assignmentautomatic, 13-6

permissions, 11-2physical links

modeling, 14-2PIR

setting on ATM VCC paths with CE endpoint, 24-41

platform requirements, 2-7

port alarm suppression, 17-11proceduralStatus attribute, 48-3processes

Gateway Station, 5-2on the NetworkStation, 8-3

programmed card type, 27-3, 36-10PSN link

deleting, 14-6

R

redundancy configuration5620 CMIP, 3-75620 NM NetworkStation, 3-9

requirementsApplication Key, 2-8Gateway Station, 2-7NetworkStation, 2-8

resource linkscreating, 14-8

restricted mode, 11-5routerTemplate object


S

security fileadding entries, 11-4decription, 11-2maintaining, 11-2permissions, 11-2

security module commands, 11-5serverTrailList attribute, 23-5split-back testing, 16-15, 16-18split-loop testing, 16-18split-through testing, 16-15splitMonitorTestObject

administering a test, 16-13attributes, 44-2description, 16-3, 44-1event notifications, 44-2

SPVC-interworking, 13-7standards

conformance, 2-5

operations — standards

Index


start-up5620 CMIP, 5-4automatic, 5-2prestartup information, 5-2

stateChange attribute, 17-9stateChangeInfo attributes, 17-7stateChangeRecord object


statisticsactivation, 18-3data files, 18-2interpreting data files, 18-3overview, 18-1Statistics Collector overview, 18-2

status5620 CMIP, 5-4communication with the 5620 NM, 8-2

stopping5620 CMIP, 5-5

synchronizationMIB and database, 9-2

system configuration5620 CMIP redundancy, 3-75620 NM NetworkStation redundancy, 3-9basic, 3-2multiple OSS access, 3-3multiple partitions, 3-5small systems, 3-2

system object, 20-7attributes, 46-2description, 46-1

T

TDMrepresentation in the MIB, 20-10

tDMProfile attribute, 24-10test object

actions, 16-5types, 16-2

testAccessConnectionObjectadministering a test, 16-16attributes, 47-2

description, 16-3, 47-1event notifications, 47-2

testActionPerformer objectactions, 16-4attributes, 48-2creating and deleting test objects, 16-4description, 48-1

testingbMGroomedCircuit objects, 16-22monitor, 16-15, 16-18split-back, 16-15, 16-18split-loop, 16-18split-through, 16-15

time stamping, 17-3traceTestObject

attributes, 49-2description, 16-4, 49-1event notifications, 29-5, 49-2

trmCircuitProfile attribute, 23-6trmDataMode attribute, 35-9trmFunctionalInterface attribute, 35-11trmPhysicalInterface attribute, 34-19trmVoiceMode attribute, 35-18tTPId attribute, 35-21

V

value descriptionmanagedEquipment object, 33-3

W

warm stop, 5-5

start-up — warm stop

Index


Customer documentation and product support

Technical support

Customer documentation

Product manuals and documentation updates are available through the Alcatel SupportDocumentation and Software Download service at Alcatel.com. If you are a new user andrequire access to this service, please contact your Alcatel sales representative.

Customer documentation feedback

http://www.alcatel.com/support/

http://www.alcatel.com/osds/

[email protected]

alcate 5620 cmip oss interface module release 7.1 technical reference

Documents

alcatel pursuant

alcatel grants

alcatel logo

alcatel harmless

failure of products

disclaimersalcatel products

internal use

incomplete information