Oracle Communications EAGLE · Oracle® Communications EAGLE Measurements Reference Release 46.3 E72179 Revision 1 June 2016

Oracle® CommunicationsEAGLEMeasurements Reference

Release 46.3

E72179 Revision 1

June 2016

Oracle Communications EAGLE Measurements Reference, Release 46.3Copyright © 1993, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation andagency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptationof the programs, including any operating system, integrated software, any programs installed on thehardware, and/or documentation, shall be subject to license terms and license restrictions applicable to theprograms. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applicationsthat may create a risk of personal injury. If you use this software or hardware in dangerous applications,then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures toensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused byuse of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarksof their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Table of Contents

Chapter 1: Introduction...............................................................................17Overview...............................................................................................................................................18Scope and Audience............................................................................................................................18Documentation Admonishments.......................................................................................................18Manual Organization...........................................................................................................................19My Oracle Support (MOS)..................................................................................................................19Emergency Response...........................................................................................................................20Related Publications............................................................................................................................20Customer Training...............................................................................................................................20Locate Product Documentation on the Oracle Help Center Site...................................................21

Chapter 2: Measurements...........................................................................22Introduction to Measurements...........................................................................................................23Obsolete OAM Measurements and FTA..........................................................................................24Measurements Platform......................................................................................................................25E5-OAM Integrated Measurements..................................................................................................26Data Mirroring......................................................................................................................................28Optional 15-Minute Measurements...................................................................................................28Reports...................................................................................................................................................30

Measurements Platform/E5-OAM Integrated Measurements Feature Reports............33Report Limitations...................................................................................................................36

Chapter 3: Reports........................................................................................38Report Tables........................................................................................................................................39STP System Totals Measurements (SYSTOT)...................................................................................39

STP SYSTOT Report.................................................................................................................39TT SYSTOT Report...................................................................................................................51CGTT SYSTOT Report.............................................................................................................54STPLAN SYSTOT Report........................................................................................................59IDPR SYSTOT Report..............................................................................................................62SIP SYSTOT Report..................................................................................................................69SFTHROT SYSTOT Report.....................................................................................................70

Component Measurements (COMP).................................................................................................71

iiiE72179 Revision 1, June 2016

LINK COMP Report................................................................................................................71LNKSET COMP Report...........................................................................................................84SCTPASOC COMP Report.....................................................................................................92SCTPCARD COMP Report.....................................................................................................97UA COMP Report..................................................................................................................101

Network Management Measurements (NM).................................................................................105STP NM Report.......................................................................................................................105LNKSET NM Report..............................................................................................................111LINK NM Report....................................................................................................................115

Daily Availability Measurements (AVLD).....................................................................................123LINK AVLD Report...............................................................................................................123

Day-To-Hour Availability Measurements (AVLDTH).................................................................131LINK AVLDTH Report.........................................................................................................132

Availability Measurements (AVL)...................................................................................................139LINK AVL Report..................................................................................................................139STPLAN AVL Report............................................................................................................148

Daily Maintenance Measurements (MTCD)..................................................................................152STP MTCD Report..................................................................................................................153LINK MTCD Report..............................................................................................................161LNKSET MTCD Report.........................................................................................................173LNP MTCD Report................................................................................................................175NP MTCD Report...................................................................................................................181STPLAN MTCD Report.........................................................................................................191EIR MTCD Report..................................................................................................................194MAPSCRN MTCD Report....................................................................................................196SCTPASOC MTCD Report...................................................................................................202SCTPCARD MTCD Report...................................................................................................207UA MTCD Report..................................................................................................................212VFLEX MTCD Report............................................................................................................215ATINPQ MTCD Report.........................................................................................................217AIQ MTCD Report.................................................................................................................220GTTAPATH MTCD Report..................................................................................................222SIP MTCD Report...................................................................................................................227DEIR MTCD Report...............................................................................................................229ENUM MTCD Report............................................................................................................231SFTHROT MTCD Report......................................................................................................237

Day-to-Hour Maintenance Measurements (MTCDTH)...............................................................238STP MTCDTH Report............................................................................................................238LINK MTCDTH Report.........................................................................................................246LNKSET MTCDTH Report...................................................................................................263STPLAN MTCDTH Report...................................................................................................266

ivE72179 Revision 1, June 2016

SCTPASOC MTCDTH Report..............................................................................................269SCTPCARD MTCDTH Report.............................................................................................275UA MTCDTH Report............................................................................................................279

Hourly Maintenance Measurements (MTCH)...............................................................................283LNP MTCH Report................................................................................................................283NP MTCH Report...................................................................................................................290EIR MTCH Report..................................................................................................................299MAPSCRN MTCH Report....................................................................................................301VFLEX MTCH Report............................................................................................................306ATINPQ MTCH Report........................................................................................................309AIQ MTCH Report.................................................................................................................311GTTPATH MTCH Report.....................................................................................................313DEIR MTCH Report...............................................................................................................319ENUM MTCH Report............................................................................................................321

Gateway Measurements (GTWY)....................................................................................................327STP GTWY Report..................................................................................................................327ORIGNI GTWY Report..........................................................................................................330ORIGNINC GTWY Report...................................................................................................331LNKSET GTWY Report.........................................................................................................333LSDESTNI GTWY Report.....................................................................................................336LSORIGNI GTWY Report.....................................................................................................338LSONISMT GTWY Report....................................................................................................341

Record Base Measurements (RBASE)..............................................................................................343STP RBASE Report.................................................................................................................343LINK RBASE Report..............................................................................................................348LNKSET RBASE Report........................................................................................................354

Maintenance Status Reports (MTCS)..............................................................................................357LINK MTCS Report...............................................................................................................357LNKSET MTCS Report..........................................................................................................363

Glossary.............................................................................................................................366

vE72179 Revision 1, June 2016

List of Tables

Table 1: Admonishments................................................................................................................................18

Table 2: Demand and Scheduled Reporting.................................................................................................24

Table 3: Enabling 15-Minute Measurements - Impacts..............................................................................29

Table 4: Measurements Platform and E5-OAM Integrated Measurements Feature SystemHeader..........................................................................................................................................................33

Table 5: STP System Total STP Measurements............................................................................................40

Table 6: Typical File Size: systot-stp.csv.......................................................................................................51

Table 7: STP System Total Translation Type Measurements.....................................................................51

Table 8: Typical File Size: systot-tt.csv..........................................................................................................54

Table 9: Calling Party GTT Measurements...................................................................................................55

Table 10: Typical File Size: systot-cgtt.csv....................................................................................................59

Table 11: STP System Total STPLAN Measurements.................................................................................59

Table 12: Typical File Size: systot-stplan.csv................................................................................................62

Table 13: Availability of SYSTOT IDPR Report...........................................................................................63

Table 14: SYSTOT IDPR Measurements.......................................................................................................63

Table 15: Typical File Size: systot-idpr.csv...................................................................................................69

Table 16: STP System Total SIP Measurements...........................................................................................69

Table 17: Typical File Size: systot-sip.csv.....................................................................................................70

Table 18: STP System Total SFTHROT Measurements...............................................................................70

Table 19: Typical File Size: systot-sfthrot.csv...............................................................................................71

Table 20: Registers Reported per LINK CLASS for Component Links....................................................72

Table 21: Component Link Measurements...................................................................................................73

viE72179 Revision 1, June 2016

Table 22: COMP LINK Column Headers.....................................................................................................83

Table 23: Typical File Size: comp-link.csv....................................................................................................84

Table 24: Registers Reported Per LINKSET CLASS....................................................................................84

Table 25: Component Linkset Measurements..............................................................................................85

Table 26: COMP LINKSET Column Headers..............................................................................................91

Table 27: Typical File Size: comp-lnkset.csv.................................................................................................91

Table 28: Component SCTPASOC Measurements......................................................................................92

Table 29: COMP SCTPASOC Column Headers..........................................................................................96

Table 30: Typical File Size: comp-sctpasoc.csv............................................................................................96

Table 31: Component SCTPCARD Measurements.....................................................................................97

Table 32: COMP SCTPCARD Column Header..........................................................................................100

Table 33: Typical File Size: comp-sctpcard.csv..........................................................................................101

Table 34: Component UA Measurements...................................................................................................101

Table 35: COMP UA Column Headers.......................................................................................................104

Table 36: Typical File Size: comp-ua.csv.....................................................................................................105

Table 37: Network Management STP Measurements...............................................................................105

Table 38: Typical File Size: nm-stp.csv........................................................................................................111

Table 39: Network Management Linkset Measurements.........................................................................112

Table 40: FTP NM LNKSET Column Headers...........................................................................................114

Table 41: Typical File Size: nm-lnkset.csv...................................................................................................115

Table 42: HSL LSL Differences for Network Management Links...........................................................115

Table 43: Network Management Link Measurements..............................................................................116

Table 44: FTP NM LINK Column Headers................................................................................................122

Table 45: Typical File Size: nm-link.csv......................................................................................................123

Table 46: Availability Link Measurements.................................................................................................124

viiE72179 Revision 1, June 2016

Table 47: FTP AVLD LINK Command Headers........................................................................................130

Table 48: Typical File Size: avld-link.csv....................................................................................................131


Table 50: FTP AVLDTH LINK Command Headers..................................................................................138

Table 51: Typical File Size: avldth-link.csv.................................................................................................139

Table 52: Availability Link Register Usage By LINK Class.....................................................................139


Table 54: FTP AVL LINK Column Headers...............................................................................................147

Table 55: Typical File Size: avl-link.csv.......................................................................................................148

Table 56: Availability STPLAN Measurements.........................................................................................149

Table 57: Typical File Size: avl-stplan.csv...................................................................................................152

Table 58: Daily Maintenance (MTCD) and Day-To-Hour Maintenance (MTCDTH)Measurements...........................................................................................................................................153

Table 59: Typical File Size: mtcd-stp.csv.....................................................................................................160

Table 60: Registers Reported per LINK CLASS for Daily (MTCD) and Day-To-Hour (MTCDTH)Link Measurements..................................................................................................................................161

Table 61: Maintenance Daily (MTCD) and Maintenance Day-to-Hour (MTCDTH) LinkMeasurements...........................................................................................................................................163

Table 62: Typical File Size: mtcd-link.csv...................................................................................................173

Table 63: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) LinksetMeasurements...........................................................................................................................................173

Table 64: Typical File Size: mtcd-lnkset.csv...............................................................................................174

Table 65: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP System WideMeasurements...........................................................................................................................................175

Table 66: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP Per SSPMeasurements...........................................................................................................................................176

Table 67: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP LRNMeasurements...........................................................................................................................................178

viiiE72179 Revision 1, June 2016

Table 68: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP NPAMeasurements...........................................................................................................................................178

Table 69: Typical File Size: mtcd-lnp.csv....................................................................................................179

Table 70: Typical File Size: mtcd-ssp.csv....................................................................................................180

Table 71: Typical File Size: mtcd-lrn.csv.....................................................................................................180

Table 72: Typical File Size: mtcd-npa.csv...................................................................................................181

Table 73: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) System-WideRegisters.....................................................................................................................................................182

Table 74: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) SSP Registers..................186

Table 75: Typical File Size: mtcd-np.csv.....................................................................................................189

Table 76: FTP Daily Maintenance (MTCD) SSP Column Header...........................................................190



Table 79: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) STPLANMeasurements...........................................................................................................................................191

Table 80: Typical File Size: mtcd-stplan.csv...............................................................................................194

Table 81: Daily Maintenance (MCTD) and Hourly Maintenance (MTCH) EIR Measurements.........194

Table 82: Typical File Size: mtcd-eir.csv.....................................................................................................196

Table 83: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening SystemWide Measurements................................................................................................................................196

Table 84: Server Entity Identification..........................................................................................................198

Table 85: Path Entity Identification.............................................................................................................198

Table 86: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening PerServer Measurements...............................................................................................................................200

Table 87: Typical File Size: mtcd-map.csv..................................................................................................201

Table 88: Typical File Size: mtcd-path.csv..................................................................................................201

ixE72179 Revision 1, June 2016

Table 89: Daily Maintenance (MTCD) and Day-to-Hour (MTCDTH) SCTPASOCMeasurements...........................................................................................................................................202

Table 90: FTP MTCD/MTCDTH SCTPASOC Column Header..............................................................206

Table 91: Typical File Size: mtcd-sctpasoc.csv...........................................................................................207

Table 92: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARDMeasurements...........................................................................................................................................207

Table 93: Typical File Size: mtcd-sctpcard.csv...........................................................................................212

Table 94: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) UAMeasurements...........................................................................................................................................212

Table 95: Typical File Size: mtcd-ua.csv......................................................................................................215

Table 96: Daily Maintenance V-Flex System Wide Measurements.........................................................215

Table 97: Daily Maintenance V-Flex Per SSP Measurements..................................................................216

Table 98: Typical File Size: mtcd-vflex.csv.................................................................................................217

Table 99: Typical File Size: mtcd-vflex-ssp.csv..........................................................................................217

Table 100: Typical File Size: mtcd-vflexssp.csv.........................................................................................217

Table 101: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ATINPQ Registers.......218

Table 102: Typical File Size: mtcd-atinpq.csv.............................................................................................219


Table 104: Typical File Size: atinpq 200 SSPs.............................................................................................219

Table 105: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) AIQ Registers...............220


Table 107: Typical File Size: mtcd-aiq.csv...................................................................................................222

Table 108: Typical File Size: aiq 200 SSPs...................................................................................................222

Table 109: MTCD/MTCH GTT Actions System-Wide Measurements..................................................223

Table 110: MTCD/MTCH GTT Actions Per-Path Measurements..........................................................224

Table 111: Typical File Size: mtcd-gttasys.csv............................................................................................225

xE72179 Revision 1, June 2016

Table 112: Entity Identification(PATH-CDSN-SCDGTA-CGSN-SCGGTA-OPSN-PKG-OPCODE-<A>/F)....................................226

Table 113: Typical File Size: mtcd-gttapath.csv.........................................................................................227


Table 115: Typical File Size: mtcd-sip.csv...................................................................................................229

Table 116: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) DEIRMeasurements...........................................................................................................................................229

Table 117: Typical File Size: mtcd-deirsys.csv...........................................................................................231

Table 118: Typical File Size: mtcd-deirconn.csv........................................................................................231

Table 119: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System LevelMeasurements...........................................................................................................................................232

Table 120: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card LevelMeasurements...........................................................................................................................................233

Table 121: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity LevelMeasurements...........................................................................................................................................234

Table 122: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL LevelMeasurements...........................................................................................................................................234

Table 123: Typical File Size: mtcd-enumsys.csv........................................................................................236

Table 124: Typical File Size: mtcd-enumcard.csv......................................................................................236

Table 125: Typical File Size: mtcd-enument.csv........................................................................................236

Table 126: Typical File Size: mtcd-enumacl.csv.........................................................................................237


Table 128: Typical File Size: mtcd-sfthrot.csv............................................................................................238


Table 130: Typical File Size: mtcdth-stp.csv...............................................................................................246

xiE72179 Revision 1, June 2016

Table 131: Registers Reported per LINK CLASS for Daily (MTCD) and Day-To-Hour (MTCDTH)Link Measurements..................................................................................................................................246

Table 132: Maintenance Daily (MTCD) and Maintenance Day-to-Hour (MTCDTH) LinkMeasurements...........................................................................................................................................249

Table 133: FTP MTCDTH LINK Command Headers...............................................................................262

Table 134: Typical File Size: mtcdth-link.csv.............................................................................................263

Table 135: Maintenance Day-to-Hour Linkset Measurements................................................................263

Table 136: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) LinksetMeasurements...........................................................................................................................................264

Table 137: Typical File Size: mtcdth-lnkset.csv..........................................................................................265

Table 138: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) STPLANMeasurements...........................................................................................................................................266

Table 139: Typical File Size: mtcdth-stplan.csv.........................................................................................269

Table 140: Daily Maintenance (MTCD) and Day-to-Hour (MTCDTH) SCTPASOCMeasurements...........................................................................................................................................270

Table 141: Typical File Size: mtcdth-sctpasoc.csv......................................................................................274

Table 142: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARDMeasurements...........................................................................................................................................275

Table 143: Typical File Size: mtcdth-sctpasoc.csv......................................................................................279

Table 144: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) UAMeasurements...........................................................................................................................................280

Table 145: Typical File Size: mtcdth-ua.csv................................................................................................283

Table 146: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP System WideMeasurements...........................................................................................................................................283

Table 147: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP Per SSPMeasurements...........................................................................................................................................285

Table 148: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP LRNMeasurements...........................................................................................................................................287

xiiE72179 Revision 1, June 2016

Table 149: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP NPAMeasurements...........................................................................................................................................287

Table 150: Typical File Size: mtch-lnp.csv..................................................................................................288

Table 151: Typical File Size: mtch-ssp.csv..................................................................................................288

Table 152: Typical File Size: mtch-lrn.csv...................................................................................................289

Table 153: Typical File Size: mtch-npa.csv.................................................................................................289

Table 154: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) System-WideRegisters.....................................................................................................................................................290

Table 155: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) SSP Registers................294

Table 156: Typical File Size: mtch-np.csv...................................................................................................298



Table 159: Daily Maintenance (MCTD) and Hourly Maintenance (MTCH) EIR Measurements.......299

Table 160: Typical File Size: mtch-eir.csv...................................................................................................300

Table 161: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening SystemWide Measurements................................................................................................................................301

Table 162: Server Entity Identification........................................................................................................302

Table 163: Path Entity Identification...........................................................................................................303

Table 164: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening PerServer Measurements...............................................................................................................................304

Table 165: Typical File Size: mtch-map.csv................................................................................................305

Table 166: Typical File Size: mtch-path.csv................................................................................................306

Table 167: Daily Maintenance V-Flex System Wide Measurements.......................................................307

Table 168: Daily Maintenance V-Flex Per SSP Measurements................................................................307

Table 169: Typical File Size: mtch-vflex.csv...............................................................................................308

Table 170: Typical File Size: mtch-vflexssp.csv..........................................................................................308

xiiiE72179 Revision 1, June 2016

Table 171: Typical File Size: mtch-vflexssp.csv..........................................................................................308

Table 172: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ATINPQ Registers.......309

Table 173: Typical File Size: mtch-atinpq.csv.............................................................................................310

Table 174: Typical File Size: mtch-atinpq.csv.............................................................................................311

Table 175: Typical File Size: atinpq 200 SSPs.............................................................................................311

Table 176: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) AIQ Registers...............312


Table 178: Typical File Size: mtcd-aiq.csv...................................................................................................313

Table 179: Typical File Size: aiq 200 SSPs...................................................................................................313

Table 180: MTCD/MTCH GTT Actions System-Wide Measurements..................................................314

Table 181: MTCD/MTCH GTT Actions Per-Path Measurements..........................................................315

Table 182: Typical File Size: mtch-gttasys.csv............................................................................................317

Table 183: Entity Identification(PATH-CDSN-SCDGTA-CGSN-SCGGTA-OPSN-PKG-OPCODE-<A>/F)....................................317

Table 184: Typical File Size: mtch-gttapath.csv.........................................................................................319

Table 185: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) DEIRMeasurements...........................................................................................................................................319

Table 186: Typical File Size: mtch-deirsys.csv...........................................................................................320

Table 187: Typical File Size: mtch-deirconn.csv........................................................................................321

Table 188: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System LevelMeasurements...........................................................................................................................................322

Table 189: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card LevelMeasurements...........................................................................................................................................323

Table 190: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity LevelMeasurements...........................................................................................................................................324

Table 191: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL LevelMeasurements...........................................................................................................................................324

xivE72179 Revision 1, June 2016

Table 192: Typical File Size: mtch-enumsys.csv........................................................................................325

Table 193: Typical File Size: mtch-enumcard.csv......................................................................................326

Table 194: Typical File Size: mtch-enument.csv........................................................................................326

Table 195: Typical File Size: mtch-enumacl.csv.........................................................................................327

Table 196: Gateway STP Measurements.....................................................................................................327

Table 197: Typical File Size: gtwy-stp.csv...................................................................................................330

Table 198: Gateway ORIGNI Measurements.............................................................................................330

Table 199: Typical File Size: gtwy-origni.csv.............................................................................................331

Table 200: Gateway ORIGNINC Measurements.......................................................................................332

Table 201: Typical File Size: gtwy-origninc.csv.........................................................................................333

Table 202: Gateway Linkset Measurements...............................................................................................334

Table 203: Typical File Size: gtwy-lnkset.csv.............................................................................................336

Table 204: Gateway LSDESTNI Measurements.........................................................................................337

Table 205: Typical File Size: gtwy-lsdestni.csv..........................................................................................338

Table 206: Gateway LSORGINI Measurements.........................................................................................339

Table 207: Typical File Size: gtwy-lsorigni.csv..........................................................................................341

Table 208: Gateway LSONISMT Measurements.......................................................................................342

Table 209: Typical File Size: gtwy-lsonismt.csv.........................................................................................343

Table 210: Record Base STP Measurements...............................................................................................343

Table 211: Typical File Size: rbase-stp.csv..................................................................................................348

Table 212: Registers reported LINK Measurements.................................................................................348

Table 213: Record Base Link Measurements..............................................................................................349

Table 214: Typical File Size: rbase-link.csv.................................................................................................354

Table 215: Record Base Linkset Measurements.........................................................................................355

Table 216: Typical File Size: rbase-lnkset.csv.............................................................................................356

xvE72179 Revision 1, June 2016

Table 217: Maintenance Status Link Measurements.................................................................................357

Table 218: Typical File Size: mtcs-link.csv..................................................................................................363

Table 219: Maintenance Status Linkset Measurements............................................................................364

Table 220: Typical File Size: mtcs-lnkset.csv..............................................................................................365

xviE72179 Revision 1, June 2016

Chapter

1Introduction

This chapter contains an overview of the manual,describes how to obtain help, where to find related

Topics:

• Overview.....18 documentation, and provides other generalinformation.• Scope and Audience.....18

• Documentation Admonishments.....18• Manual Organization.....19• My Oracle Support (MOS).....19• Emergency Response.....20• Related Publications.....20• Customer Training.....20• Locate Product Documentation on the Oracle Help

Center Site.....21

17E72179 Revision 1, June 2016

Overview

Measurements Reference describes EAGLE measurements. Measurements provide support for:

• STP performance management

• SS7 traffic monitoring and engineering

• Specific feature performance analysis (STPLAN)

Note: EAGLE supporting ANSI networks make use of the LNP and SEAS features. EAGLE supportingITU networks do not include these systems.

Scope and Audience

This manual is intended for maintenance personnel who must maintain the EAGLE. The technicianshould be familiar with SS7 protocols. The manual provides preventive and corrective proceduresthat will aid maintenance personnel in maintaining the EAGLE.

Preventive maintenance procedures are routines to be carried out on a scheduled basis to help preventsystem failures. These routines are industry-standard recommendations and may be adopted to fitany company maintenance plan.

The corrective maintenance procedures are those used in response to a system alarm or output message.These procedures are EAGLE-specific and aid in the detection, isolation, and repair of faults.

Documentation Admonishments

Admonishments are icons and text throughout this manual that alert the reader to assure personalsafety, to minimize possible service interruptions, and to warn of the potential for equipment damage.

Table 1: Admonishments

DescriptionIcon

Danger:

(This icon and text indicate the possibility ofpersonal injury.)

Warning:

(This icon and text indicate the possibility ofequipment damage.)


IntroductionMeasurements

DescriptionIcon

Caution:

(This icon and text indicate the possibility ofservice interruption.)

Topple:

(This icon and text indicate the possibility ofpersonal injury and equipment damage.)

Manual Organization

The manual is organized as follows:

• Introduction provides general information about the organization of this manual.

• Measurements describes traffic measurements used in the EAGLE.

• Reports describes the reports that can be requested.

My Oracle Support (MOS)

MOS (https://support.oracle.com) is your initial point of contact for all product support and trainingneeds. A representative at Customer Access Support (CAS) can assist you with MOS registration.

Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support hotlinefor your local country from the list at http://www.oracle.com/us/support/contact/index.html. When calling,make the selections in the sequence shown below on the Support telephone menu:

1. Select 2 for New Service Request2. Select 3 for Hardware, Networking and Solaris Operating System Support3. Select one of the following options:

• For Technical issues such as creating a new Service Request (SR), Select 1• For Non-technical issues such as registration or assistance with MOS, Select 2

You will be connected to a live agent who can assist you with MOS registration and opening a supportticket.

MOS is available 24 hours a day, 7 days a week, 365 days a year.



https://support.oracle.com

http://www.oracle.com/us/support/contact/index.html

Emergency Response

In the event of a critical service situation, emergency response is offered by the Customer AccessSupport (CAS) main number at 1-800-223-1711 (toll-free in the US), or by calling the Oracle Supporthotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html. Theemergency response provides immediate coverage, automatic escalation, and other features to ensurethat the critical situation is resolved as rapidly as possible.

A critical situation is defined as a problem with the installed equipment that severely affects service,traffic, or maintenance capabilities, and requires immediate corrective action. Critical situations affectservice and/or system operation resulting in one or several of these situations:

• A total system failure that results in loss of all transaction processing capability• Significant reduction in system capacity or traffic handling capability• Loss of the system’s ability to perform automatic system reconfiguration• Inability to restart a processor or the system• Corruption of system databases that requires service affecting corrective actions• Loss of access for maintenance or recovery operations• Loss of the system ability to provide any required critical or major trouble notification

Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilitiesmay be defined as critical by prior discussion and agreement with Oracle.

Related Publications

For information about additional publications that are related to this document, refer to the OracleHelp Center site. See Locate Product Documentation on the Oracle Help Center Site for more information.

Customer Training

Oracle University offers training for service providers and enterprises. Visit our web site to view, andregister for, Oracle Communications training:

http://education.oracle.com/communication

To obtain contact phone numbers for countries or regions, visit the Oracle University Education website:

www.oracle.com/education/contacts



http://www.oracle.com/us/support/contact/index.html

http://education.oracle.com/pls/web_prod-plq-dad/ou_product_category.getFamilyPage?p_family_id=41&p_mode=Training&sc=WWOU14047594MPP002C005

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=225

Locate Product Documentation on the Oracle Help Center Site

Oracle Communications customer documentation is available on the web at the Oracle Help Center(OHC) site, http://docs.oracle.com. You do not have to register to access these documents. Viewing thesefiles requires Adobe Acrobat Reader, which can be downloaded at http://www.adobe.com.

1. Access the Oracle Help Center site at http://docs.oracle.com.2. Click Industries.3. Under the Oracle Communications subheading, click the Oracle Communications

documentation link.The Communications Documentation page appears. Most products covered by these documentationsets will appear under the headings “Network Session Delivery and Control Infrastructure” or“Platforms.”

4. Click on your Product and then the Release Number.A list of the entire documentation set for the selected product and release appears.

5. To download a file to your location, right-click the PDF link, select Save target as (or similarcommand based on your browser), and save to a local folder.



http://docs.oracle.com

http://www.adobe.com

http://docs.oracle.com

Chapter

2Measurements

Topics:

• Introduction to Measurements.....23• Obsolete OAM Measurements and FTA.....24• Measurements Platform.....25• E5-OAM Integrated Measurements.....26• Data Mirroring.....28• Optional 15-Minute Measurements.....28• Reports.....30


Introduction to Measurements

This section describes EAGLE measurements. Measurements provide support for:

• STP performance management

• SS7 traffic monitoring and engineering

• Specific feature performance analysis

Measurements provide operations and maintenance personnel with network performance and STPperformance data in accordance with:

• Telcordia GR-82-CORE




Measurements can be collected and reported with the following collection methods:

• Measurements Platform• E5-OAM Integrated Measurements

The primary functions of Measurements are as follows:

• Collection

Measurements are collected in 5-minute, 30-minute, and 60-minute intervals. An option exists forthe default 30-minute measurements to be collected every 15 minutes. Many 30-minutemeasurements intervals are accumulated into daily intervals.

• Storage

Measurements are stored in dedicated RAM tables and/or disks after collection. Most are retainedfor 24 hours. Measurements for some features are retained for 7 days.

• Retrieval

Measurements data is retrieved from the RAM storage area and/or disk. ACTIVE measurementdata is retrieved and reported from the application cards except for SCP SMCs. Registers collectedfrom SCP SMCs are not supported for ACTIVE measurements and will be reported as zero in anACTIVE measurement report. An ACTIVE linkset report requires all links in the linkset to beavailable in order to provide the report.

• Reporting

Measurement reports are available on-demand/scheduled as shown in Table 2: Demand and ScheduledReporting.


MeasurementsMeasurements

Table 2: Demand and Scheduled Reporting

E5-OAM Integrated MeasurementsMeasurements PlatformReporting Interval

ScheduledDemandScheduledDemand

YesYesYesYes5-minute

YesYesYesYes15-minute (optional)

YesYesYesYes30-minute

NoYesNoYesDay-to-hour

YesYesYesYesHourly

YesYesYesYesDaily

Scheduled measurements are directed to the Traffic Unsolicited Output Message group. No otherunsolicited output is sent to this output group.

Note that the collection of measurements is a separate task from reporting. Measurements collectionis activated automatically upon system power-up, or through administrative commands. Collectionis organized by ENTTYPE and reporting period. Collection occurs per link every 5 minutes, andseparately every 30 minutes. Measurements are generated on the application cards and periodicallycollected by the UI and stored for later retrieval, unless the Measurements Platform is enabled, whereasthe information is collected and stored by the dedicated MPCM cards.

Refer to the Commands User's Guide for descriptions of commands used to generate, schedule, andtransfer measurements reports.

Refer to the Database Administration - System Management User's Guide for information and proceduresto provision the Measurements Platform feature and E5-OAM Integrated Measurements feature.

Obsolete OAM Measurements and FTA

Basic OAM measurements are no longer supported from Release 46.3 onward. For measurementcollection to occur, either the Measurements Platform feature or the E5-OAM Integrated Measurementsfeature must be used. To enable the E5-OAM Integrated Measurements feature, use the followingcommands:

ENABLE-CTRL-FEAT:partnum=893037301CHG-CTRL-FEAT:partnum=893037301:status=ON

OAM-based measurements are collected by an E5-OAM MASP and are stored on the E5-TDM card.

For OAM-based measurements and the Measurements Platform feature, the rept-meas commandsends measurements reports for the NP, GSM MAP screening, LNP, G-Port, A-Port, and IS41 GSMMigration (IGM) features to the file transfer area (FTA). Applications measurements (INP, GSM MAPscreening, and LNP) are now supported only by the FTP reporting capability.

The FTA measurements reporting capability is replaced with the FTP reporting capability.



EAGLE continues to support retrieval of the ACTIVE PERIOD for links/linkset for troubleshootingpurposes. All the entity types that supported the ACTIVE PERIOD collection without enabling theMeasurements Platform feature or the E5-OAM Integrated Measurements feature are still supported.

Measurements Platform

For an EAGLE node with more than 700 links, either the Measurements Platform or the E5-OAMIntegrated Measurements feature must be used to collect measurements. The Measurements Platformmust be used to collect measurements for an EAGLE node with more than 2400 links. The MeasurementsPlatform provides a dedicated processor for collecting and reporting measurements data for EAGLEfunctions, EPAP-related features that collect measurements, GSM MAP Screening, and LNP.

Note: If the 15-Minute Measurements feature is turned on, then the Measurements Plaform is requiredfor support of more than 1200 links.

Links that are supported by the Measurements Platform and E5-OAM Integrated Measurementsfeature include IP associations as shown:

• Each low-speed link (LSL) counts as 1 link• Each ATM high speed link (HSL) counts as 1 link• Each SE-HSL counts as 1 link• For IPLIM, each association counts as 1 link• For IPGW, 1 link per card• For IPSG, each association counts as 1 link

The Measurements Platform feature requires the following hardware and provisioning in the system:

• Two MCPM cards

The platform consists of multiple Measurement Collection and Polling Module (MCPM) cards ina primary/secondary configuration, in which the primary MCPM performs all collection andreporting functions. The secondary MCPM card serves as backup for the primary. The EAGLEinterface is via the standard IMT bus and allows communications with the network elements andthe OAM. The interface to the customer's network supports the FTP transfer of Measurementsreports to an FTP server.

The Primary MCPM maintains constant communication with the Secondary card as a way of eachmonitoring the health status of the other. If the primary MCPM fails before or during collection,the secondary MCPM card assumes the Primary role and begins/continues collection.

• The Measurements Platform feature turned on• The Measurements Platform enable option turned on in the MEASOPTS table• A provisioned customer FTP server• The EAGLE OA&M IP Security feature, and Secure Shell FTP (SFTP) as a client, if secure transfer

is used

Enabling the Measurements Platform feature (feature bit is turned on), allows the MeasurementsPlatform to be provisioned and tested without transferring measurement functionality from the OAMto the Measurements Platform. After the Platform hardware, software, and Ethernet connections havebeen provisioned and verified, the transfer of measurements functionality from the OAM to theMeasurement Platform is initiated by setting the Measurements Platform Enabled bit, which is set by thesystem only one time. From the point that theMeasurements Platform Enabled bit is set and initial data



transfer has occurred, the measurements functionality of the OAM is limited to operator interface formeasurement configuration and on-demand report requests. The Measurements Platform assumesthe collection duties and stores the collected data in MCPM RAM.

After collection of the measurements, scheduled reports are automatically generated and transferredfrom an MCPM card to a customer FTP server using the FTP interface.

Existing FTP file server reports are overwritten by subsequent requests that produce the identical filename.

Reports can be scheduled or generated on demand. Scheduled and on-demand reports are accessibleby the following commands:

• chg-measopts: Used to:

• Enable Measurements Platform collection

• Turn on or turn off the 15 Minute Measurements collection function

• Enable or disable the automatic generation and FTP transfer of scheduled measurements reportsto the FTP server

• Turn on or off the CLLI-based file name option for measurements reports files.

• Turn on or off the unchannelized link label option

• chg-mtc-measopts: Used to enable or disable the automatic generation and FTP transfer ofscheduled measurement reports to the FTP server.

• rept-stat-meas: Reports the status of the Measurements subsystem including card location andstate, Alarm level, and Subsystem State.

• rept-ftp-meas: Manually initiates generation and FTP transfer of a measurements report fromthe MCPM card to the FTP server.

• rtrv-measopts: Displays the status of Measurements Platform collection, scheduled reports,15-Minute Measurements collection, CLLI-based file names, and the unchannelized link label.

• rtrv-mtc-measopts: Displays the enabled or disabled status of hourly and daily maintenancescheduled reports.

Note: If a new entity is provisioned in place of a deleted entity, then the measurements for the deletedentity are set to zero. The reported peg counts apply only to the new entity.

E5-OAM Integrated Measurements

The E5-OAM Integrated Measurements feature provides full measurements support for an EAGLEnode with up to 2400 links without requiring dedicated cards. The Measurements Platform is requiredfor support of more than 2400 links.

Note: If the 15-Minute Measurements feature is turned on, then the E5-OAM Integrated Measurementsfeature supports measurements up to 1200 links, and the Measurements Plaform is required for supportof more than 1200 links.

Links that are supported by the Measurements Platform and E5-OAM Integrated Measurementsfeature include IP associations as shown:



• Each low-speed link (LSL) counts as 1 link• Each ATM high speed link (HSL) counts as 1 link• Each SE-HSL counts as 1 link• For IPLIM, each association counts as 1 link• For IPGW, 1 link per card• For IPSG, each association counts as 1 link

The E5-OAM Integrated Measurements feature requires the following hardware and provisioning inthe system:

• E5-based control cards (E5-MASP cards and E5-MDAL cards)• Ethernet port A provisioned on the E5-MCAP card portions of the E5-MASP cards• The E5-OAM Integrated Measurements feature enabled and turned on• The E5-OAM Integrated Measurements collection option turned on in the MEASOPTS table• A provisioned customer FTP server

To mitigate network failures that could cause lost reports, it is recommended that you provisionup to three FTP servers for E5-OAM Integrated Measurements. Refer to the Database Administration- System Management User's Guide for information about configuring the FTP servers for E5-OAMIntegrated Measurements. If a network failure is on or near the EAGLE OAM IP link, then a lossof reports on the server is possible. The E5-OAM card will not switch activity if the IP link isunavailable on the active MASP. An alarm is generated, but the role change is a manual action.You can run on-demand reports to retrieve the data.

• The EAGLE OA&M IP Security feature, and Secure Shell FTP (SFTP) as a client, if secure transferis used

After collection of the measurements, scheduled reports are automatically generated and transferredfrom an E5-MASP card to a customer FTP server using the FTP interface. Existing FTP file serverreports are overwritten by subsequent requests that produce the identical file name.

Reports can be scheduled or generated on demand using the following commands:

• chg-measopts:

• Turns on the E5-OAM Integrated Measurements collection option

• Turns on or turn off the 15 Minute Measurements collection function

• Enables or disables the automatic generation and FTP transfer of scheduled measurementsreports to the FTP server

• Turns on or off the CLLI-based file name option for measurements reports files

• Turn on or off the unchannelized link label option

• chg-meas: Enables report generation. The complete command that you must enter so thatmeasurement reports are generated is chg-meas:collect=on.

• chg-mtc-measopts: Enables or disables the automatic generation and FTP transfer of scheduleddaily and hourly measurement reports to the FTP server.

• rept-stat-meas: Reports the status of the measurements subsystem including card location andstate, E5-MASP and IP link state, Alarm level, and Subsystem State.

• rept-ftp-meas: Manually initiates generation and FTP transfer of a measurements report fromthe E5-MASP card to the FTP server.



• rtrv-measopts: Displays the status of E5-OAM Integrated Measurements collection, scheduledreports, 15-Minute Measurements collection, CLLI-based file names, and unchannelized link label.

• rtrv-mtc-measopts: Displays the enabled or disabled status of all FTP scheduled measurementsreports.

Note: If a new entity is provisioned in place of a deleted entity, then the measurements for the deletedentity are set to zero. The reported peg counts apply only to the new entity.

When the E5-OAM Integrated Measurements feature is used in the system,

• The rept-meas command cannot be used for the lnp, np, and mapscrn entity types, because thefile transfer area (FTA) is disabled. Use the rept-ftp-meas command for those entity types.

• Scheduled UI reports are allowed if the system has up to 700 links, and are disabled it the systemhas more than 700 links.

Data Mirroring

The measurements data that is collected at interval, as well as the derived data that is periodicallycomputed, is stored on the active/primary collection platform and mirrored on the standby/secondaryplatform. Any MEAS reports generated after the role change are identical to the reports generatedbefore the role change. The duplication of the collected data provides an additional measure of reliabilityfor the Measurements Subsystem.

In the event that the standby/secondary platform is unavailable when the mirroring occurs, that datais retained on the active/primary, but it is not retained on the standby/secondary. If a role changeoccurs, any data collected while the standby/secondary was unavailable will not be available forreporting. A second role change is required if it is necessary to report the missing data.

Optional 15-Minute Measurements

Optional 15-minute measurements are available when the 15-minute measurement option is on andeither the Measurements Platform is configured or the E5-OAM Integrated Measurements feature isturned on. This option can change the duration for 30-minute reports to 15 minutes. The MeasurementsPlatform and the E5-OAM Integrated Measurements feature have the capability to collect and reportSTP, link, and linkset measurements on a 15-minute basis. All of the measurements available for30-minute collection are available every 15 minutes when the feature option is operational.

Note: Scheduled UI reports are disabled when the 15-minute measurements feature is enabled.

The feature is controlled by a measurement option. Turning on the feature requires a part number.The feature cannot be turned off once turned on. It is a Permanently ON feature. Upon turn on, thecollection period defaults to the 30-minute option. Refer to the Database Administration - SystemManagement User's Guide for details on implementing the 15-minute measurements feature.

The feature becomes operational when the collection period has been changed to 15 minutes. Thecollection period is changed from 30 minutes to 15 minutes (and vice versa) by using thechg-measopts:collect15min command. Refer to the Commands User's Guide for detailed usageinformation. When the 30-minute option is selected, measurements data is collected and reported eachhalf-hour at hh:00 and hh:30. When the 15-minute option is selected, measurements data is collected



and reported four times each hour at hh:00, hh:15, hh:30, and hh:45. The current state of the option isdisplayed with the Measurements Platform and E5-OAM Integrated Measurements feature options.Report types supported by 15-minute measurements are:

• systot (STP system totals)

• comp (Component)

• gtwy (Gateway)

• avl (Availability)

After 15-minute measurements collection and reporting is operational, 15-minute reports are retrievedusing rept-meas or rept-ftp-meas commands. Refer to the Commands User's Guide for detailedusage information.

Data Collection

The various scenarios for making 15-minute collection operational, and the impact on data collectionare shown in Table 3: Enabling 15-Minute Measurements - Impacts. The first column specifies the fourquarter-hour intervals during which 15-minute collection could be made operational. The secondcolumn identifies the impact of making 15-minute collection operational during the specified timewindow. If 15-minute collection is made operational during the first or third quarter hour, there is noimpact on the collected data. If 15-minute collection is made operational during the second or fourthquarter hour, the data that is collected and stored for that quarter-hour actually represents 30 minutesof data. This is not an error and no measurements data is lost. Rather it is a side effect of making15-minute collection operational after the previous quarter-hour boundary has already passed.

Table 3: Enabling 15-Minute Measurements - Impacts

Data LossImpact on Data Collection

Time Window for Making15-Minute MeasurementsOperational

None15 minutes of data will becollected for the quarter-hourxx15

xx00 to xx15

NoneThe xx15 interval will contain nodata. The xx30 interval willcontain 30 minutes of data

xx15 to xx30

None15 minutes of data will becollected for the quarter-hourxx45

xx30 to xx45

NoneThe xx45 interval will contain nodata. The xx00 interval willcontain 30 minutes of data

xx45 to xx00

Some quarter-hour measurements data may not be available for 24 hours after making 15-minutecollection operational. This condition exists for quarter-hour intervals for which 15-minute collectionhas not yet occurred. Data that was collected on a 30-minute basis is available for reporting for up to24 hours after it is collected. After the 15-minute collection option is enabled, this data remains available



on a half-hour basis (xx00 and xx30) but is not available on a quarter-hour basis (xx15 and xx45). Afterthe 15-minute collection option has been enabled for 24 hours, all 15-minute measurements data isavailable on a quarter-hour basis (xx00, xx15, xx30, and xx45).

In addition, full 30-minute data coverage will not be available until 24 hours after making 15-minutecollection not operational. Reports for specific periods will always contain the amount of data collectedfor that period. If SEAS reporting is enabled, for 24 hours after 15-minute measurements are madenot operational, 30-minute demand SEAS reports for time periods prior to feature status change willonly contain 15 minutes of data, and SEAS will not support reporting at the xx15 and xx45 times.

Also note that in the exception case of making 15-minute collection not operational, if the feature ismade not operational in the first 15 minutes of a half-hour (xx00-xx15 or xx30-xx45) and a demandreport is requested in the second 15 minutes of a half-hour (xx15-xx30 or xx45-xx60) for period=last(or period unspecified), the report given will be the last 15-minute interval (xx00-xx15 or xx30-xx45),not the last collected 15-minute interval (xx45-xx00 or xx15-xx30). Note that collection did not occurduring this 15-minute period, and Measurements data not current will be issued. To get a report forthe last collected 15-minute interval, period=specific has to issued with the command with the correctQH/HH value.

If the feature control status of 15-minute measurements is turned on and a report is requested for theactive interval (period=active) prior to the next scheduled measurements collection (based on the current15-minute measurements status), then the data will be correct but the starting time for the periodshown in the report will be incorrect. As soon as the next scheduled collection occurs, then activereports will show the correct data and the correct starting time.

A similar limitation also exists for period=last. If the feature control status of 15-minute measurementsis turned on and a report is requested for the last interval prior to the next scheduled measurementscollection (based on the current 15-minute measurements status), then the start and end times for theperiod shown in the report will be incorrect. The data presented in the report will correspond to thestart and end times. As soon as the next scheduled collection occurs, then period=last reports will showthe correct start and end times and the corresponding data for that interval.

If collection has not occurred since changing the operation status, then period=specific needs to be issuedto get the last period collected.

Reports

Reports can be scheduled or printed on-demand. Scheduled and on-demand reports are accessible bythe following administrative commands:

• chg-measopts: Used to enable or disable the automatic generation and FTP transfer of scheduledmeasurement reports to the FTP server.

• rept-ftp-meas: Manually initiates generation and FTP transfer of a measurements report fromthe MCPM to the FTP server (Measurements Platform) or from the E5-MASP to the FTP server(E5-OAM Integrated Measurements).

• rtrv-measopts: Generates a user interface display showing the enabled/disabled status of allFTP scheduled reports.

• chg-mtc-measopts: Enables or disables the automatic generation and FTP transfer of scheduledmaintenance measurements reports to the FTP server.



• rtrv-mtc-measopts: Shows the enabled/disabled status of all hourly and daily scheduledmaintenance measurements reports.

Refer to the Commands User's Guide for more information on how to use measurement commands.

Characteristics

Reports have the following characteristics.

• Categories

The following are the categories and types of measurement reports collected by the EAGLE:

• Traffic Engineering Reports

• STP system totals (SYSTOT)

• Component measurements (COMP)

• Network management (NM)

• Error Tracking/Troubleshooting Reports

• Daily availability (AVLD)

• Day-to-hour availability (AVLDTH)

• Availability (AVL)

• Maintenance Reports

• Daily maintenance measurements (MTCD)

• Day-to-hour maintenance measurements (MTCDTH)

• Hourly maintenance measurements (MTCH)

• Network Usage Reports

• Gateway (GTWY)

• Record Base (RBASE)

• Maintenance Status Reports

• Maintenance Status Indicators (MTCS)

• Entity Types

The following entity types may be reported for a particular category type.

• AIQ: ANSI41 AIQ

• ATINPQ: Any-Time Interrogation Number Portability Query

• DEIR: S13 EIR Interface

• EIR: Equipment Identity Register



• ENUM: EAGLE ENUM Mobile Number Portability and Tier One Address Resolution

• GTTAPATH: GTT Actions per path

• IDPR: IDP Pre-paid Relay Query

• LINK: Signaling link

• LNKSET: Linkset

• LNP: Local number portability

• LSDESTNI: Linkset destination network identifier

• LSONISMT: Per link set, per originating network identifier, per ISUP message type measurements

• LSORIGNI: Linkset originating network identifier

• MAPSCRN: Global Systems for Mobile Communications Mobile Application Part ScreeningMeasurements

• NP: Intelligent network application part-based number portability

• ORIGNI: Originating network identifier

• ORIGNINC: Originating network identifier for network cluster

• SCTPASOC: Per association SCTP layer

• SCTPCARD: Per card SCTP layer

• SFTHROT: SS7 Firewall Throttling GTT Action

• SIP: SIP Number Portability

• STP: All nodes

• STPLAN: TCP/IP links

• TT: Translation type

• UA: Per Application Server/Association UA layer

• VFLEX: Voice Mail Router measurements

• Accessible Periods

There are four accessible periods for which measurements may be reported:

1. Last is used to access the previous collection interval.

2. Specific is used to access a specific interval (for example, one of the previous 48 half-hourintervals).

3. Active is used to access measurements for the current collection interval.

4. All is used to access measurements for all collection intervals retained.



LSL and SE-HSL Reports

As of Release 44.0, low-speed MTP2 links and high-speed unchannelized MTP2 links can be identifiedseparately in the relevant reports.

The standard link label is "MTP2", and is applicable to all types of MTP2 links, regardless of the linkspeed. When the unchlinklabel functionality is provisioned to ON in the chg-measopts command,unchannelized links are labeled with "MTP2-UNCH", while low-speed links retain the "MTP2" label.The -UNCH label is also applied to linksets that contain unchannelized MTP2 links.

The label appears in scheduled and on-demand reports, for UI and FTP.

Measurements Platform/E5-OAM Integrated Measurements Feature Reports

Measurements Platform and E5-OAM Integrated Measurements reports have the followingcharacteristics.

Report Files

Report files are divided into three sections:

1. System header

The system header size varies depending on embedded data. A typical size of 250 bytes is used inall calculations in the examples in this manual.

2. Individual report header

The report header size varies depending on the report type, but is always the same size for anindividual report type. The size of the report data section varies depending on the number ofentities being reported, and the particular data items being reported for each entity (for example,a count of 0 versus a large count).

3. Report data

For the estimates given in this manual, 6 characters are assumed for each data item, including thecomma delimiter. Other variable quantities, such as the number of entities in the report, are statedwith each example.

The output file sizes calculated in this manual are rough estimates only. They are not intended to bean exact representation of output file size, which could vary significantly depending on the configurationof a particular system.

Table 4: Measurements Platform and E5-OAM Integrated Measurements Feature System Header

UnitDescriptionField Name

ASCII TextThe Common LanguageLocation Identifier for the STP

CLLI

ASCII TextThe software release currentlyrunning on the STP

SWREL

YYYY-MM-DDThe date on which the reportwas generated

RPTDATE



UnitDescriptionField Name

HH:MM:SSThe time at which the report wasgenerated (24-hour clock)

RPTIME

ASCII TextAn abbreviation for the timezone

TZ

ASCII TextThe type of report beinggenerated

RPTTYPE

ASCII TextThe period of the reportRPTPD

YYYY-MM-DDThe date for the report intervalIVALDATE

HH:MM:SSThe starting time of the reportinterval

IVALSTART

HH:MM:SSThe ending time of the reportinterval

IVALEND

IntegerThe number of entities containedin the report

NUMENTIDS

Example header format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","31.3.0-39.1.0","1999-01-17","15:51:37","EST","STP SYSTEM TOTAL MEASUREMENTS ON STP","LAST","1999-01-17","15:00:00","15:30:00",1<cr><lf><cr><lf>

File Naming Conventions

File names consist of fields separated by underscores and followed by the .csv extension. This formatallows the files to be readily identified as a comma-separated value (CSV) format. Due to the overalllength of the file names, long file names (beyond 8.3 format) are utilized.

• CLLI-based Names Disabled

These file names consist of three fields identified as follows:

• Up to 13 characters for the report type (sched-entity, for example, systot-stp or mtcdth-lnkset)

• 8 characters for the report date (yyyymmdd). This reflects the date the data is generated.

• 4 characters for the ending report time (hhmm). This is defined as the common boundarybetween the end of the last period and the beginning of the next period. For example, the halfhour from 2:00PM to 2:30PM would end at 1430. A day-to-hour period ends on the hour. Adaily period or specific request for the final hour or half-hour of a day ends at 2400, midnight.

Examples of output file names:



• Half hourly STP system totals generated 1999-02-24 at 15:22:00 for the last period would be (theperiod from 1430 to 1500 on 02/24/99):

systot-stp_19990224_1500.csv

• Maintenance daily linkset report generated 2001-07-17 at any time would be (the period from0000 to 2400 on 07/16/01):

mtcd-lnkset_20010716_2400.csv

• Maintenance day-to-hour link report generated 2003-04-29 at 08:32:00 would be (the periodfrom 0000 to 0800 on 04/29/03):

mtcdth-link_20030429_0800.csv

• Half hourly STP system totals generated 1999-02-23 at 00:15:20 for the specific end time 0030would be (the period from 0000 to 0030 on 02/23/99):


• Half hourly STP system totals generated 1999-02-24 at 00:15:30 for the specific end time 2330would be (the period from 2300 to 2330 on 02/23/99):


• Half hourly STP system totals generated 1999-02-24 at any time for the specific end time 2400or 0000 would be (the period from 2330 to 2400 on 02/23/99):


Some applications will reformat fields when opening the .csv file. Use a text editor when opening.csv files to examine file content as presented in the output file examples in this document.

• CLLI-based Names Enabled

These file names consist of four fields identified as follows:

• Up to 11 characters for the CLLI of the EAGLE.

• Up to 13 characters for the report type (sched-entity, for example, systot-stp or mtcdth-lnkset)

• 4 characters for the report date (mmdd). This reflects the date the data is generated.

• 4 characters for the ending report time (hhmm). This is defined as the common boundarybetween the end of the last period and the beginning of the next period. For example, the halfhour from 2:00PM to 2:30PM would end at 1430. A day-to-hour period ends on the hour. Adaily period or specific request for the final hour or half-hour of a day ends at 2400, midnight.

Examples of output file names:

• Half hourly STP system totals generated 02-24 at 15:22:00 for the last period would be (theperiod from 1430 to 1500 on 02/24:

wnrtpaah01w_systot-stp_0224_1500.csv

• Maintenance daily linkset report generated 07-17 at any time would be (the period from 0000to 2400 on 07/16:

wnrtpaah01w_mtcd-lnkset_0716_2400.csv



• Maintenance day-to-hour link report generated 04-29 at 08:32:00 would be (the period from0000 to 0800 on 04/29:

wnrtpaah01w_mtcdth-link_0429_0800.csv

• Half hourly STP system totals generated 02-23 at 00:15:20 for the specific end time 0030 wouldbe (the period from 0000 to 0030 on 02/23):


• Half hourly STP system totals generated 02-24 at 00:15:30 for the specific end time 2330 wouldbe (the period from 2300 to 2330 on 02/23):


• Half hourly STP system totals generated 1999-02-24 at any time for the specific end time 2400or 0000 would be (the period from 2330 to 2400 on 02/23/99):


Some applications will reformat fields when opening the .csv file. Use a text editor when opening.csv files to examine file content as presented in the output file examples in this document.

Report Limitations

The measurement registers of a system total report can store a maximum count of 4294967295 (size ofthe register), after which the register will roll over to 0. This limitation puts constraint on the numberof the following cards that can run at the maximum card TPS in the system, or on the value of maximumTPS that can be processed by the maximum number of those cards allowed in the system:

• ENUM

• Up to 12 ENUM cards can run at the maximum advertised TPS (4000) in the system withoutexceeding the count capacity.

• The maximum allowed 16 ENUM cards can run at a maximum of 3100 TPS in the system withoutexceeding the count capacity.

• The maximum allowed 16 ENUM cards running at maximum card TPS of 4000 can run for 18hours before the count capacity is exceeded.

• SIP

• Up to 12 SIP cards can run at the maximum advertised TPS (4000) in the system withoutexceeding the count capacity.

• The maximum allowed 16 SIP cards can run at a maximum of 3100 TPS in the system withoutexceeding the count capacity.

• The maximum allowed 16 SIP cards running at maximum card TPS of 4000 can run for 18 hoursbefore the count capacity is exceeded.

• S13

• Up to six S13 cards can run at the maximum advertised TPS (8000) in the system withoutexceeding the count capacity.

• The maximum allowed 16 S13 cards can run at a maximum of 3100 TPS in the system withoutexceeding the count capacity.



• The maximum allowed 16 S13 cards running at maximum card TPS of 8000 can run for ninehours before the count capacity is exceeded.

These limitations do not affect the processing of traffic. If the limitations are exceeded, then the valueof the measurements register will roll over after reaching its maximum value and the pegging will beincorrect.



Chapter

3Reports

Topics:

• Report Tables.....39• STP System Totals Measurements (SYSTOT)..39• Component Measurements (COMP).....71• Network Management Measurements (NM)...105• Daily Availability Measurements (AVLD).....123• Day-To-Hour Availability Measurements

(AVLDTH).....131• Availability Measurements (AVL).....139• Daily Maintenance Measurements (MTCD)...152• Day-to-Hour Maintenance Measurements

(MTCDTH).....238• Hourly Maintenance Measurements (MTCH).283• Gateway Measurements (GTWY).....327• Record Base Measurements (RBASE).....343• Maintenance Status Reports (MTCS).....357


Report Tables

The tables that follow in this chapter define the parameters used in the measurement reports. Includedin the tables are the event name, description and unit of measurement as described in TelcordiaGR-82-CORE.

The Example Commands and the Example Outputs are separated according to the collection methodused to report measurements.

• FTP - Indicates measurements that are transferred to the customer's FTP server via the FTP interface.

• UI - Indicates measurements that are output on the terminal interface.

Note: The Status Event Name appearing in the Measurement Tables only appears when using theMeasurements Platform or E5-OAM Integrated Measurements. The Example Outputs and the ExampleInputs are examples. Variations exist and are likely. Refer to the Commands User's Guide for complete(options, variables) information on command usage.

If the Measurements Platform is enabled, the chg-meas:collect=off command can be used todisable the scheduled UI report output without affecting the actual collection. If UI based reports aredisabled via this mechanism, then the Traffic Unsolicited Output Message Group may be turned offsince there is no output directed to it.

STP System Totals Measurements (SYSTOT)

These measurements are used to monitor the overall performance of the STP.

Entity types: STP, Translation Type (TT), STPLAN, IDPR, SIP, SFTHROT

Accumulation interval: Every 30 minutes

Optional Accumulation Interval: Every 15 minutes

STP retention period: 24 hours

Reporting modes: Scheduled, On-Demand

Accessible collection periods: Last, Specific

STP SYSTOT Report

Example Commands:

UI: rept-meas:type=systot:enttype=stp

FTP: rept-ftp-meas:type=systot:enttype=stp


ReportsMeasurements

Table 5: STP System Total STP Measurements

UnitDescriptionEvent Name

peg countNumber of Critical SystemAlarms - The total number ofcritical system alarms.

CRSYSAL

peg countDN Table Not Present - Thetotal number of MSUs that

DNTBLNOP

require DN service but thatarrise on an IMSI ServiceModule, which does not containEPAP DN data

peg countDTAMSUs Lost - The totalnumber of MSUs that were

DTAMSULOST

discarded because the originalMSU was too large to beencapsulated.

milli-secondsDuration of Internal NodeFailure - Total time that

DURINTFL

messages could not be switchedto outgoing link (apart from anylink interface failure).

peg countG-Flex GTTs with Match - Thetotal number of G-Flex Global

GFGTMATCH

Title Translations successfullycompleted.

peg countG-Flex GTTs No Match - Thetotal number of G-Flex Global

GFGTNOMCH

Title Translations completed thatdid not match an entry in theGSM database.

peg countG-FlexGTTs No Look-up - Thetotal number of G-Flex Global

GFGTNOLKUP

Title Translations that could notbe looked up in the GSMdatabase because of an error, i.e.,when the G-Flex SCCP CdPAverification fails.

peg countGTTs Performed - Usually, thetotal number of MSUs that

GTTPERFD

successfully completed globaltitle translation (GTT). Alsoincludes G-Port and INPMSUs


ReportsMeasurements


that got a match in either theG-Port, INP, or GTT DB.

Sometimes, GTTPERFD indicatesthe total number of global titletranslations (GTTs) performedon MSUs that successfullycompleted GTT, because severalGTTs may happen for the sameMSU. One scenario wheremultiple GTTs occur for an MSUoccurs is when the ANSI/ITUSCCP Conversion Feature isactivated. In this case, the countfor GTTPERFD can be doublewhat it would be without thefeature, although the number ofMSUs received by the EAGLEdid not change.

peg countGTTs Unable to Perform -Diagnostic 0: No Translation for

GTTUN0NS

Address of Such Nature - Thesum total of times that thespecified type of translation inan MSU was not supported bythe STP.

This register contains the sum ofthe GTTUN0NS register in thesystot-tt report and theCGGTTUN0NS register in thesystot-cgtt report.


GTTUN1NT

This Address - The sum total oftimes that SCCP could not finda translation in the translationtable. This includes Global Titletranslations, Point Codetranslations, and Subsystemtranslations.

This register contains the sum ofthe GTTUN1NT register in thesystot-tt report and theCGGTTUN1NT register in thesystot-cgtt report.


ReportsMeasurements


peg countThe number of messagescounted by IARTOTAL that

IARFAILD

were dismissed due to one of theproblems reported by the UIMsthat are specific to the IAR Basefeature (that is, UIM 1020..1021and 1427..1431).


IARNOTAP

were not counted by IAR PASSDor IARFAILD; theThey weredismissed because modificationwas determined to beinappropriate (that is, notapplicable). This excludesmessages that were dismissedbecause of no matching entry indatabase (GT and TRIG CSL list,DPC (not Home SCP), NPP Rule,RTDB).


IARPASSD

were modified by the IAR basefeature. The IAR Base must havechanged the CdPN parameter,CgPN parameter, or both.

peg countThe total number of messagesreceived by the IAR Base feature

IARTOTAL

from TTR Service Selection; thetotal number to which IARpre-processing is applied. Thesum of the IARNOTAP,IARPASSD, and IARFAILD pegsand messages that weredismissed because there was nomatching entry in database: GTand TRIG CSL list/DPC (notHome SCP), NPP Rule, RTDB.

peg countTotal number of IDP/IDPSMSmessages that were selected for

IDPAPTYGTT

A-Party Routing service, but fellthrough to GTT (with or withouthaving attempted SK routingfirst).


IDPAPTYRTD


ReportsMeasurements


A-Party Routing service, andwere successfully routed basedon A-Party PPSOPTS routingdata (that is, routing dataassociated with the RTDB PTassigned to the A-Party digits).


IDPAPTYSKR

A-Party Routing service, but fellthrough to Service Key Routing,and were successfully routedbased on SK/BCSM PPSOPTSdata (that is, routing dataassociated with the RTDB PTassigned to the SK/BCSM entry).

peg countTotal number of IDP/IDPSMSmessages received that matched

IDPBKLCONN

the blacklist criteria and aCONNECT response wasgenerated.

peg countTotal number of IDP/IDPSMSmessages received that did not

IDPBKLCONT

match the blacklist criteria anda CONTINUE response wasgenerated.

peg countThe total number of MSUsselected for IDPR service which

IDPRMSERR

could not be processed due toerrors in encoding, decoding, orformatting, or IDP A-Partyrouting, or IDP SK Routing.

peg countTotal number of MSUs selectedfor IDPR service which fell

IDPRMSFAIL

through to GTT due to (1) nomatch on MSISDN in MNPDB,or (2) match on MSISDN but noassociation to RN or SP forCDPNNP or CGPNNP, (3) nomatch for IDP A-Party Blacklistquery-response criteria or, (4)IDP Blacklist relay resulted infalling through to GTT forrouting, or (5) IDP A-Party or SKRouting resulted in fallingthrough to GTT routing (due to


ReportsMeasurements


no-match on MSISDN orinsufficient data).

peg countTotal number of MSUs receivedand selected for IDPR service.

IDPRMSRCV

This register includes counts forMSUs that resulted in bothsuccessful and unsuccessfulMNPDB lookups.

peg countNumber of MSUs selected forIDPR service for which the

IDPRMSSUCC

requested IDPR feature setfunctionalities were executedsuccessfully. This includes pegsto IDPAPTYRTD, IDPSKRTD,IDPBKLCONN, andIDPBKLCONT registers.

peg countTotal number of IDPs that wereselected for Service Key Routing

IDPSKGTT

(without having first gone toA-Party Routing), but fellthrough to GTT.


IDPSKRTD

Service Key Routing (withouthaving first gone to A-PartyRouting), and were successfullyrouted based on SK/BCSMPPSOPTS data.

peg countIMSI Table Not Present - Thetotal number of MSUs that

IMSITBLNOP

require IMSI service but thatarrise on a DN Service Module,which does not contain EPAPDN data

peg countNumber of Major SystemAlarms - The total number ofmajor system alarms.

MASYSAL

peg countNumber of Minor SystemAlarms - The total of minorsystem alarms.

MISYSAL

peg countTotal number of TC_CONTINUEmessages (with Component

MOSMSSEGER

Portion) discarded by the


ReportsMeasurements


Portability Check for MO SMfeature.

peg countTotal number of TC_CONTINUEmessages (with Component

MOSMSSEGOK

Portion) relayed successfully bythe Portability Check for MOSMS and/or MO-based SMS NPfeature.

peg countTotal number of IDP messagesthat did not fully meet the

MSIDPNOMCH

criteria of the IDP Screening forPrepaid feature. These messagesare relayed to their destinationby GTT.

peg countTotal number of IDP messagesthat did meet the criteria of the

MSIDPMATCH

IDP Screening for Prepaidfeature. Instead of sending theIDP message onward, aContinue message is sent to theoriginating MSC. The criteriainvolves matching the followingTCAP fields with EAGLECommon Screening Lists:

1. CgPA and CdPA areprovisioned in the In-NetworkSubscriber List.

2. The Teleservice and ServiceKey values are in the ServiceKey/Teleservice List.

peg countMSUs Rcvd – Invalid DPC -Number of MSUs received and

MSINVDPC

discarded because the DPCcould not be found in the STProuting table.

peg countMSUs Discarded – Invalid Link- Number of MSUs discarded

MSINVLNK

because of an incorrect SLC. (TheSLC refers to a nonexistent linkor the same link.)

peg countMSUs Discarded – Invalid SIF-Number of MSUs that have been

MSINVSIF


ReportsMeasurements


received and discarded becauseof an invalid SIF.

peg countMSUs Rcvd – Invalid serviceindicator octet (SIO) - Number

MSINVSIO

of MSUs received and discardedbecause the service requested inthe service indicator octet (SIO)was not supported by the STP.

peg countMSUs Discarded – Invalid SLC- Number of MSUs discarded

MSINVSLC

because of an invalid SLC codein the ECO/COO.

peg countMSUs Discarded – InaccessibleDPC - The total number of MSUs

MSNACDPC

discarded because of aninaccessible DPC.

peg countMSUs Discarded - Translationfound, but provisioned ACTIONcaused the MSU to be discarded.

MSSCCPDISC

peg countMSUs Discarded – RoutingFailure - Number of MSUs

MSSCCPFL

discarded due to an SCCProuting failure.

peg countMSUs Discarded – GatewayScreening- The total number of

MSUDSCRD

MSUs that failed gatewayscreening and were discarded.See linkset report for individualpeg counts.

peg countMSUs Discarded – Level2/Level 3 Queue Full - Number

MSULOST1

of MSUs discarded because thelevel 2 to level 3 queue was full.

peg countMSUs Discarded – Route OnHold Buffer Overflow - Number

MSULOST2

of MSUs discarded because therouting buffer was in overflow.

peg countMSUs Discarded –MSULOST3

1. LS On Hold BufferOverflow - The number ofMSUs discarded because the


ReportsMeasurements


linkset-on-hold buffer was inoverflow. The On HoldBuffer is used duringchangeover/changebacksituations to ensure thattraffic is sequenced correctly.During changeover andchangeback, MSUs that wereoriginally sent over linkswhich are now failed (notIS-NR) are buffered while thechangeover/changebackprocedures are carried out.Once those procedures arecompleted, the traffic in theon-hold buffer is routedbased on the currentconfiguration.

2. LSL LIM does not have SCCPassignment for receivedSCCP traffic.

3. HSL –

• All Class 1 (sequenced)GTT traffic addressed toEAGLE

• A Class 0 GTT messagefor EAGLE arrives whenthe SCCP TVG queue isfull

• A GTT message in theSCCP TVG queue is morethan 2 seconds old.

peg countMSUs Discarded – Rcvd QueueFull - Number of MSUs

MSULOST4

discarded because the receivequeue was full.

peg countMSUs Discarded – LIM Init -Number of MSUs discarded

MSULOST5

while the LIM card wasinitializing.

peg countMSUs Discarded - The numberof MSUs discarded due to an

MSULOST6

error encountered duringinternal (IMT) transfer of MSUbetween cards.


ReportsMeasurements


peg countMSUSCCP Failure - TotalMSUs Discarded Due to SCCPConversion Failure.

MSUSCCPFLR

xact per secondThe current daily system-widepeak SCCP message handlingload in transactions per second.

NMSCCPMH

peg countMSUs Originated – InvalidDPC - Number of MSUs with aninvalid DPC.

OMSINVDPC

peg countOriginated MSUs - Totalnumber of outgoing MSUs

ORIGMSUS

successfully passed to MTP level2 for transmission, whilecarrying the STP point code inthe OPC field.

octetsOriginate MSU Octets - Totalnumber of outgoing octets

ORMSUOCT

associated with MSUs carryingthe STP point code in the OPCfield. This includes octets addedin MTP level 2 processing.

peg countOversized MTP 3 Messages -Number of messages received

OVSZMSG

by an HSL that exceeds 272octets (level 3) and is discarded.

xact per secondThe overall system-wide peakSCCP message handling load in

PKSCCPMH

transactions per second. Valueis the highest recorded since itwas last reset using therept-stat-sccp:mode=peakresetcommand.

peg countTotal number of successful DPClookups in PCT feature.

PCTDPCLKP

peg countTotal number of successful OPClookups in PCT feature.

PCTOPCLKP

peg countTotal number of times that aGTT translation matched a Point

SCCPLOOP

Code in the STP’s loopset entriesresulting in either a notify ordiscard of an SCCP message.


ReportsMeasurements


statusIndication of Data ValiditySTATUS

K indicates good data

I indicates incomplete interval

N indicates data not current.

peg countThrough-Switched MSUs - Thetotal number of MSUs that did

THRSWMSU

not carry the STP point code inthe OPC or the DPC, and weresuccessfully passed to MTP level2 for transmission.

peg countTerminated MSUs - The totalnumber of incoming MSUs

TRMDMSUS

carrying the STP point code inthe DPC.

octetsTerminated MSU Octets - Thetotal number of octets associated

TRMSUOCT

with incoming MSUs carryingthe STP point code in the DPC.Includes octets removed in MTPlevel 2 processing.

octetsThrough-Switched MSU Octets- The total number of octets

TSMSUOCT

associated with MSUs that didnot carry the STPs point code inthe OPC or the DPC, and weresuccessfully passed to MTP level2 for transmission.

peg countTotal number of messages forwhich UDT(S) to XUDT(S),

UDTXUDTF

XUDT(S) to UDT(S) orSegmented XUDT(S) to UDT(S)conversion has failed.

peg countX-List Entry Not Created - Thetotal number of times that an

XLXTELEI

x-list was not created because theException List ExclusionIndicator (ELEI) for the clusteris set to yes.

peg countX-List Entry Not Created - Thetotal number of times an x-list

XLXTSPACE

entry was not created because


ReportsMeasurements


there is no more space in theroute/destination table.

UI Example Output:

e1061001 11-01-22 02:24:36 MST EAGLE5 43.0.0-63.49.0 TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON STP REPORT PERIOD: LAST REPORT INTERVAL: 11-01-22, 01:30:00 THROUGH 01:59:59

STP-SYSTOT MEASUREMENTS

These measurements are from 11-01-22, 01:30:00 through 01:59:59. ORIGMSUS = 0, TRMDMSUS = 0, THRSWMSU = 0, ORMSUOCT = 0, TRMSUOCT = 0, TSMSUOCT = 0, DURINTFL = 0, DTAMSULOST = 0, MSINVDPC = 0, MSINVSIO = 0, OMSINVDPC = 0, MSINVLNK = 0, MSINVSIF = 0, MSNACDPC = 0, MSINVSLC = 0, GTTPERFD = 0, GTTUN0NS = 0, GTTUN1NT = 0, MSSCCPFL = 0, MSULOST1 = 0, MSULOST2 = 0, MSULOST3 = 0, MSULOST4 = 0, MSULOST5 = 0, CRSYSAL = 2, MASYSAL = 3, MISYSAL = 19, XLXTSPACE = 0, XLXTELEI = 0, MSUDSCRD = 0, OVSZMSG = 0, GFGTMATCH = 0, GFGTNOMCH = 0, GFGTNOLKUP = 0, MSUSCCPFLR = 0, NMSCCPMH = 0, PKSCCPMH = 0, MSSCCPDISC = 0, IDPRMSRCV = 0, IDPRMSSUCC = 0, IDPRMSFAIL = 0, IDPRMSERR = 0, MSIDPNOMCH = 0, MSIDPMATCH = 0, MSULOST6 = 0, SCCPLOOP = 0, MOSMSSEGOK = 0, MOSMSSEGER = 0, IDPAPTYRTD = 0, IDPAPTYSKR = 0, IDPAPTYGTT = 0, IDPSKRTD = 0, IDPSKGTT = 0, IDPBKLCONN = 0, IDPBKLCONT = 0, IARTOTAL = 0, IARNOTAP = 0, IARPASSD = 0, IARFAILD = 0, UDTXUDTF = 0, PCTDPCLKP = 0, PCTOPCLKP = 0

FTP Example Output File Name:systot-stp_20090319_1530.csv

FTP Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"

"e1061001","EAGLE5 43.0.0-63.49.0","2011-01-23","01:11:26","MST ","STP SYSTEM TOTAL MEASUREMENTS ON STP","LAST","2011-01-23","00:30:00","01:00:00",1

"STATUS","ORIGMSUS","TRMDMSUS","THRSWMSU","ORMSUOCT","TRMSUOCT","TSMSUOCT","DURINTFL","DTAMSULOST","MSINVDPC","MSINVSIO","OMSINVDPC","MSINVLNK","MSINVSIF","MSNACDPC","MSINVSLC","GTTPERFD","GTTUN0NS","GTTUN1NT","MSSCCPFL","MSULOST1","MSULOST2","MSULOST3","MSULOST4","MSULOST5","CRSYSAL","MASYSAL","MISYSAL","XLXTSPACE","XLXTELEI","MSUDSCRD","OVSZMSG","GFGTMATCH","GFGTNOMCH","GFGTNOLKUP","MSUSCCPFLR","NMSCCPMH","PKSCCPMH","MSSCCPDISC","IDPRMSRCV","IDPRMSSUCC","IDPRMSFAIL","IDPRMSERR","MSIDPNOMCH","MSIDPMATCH","MSULOST6","SCCPLOOP","MOSMSSEGOK","MOSMSSEGER","IDPAPTYRTD","IDPAPTYSKR","IDPAPTYGTT","IDPSKRTD","IDPSKGTT","IDPBKLCONN","IDPBKLCONT","IARTOTAL","IARNOTAP","IARPASSD","IARFAILD","UDTXUDTF","PCTDPCLKP","PCTOPCLKP""K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,2,3,19,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

Assuming the data line will be:

4 char status + 62*(avg. 6 chars per field) + 2 = 378 chars

Typical file size:


ReportsMeasurements

Table 6: Typical File Size: systot-stp.csv

File Size=Report Data+ReportHeader+

SystemHeader

1352 bytes=378+724+250

TT SYSTOT Report

When a GTT Actions feature is on with a feature that does translation based on the Called Party, theGTT measurements in this report (such as GTTADISC0) are updated.

Example Commands:

UI: rept-meas:type=systot:enttype=tt

FTP: rept-ftp-meas:type=systot:enttype=tt

Table 7: STP System Total Translation Type Measurements


peg countAdvanced CdPAGTTsPerformed - The total number of

AGTTPERFD

MSUs that successfully passedAdvanced CdPA Global TitleTranslation (AGTT). This registerappears in the SYSTOT-TTreport ONLY.

peg countFLOBR CDPA GTTs Performed- The total number of MSUs that

FCDGTTPRFD

successfully completed FlexibleCdPA Global Title Translation.This register appears in theSYSTOT-TT report ONLY.

peg countGTT Actions – MSUs Discarded- The total number of messages

GTTADISC0

discarded by the DISCARD GTTAction.


GTTADISC1

discarded by the UDTS GTTAction.


GTTADISC2

discarded by the TCAP ErrorGTT Action


ReportsMeasurements


peg countGTT Actions – MSUsDuplicated - The total number

GTTADUP

of messages for which DuplicateMSU was sent. Multipleduplicate actions in an action setshall also increment this registeronly once.

peg countGTT Actions – MSUsForwarded - The total number

GTTAFWD

of messages forwarded byForward GTT Action.

peg countGTT Actions - The total numberof messages receiving any GTTaction.

GTTASET


GTTPERFD

successfully completed globaltitle translation (GTT). Alsoincludes G-Port and INPMSUsthat got a match in either theG-Port, INP, or GTT DB.



GTTUN0NS

Address of Such Nature - Totalnumber of times that thespecified translation type in anMSU was not supported by theSTP or the form of the GTT wasincorrect for the given


ReportsMeasurements


translation type. Also includesG-Port, INP and GTT MSUs thatdid not match on new selectors(GTI,NP,NAI) in addition toones not matching on TT.


GTTUN1NT

This Address - Number of timesthat a match for the global titlecould not be found in thetranslation table. Also includesG-Port, INP MSUs that fellthrough to GTT, got a selectormatch, but still did not get amatch on the GTA.

peg countThe total number of messagesserviced by GFLEX GTT Action.

GTTASRVGFLX

peg countThe total number of messagesserviced by GPORT GTT Action.

GTTASRVGPRT

peg countThe total number of messagesserviced by SMSMR GTT Action.

GTTASRVSMSR

peg countThe total number of messagesserviced by SFLOG GTT Action.

GTTASFLOG

peg countThe total number of messagesthat successfully pass SCPVALGTT Action.

GTTAMSVTO

peg countThe total number of messagesdiscarded by SCPVAL GTTAction.

GTTAMSVDI

peg countThe total number of messageswhere validation was notapplied by SCPVAL GTT Action.

GTTAMSVNA


K – indicates good data

I – indicates incomplete interval

N – indicates data not current.


ReportsMeasurements

UI Example Output:

> rept-meas:type=systot:enttype=tt:tt=1

eagle1 15-09-20 03:55:58 EST EAGLE5 46.3.0.0.0-66.11.0 TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON TT REPORT PERIOD: LAST REPORT INTERVAL: 15-09-20, 03:00:00 THROUGH 03:29:59

TT-SYSTOT MEASUREMENTS: TT: 1

These measurements are from 15-09-20, 03:00:00 through 03:29:59. GTTPERFD = 0, GTTUN0NS = 0, GTTUN1NT = 0, AGTTPERFD = 0, FCDGTTPRFD = 0, GTTADISC0 = 0, GTTADISC1 = 0, GTTADISC2 = 0, GTTADUP = 0, GTTAFWD = 0, GTTASET = 0, GTTASRVGFLX= 0, GTTASRVGPRT= 0, GTTASRVSMSR= 0, GTTASFLOG = 0, GTTAMSVTO = 0, GTTAMSVDI = 0, GTTAMSVNA = 0

;

FTP Example Output File Name: systot-tt_20150124_2230.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 46.3.0.0.0-66.11.0","2015-09-20","03:57:47","EST ","STP SYSTEM TOTAL MEASUREMENTS ON TT","LAST","2015-09-20","03:00:00","03:30:00",256"STATUS","TT","GTTPERFD","GTTUN0NS","GTTUN1NT","AGTTPERFD","FCDGTTPRFD","GTTADISC0","GTTADISC1","GTTADISC2","GTTADUP","GTTAFWD","GTTASET","GTTASRVGFLX","GTTASRVGPRT","GTTASRVSMSR","GTTASFLOG","GTTAMSVTO","GTTAMSVDI","GTTAMSVNA""I","0",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0. . . . .

"K","255",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

Assuming each data line will be:

4 char status + 4 char TT + 18 * (6 char data) + 2 = 118 chars

For a report of 256 TTs, example typical file size:

Table 8: Typical File Size: systot-tt.csv

File Size=Report data+Reportheader+System

header

30,688 bytes=30,208+230+250

CGTT SYSTOT Report

These measurements are used to monitor the overall performance of the STP.

The system total CGTT report requires the Origin Based SCCP Routing feature to be enabled or FLOBRfeature to be activated. The entity type for CGTT reports reuses TT.When a GTT Actions feature is onwith OBSR feature (which does translation based on the Calling Party), the GTT measurements thathave names beginning with CGGTT (such as CGGTADISC0) are updated.


ReportsMeasurements

Note: The CGTT registers in the SYSTOT-CGTT report are pegged only if the GTT Translation modeis either FLOBR_CGPA (FG) or CGPA. The GTT Translation mode is determined by the GTTMODEparameter in the rtrv-ls command. When the GTTMODE is System default (SysDflt), the mode isdetermined from the DFLTGTTMODE option of the SCCPOPTS table.

Example Commands:

UI: rept-meas:type=systot:enttype=tt

FTP: rept-ftp-meas:type=systot:enttype=tt

Table 9: Calling Party GTT Measurements


peg countCgPAGTTs Performed - Thetotal number of MSUs that

CGTTPERFD

successfully passed CgPA globaltitle translation (GTT)(CgPAGTA, CgPA PC, or OPC). Thisregister is pegged only when theCgPA TT is present in the MSU.Since GTT can be done on theCgPA PC or on the OPC, theCgPA GTA is not a pre-requisiteto perform GTT.

This register appears in theSYSTOT-CGTT report ONLY,which is only generated if theOrigin Based SCCP Routingfeature is enabled or FLOBRfeature is turned on.


CGGTTADISC0



CGGTTADISC1



CGGTTADISC2



CGGTTADUP

of messages for which DuplicateMSU was sent. Multipleduplicate actions in an action set


ReportsMeasurements


shall also increment this registeronly once.


CGGTTAFWD



CGGTTASET

peg countCgPAGTTs Unable to Perform- Diagnostic 0: CgPA selectors

GTTUN0NS

not found - The total number oftimes that the specified type oftranslation in an MSU was notsupported by the STP. Thisregister counts MSUs for whichCgPA selectors were not found.This register appears in theSYSTOT-CGTT report ONLY,which is only generated if theOrigin Based SCCP Routingfeature is enabled or FLOBRfeature is turned on.

peg countOrigin Based GTTs Unable toPerform - Diagnostic 1: - The

CGGTTUN1NT

number of times that a match forthe global title or point codecould not be found in thetranslation table because:

Translation not found in CgPAGTA GTTSET or in CgPA PCGTTSET or in OPC GTTSET.

GTT on CgPA PC is required,but CgPA PC is not present inthe MSU.

This register is pegged when theCgPA TT is present in the MSU.Since GTT can be done on theCgPA PC or on the OPC, theCgPA GTA is not a pre-requisiteto perform GTT.

This register shall also bepegged, if FLOBR CgPA gttmodeis used, and translation is not


ReportsMeasurements


successful for any of thefollowing reasons:

• maximum search depth isreached

• duplicate GTTSET type isencountered

• translation not found (anyGTTSET type)

• CdPA SSN required, but notpresent in the MSU

• CgPA SSN required, but notpresent in the MSU

• CgPA PC required, but notpresent in the MSU

• Default CgPA PC Set isrequired, but not provisioned(ANSI or ITU)

This register appears in theSYSTOT-CGTT report ONLY,which is only generated if theOrigin Based SCCP Routingfeature is enabled or FLOBRfeature is turned on.

peg countFLOBR CGPA GTTs Performed- The total number of MSUs that

FCGGTTPRFD

successfully completed FlexibleCgPA Global Title Translation.This register appears in theSYSTOT-CGTT report ONLY,which is only generated iftheOrigin Based SCCP Routingfeature is enabled or FLOBRfeature is turned on.


CGGTTSRGFLX


CGGTTSRGPRT


CGGTTSRSMSR


CGGTTASFLOG


ReportsMeasurements



CGGTTAMSVTO


CGGTTAMSVDI


CGGTTAMSVNA



I – indicates incomplete interval;


UI Example Output:

tekelecstp 15-09-06 22:34:19 EST EAGLE5 46.3.0.0.0-66.11.0 TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON CGTT REPORT PERIOD: LAST REPORT INTERVAL: 15-09-06, 22:00:00 THROUGH 22:29:59

CGTT-SYSTOT MEASUREMENTS: CGTT: 1

These measurements are from 15-09-06, 22:00:00 through 22:29:59. CGGTTPERFD = 0, CGGTTUN0NS = 0, CGGTTUN1NT = 0, FCGGTTPRFD = 0, CGGTTADISC0= 0, CGGTTADISC1= 0, CGGTTADISC2= 0, CGGTTADUP = 0, CGGTTAFWD = 0, CGGTTASET = 0, CGGTTSRGFLX= 0, CGGTTSRGPRT= 0, CGGTTSRSMSR= 0, CGGTTASFLOG= 0, CGGTTAMSVTO= 0, CGGTTAMSVDI= 0, CGGTTAMSVNA= 0

;

FTP Example Output File Name:systot-cgtt_20020124_2230.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 46.3.0.0.0-66.11.0","2014-01-24","22:33:34","EST ","STP SYSTEM TOTAL MEASUREMENTS ON CGTT","LAST","2014-01-24","22:00:00","22:30:00",256

"STATUS","TT","CGGTTPERFD","CGGTTUN0NS","CGGTTUN1NT","FCGGTTPRFD","CGGTTADISC0","CGGTTADISC1","CGGTTADISC2","CGGTTADUP","CGGTTAFWD","CGGTTASET","CGGTTSRGFLX","CGGTTSRGPRT","CGGTTSRSMSR","CGGTTASFLOG","CGGTTAMSVTO","CGGTTAMSVDI","CGGTTAMSVNA""K","0",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0. . . . .

"K","255",0,0,0,0,0,0,0,0,0,0,0,0,0



ReportsMeasurements

4 char status + 4 char TT + 17 * (6 char data) + 2 = 112 chars

For a report of 256 TTs, example typical file size:

Table 10: Typical File Size: systot-cgtt.csv


header

29,166 bytes=28,672+244+250

STPLAN SYSTOT Report

Note:

The peg counts for STPLAN measurements have the possibility of rolling over during periods of highSTPLAN message transmit and receive. On the measurement reports, these measurements show upas negative numbers. This indicates that STPLAN transmit-and-receive measurements have valuesgreater than four gigabytes of data.

Example Commands:

UI: rept-meas:type=systot:enttype=stplan

FTP: rept-ftp-meas:type=systot:enttype=stplan

Table 11: STP System Total STPLAN Measurements


peg countEthernet Alignment Error -Number of packets not received

ENETALNERR

over the STPLAN interfacebecause of ethernet alignmenterrors.

peg countEthernet Bus Busy - Number oftransmissions attempted when

ENETBUSBSY

the STPLAN ethernet bus wasbusy.

peg countEthernet Collision Error -Number of packets not

ENETCOLERR

transmitted by STPLAN becauseof excessive collisions on theSTPLAN ethernet bus.

peg countEthernet CRC Error - Numberof packets not received on the

ENETCRCERR

STPLAN ethernet due to CRCerrors.


ReportsMeasurements


peg countEthernet Octets Received - Thetotal number of octets received

ENETOCTRCV

on the STPLAN ethernetinterface.

peg countEthernet Octets Transmitted -The total number of octets

ENETOCTXMT

transmitted on the STPLANethernet interface.

peg countEthernet Receive BufferOverflow Errors - Number of

ENETOVRERR

packets not received by STPLANbecause of a receive bufferoverflow.

peg countIP Address Error - The totalnumber of inbound IP

IPADDRERR

datagrams discarded on theSTPLAN interface due to a baddestination address.

peg countIP Header Errors - The totalnumber of inbound IP

IPHDRERR

datagrams discarded on theSTPLAN interface due to headererrors.

peg countIP Protocol Error - Number ofinbound IP datagrams discarded

IPPROTERR

by STPLAN due to an error inthe packet (invalid protocol).

peg countSTPLAN Discarded 1 - Numberof SLAN MSUs discarded by the

SLANDISC1

LIM cards for STPLAN featuredisabled and records aging offof the local queue.

peg countSTPLAN Discarded 2 -Numberof SLAN MSUs discarded by the

SLANDISC2

SLAN cards for networkproblems and unreachable farend servers. During networkoutages, the SLAN cards willstop TVG/MFC grants or go intoflow control. This causes thePDUs to be queued on the LIMcards, so the majority of discards


ReportsMeasurements


will be pegged on SLANDISC1under these circumstances.

msecsSTPLAN Disabled - Theduration that the STPLAN

SLANDSBLD

screening/copy feature wasdisabled.

peg countSTPLAN Screened - Number ofMSUs that were copied to the

SLANSCRND

STPLAN interface after passinggateway screening.

peg countSTPLAN Transmit - Number ofMSUs sent to the hostdestination.

SLANXMIT



I – indicates incomplete interval;


peg countTCP Connections Failed - Thetotal number of TCP connections

TCPCONNFLD

that have failed on the STPLANinterface.

peg countTCP Receive Error - The totalnumber of TCP segments

TCPRCVERR

received on the STPLANinterface in error.

peg countTCP Reset Sent - The totalnumber of TCP segments sent

TCPRSTSENT

containing the reset (RST) flagon the STPLAN interface.

peg countTCP Segment Received - Thetotal number of TCP segments

TCPSEGRCVD

received on the STPLANinterface.

peg countTCP Segment Sent - The totalnumber of TCP segments senton the STPLAN interface.

TCPSEGSENT

peg countTCP Segment Retransmitted -The total number of TCP

TCPSEGXMT2


ReportsMeasurements


segments retransmitted on theSTPLAN interface.

UI Example Output:

tekelecstp 01-08-23 11:00:11 EST EAGLE 34.0.0 TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON STPLAN REPORT PERIOD: LAST REPORT INTERVAL: 01-08-23 10:30:00 THRU 10:59:59 STPLAN-SYSTOT MEASUREMENTS Measurement data represents an incomplete interval. SLANDSBLD = 0, SLANDISC1 = 0, SLANDISC2 = 0, SLANSCRND = 0, SLANXMIT = 0, ENETALNERR = 0, ENETCRCERR = 0, ENETCOLERR = 0, ENETBUSBSY = 0, ENETOVRERR = 0, ENETOCTXMT = 0, ENETOCTRCV = 0, TCPCONNFLD = 0, TCPSEGRCVD = 0, TCPSEGSENT = 0, TCPSEGXMT2 = 0, TCPRCVERR = 0, TCPRSTSENT = 0, IPHDRERR = 0, IPADDRERR = 0, IPPROTERR = 0; tekelecstp 01-08-23 11:00:12 EST EAGLE 34.0.0 END OF HALF-HOURLY STPLAN-SYSTOT MEASUREMENT REPORT;

FTP Example Output File Name:systot-stplan_19990117_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","STP SYSTEM TOTAL MEASUREMENTS ON STPLAN","LAST","1999-01-17","15:00:00","15:30:00",1<cr><lf><cr><lf>"STATUS","SLANDSBLD","SLANDISC1","SLANDISC2","SLANSCRND","SLANXMIT","ENETALNERR","ENETCRCERR","ENETCOLERR","ENETBUSBSY","ENETOVRERR","ENETOCTXMT","ENETOCTRCV","TCPCONNFLD","TCPSEGRCVD","TCPSEGSENT","TCPSEGXMT2","TCPRCVERR","TCPRSTSENT","IPHDRERR","IPADDRERR","IPPROTERR"<cr><lf>"K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>

Example typical file size:

Table 12: Typical File Size: systot-stplan.csv


header

657 bytes=132+275+250

IDPR SYSTOT Report

Example Commands:

UI: rept-meas:type=systot:enttype=idpr

FTP: rept-ftp-meas:type=systot:enttype=idpr


ReportsMeasurements

Note: The IDPR Measurement Report table for the SYSTOT IDPR report is available as follows.

Table 13: Availability of SYSTOT IDPR Report

Reports supportedon GPLs

DisplayRetentionPeriodReporting modes

OAMHC (withoutIntegratedMeasurements)

UI24 hours30 minutesOn-demand

MCP/OAMHC(with IntegratedMeasurements)

UI24 hours15 or 30 minutesOn-demand

MCP/OAMHCFTP24 hours15 or 30 minutesScheduled/Ondemand

The IDPR Measurement Report is created for IDPR measurements through the entity "idpr."

Table 14: SYSTOT IDPR Measurements



IDPAPTYGTT

A-Party Routing service, but fellthrough to GTT (with or withouthaving attempted SK routingfirst).


IDPAPTYRTD

A-Party Routing service, andwere successfully routed basedon A-Party PPSOPTS routingdata (i.e. routing data associatedwith the RTDB PT assigned tothe A-Party digits).


IDPAPTYSKR

A-Party Routing service, but fellthrough to Service Key Routing,and were successfully routedbased on SK/BCSM PPSOPTSdata (i.e. routing data associatedwith the RTDB PT assigned tothe SK/BCSM entry).

peg countTotal number of IDP/IDPSMSmessages received that matched

IDPBKLCONN


ReportsMeasurements


the blacklist criteria and aCONNECT response wasgenerated.

peg countTotal number of IDP/IDPSMSmessages received that did not

IDPBKLCONT

match the blacklist criteria anda CONTINUE response wasgenerated.

peg countThe total number of MSUsselected for IDPR service which

IDPRMSERR

could not be processed due toerrors in encoding, decoding,formatting, or IDP A-Partyrouting, or IDP SK Routing. Thisregister also includes countwhen IDPRCDPN or IDPRCGPNservice is turned off.

peg countTotal number of MSUs selectedfor IDPR service which fell

IDPRMSFAIL

through to GTT due to (1) nomatch on MSISDN in MNPDB,or (2) match on MSISDN but noassociation to RN or SP forCDPNNP or CGPNNP, (3) nomatch for IDP A-Party Blacklistquery-response criteria or, (4)IDP Blacklist relay resulted infalling through to GTT forrouting, or (5) IDP A-Party or SKRouting resulted in fallingthrough to GTT routing (due tono-match on MSISDN orinsufficient data).

peg countTotal number of MSUs receivedand selected for IDPR service.

IDPRMSRCV

This register includes counts for(1) MSUs that resulted in bothsuccessful and unsuccessfulMNPDB lookups, (2) MSUswhich failed IDPRPreprocessing, (3) when no NPPrule is found for IDPRCDPN &IDPRCGPN service, (4) whenIDPRCDPN or IDPRCGPNservice is turned off.


ReportsMeasurements


IDPRMSRCV = IDPRMSERR +IDPRMSFAIL + IMPRMSSUCC+ Fall-Through case

Note: "Fall-Through case" - AllMSUs that have failed IDPRpre-processing or not havingmatching NPP rule forIDPRCDPN & IDPRCGPNwhich fall through to GTT.

peg countNumber of MSUs selected forIDPR service for which the

IDPRMSSUCC

requested IDPR feature setfunctionalities were executedsuccessfully. This includes pegsto IDPAPTYRTD, IDPSKRTD,IDPBKLCONN, andIDPBKLCONT registers.

peg countTotal number of IDPs that wereselected for Service Key Routing

IDPSKGTT

(without having first gone toA-Party Routing), but fellthrough to GTT.


IDPSKRTD

Service Key Routing (withouthaving first gone to A-PartyRouting), and were successfullyrouted based on SK/BCSMPPSOPTS data.

peg countTotal number of IDP Messagesfor which INPRTG Service action

IDPINPCONN

sent a CONNECT message fromIDPRCDPN service.


IDPINPCONN2

sent a CONNECT message fromIDPRCDPN2 service.


IDPINPCONN3



IDPINPCONN4


ReportsMeasurements




IDPINPCONT

sent a CONTINUE message fromIDPRCDPN service.


IDPINPCONT2

sent a CONTINUE message fromIDPRCDPN2 service.


IDPINPCONT3



IDPINPCONT4



IDPINPRLC

sent a RELEASECALL messagefrom IDPRCDPN service.


IDPINPRLC2

sent a RELEASECALL messagefrom IDPRCDPN2 service.


IDPINPRLC3



IDPINPRLC4


peg countTotal number of IDP Messagesprocessed by INPRTG Serviceaction from IDPRCDPN service.

IDPINPRTG

peg countTotal number of IDP Messagesprocessed by INPRTG Serviceaction from IDPRCDPN2 service.

IDPINPRTG2


ReportsMeasurements



IDPINPRTG3


IDPINPRTG4

peg countTotal number of IDP Messagesprocessed by SKGTARTG

IDPSKGTART

Service action from IDPRCDPNservice.


IDPSKGTART2

Service action from IDPRCDPN2service.


IDPSKGTART3



IDPSKGTART4


peg countTotal number of IDP Messagesprocessed per IDPRCDPNservice.

IDPRCDPN

peg countTotal number of IDP Messagesprocessed per IDPRCDPN2service.

IDPRCDPN2


IDPRCDPN3


IDPRCDPN4

UI Example Output:

> rept-meas:enttype=idpr:type=systot

Command Accepted - Processing

meas 02-06-30 13:01:20 EST EAGLE5 43.0.0-63.46.0


ReportsMeasurements

rept-meas:enttype=idpr:type=systot Command entered at terminal #1.; meas 02-06-30 13:01:20 EST EAGLE5 43.0.0-63.46.0 Measurements Report will be generated.;

meas 02-06-30 13:01:20 EST EAGLE5 43.0.0-63.46.0 TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON IDPR REPORT PERIOD: LAST REPORT INTERVAL: 02-06-30, 12:30:00 THROUGH 12:59:59

IDPR-SYSTOT MEASUREMENTS

These measurements are from 02-06-30, 12:30:00 through 12:59:59. Measurement data represents an incomplete interval. IDPRMSRCV = 0, IDPRMSSUCC = 0, IDPRMSFAIL = 0, IDPRMSERR = 0, IDPAPTYRTD = 0, IDPAPTYSKR = 0, IDPAPTYGTT = 0, IDPSKRTD = 0, IDPSKGTT = 0, IDPBKLCONN = 0, IDPBKLCONT = 0, IDPINPCONN = 0, IDPINPCONN2= 0, IDPINPCONN3= 0, IDPINPCONN4= 0, IDPINPCONT = 0, IDPINPCONT2= 0, IDPINPCONT3= 0, IDPINPCONT4= 0, IDPINPRLC = 0, IDPINPRLC2 = 0, IDPINPRLC3 = 0, IDPINPRLC4 = 0, IDPINPRTG = 0, IDPINPRTG2 = 0, IDPINPRTG3 = 0, IDPINPRTG4 = 0, IDPSKGTART = 0, IDPSKGTART2= 0, IDPSKGTART3= 0, IDPSKGTART4= 0, IDPRCDPN = 0, IDPRCDPN2 = 0, IDPRCDPN3 = 0, IDPRCDPN4 = 0

;

meas 02-06-30 13:01:23 EST EAGLE5 43.0.0-63.46.0 END OF ON-DEMAND IDPR-SYSTOT MEASUREMENT REPORT;

FTP Example Output File Name:systot-idpr_20820706_0445.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""meas","EAGLE5 43.0.0-63.46.0","2082-07-06","04:45:01","EST ","STP SYSTEM TOTAL MEASUREMENTS ON IDPR","LAST","2082-07-06","04:30:00","04:45:00", 1

"STATUS","IDPRMSRCV","IDPRMSSUCC","IDPRMSFAIL","IDPRMSERR","IDPAPTYRTD","IDPAPTYSKR","IDPAPTYGTT","IDPSKRTD","IDPSKGTT","IDPBKLCONN","IDPBKLCONT","IDPINPCONN","IDPINPCONN2","IDPINPCONN3","IDPINPCONN4","IDPINPCONT","IDPINPCONT2","IDPINPCONT3","IDPINPCONT4","IDPINPRLC","IDPINPRLC2","IDPINPRLC3","IDPINPRLC4","IDPINPRTG","IDPINPRTG2","IDPINPRTG3","IDPINPRTG4","IDPSKGTART","IDPSKGTART2","IDPSKGTART3","IDPSKGTART4","IDPRCDPN","IDPRCDPN2","IDPRCDPN3","IDPRCDPN4""I",32,34,36,38,52,54,56,58,60,62,64,76,78,80,82,84,86,88,90,92,94,96,98,100,102,104,106,108,110,112,114,116,118,120,122



Typical file size:


ReportsMeasurements

Table 15: Typical File Size: systot-idpr.csv


SystemHeader

923=214+459+250

SIP SYSTOT Report

Example Commands:

UI: rept-meas:type=systot:enttype=sip

FTP:rept-ftp-meas:type=systot:enttype=sip

Table 16: STP System Total SIP Measurements


peg countThe total number of SIP invitereceived (Including re-transmits)

INVITERCVD

peg countNumber of cancel receivedCANCRCVD

peg countNumber of 1xx responses sentPROVRSPSENT

peg countNumber of 2xx responses sentOKRSPSENT

peg countNumber of 302 responses sentRDRCTSENT

peg countNumber of 4xx responses sentCLNFAILSENT

peg countNumber of 5xx responses sentSRVERRSENT

peg countNumber of SIP invite messagesfor which rxdb lookup was

NPSUCC

successfully performed andRN/ASD was found

peg countNumber of SIP invite messagesfor which rxdb lookup was notperformed

NPBYPASSSUC

peg countNumber of SIP invite messagesfor which rxdb lookup returnedRN not found

INVALIDDN


NPRNNF


ReportsMeasurements

UI Example Output:

tekelecstp 02-01-03 19:06:13 MST EAGLE5 45.0.0-64.49.0 TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON SIP REPORT PERIOD: LAST REPORT INTERVAL: 02-01-03, 18:00:00 through 18:29:59

SIP-SYSTOT MEASUREMENTS

These measurements are from 02-01-03, 18:00:00 through 18:29:59 INVITERCVD = 0, CANCRCVD = 0, PROVRSPSENT= 0, OKRSPSENT = 0, RDRCTSENT = 0, CLNFAILSENT= 0, SRVERRSENT = 0, NPSUCC = 0, NPBYPASSSUC= 0, INVALIDDN = 0, NPRNNF = 0

FTP Example Output File Name:systot-sip_20020212_2200.csv



"tekelecstp","EAGLE5 45.0.0-64.49.0","2013-01-09","21:30:00","MST ","STP SYSTEM TOTAL MEASUREMENTS ON SIP","LAST","2011-01-23","00:30:00","01:00:00",1

"STATUS","INVITERCVD","CANCRCVD","PROVRSPSENT","OKRSPSENT","RDRCTSENT","CLNFAILSENT","SRVERRSENT","NPSUCC","NPBYPASSSUC","INVALIDDN","NPRNNF""K",0,0,0,0,0,0,0,0,0,0,0



Typical file size:

Table 17: Typical File Size: systot-sip.csv


SystemHeader

467 bytes=72+145+250

SFTHROT SYSTOT Report

Example Commands:

FTP:rept-ftp-meas:type=systot:enttype=sfthrot

Table 18: STP System Total SFTHROT Measurements


peg countThe total number of messagesserviced by a particularThrottling GTT Action.

GTTATHTO

peg countThe total number of messagesdiscarded because the Throttling

GTTATHDI


ReportsMeasurements

UnitDescriptionEvent NameGTT Action was in BLOCKEDstate.

FTP Example Output File Name: systot-sfthrot_20150813_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 46.3.0.0.0-66.8.0","8/13/2015","15:30:01","EST ","STP SYSTEM TOTAL MEASUREMENTS ON SFTHROT","LAST","8/13/2015","15:00:00","15:30:00",32<cr><lf>

"STATUS","THROTTLING ACTION","GTTATHTO","GTTATHDI"<cr><lf>"K","sf1",0,0<cr><lf>. . . . .

"K","sf32",0,0<cr><lf>


4 char status + 12 char TA +2 * (6 char data) + 2 = 30 chars

Typical file size:

Table 19: Typical File Size: systot-sfthrot.csv


SystemHeader

1262 bytes=960 bytes+52+250

Component Measurements (COMP)

Component Measurements provides performance data related to links and linksets.

Entity Types: LINK, LNKSET , SCTPASOC, SCTPCARD, UA

Accumulation Interval: 30 minutes


STP Retention Period: 24 hours

Reporting Modes: Scheduled, On-Demand

Accessible Collection Periods: Last, Specific, Active

LINK COMP Report

Certain registers are reported for MTP2, SAAL, IPVL, and IPVHSL classes. These registers aresummarized in Table 20: Registers Reported per LINK CLASS for Component Links.

Note: The LINK COMP Report takes about 3-4 minutes to be generated correctly after a link is deleted.


ReportsMeasurements

Table 20: Registers Reported per LINK CLASS for Component Links

IPVHSL ClassIPVL/IPVLGWClassSAAL ClassMTP2 ClassEvent Name

XXXXDURLKOTG

XXXXECCNGLV1

XXXXECCNGLV2

XXXXECCNGLV3

XECLNKCB

XECLNKXCO

XINCCELLS

XXLMSUOCTRCV

XXLMSUOCTTRN

XXLMSURCV

XXLMSURCVDSC

XXLMSUTRN

XXLMSUTRNDSC

XXXXLNKAVAIL

XM2PLKNIS

XM2PUDMRC

XM2PUDMTR

XM2PUDOCR

XM2PUDOCT

XXXXMSGDISC0

XXXXMSGDISC1

XXXXMSGDISC2

XXXXMSGDISC3

XXXXMSGSRCVD

XMSURETRN

XXXXMSGSRGTT


ReportsMeasurements

IPVHSL ClassIPVL/IPVLGWClassSAAL ClassMTP2 ClassEvent Name

XXXXMSGSTRAN

XXXXMTCEUSG

XXXXMOCTRGTT

XXXXMOCTRCVD

XXXXMOCTTRAN

XXXXNMGWSDSABL

XOCTRETRN

XOUTCELLS

XSDPDURCV

XSDPDURTR

XSDPDUTRN

XXXXTDCNGLV1

XXXXTDCNGLV2

XXXXTDCNGLV3

Command Examples

• UI:

rept-meas:type=comp:enttype=link:loc=xxxx:link=x

rept-meas:type=comp:enttype=link:lsn=ls3

• FTP:

rept-ftp-meas:type=comp:enttype=link

Measurement Events

Table 21: Component Link Measurements


secondsDuration ofLink Unavailable(Outage) - The total time a link

DURLKOTG

was unavailable to MTP level 3for any reason.


ReportsMeasurements


peg countEvent Count for Entering Level1 Link Congestion -

ECCNGLV1

The total number of times thatlink congestion level 1 wasentered.


ECCNGLV2



ECCNGLV3


peg countNumber of times the linkperformed ChangeBack

ECLNKCB

procedures, includingtime-controlled ChangeBacks.

peg countNumber of times the linkperformed Extended

ECLNKXCO

ChangeOver procedure,including time-controlledChangeOvers.

octetsTotal incoming NDC-valid ATMcells on the HSL’s VCL,

INCCELLS

including UI and OAM cells butexcluding idle/unassigned cells.

octetsThe number of octets receivedin large MSUs. This register is

LMSUOCTRCV

pegged in addition toMOCTRCVD when the LargeMSU Support for IP Signalingfeature status is on and a largeMSU is successfully received.

octetsThe number of octetstransmitted in large MSUs. This

LMSUOCTTRN

register is pegged in addition toMOCTTRAN when the LargeMSU Support for IP Signalingfeature status is on and a largeMSU is successfully transmitted.


ReportsMeasurements


peg countThe number of large MSUsreceived. This register is pegged

LMSURCV

in addition to MSURECVD whenthe Large MSU Support for IPSignaling feature status is on anda large MSU is successfullyreceived.

peg countThe number of large MSUsdiscarded in the receive path.

LMSURCVDSC

This can occur when the LargeMSU Support for IP Signalingfeature is not on or when theMSU is larger than 4095 bytes orwhen a routing failure occurs.

peg countThe number of large MSUstransmitted. This register is

LMSUTRN

pegged in addition toMSGSTRAN when the LargeMSU Support for IP Signalingfeature status is on and a largeMSU is successfully transmitted.

peg countThe number of large MSUsdiscarded in the transmit path..

LMSUTRNDSC

secondsLink Available Time - The totaltime the link was available toMTP level 3.

LNKAVAIL

msecM2PA Link Not-in-ServiceDurationThe duration the link

M2PLKNIS

was not in the in-service (INS)state at the M2PA layer (inseconds), i.e., during which thelink was in any of the otherdefined M2PA states (such asIDLE, OOS, AIP, PROVING,ALIGNED READY, orRETRIEVAL).

peg countThe number of M2PA UDMsreceived.

M2PUDMRC

peg countThe number of M2PA User DataMessages (UDMs) transmitted.

M2PUDMTR

octetsThe number of M2PA UDMoctets received.

M2PUDOCR


ReportsMeasurements


octetsThe number of M2PA User DataMessage (UDM) octetstransmitted.

M2PUDOCT

octetsMessage Octets Received -MOCTRCVD

Total number of octets associatedwith Messages received,including those removed forMTP level 2 processing andthose for which retransmissionhas been requested.

• For SAAL, IPVL, IPVHSL,and IPVLGW class linksets -applies to MTP level 3message bytes.

octetsMessage Octets Received forMessages Requiring GTT -

MOCTRGTT

Total number of octets receivedassociated with incomingMessages requiring global titletranslation (GTT), includingoctets removed in MTP level 2processing, e.g., CRC and flag.

• For SAAL class linksets,applies to MTP level 3message bytes.

octetsMessage Octets Transmitted -Total number of octets associated

MOCTTRAN

with Messages transmitted to thefar end. For all linkset classes,this includes octets for MTP level3 SIO and SIF.

• For MTP2 class linksets,octets included are thoseassociated with Messagestransmitted ANDacknowledged by level 2, aswell as any retransmittedMessages. Additional octetsincluded are MTP level 2 flag,BSN/BIB, FSN/BIB, LI, andCRC octets.

• For SAAL and IPVHSL classlinksets, octets are not


ReportsMeasurements


included until the Message isacknowledged by level 2.

• For IPVL and IPVLGW classlinks, octets are not includeduntil the Message istransmitted by level 2. ForIPVLGW class linksets, SNMs(Messages with SI=0) areNOT included.

peg countFor ANSI links: Priority 0 MSUsDiscarded Due to Congestion -

MSGDISC0

The total number of priority 0MSUs discarded due tocongestion (any level).

• For SAAL class links, appliesto MTP level 3 messages .

• For ITU links, the totalnumber of MSUs discardeddue to congestion.

Note: The EAGLE only supportsthis one ITU discard counter.When the discard threshold isreached, all MSUs are discardedand counted in this register.Prior to the discard thresholdbeing reached, no MSUs arediscarded.

Note: The MSUs or Messagesmay be discarded on thetransmit/outbound link, whichindicates congestion via theECCNGLVLx or TDCNGLVxregisters or it may appear oninbound links routing traffic tothose congested links. The latterwill not indicate eitherECCNGLVLx or TDCNGLVx.


MSGDISC1




ReportsMeasurements


For ITU links: this register is notapplicable.



MSGDISC2






MSGDISC3




Note: The MSUs or Messagesmay be discarded on thetransmit/outbound link, whichindicates congestion via the


ReportsMeasurements


ECCNGLVLx or TDCNGLVxregisters or it may appear oninbound links routing traffic tothose congested links. The latterwill not indicate eitherECCNGLVLx or TDCNGLVx.

peg countMSUs Received -MSGSRCVD

Total number of MSUs received,including those for whichretransmission has beenrequested.

• For SAAL, IPVL, IPVHSL,and IPVLGW class links,applies to MTP level 3messages.

peg countMSUs Received Requiring GTT-

MSGSRGTT

Total number of incoming MSUsrequiring global title translation(GTT).

• For SAAL class links, appliesto MTP level 3 messages.

peg countMSUs Transmitted -MSGSTRAN

Total number of MSUstransmitted to the far-end,including retransmissions.

• For MTP2 class links, MSUstransmitted ANDacknowledged by level 2.

• For SAAL, IPVL, IPVHSL,and IPVLGW class linksets,MTP level 3 messages offeredfor transmission after anyrequired conversion fromtheir respective M2PA,M3UA, or SUA formats.

peg countMSUs Retransmitted - Numberof MSUs retransmitted from theSTP on this link.

MSURETRN

• For MTP2 class links, MSUsretransmitted by level 2.


ReportsMeasurements


secondsLink Maintenance Usage - Thetotal time the link was manually

MTCEUSG

made unavailable to MTP level3.

This includes locally blocked(LPO), locally inhibited, orde-activated.

Note: MTCEUSG may be lessthan DURLKOTG due to linkrecovery time following canc-slk,act-slk command sequence

peg countNumber of Times GWSDisabled - The number of times

NMGWSDSABL

that the GWS subsystem on theLIM card supporting the linkwas disabled because of a receiveoverload condition on the card.When this occurs, the GWSsubsystem is disabled for alllinks on the card and this registeris pegged for all links on the cardregardless of whether GWS isenabled for that link. Gatewayscreening is disabled on the cardto allow recovery from thereceive overload condition andis re-enabled when the receiveoverload condition abates.

octetsMSU Octets Retransmitted -The total number of MSU octets

OCTRETRN

retransmitted. This register isNOT reported for HSLs.

peg countTotal outgoing NDC-valid ATMcells on the HSL’s VCL,

OUTCELLS


peg countSSCOPSDPDUs Received - Thenumber of SSCOP sequenced

SDPDURCV

data (SD) PDUs that werereceived during the indicatedinterval.

peg countSSCOP SDPDUs Retransmitted- The number of SSCOP SD

SDPDURTR

PDUs that were retransmitted,


ReportsMeasurements


based on an accumulated countof such retransmissionsconveyed to layer management.

peg countSSCOP SD PDUs Transmitted- The number of SSCOP SD

SDPDUTRN

PDUs that were transmitted,including retransmissions.

statusIndication of Data Validity:STATUS

K indicates good dataI indicates incompleteintervalN indicates data not current

secondsTotal Duration of Level 1 LinkCongestion -

TDCNGLV1

The total time the link was inlevel 1 congestion.


TDCNGLV2



TDCNGLV3


UI Output Examples

• rept-meas:type=comp:enttype=link:loc=xxxx:link=x

tekelecstp 12-03-20 09:24:26 EST EAGLE5 44.0.0 TYPE OF REPORT: COMPONENT MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-03-20, 08:30:00 THROUGH 08:59:59

LINK-COMP MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

These measurements are from 12-03-20, 08:30:00 through 08:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MTCEUSG = 0, DURLKOTG = 1800, MSGSRGTT = 0, MOCTRGTT = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, LNKAVAIL = 0, NMGWSDSABL = 0, LMSUTRN = 0, LMSURCV = 0, LMSUOCTTRN = 0, LMSUOCTRCV = 0, LMSUTRNDSC = 0, LMSURCVDSC = 0


ReportsMeasurements

;


LINK-COMP MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

These measurements are from 12-03-20, 08:30:00 through 08:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, MTCEUSG = 0, DURLKOTG = 1800, MSGSRGTT = 0, MOCTRGTT = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, LNKAVAIL = 0, NMGWSDSABL = 0

;


LINK-COMP MEASUREMENTS: LOC: 1105, LINK: A , LSN: ssedcm1 (IPVHSL)

These measurements are from 12-03-20, 08:30:00 through 08:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MTCEUSG = 0, DURLKOTG = 1800, MSGSRGTT = 0, MOCTRGTT = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, LNKAVAIL = 0, NMGWSDSABL = 0, LMSUTRN = 0, LMSURCV = 0, LMSUOCTTRN = 0, LMSUOCTRCV = 0, LMSUTRNDSC = 0, LMSURCVDSC = 0, M2PUDMTR = 0, M2PUDOCT = 0, M2PUDMRC = 0, M2PUDOCR = 0, M2PLKNIS = 1800, ECLNKCB = 0, ECLNKXCO = 0

;


LINK-COMP MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)

These measurements are from 12-03-20, 09:00:00 through 09:29:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MTCEUSG = 0, DURLKOTG = 1800, MSGSRGTT = 0, MOCTRGTT = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, LNKAVAIL = 0, NMGWSDSABL = 0, OUTCELLS = 1565, INCCELLS = 0, SDPDUTRN = 0, SDPDURCV = 0, SDPDURTR = 0


ReportsMeasurements

;


LINK-COMP MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)

These measurements are from 12-03-20, 09:00:00 through 09:29:59. MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, MTCEUSG = 1800, DURLKOTG = 1800, MSGSRGTT = 0, MOCTRGTT = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, LNKAVAIL = 0, NMGWSDSABL = 0

;

• rept-meas:type=comp:enttype=link:lsn=ls3:period=active

tekelecstp 12-02-10 05:38:34 EST EAGLE5 44.0.0 TYPE OF REPORT: COMPONENT MEASUREMENTS ON LINK REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-10, 05:30:00 THROUGH CURRENT

LINK-COMP MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, MTCEUSG = 0, DURLKOTG = 515, MSGSRGTT = 0, MOCTRGTT = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, LNKAVAIL = 0, NMGWSDSABL = 0

;

FTP Output Examples

Table 22: COMP LINK Column Headers

DescriptionField Name

Linkset nameLSN

Card locationLOC

Link portLINK

Link typeLNKTYPE

FTP Example Output File Name: comp-link_20101004_1000.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-10","05:39:32","EST ","COMPONENT MEASUREMENTS ON LINK","LAST","2012-02-10","05:00:00","05:30:00",5<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","MSGSTRAN","MSGSRCVD","MSURETRN","OCTRETRN","MOCTTRAN","MOC

TRCVD","MTCEUSG","DURLKOTG","MSGSRGTT","MOCTRGTT","TDCNGLV1","TDCNGLV2","TDCNGLV3","ECCNGLV1","ECCNGLV2","ECCNGLV3","MSGDISC0","MSGDISC1","MSGDISC2" "MSGDISC3","LNKAVAIL","NMGWSDSABL","OUTCELLS", "INCCELLS","SDPDUTRN","SDPDURCV","SDPDURTR","LMSUTRN","LMSURCV","LMSUOCTTRN","LMSUOCTRCV","LMSUTRNDSC","LMSURCVDSC","M2PUDMTR","M2PUDOCT","M2PUDMRC","M2PUDOCR","M2PLKNIS","ECLNKCB","ECLNKXCO"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",0,0,0,0,0,0,0,192,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",0,0,0,0,0,0,192,192,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",0,0,0,0,0,0,0,192,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm1","1105","A ","IPVHSL",0,0,0,0,0,0,0,192,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,192,0,0<cr><lf>"K","saal","1112","A ","SAAL",0,0,0,0,0,0,192,192,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 13 char LSN + 7 char LOC + 6 char LINK + 12 char LNKTYPE + 40*(6 char data) +2 = 284 chars

Table 23: Typical File Size: comp-link.csv

File Size=Report data+Reportheader+

Systemheader

142,736 bytes=142,000+486+250

LNKSET COMP Report

Certain registers are reported for MTP2, SAAL, IPVL, and IPVHSL classes. These registers aresummarized in the following table.

Table 24: Registers Reported Per LINKSET CLASS

IPVHSLIPVLSAALMTP2Register Name

XXXXGTTMSCNVTD

XINCCELLS

XXXXMSGWSDSLIM


ReportsMeasurements

IPVHSLIPVLSAALMTP2Register Name

XXXXMSGSRCVD

XXXXMSGSRGTT

XXXXMSGSTRAN

XXXXMTPMSCNVTD

XXXXMOCTRGTT

XXXXMOCTRCVD

XXXXMOCTTRAN

XOUTCELLS

XXXXSCCPLOOP

XSDPDURCV

XSDPDURTR

XSDPDUTRN

XXXXTDLSINAC

XXXXZTTMAPI

XXXXZTTMAPO

Command Examples

• UI

rept-meas:type=comp:enttype=lnkset:lsn=xy212

• FTP:

rept-ftp-meas:type=comp:enttype=lnkset

Measurement Events

Table 25: Component Linkset Measurements


peg countTotal GT Routed SCCP MSUsConverted.

GTTMSCNVTD

peg countTotal incoming NDC-valid ATMcells on the HSL’s VCL,

INCCELLS


ReportsMeasurements



octetsMessage Octets Received forMessages RequiringGTT -

MOCTRGTT

Total number of octets receivedassociated with incomingMessages requiring global titletranslation (GTT), includingoctets removed in MTP level 2processing, e.g. CRC and flag.

• For SAAL class linksets,applies to MTP level 3message bytes.





MOCTTRAN

with Messages transmitted to thefar-end. For all linkset classes,this includes octets for MTP level3 SIO and SIF.


• For SAAL and IPVHSL classlinksets, octets are notincluded until the Message isacknowledged by level 2.


ReportsMeasurements



peg countMSUs Received - Total numberof MSUs received, including

MSGSRCVD

those for which retransmissionhas been requested.

• For SAAL, IPVL, IPVHSL,and IPVLGW class linksets -applies to MTP level 3messages

peg countMSUs Received Requiring GTT- Total number of incoming

MSGSRGTT

MSUs requiring global titletranslation (GTT).

• For SAAL class linksets,applies to MTP level 3messages.





peg countMSUs lost due to GatewayScreening being Disabled on a

MSGWSDSLIM

LIM - These MSUs werediscarded because the gatewayscreening function was disabled.Gateway screening may havebeen disabled because the screen


ReportsMeasurements


set was unavailable. Thiscondition can also occur if thescreen set data is invalid orgateway screening discard is on.

peg countTotal MTP Routed SCCP MSUsConverted.

MTPMSCNVTD

peg countTotal outgoing NDC-valid ATMcells on the HSL’s VCL,

OUTCELLS


peg countThe total number of times that aGTT translation matched a Point

SCCPLOOP

Code in the STP’s loopset entriesresulting in either a notify ordiscard of an SCCP message.

This register is reported as zeroin ACTIVE, “period=active”,measurement linkset reports.

peg countSSCOP SD PDUs received - Thenumber of SSCOP SD PDUs that

SDPDURCV

were received during theindicated interval.

peg countSSCOP SD PDUs Retransmitted- The number of SSCOP

SDPDURTR

sequenced Data PDUs that wereretransmitted, based on anaccumulated count of suchretransmissions conveyed to LM.

peg countSSCOP SD PDUs Transmitted- The number of SSCOP

SDPDUTRN

sequenced Data (SD) PDUs thatwere transmitted, includingretransmissions.



secondsTotal Duration of Link SetInactivity - The total time that

TDLSINAC

all links in the linkset were


ReportsMeasurements


unavailable to MTP level 3,regardless if they were madeunavailable manually orautomatically.

peg countTranslation Type mappingtranslation performed - MSUs

ZTTMAPI

received on the gateway linkset- The total number of TranslationType Mapping translationsperformed for Message SignalUnits (MSUs) received on thegateway link set (i.e., incoming).

peg countTranslation Type MappingTranslation Performed - MSUs

ZTTMAPO

Transmitted on the GatewayLink Set - The total number ofTranslation Type Mappingtranslations performed forMessage Signal Units(MSUs)transmitted on the gateway linkset (i.e., outgoing).

UI Output Examples

• rept-meas:type=comp:enttype=lnkset:lsn=xxxx

tekelecstp 12-02-10 04:37:20 EST EAGLE5 44.0.0 TYPE OF REPORT: COMPONENT MEASUREMENTS ON LNKSET REPORT PERIOD: LAST REPORT INTERVAL: 12-02-10, 04:00:00 THROUGH 04:29:59

LNKSET-COMP MEASUREMENTS: ipsg (IPVL)

These measurements are from 12-02-10, 04:00:00 through 04:29:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MSGSRGTT = 0, MOCTRGTT = 0, TDLSINAC = 0, MSGWSDSLIM = 0, ZTTMAPO = 0, ZTTMAPI = 0, MTPMSCNVTD = 0, GTTMSCNVTD = 0, SCCPLOOP = 0

;


LNKSET-COMP MEASUREMENTS: mtp2 (MTP2)

These measurements are from 12-02-10, 04:00:00 through 04:29:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MSGSRGTT = 0, MOCTRGTT = 0,


ReportsMeasurements

TDLSINAC = 0, MSGWSDSLIM = 0, ZTTMAPO = 0, ZTTMAPI = 0, MTPMSCNVTD = 0, GTTMSCNVTD = 0, SCCPLOOP = 0

;


LNKSET-COMP MEASUREMENTS: ssedcm1 (IPVHSL)


;


LNKSET-COMP MEASUREMENTS: saal (SAAL)

These measurements are from 12-03-20, 08:30:00 through 08:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MSGSRGTT = 0, MOCTRGTT = 0, TDLSINAC = 0, MSGWSDSLIM = 0, ZTTMAPO = 0, ZTTMAPI = 0, OUTCELLS = 1565, INCCELLS = 0, SDPDUTRN = 0, SDPDURCV = 0, SDPDURTR = 0, MTPMSCNVTD = 0, GTTMSCNVTD = 0, SCCPLOOP = 0

;


LNKSET-COMP MEASUREMENTS: hcmimt1 (MTP2-UNCH)


;

• rept-meas:type=comp:enttype=lnkset:lsn=xxxx:period=active

tekelecstp 12-02-10 04:44:15 EST EAGLE5 44.0.0 TYPE OF REPORT: COMPONENT MEASUREMENTS ON LNKSET REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-10, 04:30:00 THROUGH CURRENT


ReportsMeasurements

LNKSET-COMP MEASUREMENTS: mtp2 (MTP2)

MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, MSGSRGTT = 0, MOCTRGTT = 0, TDLSINAC = 0, MSGWSDSLIM = 0, ZTTMAPO = 0, ZTTMAPI = 0, MTPMSCNVTD = 0, GTTMSCNVTD = 0, SCCPLOOP = 0

;

FTP Output Examples

Table 26: COMP LINKSET Column Headers

DescriptionFieldName

Linksetname

LSN

Link typeLNKTYPE

FTP Example Output File Name: comp-lnkset_20101004_1000.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-10","04:45:24","EST ","COMPONENT MEASUREMENTS ON LNKSET","LAST","2012-02-10","04:00:00","04:30:00",5<cr><lf><cr><lf>"STATUS","LSN","LNKTYPE","MSGSTRAN","MSGSRCVD","MOCTTRAN","MOCTRCVD","MSGSRGTT","MOCTRGTT","TDLSI

NAC","MSGWSDSLIM","ZTTMAPO","ZTTMAPI","OUTCELLS","INCCELLS","SDPDUTRN","SDPDURCV","SDPDURTR","MTPMSCNVTD","GTTMSCNVTD","SCCPLOOP"<cr><lf>"K","mtp2","MTP2",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","IPVL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm1","IPVHSL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","saal","SAAL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","hcmimt1","MTP2-UNCH",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 13 char LSN + 12 char LKNTYPE + 18*(6 char data) + 2 = 139 chars

For a report of 500 linksets, typical file size is:

Table 27: Typical File Size: comp-lnkset.csv


Systemheader

69,979 bytes=69,500+229+250


ReportsMeasurements

SCTPASOC COMP Report

The per association SCTP layer measurements and reports are shown below.

Command Examples

• UI: rept-meas:type=comp:enttype=sctpasoc:aname=assoc1

• FTP: rept-ftp-meas:type=comp:enttype=sctpasoc

Measurement Events

Table 28: Component SCTPASOC Measurements


msecSCTP Association MaximumObserved Retransmission

ASMAXRTO

Timeout - The maximumobserved value of the SCTP statevariable Retransmission Timeout(RTO) in milliseconds (ms) forSCTP packets transmitted (butnot retransmitted) to the remotepeer endpoint’s destinationtransport address during themeasurement interval.

peg countSCTP Aborted Associations -The number of times that SCTP

ASOCABTD

associations have made a directtransition to the CLOSED statefrom any state using theprimitive “Abort” (AnyState--Abort--> CLOSED), conveyingan ungraceful termination of theassociation.

peg countSCTP Association Shutdowns- The number of times that SCTP

ASOCSHTD

associations have made a directtransition to the CLOSED statefrom either theSHUTDOWN-SENT state or theSHUTDOWN-ACK-SENT state,conveying graceful terminationof the association.

peg countSCTP Control Chunks Received- The number of SCTP control

CNTLCHKR


ReportsMeasurements


chunks received from the remotepeer (excluding duplicates).

CNTLCHKR register excludesinitial SCTP association set-upmessages (INIT andCOOKIE-ECHO).

peg countSCTP Control Chunks Sent -The number of SCTP control

CNTLCHKS

chunks sent to the remote peer(excluding retransmissions),including ABORT messages,after an association has beenformed and the association ID isknown (see SCPKTRCV andSCPKTSNT).

peg countNumber of SCTP DATA chunksreceived from the remote SCTP

DATCHKRC

peer (excluding duplicates anddiscards).

peg countNumber of SCTP DATA chunkssent to the remote SCTP peer(excluding retransmissions).

DATCHKSN

secondsDuration the association was notin the Established state.

DURASNEST

peg countNumber of times the associationtransitioned out of theEstablished state.

ECASNEST

peg countSCTP Gap AcknowledgementsReceived - The number of Gap

GAPACKSR

Acknowledgement blocks inSelective Acknowledgement(SACK) control chunks receivedfrom the remote SCTP peer,indicating gaps in the peer’sreceived subsequences of DATAchunks as represented by theirTransport Sequence Numbers(TSNs). (The inclusion of thismeasurement is intended toallow network personnel toassess the message-deliveryperformance of the IPVHSLrelative to gap acknowledgmentlimits, if used as performance


ReportsMeasurements


criteria for link proving andin-service monitoring.)

peg countSCTP Ordered Data ChunksReceived - The number of SCTP

ORDCHKRC

ordered data chunks receivedfrom the remote peer (excludingduplicates).

peg countSCTP Ordered Data ChunksSent - The number of SCTP

ORDCHKSN

ordered data chunks sent to theremote peer (excludingretransmissions).

peg countSCTP Association PeerEndpoint Failures - The number

PEERFAIL

of peer endpoint failuredetection events for theassociation as triggered by thecrossing of threshold theassociation maximumretransmissions.

peg countSCTP AssociationRetransmitted Chunks - The

RTXCHNKS

number of SCTP data chunksretransmitted to the remoteSCTP peer. When T3-rtx expires,the DATA chunks that triggeredthe T3 timer will be re-sentaccording with theretransmissions rules. EveryDATA chunk that was includedin the SCTP packet that triggeredthe T3-rtx timer must be addedto the value of this counter.

octetsSCTP Packet Octets Received -The number of octets comprising

SCOCTRCV

valid SCTP packets receivedfrom the remote peer after anassociation has been formed.

octetsSCTP Packet Octets Sent - Thetotal number of octets

SCOCTSNT

comprising SCTP packetssubmitted to the IP layer fortransmittal to the remote peer fora specific association.


ReportsMeasurements


peg countSCTP Packets Received - Thetotal number of SCTP packets

SCPKTRCV

received from the remote peerthat had a valid checksum.Duplicates are included.

SCPKTRCV register excludes thepegging of SCTP Packetsreceived when the association IDis unknown (that is, theassociation parameter "OPEN"has value "NO" for all the linksconfigured on the card; theassociation ID is known whenINITs are received for openserver-mode associations or it isestablished). Also, excludespegging of ABORT messages.

peg countSCTP Packets Sent - The totalnumber of SCTP packets sent to

SCPKTSNT

the remote peer, i.e., submittedby the local SCTP instance to theIP layer for transmission.Retransmissions are included.

The SCPKTSNT register can bepegged as either per card or perassociation. Association totalsexclude initial SCTP associationset-up messages (INIT,INIT-ACK, COOKIE ECHO, andCOOKIE-ACK) and ABORTmessages if the association ID isknown (the association ID isknown when INITs are receivedfor open server-modeassociations or it is established).




ReportsMeasurements

UI Output Examplesrept-meas:type=comp:enttype=sctpasoc:aname=assoc1

stdcfg2b 07-12-31 01:00:04 EST UNKNOWN 38.0.0-XX.XX.0 TYPE OF REPORT: COMPONENT MEASUREMENTS ON SCTPASOC REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:30:00 THRU 00:59:59

SCTPASOC-COMP MEASUREMENTS: ASSOC: assoc1

These measurements are from 07-12-31, 00:30:00 through 00:59:59. ECASNEST = 0, DURASNEST = 0, DATCHKSN = 0, RTXCHNKS = 0, DATCHKRC = 0, SCPKTSNT = 20, SCPKTRCV = 20, SCOCTSNT = 0, SCOCTRCV = 0, CNTLCHKS = 400, ORDCHKSN = 400, CNTLCHKR = 0, ORDCHKRC = 0, GAPACKSR = 0, ASOCABTD = 0, ASOCSHTD = 0, PEERFAIL = 0, ASMAXRTO = 0,

FTP Output Examples

Table 29: COMP SCTPASOC Column Headers


AssociationASSOC

FTP Example Output File Name:comp-sctpasoc_20071115_1200.csv

FTP Example Output File Format (showing optional 15 minute interval):

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"ipmeas","UNKNOWN ??.?.?-58.21.0","2007-08-17","19:30:03","****","COMPONENT MEASUREMENTS ON SCTPASOC","LAST","2007-08-17","19:15:00","19:30:00",3<cr><lf>"STATUS","ASSOC","ECASNEST","DURASNEST","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","GAPACKSR","ASOCABTD","ASOCSHTD","PEERFAIL","ASMAXRTO"<cr><lf>"K","A1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","A1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","A1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 18 char association + 18*(6 char data) + 2 = 132 char

For a report of 1000 associations, the typical file size is:

Table 30: Typical File Size: comp-sctpasoc.csv


Systemheader

132425 bytes=132000+175+250


ReportsMeasurements

SCTPCARD COMP Report

The per card SCTP layer measurements and reports are shown below.

Command Examples

• UI: rept-meas:type=comp:enttype=sctpcard:loc=1204

• FTP: rept-ftp-meas:type=comp:enttype=sctpcard

Measurement Events

Table 31: Component SCTPCARD Measurements



ASOCABTD



ASOCSHTD



CNTLCHKR

chunks received from the remotepeer (excluding duplicates). Noregister will be pegged if amessage intended for anassociation is received and thatassociation is in the CLOSEDstate.


CNTLCHKS

chunks sent to the remote peer(excluding retransmissions),


ReportsMeasurements


including chunks for which anassociation has not been formed.


DATCHKRC



DATCHKSN


ORDCHKRC



ORDCHKSN



RTXCHNKS



SCOCTRCV

valid SCTP packets receivedfrom the remote peer, includingpackets for which an associationhas not yet been formed.


SCOCTSNT

comprising SCTP packetssubmitted to the IP layer fortransmittal to the remote peer,


ReportsMeasurements


including packets for which anassociation has not yet beenformed.


SCPKTRCV


SCPKTRCV register excludes thepegging of SCTP Packetsreceived when no instance existson the card for any of theassociations , i.e., the associationparameter "OPEN" has value"NO" for all the associationsconfigured on the card. Also,excludes pegging of set upmessages (INIT andCOOKIE-ECHO) that are part ofassociation establishmentprocedure. (See UNASCTPKregister.)

peg countSCTP Packets Received WithChecksum ErrorThe number of

SCPKTRER

SCTP packets received fromremote peers with an invalidchecksum.


SCPKTSNT


SCPKTSNT register excludesinitial SCTP association set-upmessages (INIT-ACK andCOOKIE-ACK). For M2PAassociation INIT packet is neverpegged.




ReportsMeasurements


peg countUnassociated (Out-of-the-Blue)SCTP PacketsThe number of

UNASCTPK

“out-of-the-blue” SCTP packetsreceived by the host, i.e., SCTPpackets correctly formed withthe correct checksum value, butfor which the receiver (localSCTP) was not able to identifythe association to which thepacket belongs.

UNASCTPK register includesthe pegging of SCTP Packetsreceived when no instance existson the card for any of theassociations, i.e., the associationparameter "OPEN" has value"NO" for all the associationsconfigured on the card. (SeeSCPKTRCV register).

UI Output Examples

stdcfg2b 07-12-31 01:00:04 EST UNKNOWN 47 TYPE OF REPORT: COMPONENT MEASUREMENTS ON SCTPCARD REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:30:00 THRU 00:59:59

SCTPCARD-COMP MEASUREMENTS: LOC: 1204

These measurements are from 07-12-31, 00:30:00 through 00:59:59. DATCHKSN = 0, RTXCHNKS = 0, DATCHKRC = 0, SCPKTSNT = 20, SCPKTRCV = 20, SCPKTRER = 0, UNASCTPK = 0, SCOCTSNT = 0, SCOCTRCV = 0, CNTLCHKS = 400, ORDCHKSN = 400, CNTLCHKR = 0, ORDCHKRC = 0, ASOCABTD = 0, ASOCSHTD = 0

FTP Output Examples

Table 32: COMP SCTPCARD Column Header


LocationLOC

FTP Example Output File Name: comp-sctpcard_20071115_1200.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>


ReportsMeasurements

"tekelecstp",”38.0.0-XX.XX.0”,”2007-12-31”,"12:11:37","EST","COMPONENT MEASUREMENTS ON SCTPCARD","LAST",”2007-12-31”,"11:45:00","12:00:00",3<cr><lf><cr><lf>"STATUS","LOC","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCPKTRER","UNASCTPK","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","ASOCABTD","ASOCSHTD"<cr><lf>"K","1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 7 char location + 15*(6 char data) + 2 = 103 chars

For a report of 80 cards, the typical file size is:

Table 33: Typical File Size: comp-sctpcard.csv


Systemheader

8650 bytes=8240+160+250

UA COMP Report

The per Application Server/Association UA layer measurements and reports are shown below.

Command Examples

• UI: rept-meas:type=comp:enttype=ua:asname=appsrvr1:aname=assoc1

• FTP: rept-ftp-meas:type=comp:enttype=ua

Measurement Events

Table 34: Component UA Measurements


peg countFor M3UA, this registerrepresents the number of DATA

RXDATAMS

messages received from the ASP.For SUA, this register representsthe total of CLDT and CLDRmessages received from the ASP.

octetsFor M3UA, this registerrepresents the number of DATA

RXDATAOC

octets received from the ASP. ForSUA, this register represents thetotal of CLDT and CLDR octetsreceived from the ASP.


ReportsMeasurements


peg countNumber of messages receivedwith multiple routing contexts

RXMLRCMS

(always pegged against thedefault AS).



peg countTXDATAMS • For M3UA, this registerrepresents the number ofDATA messages sent to theASP.

• For SUA, this registerrepresents the total of CLDTand CLDR messages sent tothe ASP.

octetsTXDATAOC • For M3UA, this registerrepresents the number ofDATA octets sent to the ASP.

• For SUA, this registerrepresents the total of CLDTand CLDR octets sent to theASP.

peg countTotal ASPM messages receivedfrom the ASP (including ASPSMand ASPTM messages).

UAASPMRX

peg countTotal ASPM messages sent to theASP (including ASPSM andASPTM messages).

UAASPMTX

peg countThe number of times the ASPtransitioned out of theASP-Active state.

UAASPNAC

secondsThe duration that the ASP wasnot in the ASP-Active state.

UAASPNAT

peg countThe number of times anAS-ASSOC experienced

UACNGCNT

congestion (this may include theAS entering congestion as aresult of the ASSOC enteringcongestion).


ReportsMeasurements


secondsThe duration that an AS-ASSOCexperienced congestion (this

UACNGTIM

may include the AS enteringcongestion as a result of theASSOC entering congestion).

peg countTotal MGMT messages receivedfrom the ASP.

UAMGMTRX

peg countTotal MGMT messages sent tothe ASP.

UAMGMTTX

peg countTotal Network Managementoctets received from the ASP -

UANMOCTR

The total number of non-DATAUA octets received from the ASP(i.e., sum of the ASPM, ASPTM,SSNM, MGMT, and RKM).

peg countTotal Network Managementoctets sent to the ASP - The total

UANMOCTT

number of non-DATA UA octetssent to the ASP (i.e., sum of theASPM, ASPTM, SSNM, MGMT,and RKM).

peg countTotal Network Managementmessages received from the

UANMMSGR

ASP - The total number ofnon-DATA UA messagesreceived from the ASP (i.e., sumof the ASPM, ASPTM, SSNM,MGMT, and RKM).

peg countTotal Network Managementmessages sent to the ASP - The

UANMMSGT

total number of non-DATA UAmessages sent to the ASP (i.e.,sum of the ASPM, ASPTM,SSNM, MGMT, and RKM).

peg countTotal SSNM messages receivedfrom the ASP.

UASSNMRX

peg countTotal SSNM messages sent to theASP.

UASSNMTX


ReportsMeasurements

UI Output Examples

stdcfg2b 07-12-31 01:00:04 EST UNKNOWN 38.0.0-XX.XX.0 TYPE OF REPORT: COMPONENT MEASUREMENTS ON UA REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:30:00 THRU 00:59:59

UA-COMP MEASUREMENTS: AS: appsrvr1 ASSOC: assoc1

These measurements are from 07-12-31, 00:30:00 through 00:59:59. RXDATAMS = 100, RXDATAOC = 4000, TXDATAMS = 200, TXDATAOC = 8000, UANMMSGT = 0, UANMOCTT = 0, UANMMSGR = 0, UANMOCTR = 0, UAASPMTX = 0, UAASPMRX = 0, UASSNMTX = 0, UASSNMRX = 0, UAMGMTTX = 0, UAMGMTRX = 0, UACNGCNT = 0, UACNGTIM = 0, UAASPNAC = 0, UAASPNAT = 0, RXMLRCMS = 0

;

FTP Output Examples

Table 35: COMP UA Column Headers


Application servername

AS

Association nameASSOC

FTP Example Output File Name: comp-ua_20071115_1200.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp",”38.0.0-XX.XX.0”,”2007-12-31”,"12:11:37","EST","COMPONENT MEASUREMENTS ON UA","LAST",”2007-12-31”,"11:45:00","12:00:00",3<cr><lf><cr><lf>"STATUS","AS","ASSOC","RXDATAMS","RXDATAOC","TXDATAMS","TXDATAOC","UANMMSGT","UANMOCTT","UANMMSGR","UANMOCTR","UAASPMTX","UAASPMRX","UASSNMTX","UASSNMRX","UAMGMTTX","UAMGMTRX","UACNGCNT","UACNGTIM","UAASPNAC","UAASPNAT","RXMLRCMS"<cr><lf>"K","as1101","a1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","as1102","a1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","as1103","a1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 15 char AS + 15 char ASSOC + 19*(6 char data) + 2 = 150 chars

For a report of 1000 AS/ASSOC pairs, typical file size is:


ReportsMeasurements

Table 36: Typical File Size: comp-ua.csv


Systemheader

150530 bytes=150000+280+250

Network Management Measurements (NM)

Network Management Reports provide measurement data on STP traffic, Global Title Translations,and MTP Network Management.

Entity Types:STP, Lnkset, and Link


STP Retention Period: 5 minutes

Reporting Mode: Scheduled, On-demand, SEAS autonomous

Accessible Collection Period: Last (STP, LINK, LNKSET), Active (LINK, LNKSET)

STP NM Report

enttype=stp

Example Commands:

UI: rept-meas:type=nm:enttype=stpFTP: rept-ftp-meas:type=nm:enttype=stp

Table 37: Network Management STP Measurements



GTTPERFD


Sometimes, GTTPERFD indicatesthe total number of global titletranslations (GTTs) performedon MSUs that successfullycompleted GTT, because severalGTTs may happen for the sameMSU. One scenario where


ReportsMeasurements


multiple GTTs occur for an MSUoccurs is when the ANSI/ITUSCCP Conversion Feature isactivated. In this case, the countfor GTTPERFD can be doublewhat it would be without thefeature, although the number ofMSUs received by the EAGLEdid not change.


GTTUN0NS

Address of Such Nature – Totalnumber of times that thespecified translation type in anMSU was not supported by theSTP or the form of the GTT wasincorrect for the giventranslation type.


GTTUN1NT

This Address – Number of timesthat a match for the global titlecould not be found in thetranslation table.

peg countMSUs Returned – Total numberof IDP messages returned to

MSIDPMATCH

originating MSC. Thesemessages bypass the prepaidengine since it has beendetermined that they meet thecriteria for subscribers withunlimited prepaid calling plan.

peg countMSUs Relayed - Total numberof IDP messages relayed to theirdestination.

MSIDPNOMCH

peg countMSUs Rcvd – Invalid DPC - Thenumber of MSUs received and

MSINVDPC


peg countMSUs Discarded – InvalidSIF -Number of MSUs that have been

MSINVSIF



ReportsMeasurements


peg countMSUs Rcvd – InvalidDPC -Number of MSUs received and

MSINVDPC


peg countMSUs Discarded – InvalidLink- Number of MSUs discarded

MSINVLNK


peg countMSUs Rcvd – Invalid ServiceIndicator Octet (SIO) -

MSINVSIO

Number of MSUs received anddiscarded because the servicerequested in the service indicatoroctet (SIO) was not supported bythe STP.

peg countMSUs Discarded – InvalidSLC- Number of MSUs discarded

MSINVSLC

because of an invalid SLC codein the ECO/COO.

peg countMSUs Discarded –InaccessibleDPC - The total

MSNACDPC

number of MSUs discardedbecause of an inaccessible DPC.

peg countMSUs Discarded – RoutingFailure - Number of MSUs

MSSCCPFL

discarded due to a routingfailure.

peg countMSUs Discarded –GatewayScreening -

MSUDSCRD

The total number of MSUs thatfailed gateway screening andhave been discarded.

peg countMSUs Discarded – Level2/Level 3 Queue Full -

MSULOST1

Number of MSUs discardedbecause the level 2 to level 3queue was full.

peg countMSUs Discarded –Route OnHold Buffer Overflow -

MSULOST2


ReportsMeasurements


Number of MSUs discardedbecause the routing buffer wasin overflow.


1. LS On Hold BufferOverflow - The number ofMSUs discarded because thelinkset-on-hold buffer was inoverflow. The On HoldBuffer is used duringchangeover/changebacksituations to ensure thattraffic is sequenced correctly.During changeover andchangeback, MSUs that wereoriginally sent over linkswhich are now failed (notIS-NR) are buffered while thechangeover/changebackprocedures are carried out.Once those procedures arecompleted, the traffic in theon-hold buffer is routedbased on the currentconfiguration.


3. HSL –




peg countMSUs Discarded – Rcv QueueFull -

MSULOST4

Number of MSUs discardedbecause the receive queue wasfull.


ReportsMeasurements


peg countNetwork Management TaskDiscard from Processor

NMTSKDSC0

Overload - The total number ofnetwork management tasks(messages) discarded because ofa processor overload (taskpriority = 0).


NMTSKDSC1



NMTSKDSC2



NMTSKDSC3


peg countMSUs Originated – InvalidDPC-

OMSINVDPC

Number of MSUs originatedwith an invalid DPC.

peg countOriginatedMSUs - The totalnumber of outgoing MSUs

ORIGMSUS

successfully passed to MTP level2 for transmission, whilecarrying the STP point code inthe OPC field.

octetsOriginateMSU Octets -ORMSUOCT

The total number of outgoingoctets associated with MSUscarrying the STP point code inthe OPC field. This includes


ReportsMeasurements


octets added in MTP level 2processing.

peg countOversizedMTP 3 Messages -Oversized MTP 3 messages

OVSZMSG

exceeding 272 octets (level 3) thatare received by an HSL and arediscarded.



peg countThrough-SwitchedMSUs -THRSWMSU

The total number of MSUs thatdid not carry the STP point codein the OPC or the DPC, and weresuccessfully passed to MTP level2 for transmission.

peg countTerminatedMSUs - The totalnumber of incoming MSUs

TRMDMSUS


octetsTerminatedMSU Octets -TRMSUOCT

The total number of octetsassociated with incoming MSUscarrying the STP point code inthe DPC. Includes octetsremoved in MTP level 2processing.

octetsThrough-SwitchedMSU Octets-

TSMSUOCT

The total number of octetsassociated with MSUs that didnot carry the STP point code inthe OPC or the DPC, and weresuccessfully passed to MTP level2 for transmission

UI Example Output:

eagle10506 03-04-15 17:13:02 EST EAGLE 34.0.0 TYPE OF REPORT: NETWORK MANAGEMENT MEASUREMENTS ON STP


ReportsMeasurements

REPORT PERIOD: LAST REPORT INTERVAL: 03-04-15, 17:05:00 THROUGH 17:09:59 STP-NM MEASUREMENTS These measurements are from 03-04-15, 17:05:00 through 17:09:59. ORIGMSUS = 80, TRMDMSUS = 80, THRSWMSU = 0, ORMSUOCT = 1540, TRMSUOCT = 1540, TSMSUOCT = 0, MSINVDPC = 0, MSINVSIO = 0, OMSINVDPC = 0, MSINVLNK = 0, GTTPERFD = 0, GTTUN0NS = 0, GTTUN1NT = 0, MSSCCPFL = 0, MSINVSIF = 0, MSNACDPC = 0, MSINVSLC = 0, MSUDSCRD = 0, MSULOST1 = 0, MSULOST2 = 0, MSULOST3 = 0, MSULOST4 = 0, NMTSKDSC0 = 0, NMTSKDSC1 = 0, NMTSKDSC2 = 0, NMTSKDSC3 = 0, OVSZMSG = 0; eagle10506 03-04-15 17:13:03 EST EAGLE 34.0.0 END OF ON-DEMAND STP-NM MEASUREMENT REPORT;

FTP Example output file name: nm-stp_19990117_1550.csv

FTP Example output file format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","NETWORK MANAGEMENT MEASUREMENTS ON STP","LAST","1999-01-17","15:45:00","15:50:00",1<cr><lf><cr><lf>"STATUS","ORIGMSUS","TRMDMSUS","THRSWMSU","ORMSUOCT","TRMSUOCT","TSMSUOCT","MSINVDPC","MSINVSIO","OMSINVDPC","MSINVLNK","GTTPERFD","GTTUN0NS","GTTUN1NT","MSSCCPFL","MSINVSIF","MSNACDPC","MSINVSLC","MSUDSCRD","MSULOST1","MSULOST2","MSULOST3","MSULOST4","NMTSKDSC0","NMTSKDSC1","NMTSKDSC2","NMTSKDSC3","OVSZMSG"<cr><lf>"K",80,80,0,1540,1540,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>

Typical file size is:

Table 38: Typical File Size: nm-stp.csv


header

1042 bytes=477+315+250

LNKSET NM Report

Command Examples

• UI

rept-meas:type=nm:enttype=lnkset:lsn=xxxx

• FTP

rept-ftp-meas:type=nm:enttype=lnkset


ReportsMeasurements

Measurement Events

Table 39: Network Management Linkset Measurements


octetsMSU Octets Received - Totalnumber of octets associated with

MOCTRCVD

MSUs received, including thoseremoved and those for whichretransmission has beenrequested.


octetsMSU Octets Transmitted - Totalnumber of octets associated with

MOCTTRAN

MSUs transmitted to the far-end.For all linkset classes, thisincludes octets for MTP level 3SIO and SIF.

• For MTP2 class linksets,octets included are thoseassociated with MSUstransmitted ANDacknowledged by level 2, aswell as any retransmittedMSUs. Additional octetsincluded are MTP level 2 flag,BSN/BIB, FSN/BIB, LI, andCRC octets.

• For SAAL and IPVHSL classlinksets, octets are notincluded until the MSU isacknowledged by level 2.

• For IPVL and IPVLGW classlinksets, octets are notincluded until the MSU istransmitted by level 2. ForIPVLGW class linksets, SNMs(MSUs with SI=0) are NOTincluded.

peg countMSUs Transmitted - Totalnumber of MSUs transmitted to

MSGSTRAN

the far-end, includingretransmissions.


ReportsMeasurements


• For MTP2 class links, MSUstransmitted ANDacknowledged by level 2

• For SAAL, IPVL, IPVHSL,and IPVLGW class links,MTP level 3 messages offeredfor transmission after anyrequired conversion fromtheir respective M2PA,M3UA, or SUA formats

peg countMSUs Received - The totalnumber of MSUs received,

MSGSRCVD

including those for whichretransmission has beenrequested.

• For SAAL, IPVL, IPVHSL,and IPVLGW class linksets -applies to MTP level 3messages



UI Reports

UI Example Output:

rept-meas:type=nm:enttype=lnkset:lsn=xxx

tekelecstp 12-02-20 17:36:25 EST EAGLE5 44.0.0 TYPE OF REPORT: NETWORK MANAGEMENT MEASUREMENTS ON LNKSET REPORT PERIOD: LAST REPORT INTERVAL: 12-02-20, 17:30:00 THROUGH 17:34:59

LNKSET-NM MEASUREMENTS: mtp2 (MTP2)

These measurements are from 12-02-20, 17:30:00 through 17:34:59. MOCTTRAN = 0, MOCTRCVD = 0, MSGSTRAN = 0, MSGSRCVD = 0

;



ReportsMeasurements

LNKSET-NM MEASUREMENTS: ipsg (IPVL)


;


LNKSET-NM MEASUREMENTS: saal (SAAL)


;


LNKSET-NM MEASUREMENTS: ssedcm2 (IPVL)


;


LNKSET-NM MEASUREMENTS: hcmimt1 (MTP2-UNCH)


;

FTP Reports

Table 40: FTP NM LNKSET Column Headers


Linksetname

LSN

Link typeLNKTYPE


ReportsMeasurements

FTP Example Output File Name:nm-lnkset_20201005_0215.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-20","17:39:16","EST ","NETWORK MANAGEMENT MEASUREMENTS ON LNKSET","LAST","2012-02-20","17:30:00","17:35:00",6<cr><lf><cr><lf>"STATUS","LSN","LNKTYPE","MOCTTRAN","MOCTRCVD","MSGSTRAN","MSGSRCVD"<cr><lf>"K","mtp2","MTP2",0,0,0,0<cr><lf>"K","ipsg","IPVL",0,0,0,0<cr><lf>"K","m3uals","IPVL",0,0,0,0<cr><lf>"K","hcmimt1","MTP2-UNCH",0,0,0,0<cr><lf>"K","ssedcm2","IPVL",0,0,0,0<cr><lf>"K","saal","SAAL",0,0,0,0<cr><lf>


4 char status + 13 char LSN + 12 char LNKTYPE + 4*(6 char data) + 2 = 55 chars

Table 41: Typical File Size: nm-lnkset.csv


header

27,821 bytes=27,500+71+250

LINK NM Report

Certain registers are reported for HSLs or LSLs only. Other registers have different interpretations forHSLs than for LSLs. These registers are summarized in Table 42: HSL LSL Differences for NetworkManagement Links.

Table 42: HSL LSL Differences for Network Management Links

HSL UsageLSL UsageEvent Name

N/A - Not reportedAs describedDRBSYLNK

N/A - Not reportedAs describedDRFEPRO

Initiated by

MAAL - REPORT_LOCAL_ PROCESSOR_OUTAGE

As describedDRLCLPRO

Command Examples

• UI

rept-meas:type=nm:enttype=link:loc=xxxx:link=x


ReportsMeasurements

rept-meas:type=nm:enttype=link:lsn=ls3

• FTP

rept-ftp-meas:type=nm:enttype=link

Measurement Events

Table 43: Network Management Link Measurements


secondsDuration of Far-End ProcessorOutage -

DRFEPRO

The cumulative duration that alink was unavailable to MTPlevel 3 because of a processoroutage at the far-end networkelement (SIPO received). Notreported for HSLs.

secondsCumulative Duration of BusyLink Status-

DRBSYLNK

The total elapsed time betweenthe receipt of a busy LSSU, andwhen the next message wasacknowledged. This is the sumof all occurrences of busy linkstatus. (MTP 2 links only.)

secondsDuration of Local ProcessorOutage - The cumulative

DRLCLPRO

duration that a link wasunavailable to MTP level 3because of a processor outage atthe near-end network element.For HSLs, this is initiated by

MAAL-REPORT_LOCAL_ PROCESSOR_OUTAGE

secondsDuration of Links Unavailable- The total time a link was

DRLNKUNV

unavailable to MTP level 3 forany reason.

peg countEvent Count for Entering Level1 Link Congestion - The total

ECCNGLV1

number of times that linkcongestion level 1 was entered.


ReportsMeasurements



ECCNGLV2



ECCNGLV3



MSGDISC0






MSGDISC1




Note: The MSUs or Messagesmay be discarded on thetransmit/outbound link, whichindicates congestion via theECCNGLVLx or TDCNGLVxregisters or it may appear oninbound links routing traffic tothose congested links. The latter


ReportsMeasurements


will not indicate eitherECCNGLVLx or TDCNGLVx.


MSGDISC2






MSGDISC3





peg countNumber of Times GWSDisabled – The number of times

NMGWSDSABL

that the GWS subsystem on theLIM card supporting the link


ReportsMeasurements


was disabled because of a receiveoverload condition on the card.When this occurs, the GWSsubsystem is disabled for alllinks on the card and this registeris pegged for all links on the cardregardless of whether GWS isenabled for that link. Gatewayscreening is disabled on the cardto allow recovery from thereceive overload condition andis re-enabled when the receiveoverload condition abates.



secondsTotal Duration of Level 1 LinkCongestion - The total time thelink was in level 1 congestion.

TDCNGLV1


TDCNGLV2


TDCNGLV3

UI Reports

UI Example Output:

• rept-meas:type=nm:enttype=link:loc=xxxx:link=x

tekelecstp 12-02-20 17:18:12 EST EAGLE5 44.0.0 TYPE OF REPORT: NETWORK MANAGEMENT MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-02-20, 17:10:00 THROUGH 17:14:59

LINK-NM MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

These measurements are from 12-02-20, 17:10:00 through 17:14:59. DRLNKUNV = 300, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, DRFEPRO = 0, DRBSYLNK = 0, NMGWSDSABL = 0, DRLCLPRO = 0


ReportsMeasurements

;


LINK-NM MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

These measurements are from 12-03-21, 00:30:00 through 00:34:59. DRLNKUNV = 300, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, NMGWSDSABL = 0, DRLCLPRO = 0

;


LINK-NM MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-NM MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


;


LINK-NM MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)

These measurements are from 12-03-21, 00:30:00 through 00:34:59. DRLNKUNV = 300, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0,


ReportsMeasurements

ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, DRFEPRO = 0, DRBSYLNK = 0, NMGWSDSABL = 0, DRLCLPRO = 0

;

• rept-meas:type=nm:enttype=link:lsn=ls3


LINK-NM MEASUREMENTS FOR LINKSET mtp2:

LINK-NM MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)


;


LINK-NM MEASUREMENTS FOR LINKSET ipsg:

LINK-NM MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)


;


LINK-NM MEASUREMENTS FOR LINKSET saal:

LINK-NM MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)



ReportsMeasurements

;


LINK-NM MEASUREMENTS FOR LINKSET ssedcm2:

LINK-NM MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-NM MEASUREMENTS FOR LINKSET hcmimt1:

LINK-NM MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)


;

FTP Reports

Table 44: FTP NM LINK Column Headers


Linksetname

LSN

Cardlocation

LOC

Link portLINK

Link typeLNKTYPE

FTP Example Output File Name: nm-link_20101001_0215.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-20","17:31:43","EST ","NETWORK MANAGEMENT MEASUREMENTS ON LINK","LAST","2012-02-20","17:25:00","17:30:00",6<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","DRLNKUNV","TDCNGLV1","TDCNGLV2","TDCNGLV3","ECCNGLV1","ECCNGLV2","ECCNGLV3","MSGDISC0","MSGDISC1","MSGDISC2","MSGDISC3","DRFEPRO","DRBSYLNK","NMGWSDSABL","DRLCLPRO"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",300,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",300,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",300,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","m3uals","1105","A ","IPVLGW",300,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm2","1107","A ","IPVLGW",300,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","saal","1112","A ","SAAL",300,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 13 char LSN + 7 char LOC + 5 char LINK + 12 char LNKTYPE + 15*(6 char data) + 2 =133 chars

Table 45: Typical File Size: nm-link.csv


Systemheader

133,456 bytes=133,000+206+250

Daily Availability Measurements (AVLD)

Daily Availability (AVLD) Reports provide measurements pertaining to link management.

Entity Types: Link

Accumulation Interval: 24 hours


Reporting Mode: On-demand, scheduled (FTP reports only)

Accessible Collection Period: Last

LINK AVLD Report

Command Examples

• UI

rept-meas:type=avld:enttype=link:loc=xxxx:link=x:nzo=no

• FTP

rept-ftp-meas:type=avld:enttype=link


ReportsMeasurements

Measurement Events

Table 46: Availability Link Measurements


secondsCumulative Duration ofSignaling Link Declared

DRDCLFLR

Failures All Types - Thecumulative duration of all linkfailures.


DRFEPRO

The cumulative duration that alink was unavailable to MTPlevel 3 because of a processoroutage at the far-end networkelement (SIPO received). Notreported for SAAL, IPVL classor IPVLGW class links.

secondsDuration of Local ProcessorOutage -

DRLCLPRO

The cumulative duration that alink was unavailable to MTPlevel 3 because of a processoroutage at the near-end networkelement.

secondsDuration of SignalingLinkMgmt Inhibit - The

DRLKINHB

duration that a signaling linkwas unavailable because asignaling link was inhibited. Notreported for IPVL, IPVLGW, orIPVHSL links.

peg countNumber of Far-EndManagement Inhibits - The total

FARMGINH

number of times that a link wasinhibited by far-endmanagement. Not reported forIPVL, IPVLGW, or IPVHSLlinks.

peg countNumber of SignalingLinkFailures – Abnormal

NDCLFLABN

FIB/BSN - Number of times thesignaling link was takenout-of-service because of


ReportsMeasurements


abnormal FIB/BSN received. Acount was accumulated if twobackward sequence numbervalues in three consecutivelyreceived MSUs or FISUs are notthe same as the previous one orany of the forward sequencenumbers of the signal units inthe retransmission buffer at thetime they are retransmitted.Reported for MTP2 Links only.Occurrences of this conditionwhile the link is not in-serviceare not accumulated in thisregister.

peg countLink Failure – Alignment orProving Failure - Number of

NDCLFALP

times a signaling link wasreturned to out-of-servicebecause of the excessive errorrate detected by the alignmenterror rate monitor (AERM). Notreported for SAAL class links.

peg countLink Failure – Too ManyInterrupts -

NDCLFINTR

The number of times a signalinglink was out-of-service becausean excessive number of linkinterrupts occurred.

peg countLink Failure - Loss ofSynchronization -

NDCLFSYNC

Number of times that the linkwas taken out-of-service becauseof a loss of synchronization.

peg countNumber of Signaling LinkFailures – Excessive Delay of

NDCFLXDA

Acknowledgment - The numberof times a signaling link wasout-of-service due to anexcessive delay inacknowledgments. For SAALand IPVHSL class links, timerNO_RESPONSE expired forPOLL/STAT response. Not


ReportsMeasurements


reported for IPVL and IPVLGWclass links.

peg countNumber of Signaling LinkFailures - Excessive Duration of

NDCFLXDC

Congestion - The number oftimes a signaling link wasout-of-service because the timerT6 (remote congestion) expired.

• For SAAL and IPVHSL classlinks, timer NO_CREDITexpired for POLL/STATresponse.

• Not reported for IPVL andIPVLGW class links.

peg countNumber of Signaling LinkFailures – Excessive Error Rate

NDCFLXER

- Number of times a signalinglink was out-of-service becauseit reached the signal unit errorrate monitor (SUERM) threshold.

peg countNumber of Near-EndManagement Inhibits - Number

NEARMGIH

of times a link was unavailableto MTP level 3 because it waslocally inhibited. Not reportedfor IPVL, IPVLGW, or IPVHSLlinks.

peg countNumber of Signaling LinkDeclared Failures All Types -

NMDCLFLR

The cumulative total of all linkfailures.

peg countNumber of Far-End ProcessorOutages -

NMFEPRO

The total number of far-endprocessor outages. Reported forMTP2 links only.

peg countNumber of Local ProcessorOutages - The total number oflocal processor outages.

NMLCLPRO

peg countPCR N1 or N2 Count Exceeded- The total number of forced

PCRN1N2EXC

retransmissions when preventive


ReportsMeasurements


cyclic retransmission (PCR) isused as the error correctionmethod on a link. Reported forMTP2 links only.



peg countNumber of SUs Received inError - SUs received with

SURCVERR

checksum errors, indicatingtransmission errors. (For MTP2class links, applies to FISUs,LSSUs and MSUs. For SAALclass links and ATM HSLs, thisregister reflects the number ofSSCOP PDUs received witherrors).

peg countSignaling Units Received - Thetotal number of signaling units

SUSRECVD

received. (For ATM HSLs thisregister reflects the number ofSSCOP PDUs received).

peg countSignaling Units Transmitted -The total number of signaling

SUSTRAN

units transmitted. (For ATMHSLs this register reflects thenumber of SSCOP PDUstransmitted.)

UI Reports

Example Output:

• rept-meas:type=avldth:enttype=link:loc=xxxx:link=x:nzo=no

tekelecstp 12-02-21 00:11:11 EST EAGLE5 44.0.0 TYPE OF REPORT: DAILY AVAILABILITY MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-02-20, 00:00:00 THROUGH 23:59:59

LINK-AVLD MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

These measurements are from 12-02-20, 00:00:00 through 23:59:59. Measurement data represents an incomplete interval. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0,


ReportsMeasurements

DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRFEPRO = 0, DRLCLPRO = 0

;


LINK-AVLD MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

These measurements are from 12-02-20, 00:00:00 through 23:59:59. Measurement data represents an incomplete interval. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRFEPRO = 0, DRLCLPRO = 0

;


LINK-AVLD MEASUREMENTS: LOC: 1105, LINK: A , LSN: m3uals (IPVLGW)

These measurements are from 12-02-20, 00:00:00 through 23:59:59. Measurement data represents an incomplete interval. NMDCLFLR = 0, DRDCLFLR = 0, DRLCLPRO = 0

;


LINK-AVLD MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


;


LINK-AVLD MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)

These measurements are from 12-02-20, 00:00:00 through 23:59:59. Measurement data represents an incomplete interval. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRLCLPRO = 0


ReportsMeasurements

;


LINK-AVLD MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)


;

• rept-meas:type=avl:enttype=link:lsn=ls3

tekelecstp 12-02-20 17:49:42 EST EAGLE5 44.0.0 TYPE OF REPORT: AVAILABILITY MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-02-20, 17:00:00 THROUGH 17:29:59

LINK-AVL MEASUREMENTS FOR LINKSET mtp2:

LINK-AVL MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

These measurements are from 12-02-20, 17:00:00 through 17:29:59. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, NDCFLABN = 0, NDCLFSYNC = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NDCLFALP = 146, NDCLFINTR = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, SUSRECVD = 0, SUSTRAN = 1504478, PCRN1N2EXC = 0

;


LINK-AVL MEASUREMENTS FOR LINKSET ipsg:

LINK-AVL MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

These measurements are from 12-03-21, 00:30:00 through 00:59:59. NMDCLFLR = 0, DRDCLFLR = 0, NDCLFSYNC = 0, NDCLFALP = 0, NDCLFINTR = 0, NMLCLPRO = 0, DRLCLPRO = 0, SUSRECVD = 0, SUSTRAN = 0

;


LINK-AVL MEASUREMENTS FOR LINKSET saal:


ReportsMeasurements

LINK-AVL MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)

These measurements are from 12-03-21, 00:30:00 through 00:59:59. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, NDCLFSYNC = 15, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NDCLFINTR = 0, NMLCLPRO = 0, DRLCLPRO = 0, SUSRECVD = 0, SUSTRAN = 1560

;


LINK-AVL MEASUREMENTS FOR LINKSET ssedcm2:

LINK-AVL MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-AVL MEASUREMENTS FOR LINKSET hcmimt1:

LINK-AVL MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)


;

FTP Reports

Table 47: FTP AVLD LINK Command Headers


Linksetname

LSN


ReportsMeasurements


Cardlocation

LOC

Link portLINK

Link typeLNKTYPE

FTP Example Output File Name: avld-link_20101004_2400.csv

Example output file format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","00:17:33","EST ","DAILY AVAILABILITY MEASUREMENTS ON LINK","LAST","2012-02-20","00:00:00","24:00:00",6<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","NEARMGIH","FARMGINH","NMDCLFLR","DRDCLFLR","SURCVERR","DRLKINHB","DRFEPRO","DRLCLPRO"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",0,0,0,0,0,0,0,0<cr><lf>"K","m3uals","1105","A ","IPVLGW",0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm2","1107","A ","IPVLGW",0,0,0,0,0,0,0,0<cr><lf>"K","saal","1112","A ","SAAL",0,0,0,0,0,0,0,0<cr><lf>



Table 48: Typical File Size: avld-link.csv


header

91,377 bytes=91,000+127+250

Day-To-Hour Availability Measurements (AVLDTH)

Day-To-Hour Availability (AVLDTH) Reports provide measurements pertaining to link managementaccumulating through the day.

Entity Types: Link

Accumulation Interval: Daily total to the last full hour

STP Retention Period: 1 hour

Reporting Mode: On-demand

Accessible Collection Period: Last


ReportsMeasurements

LINK AVLDTH Report

Command Examples

• UI

rept-meas:type=avldth:enttype=link:loc=xxxx:link=x:nzo=no

• FTP

rept-ftp-meas:type=avldth:enttype=link

Measurement Events




DRDCLFLR



DRFEPRO



DRLCLPRO



DRLKINHB



ReportsMeasurements



FARMGINH



NDCLFLABN

FIB/BSN - Number of times thesignaling link was takenout-of-service because ofabnormal FIB/BSN received. Acount was accumulated if twobackward sequence numbervalues in three consecutivelyreceived MSUs or FISUs are notthe same as the previous one orany of the forward sequencenumbers of the signal units inthe retransmission buffer at thetime they are retransmitted.Reported for MTP2 Links only.Occurrences of this conditionwhile the link is not in-serviceare not accumulated in thisregister.


NDCLFALP



NDCLFINTR



NDCLFSYNC


ReportsMeasurements




NDCFLXDA

Acknowledgment - The numberof times a signaling link wasout-of-service due to anexcessive delay inacknowledgments. For SAALand IPVHSL class links, timerNO_RESPONSE expired forPOLL/STAT response. Notreported for IPVL and IPVLGWclass links.


NDCFLXDC





NDCFLXER



NEARMGIH



NMDCLFLR



ReportsMeasurements



NMFEPRO



NMLCLPRO


PCRN1N2EXC

retransmissions when preventivecyclic retransmission (PCR) isused as the error correctionmethod on a link. Reported forMTP2 links only.




SUSRECVD

received. (For ATM HSLs thisregister reflects the number ofSSCOP PDUs received.)


SUSTRAN


UI Reports

Example output:

• rept-meas:type=avldth:enttype=link:loc=xxxx:link=x:nzo=no




ReportsMeasurements

These measurements are from 12-02-20, 00:00:00 through 23:59:59. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRFEPRO = 0, DRLCLPRO = 0

;



These measurements are from 12-03-20, 00:00:00 through 23:59:59. NMDCLFLR = 0, DRDCLFLR = 0, DRLCLPRO = 0

;



These measurements are from 12-03-20, 00:00:00 through 23:59:59. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRLCLPRO = 0

;




;

tekelecstp 12-03-12 13:14:15 EST EAGLE5 44.0.0 TYPE OF REPORT: DAY-TO-HOUR AVAILABILITY MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-03-12, 00:00:00 THROUGH 12:59:59

LINK-AVLDTH MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)



ReportsMeasurements

;

• rept-meas:type=avldth:enttype=link:lsn=xxxx


LINK-AVLD MEASUREMENTS FOR LINKSET mtp2:


These measurements are from 12-02-20, 00:00:00 through 23:59:59. Measurement data represents an incomplete interval. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRFEPRO = 0, DRLCLPRO = 0

;


LINK-AVLD MEASUREMENTS FOR LINKSET ipsg:



;


LINK-AVLD MEASUREMENTS FOR LINKSET saal:


These measurements are from 12-03-20, 00:00:00 through 23:59:59. NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, DRLCLPRO = 0

;


LINK-AVLD MEASUREMENTS FOR LINKSET ssedcm2:



ReportsMeasurements


;


LINK-AVLD MEASUREMENTS FOR LINKSET hcmimt1:

LINK-AVLD MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)


;

FTP Reports

Table 50: FTP AVLDTH LINK Command Headers


Linksetname

LSN

Cardlocation

LOC

Link portLINK

Link typeLNKTYPE

FTP Example Output File Name:avldth-link_20101004_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","00:17:33","EST ","DAILY AVAILABILITY MEASUREMENTS ON LINK","LAST","2012-02-20","00:00:00","24:00:00",6<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","NEARMGIH","FARMGINH","NMDCLFLR","DRDCLFLR","SURCVERR","DRLKINHB","DRFEPRO","DRLCLPRO"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",0,0,0,0,0,0,0,0<cr><lf>"K","m3uals","1105","A ","IPVLGW",0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm2","1107","A ","IPVLGW",0,0,0,0,0,0,0,0<cr><lf>"K","saal","1112","A ","SAAL",0,0,0,0,0,0,0,0<cr><lf>


ReportsMeasurements



Table 51: Typical File Size: avldth-link.csv


header

91,377 bytes=91,000+127+250

Availability Measurements (AVL)

Availability Measurements (AVL) provide measurements relating to the availability of signaling links.

Entity Types: Link, STPLAN




Reporting Mode: On-demand, scheduled (FTP reports)

Accessible Collection Period: Last, active, specific, or all

LINK AVL Report

Certain registers are reported for HSLs or LSLs only. Other registers have different interpretations forHSLs than for LSLs. These registers are summarized in Table 52: Availability Link Register Usage ByLINK Class.

Table 52: Availability Link Register Usage By LINK Class

IPVHSL UsageIPVL andIPVLGW UsageSAAL UsageMTP2 UsageEvent Name

As describedN/A - notreported

N/A - notreported

As describedDRFEPRO


As describedAs describedDRLKINHB


As describedAs describedFARMGINH

N/A - notreported

N/A - notreported

N/A - notreported

As describedNDCFLABN


ReportsMeasurements

IPVHSL UsageIPVL andIPVLGW UsageSAAL UsageMTP2 UsageEvent Name

Level 2 timer t7expired


TimerNO_RESPONSEexpired for


NDCFLXDA

POLL/STATresponse



TimerNO_CREDITexpired


NDCFLXDC

As describedAs describedN/A - notreported

As describedNDCLFALP

No data receivedon the line


DS1: LOS, LOF, orLCD indications


NDCLFSYNC


As describedAs describedNEARMGIH

As describedAs describedN/A - notreported

As describedNMFEPRO

N/A - notreported

N/A - notreported

N/A - notreported

As describedPCRN1N2EXC

N/A - notreported

N/A - notreported

SSCOPPDUs (alltypes) receivedwith errors

Level 2 signalingunits (all types)received witherrors

SURCVERR

Level 2 signalingunits (all types)received


SSCOPPDUs (alltypes) received


SUSRECVD

Level 2 signalingunits (all types)transmitted


SSCOPPDUs (alltypes) transmitted


SUSTRAN

Command Examples

• UI

rept-meas:type=avl:enttype=link:loc=xxxx:link=x

• FTP

rept-ftp-meas:type=avl:enttype=link


ReportsMeasurements

Measurement Events




DRDCLFLR



DRFEPRO



DRLCLPRO



DRLKINHB



FARMGINH



NDCLFLABN

FIB/BSN - Number of times thesignaling link was takenout-of-service because of


ReportsMeasurements


abnormal FIB/BSN received. Acount was accumulated if twobackward sequence numbervalues in three consecutivelyreceived MSUs or FISUs are notthe same as the previous one orany of the forward sequencenumbers of the signal units inthe retransmission buffer at thetime they are retransmitted.Reported for MTP2 Links only.Occurrences of this conditionwhile the link is not in-serviceare not accumulated in thisregister.


NDCLFALP



NDCLFINTR



NDCLFSYNC



NDCFLXDA

Acknowledgment - The numberof times a signaling link wasout-of-service due to anexcessive delay inacknowledgments. For SAALand IPVHSL class links, timerNO_RESPONSE expired forPOLL/STAT response. Not


ReportsMeasurements


reported for IPVL and IPVLGWclass links.


NDCFLXDC





NDCFLXER



NEARMGIH



NMDCLFLR



NMFEPRO



NMLCLPRO


PCRN1N2EXC

retransmissions when preventive


ReportsMeasurements


cyclic retransmission (PCR) isused as the error correctionmethod on a link. Reported forMTP2 links only.



peg countNumber of SUs Received inError - SUs received with

SURCVERR

checksum errors, indicatingtransmission errors. (For MTP2class links, applies to FISUs,LSSUs and MSUs. For SAALclass links and ATM HSLs, thisregister reflects the number ofSSCOP PDUs received witherrors).


SUSRECVD

received. (For ATM HSLs thisregister reflects the number ofSSCOP PDUs received).


SUSTRAN


UI Reports

UI Example Output:

Note: Only non-zero measurements are shown in the UI reports. The examples will show all registerswith non-zero values.

• rept-meas:type=avl:enttype=link:loc=xxxx:link=x:nzo=no




ReportsMeasurements


;




;




;




;



ReportsMeasurements



;

• rept-meas:type=avl:enttype=link:lsn=xxx


LINK-AVL MEASUREMENTS FOR LINKSET mtp2:



;


LINK-AVL MEASUREMENTS FOR LINKSET ipsg:



;


LINK-AVL MEASUREMENTS FOR LINKSET saal:



ReportsMeasurements


;


LINK-AVL MEASUREMENTS FOR LINKSET ssedcm2:



;


LINK-AVL MEASUREMENTS FOR LINKSET hcmimt1:



;

FTP Reports

Table 54: FTP AVL LINK Column Headers


Linksetname

LSN

Cardlocation

LOC


ReportsMeasurements


Link portLINK

Link typeLNKTYPE

FTP Example Output File Name:avl-link_20101005_1830.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-20","17:52:43","EST ","AVAILABILITY MEASUREMENTS ON LINK","LAST","2012-02-20","17:00:00","17:30:00",6<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","NEARMGIH","FARMGINH","NMDCLFLR","DRDCLFLR","SURCVERR","DRLKINHB","NDCFLABN","NDCLFSYNC","NDCFLXDA","NDCFLXER","NDCFLXDC","NDCLFALP","NDCLFINTR","NMFEPRO","NMLCLPRO","DRFEPRO","DRLCLPRO","SUSRECVD","SUSTRAN","PCRN1N2EXC"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",0,0,0,0,0,0,0,0,0,0,0,146,0,0,0,0,0,0,1504478,0<cr><lf>"K","m3uals","1105","A ","IPVLGW",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm2","1107","A ","IPVLGW",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","saal","1112","A ","SAAL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1562,0<cr><lf>



Table 55: Typical File Size: avl-link.csv


header

82,011 bytes=81,500+261+250

STPLAN AVL Report

This enttype consists of measurements for LIM and DSM cards. The outputs are separate for the UIreports and combined for the FTP reports. The FTP reports appear after the UI reports for the DSMcards.

Note: The peg counts forSTPLAN measurements have the possibility of rolling over during periodsof highSTPLAN message transmit and receive. On the measurement reports these measurements showup as negative numbers. This indicatesSTPLAN transmit and receive measurements have valuesgreater than four gigabytes of data.

Command Examples

• UI


ReportsMeasurements

rept-meas:type=avl:enttype=stplan:loc=xxxx

• FTP

rept-ftp-meas:type=avl:enttype=stplan

Table 56: Availability STPLAN Measurements


peg countEthernet Alignment Error - Thenumber of packets not received

ENETALNERR

over the STPLAN interfacebecause of Ethernet alignmenterrors.

peg countEthernet Bus Busy - The numberof transmissions attempted when

ENETBUSBSY

the STPLAN Ethernet bus wasbusy.

peg countEthernet Collision Error - Thenumber of packets not

ENETCOLERR

transmitted by STPLAN becauseof excessive collisions on theSTPLAN Ethernet bus. The FTCReports will display this registeras zero for card types other thanACM cards.

peg countEthernet CRC Error - Thenumber of packets not received

ENETCRCERR

on the STPLAN Ethernet due toCRC errors.


ENETOCTRCV

on the STPLAN Ethernetinterface.


ENETOCTXMT

transmitted on the STPLANEthernet interface.

peg countEthernet Receive BufferOverflow Errors - The number

ENETOVRERR

of packets not received bySTPLAN because of a receivebuffer overflow.

peg countIP Address Error - The totalnumber of inbound IP

IPADDRERR


ReportsMeasurements




IPHDRERR

datagrams discarded on theSTPLAN interface due to headererrors. The FTC Reports willdisplay this register as zero forcard types other than ACMcards.

peg countIP Protocol Error - The numberof inbound IP datagrams

IPPROTERR

discarded by STPLAN due to anerror in the packet (invalidprotocol). The FTC Reports willdisplay this register as zero forcard types other than ACMcards.


SLANDISC1


peg countSTPLAN Discarded 2 - Thenumber of SLAN MSUs

SLANDISC2

discarded by the SLAN cards fornetwork problems andunreachable far end servers.During network outages theSLAN cards will stop TVG/MFCgrants or go into flow control.This causes the PDUs to bequeued on the LIM cards, so themajority of discards will bepegged on SLANDISC1 underthese circumstances.

msecSTPLAN Disabled – Theduration that the STPLAN

SLANDSBLD


peg countSTPLAN Screened – Number ofMSUs that were copied to the

SLANSCRND


ReportsMeasurements



peg countSTPLAN Transmit - Thenumber of MSUs sent to the host

SLANXMIT

destination. The FTC Reportswill display this register as zerofor card types other than ACMcards.

peg countSTPLAN Transmit - Thenumber of MSUs sent to the hostdestination.

SLANXMIT


TCPCONNFLD

that have failed on the STPLANinterface. MCP/OAMHCReports will display this registeras zero for card types other thanACM cards.


TCPSEGRCVD

received on the STPLANinterface. MCP/OAMHCReports will display this registeras zero for card types other thanACM cards.

peg countTCP Segment Sent - The totalnumber of TCP segments sent

TCPSEGSENT

on the STPLAN interface. TheFTC Reports will display thisregister as zero for card typesother than ACM cards

UI Example Output:

e1061001 10-08-16 19:36:15 EST EAGLE5 42.0.0-63.32.0 TYPE OF REPORT: AVAILABILITY MEASUREMENTS ON STPLAN REPORT PERIOD: LAST REPORT INTERVAL: 10-08-16 19:00:00 THROUGH 19:29:59

STPLAN-AVL MEASUREMENTS: LOC: 1215

These measurements are from 10-08-16 19:00:00 through 19:29:59. SLANDSBLD = 0 SLANDISC1 = 0 SLANDISC2 = 0 SLANSCRND = 0 SLANXMIT = 0 ENETALNERR = 0 ENETCRCERR = 0 ENETCOLERR = 0 ENETBUSBSY = 0 ENETOVRERR = 0 ENETOCTXMT = 0 ENETOCTRCV = 0 TCPCONNFLD = 0 TCPSEGRCVD = 0 TCPSEGSENT = 0


ReportsMeasurements

TCPSEGXMT2 = 0 TCPRCVERR = 0 TCPRSTSENT = 0 IPHDRERR = 0 IPADDRERR = 0 IPPROTERR = 0

;

e1061001 10-08-16 19:36:17 EST EAGLE5 42.0.0-63.32.0 END OF ON-DEMAND STPLAN-AVL MEASUREMENT REPORT;

FTP Example Output File Name:avl-stplan_19990117_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.32.0","2010-08-16","20:46:45","EST ","AVAILABILITY MEASUREMENTS ON STPLAN","LAST","2010-08-16","20:00:00","20:30:00",2

"STATUS","TYPE","LOC","SLANDSBLD","SLANDISC1","SLANDISC2","SLANSCRND","SLANXMIT","ENETALNERR","ENETCRCERR","ENETCOLERR","ENETBUSBSY","ENETOVRERR","ENETOCTXMT","ENETOCTRCV","TCPCONNFLD","TCPSEGRCVD","TCPSEGSENT","TCPSEGXMT2","TCPRCVERR","TCPRSTSENT","IPHDRERR","IPADDRERR","IPPROTERR""K","LIM","1104",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"K","DSM","1215",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0


4 char status + 6 char TYPE + 7 char LOC + 21*(6 char data) + 2 = 145 chars

For a report of 100 LIMs and 10 DSMs, the typical file size is:

Table 57: Typical File Size: avl-stplan.csv


header

679 bytes=145+284+250

Daily Maintenance Measurements (MTCD)

The Daily Maintenance (MTCD) reports provide measurements useful in determining STP performancebased on traffic.

Entity Types: STP, LINK, LNKSET, STPLAN, LNP, NP, EIR, MAPSCRN, SCTPASOC, SCTPCARD,UA, VFLEX, GTTAPATH, AIQ, ATINPQ, SIP, DEIR, ENUM, SFTHROT

Default Accumulation Interval: 24 hours

STP Retention Period:

• 24 hours: STP, LINK, LNKSET, STPLAN, SCTPASOC, SCTPCARD, UA, SIP, ENUM, SFTHROT

• 7 days: LNP, NP, EIR, MAPSCRN, VFLEX, ATINPQ, AIQ, GTTAPATH, DEIR

Reporting Modes: Scheduled and On-Demand


ReportsMeasurements

Note: Daily measurements are not available for the following features on the E5-OAM if the IntegratedMeasurements feature is not enabled:

• ATINPQ/PATINP• AIQ• EGMS• VFLEX• GTT Actions• EIR• LNP 384

Accessible Collection Periods: Last, Specific

STP MTCD Report

Example Commands:

UI : rept-meas:type=mtcd:enttype=stpFTP : rept-ftp-meas:type=mtcd:enttype=stp

Table 58: Daily Maintenance (MTCD) and Day-To-Hour Maintenance (MTCDTH) Measurements


peg countCritical System Alarms - Thetotal number of critical systemalarms.

CRSYSAL

secondsCumulative DurationofSignaling Link DeclaredFailures All Types -

DRDCLFLR

The cumulative duration of alllink failures.

secondsDuration ofLink Outage - Thetotal time a link was unavailableto MTP level 3 for any reason.

DURLKOTG

peg countDTAMSUsLost - The totalnumber of MSUs that were

DTAMSULOST

discarded because the redirectfunction was turned off or theoriginal MSU was too large to beencapsulated.

peg countG-FlexGTTs with Match - Thetotal number of G-Flex Global

GFGTMATCH

Title Translation successfullycompleted.


ReportsMeasurements


peg countG-FlexGTTs No Match - Thetotal number of G-Flex Global

GFGTNOMCH



GFGTNOLKUP



GTTPERFD




GTTUN0NS

Address of Such Nature – Totalnumber of times that thespecified translation type in anMSU was not supported by theSTP or the form of the GTT wasincorrect for the giventranslation type. Also includesG-Flex, INP and GTT MSUs thatdid not match on new selectors


ReportsMeasurements


(GTI,NP,NAI) in addition toones not matching on TT.


GTTUN1NT

This Address – The sum total oftimes that SCCP could not finda translation in the translationtable. This includes Global Titletranslations, Point Codetranslations, and Subsystemtranslations.

In general, this register containsthe sum of the GTTUN1NTregister in the systot-tt reportand the CGGTTUN1NT


MSIDPNOMCH


MSIDPMATCH


peg countMSUs Rcvd – InvalidDPC -MSINVDPC

Number of MSUs received anddiscarded because the DPCcould not be found in the STProuting table.


MSINVSIF



MSINVSIO



ReportsMeasurements


peg countMajor system alarms - The totalnumber of major system alarms.

MASYSAL

peg countMinor system alarms - The totalnumber of minor system alarms.

MISYSAL


MSINVLNK


peg countMSUs Discarded – InvalidSLC-

MSINVSLC

Number of MSUs discardedbecause of an invalid SLC codein the ECO/COO.

peg countMSUs Discarded –InaccessibleDPC -

MSNACDPC

The total number of MSUsdiscarded because of aninaccessible DPC.

peg countMSUs Discarded – RoutingFailure -

MSSCCPFL

Number of MSUs discarded dueto an SCCP routing failure. Alsoincludes G-Flex, INP MSUs thatgot a match from either theG-Flex, INP or GTT DB butcannot be routed due to PC or SScongestion, PC or SS unavailable,SS unequipped, or anunqualified error.

peg countMSUSCCP Failure - Total MSUsDiscarded Due to SCCPConversion Failure.

MSUSCCPFLR


MSUDSCRD

The total number of MSUs thatfailed gateway screening andwere discarded. See linksetreport for individual peg counts.


ReportsMeasurements



MSULOST1



MSULOST2



1. LS On Hold BufferOverflow - The number ofMSUs discarded because thelinkset-on-hold buffer was inoverflow. The On HoldBuffer is used duringchangeover/changebacksituations to ensure thattraffic is sequenced correctly.During changeover andchangeback, MSUs that wereoriginally sent over linkswhich are now failed (notIS-NR) are buffered while thechangeover/changebackprocedures are carried out.Once those procedures arecompleted, the traffic in theon-hold buffer is routedbased on the currentconfiguration.


3. HSL –




ReportsMeasurements




MSULOST4


peg countMSUs Discarded –LIM Init -MSULOST5

Number of MSUs discardedwhile the LIM card wasinitializing.

peg countMSUs Discarded – The numberof MSUs discarded due to an

MSULOST6


peg countMTP Restarts Initiated -Number of times MTP restart

MTPRESTS

was initiated by the STP. Thecount does not include thenumber of MTP restarts initiatedas a result of messages fromadjacent nodes.

peg countMSUs Originated - Invalid DPC- The number of MSUsoriginated with an invalid DPC.

OMSINVDPC

peg countOriginatedMSUs -ORIGMSUS

The total number of outgoingMSUs successfully passed toMTP level 2 for transmission,while carrying the STP pointcode in the OPC field. For IPGWlinks, this register includescounts for managementmessages such as RST messages.This register is not an aggregateof link or linkset registers.


OVSZMSG

exceeding 272 octets (level 3) that


ReportsMeasurements


are received by an HSL and arediscarded.

peg countThe total number of times that aGTT translation matched a

SCCPLOOP

Point Code in the STP’s loopsetentries resulting in either a notifyor discard of an SCCP message.






TRMDMSUS


peg countTranslation Type MappingTranslations Performed - The

TTMAPPF

total number of Translation TypeMapping translations performed(that is, a mapped SS7 messagetranslation type was found forthe existing SS7 messagetranslation type).


UDTXUDTF



XLXTELEI

X-List entry was not createdbecause the ELEI for the clusterwas set to ‘yes’.

peg countX-List Entry Not Created - Thetotal number of times an X-List

XLXTSPACE


ReportsMeasurements


entry was not created due to lackof space in the route/destinationtable.

UI Example Output:

e1061001 11-01-23 00:10:07 MST EAGLE5 43.0.0-63.49.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON STP REPORT PERIOD: LAST REPORT INTERVAL: 11-01-22 00:00:00 THRU 23:59:59

STP-MTCD MEASUREMENTS

ORIGMSUS = 0, TRMDMSUS = 0, THRSWMSU = 0, MTPRESTS = 0, DTAMSULOST = 0, MSINVDPC = 0, MSINVSIO = 0, OMSINVDPC = 0, MSINVLNK = 0, MSINVSIF = 0, MSNACDPC = 0, MSINVSLC = 0, GTTPERFD = 0, GTTUN0NS = 0, GTTUN1NT = 0, MSSCCPFL = 0, MSULOST1 = 0, MSULOST2 = 0, MSULOST3 = 0, MSULOST4 = 0, MSULOST5 = 0, DRDCLFLR = 0, DURLKOTG = 7713, CRSYSAL = 10, MASYSAL = 15, MISYSAL = 95, XLXTSPACE = 0, XLXTELEI = 0, TTMAPPF = 0, MSUDSCRD = 0, OVSZMSG = 0, GFGTMATCH = 0, GFGTNOMCH = 0, GFGTNOLKUP = 0, MSUSCCPFLR = 0, MSSCCPDISC = 0, MSIDPNOMCH = 0, MSIDPMATCH = 0, MSULOST6 = 0, SCCPLOOP = 0, UDTXUDTF = 0

FTP Example Output

FTP Example Output File Name: mtcd-stp_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 43.0.0-63.49.0","2011-01-23","01:11:43","MST ","DAILY MAINTENANCE MEASUREMENTS ON STP","LAST","2011-01-22","00:00:00","24:00:00",1

"STATUS","ORIGMSUS","TRMDMSUS","THRSWMSU","MTPRESTS","DTAMSULOST","MSINVDPC","MSINVSIO","OMSINVDPC","MSINVLNK","MSINVSIF","MSNACDPC","MSINVSLC","GTTPERFD","GTTUN0NS","GTTUN1NT","MSSCCPFL","MSULOST1","MSULOST2","MSULOST3","MSULOST4","MSULOST5","DRDCLFLR","DURLKOTG","CRSYSAL","MASYSAL","MISYSAL","XLXTSPACE","XLXTELEI","TTMAPPF","MSUDSCRD","OVSZMSG","GFGTMATCH","GFGTNOMCH","GFGTNOLKUP","MSUSCCPFLR","MSSCCPDISC","MSIDPNOMCH","MSIDPMATCH","MSULOST6","SCCPLOOP","UDTXUDTF""K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,7713,10,15,95,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

Typical file size:

Table 59: Typical File Size: mtcd-stp.csv


header

985 bytes=252+483+250


ReportsMeasurements

LINK MTCD Report

Certain registers are reported for MTP2, SAAL, IPVL, and IPVHSL classes. These registers aresummarized in Table 60: Registers Reported per LINK CLASS for Daily (MTCD) and Day-To-Hour(MTCDTH) Link Measurements.

Table 60: Registers Reported per LINK CLASS for Daily (MTCD) and Day-To-Hour (MTCDTH)Link Measurements

IPVHSL ClassIPVLGW ClassIPVL ClassSAAL ClassMTP2 ClassEvent Name

XXXXXACHGOVRS

XXDRBSYLNK

XXXXXDRDCLFLR

XXDRFEPRO

XXXXXDRLCLPRO

XXXDRLKINHB

XXXXXECCNGLV1

XXXXXECCNGLV2

XXXXXECCNGLV3

XECLNKCB

XECLNKXCO

XXXFARMGINH

XXXLMSUOCTRCV

XXXLMSUOCTTRN

XXXLMSURCV

XXXLMSURCVDSC

XXXLMSUTRN

XXXLMSUTRNDSC

XXXXXLNKAVAIL

XM2PLKNIS

XM2PUDMRC

XM2PUDMTR


ReportsMeasurements


XM2PUDOCR

XM2PUDOCT

XXXXXMOCTRCVD

XXXXXMOCTTRAN

XXXXXMSGDISC0

XXXXXMSGDISC1

XXXXXMSGDISC2

XXXXXMSGDISC3

XXXXXMSGSRCVD

XXXXXMSGSTRAN

XMSURCERR

XMSURETRN

XNDCFLABN

XXXNDCFLXDA

XXXNDCFLXDC

XXNDCFLXER

XXXNEARMGIH

XNEGACKS

XXXXXNMLCLPRO

XXXXXNMDCLFLR

XXNMFEPRO

XOCTRETRN

XPCRN1N2EXC

XSDPDURTR

XXXXXTDCNGLV1

XXXXXTDCNGLV2

XXXXXTDCNGLV3


ReportsMeasurements


XXXXXTLNKACTV

Command Examples

• FTP:

rept-ftp-meas:type=mtcd:enttype=link

Measurement Events

Table 61: Maintenance Daily (MTCD) and Maintenance Day-to-Hour (MTCDTH) LinkMeasurements


peg countNumber of AutomaticChangeovers - Number of times

ACHGOVRS

that a changeover procedure wasused to divert traffic from onelink to alternative links.


DRBSYLNK

The total elapsed time betweenthe receipt of a busy LSSU, andwhen the next message wasacknowledged. This is the sumof all occurrences of busy linkstatus. Reported for MTP2 Linksonly.


DRDCLFLR



DRFEPRO

The cumulative duration that alink was unavailable to MTPlevel 3 because of a processoroutage at the far-end networkelement (SIPO received).Reported for MTP2 and IPVHSLclass links ONLY.


ReportsMeasurements



DRLCLPRO


secondsDuration Link Inhibited - Thecumulative duration that a link

DRLKINHB

was inhibited at the local orfar-end network element.


ECCNGLV1



ECCNGLV2



ECCNGLV3



ECLNKCB



ECLNKXCO


peg countNumber of Far-EndManagement Inhibits - Number

FARMGINH

of times a link was inhibitedsuccessfully from the far-end.


LMSUOCTRCV

pegged in addition toMOCTRCVD when the LargeMSU Support for IP Signaling


ReportsMeasurements


feature status is on and a largeMSU is successfully received.


LMSUOCTTRN



LMSURCV

in addition to MSGSRCVD whenthe Large MSU Support for IPSignaling feature status is on anda large MSU is successfullyreceived.


LMSURCVDSC



LMSUTRN


peg countThe number of large MSUsdiscarded in the transmit path.

LMSUTRNDSC


LNKAVAIL


M2PLKNIS

was not in the in-service (INS)state at the M2PA layer (inseconds), i.e., during which thelink was in any of the otherdefined M2PA states (such asIDLE, OOS, AIP, PROVING,


ReportsMeasurements


ALIGNED READY, orRETRIEVAL).


M2PUDMRC


M2PUDMTR


M2PUDOCR


M2PUDOCT





MOCTTRAN

with MSUs transmitted to thefar-end. For all linkset classes,this includes octets for MTP level3 SIO and SIF.




ReportsMeasurements




MSGDISC0



Note: EAGLE supports this oneITU discard counter only. Whenthe discard threshold is reached,all MSUs are discarded andcounted in this register. Prior tothe discard threshold beingreached, no MSUs are discarded.



MSGDISC1




Note: The MSUs or Messagesmay be discarded on thetransmit/outbound link, whichindicates congestion via the


ReportsMeasurements


ECCNGLVLx or TDCNGLVxregisters or it may appear oninbound links routing traffic tothose congested links. The latterwill not indicate eitherECCNGLVLx or TDCNGLVx.


MSGDISC2






MSGDISC3






ReportsMeasurements



MSGSRCVD


• For SAAL, IPVL, IPVHSL,and IPVLGW class linksets -applies to MTP level 3messages.





peg countNumber of Message signalUnits received in error - bad

MSURCERR

CRC. This register applies toMTP2 links only.

peg countMSUs Retransmitted - Numberof MSUs retransmitted becauseof errors.

MSURETRN

peg countNumber of Signaling LinkFailures - Abnormal FIB/BSN -

NDCFLABN

The number of times thesignaling link was takenout-of-service because ofabnormal FIB/BSN received. Acount was accumulated if twobackward sequence numbervalues in three consecutivelyreceived MSUs or FISUs are notthe same as the previous one orany of the forward sequencenumbers of the signal units inthe retransmission buffer at thetime they are retransmitted.


ReportsMeasurements


Reported for MTP2 links only.Occurrences of this conditionwhile the link is not in-serviceare not accumulated in thisregister.

peg countNumber of Signaling LinkFailures - Excessive Delay of

NDCFLXDA

Acknowledgment - Number oftimes a signaling link wasout-of-service due to anexcessive delay inacknowledgments.

• For MTP2and IPVHSL classlinks, level 2 t7 expired level

• For SAAL class links, timerNO_RESPONSE expired forPOLL/STAT response

• Not reported for IPVL andIPVLGW class links

peg countNumber of Signaling LinkFailures - Excessive Duration ofCongestion

NDCFLXDC

• For MTP2 and IPVHSL classlinks, the number of times asignaling link wasout-of-service because theLevel 2 timer T6 (remotecongestion) expired

• For SAAL class links, thenumber of times timerNO_CREDIT expired


peg countNumber of Signaling LinkFailures - Excessive Error Rate

NDCFLXER

- Number of times a signalinglink was out-of-service becauseit reached the signal unit errorrate monitor (SUERM) threshold.Reported for MTP2 and SAALlinks only.


NEARMGIH

of times a link was unavailable


ReportsMeasurements


to MTP level 3 because it waslocally inhibited. Not reportedfor IPVL and IPVLGW classlinks.

peg countNumber of NegativeAcknowledgments Received

NEGACKS

-Number of times the BSN in anMSU was inverted, indicating aretransmission request. Thisregister is NOT applicable toHSLs.

peg countNumber of Local ProcessorOutages - The total number of

NMLCLPRO

local processor outages in thisSTP.

peg countNumber ofSignalingLinkDeclared Failures All

NMDCLFLR

Types - The cumulative total ofall link failures.


NMFEPRO

Number of far-end processoroutages that have occurred.Reported for MTP2 links only

peg countNumber of MSU octetsretransmitted. This register is

OCTRETRN

NOT reported for SAAL classlinks.


PCRN1N2EXC

retransmissions when preventivecyclic retransmission (PCR) isused as the error correctionmethod on a link. This registeris not applicable to HSLs.


SDPDURTR

sequenced Data PDUs that wereretransmitted, based on anaccumulated count of suchretransmissions conveyed to LM.This measurement replaces the


ReportsMeasurements


MTP level 2 negativeacknowledgments.




TDCNGLV1


TDCNGLV2


TDCNGLV3

secondsLink active time - total time thelink is active and transmittingMSUs.

TLNKACTV

• For SAAL class links, thetime the link is active andgiving MSUs to SAAL fortransmission.

• For IP7 links, TLNKACTV isbased on 10MB Ethernet linkspeed. Hence the report willbe relative to 10MB/sec.

FTP Reports

FTP Example Output File Name: mtcd-link_20101004_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-12","00:14:53","EST ","DAILY MAINTENANCE MEASUREMENTS ON LINK","LAST","2012-02-11","00:00:00","24:00:00",5<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","MSGSTRAN","MSGSRCVD","MSURETRN","OCTRETRN","MOCTTRAN","MOCTRCVD","TDCNGLV1","TDCNGLV2","TDCNGLV3","ECCNGLV1","ECCNGLV2","ECCNGLV3","MSGDISC0","MSGDISC1","MSGDISC2","MSGDISC3","TLNKACTV","LNKAVAIL","ACHGOVRS","NEARMGIH","FARMGINH","NMDCLFLR","DRDCLFLR","SURCVERR","NEGACKS","DRLKINHB","NDCFLABN","NDCFLXDA","NDCFLXER","NDCFLXDC","NMFEPRO","NMLCLPRO","DRFEPRO","DRLCLPRO","MSURCERR","DRBSYLNK","PCRN1N2EXC","SDPDURTR","LMSUTRN","LMSURCV","LMSUOCTTRN","LMSUOCTRCV","LMSUTRNDSC","LMSURCVDSC","M2PUDMTR","M2PUDOCT","M2PUDMRC","M2PUDOCR","M2PLKNIS",


ReportsMeasurements

"ECLNKCB","ECLNKXCO"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm1","1105","A ","IPVHSL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1281,0,0<cr><lf>"K","saal","1112","A ","SAAL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 13 char LSN + 7 char LOC + 6 char LINK + 12 char LKNTYPE + 51*(6 char data) + 2 =350 char

Table 62: Typical File Size: mtcd-link.csv


header

175,855 bytes=175,000+605+250

LNKSET MTCD Report

Command Examples

• FTP example command:

rept-ftp-meas:type=mtcd:enttype=lnkset

Measurement Events

Table 63: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) LinksetMeasurements



SCCPLOOP



K indicates good data


ReportsMeasurements


I indicates incompleteintervalN indicates data not current


ZTTMAPI

Received on the Gateway Linkset- The total number of TranslationType Mapping translationsperformed for incoming MessageSignal Units (MSUs) received onthe specified linkset.


ZTTMAPO

Transmitted on the GatewayLinkset - The total number oftranslations performed onoutgoing Message Signal Units(MSUs) for the specified linkset.

FTP Reports

FTP Example Output File Name: mtcd-lnkset_20101004_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-12","00:28:19","EST ","DAILY MAINTENANCE MEASUREMENTS ON LNKSET","LAST","2012-02-11","00:00:00","24:00:00",5<cr><lf>

"STATUS","LSN","LNKTYPE","ZTTMAPO","ZTTMAPI","SCCPLOOP"<cr><lf>"K","mtp2","MTP2",0,0,0<cr><lf>"K","ipsg","IPVL",0,0,0<cr><lf>"K","ssedcm1","IPVHSL",0,0,0<cr><lf>"K","saal","SAAL",0,0,0<cr><lf>"K","hcmimt1","MTP2-UNCH",0,0,0<cr><lf>



Table 64: Typical File Size: mtcd-lnkset.csv


header

24,808 bytes=24,500+58+250


ReportsMeasurements

LNP MTCD Report

The enttype=lnp entity generates four separate reports per period. The command example will generatethe following daily reports:

• Daily LNP System Wide Measurements

• Daily LNP Measurements Per SSP

• Daily LNP Measurements Per LRN

• Daily LNP Measurements Per NPA

LNP reports are supported only by the FTP reporting capability.

Example Command: rept-ftp-meas:type=mtcd:enttype=lnp[:day=xxx:period=specific]

Table 65: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP System WideMeasurements


peg countTrigger BasedLNPQRCV

The total number of queriesreceived by LNPQS.

peg countTriggerless

Number of encapsulated IAMmessages received by LNPQS

peg countTrigger BasedLNPQDSC

The number of invalid queriesthat are discarded because noreply can be generated.

not applicableTriggerless

All invalid IAM messages arerouted without LNP;LNPQTCPE is pegged.

peg countTrigger BasedLNPQTCPE

The number of error replies withTCAP error codes.


The number of invalidencapsulated IAM messagesreceived by LNPQS. Note thatthese messages are routed totheir destinations with no LNPlookup.


ReportsMeasurements


peg countTrigger BasedLNPSREP

The number of successful replies.


The number of successful IAMmessages.

peg countTrigger BasedLNPQUNPA

The number of correct queriesreceived for non-ported DNwhen NPA-NXX is notprovisioned.


The number of correctencapsulated IAM messagesreceived for a non-ported DN,when the NPA-NXX is notprovisioned.



Table 66: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP Per SSP Measurements


peg countTrigger BasedSSPQRCV

Number of correct queriesreceived per originating SSP.


The number of correctencapsulated IAM messagesreceived by LNPQS per OPC.

peg countNumber of valid CLASS GTTreceived per originating SSP.

CLASSGTRQ

peg countNumber of valid LIDB GTTreceived per originating SSP.

LIDBGTRQ


ReportsMeasurements


peg countNumber of correct queriesreceived for ported TNs, peroriginating SSP.

SSPQRCVP

peg countNumber of correct queriesreceived for non-ported TNs, peroriginating SSP.

SSPQRCVNP

peg countNumber of CLASS Global TitleTranslation received for portedTNs, per originating SSP.

CLASSGTRQP

peg countNumber of CLASS Global TitleTranslation received for

CLASSGTRQNP

non-ported TNs, per originatingSSP.

peg countNumber of LIDB Global TitleTranslation received for portedTNs, per originating SSP.

LIDBGTRQP

peg countNumber of LIDB Global TitleTranslation received for

LIDBGTRQNP


peg countNumber of CNAM Global TitleTranslation received for portedTNs, per originating SSP.

CNAMGTRQP

peg countNumber of CNAM Global TitleTranslation received for

CNAMGTRQNP


peg countNumber of ISVM Global TitleTranslation received for portedTNs, per originating SSP.

ISVMGTRQP

peg countNumber of ISVM Global TitleTranslation received for

ISVMGTRQNP


peg countNumber of WSMSC Global TitleTranslations received for portedTNs, per originating SSP

WSMSCGTRQP

peg countNumber of WSMSC Global TitleTranslations received for

WSMSCGTRQNP


ReportsMeasurements


non-ported TNs, per originatingSSP



textThe TYPE of the point code.Valid values are ANSI, ITUI,ITUN, and ITUN24.

PC TYPE

The following equations apply:

SSPQRCV = SSPQRCVP + SSPQRCVNP

CLASSGTRQ = CLASSGTRQP + CLASSGTRQNP

LIDBGTRQ = LIDBGTRQP + LIDBGTRQNP

Table 67: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP LRN Measurements


peg countTrigger BasedLRNQRCV

The number of correct queriesreceived per LRN.


The number of correctencapsulated IAM messagesreceived per LRN.



Table 68: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP NPA Measurements


peg countThe number of correct queriesreceived per NPANXX fornon-ported DN.

NPAQRCV


ReportsMeasurements




FTP Reports

Daily LNP System Wide Measurements

FTP Example Output File Name: mtcd-lnp_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","DAILY MAINTENANCE MEASUREMENTS ON LNP SYSTEM","LAST","1999-01-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","LNPQRCV","LNPQDSC","LNPQTCPE","LNPSREP","LNPQUNPA"<cr><lf>"K",429496729,429496729,429496729,429496729,429496729<cr><lf>


Table 69: Typical File Size: mtcd-lnp.csv

File Size=Report dataReportheader

Systemheader

347 bytes=34+63+250

Daily LNP Measurements Per SSPFTP Example Output File Name:mtcd-ssp_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","DAILY MAINTENANCE MEASUREMENTS ON LNPSSP","LAST","1999-01-16","00:00:00","24:00:00",200<cr><lf><cr><lf>"STATUS","SSP","PC_TYPE","SSPQRCV","CLASSGTRQ","LIDBGTRQ","SSPQRCVP","SSPQRCVNP","CLASSGTRQP","CLASSGTRQNP","LIDBGTRQP","LIDBGTRQNP","CNAMGTRQP","CNAMGTRQNP","ISVMGTRQP","ISVMGTRQNP","WSMSCGTRQP","WSMSCGTRQNP"<cr><lf>"K","002-002-100","ANSI",123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999<cr><lf>. . . . .


ReportsMeasurements

"K","002-005-123","ANSI",123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999<cr><lf>


4 char status + 14 char SSP + 10 char PC type+ 15*(6 char data) + 2 = 120 chars

For a report of 200 SSPs, the typical file size is:

Table 70: Typical File Size: mtcd-ssp.csv


header

24410 bytes=24000+160+250

Daily LNP Measurements Per LRNFTP Example Output File Name:mtcd-lrn_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","DAILY MAINTENANCE MEASUREMENTS ON LNP LRN","LAST","1999-01-16","00:00:00","24:00:00",600<cr><lf><cr><lf>"STATUS","LRN","LRNQRCV"<cr><lf>"K",9194560000,123456789<cr><lf>"K",4087550001,23456789<cr><lf>"K",5155550000,456789<cr><lf>. . . . ."K",3022330001,345<cr><lf>"K",7032110002,99999<cr><lf>"K",8123048059,4294967295<cr><lf>


4 char status + 11 char LRN + 6 char data + 2 = 23 chars

For a report of 600 LRNs, the typical file size is:

Table 71: Typical File Size: mtcd-lrn.csv

Report data+Reportheader+System

header

14077 bytes=13800+27+250

Daily LNP Measurements Per NPAFTP Example Output File Name:mtcd-npa_19990116_2400.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","DAILY MAINTENANCE MEASUREMENTS ON LNP NPANXX","LAST","1999-01-16","00:00:00","24:00:00",600<cr><lf><cr><lf>"STATUS","NPANXX","NPAQRCV"<cr><lf>"K",919456,123456789<cr><lf>"K",408755,23456789<cr><lf>"K",515555,456789<cr><lf>. . . . ."K",302233,345<cr><lf>"K",703211,99999<cr><lf>"K",812304,4294967295<cr><lf>


4 char status + 7 char NPANXX + 6 char data + 2 = 19 chars


Table 72: Typical File Size: mtcd-npa.csv


header

11680 bytes=11400+30+250

NP MTCD Report

The daily Number Portability measurements specify the entity type NP (enttype=np) which generatestwo separate reports per period. The command example will generate the following daily reports:

• Daily System Wide Measurements

• Daily Measurements Per SSP

Command Examples

• FTP

rept-ftp-meas:type=mtcd:enttype=np[:period=specific:day=xxx]

Measurement Events

• System Wide Measurements

indicates system registers that may be pegged. Register counts for features not turned on willalways be zero.


ReportsMeasurements

Table 73: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) System-Wide Registers


peg countNumber of SMSREQ messagesresulting in error.

APSMRQERR

peg countNumber of SMSREQ messagesresulting in SMSREQ_ACK orSMSREQ_NACK.

APSMRQREP

peg countNumber of SMS Requestmessages received.

APSMSRCV

peg countNumber of SMS Requestmessages relayed.

APSMSREL

Peg CountNumber of non-call relatedmessages relayed by G-Port.

GPNOCL

Peg CountNumber of non-call relatedmessages that fell through toGTT.

GPNOCLGT

Peg CountNumber of call relatedmessages that cause an error

GPSRERR

response message(SRI-SendRouting InformationNEGATIVE ACK) because ofG-Port service failure. This doesnot include peg counts toregister GPSRERRPP.

Peg CountNumber of call related(SRI-Send Routing Information)

GPSRREPPP

messages that received G-Portservice specifically for feature:G-Port SRI query for Prepaid.This does not include pegcounts to register GPSRREP.


GPSRGTT

messages that fell through toGTT. This does not include pegcounts to register GPSRGTTPP.


GPSRGTTPP

messages that fell through toGTT specifically for feature:G-Port SRI query for Prepaid.


ReportsMeasurements


This does not include pegcounts to register GPSRGTT.


GPSRRCV

messages received. This doesnot include peg counts toregister GPSRRCVPP.


GPSRRCVPP

messages received specificallyfor feature: G-Port SRI queryfor Prepaid. This does notinclude peg counts to registerGPSRRCV.


GPSRREP

messages that received G-Portservice. This does not includepeg counts to registerGPSRREPPP.


GPSRERRPP

response message (SRI-SendRouting InformationNEGATIVE ACK) specificallyfor feature: G-Port SRI queryfor Prepaid. This does notinclude peg counts to registerGPSRERR.

peg countNumber of SRI_SM messagesresulting in error.

GPSRSMERR

peg countNumber of SRI_SM messagesreceived.

GPSRSMRCV

peg countNumber of SRI_SM messagesresulting in SRI_SM_ACK orSRI_SM_NACK.

GPSRSMREP

peg countNumber of invalid queries thatare discarded as no reply canbe generated.

INPQDSC

peg countNumber of total queriesreceived by INPQS.

INPQRCV


ReportsMeasurements


peg countNumber of queries received byINPQS that meet the conditionfor circular route detection.

INPQSCRD

peg countNumber of error replies withTCAP error code.

INPQTCPE

peg countNumber of successful replies toINP non-queried queries. These

INPSREP

replies will be either INPConnect, INP Continue, or INPReleaseCall (every time anINAP RELEASECALL responseis generated due to circularroute dection by INPQS).

peg countNumber of IS-41 locationrequest - error responsemessages sent.

IS41LRERR

peg countNumber of IS-41 locationrequest messages received

IS41LRMRCV

peg countNumber of IS-41 locationrequest - return result messagessent

IS41LRRTRN

peg countNumber of times CircularRoute is Detected

MNPCRD

peg countNumber of MO_SMS messagesreceived that result in an error

SMSMOGERR

peg countNumber of MO_SMS messagesreceived that result in a

SMSMOGRCV

modification of the outgoingMO_SMS

peg countNumber of SMDPP messagesreceived that result in an error

SMSMOIERR

peg countNumber of SMDPP messagesreceived that result in a

SMSMOIRCV

modification of the outgoingSMDPP.


K indicates good dataI indicates incompleteinterval


ReportsMeasurements


N indicates data not current

peg countTotal number of MSUsprocessed by TIF and

TIFFPFXRLS

blacklisted by the FPFXRLSService Action


TIFNFNDRLS

blacklisted by the BLNFNDRLSService Action


TIFNOCGRLS

blacklisted by theNOCGPNRLS Service Action


TIFRLS

blacklisted by the BLRLSService Action

peg countNumber of MSUs processed byTIF and found to be blacklistedby SELSCR Service Action

TIFSSCRRLS

peg countNumber of MSUs processed byTIF and relayed by SELSCRService Action

TIFSSCRRLY

peg countNumber of IAM messagesreceived that required TIF

TINPERR

processing but resulted inexecution of an error case.


TINPMGEN

processing and resulted in themodification of the IAMmessage or the generation of aREL message.

peg countNumber of IAM messagesreceived that require TIFprocessing.

TINPMRCV


INPQRCV = INPQDSC + INPQTCPE + INPSREP

GPSRRCV = GPSRGTT + GPSRREP + GPSRERR


ReportsMeasurements

GPSRRCVPP = GPSRGTTPP + GPSRREPPP + GPSRERRPP

GPSRSMRCV = GPSRSMREP + GPSRSMERR

• Per SSP Measurements

These measurements are available on a per SSP PC basis where SSP PC is the CGPA PC, if it exists,or it is the MTP OPC.

Table 74: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) SSP Registers


peg countNumber of call relatedLOCREQ messagesacknowledged.

APLRACK

peg countNumber of call relatedLOCREQ messages relayed.

APLRRLY

peg countNumber of non-callnon-LOCREQ related messagesrelayed.

APNOCL

peg countNumber of non-callnon-LOCREQ related messagesthat fell through to GTT.

APNOCLGT


APSMRQERR

peg countNumber of SMSREQ messagesresulting in SMSREQ_ACK orSMSREQ_NACK

APSMRQREP

peg countNumber of SMSREQ messagesreceived

APSMSRCV

peg countNumber of non-call relatedmessages relayed by G-Port.

GPNOCL

peg countNumber of non-call relatedmessages that fell through toGTT.

GPNOCLGT

peg countNumber of call related(SRI-Send Routing Information

GPSRACK

ACK) responses. This does notinclude peg counts to registerGPSRACKPP.


GPSRACKPP

ACK) responses specifically forfeature 61544: G-Port SRI query


ReportsMeasurements


for Prepaid. This does notinclude peg counts to registerGPSRACK.

peg countNumber of call related SRINegative ACK responses in

GPSRNACK

case of successful G-Portservice.

peg countNumber of call related(SRI-Send Routing Information)messages relayed.

GPSRRLY


GPSRSMERR


GPSRSMRCV

peg countNumber of SRI_SM messagesresulting in SRI_SM_ACK orSRI_SM_NACK

GPSRSMREP

peg countNumber of messages sent toMR service that fall through to

INPMRCRD

GTT due to circular routedetection.


INPMRGTT

GTT. This includes the numberof messages sent to MR servicethat fall through to GTT due tocircular route detection.

peg countNumber of messages sent toMR service that receive MRtranslation.

INPMRTR

peg countNumber of non-erroredQSmessages with QS Connectresponses, per originating SSP.

INPQSCONN

peg countNumber of non-errored QSmessages with QS Continueresponses, per originating SSP.

INPQSCONT

peg countNumber of messages sent toINP QS that meet the conditionfor circular route detection.

INPQSCRD


ReportsMeasurements


peg countNumber of messages sent toINP QS that result in successful

INPQSREL

generation of INAPRELEASECALL response dueto circular route detection byINPQS.

peg countNumber of times CircularRoute is Detected.

MNPCRD

textTYPE of the point code. Validvalues are ANSI, ITUI, ITUN,and ITUN24.

PC Type


SMSMOGERR


SMSMOGRCV



SMSMOIERR


SMSMOIRCV

modification of the outgoingSMDPP




TIFRANGEBL

blacklisted by the FPFXRLS orNOCGPNRLS Service Action

peg countTotal number of MSUsprocessed by TIF and found to

TIFSBSCRBL

be blacklisted by BLRLS orBLNFNDRLS Service Actions

peg countNumber of IAM messagesprocessed by TIF which

TIFSELSCR

resulted in either an ISUPmessage generation or the MSU


ReportsMeasurements


being relayed by SELSCRService Action


TINPERR



TINPMGEN



TINPMRCV

The following equation applies to NP registers:

GPSRREP = ∑GPSRACK + ∑GPSRRLY+ ∑GPSRNACK

FTP Reports

• Daily System Wide Measurements

FTP Example Output File Name:mtcd-np_20080125_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-20","00:00:57","EST ","DAILY MAINTENANCE MEASUREMENTS ON NP SYSTEM","LAST","2010-08-19","00:00:00","24:00:00",1

"STATUS","INPQRCV","INPQDSC","INPQTCPE","INPSREP","GPSRRCV","GPSRGTT","GPSRREP","GPSRERR","GPNOCL","GPNOCLGT","IS41LRERR","IS41LRMRCV","IS41LRRTRN","GPSRRCVPP","GPSRGTTPP","GPSRREPPP","GPSRERRPP","APSMSRCV","APSMSREL","TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV","SMSMOIERR","SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP","APSMRQERR","INPQSCRD","MNPCRD""K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,

Assuming each data line will be: 4 char status + 33 * (6 char data) + 2 = 204 chars


Table 75: Typical File Size: mtcd-np.csv


header

832 bytes=204+378+250


ReportsMeasurements

• Daily Measurements Per SSP

Table 76: FTP Daily Maintenance (MTCD) SSP Column Header

DescriptionField Name

Service switching point codeSSP

FTP Example Output File Name: mtcd-ssp_20080125_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-20","00:00:58","EST ","DAILYMAINTENANCE MEASUREMENTS ON NP SSP","LAST","2010-08-19","00:00:00","24:00:00",3"STATUS","SSP","PC_TYPE","INPQSCONN","INPQSCONT","INPMRTR","INPMRGTT","GPSRACK","GPSRRLY","GPNOCL","GPNOCLGT","GPSRACKPP","APLRACK","APLRRLY","APNOCL","APNOCLGT","TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV","SMSMOIERR","SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP","APSMRQERR","APSMSRCV","INPQSCRD","INPQSREL","INPMRCRD","MNPCRD","GPSRNACK""K"," 001-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,"K"," 101-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,"K"," 201-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,

Assuming each data line will be: 4 char status + 14 char SSP + 10 char PC type + 31 * (6 char data)+ 2 = 216 chars




header

606 + ( 216 *#Point

=(216 * #PointCodes )

+356+250

Codes )bytes

For a report of 200 SSPs, typical file size is:



header

43806 bytes=(216 * 200 )+356+250


ReportsMeasurements

STPLAN MTCD Report

Example Commands:

UI: rept-meas:type=mtcd:enttype=stplan

FTP: rept-ftp-meas:type=mtcd:enttype=stplan

Table 79: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) STPLANMeasurements



ENETALNERR



ENETBUSBSY


peg countEthernetCRC Error - Number ofpackets not received on the

ENETCRCERR



ENETCOLERR



ENETOCTRCV



ENETOCTXMT


peg countEthernet Receive BufferOverflow Errors -

ENETOVRERR

Number of packets not receivedby STPLAN because of a receivebuffer overflow.


ReportsMeasurements


peg countIP Address Error- The totalnumber of inbound IP

IPADDRERR



IPHDRERR



IPPROTERR



SLANDISC1



SLANDISC2

SLAN cards for networkproblems and unreachable farend servers. During networkoutages, the SLAN cards willstop TVG/MFC grants or go intoflow control. This causes thePDUs to be queued on the LIMcards, so the majority of discardswill be pegged on SLANDISC1under these circumstances.


SLANDSBLD



SLANSCRND



SLANXMIT


ReportsMeasurements





TCPCONNFLD



TCPRCVERR



TCPRSTSENT



TCPSEGRCVD



TCPSEGSENT


TCPSEGXMT2


UI Example Output:

tekelecstp 01-08-18 00:00:21 EST EAGLE 34.0.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON STPLAN REPORT PERIOD: LAST REPORT INTERVAL: 01-08-17 00:00:00 THRU 23:59:59 STPLAN-MTCD MEASUREMENTS SLANDSBLD = 0, SLANDISC1 = 0, SLANDISC2 = 0, SLANSCRND = 0, SLANXMIT = 0, ENETALNERR = 0, ENETCRCERR = 0, ENETCOLERR = 0, ENETBUSBSY = 0, ENETOVRERR = 0, ENETOCTXMT = 0, ENETOCTRCV = 0, TCPCONNFLD = 0, TCPSEGRCVD = 0, TCPSEGSENT = 0, TCPSEGXMT2 = 0, TCPRCVERR = 0, TCPRSTSENT = 0, IPHDRERR = 0, IPADDRERR = 0, IPPROTERR = 0; tekelecstp 01-08-18 00:00:22 EST EAGLE 34.0.0


ReportsMeasurements

END OF DAILY STPLAN-MTCD MEASUREMENT REPORT;

FTP Example Output File Name: mtcd-stplan_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","DAILY MAINTENANCE MEASUREMENTS ON STPLAN","LAST","1999-01-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","SLANDSBLD","SLANDISC1","SLANDISC2","SLANSCRND","SLANXMIT","ENETALNERR","ENETCRCERR","ENETCOLERR","ENETBUSBSY","ENETOVRERR","ENETOCTXMT","ENETOCTRCV","TCPCONNFLD","TCPSEGRCVD","TCPSEGSENT","TCPSEGXMT2","TCPRCVERR","TCPRSTSENT","IPHDRERR","IPADDRERR","IPPROTERR"<cr><lf>"K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


Table 80: Typical File Size: mtcd-stplan.csv


header

651 bytes=130+271+250

EIR MTCD Report

The EIR measurements specify the entity type EIR, and generate one daily report. The commands arespecified with xxx as a three-letter abbreviation for a day of the week (MON, TUE, WED, THU, FRI,SAT, or SUN). The retention period for daily measurement records is seven days.

FTP Example Command:

rept-ftp-meas:type=mtcd:enttype=eir[:day=xxxx:period=specific]

Table 81: Daily Maintenance (MCTD) and Hourly Maintenance (MTCH) EIR Measurements lists the EIRevents and their descriptions.

Table 81: Daily Maintenance (MCTD) and Hourly Maintenance (MTCH) EIR Measurements


peg countTotal number ofMAP_CHECK_IMEI messagesreceived

IMEIRCV

peg countTotal number of searches thatresulted in a match with a “whitelisted” IMEI

WHITEIMEI


ReportsMeasurements


peg countTotal number of searches thatresulted in a match with a “graylisted” IMEI

GRAYIMEI

peg countTotal number of searches thatresulted in a match with a “blacklisted” IMEI

BLACKIMEI

peg countTotal number of searches thatresulted in a match with a “black

BLKALIMEI

listed” IMEI, but were alloweddue to IMSI Check match


BLKNALIMEI

listed” IMEI, and the IMSI in thedatabase did not match the IMSIin the message

peg countTotal number of searches thatresulted in a match with an“unknown” IMEI

UNKNIMEI

peg countTotal number of searches thatresulted in no match in thedatabase.

NOMTCHIMEI

NOMTCHIMEI is peggedwhenever an IMEI is not foundin the database.



The following equation applies:

IMEIRCV = WHITEIMEI + GRAYIMEI + UNKNIMEI

FTP Example Output File Name: mtcd-eir_20030816_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-51.1.0","2003-08-17","15:51:37","EST","DAILY MAINTENANCE MEASUREMENTS ON EIR SYSTEM","LAST","2003-08-16", "00:00:00","24:00:00",1<cr><lf><cr><lf>"IMEIRCV","WHITEIMEI","GRAYIMEI","BLACKIMEI","BLKALIMEI","BLKNALIMEI","UNKNIMEI","NOMTCHIMEI"<cr><lf>


ReportsMeasurements

4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295, 4294967295<cr><lf>


Table 82: Typical File Size: mtcd-eir.csv


Systemheader

440 bytes=89+95+256

MAPSCRN MTCD Report

The enttype=mapscrn entity generates two separate reports per period.

The command example generates the following daily measurement reports when the GSMMAPScreening feature is activated:

• Daily MAP Screening System Wide Measurements

• Daily MAP Screening Measurements Per Server

The command example generates the following daily measurement reports when theGSMMAP/Enhanced GSMMAP Screening feature is activated:

• Daily MAP Screening System Wide Measurements

• Daily MAP Screening Measurements Per Path

All the FTP reports are listed together.

Example Commands:

• FTP: rept-ftp-meas:type=mtcd:enttype=mapscrn

Note: When MTP MAP Screening is enabled and on, the registers in Table 83: Daily Maintenance(MTCD) and Hourly Maintenance (MTCH) MAP Screening System Wide Measurements and Table 86: DailyMaintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening Per Server Measurements includethe sum total of MTP-routed and GTT-routed messages for the particular event.

Table 83: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening SystemWide Measurements


countTotal number of messages thatPassed MAP screening

MSCRNPASS

countTotal number of messages thatgot Rejected by MAP screening

MSCRNRJNE

because an entry was not foundin the MAP screening table (i.e.,


ReportsMeasurements


rejected as System wide MAPOpcode action is DISCARD)


MSCRNRJFP

due to forbidden parameters inthe message.

countTotal number of messages thatcontained the forbidden

MSCRNPAFP

parameter but were not rejecteddue to Screening action set asPASS.

countTotal number of messages,where an entry was not found in

MSCRNPANE

the MAP screening table but theMessage was not rejected asscreening action was marked asPASS (i.e., not rejected as Systemwide MAP Opcode action isPASS)

countTotal number of message thatgot rejected as Message MAP

MSCRNRJOP

Opcode was not found in theMAP Opcode table (system wideaction - DISCARD for the nonmatching OPCODEs)

countTotal number of messages thatwere selected by MAP Screening

MSCRNDUP

for the Duplicate screeningaction.

countTotal number of messages thatewere selected by MAP Screeningfor the Forward screening action.

MSCRNFOR

countTotal number of messages thatewere selected by MAP Screening

MSCRNDAD

for the Duplicate and Discardscreening action.




ReportsMeasurements

Server Entity Identification information in Table 84: Server Entity Identification is used to clarify theserver. The Maintenance MAP Screening Per Server Measurements are applicable.

Table 84: Server Entity Identification

DescriptionEntity Name

The screened origination address of the callingparty address (CGPA) assigned when the GSMMAP screen was entered.

SERVER

The screened number plan value (NPV) assignedto the server address when the GSM MAP screen

NP

was entered. This field is filled with the defaultidentifier * if no value was assigned.

The screened nature of address value (NAIV)assigned to the server address when the GSM

NAI

MAP screen was entered. This field is filled withthe default identifier * if no value was assigned.

The operation code number assigned when theGSM MAP opcode was entered.

OPCODE

Measurements does not report entries created fora range of addresses.

Server Path Entity Identification information in Table 85: Path Entity Identification is used to clarify thepath. The Maintenance MAP Screening Per Path Measurements are applicable.

Table 85: Path Entity Identification


The screened origination address of the callingparty address (CGPA-NP-NAI), or a combination

PATH

of screened destination address of the called partyaddress (CDPA-NP-NAI) and the screenedorigination addresses assigned when the GSMMAP screen was entered.

The possible fields within the path are delimitedas follows to allow for efficient sorting:

• When both the origination and destinationaddresses are present (as either single serverentries or provisioned wildcard entries) theorigination address is preceded by a carat (^) andthe destination address is preceded by a "greaterthan" sign (>):

^CGPA-NP-NAI>CDPA-NP-NAI


ReportsMeasurements


• When only the origination address is present(occurs when the CDPA is a default wildcard) itis preceded by a "less than" sign (<):

<CGPA-NP-NAI

The calling party global title address assignedwhen the GSM MAP screen was entered. Any or

CGPA

all of the three fields (GTA, NP, NAI) can be filledwith the identifier (*) if a wildcard value isassigned for that field. There is no defaultwildcard value for the CGPA.

The called party global title address assignedwhen the GSM MAP screen was entered. Any or

CDPA

all of the three fields (GTA, NP, NAI) can be filledwith the identifier (*) if a wildcard value isassigned for that field. If the CDPA value is notassigned, the default wildcard value, which is notprinted, is assumed.

The screened number plan value (NPV) assignedto the path address when the GSM MAP screen

NP

was entered. The identifier (*) is used to signify awildcard NP.

The screened nature of address value (NAIV)assigned to the path address when the GSM MAP

NAI

screen was entered. The identifier (*) is used tosignify a wildcard NAI.

The operation code number assigned when theGSM MAP opcode was entered. The identifier (*)is used to signify a wildcard opcode.

OPCODE

Note:

Measurements does not report entries created for a range of addresses.

Measurements does not report default wildcard CDPA address in entries containing them.

There can never be a default wildcard CGPA entry. All wildcard CGPA entries must be explicitlyprovisioned. There can never be an entry with only a CDPA path listed.

The string formats were designed to allow efficient automated post processing of measurementsreports. A brief note explaining the format is included in the report.


ReportsMeasurements

Table 86: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening Per ServerMeasurements



MSCRNPASS


MSCRNRJFP


countTotal number of messages perserver that were selected by

MSCRNDUP

MAP Screening for the Duplicatescreening action.


MSCRNFOR

MAP Screening for the Forwardscreening action.


MSCRNDAD



MSCRNPAFP




FTP Reports

Daily MAP Screening System Wide Measurements

FTP Example Output File Name: mtcd-map_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-21","00:00:58","EST ","DAILY MAINTENANCE MEASUREMENTS ON MAPSCRN


ReportsMeasurements

SYSTEM","LAST","2010-08-20","00:00:00","24:00:00",1

"STATUS","MSCRNPASS","MSCRNRJOP","MSCRNRJNE","MSCRNRJFP","MSCRNPAFP","MSCRNPANE","MSCRNFOR","MSCRNDUP","MSCRNDAD""K",0,0,0,0,0,0,0,0,0,


Table 87: Typical File Size: mtcd-map.csv


header

426 bytes=60+116+250

Daily MAP Screening Measurements Per Path

FTP Example Output File Name: mtcd-path_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-21","00:00:59","EST ","DAILY MAINTENANCE MEASUREMENTS ON MAPSCRN PER-SERVER","LAST","2010-08-20","00:00:00","24:00:00",11

"For a path containing CGPA only, PATH-OPCODE = <CGPA-NP-NAI-OPCODE""For a path containing both CGPA and CDPA, PATH-OPCODE = ^CGPA-NP-NAI>CDPA-NP-NAI-OPCODE"

"STATUS","PATH-OPCODE","MSCRNPASS","MSCRNRJFP","MSCRNFOR","MSCRNDUP","MSCRNDAD","MSCRNPAFP""K","<123456789012345-*-*-0",0,0,0,0,0,0"K","<234567890123456-*-*-0",0,0,0,0,0,0"K","<345678901234567-*-*-0",0,0,0,0,0,0"K","<456789012345678-*-*-0",0,0,0,0,0,0"K","<567890123456789-*-*-0",0,0,0,0,0,0"K","<678901234567890-*-*-0",0,0,0,0,0,0"K","<789012345678901-*-*-0",0,0,0,0,0,0"K","<123456789012345-*-*-1",0,0,0,0,0,0"K","<234567890123456-*-*-1",0,0,0,0,0,0"K","<345678901234567-*-*-1",0,0,0,0,0,0"K","<456789012345678-*-*-1",0,0,0,0,0,0


4 char status + 40 char PATH-OPCODE + 6*(6 char data) + 2 = 82 chars

For a report of 20 paths, the typical file size is:

Table 88: Typical File Size: mtcd-path.csv


header

2141 bytes=1640+251+250


ReportsMeasurements

SCTPASOC MTCD Report

Command Examples

• UI:rept-meas:type=mtcd:enttype=sctpasoc:aname=assoc1

• FTP:rept-ftp-meas:type=mtcd:enttype=sctpasoc

Measurement Events

Table 89: Daily Maintenance (MTCD) and Day-to-Hour (MTCDTH) SCTPASOC Measurements lists theSCTPASOC events and their descriptions.

Table 89: Daily Maintenance (MTCD) and Day-to-Hour (MTCDTH) SCTPASOC Measurements


peg countSCTP Association ActiveEstablishments - The number of

ACTVESTB

times that SCTP associationshave made a direct transition tothe ESTABLISHED state fromthe COOKIEECHOED state(COOKIE-ECHOED -->ESTABLISHED). In this case theupper layer (i.e., the local M2PA)was the initiator of theassociation establishmentbetween the SCTP peers.


ASMAXRTO



ASOCABTD



ReportsMeasurements



ASOCSHTD



CNTLCHKR



CNTLCHKS

chunks sent to the remote peer(excluding retransmissions) afteran association has been formed.



DATCHKRC



DATCHKSN

peg countDuration the association was notin the Established state.

DURASNEST


ECASNEST


GAPACKSR

Acknowledgement blocks inSelective Acknowledgement(SACK) control chunks receivedfrom the remote SCTP peer,indicating gaps in the peer’sreceived subsequences of DATAchunks as represented by their


ReportsMeasurements


Transport Sequence Numbers(TSNs) (The inclusion of thismeasurement is intended toallow network personnel toassess the message-deliveryperformance of the IPVHSLrelative to gap acknowledgmentlimits, if used as performancecriteria for link proving andin-service monitoring).


ORDCHKRC



ORDCHKSN


peg countSCTP Association PassiveEstablishments - The number of

PASVESTB

times that SCTP associationshave made a direct transition tothe ESTABLISHED state fromthe CLOSED state (CLOSED -->ESTABLISHED), indicating thatthe remote peers initiatedassociation establishment.


PEERFAIL

of peer endpoint failuredetection events for theassociation as triggered by thecrossing of threshold Assoc.Max. Retrans.


RTXCHNKS

number of SCTP data chunksretransmitted to the remoteSCTP peer. When T3-rtx expires,the DATA chunks that triggeredthe T3 timer will be re-sentaccording with theretransmissions rules. Every


ReportsMeasurements


DATA chunk that was includedin the SCTP packet that triggeredthe T3-rtx timer must be addedto the value of this counter.


SCOCTRCV



SCOCTSNT



SCPKTRCV


SCPKTRCV register excludes thepegging of SCTP Packetsreceived when no instance existson the card for any of the links,i.e., the association parameter"OPEN" has value "NO" for allthe links configured on the card.Also, excludes pegging of set upmessages (INIT andCOOKIE-ECHO) that are part ofassociation establishmentprocedure.


SCPKTSNT


SCPKTSNT register excludesinitial SCTP association set-upmessages (INIT-ACK andCOOKIE-ACK) and ABORTmessages. For M2PA associationINIT packet is never pegged.


ReportsMeasurements




UI Reports

UI Example Output:

stdcfg2b 07-12-31 06:07:04 EST UNKNOWN 38.0.0-XX.XX.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON SCTPASOC REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:00:00 THRU 23:59:59

SCTPASOC-MTCD MEASUREMENTS: ASSOC: assoc1

These measurements are from 07-12-31, 00:00:00 through 23:59:59. ECASNEST = 0, DURASNEST = 0, DATCHKSN = 0, RTXCHNKS = 0, DATCHKRC = 0, SCPKTSNT = 20, SCPKTRCV = 20, SCOCTSNT = 0, SCOCTRCV = 0, CNTLCHKS = 400, ORDCHKSN = 400, CNTLCHKR = 0, ORDCHKRC = 0, GAPACKSR = 0, ACTVESTB = 0, PASVESTB = 0, ASOCABTD = 0, ASOCSHTD = 0, PEERFAIL = 0, ASMAXRTO = 0

;

FTP Reports

Table 90: FTP MTCD/MTCDTH SCTPASOC Column Header


Associationname

ASSOC

FTP Example Output File Name:mtcd-sctpasoc_20071115_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"ipmeas","UNKNOWN ??.?.?-58.21.0","2007-08-18","00:00:18","****","DAILY MAINTENANCE MEASUREMENTS ON SCTPASOC","LAST","2007-08-17","00:00:00","24:00:00",3<cr><lf>"STATUS","ASSOC","ECASNEST","DURASNEST","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","GAPACKSR","ACTVESTB","PASVESTB","ASOCABTD","ASOCSHTD","PEERFAIL","ASMAXRTO"<cr><lf>

"K","A1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


ReportsMeasurements

"K","A1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","A1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 18 char association + 20*(6 char data) + 2 = 144 chars

For a report of 1000 associations, typical file size is:

Table 91: Typical File Size: mtcd-sctpasoc.csv


Systemheader

144445 bytes=144000+195+250

SCTPCARD MTCD Report

Command Examples

• UI:rept-meas:type=mtcd:enttype=sctpcard:loc=1201

• FTP:rept-ftp-meas:type=mtcd:enttype=sctpcard

Measurement Events

Table 92: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARD Measurementslists the SCTPCARD events and their descriptions.

Table 92: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARDMeasurements



ACTVESTB



ASOCABTD

associations have made a directtransition to the CLOSED state


ReportsMeasurements


from any state using theprimitive “Abort” (AnyState--Abort--> CLOSED), conveyingan ungraceful termination of theassociation.


ASOCSHTD



CNTLCHKR



CNTLCHKS

chunks sent to the remote peer(excluding retransmissions),including chunks for which anassociation has not yet beenformed.


DATCHKRC



DATCHKSN


ORDCHKRC



ORDCHKSN



ReportsMeasurements



PASVESTB



RTXCHNKS



SCOCTRCV



SCOCTSNT

comprising SCTP packetssubmitted to the IP layer fortransmittal to the remote peer,including packets for which anassociation has not been formed.


SCPKTRCV


SCPKTRCV register excludes thepegging of SCTP Packetsreceived when no instance existson the card for any of theassociations, i.e., the association


ReportsMeasurements


parameter "OPEN" has value"NO" for all the associationsconfigured on the card. Also,excludes pegging of set upmessages (INIT andCOOKIE-ECHO) that are part ofassociation establishmentprocedure.

peg countSCTP Packets Received WithChecksum Error - The number

SCPKTRER

of SCTP packets received fromremote peers with an invalidchecksum


SCPKTSNT





peg countUnassociated (Out-of-the-Blue)SCTP Packets - The number of

UNASCTPK


UNASCTPK register includesthe pegging of SCTP Packetsreceived when no instance existson the card for any of the


ReportsMeasurements


associations, i.e., the associationparameter "OPEN" has value"NO" for all the associationsconfigured on the card (SeeSCPKTRCV register).

UI Reports

UI Example Output:

stdcfg2b 07-12-31 EST UNKNOWN 38.0.0-XX.XX.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON SCTPCARD REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:00:00 THRU 23:59:59

SCTPCARD-MTCD MEASUREMENTS: LOC: 1201

These measurements are from 07-12-31, 00:00:00 through 23:59:59. DATCHKSN = 0, RTXCHNKS = 0, DATCHKRC = 0, SCPKTSNT = 20, SCPKTRCV = 20, SCPKTRER = 0, UNASCTPK = 0, SCOCTSNT = 0, SCOCTRCV = 0, CNTLCHKS = 400, ORDCHKSN = 400, CNTLCHKR = 0, ORDCHKRC = 0, ACTVESTB = 0, PASVESTB = 0, ASOCABTD = 0, ASOCSHTD = 0

;

FTP Reports

FTP Example Output File Name: mtcd-sctpcard_20071115_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp",”38.0.0-XX.XX.0”,”2007-12-31”,"12:12:10","EST","DAILY MAINTENANCE MEASUREMENTS ON SCTPCARD","LAST",”2007-12-30”,"00:00:00","24:00:00",3<cr><lf><cr><lf>"STATUS","LOC","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCPKTRER","UNASCTPK","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","ACTVESTB","PASVESTB","ASOCABTD","ASOCSHTD"<cr><lf>"K","1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>



For a report of 80 cards, typical file size is:


ReportsMeasurements

Table 93: Typical File Size: mtcd-sctpcard.csv


Systemheader

9635 bytes=9200+185+250

UA MTCD Report

Command Examples

• UI:rept-meas:type=mtcd:enttype=ua:aname=assoc1:asname=appsrvr1

• FTP:rept-ftp-meas:type=mtcd:enttype=ua

Measurement Events

Table 94: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) UA Measurements liststhe UA events and their descriptions.

Table 94: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) UA Measurements



RXDATAMS

messages received from theASP.

For SUA, this register representsthe total of CLDT and CLDRmessages received from theASP.

octetsFor M3UA, this registerrepresents the number of DATAoctets received from the ASP.

RXDATAOC

For SUA, this register representsthe total of CLDT and CLDRoctets received from the ASP.


RXMLRCMS





ReportsMeasurements



peg countFor M3UA, this registerrepresents the number of DATAmessages sent to the ASP.

TXDATAMS

For SUA, this register representsthe total of CLDT and CLDRmessages sent to the ASP.

octetsFor M3UA, this registerrepresents the number of DATAoctets sent to the ASP.

TXDATAOC

For SUA, this register representsthe total of CLDT and CLDRoctets sent to the ASP.


UAASPMRX

peg countTotal ASPM messages sent tothe ASP (including ASPSM andASPTM messages).

UAASPMTX


UAASPNAC


UAASPNAT


UACNGCNT



UACNGTIM



UAMGMTRX


UAMGMTTX


ReportsMeasurements



UANMOCTR



UANMOCTT



UANMMSGR

ASP - The total number ofnon-DATA UA messagesreceived from the ASP (i.e., sumof the ASPM, ASPTM, SSNM,MGMT, and RKM).


UANMMSGT



UASSNMRX


UASSNMTX

UI Reports

stdcfg2b 07-12-31 06:07:04 EST UNKNOWN 38.0.0-XX.XX.0 UA-MTCD MEASUREMENTS: AS: appsrvr1 ASSOC: assoc1


;


ReportsMeasurements

FTP Reports

FTP Example Output File Name: mtcd-ua_20071114_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","37.5.0-58.25.0","2007-11-15","02:01:10","EST","DAILY MAINTENANCE MEASUREMENTS ON UA","LAST","2007-11-14","00:00:00","24:00:00",3<cr><lf><cr><lf>"STATUS","AS","ASSOC","RXDATAMS","TXDATAMS","RXDATAOC","TXDATAOC","RXMLRCMS","UAASPMRX","UAASPNAC","UAASPNAT","UACNGCNT","UACNGTIM","UAMGMTRX","UAMGMTTX","UANMOCTR","UANMOCTT","UANMMSGR","UANMMSGT","UASSNMRX","UASSNMTX","RXMLRCMS"<cr><lf>"K","as1101","a1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","as1102","a1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","as1103","a1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>



For a report of 1000 Application Servers, typical file size is:

Table 95: Typical File Size: mtcd-ua.csv


Systemheader

150000 bytes=150000+280+250

VFLEX MTCD Report

The enttype=vflex entity generates two separate reports per period. These reports are generated asCSV files and FTP'd to the customer FTP server. The command example will generate the followingdaily reports:

• Daily V-Flex System Wide Measurements

• Daily V-Flex Measurements Per SSP

Example Commands:

FTP: rept-ftp-meas:type=mtcd:enttype=vflex[:period=specific:day=xxx]

Table 96: Daily Maintenance V-Flex System Wide Measurements





ReportsMeasurements


peg countTotal number of IDP Connectresponses sent by VFLEX service.

VFCNCTRSP

peg countTotal number of IDP queriesreceived with errors (those

VFERRRSP

resulted in TCAP Error responsefrom VFLEX).

peg countTotal number of IDP queriesreceived for VFLEX service.

VFIDPQRCV

Table 97: Daily Maintenance V-Flex Per SSP Measurements




peg countTotal number of IDP queriesreceived for VFLEX service withinvalid MSISDN.

VFIMSISDN

peg countTotal number of IDP queriesreceived for VFLEX service withvalid MSISDN.

VFVMSISDN

FTP Reports

Daily V-Flex System Wide Measurements

FTP Example Output File Name: mtcd-vflex_20070816_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","37.6.0-58.20.0","2007-08-17","11:32:53","EST","DAILY MAINTENANCE MEASUREMENTS ON VFLEX SYSTEM","LAST","2007-08-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","VFIDPQRCV","VFCNCTRSP","VFERRRSP"<cr><lf>"K", 20,10,10<cr><lf>

Assuming each data line will be: 4 char status + 3*(6 char data) + 2 = 24 chars, the typical file size is:


ReportsMeasurements

Table 98: Typical File Size: mtcd-vflex.csv


header

347=24+45+260

Daily V-Flex Measurements Per SSPFTP Example Output File Name: mtcd-vflexssp_20070816_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""<cr><lf>"tekelecstp","37.6.0-58.20.0","2007-08-17","11:32:58","EST","DAILY MAINTENANCE MEASUREMENTS ON VFLEX SSP","LAST","2007-08-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS",“SSP”,“VFVMSISDN”,“VFIMSISDN”<cr><lf>“K”, “001-101-002”,10,10<cr><lf>

Note: The field identifier SSP designates the Service Switching Point.

Assuming each data line will be: 4 char status + 14 char SSP + 2*(6 char data) + 2 = 32 chars, the typicalfile size is:

Table 99: Typical File Size: mtcd-vflex-ssp.csv


header

297 + (32 *#PointCodes) bytes

=32 * #PointCodes

+40+257


Table 100: Typical File Size: mtcd-vflexssp.csv


header

6697 bytes=32 * 200+40+257

ATINPQ MTCD Report

The enttype=atinpq entity generates two separate reports per period. These reports are generated asCSV files and FTP'd to the customer FTP server. The command example will generate the followingdaily reports:

• Daily ATINPQ System Wide Measurements

• Daily ATINPQ Per SSP Measurements


ReportsMeasurements

Example Commands:

• FTP

rept-ftp-meas:type=mtcd:enttype=atinpq[:period=specific:day=xxx]

Measurement Events

Table 101: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ATINPQ Registers


peg countTotal number of ATINP queriesreceived for ATINPQ service.

ATINPQRCV

This peg is incremented only ifATINP feature is enabled andthe incoming message opcode isATI.

peg countTotal number of ATI ACKmessages sent by the ATINPQ

ATINPQACK

service. This peg is incrementedonly if the ATINP feature isenabled.

peg countTotal number of incoming ATImessages that did not result in

ATINPQERR

either ATI ACK or ATI NACKwith error code of eitherUnknown Subscriber or ATI NotAllowed. This peg isincremented only if the ATINPfeature is enabled.




PC TYPE

Daily ATINPQ Reports

System Wide Report

• Example Output File Name:

mtcd-atinpq_20080616_2400.csv


ReportsMeasurements

• Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","39.0.0-61.5.0","2008-06-17","11:32:53","EST","DAILY MAINTENANCE MEASUREMENTS ON ATINPQ SYSTEM","LAST","2008-06-17","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","ATINPQRCV","ATINPQACK","ATINPQERR"<cr><lf>"K", 20,10,10<cr><lf>

Assuming each data line will be: 4 char status + 3*(6 char data) + 2 = 24 chars, the typical file sizeis:

Table 102: Typical File Size: mtcd-atinpq.csv


header

347=24+45+260

Per SSP Report


mtcd-atinpqssp_20080616_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""<cr><lf>"tekelecstp","39.0.0-61.5.0","2008-06-17","11:32:58","EST","DAILY MAINTENANCE MEASUREMENTS ON ATINPQ SSP","LAST","2008-06-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS",“SSP”,“ATINPQRCV”,“ATINPQACK”,“ATINPQERR”<cr><lf>“K”, “001-101-002”,10,10,10<cr><lf>

Assuming each data line will be: 4 char status + 14 char SSP + 3*(6 char data) + 2 = 38 chars, thetypical file size is:



header

297 + (38 *#Point

Codes) bytes

=(38 * #PointCodes)

+40+257


Table 104: Typical File Size: atinpq 200 SSPs


header

7897 bytes=(38 * 200)+40+257


ReportsMeasurements

AIQ MTCD Report

The entity type for ANSI41 AIQ measurements is “AIQ”, which generates two reports per period. Thecommands to generate the daily on-demand measurement report can be specified with an optionalday parameter, xxx, providing a three-letter abbreviation for a day of the week (MON, TUE, WED,THU, FRI, SAT, or SUN). The specific period, period=specific, parameter is required when the optionalday parameter is used.

The measurements reports supported are:

• Per System Totals

• Per SSP Totals

The measurement report types supported are:

• Daily measurement report type "mtcd"

• Hourly measurement report type "mtch"

The on demand reports and scheduled reports are rejected until the AIQ feature is enabled. Thecommand chg-mtc-measopts:mtchaiq=on:mtcdaiq=on starts scheduled reports generation.Both on-demand and scheduled reports at hourly and daily boundary (MTCH and MTCD) generatetwo reports, namely Per System totals and Per SSP totals.

Example Commands:

• FTP: rept-ftp-meas:type=mtcd:enttype=aiq[:period=specific:day=xxx]

This command creates both the Per System and Per SSP Totals daily reports.

Measurement Events

Table 105: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) AIQ Registers


peg countTotal number ofAnalyzedInformation messages

AIQRCV

received for AIQ service. Thispeg is incremented only ifANSI41 AIQ feature is enabled.

peg countTotal number of Return Resultsent by the AIQ service. This peg

AIQSUCC

is incremented only if theANSI41 AIQ feature is enabled.

peg countTotal number of ANSI41 AIQqueries resulting in a negative

AIQERR

response (Return Error or Reject)generation by AIQ service. This


ReportsMeasurements


peg is incremented only if theANSI41 AIQ feature is enabled.


PC TYPE

Daily AIQ Reports

System Wide Report


mtcd-aiq_20090820_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","41.0.0-62.34.51","2009-08-20","11:32:53","EST","DAILY MAINTENANCE MEASUREMENTS ON AIQ SYSTEM","LAST","2009-08-20","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","AIQRCV","AIQSUCC","AIQERR"<cr><lf>"K",20,10,10<cr><lf>




header

322=24+38+260

Per SSP Report


mtcd-aiqssp_20090820_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""<cr><lf>"tekelecstp","41.0.0-62.34.51","2009-08-20","11:32:58","EST","DAILY MAINTENANCE MEASUREMENTS ON AIQ SSP","LAST","2009-08-19","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS",“SSP”,“AIQRCV”,“AIQSUCC”,“AIQERR”<cr><lf>“K”, “001-101-002”,20,10,10<cr><lf>



ReportsMeasurements

Table 107: Typical File Size: mtcd-aiq.csv


header

301 + ( 38 *#Point

=( 38 * #Pointcodes )

+44+257

Codes )bytes


Table 108: Typical File Size: aiq 200 SSPs


header

7901 bytes=( 38 * 200 )+44+257

GTTAPATH MTCD Report

The entity type for GTT Actions Per-Path measurements is “gttapath”, which generates two reportsper period. The commands to generate the daily on-demand measurement report can be specifiedwith an optional day parameter, xxx, providing a three-letter abbreviation for a day of the week (MON,TUE, WED, THU, FRI, SAT, or SUN). The specific period, period=specific, parameter is required whenthe optional day parameter is used.

The measurement report supported are:


• Per Path Totals


• Daily measurement report type “mtcd”

• Hourly measurement report type “mtch”

The on-demand reports and scheduled reports are rejected until the GTT Duplicate and/or Discardand/or Forward Action feature is enabled. Turning ON the feature is not required, because one of theregister “GTTACTNA” might get pegged in case GTT action fails because of the feature not being inthe ON state.

The command chg-mtc-measopts:mtchgttapath=on:mtcdgttapath=on starts scheduledreports generation. Both on-demand and scheduled reports at hourly and daily boundary (MTCHand MTCD) generate two reports: Per System Totals and Per-Path.

Example Commands:

FTP : rept-ftp-meas:type=mtcd:enttype=gttapath[:period=specific:day=xxx]where [:period=specific:day=xxx] is optional.


ReportsMeasurements

This example command creates both the Per-Path System Totals and the Per-Path Totals daily reports(the report date corresponds to the day entered in the command).

Table 109: MTCD/MTCH GTT Actions System-Wide Measurements



GTTADISC0



GTTADISC1



GTTADISC2



GTTADUP

of messages for which DuplicateMSU was sent. Multipleduplicate actions in an action setshall also increment this registeronly once.


GTTAFWD



GTTASET


GTTASRVGFLX


GTTASRVGPRT


GTTASRVSMSR


GTTASFLOG


ReportsMeasurements



GTTAMSVTO


GTTAMSVDI


GTTAMSVNA

Table 110: MTCD/MTCH GTT Actions Per-Path Measurements


pegcount

GTT Actions - The total number of messages for which no GTT action wassuccessfully performed.

GTTACTNA

This register shall be pegged for a message if either of these occurs:

• No GTT Action set was associated with the final GTT translation

• No GTT Action in the associated GTT Action set could be executedsuccessfully (for any reason).

pegcount

GTT Actions – MSUs Discarded - The total number of messages discarded bythe DISCARD GTT Action.

GTTADISC0

pegcount

GTT Actions – MSUs Discarded - The total number of messages discarded bythe UDTS GTT Action.

GTTADISC1

pegcount

GTT Actions – MSUs Discarded - The total number of messages discarded bythe TCAP Error GTT Action

GTTADISC2

pegcount

GTT Actions – MSUs Duplicated - The total number of messages for whichDuplicate MSU was sent.

GTTADUP

This register shall be pegged for a message only once for which either a singleor multiple duplicate GTT Actions were performed.

pegcount

GTT Actions – MSUs Forwarded - The total number of messages forwardedby Forward GTT Action.

GTTAFWD

pegcount

The total number of messages serviced by GFLEX GTT Action.GTTASRVGFLX

pegcount

The total number of messages serviced by GPORT GTT Action.GTTASRVGPRT

pegcount

The total number of messages serviced by SMSMR GTT Action.GTTASRVSMSR


ReportsMeasurements


pegcount

The total number of messages serviced by SFLOG GTT Action.GTTASFLOG

pegcount

The total number of messages that successfully pass SCPVAL GTT Action.GTTAMSVTO

pegcount

The total number of messages discarded by SCPVAL GTT Action.GTTAMSVDI

pegcount

The total number of messages where validation was not applied by SCPVALGTT Action.

GTTAMSVNA

Daily GTTAPATH ReportsThe command rept-ftp-meas:type=mtcd:enttype=gttapath produces the system-wide reportand the per-path report shown here.

System Wide Report

• Example Output File Name: mtcd-gttasys_20140228_2400.csv• Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 46.3.0.0.0-66.11.0","2015-10-06","00:10:33","EST ","DAILY MAINTENANCE MEASUREMENTS ON GTTACTION SYSTEM","LAST","2015-10-06","00:00:00","24:00:00",1

"STATUS","GTTADISC0","GTTADISC1","GTTADISC2","GTTADUP","GTTAFWD","GTTASET","GTTASRVGFLX","GTTASRVGPRT","GTTASRVSMSR","GTTASFLOG","GTTAMSVTO","GTTAMSVDI","GTTAMSVNA""K",0,0,0,0,0,0,0,0,0,0,0,0,0

Assuming each data line will be: 4 char status + 13 * (6 char data) + 2 = 84 chars, the typical file sizeis:

Table 111: Typical File Size: mtcd-gttasys.csv


header

501 bytes=84+167+250

Per Path Report

• Example Output File Name: mtcd-gttapath_20140124_2200.csv


ReportsMeasurements

Table 112: Entity Identification(PATH-CDSN-SCDGTA-CGSN-SCGGTA-OPSN-PKG-OPCODE-<A>/F)

DefinitionString Format

The GTT path name assigned when GTTACTpath was entered.

PATH

The called party global title translations set nameassigned when GTTACT path was entered.

CDSN

The called party start global title address(SCDGTA) assigned when GTTACT pathentered for a non-ranged entry

SCDGTA

or

The ranged called party start global title address(SCDGTA) and End global title address

SCDGTA->ECDGTA

(ECDGTA) assigned when the GTTACT pathwas entered.

The calling party global title translations setname assigned when GTTACT path was entered.

CGSN

The calling party start global title addressassigned when GTTACT path entered for anon-ranged entry

SCGGTA

or

The ranged calling party start global title address(SCGGTA) and End global title address

SCDGTA->ECDGTA

(ECGGTA) assigned when the GTTACT pathwas entered.

The global title translations set name of TCAPoperation code assigned when GTTACT pathwas entered

OPSN

The ANSI/ITU TCAP package type assignedwhen GTTACT Path was entered.

PKG

TCAP operation code assigned when GTTACTpath was entered.

OPCODE

‘<A>’ stands for Application Context Name(ACN) assigned when GTTACT path entered if

<A>/F

package type is ITU TCAP. It is preceded by a“less than” sign(<) and followed by a “greaterthan” sign (>).

‘F’ stands for ANSI TCAP family field assignedif package type is ANSI TCAP when GTTACTPath was entered.


ReportsMeasurements

DefinitionString FormatBackslash ‘/’ will not be displayed in the reportdata. Its only signifies that either <A> or F willbe displayed at a time based on the package typedisplayed in the PKG entry.

Note:

• If any entry has no value assigned then default value “#” will be displayed for it.

• These string formats allow efficient automated post processing of measurements reports; theyare not designed to be easily readable. A brief note explaining the format is included in thereport.


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 46.3.0.0.0-66.11.0","2015-09-06","00:10:35","EST ","DAILY MAINTENANCE MEASUREMENTS ON GTTACTION PER-PATH","LAST","2015-09-06","00:00:00","24:00:00",6

For a path containing GTA ranges, PATH-CDSN-SCDGTA-CGSN-CGGTA-OPSN-PKG-OPCODE-<A>/F = PATH-CDSN-SCDGTA->ECDGTA-CGSN-SCGGTA->ECGTA-OPSN-PKG-OPCODE-<A>/F"STATUS","PATH-CDSN-SCDGTA-CGSN-CGGTA-OPSN-PKG-OPCODE-<A>/F","GTTACTNA","GTTADISC0","GTTADISC1","GTTADISC2",""GTTADUP","GTTAFWD","GTTASRVGFLX","GTTASRVGPRT","GTTASRVSMSR","GTTASFLOG","GTTAMSVTO","GTTAMSVDI","GTTAMSVNA""K","path1-cdlim1-12345-cglim2-123-oplim3-ituuni-<1-1-1-1-1-1-1>",0,0,0,0,0,0,0,0,0,0,0,0,0"K","gttp5-#-#-cglim2-126-opname3-bgn-10",0,0,0,0,0,0,0,0,0,0,0,0,0"K","p6-#-#-cglim6-1234-#-#-#",0,0,0,0,0,0,0,0,0,0,0,0,0

Assuming each data line will be: 4 char status + 169 char(PATH-CDSN-SCDGTA-CGSN-CGGTA-OPSN-PKG-OPCODE-<A>/F) + 13 * (6 char data) + 2 =253 chars, the typical file size is:

Table 113: Typical File Size: mtcd-gttapath.csv

File Size=Report data(1000 paths)+Report

header+Systemheader

253,487bytes

=253,000+237+250

SIP MTCD Report

Example Commands:

UI: rept-meas:type=mtcd:enttype=sip

FTP:rept-ftp-meas:type=mtcd:enttype=sip


ReportsMeasurements



peg countThe total number of SIP invitereceived (Including re-transmits)

INVITERCVD

peg countNumber of cancel receivedCANCRCVD

peg countNumber of 1xx responses sentPROVRSPSENT

peg countNumber of 2xx responses sentOKRSPSENT

peg countNumber of 302 responses sentRDRCTSENT

peg countNumber of 4xx responses sentCLNFAILSENT

peg countNumber of 5xx responses sentSRVERRSENT

peg countNumber of SIP invite messagesfor which rxdb lookup was

NPSUCC

successfully performed andRN/ASD was found

peg countNumber of SIP invite messagesfor which rxdb lookup was notperformed

NPBYPASSSUC


INVALIDDN


NPRNNF

UI Example Output:

tekelecstp 13-01-11 00:07:56 EST EAGLE5 45.0.0-64.49.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON SIP REPORT PERIOD: LAST REPORT INTERVAL: 03-01-10, 00:00:00 through 23:59:59

SIP-MTCD MEASUREMENTS

INVITERCVD = 0, CANCRCVD = 0, PROVRSPSENT= 0, OKRSPSENT = 0, RDRCTSENT = 0, CLNFAILSENT= 0, SRVERRSENT = 0, NPSUCC = 0, NPBYPASSSUC= 0, INVALIDDN = 0, NPRNNF = 0

FTP Example Output File Name:mtcd-sip_20131004_2400.csv




ReportsMeasurements

"tekelecstp","EAGLE5 45.0.0-64.49.0","2013-01-11","00:10:54","EST ","DAILY MAINTENANCE MEASUREMENTS ON SIP","LAST","2013-01-10","00:00:00","24:00:00",1

"STATUS","INVITERCVD","CANCRCVD","PROVRSPSENT","OKRSPSENT","RDRCTSENT","CLNFAILSENT","SRVERRSENT","NPSUCC","NPBYPASSSUC","INVALIDDN","NPRNNF""K",0,0,0,0,0,0,0,0,0,0,0



Typical file size:

Table 115: Typical File Size: mtcd-sip.csv


SystemHeader

467 bytes=72+145+250

DEIR MTCD Report

The DEIR measurements specify the entity type deir and include two daily reports:

• Per system (DEIRSYS)• Per diameter connection (DEIRCONN)

Table 116: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) DEIR Measurements lists theevents added in all DEIR measurements reports.

The retention period is 7 days for the daily reports.


rept-ftp-meas:type=mtcd:enttype=deir

Table 116: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) DEIR Measurements


Peg countTotal number ofME-Identity-Check requests(ECR) received by the EIR.

ECRRCV

Peg countTotal number of searches thatresulted in a match with a "whitelisted" IMEI.

WHITEIMEI

Peg countTotal number of searches thatresulted in a match with a "graylisted" IMEI.

GRAYIMEI

Peg countTotal number of searches thatresulted in a match with a "blacklisted" IMEI.

BLACKIMEI


ReportsMeasurements


Peg countTotal number of searches thatresulted in a match with a "black

BLKALIMEI

listed" IMEI, but were alloweddue to IMSI Check match.


BLKNALIMEI

listed" IMEI, and the IMSI in thedatabase did not match the IMSIin the message.

Peg countTotal number of searches thatresulted in a match with an"unknown" IMEI.

UNKNIMEI

Peg countTotal number of searches thatresulted in no match in thedatabase.

NOMTCHIMEI

StatusIndication of Data Validity:STATUS

K - indicates good dataI - indicates incompleteintervalN - indicates data not current

Example Output File Names:

mtcd-deirsys_yyyymmdd_2400.csvDaily DEIR system totals measurements report

mtcd-deirconn_yyyymmdd_2400.csvDaily DEIR per diameter connectionmeasurements report

FTP example output file format for DEIR system total report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 45.1.0-64.74.1","2013-06-20","10:48:59 AM","MST ","DAILY MAINTENANCE MEASUREMENTS ON DEIR SYSTEM","SPECIFIC","2013-06-19","00:00:00","24:00:00",1

"STATUS","ECRRCV","WHITEIMEI","GRAYIMEI","BLACKIMEI","BLKALIMEI","BLKNALIMEI","UNKNIMEI","NOMTCHIMEI""K",23723,7687,0,16036,0,0,0,7687


4 char status + 8 * (6 char data) + 2 = 54 chars



ReportsMeasurements

Table 117: Typical File Size: mtcd-deirsys.csv


Systemheader

417 bytes=54+104+250

FTP example output file format for per diameter connection report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 45.1.0-64.74.1","2013-06-20","10:38:59 AM","MST ","DAILY MAINTENANCE MEASUREMENTS ON DEIR PER-CONNECTION","SPECIFIC","2013-06-19","00:00:00","24:00:00",5

"STATUS","DCNAME","ECRRCV","WHITEIMEI","GRAYIMEI","BLACKIMEI","BLKALIMEI","BLKNALIMEI","UNKNIMEI","NOMTCHIMEI""K","d1",100,100,0,0,0,0,0,0"K","d2",768,768,0,0,0,0,0,768"K","d3",0,0,0,0,0,0,0,0"K","d4",500,0,0,500,0,0,0,0"K","d5",1000,0,1000,0,0,0,0,0


4 char status + 18 char (Diameter connection) + 8 * (6 char data) + 2 = 72 chars


Table 118: Typical File Size: mtcd-deirconn.csv

File Size=

Report data(512

connections)

Reportheader

Systemheader

37227 bytes=36864 bytes+113+250

ENUM MTCD Report

The ENUM measurements specify the entity type enum and include four daily reports:

• Per system (ENUMSYS)

Table 119: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System LevelMeasurements lists the events added per system.

• Per card (ENUMCARD)

Table 120: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card Level Measurementslists the events added for each card.

• Per entity (ENUMENT)

Table 121: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity LevelMeasurements lists the events added for each entity ID in the entity ID table or each DN block inthe DN block profile table.

• Per ACL (ENUMACL)


ReportsMeasurements

Table 122: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL Level Measurementslists the events added for each ACL entry in the ACL table.

The retention period is 24 hours.


rept-ftp-meas:type=mtcd:enttype=enum

Table 119: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System LevelMeasurements


Peg countTotal number of ENUM queriesreceived

ENUMQRYRX

Peg countTotal number of NAPTR queriesreceived

ENUMNAPTRRX

Peg countTotal number of NS queriesreceived

ENUMNSRX

Peg countTotal number of CNAME queriesreceived

ENUMCNAMERX

Peg countTotal number of ENUM queriesrejected by ENUM server

ENUMQRYRJTD

Peg countTotal number of ENUM queriesdiscarded due to congestion

ENUMCNGDISC

Peg countTotal number of ENUM queriesdiscarded due to ACL validationfailure

ENUMACLDISC

Peg countTotal number of successfulENUM responses sent

ENUMTXRC0

Peg countTotal number of ENUM errorresponses sent due to ENUMquery format error

ENUMTXRC1

Peg countTotal number of ENUM errorresponses sent due to ENUMserver failure

ENUMTXRC2

Peg countTotal number of ENUM errorresponses sent due tonon-existent domain error

ENUMTXRC3

Peg countTotal number of ENUM errorresponses sent due to notimplemented error

ENUMTXRC4

Peg countTotal number of ENUM errorresponses sent due to refusal byENUM server

ENUMTXRC5


ReportsMeasurements


Peg countTotal number ENUM responsessent with default ENUM profile

ENUMTXDEFPR



Table 120: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card LevelMeasurements



ENUMCQRYRX


ENUMCNAPTRX


ENUMCNSRX


ENUMCCNAMRX


ENUMCQRRJTD


ENUMCCNGDSC


ENUMCACLDSC


ENUMCTXRC0


ENUMCTXRC1


ENUMCTXRC2


ENUMCTXRC3


ReportsMeasurements



ENUMCTXRC4


ENUMCTXRC5


ENUMCTXDEFP



Table 121: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity LevelMeasurements


Peg countTotal number of ENUM queriesreceived or ENUM responsessent per entity

ENUMENTMSGS



Table 122: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL LevelMeasurements



ENUMACLQRCV


ENUMACLQRJD


ENUMACLRC0


ENUMACLRC1


ReportsMeasurements



ENUMACLRC2


ENUMACLRC3


ENUMACLRC4


ENUMACLRC5




mtcd-enumsys_yyyymmdd_2400.csvDaily ENUM system totals measurements report

mtcd-enumcard_yyyymmdd_2400.csvDaily ENUM per card measurements report

mtcd-enument_yyyymmdd_2400.csvDaily ENUM per entity measurements report

mtcd-enumacl_yyyymmdd_2400.csvDaily ENUM per acl measurements report

FTP example output file format for system total report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:32","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM SYSTEM","LAST","2014-08-22","00:00:00","24:00:00",1

"STATUS","ENUMQRYRX","ENUMNAPTRRX","ENUMNSRX","ENUMCNAMERX","ENUMQRYRJTD","ENUMCNGDISC","ENUMACLDISC","ENUMTXRC0","ENUMTXRC1","ENUMTXRC2","ENUMTXRC3","ENUMTXRC4","ENUMTXRC5","ENUMTXDEFPR""K",2134,0,2134,0,0,0,0,2134,0,0,0,0,0,0





ReportsMeasurements

Table 123: Typical File Size: mtcd-enumsys.csv


Systemheader

529 bytes=90 bytes+189+250

FTP example output file format for per card report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:35","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM PER-CARD","LAST","2014-08-22","00:00:00","24:00:00",2

"STATUS","LOC","ENUMCQRYRX","ENUMCNAPTRX","ENUMCNSRX","ENUMCCNAMRX","ENUMCQRRJTD","ENUMCCNGDSC","ENUMCACLDSC","ENUMCTXRC0","ENUMCTXRC1","ENUMCTXRC2","ENUMCTXRC3","ENUMCTXRC4","ENUMCTXRC5","ENUMCTXDEFP""K","1101",2134,0,2134,0,0,0,0,2134,0,0,0,0,0,0"K","1105",0,0,0,0,0,0,0,0,0,0,0,0,0,0


4 char status + 7 char (card) + 14 * (6 char data) + 2 = 95 chars


Table 124: Typical File Size: mtcd-enumcard.csv

File Size=Report data(250 card)

Reportheader

Systemheader

24203 bytes=23750 bytes+203+250

FTP example output file format for per entity report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:33","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM PER-ENTITY","LAST","2014-08-22","00:00:00","24:00:00",2

"STATUS","ENTITY ID","SDN","EDN","ENUMENTMSGS""K","123456789012345","","",0"K","123456789123456","","",2134


4 char status + 3* (18 char Entity ID/SDN/EDN) + (6 char data) + 2 = 66 chars


Table 125: Typical File Size: mtcd-enument.csv

File Size=

Report data(1024

entries)

Reportheader

Systemheader

67882 bytes=67584 bytes+48+250


ReportsMeasurements

FTP example output file format for per ACL report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:34","MST ","DAILY MAINTENANCE MEASUREMENTS ON ENUM PER-ACL","LAST","2014-08-22","00:00:00","24:00:00",1

"STATUS","IP ADDRESS","ENUMACLQRCV","ENUMACLQRJD","ENUMACLRC0","ENUMACLRC1","ENUMACLRC2","ENUMACLRC3","ENUMACLRC4","ENUMACLRC5""K","10.*.*.*",2134,0,2134,0,0,0,0,0


4 char status + 18 char (IP Address) + 8 * (6 char data) + 2 = 72 chars


Table 126: Typical File Size: mtcd-enumacl.csv

File Size=Report data(100 entries)

Reportheader

Systemheader

7579 bytes=7200 bytes+129+250

SFTHROT MTCD Report

The entity type for SFTHROT measurements is SFTHROT, which generates one report per period.

The measurement report supported is:

• Per Throttling Action System Totals

The measurement report Type supported is:

• MTCD - Daily measurement report type

Example Commands:

FTP: rept-ftp-meas:type=mtcd:enttype=sfthrot



peg countThe total number of messagesserviced by a particularThrottling GTT Action.

GTTATHTO

peg countThe total number of messagesdiscarded because the Throttling

GTTATHDI

GTT Action was in BLOCKEDstate.

FTP Example Output File Name:mtcd-sfthrot_20150813_2400.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 46.3.0.0.0-66.8.0","8/14/2015","0:00:03","EST" , "DAILY MAINTENANCE MEASUREMENTS ON SFTHROT","LAST","8/13/2015","0:00:00","24:00:00",32<cr><lf>

"STATUS","THROTTLING ACTION","GTTATHTO","GTTATHDI"<cr><lf>"K","sf1",0,0<cr><lf>. . . . .

"K","sf32",0,0<cr><lf>


4 char status + 12 char TA + 2 * (6 char data) + 2 = 30 chars

Typical file size:

Table 128: Typical File Size: mtcd-sfthrot.csv

File Size=

Report Data(32

ThrottlingActions)+

ReportHeader+

SystemHeader

1262 bytes=960 bytes+52+250

Day-to-Hour Maintenance Measurements (MTCDTH)

The Maintenance Day-to-Hour (MTCDTH) report provides the current value of various maintenancemeasurements accumulating during the day.

Entity Types:STP, Link, Lnkset, STPLAN, SCTPASOC, SCTPCARD, UA

Accumulation Interval: Cumulative Daily Total to the last full hour.

STP Retention Period: 1 hour

Reporting Mode: On-demand

Accessible Collection Periods: Last

STP MTCDTH Report

Example Commands:

UI: rept-meas:type=mtcdth:enttype=stpFTP: rept-ftp-meas:type=mtcdth:enttype=stp


ReportsMeasurements



peg countCritical System Alarms - Thetotal number of critical systemalarms.

CRSYSAL

secondsCumulative DurationofSignaling Link DeclaredFailures All Types -

DRDCLFLR

The cumulative duration of alllink failures.

secondsDuration ofLink Outage - Thetotal time a link was unavailableto MTP level 3 for any reason.

DURLKOTG

peg countDTAMSUsLost - The totalnumber of MSUs that were

DTAMSULOST

discarded because the redirectfunction was turned off or theoriginal MSU was too large to beencapsulated.

peg countG-FlexGTTs with Match - Thetotal number of G-Flex Global

GFGTMATCH

Title Translation successfullycompleted.

peg countG-FlexGTTs No Match - Thetotal number of G-Flex Global

GFGTNOMCH



GFGTNOLKUP



GTTPERFD



ReportsMeasurements




GTTUN0NS

Address of Such Nature – Totalnumber of times that thespecified translation type in anMSU was not supported by theSTP or the form of the GTT wasincorrect for the giventranslation type. Also includesG-Flex, INP and GTT MSUs thatdid not match on new selectors(GTI,NP,NAI) in addition toones not matching on TT.


GTTUN1NT

This Address – The sum total oftimes that SCCP could not finda translation in the translationtable. This includes Global Titletranslations, Point Codetranslations, and Subsystemtranslations.

In general, this register containsthe sum of the GTTUN1NTregister in the systot-tt reportand the CGGTTUN1NT


MSIDPNOMCH


ReportsMeasurements



MSIDPMATCH


peg countMSUs Rcvd – InvalidDPC -MSINVDPC

Number of MSUs received anddiscarded because the DPCcould not be found in the STProuting table.


MSINVSIF



MSINVSIO


peg countMajor system alarms - The totalnumber of major system alarms.

MASYSAL

peg countMinor system alarms - The totalnumber of minor system alarms.

MISYSAL


MSINVLNK


peg countMSUs Discarded – InvalidSLC-

MSINVSLC

Number of MSUs discardedbecause of an invalid SLC codein the ECO/COO.

peg countMSUs Discarded –InaccessibleDPC -

MSNACDPC


ReportsMeasurements


The total number of MSUsdiscarded because of aninaccessible DPC.

peg countMSUs Discarded – RoutingFailure -

MSSCCPFL

Number of MSUs discarded dueto an SCCP routing failure. Alsoincludes G-Flex, INP MSUs thatgot a match from either theG-Flex, INP or GTT DB butcannot be routed due to PC or SScongestion, PC or SS unavailable,SS unequipped, or anunqualified error.

peg countMSUSCCP Failure - Total MSUsDiscarded Due to SCCPConversion Failure.

MSUSCCPFLR


MSUDSCRD

The total number of MSUs thatfailed gateway screening andwere discarded. See linksetreport for individual peg counts.


MSULOST1



MSULOST2



1. LS On Hold BufferOverflow - The number ofMSUs discarded because thelinkset-on-hold buffer was inoverflow. The On HoldBuffer is used duringchangeover/changebacksituations to ensure that


ReportsMeasurements


traffic is sequenced correctly.During changeover andchangeback, MSUs that wereoriginally sent over linkswhich are now failed (notIS-NR) are buffered while thechangeover/changebackprocedures are carried out.Once those procedures arecompleted, the traffic in theon-hold buffer is routedbased on the currentconfiguration.


3. HSL –





MSULOST4


peg countMSUs Discarded –LIM Init -MSULOST5

Number of MSUs discardedwhile the LIM card wasinitializing.

peg countMSUs Discarded – The numberof MSUs discarded due to an

MSULOST6


peg countMTP Restarts Initiated -Number of times MTP restart

MTPRESTS

was initiated by the STP. The


ReportsMeasurements


count does not include thenumber of MTP restarts initiatedas a result of messages fromadjacent nodes.

peg countMSUs Originated - Invalid DPC- The number of MSUsoriginated with an invalid DPC.

OMSINVDPC

peg countOriginatedMSUs -ORIGMSUS

The total number of outgoingMSUs successfully passed toMTP level 2 for transmission,while carrying the STP pointcode in the OPC field. For IPGWlinks, this register includescounts for managementmessages such as RST messages.This register is not an aggregateof link or linkset registers.


OVSZMSG

exceeding 272 octets (level 3) thatare received by an HSL and arediscarded.


SCCPLOOP







TRMDMSUS


ReportsMeasurements



peg countTranslation Type MappingTranslations Performed - The

TTMAPPF

total number of Translation TypeMapping translations performed(that is, a mapped SS7 messagetranslation type was found forthe existing SS7 messagetranslation type).


UDTXUDTF



XLXTELEI

X-List entry was not createdbecause the ELEI for the clusterwas set to ‘yes’.

peg countX-List Entry Not Created - Thetotal number of times an X-List

XLXTSPACE

entry was not created due to lackof space in the route/destinationtable.

UI Reports

UI Example Output:

e1061001 11-01-23 01:10:37 MST EAGLE5 43.0.0-63.49.0 TYPE OF REPORT: DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON STP REPORT PERIOD: LAST REPORT INTERVAL: 11-01-23, 00:00:00 THROUGH 00:59:59

STP-MTCDTH MEASUREMENTS

These measurements are from 11-01-23, 00:00:00 through 00:59:59. ORIGMSUS = 0, TRMDMSUS = 0, THRSWMSU = 0, MTPRESTS = 0, DTAMSULOST = 0, MSINVDPC = 0, MSINVSIO = 0, OMSINVDPC = 0, MSINVLNK = 0, MSINVSIF = 0, MSNACDPC = 0, MSINVSLC = 0, GTTPERFD = 0, GTTUN0NS = 0, GTTUN1NT = 0, MSSCCPFL = 0, MSULOST1 = 0, MSULOST2 = 0, MSULOST3 = 0, MSULOST4 = 0, MSULOST5 = 0, DRDCLFLR = 0, DURLKOTG = 888, CRSYSAL = 2, MASYSAL = 3, MISYSAL = 19, XLXTSPACE = 0, XLXTELEI = 0, TTMAPPF = 0, MSUDSCRD = 0, OVSZMSG = 0, GFGTMATCH = 0, GFGTNOMCH = 0, GFGTNOLKUP = 0, MSUSCCPFLR = 0, MSSCCPDISC = 0,


ReportsMeasurements

MSIDPNOMCH = 0, MSIDPMATCH = 0, MSULOST6 = 0, SCCPLOOP = 0, UDTXUDTF = 0

;

FTP Reports

FTP Example Output File Name: mtcdth-stp_19990117_1500.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 43.0.0-63.49.0","2011-01-23","01:11:39","MST ","DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON STP","LAST","2011-01-23","00:00:00","01:00:00",1

"STATUS","ORIGMSUS","TRMDMSUS","THRSWMSU","MTPRESTS","DTAMSULOST","MSINVDPC","MSINVSIO","OMSINVDPC","MSINVLNK","MSINVSIF","MSNACDPC","MSINVSLC","GTTPERFD","GTTUN0NS","GTTUN1NT","MSSCCPFL","MSULOST1","MSULOST2","MSULOST3","MSULOST4","MSULOST5","DRDCLFLR","DURLKOTG","CRSYSAL","MASYSAL","MISYSAL","XLXTSPACE","XLXTELEI","TTMAPPF","MSUDSCRD","OVSZMSG","GFGTMATCH","GFGTNOMCH","GFGTNOLKUP","MSUSCCPFLR","MSSCCPDISC","MSIDPNOMCH","MSIDPMATCH","MSULOST6","SCCPLOOP","UDTXUDTF""K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,888,2,3,19,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

Typical file size:

Table 130: Typical File Size: mtcdth-stp.csv


header

985 bytes=252+583+250

LINK MTCDTH Report

Certain registers are reported for MTP2, SAAL, IPVL, and IPVHSL classes. These registers aresummarized in Table 131: Registers Reported per LINK CLASS for Daily (MTCD) and Day-To-Hour(MTCDTH) Link Measurements.

Table 131: Registers Reported per LINK CLASS for Daily (MTCD) and Day-To-Hour (MTCDTH)Link Measurements


XXXXXACHGOVRS

XXDRBSYLNK

XXXXXDRDCLFLR

XXDRFEPRO

XXXXXDRLCLPRO

XXXDRLKINHB


ReportsMeasurements


XXXXXECCNGLV1

XXXXXECCNGLV2

XXXXXECCNGLV3

XECLNKCB

XECLNKXCO

XXXFARMGINH

XXXLMSUOCTRCV

XXXLMSUOCTTRN

XXXLMSURCV

XXXLMSURCVDSC

XXXLMSUTRN

XXXLMSUTRNDSC

XXXXXLNKAVAIL

XM2PLKNIS

XM2PUDMRC

XM2PUDMTR

XM2PUDOCR

XM2PUDOCT

XXXXXMOCTRCVD

XXXXXMOCTTRAN

XXXXXMSGDISC0

XXXXXMSGDISC1

XXXXXMSGDISC2

XXXXXMSGDISC3

XXXXXMSGSRCVD

XXXXXMSGSTRAN

XMSURCERR


ReportsMeasurements


XMSURETRN

XNDCFLABN

XXXNDCFLXDA

XXXNDCFLXDC

XXNDCFLXER

XXXNEARMGIH

XNEGACKS

XXXXXNMLCLPRO

XXXXXNMDCLFLR

XXNMFEPRO

XOCTRETRN

XPCRN1N2EXC

XSDPDURTR

XXXXXTDCNGLV1

XXXXXTDCNGLV2

XXXXXTDCNGLV3

XXXXXTLNKACTV

Command Examples

• UI

rept-meas:type=mtcdth:enttype=link:loc=xxxx:link=x

rept-meas:type=mtcdth:enttype=link:lsn=lsn123

• FTP

rept-ftp-meas:type=mtcdth:enttype=link


ReportsMeasurements

Measurement Events

Table 132: Maintenance Daily (MTCD) and Maintenance Day-to-Hour (MTCDTH) LinkMeasurements


peg countNumber of AutomaticChangeovers - Number of times

ACHGOVRS

that a changeover procedure wasused to divert traffic from onelink to alternative links.


DRBSYLNK

The total elapsed time betweenthe receipt of a busy LSSU, andwhen the next message wasacknowledged. This is the sumof all occurrences of busy linkstatus. Reported for MTP2 Linksonly.


DRDCLFLR



DRFEPRO

The cumulative duration that alink was unavailable to MTPlevel 3 because of a processoroutage at the far-end networkelement (SIPO received).Reported for MTP2 and IPVHSLclass links ONLY.


DRLCLPRO


secondsDuration Link Inhibited - Thecumulative duration that a link

DRLKINHB

was inhibited at the local orfar-end network element.


ReportsMeasurements



ECCNGLV1



ECCNGLV2



ECCNGLV3



ECLNKCB



ECLNKXCO


peg countNumber of Far-EndManagement Inhibits - Number

FARMGINH

of times a link was inhibitedsuccessfully from the far-end.


LMSUOCTRCV

pegged in addition toMOCTRCVD when the LargeMSU Support for IP Signalingfeature status is on and a largeMSU is successfully received.


LMSUOCTTRN



LMSURCV

in addition to MSGSRCVD when


ReportsMeasurements


the Large MSU Support for IPSignaling feature status is on anda large MSU is successfullyreceived.


LMSURCVDSC



LMSUTRN


peg countThe number of large MSUsdiscarded in the transmit path.

LMSUTRNDSC


LNKAVAIL


M2PLKNIS

was not in the in-service (INS)state at the M2PA layer (inseconds), i.e., during which thelink was in any of the otherdefined M2PA states (such asIDLE, OOS, AIP, PROVING,ALIGNED READY, orRETRIEVAL).


M2PUDMRC


M2PUDMTR


M2PUDOCR


M2PUDOCT


ReportsMeasurements






MOCTTRAN

with MSUs transmitted to thefar-end. For all linkset classes,this includes octets for MTP level3 SIO and SIF.





MSGDISC0



ReportsMeasurements



Note: EAGLE supports this oneITU discard counter only. Whenthe discard threshold is reached,all MSUs are discarded andcounted in this register. Prior tothe discard threshold beingreached, no MSUs are discarded.



MSGDISC1






MSGDISC2




ReportsMeasurements





MSGDISC3






MSGSRCVD


• For SAAL, IPVL, IPVHSL,and IPVLGW class linksets -applies to MTP level 3messages.




ReportsMeasurements




peg countNumber of Message signalUnits received in error - bad

MSURCERR

CRC. This register applies toMTP2 links only.

peg countMSUs Retransmitted - Numberof MSUs retransmitted becauseof errors.

MSURETRN

peg countNumber of Signaling LinkFailures - Abnormal FIB/BSN -

NDCFLABN

The number of times thesignaling link was takenout-of-service because ofabnormal FIB/BSN received. Acount was accumulated if twobackward sequence numbervalues in three consecutivelyreceived MSUs or FISUs are notthe same as the previous one orany of the forward sequencenumbers of the signal units inthe retransmission buffer at thetime they are retransmitted.Reported for MTP2 links only.Occurrences of this conditionwhile the link is not in-serviceare not accumulated in thisregister.

peg countNumber of Signaling LinkFailures - Excessive Delay of

NDCFLXDA

Acknowledgment - Number oftimes a signaling link wasout-of-service due to anexcessive delay inacknowledgments.


ReportsMeasurements


• For MTP2and IPVHSL classlinks, level 2 t7 expired level

• For SAAL class links, timerNO_RESPONSE expired forPOLL/STAT response


peg countNumber of Signaling LinkFailures - Excessive Duration ofCongestion

NDCFLXDC

• For MTP2 and IPVHSL classlinks, the number of times asignaling link wasout-of-service because theLevel 2 timer T6 (remotecongestion) expired

• For SAAL class links, thenumber of times timerNO_CREDIT expired


peg countNumber of Signaling LinkFailures - Excessive Error Rate

NDCFLXER

- Number of times a signalinglink was out-of-service becauseit reached the signal unit errorrate monitor (SUERM) threshold.Reported for MTP2 and SAALlinks only.


NEARMGIH

of times a link was unavailableto MTP level 3 because it waslocally inhibited. Not reportedfor IPVL and IPVLGW classlinks.

peg countNumber of NegativeAcknowledgments Received

NEGACKS

-Number of times the BSN in anMSU was inverted, indicating aretransmission request. Thisregister is NOT applicable toHSLs.


ReportsMeasurements


peg countNumber of Local ProcessorOutages - The total number of

NMLCLPRO

local processor outages in thisSTP.

peg countNumber ofSignalingLinkDeclared Failures All

NMDCLFLR

Types - The cumulative total ofall link failures.


NMFEPRO

Number of far-end processoroutages that have occurred.Reported for MTP2 links only

peg countNumber of MSU octetsretransmitted. This register is

OCTRETRN

NOT reported for SAAL classlinks.


PCRN1N2EXC

retransmissions when preventivecyclic retransmission (PCR) isused as the error correctionmethod on a link. This registeris not applicable to HSLs.


SDPDURTR

sequenced Data PDUs that wereretransmitted, based on anaccumulated count of suchretransmissions conveyed to LM.This measurement replaces theMTP level 2 negativeacknowledgments.




TDCNGLV1


ReportsMeasurements



TDCNGLV2


TDCNGLV3

secondsLink active time - total time thelink is active and transmittingMSUs.

TLNKACTV

• For SAAL class links, thetime the link is active andgiving MSUs to SAAL fortransmission.

• For IP7 links, TLNKACTV isbased on 10MB Ethernet linkspeed. Hence the report willbe relative to 10MB/sec.

UI Reports

• rept-meas:type=mtcdth:enttype=link:loc=xxxx:link=x

tekelecstp 12-02-12 00:07:37 EST EAGLE5 44.0.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-02-11 00:00:00 THRU 23:59:59

LINK-MTCD MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)

MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, NEGACKS = 0, DRLKINHB = 0, NDCFLABN = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, MSURCERR = 0, DRBSYLNK = 0, PCRN1N2EXC = 0

;

tekelecstp 12-02-12 00:07:40 EST EAGLE5 44.0.0 LINK-MTCD MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0,


ReportsMeasurements

LNKAVAIL = 0, ACHGOVRS = 0, NMDCLFLR = 0, DRDCLFLR = 0, NMLCLPRO = 0, DRLCLPRO = 0, LMSUTRN = 0, LMSURCV = 0, LMSUOCTTRN = 0, LMSUOCTRCV = 0, LMSUTRNDSC = 0, LMSURCVDSC = 0

;

tekelecstp 12-02-12 00:07:42 EST EAGLE5 44.0.0 LINK-MTCD MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, NEGACKS = 0, DRLKINHB = 0, NDCFLABN = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, MSURCERR = 0, DRBSYLNK = 0, PCRN1N2EXC = 0

;

tekelecstp 12-02-12 00:07:44 EST EAGLE5 44.0.0 LINK-MTCD MEASUREMENTS: LOC: 1105, LINK: A , LSN: ssedcm1 (IPVHSL)

MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, DRLKINHB = 0, NDCFLXDA = 0, NDCFLXDC = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, DRBSYLNK = 0, LMSUTRN = 0, LMSURCV = 0, LMSUOCTTRN = 0, LMSUOCTRCV = 0, LMSUTRNDSC = 0, LMSURCVDSC = 0, M2PUDMTR = 0, M2PUDOCT = 0, M2PUDMRC = 0, M2PUDOCR = 0, M2PLKNIS = 1281, ECLNKCB = 0, ECLNKXCO = 0

;

tekelecstp 12-02-12 00:07:46 EST EAGLE5 44.0.0 LINK-MTCD MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)

MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NMLCLPRO = 0, DRLCLPRO = 0, SDPDURTR = 0

;


ReportsMeasurements

• rept-meas:type=mtcdth:enttype=link:lsn=xxx

tekelecstp 12-02-12 00:10:12 EST EAGLE5 44.0.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON LINK REPORT PERIOD: LAST REPORT INTERVAL: 12-02-11, 00:00:00 THROUGH 23:59:59

LINK-MTCD MEASUREMENTS FOR LINKSET mtp2:

LINK-MTCD MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

These measurements are from 12-02-11, 00:00:00 through 23:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, NEGACKS = 0, DRLKINHB = 0, NDCFLABN = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, MSURCERR = 0, DRBSYLNK = 0, PCRN1N2EXC = 0

;


LINK-MTCD MEASUREMENTS FOR LINKSET ipsg:

LINK-MTCD MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

These measurements are from 12-02-11, 00:00:00 through 23:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MSURETRN = 0, OCTRETRN = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, NEGACKS = 0, DRLKINHB = 0, NDCFLABN = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, MSURCERR = 0, DRBSYLNK = 0, PCRN1N2EXC = 0

;


LINK-MTCD MEASUREMENTS FOR LINKSET saal:

LINK-MTCD MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


ReportsMeasurements

These measurements are from 12-02-11, 00:00:00 through 23:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NMDCLFLR = 0, DRDCLFLR = 0, NMLCLPRO = 0, DRLCLPRO = 0, LMSUTRN = 0, LMSURCV = 0, LMSUOCTTRN = 0, LMSUOCTRCV = 0, LMSUTRNDSC = 0, LMSURCVDSC = 0

;


LINK-MTCD MEASUREMENTS FOR LINKSET ssedcm1:

LINK-MTCD MEASUREMENTS: LOC: 1105, LINK: A , LSN: ssedcm1 (IPVHSL)

These measurements are from 12-02-11, 00:00:00 through 23:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, SURCVERR = 0, DRLKINHB = 0, NDCFLXDA = 0, NDCFLXER = 0, NDCFLXDC = 0, NMLCLPRO = 0, DRLCLPRO = 0, SDPDURTR = 0

;


LINK-MTCD MEASUREMENTS FOR LINKSET hcmimt1:

LINK-MTCD MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)

These measurements are from 12-02-11, 00:00:00 through 23:59:59. MSGSTRAN = 0, MSGSRCVD = 0, MOCTTRAN = 0, MOCTRCVD = 0, TDCNGLV1 = 0, TDCNGLV2 = 0, TDCNGLV3 = 0, ECCNGLV1 = 0, ECCNGLV2 = 0, ECCNGLV3 = 0, MSGDISC0 = 0, MSGDISC1 = 0, MSGDISC2 = 0, MSGDISC3 = 0, TLNKACTV = 0, LNKAVAIL = 0, ACHGOVRS = 0, NEARMGIH = 0, FARMGINH = 0, NMDCLFLR = 0, DRDCLFLR = 0, DRLKINHB = 0, NDCFLXDA = 0, NDCFLXDC = 0, NMFEPRO = 0, NMLCLPRO = 0, DRFEPRO = 0, DRLCLPRO = 0, DRBSYLNK = 0, LMSUTRN = 0, LMSURCV = 0, LMSUOCTTRN = 0, LMSUOCTRCV = 0, LMSUTRNDSC = 0, LMSURCVDSC = 0, M2PUDMTR = 0, M2PUDOCT = 0, M2PUDMRC = 0, M2PUDOCR = 0, M2PLKNIS = 0, ECLNKCB = 0, ECLNKXCO = 0


ReportsMeasurements

;

FTP Reports

Table 133: FTP MTCDTH LINK Command Headers


Linksetname

LSN

Cardlocation

LOC

Link portLINK

Link typeLNKTYPE

FTP Example Output File Name: mtcdth-link_20101004_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-12","00:14:53","EST ","DAILY MAINTENANCE MEASUREMENTS ON LINK","LAST","2012-02-11","00:00:00","24:00:00",5<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","MSGSTRAN","MSGSRCVD","MSURETRN","OCTRETRN","MOCTTRAN","MOCTRCVD","TDCNGLV1","TDCNGLV2","TDCNGLV3","ECCNGLV1","ECCNGLV2","ECCNGLV3","MSGDISC0","MSGDISC1","MSGDISC2","MSGDISC3","TLNKACTV","LNKAVAIL","ACHGOVRS","NEARMGIH","FARMGINH","NMDCLFLR","DRDCLFLR","SURCVERR","NEGACKS","DRLKINHB","NDCFLABN","NDCFLXDA","NDCFLXER","NDCFLXDC","NMFEPRO","NMLCLPRO","DRFEPRO","DRLCLPRO","MSURCERR","DRBSYLNK","PCRN1N2EXC","SDPDURTR","LMSUTRN","LMSURCV","LMSUOCTTRN","LMSUOCTRCV","LMSUTRNDSC","LMSURCVDSC","M2PUDMTR","M2PUDOCT","M2PUDMRC","M2PUDOCR","M2PLKNIS","ECLNKCB","ECLNKXCO"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ipsg","1103","A ","IPVL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","ssedcm1","1105","A ","IPVHSL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1281,0,0<cr><lf>"K","saal","1112","A ","SAAL",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 13 char LSN + 7 char LOC + 6 char LINK + 12 char LKNTYPE + 51*(6 char data) + 2 =350 chars


ReportsMeasurements

Table 134: Typical File Size: mtcdth-link.csv


header

175,855 bytes=175,000+605+250

LNKSET MTCDTH Report

Command Examples

• UI

rept-meas:type=mtcdth:enttype=lnkset:lsn=ayyyyyyy

• FTP

rept-ftp-meas:type=mtcdth:enttype=lnkset

Table 135: Maintenance Day-to-Hour Linkset Measurements



SCCPLOOP




peg countTranslation Type MappingTranslation Incoming - The total

ZTTMAPI

number of Translation TypeMapping translations performedon incoming Message SignalUnits (MSUs) for the specifiedlinkset.

peg countTranslation Type MappingTranslation Outgoing - The total

ZTTMAPO

number of Translation TypeMapping translations performedon outgoing Message SignalUnits (MSUs) for the specifiedlinkset.


ReportsMeasurements

Measurement Events

Table 136: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) LinksetMeasurements



SCCPLOOP





ZTTMAPI

Received on the Gateway Linkset- The total number of TranslationType Mapping translationsperformed for incoming MessageSignal Units (MSUs) received onthe specified linkset.


ZTTMAPO

Transmitted on the GatewayLinkset - The total number oftranslations performed onoutgoing Message Signal Units(MSUs) for the specified linkset.

UI Reports

UI Example Output:

• Example of rept-meas:type=mtcdth:enttype=lnkset:lsn=xxx

tekelecstp 12-02-12 00:07:51 EST EAGLE5 44.0.0 TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON LNKSET REPORT PERIOD: LAST REPORT INTERVAL: 12-02-11 00:00:00 THRU 23:59:59

LNKSET-MTCD MEASUREMENTS: mtp2 (MTP2)

ZTTMAPO = 0, ZTTMAPI = 0, SCCPLOOP = 0

;

tekelecstp 12-02-12 00:07:52 EST EAGLE5 44.0.0-64.23.0


ReportsMeasurements

LNKSET-MTCD MEASUREMENTS: ipsg (IPVL)


;

tekelecstp 12-02-12 00:07:53 EST EAGLE5 44.0.0 LNKSET-MTCD MEASUREMENTS: ssedcm1 (IPVHSL)


;

tekelecstp 12-02-12 00:07:54 EST EAGLE5 44.0.0 LNKSET-MTCD MEASUREMENTS: saal (SAAL)


;

tekelecstp 12-02-12 00:07:55 EST EAGLE5 44.0.0 LNKSET-MTCD MEASUREMENTS: hcmimt1 (MTP2-UNCH)


;

FTP Reports

FTP Example Output File Name: mtcdth-lnkset_20101005_0100.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-12","01:02:37","EST ","DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON LNKSET","LAST","2012-02-12","00:00:00","01:00:00",5<cr><lf><cr><lf>"STATUS","LSN","LNKTYPE","ZTTMAPO","ZTTMAPI","SCCPLOOP"<cr><lf>"K","mtp2","MTP2",0,0,0<cr><lf>"K","ipsg","IPVL",0,0,0<cr><lf>"K","ssedcm1","IPVHSL",0,0,0<cr><lf>"K","saal","SAAL",0,0,0<cr><lf>"K","hcmimt1","MTP2-UNCH",0,0,0<cr><lf>


4 char status + 13 char LSN + 12 char LKNTYPE + 3*(6 char data) + 2 = 49 chars

For a report of 500 linksets, the typical file size is:

Table 137: Typical File Size: mtcdth-lnkset.csv


header

24,808 bytes=24,500+58+250


ReportsMeasurements

STPLAN MTCDTH Report

Note: The peg counts forSTPLAN measurements have the possibility of rolling over during periodsof highSTPLAN message transmit and receive. On the measurement reports these measurements showup as negative numbers. This indicatesSTPLAN transmit and receive measurements have valuesgreater than four gigabytes of data.

Example Commands:

UI: rept-meas:type=mtcdth:enttype=stplanFTP: rept-ftp-meas:type=mtcdth:enttype=stplan

Table 138: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) STPLANMeasurements



ENETALNERR



ENETBUSBSY


peg countEthernetCRC Error - Number ofpackets not received on the

ENETCRCERR



ENETCOLERR



ENETOCTRCV



ENETOCTXMT


peg countEthernet Receive BufferOverflow Errors -

ENETOVRERR


ReportsMeasurements


Number of packets not receivedby STPLAN because of a receivebuffer overflow.

peg countIP Address Error- The totalnumber of inbound IP

IPADDRERR



IPHDRERR



IPPROTERR



SLANDISC1



SLANDISC2

SLAN cards for networkproblems and unreachable farend servers. During networkoutages, the SLAN cards willstop TVG/MFC grants or go intoflow control. This causes thePDUs to be queued on the LIMcards, so the majority of discardswill be pegged on SLANDISC1under these circumstances.


SLANDSBLD



SLANSCRND



ReportsMeasurements



SLANXMIT




TCPCONNFLD



TCPRCVERR



TCPRSTSENT



TCPSEGRCVD



TCPSEGSENT


TCPSEGXMT2


UI Reports

UI Example Output:

tekelecstp 01-08-18 00:00:21 EST EAGLE 34.0.0 TYPE OF REPORT: DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON STPLAN REPORT PERIOD: LAST REPORT INTERVAL: 01-08-17 00:00:00 THRU 23:59:59 STPLAN-MTCD MEASUREMENTS SLANDSBLD = 0, SLANDISC1 = 0, SLANDISC2 = 0, SLANSCRND = 0, SLANXMIT = 0, ENETALNERR = 0,


ReportsMeasurements

ENETCRCERR = 0, ENETCOLERR = 0, ENETBUSBSY = 0, ENETOVRERR = 0, ENETOCTXMT = 0, ENETOCTRCV = 0, TCPCONNFLD = 0, TCPSEGRCVD = 0, TCPSEGSENT = 0, TCPSEGXMT2 = 0, TCPRCVERR = 0, TCPRSTSENT = 0, IPHDRERR = 0, IPADDRERR = 0, IPPROTERR = 0; tekelecstp 01-08-18 00:00:22 EST EAGLE 34.0.0 END OF ON-DEMAND STPLAN-MTCDTH MEASUREMENT REPORT;

FTP ReportsFTP Example Output File Name: mtcdth-stplan_19990117_1500.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON STPLAN","LAST","1999-01-17","00:00:00","15:00:00",1<cr><lf><cr><lf>"STATUS","SLANDSBLD","SLANDISC1","SLANDISC2","SLANSCRND","SLANXMIT","ENETALNERR","ENETCRCERR","ENETCOLERR","ENETBUSBSY","ENETOVRERR","ENETOCTXMT","ENETOCTRCV","TCPCONNFLD","TCPSEGRCVD","TCPSEGSENT","TCPSEGXMT2","TCPRCVERR","TCPRSTSENT","IPHDRERR","IPADDRERR","IPPROTERR"<cr><lf>"K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


Table 139: Typical File Size: mtcdth-stplan.csv


header

792 bytes=260+282+250

SCTPASOC MTCDTH Report

Command Examples

• UI: rept-meas:type=mtcdth:enttype=sctpasoc:aname=assoc1

• FTP: rept-ftp-meas:type=mtcdth:enttype=sctpasoc

Measurement Events

Table 140: Daily Maintenance (MTCD) and Day-to-Hour (MTCDTH) SCTPASOC Measurements lists theSCTPASOC events and their descriptions.


ReportsMeasurements

Table 140: Daily Maintenance (MTCD) and Day-to-Hour (MTCDTH) SCTPASOC Measurements



ACTVESTB



ASMAXRTO



ASOCABTD



ASOCSHTD



CNTLCHKR


ReportsMeasurements




CNTLCHKS

chunks sent to the remote peer(excluding retransmissions) afteran association has been formed.



DATCHKRC



DATCHKSN

peg countDuration the association was notin the Established state.

DURASNEST


ECASNEST


GAPACKSR

Acknowledgement blocks inSelective Acknowledgement(SACK) control chunks receivedfrom the remote SCTP peer,indicating gaps in the peer’sreceived subsequences of DATAchunks as represented by theirTransport Sequence Numbers(TSNs) (The inclusion of thismeasurement is intended toallow network personnel toassess the message-deliveryperformance of the IPVHSLrelative to gap acknowledgmentlimits, if used as performancecriteria for link proving andin-service monitoring).


ReportsMeasurements



ORDCHKRC



ORDCHKSN



PASVESTB



PEERFAIL

of peer endpoint failuredetection events for theassociation as triggered by thecrossing of threshold Assoc.Max. Retrans.


RTXCHNKS



SCOCTRCV



ReportsMeasurements



SCOCTSNT



SCPKTRCV


SCPKTRCV register excludes thepegging of SCTP Packetsreceived when no instance existson the card for any of the links,i.e., the association parameter"OPEN" has value "NO" for allthe links configured on the card.Also, excludes pegging of set upmessages (INIT andCOOKIE-ECHO) that are part ofassociation establishmentprocedure.


SCPKTSNT


SCPKTSNT register excludesinitial SCTP association set-upmessages (INIT-ACK andCOOKIE-ACK) and ABORTmessages. For M2PA associationINIT packet is never pegged.




ReportsMeasurements

UI Reports

UI Example Output:

stdcfg2b 07-12-31 06:07:04 EST UNKNOWN 38.0.0-XX.XX.0 TYPE OF REPORT: DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON SCTPASOC REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:00:00 THRU 05:59:59

SCTPASOC-MTCDTH MEASUREMENTS: ASSOC: assoc1

These measurements are from 07-12-31, 00:00:00 through 05:59:59. ECASNEST = 0, DURASNEST = 0, DATCHKSN = 0, RTXCHNKS = 0, DATCHKRC = 0, SCPKTSNT = 20, SCPKTRCV = 20, SCOCTSNT = 0, SCOCTRCV = 0, CNTLCHKS = 400, ORDCHKSN = 400, CNTLCHKR = 0, ORDCHKRC = 0, GAPACKSR = 0, ACTVESTB = 0, PASVESTB = 0, ASOCABTD = 0, ASOCSHTD = 0, PEERFAIL = 0, ASMAXRTO = 0

;

FTP Reports

FTP Example Output File Name: mtcdth-sctpasoc_20071115_0200.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"ipmeas","UNKNOWN ??.?.?-58.21.0","2007-08-18","00:00:18","****","DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON SCTPASOC","LAST","2007-08-17","00:00:00","02:00:00",3<cr><lf>"STATUS","ASSOC","ECASNEST","DURASNEST","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","GAPACKSR","ACTVESTB","PASVESTB","ASOCABTD","ASOCSHTD","PEERFAIL","ASMAXRTO"<cr><lf>

"K","A1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","A1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","A1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 18 char association + 16*(6 char data) + 2 = 144 chars

For a report of 1000 associations, typical file size is:

Table 141: Typical File Size: mtcdth-sctpasoc.csv


header

144445 bytes=144000+195+250


ReportsMeasurements

SCTPCARD MTCDTH Report

Command Examples

• UI: rept-meas:type=mtcdth:enttype=sctpcard:loc=1202

• FTP: rept-ftp-meas:type=mtcdth:enttype=sctpcard

Measurement Events

Table 142: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARD Measurementslists the SCTPCARD events and their descriptions.

Table 142: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARDMeasurements



ACTVESTB



ASOCABTD



ASOCSHTD



ReportsMeasurements



CNTLCHKR



CNTLCHKS

chunks sent to the remote peer(excluding retransmissions),including chunks for which anassociation has not yet beenformed.


DATCHKRC



DATCHKSN


ORDCHKRC



ORDCHKSN



PASVESTB



RTXCHNKS

number of SCTP data chunksretransmitted to the remoteSCTP peer. When T3-rtx expires,the DATA chunks that triggered


ReportsMeasurements


the T3 timer will be re-sentaccording with theretransmissions rules. EveryDATA chunk that was includedin the SCTP packet that triggeredthe T3-rtx timer must be addedto the value of this counter.


SCOCTRCV



SCOCTSNT

comprising SCTP packetssubmitted to the IP layer fortransmittal to the remote peer,including packets for which anassociation has not been formed.


SCPKTRCV


SCPKTRCV register excludes thepegging of SCTP Packetsreceived when no instance existson the card for any of theassociations, i.e., the associationparameter "OPEN" has value"NO" for all the associationsconfigured on the card. Also,excludes pegging of set upmessages (INIT andCOOKIE-ECHO) that are part ofassociation establishmentprocedure.

peg countSCTP Packets Received WithChecksum Error - The number

SCPKTRER

of SCTP packets received fromremote peers with an invalidchecksum


SCPKTSNT


ReportsMeasurements






peg countUnassociated (Out-of-the-Blue)SCTP Packets - The number of

UNASCTPK


UNASCTPK register includesthe pegging of SCTP Packetsreceived when no instance existson the card for any of theassociations, i.e., the associationparameter "OPEN" has value"NO" for all the associationsconfigured on the card (SeeSCPKTRCV register).

UI Reports

UI Example Output:

stdcfg2b 07-12-31 EST UNKNOWN 38.0.0-XX.XX.0 TYPE OF REPORT: DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON SCTPCARD REPORT PERIOD: LAST REPORT INTERVAL: 07-12-31 00:00:00 THRU 03:59:59

SCTPCARD-MTCDTH MEASUREMENTS: LOC: 1201

These measurements are from 07-12-31, 00:00:00 through 03:59:59.


ReportsMeasurements

DATCHKSN = 0, RTXCHNKS = 0, DATCHKRC = 0, SCPKTSNT = 20, SCPKTRCV = 20, SCPKTRER = 0, UNASCTPK = 0, SCOCTSNT = 0, SCOCTRCV = 0, CNTLCHKS = 400, ORDCHKSN = 400, CNTLCHKR = 0, ORDCHKRC = 0, ACTVESTB = 0, PASVESTB = 0, ASOCABTD = 0, ASOCSHTD = 0

;

FTP Reports

FTP Example Output File Name: mtcdth-sctpcard_20071115_0400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp",”38.0.0-XX.XX.0”,”2007-12-31”,"12:12:10","EST","DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON SCTPCARD","LAST",”2007-12-30”,"00:00:00","04:00:00",3<cr><lf><cr><lf>"STATUS","LOC","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCPKTRER","UNASCTPK","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","ACTVESTB","PASVESTB","ASOCABTD","ASOCSHTD"<cr><lf>"K","1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>



For a report of 80 cards, typical file size is:

Table 143: Typical File Size: mtcdth-sctpasoc.csv


header

8675 bytes=8240+185+250

UA MTCDTH Report

Command Examples

• UI: rept-meas:type=mtcdth:enttype=ua:aname=assoc1:asname=appsrvr1

• FTP: rept-ftp-meas:type=mtcdth:enttype=ua

Measurement Events

Table 144: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) UA Measurements liststhe UA events and their descriptions.


ReportsMeasurements

Table 144: Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) UA Measurements



RXDATAMS

messages received from theASP.

For SUA, this register representsthe total of CLDT and CLDRmessages received from theASP.

octetsFor M3UA, this registerrepresents the number of DATAoctets received from the ASP.

RXDATAOC

For SUA, this register representsthe total of CLDT and CLDRoctets received from the ASP.


RXMLRCMS




peg countFor M3UA, this registerrepresents the number of DATAmessages sent to the ASP.

TXDATAMS

For SUA, this register representsthe total of CLDT and CLDRmessages sent to the ASP.

octetsFor M3UA, this registerrepresents the number of DATAoctets sent to the ASP.

TXDATAOC

For SUA, this register representsthe total of CLDT and CLDRoctets sent to the ASP.


UAASPMRX


ReportsMeasurements


peg countTotal ASPM messages sent tothe ASP (including ASPSM andASPTM messages).

UAASPMTX


UAASPNAC


UAASPNAT


UACNGCNT



UACNGTIM



UAMGMTRX


UAMGMTTX


UANMOCTR



UANMOCTT



UANMMSGR

ASP - The total number ofnon-DATA UA messagesreceived from the ASP (i.e., sum


ReportsMeasurements


of the ASPM, ASPTM, SSNM,MGMT, and RKM).


UANMMSGT



UASSNMRX


UASSNMTX

UI Reports

UI Example Output:

stdcfg2b 07-12-31 06:07:04 EST UNKNOWN 38.0.0-XX.XX.0 UA-MTCD MEASUREMENTS: AS: appsrvr1 ASSOC: assoc1


;

FTP Reports

FTP Example Output File Name: mtcdth-ua_20071115_1200.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","37.5.0-58.25.0","2007-11-15","12:59:10","EST","DAY-TO-HOUR MAINTENANCE MEASUREMENTS ON UA","LAST","2007-11-15","00:00:00","12:00:00",3<cr><lf><cr><lf>"STATUS","AS","ASSOC","RXDATAMS","TXDATAMS","RXDATAOC","TXDATAOC","RXMLRCMS","UAASPMRX","UAASPNAC","UAASPNAT","UACNGCNT","UACNGTIM","UAMGMTRX","UAMGMTTX","UANMOCTR","UANMOCTT","UANMMSGR","UANMMSGT","UASSNMRX","UASSNMTX","RXMLRCMS"<cr><lf>"K","as1101","a1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","as1102","a1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","as1103","a1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>


ReportsMeasurements



For a report of 1000 Application Servers, typical file size is:

Table 145: Typical File Size: mtcdth-ua.csv


header

150530 bytes=150000+280+250

Hourly Maintenance Measurements (MTCH)

The Maintenance Hour (MTCH) report provides the value of various maintenance measurementsaccumulated during a specific hour.

Entity Types: LNP, NP, EIR, MAPSCRN, VFLEX, ATINPQ, AIQ, GTTAPATH, DEIR, ENUM



Reporting Modes: On-demand, Scheduled (FTP reports only)

Accessible Collection Periods: Last, Specific

LNP MTCH Report

The enttype=lnp entity generates four separate reports per period. FTP reports are generated as CSVfiles and FTP'd to the customer FTP server. The command example will generate the following hourlyreports:

• Hourly LNP System Wide Measurements

• Hourly LNP Measurements Per SSP

• Hourly LNP Measurements Per LRN

• Hourly LNP Measurements Per NPA

Example Commands:

FTP:rept-ftp-meas:type=mtch:enttype=lnp:period=last

Table 146: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP System WideMeasurements


peg countTrigger BasedLNPQRCV


ReportsMeasurements


The total number of queriesreceived by LNPQS.


Number of encapsulated IAMmessages received by LNPQS

peg countTrigger BasedLNPQDSC

The number of invalid queriesthat are discarded because noreply can be generated.

not applicableTriggerless

All invalid IAM messages arerouted without LNP;LNPQTCPE is pegged.

peg countTrigger BasedLNPQTCPE

The number of error replies withTCAP error codes.


The number of invalidencapsulated IAM messagesreceived by LNPQS. Note thatthese messages are routed totheir destinations with no LNPlookup.

peg countTrigger BasedLNPSREP

The number of successful replies.


The number of successful IAMmessages.

peg countTrigger BasedLNPQUNPA

The number of correct queriesreceived for non-ported DNwhen NPA-NXX is notprovisioned.


The number of correctencapsulated IAM messagesreceived for a non-ported DN,


ReportsMeasurements


when the NPA-NXX is notprovisioned.



Table 147: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP Per SSPMeasurements


peg countTrigger BasedSSPQRCV

Number of correct queriesreceived per originating SSP.


The number of correctencapsulated IAM messagesreceived by LNPQS per OPC.

peg countNumber of valid CLASS GTTreceived per originating SSP.

CLASSGTRQ

peg countNumber of valid LIDB GTTreceived per originating SSP.

LIDBGTRQ

peg countNumber of correct queriesreceived for ported TNs, peroriginating SSP.

SSPQRCVP

peg countNumber of correct queriesreceived for non-ported TNs, peroriginating SSP.

SSPQRCVNP

peg countNumber of CLASS Global TitleTranslation received for portedTNs, per originating SSP.

CLASSGTRQP

peg countNumber of CLASS Global TitleTranslation received for

CLASSGTRQNP


peg countNumber of LIDB Global TitleTranslation received for portedTNs, per originating SSP.

LIDBGTRQP


ReportsMeasurements


peg countNumber of LIDB Global TitleTranslation received for

LIDBGTRQNP


peg countNumber of CNAM Global TitleTranslation received for portedTNs, per originating SSP.

CNAMGTRQP

peg countNumber of CNAM Global TitleTranslation received for

CNAMGTRQNP


peg countNumber of ISVM Global TitleTranslation received for portedTNs, per originating SSP.

ISVMGTRQP

peg countNumber of ISVM Global TitleTranslation received for

ISVMGTRQNP


peg countNumber of WSMSC Global TitleTranslations received for portedTNs, per originating SSP

WSMSCGTRQP

peg countNumber of WSMSC Global TitleTranslations received for

WSMSCGTRQNP

non-ported TNs, per originatingSSP




PC TYPE


SSPQRCV = SSPQRCVP + SSPQRCVNP

CLASSGTRQ = CLASSGTRQP + CLASSGTRQNP

LIDBGTRQ = LIDBGTRQP + LIDBGTRQNP


ReportsMeasurements

Table 148: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP LRN Measurements


peg countTrigger BasedLRNQRCV

The number of correct queriesreceived per LRN.


The number of correctencapsulated IAM messagesreceived per LRN.



Table 149: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) LNP NPA Measurements


peg countThe number of correct queriesreceived per NPANXX fornon-ported DN.

NPAQRCV



FTP Reports

Hourly LNP System Wide Measurements

FTP Example Output File Name: mtch-lnp_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","HOURLY MAINTENANCE MEASUREMENTS ON LNP SYSTEM","LAST","1999-01-16","00:00:00","24:00:00",1<cr><lf><cr><lf>


ReportsMeasurements

"STATUS","LNPQRCV","LNPQDSC","LNPQTCPE","LNPSREP","LNPQUNPA"<cr><lf>"K",429496729,429496729,429496729,429496729,429496729<cr><lf>


Table 150: Typical File Size: mtch-lnp.csv


header

347 bytes=34+63+250

Hourly LNP Measurements Per SSPFTP Example Output File Name:mtch-ssp_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","HOURLY MAINTENANCE MEASUREMENTS ON LNPSSP","LAST","1999-01-16","00:00:00","24:00:00",200<cr><lf><cr><lf>"STATUS","SSP","PC_TYPE","SSPQRCV","CLASSGTRQ","LIDBGTRQ","SSPQRCVP","SSPQRCVNP","CLASSGTRQP","CLASSGTRQNP","LIDBGTRQP","LIDBGTRQNP","CNAMGTRQP","CNAMGTRQNP","ISVMGTRQP","ISVMGTRQNP","WSMSCGTP","WSMSCGTNP"<cr><lf>"K","002-002-100","ANSI",123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999<cr><lf>. . . . ."K","002-005-123","ANSI",123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999,123456789,456789,99999<cr><lf>


4 char status + 14 char SSP + 10 char PC type + 15*(6 char data) + 2 = 120 chars

For a report of 200 SSPs, the typical file size is:

Table 151: Typical File Size: mtch-ssp.csv


header

24410 bytes=24000+160+250

Hourly LNP Measurements Per LRNFTP Example Output File Name:mtch-lrn_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","HOURLY MAINTENANCE MEASUREMENTS ON LNP LRN","LAST","1999-01-16","00:00:00","24:00:00",600<cr><lf><cr><lf>


ReportsMeasurements

"STATUS","LRN","LRNQRCV"<cr><lf>"K",9194560000,123456789<cr><lf>"K",4087550001,23456789<cr><lf>"K",5155550000,456789<cr><lf>. . . . ."K",3022330001,345<cr><lf>"K",7032110002,99999<cr><lf>"K",8123048059,4294967295<cr><lf>


4 char status + 11 char LRN + 6 char data + 2 = 23 chars


Table 152: Typical File Size: mtch-lrn.csv

Report data+Reportheader+System

header

14077 bytes=13800+27+250

Hourly LNP Measurements Per NPAFTP Example Output File Name:mtch-npa_19990116_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","HOURLY MAINTENANCE MEASUREMENTS ON LNP NPANXX","LAST","1999-01-16","00:00:00","24:00:00",600<cr><lf><cr><lf>"STATUS","NPANXX","NPAQRCV"<cr><lf>"K",919456,123456789<cr><lf>"K",408755,23456789<cr><lf>"K",515555,456789<cr><lf>. . . . ."K",302233,345<cr><lf>"K",703211,99999<cr><lf>"K",812304,4294967295<cr><lf>


4 char status + 7 char NPANXX + 6 char data + 2 = 19 chars


Table 153: Typical File Size: mtch-npa.csv


header

11680 bytes=11400+30+250


ReportsMeasurements

NP MTCH Report

The hourly Number Portability measurements specify the entity type NP (enttype=np) whichgenerates two separate reports per period. The command example will generate the following hourlyreports:

• Hourly System Wide Measurements

• Hourly Measurements Per SSP

Command Examples

• FTP

rept-ftp-meas:type=mtch:enttype=np[:period=specific:day=xxx]

Measurement Events

• System Wide Measurements

indicates system registers that may be pegged. Register counts for features not turned on willalways be zero.

Table 154: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) System-Wide Registers



APSMRQERR

peg countNumber of SMSREQ messagesresulting in SMSREQ_ACK orSMSREQ_NACK.

APSMRQREP

peg countNumber of SMS Requestmessages received.

APSMSRCV

peg countNumber of SMS Requestmessages relayed.

APSMSREL

Peg CountNumber of non-call relatedmessages relayed by G-Port.

GPNOCL

Peg CountNumber of non-call relatedmessages that fell through toGTT.

GPNOCLGT


GPSRERR

response message(SRI-SendRouting InformationNEGATIVE ACK) because ofG-Port service failure. This does


ReportsMeasurements


not include peg counts toregister GPSRERRPP.


GPSRREPPP

messages that received G-Portservice specifically for feature:G-Port SRI query for Prepaid.This does not include pegcounts to register GPSRREP.


GPSRGTT

messages that fell through toGTT. This does not include pegcounts to register GPSRGTTPP.


GPSRGTTPP

messages that fell through toGTT specifically for feature:G-Port SRI query for Prepaid.This does not include pegcounts to register GPSRGTT.


GPSRRCV

messages received. This doesnot include peg counts toregister GPSRRCVPP.


GPSRRCVPP

messages received specificallyfor feature: G-Port SRI queryfor Prepaid. This does notinclude peg counts to registerGPSRRCV.


GPSRREP

messages that received G-Portservice. This does not includepeg counts to registerGPSRREPPP.


GPSRERRPP

response message (SRI-SendRouting InformationNEGATIVE ACK) specifically


ReportsMeasurements


for feature: G-Port SRI queryfor Prepaid. This does notinclude peg counts to registerGPSRERR.


GPSRSMERR


GPSRSMRCV

peg countNumber of SRI_SM messagesresulting in SRI_SM_ACK orSRI_SM_NACK.

GPSRSMREP

peg countNumber of invalid queries thatare discarded as no reply canbe generated.

INPQDSC

peg countNumber of total queriesreceived by INPQS.

INPQRCV

peg countNumber of queries received byINPQS that meet the conditionfor circular route detection.

INPQSCRD

peg countNumber of error replies withTCAP error code.

INPQTCPE

peg countNumber of successful replies toINP non-queried queries. These

INPSREP

replies will be either INPConnect, INP Continue, or INPReleaseCall (every time anINAP RELEASECALL responseis generated due to circularroute dection by INPQS).

peg countNumber of IS-41 locationrequest - error responsemessages sent.

IS41LRERR

peg countNumber of IS-41 locationrequest messages received

IS41LRMRCV

peg countNumber of IS-41 locationrequest - return result messagessent

IS41LRRTRN

peg countNumber of times CircularRoute is Detected

MNPCRD


ReportsMeasurements



SMSMOGERR


SMSMOGRCV



SMSMOIERR


SMSMOIRCV

modification of the outgoingSMDPP.




TIFFPFXRLS

blacklisted by the FPFXRLSService Action


TIFNFNDRLS

blacklisted by the BLNFNDRLSService Action


TIFNOCGRLS

blacklisted by theNOCGPNRLS Service Action


TIFRLS

blacklisted by the BLRLSService Action

peg countNumber of MSUs processed byTIF and found to be blacklistedby SELSCR Service Action

TIFSSCRRLS

peg countNumber of MSUs processed byTIF and relayed by SELSCRService Action

TIFSSCRRLY


ReportsMeasurements



TINPERR



TINPMGEN



TINPMRCV


INPQRCV = INPQDSC + INPQTCPE + INPSREP

GPSRRCV = GPSRGTT + GPSRREP + GPSRERR

GPSRRCVPP = GPSRGTTPP + GPSRREPPP + GPSRERRPP

GPSRSMRCV = GPSRSMREP + GPSRSMERR

• Per SSP Measurements

These measurements are available on a per SSP PC basis where SSP PC is the CGPA PC, if it exists,or it is the MTP OPC.

Table 155: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) SSP Registers


peg countNumber of call relatedLOCREQ messagesacknowledged.

APLRACK

peg countNumber of call relatedLOCREQ messages relayed.

APLRRLY

peg countNumber of non-callnon-LOCREQ related messagesrelayed.

APNOCL

peg countNumber of non-callnon-LOCREQ related messagesthat fell through to GTT.

APNOCLGT


APSMRQERR


ReportsMeasurements


peg countNumber of SMSREQ messagesresulting in SMSREQ_ACK orSMSREQ_NACK

APSMRQREP

peg countNumber of SMSREQ messagesreceived

APSMSRCV

peg countNumber of non-call relatedmessages relayed by G-Port.

GPNOCL

peg countNumber of non-call relatedmessages that fell through toGTT.

GPNOCLGT


GPSRACK

ACK) responses. This does notinclude peg counts to registerGPSRACKPP.


GPSRACKPP

ACK) responses specifically forfeature 61544: G-Port SRI queryfor Prepaid. This does notinclude peg counts to registerGPSRACK.

peg countNumber of call related SRINegative ACK responses in

GPSRNACK

case of successful G-Portservice.

peg countNumber of call related(SRI-Send Routing Information)messages relayed.

GPSRRLY


GPSRSMERR


GPSRSMRCV

peg countNumber of SRI_SM messagesresulting in SRI_SM_ACK orSRI_SM_NACK

GPSRSMREP


INPMRCRD

GTT due to circular routedetection.


ReportsMeasurements



INPMRGTT

GTT. This includes the numberof messages sent to MR servicethat fall through to GTT due tocircular route detection.

peg countNumber of messages sent toMR service that receive MRtranslation.

INPMRTR

peg countNumber of non-erroredQSmessages with QS Connectresponses, per originating SSP.

INPQSCONN

peg countNumber of non-errored QSmessages with QS Continueresponses, per originating SSP.

INPQSCONT

peg countNumber of messages sent toINP QS that meet the conditionfor circular route detection.

INPQSCRD

peg countNumber of messages sent toINP QS that result in successful

INPQSREL

generation of INAPRELEASECALL response dueto circular route detection byINPQS.

peg countNumber of times CircularRoute is Detected.

MNPCRD

textTYPE of the point code. Validvalues are ANSI, ITUI, ITUN,and ITUN24.

PC Type


SMSMOGERR


SMSMOGRCV



SMSMOIERR


SMSMOIRCV

modification of the outgoingSMDPP


ReportsMeasurements





TIFRANGEBL

blacklisted by the FPFXRLS orNOCGPNRLS Service Action

peg countTotal number of MSUsprocessed by TIF and found to

TIFSBSCRBL

be blacklisted by BLRLS orBLNFNDRLS Service Actions

peg countNumber of IAM messagesprocessed by TIF which

TIFSELSCR

resulted in either an ISUPmessage generation or the MSUbeing relayed by SELSCRService Action


TINPERR



TINPMGEN



TINPMRCV

The following equation applies to NP registers:

GPSRREP = ∑GPSRACK + ∑GPSRRLY+ ∑GPSRNACK

FTP Reports

• Hourly System Wide Measurements

FTP Example Output File Name:mtch-np_20080125_2400.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-20","00:00:50","EST ","HOURLY MAINTENANCE MEASUREMENTS ON NP SYSTEM","LAST","2010-08-19","23:00:00","24:00:00",1

"STATUS","INPQRCV","INPQDSC","INPQTCPE","INPSREP","GPSRRCV","GPSRGTT","GPSRREP","GPSRERR","GPNOCL","GPNOCLGT","IS41LRERR","IS41LRMRCV","IS41LRRTRN","GPSRRCVPP","GPSRGTTPP","GPSRREPPP","GPSRERRPP","APSMSRCV","APSMSREL","TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV","SMSMOIERR","SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP","APSMRQERR","INPQSCRD","MNPCRD""K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,

Assuming each data line will be: 4 char status + 33 * (6 char data) + 2 = 204 chars


Table 156: Typical File Size: mtch-np.csv


header

832 bytes=204+378+250

• Hourly Measurements Per SSP

FTP Example Output File Name: mtch-ssp_20080125_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-20","00:00:51","EST ","HOURLYMAINTENANCE MEASUREMENTS ON NP SSP","LAST","2010-08-19","23:00:00","24:00:00",3"STATUS","SSP","PC_TYPE","INPQSCONN","INPQSCONT","INPMRTR","INPMRGTT","GPSRACK","GPSRRLY","GPNOCL","GPNOCLGT","GPSRACKPP","APLRACK","APLRRLY","APNOCL","APNOCLGT","TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV","SMSMOIERR","SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP","APSMRQERR","APSMSRCV","INPQSCRD","INPQSREL","INPMRCRD","MNPCRD","GPSRNACK""K"," 001-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,"K"," 101-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,"K"," 201-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,

Assuming each data line will be: 4 char status + 14 char SSP + 10 char PC type + 31 * (6 char data)+ 2 = 216 chars




header


=(216 * #PointCodes )

+356+250


ReportsMeasurements




header

43806 bytes=(216 * 200 )+356+250

EIR MTCH Report

The EIR measurements specify the entity type EIR, and generate one report per period. The commandsare specified with yy as a two-number abbreviation for any hour of a 24-hour day (00 through 23 forthe hours 0000 through 2300). The retention period for hourly measurement records is 24 hours.

Example Commands:

FTP: rept-ftp-meas:type=mtch:enttype=eir:[hh=yy:period=specific]

Table 159: Daily Maintenance (MCTD) and Hourly Maintenance (MTCH) EIR Measurements lists the EIRevents and their descriptions.

Table 159: Daily Maintenance (MCTD) and Hourly Maintenance (MTCH) EIR Measurements


peg countTotal number ofMAP_CHECK_IMEI messagesreceived

IMEIRCV

peg countTotal number of searches thatresulted in a match with a “whitelisted” IMEI

WHITEIMEI

peg countTotal number of searches thatresulted in a match with a “graylisted” IMEI

GRAYIMEI

peg countTotal number of searches thatresulted in a match with a “blacklisted” IMEI

BLACKIMEI


BLKALIMEI

listed” IMEI, but were alloweddue to IMSI Check match


BLKNALIMEI

listed” IMEI, and the IMSI in thedatabase did not match the IMSIin the message


ReportsMeasurements


peg countTotal number of searches thatresulted in a match with an“unknown” IMEI

UNKNIMEI

peg countTotal number of searches thatresulted in no match in thedatabase.

NOMTCHIMEI

NOMTCHIMEI is peggedwhenever an IMEI is not foundin the database.



The following equation applies:

IMEIRCV = WHITEIMEI + GRAYIMEI + UNKNIMEI

FTP ReportsFTP Example Output File Name: mtch-eir_20030818_2300.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-51.1.0","2003-08-19","15:51:37","EST","HOURLY MAINTENANCE MEASUREMENTS ON EIR SYSTEM","LAST","2003-08-18", "23:00:00","24:00:00",1<cr><lf><cr><lf>"IMEIRCV","WHITEIMEI","GRAYIMEI","BLACKIMEI","BLKALIMEI","BLKNALIMEI","UNKNIMEI","NOMTCHIMEI"<cr><lf>4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295, 4294967295<cr><lf>


Table 160: Typical File Size: mtch-eir.csv


header

440 bytes=89+95+256


ReportsMeasurements

MAPSCRN MTCH Report

The enttype=mapscrn entity generates two separate reports per period.

FTP reports are generated as CSV files and FTP'd to the customer FTP server. The command examplegenerates the following hourly measurement reports when the GSM MAP Screening feature is activated:

• Hourly MAP Screening System Wide Measurements

• Hourly MAP Screening Measurements Per Server

The command example will generate the following hourly measurement reports when the GSMMAP/Enhanced GSM MAP Screening feature is activated:

• Hourly MAP Screening System Wide Measurements

• Hourly MAP Screening Measurements Per Path

Example Commands:

FTP: rept-ftp-meas:type=mtch:enttype=mapscrn

Note: When MTP MAP Screening is enabled and on, the registers in Table 161: Daily Maintenance(MTCD) and Hourly Maintenance (MTCH) MAP Screening System Wide Measurements and Table 164:Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening Per Server Measurementsinclude the sum total of MTP-routed and GTT-routed messages for the particular event.

Table 161: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening SystemWide Measurements



MSCRNPASS


MSCRNRJNE

because an entry was not foundin the MAP screening table (i.e.,rejected as System wide MAPOpcode action is DISCARD)


MSCRNRJFP



MSCRNPAFP


countTotal number of messages,where an entry was not found in

MSCRNPANE


ReportsMeasurements


the MAP screening table but theMessage was not rejected asscreening action was marked asPASS (i.e., not rejected as Systemwide MAP Opcode action isPASS)

countTotal number of message thatgot rejected as Message MAP

MSCRNRJOP

Opcode was not found in theMAP Opcode table (system wideaction - DISCARD for the nonmatching OPCODEs)

countTotal number of messages thatwere selected by MAP Screening

MSCRNDUP

for the Duplicate screeningaction.

countTotal number of messages thatewere selected by MAP Screeningfor the Forward screening action.

MSCRNFOR

countTotal number of messages thatewere selected by MAP Screening

MSCRNDAD

for the Duplicate and Discardscreening action.



Server Entity Identification information in Table 162: Server Entity Identification is used to clarify theserver. The Maintenance MAP Screening Per Server Measurements are applicable.

Table 162: Server Entity Identification


The screened origination address of the callingparty address (CGPA) assigned when the GSMMAP screen was entered.

SERVER

The screened number plan value (NPV) assignedto the server address when the GSM MAP screen

NP

was entered. This field is filled with the defaultidentifier * if no value was assigned.


ReportsMeasurements


The screened nature of address value (NAIV)assigned to the server address when the GSM

NAI

MAP screen was entered. This field is filled withthe default identifier * if no value was assigned.

The operation code number assigned when theGSM MAP opcode was entered.

OPCODE

Measurements does not report entries created fora range of addresses.

Server Path Entity Identification information in Table 163: Path Entity Identification is used to clarifythe path. The Maintenance MAP Screening Per Path Measurements are applicable.

Table 163: Path Entity Identification


The screened origination address of the callingparty address (CGPA-NP-NAI), or a combination

PATH

of screened destination address of the called partyaddress (CDPA-NP-NAI) and the screenedorigination addresses assigned when the GSMMAP screen was entered.

The possible fields within the path are delimitedas follows to allow for efficient sorting:

• When both the origination and destinationaddresses are present (as either single serverentries or provisioned wildcard entries) theorigination address is preceded by a carat (^) andthe destination address is preceded by a "greaterthan" sign (>):

^CGPA-NP-NAI>CDPA-NP-NAI

• When only the origination address is present(occurs when the CDPA is a default wildcard) itis preceded by a "less than" sign (<):

<CGPA-NP-NAI

The calling party global title address assignedwhen the GSM MAP screen was entered. Any or

CGPA

all of the three fields (GTA, NP, NAI) can be filledwith the identifier (*) if a wildcard value isassigned for that field. There is no defaultwildcard value for the CGPA.

The called party global title address assignedwhen the GSM MAP screen was entered. Any or

CDPA


ReportsMeasurements


all of the three fields (GTA, NP, NAI) can be filledwith the identifier (*) if a wildcard value isassigned for that field. If the CDPA value is notassigned, the default wildcard value, which is notprinted, is assumed.

The screened number plan value (NPV) assignedto the path address when the GSM MAP screen

NP

was entered. The identifier (*) is used to signify awildcard NP.

The screened nature of address value (NAIV)assigned to the path address when the GSM MAP

NAI

screen was entered. The identifier (*) is used tosignify a wildcard NAI.

The operation code number assigned when theGSM MAP opcode was entered. The identifier (*)is used to signify a wildcard opcode.

OPCODE

Note:

Measurements does not report entries created for a range of addresses.

Measurements does not report default wildcard CDPA address in entries containing them.

There can never be a default wildcard CGPA entry. All wildcard CGPA entries must be explicitlyprovisioned. There can never be an entry with only a CDPA path listed.

The string formats were designed to allow efficient automated post processing of measurementsreports. A brief note explaining the format is included in the report.

Table 164: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) MAP Screening PerServer Measurements



MSCRNPASS


MSCRNRJFP



MSCRNDUP



MSCRNFOR


ReportsMeasurements


MAP Screening for the Forwardscreening action.


MSCRNDAD



MSCRNPAFP




FTP Reports

Hourly MAP Screening System Wide Measurements

FTP Example Output File Name: mtch-map_19990116_2400.csv

FTP Example Output File Name: mtch-map_19990116_2400.csv

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-21","00:00:52","EST ","HOURLY MAINTENANCE MEASUREMENTS ON MAPSCRN SYSTEM","LAST","2010-08-20","23:00:00","24:00:00",1

"STATUS","MSCRNPASS","MSCRNRJOP","MSCRNRJNE","MSCRNRJFP","MSCRNPAFP","MSCRNPANE","MSCRNFOR","MSCRNDUP","MSCRNDAD""K",0,0,0,0,0,0,0,0,0,


Table 165: Typical File Size: mtch-map.csv


header

426 bytes=60+116+250

Hourly MAP Screening Measurements Per PathFTP Example Output File Name:mtch-path_19990116_2400.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""e1061001","EAGLE5 42.0.0-63.33.0","2010-08-21","00:00:53","EST ","HOURLY MAINTENANCE MEASUREMENTS ON MAPSCRN PER-SERVER","LAST","2010-08-20","23:00:00","24:00:00",11

"For a path containing CGPA only, PATH-OPCODE = <CGPA-NP-NAI-OPCODE""For a path containing both CGPA and CDPA, PATH-OPCODE = ^CGPA-NP-NAI>CDPA-NP-NAI-OPCODE"

"STATUS","PATH-OPCODE","MSCRNPASS","MSCRNRJFP","MSCRNFOR","MSCRNDUP","MSCRNDAD","MSCRNPAFP""K","<123456789012345-*-*-0",0,0,0,0,0,0"K","<234567890123456-*-*-0",0,0,0,0,0,0"K","<345678901234567-*-*-0",0,0,0,0,0,0"K","<456789012345678-*-*-0",0,0,0,0,0,0"K","<567890123456789-*-*-0",0,0,0,0,0,0"K","<678901234567890-*-*-0",0,0,0,0,0,0"K","<789012345678901-*-*-0",0,0,0,0,0,0"K","<123456789012345-*-*-1",0,0,0,0,0,0"K","<234567890123456-*-*-1",0,0,0,0,0,0"K","<345678901234567-*-*-1",0,0,0,0,0,0"K","<456789012345678-*-*-1",0,0,0,0,0,0


4 char status + 40 char PATH-OPCODE + 6*(6 char data) + 2 = 82 chars

For a report of 20 paths, the typical file size is:

Table 166: Typical File Size: mtch-path.csv


header

2141 bytes=1640+251+250

VFLEX MTCH Report

The enttype=vflex entity generates two separate reports per period. These reports are generated asCSV files and FTP'd to the customer FTP server. The command example will generate the followingdaily reports:

• Hourly V-Flex System Wide Measurements

• Hourly V-Flex Measurements Per SSP

Example Commands:

FTP: rept-ftp-meas:type=mtch:enttype=vflex[:period=specific:day=xxx]


ReportsMeasurements

Table 167: Daily Maintenance V-Flex System Wide Measurements




peg countTotal number of IDP Connectresponses sent by VFLEX service.

VFCNCTRSP

peg countTotal number of IDP queriesreceived with errors (those

VFERRRSP

resulted in TCAP Error responsefrom VFLEX).

peg countTotal number of IDP queriesreceived for VFLEX service.

VFIDPQRCV

Table 168: Daily Maintenance V-Flex Per SSP Measurements




peg countTotal number of IDP queriesreceived for VFLEX service withinvalid MSISDN.

VFIMSISDN

peg countTotal number of IDP queriesreceived for VFLEX service withvalid MSISDN.

VFVMSISDN

FTP Reports

Hourly V-Flex System Wide Measurements

FTP Example Output File Name: mtch-vflex_20070816_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","37.6.0-58.20.0","2007-08-17","11:32:53","EST","HOURLY MAINTENANCE MEASUREMENTS ON VFLEX SYSTEM","LAST","2007-08-16","00:00:00","24:00:00",1<cr><lf>


ReportsMeasurements

<cr><lf>"STATUS","VFIDPQRCV","VFCNCTRSP","VFERRRSP"<cr><lf>"K", 20,10,10<cr><lf>

Assuming each data line will be: 4 char status + 3*(6 char data) + 2 = 24 chars, the typical file size is:

Table 169: Typical File Size: mtch-vflex.csv


header

347=24+45+260

Hourly V-Flex Measurements Per SSPMP Example Output File Name:mtch-vflexssp_20070816_2400.csv

MP Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""<cr><lf>"tekelecstp","37.6.0-58.20.0","2007-08-17","11:32:58","EST","HOURLY MAINTENANCE MEASUREMENTS ON VFLEX SSP","LAST","2007-08-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS",“SSP”,“VFVMSISDN”,“VFIMSISDN”<cr><lf>“K”, “001-101-002”,10,10<cr><lf>

Note: The field identifier SSP designates the Service Switching Point.

Assuming each data line will be: 4 char status + 14 char SSP + 2*(6 char data) + 2 = 32 chars, the typicalfile size is:

Table 170: Typical File Size: mtch-vflexssp.csv


header


=32 * #PointCodes

+40+257


Table 171: Typical File Size: mtch-vflexssp.csv


header

6697 bytes=32 * 200+40+257


ReportsMeasurements

ATINPQ MTCH Report

The enttype=atinpq entity generates two separate reports per period. These reports are generated asCSV files and FTP'd to the customer FTP server. The command example will generate the followingdaily reports:

• Hourly ATINPQ System Wide Measurements

• Hourly ATINPQ Per SSP Measurements

Example Commands:

• FTP

rept-ftp-meas:type=mtch:enttype=atinpq[:period=specific:hh=xxx]

Measurement Events

Table 172: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ATINPQ Registers


peg countTotal number of ATINP queriesreceived for ATINPQ service.

ATINPQRCV

This peg is incremented only ifATINP feature is enabled andthe incoming message opcode isATI.

peg countTotal number of ATI ACKmessages sent by the ATINPQ

ATINPQACK

service. This peg is incrementedonly if the ATINP feature isenabled.

peg countTotal number of incoming ATImessages that did not result in

ATINPQERR

either ATI ACK or ATI NACKwith error code of eitherUnknown Subscriber or ATI NotAllowed. This peg isincremented only if the ATINPfeature is enabled.




ReportsMeasurements



PC TYPE

Hourly ATINPQ Reports

System Wide Report


mtch-atinpq_20080616_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","39.0.0-61.5.0","2008-06-17","11:32:53","EST","HOURLY MAINTENANCE MEASUREMENTS ON ATINPQ SYSTEM","LAST","2008-06-17","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","ATINPQRCV","ATINPQACK","ATINPQERR"<cr><lf>"K", 20,10,10<cr><lf>


Table 173: Typical File Size: mtch-atinpq.csv


header

347=24+45+260

Per SSP Report


mtch-atinpqssp_20080616_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""<cr><lf>"tekelecstp","39.0.0-61.5.0","2008-06-17","11:32:58","EST","HOURLY MAINTENANCE MEASUREMENTS ON ATINPQ SSP","LAST","2008-06-16","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS",“SSP”,“ATINPQRCV”,“ATINPQACK”,“ATINPQERR”<cr><lf>“K”, “001-101-002”,10,10,10<cr><lf>



ReportsMeasurements

Table 174: Typical File Size: mtch-atinpq.csv


header

297 + (38 *#Point

Codes) bytes

=(38 * #PointCodes)

+40+257


Table 175: Typical File Size: atinpq 200 SSPs


header

7897 bytes=(38 * 200)+40+257

AIQ MTCH Report

The entity type for ANSI41 AIQ measurements is “AIQ”, which generates two reports per period. Thecommands to generate the hourly on-demand measurement report can be specified with an optionalhour parameter, xxxx, providing a four-digit hour (0100, 0200, 2300, and so on). The specific period,period=specific, parameter is required when the optional hour parameter is used.

The measurements reports supported are:


• Per SSP Totals


• Daily measurement report type "mtcd"

• Hourly measurement report type "mtch"

The on demand reports and scheduled reports are rejected until the AIQ feature is enabled. Thecommand chg-mtc-measopts:mtchaiq=on:mtcdaiq=on starts scheduled reports generation.Both on-demand and scheduled reports at hourly and daily boundary (MTCH and MTCD) generatetwo reports, namely Per System totals and Per SSP totals.

Example Commands:

• UI: Not applicable.

• FTP: rept-ftp-meas:type=mtcd:enttype=aiq[:period=specific:hh=xxxx]

This command creates both the Per System and Per SSP Totals hourly reports.


ReportsMeasurements

Measurement Events

Table 176: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) AIQ Registers


peg countTotal number ofAnalyzedInformation messages

AIQRCV

received for AIQ service. Thispeg is incremented only ifANSI41 AIQ feature is enabled.

peg countTotal number of Return Resultsent by the AIQ service. This peg

AIQSUCC

is incremented only if theANSI41 AIQ feature is enabled.

peg countTotal number of ANSI41 AIQqueries resulting in a negative

AIQERR

response (Return Error or Reject)generation by AIQ service. Thispeg is incremented only if theANSI41 AIQ feature is enabled.


PC TYPE

Daily AIQ Reports

System Wide Report


mtcd-aiq_20090820_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","41.0.0-62.34.51","2009-08-20","11:32:53","EST","DAILY MAINTENANCE MEASUREMENTS ON AIQ SYSTEM","LAST","2009-08-20","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS","AIQRCV","AIQSUCC","AIQERR"<cr><lf>"K",20,10,10<cr><lf>



ReportsMeasurements



header

322=24+38+260

Per SSP Report


mtcd-aiqssp_20090820_2400.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""<cr><lf>"tekelecstp","41.0.0-62.34.51","2009-08-20","11:32:58","EST","DAILY MAINTENANCE MEASUREMENTS ON AIQ SSP","LAST","2009-08-19","00:00:00","24:00:00",1<cr><lf><cr><lf>"STATUS",“SSP”,“AIQRCV”,“AIQSUCC”,“AIQERR”<cr><lf>“K”, “001-101-002”,20,10,10<cr><lf>


Table 178: Typical File Size: mtcd-aiq.csv


header

301 + ( 38 *#Point

=( 38 * #Pointcodes )

+44+257

Codes )bytes


Table 179: Typical File Size: aiq 200 SSPs


header

7901 bytes=( 38 * 200 )+44+257

GTTPATH MTCH Report

The entity type for GTT Actions Per-Path measurements is “gttapath”, which generates two reportsper period. The commands to generate the hourly on-demand measurement report can be specifiedwith an optional hour parameter, xxxx, providing a four-digit hour (0100, 0200, 2300, and so on). Thespecific period, period=specific, parameter is required when the optional hour parameter is used.


ReportsMeasurements

The measurement report supported are:


• Per Path Totals


• Daily measurement report type “mtcd”

• Hourly measurement report type “mtch”

The on-demand reports and scheduled reports are rejected until the GTT Duplicate and/or Discardand/or Forward Action feature is enabled. Turning ON the feature is not required, because one of theregister “GTTACTNA” might get pegged in case GTT action fails because of the feature not being inthe ON state.

The command chg-mtc-measopts:mtchgttapath=on:mtcdgttapath=on starts scheduledreports generation. Both on-demand and scheduled reports at hourly and daily boundary (MTCHand MTCD) generate two reports: Per System Totals and Per-Path.

Example Commands:

UI: Not applicable.FTP: rept-ftp-meas:type=mtch:enttype=gttapath[:period=specific:hh=xxxx]where [:period=specific:hh=xxxx] is optional.

This example command creates both the Per-Path System Totals and the Per-Path Totals daily reports(the report date corresponds to the day entered in the command).

Table 180: MTCD/MTCH GTT Actions System-Wide Measurements



GTTADISC0



GTTADISC1



GTTADISC2



GTTADUP

of messages for which DuplicateMSU was sent. Multipleduplicate actions in an action set


ReportsMeasurements


shall also increment this registeronly once.


GTTAFWD



GTTASET


GTTASRVGFLX


GTTASRVGPRT


GTTASRVSMSR


GTTASFLOG


GTTAMSVTO


GTTAMSVDI


GTTAMSVNA

Table 181: MTCD/MTCH GTT Actions Per-Path Measurements


pegcount

GTT Actions - The total number of messages for which no GTT action wassuccessfully performed.

GTTACTNA

This register shall be pegged for a message if either of these occurs:

• No GTT Action set was associated with the final GTT translation

• No GTT Action in the associated GTT Action set could be executedsuccessfully (for any reason).


ReportsMeasurements


pegcount

GTT Actions – MSUs Discarded - The total number of messages discarded bythe DISCARD GTT Action.

GTTADISC0

pegcount

GTT Actions – MSUs Discarded - The total number of messages discarded bythe UDTS GTT Action.

GTTADISC1

pegcount

GTT Actions – MSUs Discarded - The total number of messages discarded bythe TCAP Error GTT Action

GTTADISC2

pegcount

GTT Actions – MSUs Duplicated - The total number of messages for whichDuplicate MSU was sent.

GTTADUP

This register shall be pegged for a message only once for which either a singleor multiple duplicate GTT Actions were performed.

pegcount

GTT Actions – MSUs Forwarded - The total number of messages forwardedby Forward GTT Action.

GTTAFWD

pegcount

The total number of messages serviced by GFLEX GTT Action.GTTASRVGFLX

pegcount

The total number of messages serviced by GPORT GTT Action.GTTASRVGPRT

pegcount

The total number of messages serviced by SMSMR GTT Action.GTTASRVSMSR

pegcount

The total number of messages serviced by SFLOG GTT Action.GTTASFLOG

pegcount

The total number of messages that successfully pass SCPVAL GTT Action.GTTAMSVTO

pegcount

The total number of messages discarded by SCPVAL GTT Action.GTTAMSVDI

pegcount

The total number of messages where validation was not applied by SCPVALGTT Action.

GTTAMSVNA

Hourly GTTAPATH ReportsThe command rept-ftp-meas:type=mtch:enttype=gttapath produces the system-wide reportand the per-path report report shown here.

System Wide Report

• Example Output File Name: mtch-gttasys_20140228_2400.csv• Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 46.0.0-65.6.0","2014-02-28","00:10:33","EST ","HOURLY


ReportsMeasurements

MAINTENANCE MEASUREMENTS ON GTTACTION SYSTEM","LAST","2014-02-28","23:00:00","23:59:59",1

"STATUS","GTTADISC0","GTTADISC1","GTTADISC2","GTTADUP","GTTAFWD","GTTASET","GTTASRVGFLX","GTTASRVGPRT","GTTASRVSMSR""K",0,0,0,0,0,0,0,0,0


Table 182: Typical File Size: mtch-gttasys.csv


header

427 bytes=60+117+250

Per Path Report

• Example Output File Name: mtch-gttapath_20140124_2200.csv

Table 183: Entity Identification(PATH-CDSN-SCDGTA-CGSN-SCGGTA-OPSN-PKG-OPCODE-<A>/F)

DefinitionString Format

The GTT path name assigned when GTTACTpath was entered.

PATH

The called party global title translations set nameassigned when GTTACT path was entered.

CDSN

The called party start global title address(SCDGTA) assigned when GTTACT pathentered for a non-ranged entry

SCDGTA

or

The ranged called party start global title address(SCDGTA) and End global title address

SCDGTA->ECDGTA

(ECDGTA) assigned when the GTTACT pathwas entered.

The calling party global title translations setname assigned when GTTACT path was entered.

CGSN

The calling party start global title addressassigned when GTTACT path entered for anon-ranged entry

SCGGTA

or

The ranged calling party start global title address(SCGGTA) and End global title address

SCDGTA->ECDGTA


ReportsMeasurements

DefinitionString Format(ECGGTA) assigned when the GTTACT pathwas entered.

The global title translations set name of TCAPoperation code assigned when GTTACT pathwas entered

OPSN

The ANSI/ITU TCAP package type assignedwhen GTTACT Path was entered.

PKG

TCAP operation code assigned when GTTACTpath was entered.

OPCODE

‘<A>’ stands for Application Context Name(ACN) assigned when GTTACT path entered if

<A>/F

package type is ITU TCAP. It is preceded by a“less than” sign(<) and followed by a “greaterthan” sign (>).

‘F’ stands for ANSI TCAP family field assignedif package type is ANSI TCAP when GTTACTPath was entered.

Backslash ‘/’ will not be displayed in the reportdata. Its only signifies that either <A> or F willbe displayed at a time based on the package typedisplayed in the PKG entry.

Note:

• If any entry has no value assigned then default value “#” will be displayed for it.

• These string formats allow efficient automated post processing of measurements reports; theyare not designed to be easily readable. A brief note explaining the format is included in thereport.


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 46.0.0-65.6.0","2014-01-24","00:10:35","EST ","HOURLY MAINTENANCE MEASUREMENTS ON GTTACTION PER-PATH","LAST","2014-01-24","23:00:00","23:59:59",6

For a path containing GTA ranges, PATH-CDSN-SCDGTA-CGSN-CGGTA-OPSN-PKG-OPCODE-<A>/F = PATH-CDSN-SCDGTA->ECDGTA-CGSN-SCGGTA->ECGTA-OPSN-PKG-OPCODE-<A>/F"STATUS","PATH-CDSN-SCDGTA-CGSN-CGGTA-OPSN-PKG-OPCODE-<A>/F","GTTACTNA","GTTADISC0","GTTADISC1", "GTTADISC2","GTTADUP","GTTAFWD","GTTASRVGFLX","GTTASRVGPRT","GTTASRVSMSR""K","path1-cdlim1-12345-cglim2-123-oplim3-ituuni-<1-1-1-1-1-1-1>",0,0,0,0,0,0,0,0,0"K","gttp5-#-#-cglim2-126-opname3-bgn-10",0,0,0,0,0,0,0,0,0"K","p6-#-#-cglim6-1234-#-#-#",0,0,0,0,0,0,0,0,0

Assuming each data line will be: 4 char status + 169 char(PATH-CDSN-SCDGTA-CGSN-CGGTA-OPSN-PKG-OPCODE-<A>/F)+ 9*(6 char data) + 2 = 229chars, the typical file size is:


ReportsMeasurements

Table 184: Typical File Size: mtch-gttapath.csv

File Size=Report data(1000 paths)+Report

header+Systemheader

229576=229000+326+250

DEIR MTCH Report

The DEIR measurements specify the entity type deir and include two hourly reports:

• Per system (DEIRSYS)• Per diameter connection (DEIRCONN)

Table 116: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) DEIR Measurements lists theevents added in all DEIR measurements reports.

The retention period for the hourly reports is 24 hours.


rept-ftp-meas:type=mtch:enttype=deir

Table 185: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) DEIR Measurements


Peg countTotal number ofME-Identity-Check requests(ECR) received by the EIR.

ECRRCV

Peg countTotal number of searches thatresulted in a match with a "whitelisted" IMEI.

WHITEIMEI

Peg countTotal number of searches thatresulted in a match with a "graylisted" IMEI.

GRAYIMEI

Peg countTotal number of searches thatresulted in a match with a "blacklisted" IMEI.

BLACKIMEI


BLKALIMEI

listed" IMEI, but were alloweddue to IMSI Check match.


BLKNALIMEI

listed" IMEI, and the IMSI in thedatabase did not match the IMSIin the message.


ReportsMeasurements


Peg countTotal number of searches thatresulted in a match with an"unknown" IMEI.

UNKNIMEI

Peg countTotal number of searches thatresulted in no match in thedatabase.

NOMTCHIMEI


K - indicates good dataI - indicates incompleteintervalN - indicates data not current


mtch-deirsys_yyyymmdd_hhmm.csvHourly DEIR system total measurements report

mtch-deirconn_yyyymmdd_hhmm.csvHourly DEIR per diameter connectionmeasurements report

FTP example output file format for DEIR system total report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 45.1.0-64.74.1","2013-06-20","10:48:59 AM","MST ","HOURLY MAINTENANCE MEASUREMENTS ON DEIR SYSTEM","SPECIFIC","2013-06-19","21:00:00","22:00:00",1

"STATUS","ECRRCV","WHITEIMEI","GRAYIMEI","BLACKIMEI","BLKALIMEI","BLKNALIMEI","UNKNIMEI","NOMTCHIMEI""K",23723,7687,0,16036,0,0,0,7687




Table 186: Typical File Size: mtch-deirsys.csv


Systemheader

417 bytes=54+104+250

FTP example output file format for per diameter connection report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","EAGLE5 45.1.0-64.74.1","2013-06-20","10:38:59 AM","MST ","HOURLY MAINTENANCE MEASUREMENTS ON DEIR PER-CONNECTION","SPECIFIC","2013-06-19","21:00:00","22:00:00",5

"STATUS","DCNAME","ECRRCV","WHITEIMEI","GRAYIMEI","BLACKIMEI","BLKALIMEI","BLKNALIMEI","UNKNIMEI","NOMTCHIMEI"


ReportsMeasurements

"K","d1",100,100,0,0,0,0,0,0"K","d2",768,768,0,0,0,0,0,768"K","d3",0,0,0,0,0,0,0,0"K","d4",500,0,0,500,0,0,0,0"K","d5",1000,0,1000,0,0,0,0,0


4 char status + 18 char (Diameter connection) + 8 * (6 char data) + 2 = 72 chars


Table 187: Typical File Size: mtch-deirconn.csv

File Size=

Report data(512

connections)

Reportheader

Systemheader

37227 bytes=36864 bytes+113+250

ENUM MTCH Report

The ENUM measurements specify the entity type enum and include four hourly reports:

• Per system (ENUMSYS)

Table 188: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System LevelMeasurements lists the events added per system.

• Per card (ENUMCARD)

Table 189: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card Level Measurementslists the events added for each card.

• Per entity (ENUMENT)

Table 190: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity LevelMeasurements lists the events added for each entity ID in the entity ID table or each DN block inthe DN block profile table.

• Per ACL (ENUMACL)

Table 191: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL Level Measurementslists the events added for each ACL entry in the ACL table.

The retention period is 24 hours.


rept-ftp-meas:type=mtch:enttype=enum


ReportsMeasurements

Table 188: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM System LevelMeasurements



ENUMQRYRX


ENUMNAPTRRX


ENUMNSRX


ENUMCNAMERX


ENUMQRYRJTD


ENUMCNGDISC


ENUMACLDISC


ENUMTXRC0

Peg countTotal number of ENUM errorresponses sent due to ENUMQuery format error

ENUMTXRC1

Peg countTotal number of ENUM errorresponses sent due to ENUMServer failure

ENUMTXRC2


ENUMTXRC3


ENUMTXRC4


ENUMTXRC5


ENUMTXDEFPR




ReportsMeasurements



Table 189: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Card LevelMeasurements



ENUMCQRYRX


ENUMCNAPTRX


ENUMCNSRX


ENUMCCNAMRX


ENUMCQRRJTD


ENUMCCNGDSC


ENUMCACLDSC


ENUMCTXRC0


ENUMCTXRC1


ENUMCTXRC2


ENUMCTXRC3


ENUMCTXRC4


ENUMCTXRC5


ENUMCTXDEFP


ReportsMeasurements




Table 190: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM Entity LevelMeasurements


Peg countTotal number of ENUM queriesreceived or ENUM responsessent per entity

ENUMENTMSGS



Table 191: Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) ENUM ACL LevelMeasurements



ENUMACLQRCV


ENUMACLQRJD


ENUMACLRC0


ENUMACLRC1


ENUMACLRC2


ENUMACLRC3


ENUMACLRC4


ReportsMeasurements



ENUMACLRC5




mtch-enumsys_yyyymmdd_hhmm.csvHourly ENUM system totals measurements report

mtch-enumcard_yyyymmdd_hhmm.csvHourly ENUM per card measurements report

mtch-enument_yyyymmdd_hhmm.csvHourly ENUM per entity measurements report

mtch-enumacl_yyyymmdd_hhmm.csvHourly ENUM per acl measurements report

FTP example output file format for system total report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:32","MST ","HOURLY MAINTENANCE MEASUREMENTS ON ENUM SYSTEM","LAST","2014-08-22","21:00:00","22:00:00",1

"STATUS","ENUMQRYRX","ENUMNAPTRRX","ENUMNSRX","ENUMCNAMERX","ENUMQRYRJTD","ENUMCNGDISC","ENUMACLDISC","ENUMTXRC0","ENUMTXRC1","ENUMTXRC2","ENUMTXRC3","ENUMTXRC4","ENUMTXRC5","ENUMTXDEFPR""K",2134,0,2134,0,0,0,0,2134,0,0,0,0,0,0




Table 192: Typical File Size: mtch-enumsys.csv


Systemheader

529 bytes=90 bytes+189+250

FTP example output file format for per card report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:35","MST ","HOURLY MAINTENANCE MEASUREMENTS ON ENUM PER-CARD","LAST","2014-08-22","21:00:00","22:00:00",2

"STATUS","LOC","ENUMCQRYRX","ENUMCNAPTRX","ENUMCNSRX","ENUMCCNAMRX","ENUMCQRRJTD","ENUMCCNGDSC","ENUMCACLDSC","ENUMCTXRC0","ENUMCTXRC1","ENUMCTXRC2","ENUMCTXRC3","ENUMCTXRC4","ENUMCTXRC5","ENUMCTXDEFP"


ReportsMeasurements

"K","1101",2134,0,2134,0,0,0,0,2134,0,0,0,0,0,0"K","1105",0,0,0,0,0,0,0,0,0,0,0,0,0,0


4 char status + 7 char (card) + 14 * (6 char data) + 2 = 95 chars


Table 193: Typical File Size: mtch-enumcard.csv

File Size=Report data(250 card)

Reportheader

Systemheader

24203 bytes=23750 bytes+203+250

FTP example output file format for per entity report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:33","MST ","HOURLY MAINTENANCE MEASUREMENTS ON ENUM PER-ENTITY","LAST","2014-08-22","21:00:00","22:00:00",2

"STATUS","ENTITY ID","SDN","EDN","ENUMENTMSGS""K","123456789012345","","",0"K","123456789123456","","",2134


4 char status + 3* (18 char Entity ID/SDN/EDN) + (6 char data) + 2 = 66 chars


Table 194: Typical File Size: mtch-enument.csv

File Size=

Report data(1024

entries)

Reportheader

Systemheader

67882 bytes=67584 bytes+48+250

FTP example output file format for per ACL report:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS""tekelecstp","UNKNOWN ??.?.?-65.27.0","2014-08-22","22:01:34","MST ","HOURLY MAINTENANCE MEASUREMENTS ON ENUM PER-ACL","LAST","2014-08-22","21:00:00","22:00:00",1

"STATUS","IP ADDRESS","ENUMACLQRCV","ENUMACLQRJD","ENUMACLRC0","ENUMACLRC1","ENUMACLRC2","ENUMACLRC3","ENUMACLRC4","ENUMACLRC5""K","10.*.*.*",2134,0,2134,0,0,0,0,0


4 char status + 18 char (IP Address) + 8 * (6 char data) + 2 = 72 chars


ReportsMeasurements


Table 195: Typical File Size: mtch-enumacl.csv

File Size=Report data(100 entries)

Reportheader

Systemheader

7579 bytes=7200 bytes+129+250

Gateway Measurements (GTWY)

The GTWY measurement report collects and reports gateway-related data from the STP. The gatewayrelated data collected for this report is the network management and global title translation load onthe EAGLE, and the source of this load. The level and source of pass through TCAP traffic is alsocollected. The MTP cards measure this data which is reported when requested.

Entity Types:STP, ORIGNI, ORIGNINC, LNKSET, LSDESTNI, LSORIGINI, and LSONISMT




Reporting Mode: Scheduled, On-demand

Accessible Collection Period: Last, Specific

STP GTWY Report

Command Examples

• UI

rept-meas:type=gtwy:enttype=stp

• FTP

rept-ftp-meas:type=gtwy:enttype=stp

Measurement Events

Table 196: Gateway STP Measurements


peg countNumber of Global TitleTranslations (GTTs) performed

GTTPFDIC

on messages received from aninterconnecting network.


ReportsMeasurements


peg countNumber of MSUs discarded dueto screening failure.

MSUDSCRD

peg countNumber of MSUs rejected dueto screening - disallowed OPC.

MSURJOPC

peg countNumber of MSUs rejected dueto screening - disallowed DPC.

MSURJDPC

peg countNumber of MSUs rejected dueto screening - invalid serviceinformation octet (SIO).

MSURJSIO

peg countNumber of MSUs rejected dueto screening - invalid callingparty address.

MSURJCPA

peg countNumber of subsystem prohibited(SSP) and subsystem allowed

MSURJAPC

(SSA) MSUs rejected due toscreening - invalid affected pointcode.

peg countNumber of subsystem status test(SST) MSUs rejected due to

MSURJPCS

screening - invalid affected pointcode and SSN.

peg countNumber of MTP-NM MSUsrejected due to screening -invalid affected destination field.

MSURJDST

peg countNumber of SCCP MSUs rejecteddue to screening - invalidtranslation type.

MSURJTT

peg countNumber of SCCP MSUs rejecteddue to screening - disallowed

MSURJDSN

DPC/SSN in called partyaddress.

peg countNumber of transfer controlled(TFC) MSUs rejected due to

MSURJTFC

screening - invalid affecteddestination field.

peg countNumber of signaling routesettest (SRST) MSUs rejected due to

MSURJSRT



ReportsMeasurements




peg countNumber of translation typemapping translations performed.

TTMAPPF

For example, a mapped SS7message translation type wasfound for the existing SS7message translation type.

UI Reports

UI Example Output:

tekelecstp 03-12-19 12:51:24 EST EAGLE 34.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON STP REPORT PERIOD: LAST REPORT INTERVAL: 03-12-19, 12:00:00 THROUGH 12:29:59

STP-GTWY MEASUREMENTS

These measurements are from 03-12-19, 12:00:00 through 12:29:59. TTMAPPF = 0, GTTPFDIC = 0, MSUDSCRD = 0, MSURJOPC = 0, MSURJDPC = 0, MSURJSIO = 0, MSURJCPA = 0, MSURJAPC = 0, MSURJPCS = 0, MSURJDST = 0, MSURJTT = 0, MSURJDSN = 0, MSURJTFC = 0, MSURJSRT = 0

; tekelecstp 03-12-19 12:51:26 EST EAGLE 34.0.0 END OF ON-DEMAND STP-GTWY MEASUREMENT REPORT;

FTP Reports

FTP Example Output File Name: gtwy-stp_19990117_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","GATEWAY MEASUREMENTS ON STP","LAST","1999-01-17","15:00:00","15:30:00",1<cr><lf><cr><lf>"STATUS","TTMAPPF","GTTPFDIC","MSUDSCRD","MSURJOPC","MSURJDPC","MSURJSIO", "MSURJCPA","MSURJAPC","MSURJPCS","MSURJDST","MSURJTT","MSURJDSN","MSURJTFC", "MSURJSRT"<cr><lf>"K",0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>



ReportsMeasurements

Table 197: Typical File Size: gtwy-stp.csv


header

504 bytes=90+164+250

ORIGNI GTWY Report

Command Examples

• UI

rept-meas:type=gtwy:enttype=origni:ni=200

• FTP

rept-ftp-meas:type=gtwy:enttype=origni

Measurement Events

Table 198: Gateway ORIGNI Measurements


peg countNumber of global titletranslations (GTTs) performed -

GTTPFDPC

result is a DPC of aninterconnecting network.

peg countNumber of GTTs unable toperform on messages received

GTTUNTT

from an interconnecting network- no translation table for thetranslation type.

peg countNumber of GTTs performed onmessages received from aninterconnecting network.

GTTPFDIC


GTTUNADR

from an interconnecting network- no translation for this address.




ReportsMeasurements

UI Reports

UI Example Output:

tekelecstp 03-12-19 12:31:12 EST EAGLE 34.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON ORIGNI REPORT PERIOD: LAST REPORT INTERVAL: 03-12-19, 12:00:00 THROUGH 12:29:59

ORIGNI-GTWY MEASUREMENTS: NI: 5

These measurements are from 03-12-19, 12:00:00 through 12:29:59. GTTPFDPC = 0, GTTUNTT = 0, GTTPFDIC = 834033, GTTUNADR = 834034

; tekelecstp 03-12-19 12:31:13 EST EAGLE 34.0.0 END OF ON-DEMAND ORIGNI-GTWY MEASUREMENT REPORT;

FTP Reports

FTP Example Output File Name: gtwy-origni_19990117_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","GATEWAY MEASUREMENTS ON ORIGNI","LAST","1999-01-17","15:00:00","15:30:00",100<cr><lf><cr><lf>"STATUS","NI","GTTPFDPC","GTTUNTT","GTTPFDIC","GTTUNADR"<cr><lf>"K",100,0,0,834033,834034<cr><lf>. . . . ."K",200,0,0,834033,834034<cr><lf>


4 char status + 4 char NI + 4*(6 char data) + 2 = 34 chars

For a report of 100 NIs, typical file size is:

Table 199: Typical File Size: gtwy-origni.csv


header

3709 bytes=3400+59+250

ORIGNINC GTWY Report

Command Examples

• UI

rept-meas:type=gtwy:enttype=origninc:ni=4:nc=200


ReportsMeasurements

• FTP

rept-ftp-meas:type=gtwy:enttype=origninc

Measurement Events

Table 200: Gateway ORIGNINC Measurements


peg countNumber of global titletranslations (GTTs) performed -

GTTPFDPC

result is a DPC of aninterconnecting network.


GTTUNTT

from an interconnecting network- no translation table for thetranslation type.

peg countNumber of GTTs performed onmessages received from aninterconnecting network.

GTTPFDIC


GTTUNADR

from an interconnecting network- no translation for this address.



UI Reports

UI Example Output:

tekelecstp 03-12-19 12:31:37 EST EAGLE 34.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON ORIGNINC REPORT PERIOD: LAST REPORT INTERVAL: 03-12-19, 12:00:00 THROUGH 12:29:59

ORIGNINC-GTWY MEASUREMENTS: NI: 5, NC: 5

These measurements are from 03-12-19, 12:00:00 through 12:29:59. GTTPFDPC = 0, GTTUNTT = 0, GTTPFDIC = 834033, GTTUNADR = 834034

; tekelecstp 03-12-19 12:31:38 EST EAGLE 34.0.0


ReportsMeasurements

END OF ON-DEMAND ORIGNINC-GTWY MEASUREMENT REPORT;

FTP Reports

FTP Example Output File Name: gtwy-origninc_19990117_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","GATEWAY MEASUREMENTS ON ORIGNINC","LAST","1999-01-17","15:00:00","15:30:00",100<cr><lf><cr><lf>"STATUS","NI","NC","GTTPFDPC","GTTUNTT","GTTPFDIC","GTTUNADR"<cr><lf>"K",4,200,0,0,834033,834034<cr><lf>. . . . ."K",25,200,0,0,834033,834034<cr><lf>


4 char status + 4 char NI + 4 char NC + 4*(6 char data) + 2 = 38 chars

For a report of 100 NI/NCs, the typical file size is:

Table 201: Typical File Size: gtwy-origninc.csv


header

4114 bytes=3800+64+250

LNKSET GTWY Report

Note: The determination of which linksets are included in this report is controlled by the state of thegtwylsfltr field in the measurement control table. By default, only gateway linksets are included. Thiscan be changed with the chg-meas:gtwylsfltr={ both | stp | seas | none } command.See the Commands User's Guide for details on using this command.

Command Examples

• UI

rept-meas:type=gtwy:enttype=lnkset:lsn=ls1201a

• FTP

rept-ftp-meas:type=gtwy:enttype=lnkset


ReportsMeasurements

Measurement Events

Table 202: Gateway Linkset Measurements


peg countThe number of transferprohibited (TFP) and transfer

TFPTRAN

cluster prohibited (TCP) MSUstransmitted.

peg countThe number of TFP and TCPMSUs received.

TFPRECD

peg countThe number of transfer restricted(TFR) and transfer cluster

TFRTRAN

restricted (TCR) MSUstransmitted.

peg countThe number of TFR and TCRMSUs received.

TFRRECD

peg countThe number of transfer allowed(TFA) and transfer cluster

TFATRAN

allowed (TCA) MSUstransmitted.

peg countThe number of TFA and TCAMSUs received.

TFARECD

peg countThe number of signaling routesettest (SRST) and cluster signaling

SRSTTRAN

routeset test (CSRST) MSUstransmitted.

peg countThe number of SRST and CSRSTMSUs received.

SRSTRECD

peg countThe number of signaling routesetcongestion test (SRSCT) MSUstransmitted.

SRSCTRAN

peg countThe number of SRSCT MSUsreceived.

SRSCTRCD




ReportsMeasurements


peg countThe number of testing andmaintenance (T&M) MSUsreceived.

TSTMTRCD

peg countThe number of subsystemprohibited (SSP) MSUstransmitted.

SSPTRAN

peg countThe number of SSP MSUsreceived.

SSPRECD

peg countThe number of subsystemallowed (SSA) MSUstransmitted.

SSATRAN

peg countThe number of SSA MSUsreceived.

SSARECD

peg countThe number of subsystem statustest (SST) MSUs transmitted.

SSTTRAN

peg countThe number of SST MSUsreceived.

SSTRECD

peg countThe number of signaling linktests received.

SLTRECD



I– indicates incomplete interval;


Note: Output is identical for all linkset types.

UI Reports

• Example of rept-meas:type=gtwy:enttype=lnkset:lsn=xxxx

tekelecstp 12-02-21 02:00:53 EST EAGLE5 44.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON LNKSET REPORT PERIOD: LAST REPORT INTERVAL: 12-02-21, 01:30:00 THROUGH 01:59:59

LNKSET-GTWY MEASUREMENTS: gtwy (MTP2)

These measurements are from 12-02-21, 01:30:00 through 01:59:59. TFPTRAN = 0, TFPRECD = 0, TFRTRAN = 0, TFRRECD = 0, TFATRAN = 0, TFARECD = 0, SRSTTRAN = 0, SRSTRECD = 0, SLTRECD = 0, SRSCTRAN = 0, SRSCTRCD = 0, TSTMTRCD = 0, SSPTRAN = 0, SSPRECD = 0, SSATRAN = 0,


ReportsMeasurements

SSARECD = 0, SSTTRAN = 0, SSTRECD = 0

;

tekelecstp 12-02-21 02:30:52 EST EAGLE5 44.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON LNKSET REPORT PERIOD: LAST REPORT INTERVAL: 12-02-21, 02:00:00 THROUGH 02:29:59

LNKSET-GTWY MEASUREMENTS: hcmimt1 (MTP2-UNCH)

These measurements are from 12-02-21, 02:00:00 through 02:29:59. TFPTRAN = 0, TFPRECD = 0, TFRTRAN = 0, TFRRECD = 0, TFATRAN = 0, TFARECD = 0, SRSTTRAN = 0, SRSTRECD = 0, SLTRECD = 0, SRSCTRAN = 0, SRSCTRCD = 0, TSTMTRCD = 0, SSPTRAN = 0, SSPRECD = 0, SSATRAN = 0, SSARECD = 0, SSTTRAN = 0, SSTRECD = 0

;

FTP Reports

FTP Example Output File Name: gtwy-lnkset_20101005_2030.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","02:32:03","EST ","GATEWAY MEASUREMENTS ON LNKSET","LAST","2012-02-21","02:00:00","02:30:00",2<cr><lf><cr><lf>"STATUS","LSN","LNKTYPE","TFPTRAN","TFPRECD","TFRTRAN","TFRRECD","TFATRAN","TFARECD","SRSTTRAN","SRSTRECD","SLTRECD","SRSCTRAN","SRSCTRCD","TSTMTRCD","SSPTRAN","SSPRECD","SSATRAN","SSARECD","SSTTRAN","SSTRECD"<cr><lf>"K","hcmimt1","MTP2-UNCH",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>"K","gtwy","MTP2",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>



Table 203: Typical File Size: gtwy-lnkset.csv


header

69,962 bytes=69,500+212+250

LSDESTNI GTWY Report

Note:

The determination of which linksets are included in this report is controlled by the state of the gtwylsfltrfield in the measurement control table. By default, only gateway linksets are included. This can be


ReportsMeasurements

changed with the chg-meas:gtwylsfltr={ both | stp | seas | none } command. Seethe Commands User's Guide for details on using this command. The NI parameter is not part of theoutput for ITU GTWY linksets.

Command Examples

• UI

rept-meas:type=gtwy:enttype=lsdestni:lsn=ls1201:ni=5

• FTP

rept-ftp-meas:type=gtwy:enttype=lsdestni

Measurement Events

Table 204: Gateway LSDESTNI Measurements


peg countThe number of MSUs receivedfrom another network - notaddressed to the BCC network.

MSURCVNA

octetsThe number of MSU octetsreceived from another network

OCTRCVNA

- not addressed to the BCCnetwork.

peg countThe number of MSUstransmitted - addressed to a

MSUTRNNA

network other than the adjacentreceiving network.

octetsThe number of MSU octetstransmitted - addressed to a

OCTTRNNA

network other than the adjacentreceiving network.



peg countThe number transfer controlled(TFC) MSUs transmitted -originated by the gateway STP.

TFCGTRAN


ReportsMeasurements

UI Reports

UI Example Output:

tekelecstp 03-12-19 12:30:16 EST EAGLE 34.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON LSDESTNI REPORT PERIOD: LAST REPORT INTERVAL: 03-12-19, 12:00:00 THROUGH 12:29:59

LSDESTNI-GTWY MEASUREMENTS: LSN: ls1201, NI: 5

These measurements are from 03-12-19, 12:00:00 through 12:29:59. MSURCVNA = 5040000, OCTRCVNA = 201600K, MSUTRNNA = 834033, OCTTRNNA = 14757021, TFCGTRAN = 0

; tekelecstp 03-12-19 12:30:18 EST EAGLE 34.0.0 END OF ON-DEMAND LSDESTNI-GTWY MEASUREMENT REPORT;

FTP Reports

FTP Example Output File Name: gtwy-lsdestni_19990117_1530.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","GATEWAY MEASUREMENTS ON LSDESTNI","LAST","1999-01-17","15:00:00","15:30:00",400<cr><lf><cr><lf>"STATUS","LSN","LSTYPE","NI","MSURCVNA","OCTRCVNA","MSUTRNNA","OCTTRNNA","TFCGTRAN"<cr><lf>"K","ls1201","ANSI",5,5040000,201600K,834033,14757021,0<cr><lf>. . . . ."K","lsitu","ITU",,5040000,201600K,834033,14757021,0<cr><lf>


4 char status + 8 char LSN + 6 char LSTYPE + 4 char NI + 5*(6 char data) + 2 = 54 chars

For a report of 400 LSDESTNIs, the typical file size is:

Table 205: Typical File Size: gtwy-lsdestni.csv


header

21936 bytes=21600+86+250

LSORIGNI GTWY Report

Note:

The determination of which linksets are included in this report is not controlled by the state of thegtwylsfltr field in the measurement control table. LSONISMT register MSUISPMT counts are rolled


ReportsMeasurements

into the MSUDSCRD register. It is possible to have counts for MSUDSCRD, but no counts for anyother registers in this report due to the MSUISPMT register count in the LSONISMT report.

The NI parameter is not part of the output for ITU GTWY linksets.


Command Examples

• UI

rept-meas:type=gtwy:enttype=lsorigni:lsn=ls1201:ni=12

• FTP

rept-ftp-meas:type=gtwy:enttype=lsorigni

Measurement Events

Table 206: Gateway LSORGINI Measurements


peg countThe number of transfercontrolled (TFC) MSUs received

TFCGRECD

peg countThe number of MSUs rejecteddue to screening - disallowedOPC.

MSURJOPC

peg countThe number of MSUs rejecteddue to screening - disallowedDPC.

MSURJDPC

peg countThe number of MSUs rejecteddue to screening - invalid callingparty address.

MSURJCPA

peg countThe number of subsystemprohibited (SSP) and subsystem

MSURJAPC

allowed (SSA) MSUs rejecteddue to screening - invalidaffected point code.

peg countThe number of subsystem statustest (SST) MSUs rejected due to

MSURJPCS

screening - invalid affected pointcode and SSN.

peg countNumber of MSUs discarded dueto screening H0H1

MSURJHC

peg countThe number of TFC MSUsrejected due to screening -invalid affected destination field.

MSURJTFC


ReportsMeasurements


peg countThe number of signaling routesettest (SRST) MSUs rejected due to

MSURJSRT


peg countThe number of MSUs rejecteddue to screening failure.

MSUDSCRD

peg countThe number of MSUs rejecteddue to screening - invalid serviceinformation octet (SIO).

MSURJSIO

peg countThe number of MTP-NM MSUsrejected due to screening -invalid affected destination field.

MSURJDST

peg countThe number of SCCP MSUsrejected due to screening -invalid translation type.

MSURJTT

peg countThe number of SCCP MSUsrejected due to screening -disallowed DPC/SSN.

MSURJDSN



peg countThe number of transfercontrolled (TFC) MSUs received

TFCGRECD

UI Reports

UI Example Output:

tekelecstp 03-12-19 12:29:26 EST EAGLE 34.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON LSORIGNI REPORT PERIOD: LAST REPORT INTERVAL: 03-12-19, 11:30:00 THROUGH 11:59:59

LSORIGNI-GTWY MEASUREMENTS: LSN: ls1201, NI: 5

These measurements are from 03-12-19, 11:30:00 through 11:59:59. TFCRECD = 0, MSURJOPC = 834033, MSURJDPC = 834034, MSURJCPA = 14757021, MSURJAPC = 14757039, MSURJPCS = 0, MSURJTFC = 0, MSURJSRT = 0, MSUDSCRD = 0, MSURJSIO = 0, MSURJDST = 0, MSURJTT = 0, MSURJDSN = 0

;


ReportsMeasurements

tekelecstp 03-12-19 12:29:27 EST EAGLE 34.0.0 END OF ON-DEMAND LSORIGNI-GTWY MEASUREMENT REPORT

FTP Reports

FTP Example Output File Name: gtwy-lsorigni_19990117_1530.csv

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST","GATEWAY MEASUREMENTS ON LSORIGNI","LAST","1999-01-17","15:00:00","15:30:00",400<cr><lf><cr><lf>"STATUS","LSN","LSTYPE","NI","TFCGRECD","MSURJOPC","MSURJDPC","MSURJCPA","MSURJAPC","MSURJPCS","MSURJHC","MSURJTFC","MSURJSRT","MSUDSCRD","MSURJSIO","MSURJDST","MSURJTT","MSURJDSN"<cr><lf>"K","ls1201","ANSI",5,0,834033,834034,14757021,14757039,0,0,0,0,0,0,0,0,0<cr><lf>. . . . ."K","lsitu","ITU",,0,834033,834034,14757021,14757039,0,0,0,0,0,0,0,0,0<cr><lf>


4 char status + 8 char LSN + 6 char LSTYPE + 4 char NI + 14*(6 char data) + 2 = 108 chars

For a report of 400 LSORIGNIs, typical file size is:

Table 207: Typical File Size: gtwy-lsorigni.csv


header

43623 bytes=43200+173+250

LSONISMT GTWY Report

Note:

The determination of which linksets are included in this report is not controlled by the state of thegtwylsfltr field in the measurement control table. MSUISPMT counts are rolled into the MSUDSCRDregister of the LSORIGNI and STP reports.



Command Examples

• UI

rept-meas:type=gtwy:enttype=lsonismt:lsn=ls1201a:ni=43

• FTP

rept-ftp-meas:type=gtwy:enttype=lsonismt


ReportsMeasurements

Measurement Events

Table 208: Gateway LSONISMT Measurements


peg countNumber of ISDNUP MSUsrejected due to screening --invalid ISUP message type

MSUISPMT

UI Reports

UI Example Output:

tekelecstp 03-12-19 12:29:26 EST EAGLE 34.0.0 TYPE OF REPORT: GATEWAY MEASUREMENTS ON LSONISMT REPORT PERIOD: LAST REPORT INTERVAL: 02-12-19, 12:00:00 THROUGH 12:29:59

LSONISMT-GTWY MEASUREMENTS: LSN: ls1201a, NI: 43, ISMT: 6

These measurements are from 02-12-19, 12:00:00 through 12:29:59. MSUISPMT = 45397

; LSONISMT-GTWY MEASUREMENTS: LSN: ls1201a, NI: 43, ISMT: 7

These measurements are from 02-12-19, 12:00:00 through 12:29:59. MSUISPMT = 61423; tekelecstp 02-12-19 12:41:21 EST EAGLE 34.0.0 END OF ON-DEMAND LSONISMT-GTWY MEASUREMENT REPORT;

FTP Reports

FTP Example Output File Name: gtwy-lsonismt_20021217_1530.csv

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","30.0.0-48.1.0","2002-12-17","15:51:37","EST","GATEWAY MEASUREMENTS ON LSONISMT","LAST","2002-12-17","15:00:00","15:30:00",400<cr><lf><cr><lf>"STATUS","LSN","LSTYPE","NI","ISMT","MSUISPMT"<cr><lf>"K","ls1201","ANSI",5,6,34033<cr><lf>. . . . ."K","lsitu","ITU",,7,57021<cr><lf>


4 char status + 8 char LSN + 6 char LSTYPE + 4 char NI + 4 char ISMT + 1*(6 char data) + 2 = 34 chars

For a report of 400 LSONISMT, typical file size is:


ReportsMeasurements

Table 209: Typical File Size: gtwy-lsonismt.csv


header

13899 bytes=13600+49+250

Record Base Measurements (RBASE)

The RBASE measurements report various data related to the configuration or status of the EAGLE’smajor configurable components. The data in this measurement report is obtained from either thedatabase or from maintenance tasks performed on the EAGLE. The data is not periodically collectedand stored in the manner of other measurements data, but it is collected on demand when a RBASEmeasurement report is requested.

Entity Types:STP, Lnkset, and Link

Accumulation Interval: Snapshot

STP Retention Period: None

Reporting Mode: Scheduled-Polled (SEAS only), On-demand

Accessible Collection Period: Active

STP RBASE Report

Command Examples

• UI

rept-meas:type=rbase:enttype=stp

• FTP

rept-ftp-meas:type=rbase:enttype=stp

Measurement Events

Table 210: Record Base STP Measurements


peg countThe number of IS-NR or IS-ANRIMT buses

BUSS

secondsThe value of the SCCPManagement: subsystem status

CTSDLSST

test (SS7) delay timer (level 3 T32timer). This value of this timer is


ReportsMeasurements


fixed at 30 seconds and is notconfigurable.

peg countThe number of configuredsignaling links.

LINKS

peg countThe number of configuredlinksets.

LNKSETS

secondsThe value of the delay to avoidmis-sequencing on changeovertimer (level 3 T1 timer).

NT1TDCHO

secondsThe value of the waiting forchangeover acknowledgmenttimer (level 3 T2 timer).

NT2CHOAK

secondsThe value of the delay to avoidmis-sequencing on changebacktimer (level 3 T3 timer).

NT3TDCHB

secondsThe value of the waiting forchangeover acknowledgment

NT4CHBK1

(first attempt) timer (level 3 T4timer).

secondsThe value of the waiting forchangeover acknowledgment

NT5CHBK2

(second attempt) timer (level 3T5 timer).

secondsThe value of the delay to avoidmis-sequencing on controlled

NT6TDCRR

rerouting timer (level 3 T6timer).

secondsThe value of the waiting forsignaling link connection

NT7SLKCN

acknowledgment timer (level 3T7 timer).

secondsThe value of the transferprohibited inhibited timer (level3 T8 timer).

NT8TRPRH

secondsThe value of the waiting torepeat signaling routeset testtimer (level 3 T10 timer).

NT10SRST


ReportsMeasurements


secondsThe value of the transferrestricted timer (level 3 T11timer).

NT11TFRS

secondsThe value of the waiting foruninhibit timer (level 3 T12timer).

NT12UNAK

secondsThe value of the waiting for forceuninhibit timer (level 3 T13timer).

NT13FUNH

secondsThe value of the waiting forinhibition acknowledgmenttimer (level 3 T14 timer).

NT14INAK

secondsThe value of the waiting forrepeat signaling routeset

NT15RSCT

congestion test timer (level 3 T15timer).

secondsThe value of the waiting forrouteset status update timer(level 3 T16 timer).

NT16RSCS

secondsThe value of the delay to avoidoscillation of initial alignment

NT17REAL

failure and restart timer (level 3T17 timer).

secondsThe value of the transfer clusterrestricted interval timer (level 3T18 timer).

NT18TCLR

secondsThe value of the failed link craftreferral timer (level 3 T19 timer).

NT19FLKR

secondsThe value of the waiting torepeat local inhibit test timer(level 3 T20 timer).

NT20RLIH

secondsThe value of the waiting torepeat remote inhibit test timer(level 3 T21 timer).

NT21RRIH

secondsThe value of the restarting SPwaiting for links to become

NT22RSTL

available timer (level 3 T22timer).


ReportsMeasurements


secondsThe value of the waiting afterT22 to receive all TRAs timer(level 3 T23 timer).

NT23WTRA

secondsThe value of the restarting:waiting to broadcast all TRAstimer (level 3 T24 timer).

NT24BTRA

secondsThe value of the adjacent andrestarting: waiting for TRA timer(level 3 T25 timer).

NT25WTRA

secondsThe value of the restarting:waiting to repeat TRW timer(level 3 T26 timer).

NT26RTRW

secondsThe value of the adjacent:waiting for TRW timer (level 3T28 timer).

NT28WTRW

secondsThe value of the TRA sent,unexpected TRA, TRW,

NT29RSUX

resumption timer (level 3 T29timer).

secondsThe value of the limitTFPs/TFRs for unexpected

NT30LMTF

TRAs/TRWs timer (level 3 T30timer).

secondsThe value of the false linkcongestion detection timer (level3 T31 timer).

NT31FLCD

secondsThe value of the link oscillationfilter - procedure A timer (level3 T32 timer).

NT32OSCA

peg countThe number of configured cardsthat are in service normal

PROCS

(IS-NR) or in-service abnormal(IS-ANR).




ReportsMeasurements


secondsThe value of the supervisiontimer for circular route detection

STLOOP

test timer (the value of themtpltst parameter of thechg-stpopts command).

secondsJT-Q.704/NTT-Q.704 Tc timer:To release (reset) transfer

NTCRSCS

controlled status of a DPC intime controlled fashion.

UI Reports

UI Example Output:

Tekelecstp 15-09-20 01:10:32 EST EAGLE5 46.3.0.0.0-66.13.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON STP REPORT PERIOD: ACTIVE REPORT INTERVAL: 15-09-20, 01:10:32 THROUGH CURRENT

STP-RBASE MEASUREMENTS

PROCS = 10, LNKSETS = 6, LINKS = 6, BUSS = 2, NT1TDCHO = 0.8, NT2CHOAK = 1.4, NT3TDCHB = 0.8, NT4CHBK1 = 0.8, NT5CHBK2 = 0.8, NT6TDCRR = 0.8, NT7SLKCN = 1, NT8TRPRH = 0.8, NT10SRST = 30, NT11TFRS = 30, NT12UNAK = 0.8, NT13FUNH = 0.8, NT14INAK = 2, NT15RSCT = 3, NT16RSCS = 1.4, NT17REAL = 0.8, NT18TCLR = 10, NT19FLKR = 480, NT20RLIH = 90, NT21RRIH = 90, NT22RSTL = 10, NT23WTRA = 10, NT24BTRA = 10, NT25WTRA = 30, NT26RTRW = 12, NT28WTRW = 3, NT29RSUX = 60, NT30LMTF = 30, NT31FLCD = 60, NT32OSCA = 60, STLOOP = 10, CTSDLSST = 30, NTCRSCS = 4

FTP Reports

FTP Example Output File Name: rbase-stp_20101005_1937.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 46.3.0.0.0-66.13.0","2015-09-20","01:11:25","EST ","RECORD BASE MEASUREMENTS ON STP","ACTIVE","2015-09-20","01:11:25","01:11:25",1<cr><lf><cr><lf>"STATUS","PROCS","LNKSETS","LINKS","BUSS","NT1TDCHO","NT2CHOAK","NT3TDCHB","NT4CHBK1","NT5CHBK2","NT6TDCRR","NT7SLKCN","NT8TRPRH","NT10SRST","NT11TFRS","NT12UNAK","NT13FUNH","NT14INAK","NT15RSCT","NT16RSCS","NT17REAL","NT18TCLR","NT19FLKR","NT20RLIH","NT21RRIH","NT22RSTL","NT23WTRA","NT24BTRA","NT25WTRA","NT26RTRW","NT28WTRW","NT29RSUX","NT30LMTF","NT31FLCD","NT32OSCA","STLOOP","CTSDLSST","NTCRSCS"<cr><lf>"K",10,6,6,2,0.8,1.4,0.8,0.8,0.8,0.8,1,0.8,30,30,0.8,0.8,2,3,1.4,0.8,10,480,90,90,10,10,10,30,12,3,60,30,60,60,10,30,4<cr><lf>




ReportsMeasurements


Table 211: Typical File Size: rbase-stp.csv


header

882 bytes=228+404+250

LINK RBASE Report

Certain registers are reported for MTP2, SAAL, IPVL, and IPVHSL classes. These registers aresummarized in the following table.

Table 212: Registers reported LINK Measurements

SAAL usageMTP2, IPVL, IPVLGW, &IPVHSL usage

Register

not reportedas describedLT1ALNRD

not reportedas describedLT2NOALN

not reportedas describedLT3ALIND

not reportedas describedLT4NMLPV

not reportedas describedLT4EMGPV

not reportedas describedLT5SDSIB

not reportedas describedLT6RMCNG

not reportedas describedLT7XDLAK

Command Examples

• UI

rept-meas:type=rbase:enttype=link:loc=1201:link=a

rept-meas:type=rbase:enttype=link:lsn=ls3

• FTP

rept-ftp-meas:type=rbase:enttype=link


ReportsMeasurements

Measurement Events

Table 213: Record Base Link Measurements


MSUsThe level 1congestion onset

CNGONTH1

threshold for linktransmit buffers

MSUsThe level 1congestion discard

CNGDITH1


MSUsThe level 1congestion

CNGABTH1

abatementthreshold for linktransmit buffers


CNGONTH2



CNGDITH2



CNGABTH2



CNGONTH3



CNGDITH3



CNGABTH3



ReportsMeasurements


statusIndication of DataValidity:

STATUS

K indicatesgood dataI indicatesincompleteintervalN indicatesdata notcurrent

The following registers are applicable to MTP level 2 links ONLY. These registers are omitted fromreports for ATM based links on EAGLE HMI output. On SEAS reports these registers are reportedas ZERO-valued.

secondsThe value of thealigned/ready

LT1ALNRD

timer (level 2 T1timer).

secondsThe value of thenot aligned timer(level 2 T2 timer).

LT2NOALN

secondsThe value of thealigned timer(level 2 T3 timer).

LT3ALIND

secondsThe value of theproving period

LT4NMLPV

(normal) timer(level 2 T4npptimer).

secondsThe value of theproving period

LT4EMGPV

(emergency) timer(level 2 T4epptimer).

secondsThe value of thesending SIB timer(level 2 T5 timer).

LT5SDSIB

secondsThe value of theremote congestion

LT6RMCNG

timer (level 2 T6timer).


ReportsMeasurements


secondsThe value of theexcessive delay of

LT7XDLAK

acknowledgmenttimer (level 2 T7timer).

UI Reports

• rept-meas:type=rbase:enttype=link:loc=1201:link=a

tekelecstp 12-02-21 01:24:28 EST EAGLE5 44.0.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON LINK REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-21, 01:24:28 THROUGH CURRENT

LINK-RBASE MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

CNGONTH1 = 80, CNGDITH1 = 99, CNGABTH1 = 60, CNGONTH2 = 101, CNGDITH2 = 109, CNGABTH2 = 81, CNGONTH3 = 111, CNGDITH3 = 120, CNGABTH3 = 102, LT1ALNRD = 13, LT2NOALN = 11.5, LT3ALIND = 11.5, LT4NMLPV = 2.3, LT4EMGPV = 0.6, LT5SDSIB = 0.1, LT6RMCNG = 4, LT7XDLAK = 1.5

;

tekelecstp1 12-03-22 19:15:21 EST EAGLE5 44.0.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON LINK REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-03-22, 19:15:21 THROUGH CURRENT

LINK-RBASE MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

CNGONTH1 = 480, CNGDITH1 = 600, CNGABTH1 = 241, CNGONTH2 = 605, CNGDITH2 = 720, CNGABTH2 = 481, CNGONTH3 = 725, CNGDITH3 = 840, CNGABTH3 = 606

;


LINK-RBASE MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


;



ReportsMeasurements

LINK-RBASE MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-RBASE MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)

CNGONTH1 = 640, CNGDITH1 = 792, CNGABTH1 = 480, CNGONTH2 = 808, CNGDITH2 = 872, CNGABTH2 = 648, CNGONTH3 = 888, CNGDITH3 = 960, CNGABTH3 = 816, LT1ALNRD = 151, LT2NOALN = 14, LT3ALIND = 14, LT4NMLPV = 30, LT4EMGPV = 3, LT5SDSIB = 0.08, LT6RMCNG = 3, LT7XDLAK = 0.5

;

• rept-meas:type=rbase:enttype=link:lsn=xxx


LINK-RBASE MEASUREMENTS FOR LINKSET mtp2:

LINK-RBASE MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

CNGONTH1 = 80, CNGDITH1 = 99, CNGABTH1 = 60, CNGONTH2 = 101, CNGDITH2 = 109, CNGABTH2 = 81, CNGONTH3 = 111, CNGDITH3 = 120, CNGABTH3 = 102, LT1ALNRD = 13, LT2NOALN = 11.5, LT3ALIND = 11.5, LT4NMLPV = 2.3, LT4EMGPV = 0.6, LT5SDSIB = 0.1, LT6RMCNG = 4, LT7XDLAK = 1.5

;


LINK-RBASE MEASUREMENTS FOR LINKSET ipsg:

LINK-RBASE MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)


;


ReportsMeasurements


LINK-RBASE MEASUREMENTS FOR LINKSET saal:

LINK-RBASE MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


;


LINK-RBASE MEASUREMENTS FOR LINKSET ssedcm2:

LINK-RBASE MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-RBASE MEASUREMENTS FOR LINKSET hcmimt1:

LINK-RBASE MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)

CNGONTH1 = 640, CNGDITH1 = 792, CNGABTH1 = 480, CNGONTH2 = 808, CNGDITH2 = 872, CNGABTH2 = 648, CNGONTH3 = 888, CNGDITH3 = 960, CNGABTH3 = 816, LT1ALNRD = 151, LT2NOALN = 14, LT3ALIND = 14, LT4NMLPV = 30, LT4EMGPV = 3, LT5SDSIB = 0.08, LT6RMCNG = 3, LT7XDLAK = 0.5

;

FTP Reports

FTP Example Output File Name: rbase-link_20101005_2042.csv


ReportsMeasurements


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","01:11:21","EST ","RECORD BASE MEASUREMENTS ON LINK","ACTIVE","2012-02-21","01:11:21","01:11:21",6<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","CNGONTH1","CNGDITH1","CNGABTH1","CNGONTH2","CNGDITH2","CNGABTH2","CNGONTH3","CNGDITH3","CNGABTH3","LT1ALNRD","LT2NOALN","LT3ALIND","LT4NMLPV","LT4EMGPV","LT5SDSIB","LT6RMCNG","LT7XDLAK"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH",640,792,480,808,872,648,888,960,816,151,14,14,30,3,0.080, 3,0.5<cr><lf>"K","ipsg","1103","A ","IPVL",480,600,241,605,720,481,725,840,606,0,0,0,0,0,0,0,0<cr><lf>"K","mtp2","1104","A ","MTP2",80,99,60,101,109,81,111,120,102,13,11.5,11.5,2.3,0.6,0.1,4,1.5 <cr><lf>"K","m3uals","1105","A ","IPVLGW",750,998,401,1000,1248,751,1250,1375,1001,0,0,0,0,0,0,0,0 <cr><lf>"K","ssedcm2","1107","A ","IPVLGW",750,998,401,1000,1248,751,1250,1375,1001,0,0,0,0,0,0,0,0 <cr><lf>"K","saal","1112","A ","SAAL",560,693,420,707,763,567,777,840,714,0,0,0,0,0,0,0,0<cr><lf>



Table 214: Typical File Size: rbase-link.csv


header

145,477 bytes=145,000+227+250

LNKSET RBASE Report

Command Examples

• UI

rept-meas:type=rbase:enttype=lnkset:lsn=1201a

• FTP

rept-ftp-meas:type=rbase:enttype=lnkset


ReportsMeasurements

Measurement Events

Table 215: Record Base Linkset Measurements


peg countThe number of configuredsignaling links.

LINKS

peg countThe number of receiving linkbuffers. The number of receiving

RCLKBFRS

link buffers is always 1 for eachsignaling link, so a value of 1 isalways reported for this register.

secondsSupervision timer for SLTA.ST01SLTA

secondsSLT interval timer.ST02SLTI



UI Reports

rept-meas:type=nm:enttype=lnkset:lsn=xxxx

tekelecstp 12-02-21 01:14:30 EST EAGLE5 44.0.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON LNKSET REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-21, 01:14:30 THROUGH CURRENT

LNKSET-RBASE MEASUREMENTS: mtp2 (MTP2)

LINKS = 1, RCLKBFRS = 1, ST01SLTA = 4, ST02SLTI = 30

;

tekelecstp1 12-03-22 19:12:04 EST EAGLE5 44.0.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON LNKSET REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-03-22, 19:12:04 THROUGH CURRENT

LNKSET-RBASE MEASUREMENTS: ipsg (IPVL)

LINKS = 1, RCLKBFRS = 1

;

tekelecstp1 12-03-22 19:12:09 EST EAGLE5 44.0.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON LNKSET REPORT PERIOD: ACTIVE


ReportsMeasurements

REPORT INTERVAL: 12-03-22, 19:12:09 THROUGH CURRENT

LNKSET-RBASE MEASUREMENTS: saal (SAAL)


;

tekelecstp 12-02-21 01:15:52 EST EAGLE5 44.0.0 TYPE OF REPORT: RECORD BASE MEASUREMENTS ON LNKSET REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-21, 01:15:52 THROUGH CURRENT

LNKSET-RBASE MEASUREMENTS: hcmimt1 (MTP2-UNCH)


;

FTP Reports

FTP Example Output File Name: rbase-lnkset_20101005_1941.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","01:17:12","EST ","RECORD BASE MEASUREMENTS ON LNKSET","ACTIVE","2012-02-21","01:17:12","01:17:12",6<cr><lf><cr><lf>"STATUS","LSN","LNKTYPE","LINKS","RCLKBFRS","ST01SLTA","ST02SLTI"<cr><lf>"K","mtp2","MTP2",1,1,4,30<cr><lf>"K","ipsg","IPVL",1,1,0,0<cr><lf>"K","m3uals","IPVL",1,1,0,0<cr><lf>"K","hcmimt1","MTP2-UNCH",1,1,4,30<cr><lf>"K","ssedcm2","IPVL",1,1,0,0<cr><lf>"K","saal","SAAL",1,1,4,30<cr><lf>



Table 216: Typical File Size: rbase-lnkset.csv


header

33,318 bytes=33,000+68+250


ReportsMeasurements

Maintenance Status Reports (MTCS)

The Maintenance Status (MTCS) report is a snapshot of the maintenance status indicators. It supportsentity types LINK and LNKSET. The report is available through the EAGLE terminal interface andthrough the SEAS interface via the IPSM.

Entity Types: Lnkset and Link

Accumulation Interval: Snapshot

STP Retention Period: None

Reporting Mode: On-demand (EAGLE/SEAS)

Accessible Collection Period: Active (snapshot)

LINK MTCS Report

Command Examples

• UI

rept-meas:type=mtcs:enttype=link:loc=1201:link=a

rept-meas:type=mtcs:enttype=link:lsn=ls3:period=active

• FTP

rept-ftp-meas:type=mtcs:enttype=link

Measurement Events

Table 217: Maintenance Status Link Measurements


ACT – link primary state isIS-NR and is or can be used tocarry traffic.

Maintenance StateLKMTCST

UNAV - link has been madeunavailable by local orcentralized maintenancepersonnel (inhibited or canceledlink or active local processoroutage).

OOS – link out-of-service butcan be made available by theSTP.

Y – link failure reason of remoteprocessor outage exists.

Indication of processor outagestatus units being received.

PROSTAT


ReportsMeasurements


N - link failure reason of remoteprocessor outage does not exist.

Y – link failure reason of localprocessor outage exists.

Indication of processor outagestatus units being transmitted.

PROTRAN

N - link failure reason of localprocessor outage does not exist.

L (Local) - link is deactivated orinhibited or link failure reasonof local processor outage exists.

Indication of link managementinhibit status

MGMTINHB

R (remote) - link failure reasonof remote processor outage existsor remote management initiatedexists.

B (Both) –both local and removefailure reasons exist.

N (Not/Neither) no local orremote failure reasons exists.

Congestion level:Current link transmit congestionlevel

CGSTLEVL

0 – no link congestion

1, 2, or 3 - link congestion levelexists.

N – none (congestion level 0)Current link transmit congestionstate

CGSTSTAT

O – onset (congestion level 1, 2,or 3)

N – not failed.Indication of link declaredfailure state (last known cause)

DCLRFAIL

LSL: Link is available to sendand receive MSUs (in-servicenormal state).

HSL: Same

ABN – link failed due toreceiving too many abnormalFIBR/BNSR.

LSL: Link received 2 out of 3invalid BSNs.

Link received 2 out of 3 invalidFIBs.

HSL: N/A


ReportsMeasurements


XDA – Excessive delay ofacknowledgment

LSL: MSU not acknowledgedwithin level 2 -T7 timerexpiration. T7 configurablebetween .5 and 2.0 seconds.

HSL: Timer no response or timerno credit expired.

XER – Excessive error rate.

Received 64 out of 256 signalingunits in error.

LSL: Signaling Unit Error RateMonitor

HSL: SignalingUnit-Error-Rate-Monitorthreshold exceeded.

XDC – Excessive duration ofcongestion

LSL: Level-2 T6 timed-out

HSL: N/A.

APF – alignment/provingfailure

LSL: Link not aligned. Link statecontrol aligned not ready oraligned ready timeout (T1),initial alignment control timeout(T2,T3), initial alignment controlabort proving – maximumproving period, or initialalignment control received SIOS.

HSL: N/A.




ReportsMeasurements

UI Reports

• rept-meas:type=mtcs:enttype=link:loc=1201:link=a

tekelecstp 12-02-21 04:36:38 EST EAGLE5 44.0.0 TYPE OF REPORT: MAINTENANCE STATUS INDICATORS ON LINK REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-21, 04:36:38 THROUGH CURRENT

LINK-MTCS MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

LKMTCST = 'UNAV', PROSTAT = 'N', PROTRAN = 'N', DCLRFAIL = 'APF', MGMTINHB = 'N', CGSTLEVL = '0', CGSTSTAT = 'N'

;


LINK-MTCS MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)

LKMTCST = 'OOS', PROSTAT = 'N', PROTRAN = 'N', DCLRFAIL = 'MMR', MGMTINHB = 'L', CGSTLEVL = '0', CGSTSTAT = 'N'

;


LINK-MTCS MEASUREMENTS: LOC: 1105, LINK: A , LSN: m3uals (IPVLGW)


;


LINK-MTCS MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


;



ReportsMeasurements

LINK-MTCS MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-MTCS MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)


;

• rept-meas:type=mtcs:enttype=link:lsn=xxx

tekelecstp 12-02-21 04:38:49 EST EAGLE5 44.0.0-64.23.0 TYPE OF REPORT: MAINTENANCE STATUS INDICATORS ON LINK REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-21, 04:38:49 THROUGH CURRENT

LINK-MTCS MEASUREMENTS FOR LINKSET mtp2:

LINK-MTCS MEASUREMENTS: LOC: 1104, LINK: A , LSN: mtp2 (MTP2)

LKMTCST = 'UNAV', PROSTAT = 'N', PROTRAN = 'N', DCLRFAIL = 'APF', MGMTINHB = 'N', CGSTLEVL = '0', CGSTSTAT = 'N'

;


LINK-MTCS MEASUREMENTS FOR LINKSET ipsg:

LINK-MTCS MEASUREMENTS: LOC: 1103, LINK: A , LSN: ipsg (IPVL)


;


LINK-MTCS MEASUREMENTS FOR LINKSET m3uals:


ReportsMeasurements

LINK-MTCS MEASUREMENTS: LOC: 1105, LINK: A , LSN: m3uals (IPVLGW)


;


LINK-MTCS MEASUREMENTS FOR LINKSET saal:

LINK-MTCS MEASUREMENTS: LOC: 1112, LINK: A , LSN: saal (SAAL)


;


LINK-MTCS MEASUREMENTS FOR LINKSET ssedcm2:

LINK-MTCS MEASUREMENTS: LOC: 1107, LINK: A , LSN: ssedcm2 (IPVLGW)


;


LINK-MTCS MEASUREMENTS FOR LINKSET hcmimt1:

LINK-MTCS MEASUREMENTS: LOC: 1203, LINK: A , LSN: hcmimt1 (MTP2-UNCH)


;


ReportsMeasurements

FTP Reports

FTP Example Output File Name: mtcs-link_20101005_2123.csv

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","04:41:05","EST ","MAINTENANCE STATUS INDICATORS ON LINK","ACTIVE","2012-02-21","04:41:05","04:41:05",8<cr><lf><cr><lf>"STATUS","LSN","LOC","LINK","LNKTYPE","LKMTCST","PROSTAT","PROTRAN","DCLRFAIL","MGMTINHB","CGSTLEVL","CGSTSTAT"<cr><lf>"K","hcmimt1","1203","A ","MTP2-UNCH","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>"K","ipsg","1103","A ","IPVL","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>"K","mtp2","1104","A ","MTP2","'UNAV'","'N'","'N'","'APF'","'N'","'0'","'N'"<cr><lf>"K","gtwy","1104","B ","MTP2","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>"K","m3uals","1105","A ","IPVLGW","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>"K","ssedcm2","1107","A ","IPVLGW","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>"K","saal","1112","A ","SAAL","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>"K","gtwy","1104","A1 ","MTP2","'OOS'","'N'","'N'","'MMR'","'L'","'0'","'N'"<cr><lf>



For a report of 600 linksets, the typical file size is:

Table 218: Typical File Size: mtcs-link.csv


header

85,364 bytes=85,000+114+250

LNKSET MTCS Report

Command Examples

• UI

rept-meas:type=mtcs:enttype=lnkset:lsn=ls1201

• FTP

rept-ftp-meas:type=mtcs:enttype=lnkset


ReportsMeasurements

Measurement Events

Table 219: Maintenance Status Linkset Measurements


ACT – link primary state isIS-NR and is or can be used tocarry traffic.

Maintenance StateLKMTCST

UNAV - link has been madeunavailable by local orcentralized maintenancepersonnel (inhibited or canceledlink or active local processoroutage).

OOS – link out-of-service butcan be made available by theSTP.

Number of links in the IS-NR(ACT) state.

Number of currently active links.ACTLINKS

Number of links in theOOS-MT-DSBLD (UNAV) state.

Number of links in theunavailable maintenance state.

UAVLINKS

Number of links in amaintenance state other thanIS-NR and OOS-MT-DSBLD.

Number of out-of-service linksOOSLINKS



UI Reports

UI Example output:

• Example of rept-meas:type=nm:enttype=lnkset:lsn=xxxx

tekelecstp 12-02-21 04:44:56 EST EAGLE5 44.0.0 TYPE OF REPORT: MAINTENANCE STATUS INDICATORS ON LNKSET REPORT PERIOD: ACTIVE REPORT INTERVAL: 12-02-21, 04:44:56 THROUGH CURRENT

LNKSET-MTCS MEASUREMENTS: gtwy (MTP2)

LSMTCST = 'OOS', ACTLINKS = 0, UAVLINKS = 0, OOSLINKS = 2

;


ReportsMeasurements

FTP Reports

FTP Example Output File Name: mtcs-lnkset_20101005_2126.csv


"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"<cr><lf>"tekelecstp","EAGLE5 44.0.0-64.23.0","2012-02-21","04:45:44","EST ","MAINTENANCE STATUS INDICATORS ON LNKSET","ACTIVE","2012-02-21","04:45:44","04:45:44",7<cr><lf><cr><lf>"STATUS","LSN","LNKTYPE","LSMTCST","ACTLINKS","UAVLINKS","OOSLINKS"<cr><lf>"K","mtp2","MTP2","'UNAV'",0,1,0<cr><lf>"K","ipsg","IPVL","'OOS'",0,0,1<cr><lf>"K","m3uals","IPVL","'OOS'",0,0,1<cr><lf>"K","hcmimt1","MTP2-UNCH","'OOS'",0,0,1<cr><lf>"K","ssedcm2","IPVL","'OOS'",0,0,1<cr><lf>"K","saal","SAAL","'OOS'",0,0,1<cr><lf>"K","gtwy","MTP2","'OOS'",0,0,2<cr><lf>



Table 220: Typical File Size: mtcs-lnkset.csv


header

26,320 bytes=26,000+70+250


ReportsMeasurements

Glossary

A

ActivateACT

Alignment Error Rate MonitorAERM

AnalyzedInformation QueryAIQ

Name for the local subsystem andservice for the ANSI41 AIQ feature.

American Standard Code forInformation Interchange

ASCII

ATI Number Portability Query(Name of the local subsystem)

ATINPQ

Asynchronous Transfer ModeATM

A packet-oriented transfer modethat uses an asynchronous timedivision multiplexing technique tomultiplex information flow in fixedblocks, called cells.

A high-bandwidth, low-delayswitching, and multiplexingtechnology to support applicationsthat include high-speed data, localarea network interconnection,multimedia application andimaging, and residentialapplications such as videotelephony and otherinformation-based services.

B

Backward Sequence NumberBSN


C

Called Party Address - The field inthe SCCP portion of the MSU that

CdPA

contains the additional addressinginformation of the destination ofthe MSU. Gateway screening usesthis additional information todetermine if MSUs that contain theDPC in the routing label and thesubsystem number in the calledparty address portion of the MSUare allowed in the network wherethe EAGLE is located.

Calling Party Address - The pointcode and subsystem number that

CgPA

originated the MSU. This pointcode and subsystem number arecontained in the calling partyaddress in the SCCP portion of thesignaling information field of theMSU. Gateway screening uses thisinformation to determine if MSUsthat contain this point code andsubsystem number area allowed inthe network where the EAGLE islocated.

Custom Local Area SignalingService

CLASS

Custom Local Area SubscriberServices

Common Language LocationIdentifier

CLLI

The CLLI uniquely identifies theSTP in terms of its physicallocation. It is usually comprised ofa combination of identifiers for theSTP’s city (or locality), state (orprovince), building, and traffic unitidentity. The format of the CLLI is:

• The first four characters identifythe city, town, or locality


GlossaryMeasurements

C

• The first character of the CLLImust be an alphabeticalcharacter

• The fifth and sixth charactersidentify state or province

• The seventh and eighthcharacters identify the building

• The last three charactersidentify the traffic unit

Calling Name DeliveryCNAM

An IN (Intelligent Network) servicethat displays the caller’s name onthe calling party’s phone. This issimilar to caller ID except that thecalling party’s name is displayedalong with the calling number orinstead of the calling number.

Changeover OrderCOO

CAM Redundancy ControllerCRC

Cyclic Redundancy Check

A number derived from, and storedor transmitted with, a block of datain order to detect corruption. Byrecalculating the CRC andcomparing it to the value originallytransmitted, the receiver can detectsome types of transmission errors.

Comma-Separated ValuesCSV

The comma-separated value fileformat is a delimited data formatthat has fields separated by thecomma character and recordsseparated by newlines (a newlineis a special character or sequenceof characters signifying the end ofa line of text).



D

DatabaseDB

Daughter BoardDocumentation BulletinData bus

Detailed DesignDD

Directory numberDN

A DN can refer to any mobile orwireline subscriber number, andcan include MSISDN, MDN, MIN,or the wireline Dialed Number.

Destination Point Code - DPCrefers to the scheme in SS7

DPC

signaling to identify the receivingsignaling point. In the SS7 network,the point codes are numericaddresses which uniquely identifyeach signaling point. This pointcode can be adjacent to the EAGLE,but does not have to be.

Database Service Module.DSM

The DSM provides large capacitySCCP/database functionality. TheDSM is an application card thatsupports network specific functionssuch as EAGLE ApplicationProcessor (EPAP), Global Systemfor Mobile Communications(GSM), EAGLE Local NumberPortability (ELAP), and interfaceto Local Service ManagementSystem (LSMS).

Database Transport Access - Afeature in the EAGLE that

DTA

encapsulates specific MSUs into thedata portion of SCCP within a new



D

SS7 MSU and sends the new MSUto the destination using global titletranslation. The EAGLE usesgateway screening to determinewhich MSUs are used by the DTAfeature.

E

Engineering Change OrderECO

Equipment Identity RegisterEIR

A network entity used in GSMnetworks, as defined in the 3GPPSpecifications for mobile networks.The entity stores lists ofInternational Mobile EquipmentIdentity (IMEI) numbers, whichcorrespond to physical handsets(not subscribers). Use of the EIRcan prevent the use of stolenhandsets because the networkoperator can enter the IMEI of thesehandsets into a 'blacklist' andprevent them from being registeredon the network, thus making themuseless.

Exception List Exclusion IndicatorELEI

Indicates whether entries made tothe exception list for each clusterpoint code are added to or changedin the destination point code table.

TElephone NUmber Mapping - Atechnology for unifying various

ENUM

communications and telephoneaddresses for private and businessnumbers, facsimile and mobilephone numbers, SMS services,Instant Messaging and email.ENUM integrates legacy phonenumbers with the Domain NameSystem (DNS). Users can access



E

and maintain a directory thatsupports all forms of wiredcommunication, mobilecommunications networks, and theInternet. ENUM allows for an enduser to be reached on multipledevices via one phone number andallows the end user to determinewhich device to contact first ormultiple devices simultaneously.E.164 Number Mapping

F

Forward Indicator BitFIB

Flexible Linkset Optional BasedRouting

FLOBR

A feature that provides thecapability to fully customize thedesired routing translation. Whenflexible routing is used, the routingtranslation can cascade from oneGTT translation table to any otherGTT translation table.

File Transfer ProtocolFTP

A client-server protocol that allowsa user on one computer to transferfiles to and from another computerover a TCP/IP network.

Feature Test Plan

G

GSM Flexible numberingG-Flex

A feature that allows the operatorto flexibly assign individualsubscribers across multiple HLRsand route signaling messages,based on subscriber numbering,accordingly.



G

GSM Mobile Number PortabilityG-Port

A feature that provides mobilesubscribers the ability to changethe GSM subscription networkwithin a portability cluster, whileretaining their original MSISDN(s).

Global System for MobileCommunications

GSM

A second generation digital PCSmobile phone standard used inmany parts of the world.

Global Title AddressGTA

Global Title IndicatorGTI

Global Title TranslationGTT

A feature of the signalingconnection control part (SCCP) ofthe SS7 protocol that the EAGLEuses to determine which servicedatabase to send the query messagewhen an MSU enters the EAGLEand more information is needed toroute the MSU. These servicedatabases also verify calling cardnumbers and credit card numbers.The service databases are identifiedin the SS7 network by a point codeand a subsystem number.

H

Human-to-Machine InterfaceHMI

High-Speed LinkHSL

An innovative distributed I/Otechnology designed forautomation applications that is



H

based on an open standard RS-422,which is designed forfull/half-duplex, multi-drop serialtransmission.

I

Initial Address MessageIAM

Ensures the services offered arecompatible with the receptiondevices, and can be used. Forexample, IAM prevents a phonebeing connected to a facsimile.

Initial Detection PointIDP

Service for the Prepaid IDP QueryRelay feature.

IDPR

International Mobile EquipmentIdentifier

IMEI

International Mobile SubscriberIdentity

IMSI

International Mobile StationIdentityA unique internal network IDidentifying a mobile subscriber.

Inter-Module-TransportIMT

The communication software thatoperates theinter-module-transport bus on allcards except the LIMATM, DCM,DSM, and HMUX.

Intelligent Network ApplicationPart

INAP



I

A standardized interface forintelligent networks (IN). Thisinterface allows Service Providersto offer their own services.

INAP-based Number PortabilityINP

INP can be deployed as astand-alone or an integrated signaltransfer point/number portabilitysolution. With a stand-alone NPserver, no network reconfigurationis required to implement numberportability. The NP server deliversa much greater signaling capabilitythan the conventional SCP-basedapproach.

Intelligent Network (IN) Portability

Intelligent PeripheralIP

Internet Protocol - IP specifies theformat of packets, also calleddatagrams, and the addressingscheme. The network layer for theTCP/IP protocol suite widely usedon Ethernet networks, defined inSTD 5, RFC 791. IP is aconnectionless, best-effort packetswitching protocol. It providespacket routing, fragmentation andre-assembly through the data linklayer.

The location of a device on aTCP/IP network. The IP Address

IP Address

is either a number in dotteddecimal notation which lookssomething like (IPv4), or a 128-bithexadecimal string such as (IPv6).

IP Services ModuleIPSM

A card that provides an IPconnection for the IPUI (Telnet)



I

and FTP-based Table Retrievefeatures. The IPSM is a GPSM-IIcard with a one Gigabyte (UD1G)expansion memory board in asingle-slot assembly running theIPS application.

Interim Standard 41IS-41

Same as and interchangeable withANSI-41. A standard foridentifying and authenticatingusers, and routing calls on mobilephone networks. The standard alsodefines how users are identifiedand calls are routed when roamingacross different networks.

In Service - AbnormalIS-ANR

The entity is in service but onlyable to perform a limited subset ofits normal service functions.

In Service - NormalIS-NR

ISDN User PartISDNUP

ISDN User PartISUP

The ISDN-specific part of thetransmission with additionalinformation via a signaling channelbetween exchanges.

Inter-switch Voice MessagingISVM

International TelecommunicationsUnion

ITU

An organization that operatesworldwide to allow governments



I

and the privatetelecommunications sector tocoordinate the deployment andoperating of telecommunicationsnetworks and services. The ITU isresponsible for regulating,coordinating and developinginternational telecommunications,and for harmonizing nationalpolitical interests.

L

Line Information DatabaseLIDB

Link Interface ModuleLIM

Provides access to remote SS7, IP,and other network elements suchas a Signaling Control Point (SCP)through a variety of signalinginterfaces (DS0, MPL, E1/T1 MIM,LIM-ATM, E1-ATM, IPLIMx,IPGWx). The LIMs consist of amain assembly and possibly, aninterface appliqué board. Theseappliqués provide level one andsome level two functionality on SS7signaling links.

Signaling LinkLink

Carries signaling within a Link Setusing a specific Association. A Linkcan belong to only one Link Set andone Association. There is generallyone Link per Association in a LinkSet.

Local Number PortabilityLNP

The ability of subscribers to switchlocal or wireless carriers and stillretain the same phone number.



L

LNP Query ServiceLNPQS

Location Request MessageLOCREQ

A TDMA/CDMA MSC query toan HLR for retrievingsubscription/location informationabout a subscriber to terminate avoice call.

Location Routing NumberLRN

A 10-digit number in a databasecalled a Service Control Point (SCP)that identifies a switching port fora local telephone exchange. LRN isa technique for providing LocalNumber Portability.

Link Set NameLSN

The name of the link set.

Link Status Signaling UnitLSSU

M

Mated Application PartMAP

Mobile Application Part

An application part in SS7signaling for mobilecommunications systems.

Measurement Collection andPolling Module

MCPM

Provides comma delimited coreSTP measurement data to a remoteserver for processing. The MCPMis either an EDSM with 2 GB ofmemory or an E5-MCPM-B cardrunning the MCP application.



M

A feature that supports the EAGLEbeyond 700 links by providing a

Measurement Platform

dedicated processor for collectingand reporting Measurements data.The Measurement Platformcollection function cannot bedisabled once it is enabled in thesystem.

Measurement PlatformMP

Message Processor - The role of theMessage Processor is to provide theapplication messaging protocolinterfaces and processing.However, these servers also haveOAM components. All MessageProcessors replicate from theirSignaling OAM's database andgenerate faults to a FaultManagement System.

Message RelayMR

Mobile Switching CenterMSC

An intelligent switching system inGSM networks. This systemestablishes connections betweenmobile communicationssubscribers.The primary service delivery nodefor GSM/CDMA, responsible forrouting voice calls and SMS as wellas other services (such asconference calls, FAX and circuitswitched data).

Mobile Station InternationalSubscriber Directory Number

MSISDN

Mobile Subscriber IntegratedServices Digital Network [Number]The MSISDN is the networkspecific subscriber number of amobile communications subscriber.



M

This is normally the phone numberthat is used to reach the subscriber.Mobile Station InternationalSubscriber Directory Number. Theunique, network-specific subscribernumber of a mobilecommunications subscriber.MSISDN follows the E.164numbering plan; that is, normallythe MSISDN is the phone numberthat is used to reach the subscriber.

Message Signal UnitMSU

The SS7 message that is sentbetween signaling points in the SS7network with the necessaryinformation to get the message toits destination and allow thesignaling points in the network toset up either a voice or dataconnection between themselves.The message contains the followinginformation:

• The forward and backwardsequence numbers assigned tothe message which indicate theposition of the message in thetraffic stream in relation to theother messages.

• The length indicator whichindicates the number of bytesthe message contains.

• The type of message and thepriority of the message in thesignaling information octet ofthe message.

• The routing information for themessage, shown in the routinglabel of the message, with theidentification of the node thatsent message (originating pointcode), the identification of thenode receiving the message(destination point code), and thesignaling link selector which theEAGLE uses to pick which link



M

set and signaling link to use toroute the message.

Message Transfer PartMTP

The levels 1, 2, and 3 of the SS7protocol that control all thefunctions necessary to route an SS7MSU through the network

Module Test Plan

N

Nature of Address IndicatorNAI

Standard method of identifyingusers who request access to anetwork.

Network Access Identifier

The user identity submitted by theclient during networkauthentication.

NAI ValueNAIV

Network ClusterNC

Network CodeNot CompliantNorth Carolina

Network IndicatorNI

Network ManagementNM

The execution of the set offunctions required for controlling,planning, allocating, deploying,coordinating and monitoring theresources of a telecommunicationsnetwork, including performingfunctions such as initial networkplanning, frequency allocation,



N

predetermined traffic routing tosupport load balancing,cryptographic key distributionauthorization, configurationmanagement, fault management,security management, performancemanagement, and accountingmanagement. Note: Networkmanagement does not includeuser-terminal equipment.Notification manager

Number PlanNP

Numbering PlanNumber PortabilityA capability that permitstelecommunications users tomaintain the same telephone accessnumber as they changetelecommunication suppliers.

Number Plan AreaNPA

The North American “AreaCodes.” (3 digits: 2- to-9, 0 or 1,0-to-9. Middle digit to expandsoon).

Numbering Plan ProcessorNPP

Provides the flexible serviceapplication behavior that satisfiesthe needs of customers resident incomplex signaling networks. It isused for number conditioning,RTDB lookup, and outgoingnumber formatting.

Numbering Plan ValueNPV

Central Office Exchange CodeNXX

O



O

Operations, Administration, andMaintenance. These functions are

OAM

generally managed by individualapplications and not managed bya platform managementapplication, such as PM&C.

Operations – Monitoring theenvironment, detecting anddetermining faults, and alertingadministrators.

Administration – Typicallyinvolves collecting performancestatistics, accounting data for thepurpose of billing, capacityplanning, using usage data, andmaintaining system reliability.

Maintenance – Provides suchfunctions as upgrades, fixes, newfeature enablement, backup andrestore tasks, and monitoringmedia health (for example,diagnostics).

Out of ServiceOOS

Within an SS7 network, the pointcodes are numeric addresses which

OPC

uniquely identify each signalingpoint. The OPC identifies thesending signaling point.

P

Point CodePC

The identifier of a signaling pointor service control point in anetwork. The format of the pointcode can be one of the followingtypes:

• ANSI point codes in the formatnetwork indicator-networkcluster-network cluster member(ni-nc-ncm).



P

• Non-ANSI domestic point codesin the format networkindicator-networkcluster-network cluster member(ni-nc-ncm).

• Cluster point codes in theformat networkindicator-network cluster-* ornetwork indicator-*-*.

• ITU international point codesin the format zone-area-id.

• ITU national point codes in theformat of a 5-digit number(nnnnn), or 2, 3, or 4 numbers(members) separated by dashes(m1-m2-m3-m4) as defined bythe Flexible Point Code systemoption. A group code isrequired (m1-m2-m3-m4-gc)when the ITUDUPPC feature isturned on.

• 24-bit ITU national point codesin the format main signalingarea-subsignaling area-servicepoint (msa-ssa-sp).

Preventive Cyclic RetransmissionPCR

A method of error correction usedfor the SS7 protocol. PCR is anerror correction method that keepsa copy of each message signal unittransmitted on a signaling link ina retransmission buffer. Ifthereceiving end of the signalinglink receives the MSU with noerrors, positive acknowledgmentmessage is sent to the transmittingend of the signaling link. The MSUis then discarded from theretransmission buffer. If thetransmitting end of the signalinglink does not receive positiveacknowledgment from thereceiving end of the signaling link,the MSU is retransmitted untilpositive acknowledgment is



P

received. The PCR error correctionmethod is assigned to SS7 signalinglinks using the ent-slkcommand.

Q

Query ServerQS

Query Service

R

Random Access MemoryRAM

A type of computer memory thatcan be accessed randomly; that is,any byte of memory can beaccessed without touching thepreceding bytes.

Routing NumberRN

The number provided by theFreephone Service Provider (FSP)to the Access Service Provider(ASP) to enable a pre-determinedrouting of traffic to a specificnetwork/carrier/customer.

A signaling path from an LSP to anRSP using a specified Link Set.

Route

Route Set TestRST

Route Set Prohibited Test (Msg)

Signaling-route-set-test signal forprohibited destination.

Real Time DatabaseRTDB

S

Supervisory Audio ToneSAT



S

Signaling Connection Control PartSCCP

The signaling connection controlpart with additional functions forthe Message Transfer Part (MTP)in SS7 signaling. Messages can betransmitted between arbitrarynodes in the signaling networkusing a connection-oriented orconnectionless approach.

Signaling Engineering andAdministration System

SEAS

An interface defined by Bellcoreand used by the Regional BellOperating Companies (RBOCs), aswell as other Bellcore ClientCompanies (BCCs), to remotelyadminister and monitor thesignaling points in their networkfrom a central location.

Service Information FieldSIF

MTP Service Information Field isthe payload field of an SS7 MSUheader. The first byte of the SIF isthe start of the MTP3 routing label.For MTP3-variant networks, themaximum SIF size is 272 bytes. ForMTP3b-variant networks, themaximum SIF size is 4095 bytes.

The transmission path connectingthe EAGLE to other signaling

Signaling Link

points in the network andproviding access to ANSI SS7 andITU SS7 network elements. Thesignaling link is connected to theEAGLE at the link interface module(LIM).

Service Information OctetSIO



S

The network indicator code (NIC),priority (PRI), and service indicator(SI) in the SIO field in the messagesignaling unit (MSU). Thisinformation identifies the type ofMSU (ISUP, TCAP, and so forth)that is allowed in the networkwhere the EAGLE is located.

Session Initiation ProtocolSIP

A peer-to-peer protocol used forvoice and video communications.

Signaling Link CodeSLC

Signaling Link TestAcknowledgment

SLTA

Short Message ServiceSMS

A communication servicecomponent of the GSM mobilecommunication system that usesstandard communicationsprotocols to exchange short textmessages between mobile phonedevices. See also GSM.

Shared Metric Service

Service ProviderSP

Signaling Point

A set of signaling equipmentrepresented by a unique point codewithin an SS7 domain.

Send Routing InformationSRI

Send_Route_Information Message



S

SubsystemSS

Supplementary Services

Signaling System #7SS7

A communications protocol thatallows signaling points in anetwork to send messages to eachother so that voice and dataconnections can be set up betweenthese signaling points. Thesemessages are sent over its ownnetwork and not over the revenueproducing voice and data paths.The EAGLE is an STP, which is adevice that routes these messagesthrough the network.

Subsystem AllowedSSA

Service Specific ConnectionOriented Protocol.

SSCOP

The primary task of the SSCOP(Service Specific ConnectionOriented Protocol) is to provideassured data delivery betweenAAL connection endpoints.Breaking the SSCS into 2 sublayersallows a common connectionoriented protocol with errorrecovery (the SSCOP) to provide ageneric reliable data transferservice for different AAL interfacesdefined by different SSCF layers.

SS7 Subsystem NumberSSN

The subsystem number of a givenpoint code. The subsystem numberidentifies the SCP application thatshould receive the message, or thesubsystem number of thedestination point code to be



S

assigned to the LNP subsystem ofthe EAGLE.

Subsystem Number

A value of the routing indicatorportion of the global titletranslation data commandsindicating that no further globaltitle translation is required for thespecified entry.

Subsystem Number

Used to update the CdPA.

Subsystem Prohibited networkmanagement message

SSP

Subsystem Prohibited SCCP(SCMG) management message.(CER)Service Switching Point (SS7Network)Signal Switching PointSignal Switching Points areswitches that originate, terminate,or tandem calls. An SSP sendssignaling messages to other SSPsto setup, manage, and release voicecircuits required to complete a call.

Secondary StateSST

The secondary state of the specifiedentity.

Subsystem Status Test

Subsystem Status Test networkmanagement message.

Subsystem Status Test SCCP(SCMG) management message.(CER)

Signal Transfer PointSTP



S

The STP is a special high-speedswitch for signaling messages inSS7 networks. The STP routes coreINAP communication between theService Switching Point (SSP) andthe Service Control Point (SCP)over the network.

Spanning Tree Protocol

Signaling Transfer Point Local AreaNetwork

STPLAN

The application used by the SLANcard and E5-SLAN card to supportthe STP LAN feature. Thisapplication does not support 24-bitITU-N point codes.

Signal Unit Error Rate MonitorSUERM

T

Transmission Level 1T1

A T1 interface terminates ordistributes T1 facility signals forthe purpose of processing the SS7signaling links carried by the E1carrier.

A leased-line connection capableof carrying data at 1,544,000bits-per-second.

Transfer Cluster AllowedTCA

Transaction CapabilitiesApplication Part

TCAP

A protocol in the SS7 protocol suitethat enables the deployment ofadvanced intelligent networkservices by supporting non-circuitrelated information exchangebetween signaling points using the



T

Signaling Connection Control Partconnectionless service. TCAP alsosupports remote control - ability toinvoke features in another remotenetwork switch.

Transfer-Cluster-ProhibitedTCP

Transfer Control Protocol

Transmission Control Protocol

A connection-oriented protocolused by applications on networkedhosts to connect to one another andto exchange streams of data in areliable and in-order manner.

Transmission ControlProtocol/Internet Protocol

TCP/IP

Transfer Cluster RestrictedTCR

TransFer Allowed (Msg)TFA

Transfer ControlTFC

TransFer Controlled (Msg)Transfer Congested

TransFer Prohibited (Msg)TFP

A procedure included in thesignaling route management(functionality) used to inform asignaling point of the unavailabilityof a signaling route.

Transfer RestrictedTFR

Traffic Restarting AllowedTRA



T

See TT.Translation Type

Traffic Restarting WaitingTRW

Translation TypeTT

Resides in the Called Party Address(CdPA) field of the MSU anddetermines which service databaseis to receive query messages. Thetranslation type indicates whichGlobal Title Translation tabledetermines the routing to aparticular service database.

U

ETF User Adaptation LayersUA

User Agent

User InterfaceUI

V

Voicemail Flexible RoutingV-Flex

An advanced database applicationbased on the industry provenEAGLE. Deployed as a localsubsystem on the EAGLE platform,V-Flex centralizes voicemailrouting.

W

Wireless Short Message ServiceCenter

WSMSC



Documents

Oracle Communications EAGLE · Oracle® Communications EAGLE Measurements Reference Release 46.3 E72179 Revision 1 June 2016