Transport HW Counters d

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 02, Documentation Change Delivery 3

RNC Counters - Transport and HW Part

DN04143903

Issue 08CApproval Date 2013-08-05

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN04143903


Id:0900d80580a02820Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN04143903 3



Table of contentsThis document has 615 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1 Introduction to RNC transport and HW part counters . . . . . . . . . . . . . . . 91.1 Optional counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Measurement support in different controller types. . . . . . . . . . . . . . . . . 131.3 Field descriptions of counter boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1 Computer unit code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.2 Signalling network code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 RNC Resource Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1 RNC capacity usage measurement (802/322H) . . . . . . . . . . . . . . . . . . 21

4 Transport network resource measurements . . . . . . . . . . . . . . . . . . . . . 344.1 AAL2 resource reservation measurement (800/320H) . . . . . . . . . . . . . 344.1.1 Introduction to AAL2 resource reservation measurement . . . . . . . . . . . 344.1.2 AAL2 resource reservation measurement counters. . . . . . . . . . . . . . . . 374.2 AAL2 path CAC resource measurement (550/226H). . . . . . . . . . . . . . . 474.2.1 Introduction to AAL2 path CAC resource measurement . . . . . . . . . . . . 474.2.2 AAL2 path CAC resource measurement counters. . . . . . . . . . . . . . . . . 534.3 RNC IP CAC measurement (804/324H) . . . . . . . . . . . . . . . . . . . . . . . . 63

5 Signalling measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685.1 AAL2 signalling protocol at UNI measurement (548/224H) . . . . . . . . . . 685.1.1 Introduction to AAL2 signalling at UNI protocol measurement . . . . . . . 685.1.2 AAL2 signalling at UNI protocol measurement counters . . . . . . . . . . . . 705.2 AAL2 signalling at NNI measurement (552/228H) . . . . . . . . . . . . . . . . . 855.2.1 Introduction to AAL2 signalling at NNI measurement . . . . . . . . . . . . . . 855.2.2 AAL2 signalling at NNI measurement counters . . . . . . . . . . . . . . . . . . . 875.3 SAAL signalling protocol at UNI measurement (546/222H). . . . . . . . . 102

6 SS7 signalling measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1276.1 Functional parts of SS7 signalling measurements and reporting. . . . . 1276.2 Logical files of SS7 signalling measurements . . . . . . . . . . . . . . . . . . . 1296.3 Reading instructions for tables containing MTP and SCCP measurement

descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306.4 MTP (message transfer part) measurements in RNC . . . . . . . . . . . . . 1316.4.1 MTP fault and configuration management measurements . . . . . . . . . 1356.4.2 MTP performance in RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376.4.3 MTP signalling link availability report (208/D0H) . . . . . . . . . . . . . . . . . 1386.4.4 MTP signalling link performance report (209/D1H) . . . . . . . . . . . . . . . 1456.4.5 MTP signalling link utilization report (210/D2H) . . . . . . . . . . . . . . . . . . 1516.4.6 MTP signalling point status report (211/D3H) . . . . . . . . . . . . . . . . . . . 1626.4.7 MTP signalling set and route set availability report (212/D4H) . . . . . . 1666.4.8 MTP signalling traffic report of signalling points (213/D5H) . . . . . . . . . 1706.4.9 MTP signalling traffic report of user parts (214/D6H). . . . . . . . . . . . . . 177

4 DN04143903



6.4.10 MTP matrix signalling traffic report (215/D7H) . . . . . . . . . . . . . . . . . . . 1786.5 SCCP (signalling connection control part) measurements . . . . . . . . . . 1796.5.1 SCCP fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836.5.2 SCCP performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846.5.3 SCCP quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856.5.4 SCCP signalling point report (216/D8H) . . . . . . . . . . . . . . . . . . . . . . . . 1866.5.5 SCCP subsystem report (217/D9H) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2376.5.6 SCCP local subsystem availability report (218/DAH) . . . . . . . . . . . . . . 2476.5.7 SCCP single meters' report (219/DBH). . . . . . . . . . . . . . . . . . . . . . . . . 2496.6 1st+ interval log reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566.6.1 Signalling link log report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2566.6.2 MTP signalling point log report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2576.6.3 SCCP signalling point log report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2586.6.4 SCCP reassembly and segmentation errors log report . . . . . . . . . . . . 260

7 ATM transport measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637.1 ATM layer performance measurement (528/210H) . . . . . . . . . . . . . . . 2647.2 ATM virtual path connection measurement (529/211H) . . . . . . . . . . . . 2747.3 ATM virtual channel connection measurement (530/212H) . . . . . . . . . 2787.4 ATM VCC Bundle (533/215H). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2907.5 ATM route load measurement (531/213H) . . . . . . . . . . . . . . . . . . . . . . 2937.6 ATM interface measurement (532/214H) . . . . . . . . . . . . . . . . . . . . . . . 3017.7 AAL2 scheduling performance in RNC measurement (553/229H) . . . . 3147.7.1 Introduction to AAL2 scheduling performance in RNC measurement . 3147.7.2 AAL2 scheduling performance in RNC counters . . . . . . . . . . . . . . . . . 3157.8 AAL5 protocol measurement in Chorus (549/225H) . . . . . . . . . . . . . . . 3317.9 AAL5 protocol measurement in DMX (547/223H). . . . . . . . . . . . . . . . . 3367.10 PDH interface measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3397.10.1 PDH interface statistics permanent measurement (145/91H). . . . . . . . 3397.10.2 PDH interface statistics temporary measurement. . . . . . . . . . . . . . . . . 3647.10.3 PDH interface disturbance measurement report. . . . . . . . . . . . . . . . . . 3647.10.4 PCM statistics permanent measurement . . . . . . . . . . . . . . . . . . . . . . . 3657.11 IMA logical interface measurement (514/202H) . . . . . . . . . . . . . . . . . . 3667.12 STM-1 interface measurement (513/201H) . . . . . . . . . . . . . . . . . . . . . 3767.13 SONET/SDH protection group measurement (516/204H) . . . . . . . . . . 398

8 IP transport measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4008.1 TCP/IP protocol measurement (563/233H). . . . . . . . . . . . . . . . . . . . . . 4008.2 Iu-PS performance measurement (801/321H) . . . . . . . . . . . . . . . . . . . 5118.2.1 Introduction to Iu-PS performance measurement . . . . . . . . . . . . . . . . . 5118.2.2 Iu-PS performance measurement counters . . . . . . . . . . . . . . . . . . . . . 5118.3 IP Based Route measurement (568/238H). . . . . . . . . . . . . . . . . . . . . . 5208.4 IP measurement on IP interface (565/235H) . . . . . . . . . . . . . . . . . . . . 5318.5 UDP measurement on IP interface (566/236H) . . . . . . . . . . . . . . . . . . 5428.6 IP QoS measurement (567/237H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5448.7 M3UA association set measurement (661/295H) . . . . . . . . . . . . . . . . . 5478.8 RNC RTP/RTCP measurement (803/323H) . . . . . . . . . . . . . . . . . . . . . 5558.9 Ethernet interface performance measurement (564/234H) . . . . . . . . . 567

DN04143903 5



8.10 IP TWAMP Statistics (569/239H). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

9 Computing unit measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5839.1 Availability performance measurement (608/260H). . . . . . . . . . . . . . . 5839.2 Unit load measurement (592/250H). . . . . . . . . . . . . . . . . . . . . . . . . . . 5859.3 WAC overload control measurement (594/252H) . . . . . . . . . . . . . . . . 587

10 DSP resource measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58910.1 DSP service statistics measurement (609/261H) . . . . . . . . . . . . . . . . 58910.2 DSP state changes measurement (612/264H) . . . . . . . . . . . . . . . . . . 59210.3 DSP resource utilization measurement (615/267H). . . . . . . . . . . . . . . 59310.4 DSP load measurement (617/269H) . . . . . . . . . . . . . . . . . . . . . . . . . . 598

11 Multicontroller RNC measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . 60711.1 Measurement: Logical Resource Usage (M610) . . . . . . . . . . . . . . . . . 60711.2 Measurement: CPU Usage Core Level (M2002) . . . . . . . . . . . . . . . . . 60811.3 Measurement: Networking Logical (M2004) . . . . . . . . . . . . . . . . . . . . 61011.4 Measurement: CPU Usage Node Level (M2007) . . . . . . . . . . . . . . . . 614

6 DN04143903



List of figuresFigure 1 Transport resource reservation over Iub for mobile originated call . . . . . 35Figure 2 Transport resource reservation over Iur in case new SHO branch is estab-

lished. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 3 Example of AAL2 path capacity allocations and related counters . . . . . 48Figure 4 Example of AAL2 path capacity allocations and related counters for VCC

bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 5 AAL2 signalling between RNC and BTS. . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 6 AAL2 signalling between RNC and AXC (AAL2 multiplexing enabled in AX-

UB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Figure 7 AAL2 signalling between two RNCs over Iur interface . . . . . . . . . . . . . . 86Figure 8 SS7 signalling statistics system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Figure 9 RAN ATM connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Figure 10 An example of ATM VC connections between RNC and BTS that can be

selected for the ATM virtual channel connection measurement . . . . . . 279Figure 11 ATM layer counters inside an ATM interface . . . . . . . . . . . . . . . . . . . . 301Figure 12 RNC ATM and AAL2 scheduling as a conceptual representation . . . . 315Figure 13 Relation between defect types and counters . . . . . . . . . . . . . . . . . . . . 377Figure 14 Iu-PS interface termination in the RNC. . . . . . . . . . . . . . . . . . . . . . . . . 511

DN04143903 7



List of tablesTable 1 Measurement support in different controller types . . . . . . . . . . . . . . . . 13Table 2 Computer unit code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 3 Signalling network code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Table 4 Support for M802 counters in different RNC HW configurations . . . . . 21Table 5 Updating of AAL2 CAC counters for different connection types that are not

part of VCC bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Table 6 Updating of AAL2 CAC counters for different connection types that are part

of VCC bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Table 7 The logical files of SS7 measurement reports . . . . . . . . . . . . . . . . . . 129Table 8 The logical files of SS7 interval log reports . . . . . . . . . . . . . . . . . . . . . 130Table 9 Q.2144 MTP Signalling Link Faults and Performance, ATM links (The mea-

surements with a 30-minute counter can also be reported with MTP Signal-ling Link Performance report.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Table 10 MTP Signalling Link Availability (The measurements with a 30-minute counter can also be reported with MTP Signalling Link Performance report.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Table 11 MTP Signalling Link Utilisation (The measurements with a 30-minute coun-ter can also be reported with MTP Signalling Link Performance report.) . 133

Table 12 MTP Signalling Link Set and Route Set Availability (The measurements with a 30-minute counter can also be reported with MTP Signalling link set and Route set report.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Table 13 MTP Signalling Point Status (The measurements with a 30-minute counter can also be reported with MTP Signalling Point Status report.) . . . . . 134

Table 14 MTP Signalling Traffic Distribution (Signalling Route Utilisation) (The mea-surements with a 30-minute counter can also be reported with MTP Signal-ling Traffic reports.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Table 15 SCCP Error Performance (SP Signalling Point) (The measurements with a 30-minute counter can also be reported with SCCP Signalling Point mea-surement report.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Table 16 SCCP Subsystem Availability (The measurements with a 30-minute coun-ter can also be reported with SCCP Subsystem measurement report and with SCCP Local Subsystem availability report.) . . . . . . . . . . . . . . . . 181

Table 17 SCCP – Utilisation (The measurements with a 30-minute counter can also be reported with SCCP Subsystem measurement report and with SCCP Single measurement report.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Table 18 SCCP – Quality of Service (The measurements with a 30-minute counter can also be reported with SCCP Signalling Point measurement report.) . 182

Table 19 Measurements used for ATM connections . . . . . . . . . . . . . . . . . . . . . 263Table 20 Counters for IMA links 2–8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374Table 21 Additional object levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579Table 22 DSP service names used in M609 measurement . . . . . . . . . . . . . . . . 589Table 23 DSP service pool names used in M615 measurement . . . . . . . . . . . . 593Table 24 Available FPNODE objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608

8 DN04143903



Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes made between issues 08B (2013-06-10, RU40) and 08C (2013-08-05, RU40)

Updated countersIP Based Route measurement (568/238H)

• M568C7 • M568C8

Changes made between issues 08A (2013-02-21, RU40) and 08B (2013-06-10, RU40)

Updated countersIP measurement on IP interface (565/235H)

• M565C7 • M565C8

Changes made between issues 08 (2012-10-08, RU40) and 08A (2013-02-21, RU40)New content on M802 counters in RAN2117 mcRNC co-siting has been added in chapter 3.1 RNC capacity usage measurement (802/322H).

DN04143903 9

RNC Counters - Transport and HW Part Introduction to RNC transport and HW part counters

Id:0900d8058092e3c1Confidential

1 Introduction to RNC transport and HW part countersThis document describes the RNC transport layer and HW related measurements. These measurements give information about the performance of the network element, network availability and possible problems in the network. The measurements in this document are divided into eight groups: RNC resources, Transport network resources, Signalling, ATM transport, IP transport, Transmission quality, Computing unit, and DSP resource measurements. This document includes descriptions for every counter avail-able in these measurements. For more information on the radio layer specific statistics see RNC Counters - RNW part

The IPA-RNC measurements can be managed with T2 MML command group or using RNW Measurement Management GUI in OMS Element Manager. For more information, see document Managing and Viewing RNC Measurements. The SS7 and PDH mea-surements are managed with other MML command groups. For more information, see MML documents.

The Multicontroller RNC Transport&HW measurements are managed with sCLI com-mands. It is not possible to manage them with the OMS Element Manager.

Statistic reports are directed automatically via a logical file to OMS where the data is stored to the database. You can browse the contents of the database with the RNW Measurement Presentation application.

1.1 Optional countersSome of the counters produced by the RNC are optional and if the related feature is dis-abled, the counters will not be sent to NetAct and their value will always be zero in the RNC Element Manager. If all the counters in the measurement are optional and the related features are disabled, it is not even possible to start the measurement.

The following tables list the optional counters in each measurement type.

Measurement 529

Measurement 530

PI ID Name Feature Optionality control

M529C0 IN_TOT_CELLS_VP RAN224 FIFILE

M529C1 EG_TOT_CELLS_VP RAN224 FIFILE

M529C2 IN_REC_CELLS_VP RAN224 FIFILE

M529C3 IN_QUEUED_CELLS_VP RAN224 FIFILE

M529C4 IN_CAP_VP RAN224 FIFILE

M529C5 EG_REC_CELLS_VP RAN224 FIFILE

M529C6 EG_QUEUED_CELLS_VP RAN224 FIFILE

M529C7 EG_CAP_VP RAN224 FIFILE

10 DN04143903



Introduction to RNC transport and HW part counters

Measurement 533

Measurement 550


M530C0 IN_TOT_CELLS_VC RAN224 FIFILE

M530C1 EG_TOT_CELLS_VC RAN224 FIFILE

M530C2 IN_REC_CELLS_VC RAN224 FIFILE

M530C3 IN_QUEUED_CELLS_VC RAN224 FIFILE

M530C4 IN_CAP_VC RAN224 FIFILE

M530C5 EG_REC_CELLS_VC RAN224 FIFILE

M530C6 EG_QUEUED_CELLS_VC RAN224 FIFILE

M530C7 EG_CAP_VC RAN224 FIFILE

M530C8 VC_EG_BW_UTI_CLASS_1 RAN2105 license





M530C13 VC_IN_BW_UTI_CLASS_1 RAN2105 license





M530C18 VC_EG_BW_CONFIG RAN2105 license

M530C19 VC_IN_BW_CONFIG RAN2105 license

M530C20 VC_EG_PEAK_THRPUT RAN2105 license

M530C21 VC_IN_PEAK_THRPUT RAN2105 license


M533C0 BUN_EG_BW_UTI_CLASS_1 RAN2105 license





M533C5 BUN_EG_BW_CONFIG RAN2105 license

M533C6 BUN_EG_PEAK_THRPUT RAN2105 license

DN04143903 11



Measurement 568


M550C0 AAL2_PATH_GUAR_CELL_RATE RAN773 FIFILE

M550C1 SUM_RESERVED_CELL_RATE RAN773 FIFILE

M550C2 MIN_RESERVED_CELL_RATE RAN773 FIFILE

M550C3 MAX_RESERVED_CELL_RATE RAN773 FIFILE

M550C4 SUM_AAL2_CONNECTIONS RAN773 FIFILE

M550C5 MIN_AAL2_CONNECTIONS RAN773 FIFILE

M550C6 MAX_AAL2_CONNECTIONS RAN773 FIFILE

M550C7 NBR_SAMPLES RAN773 FIFILE

M550C8 AAL2_RM_SUCCEEDED RAN773 FIFILE

M550C9 AAL2_CAC_REJECTED RAN773 FIFILE

M550C10 AAL2_HW_REJECTED RAN773 FIFILE

M550C11 SUM_AAL2_CONNECTIONS_HSDPA

RAN773 FIFILE

M550C12 MIN_AAL2_CONNECTION_HSDPA

RAN773 FIFILE

M550C13 MAX_AAL2_CONNECTIONS_HSDPA

RAN773 FIFILE

M550C14 AAL2_CAC_REJECTED_HSDPA RAN773 FIFILE

M550C15 AAL2_HW_REJECTED_HSDPA RAN773 FIFILE

M550C16 SHARED_HSDPA_AAL2_ALLOCATION

RAN773 FIFILE

M550C17 AAL2_RM_SUCCEEDED_HSDPA RAN773 FIFILE

M550C18 MIN_SHARED_HSDPA_AAL2_ALLOC

RAN773 FIFILE

M550C19 MAX_SHARED_HSDPA_AAL2_ALLOC

RAN773 FIFILE


M568C10 IP_EG_BW_UTI_CLASS_1 RAN2106 license





M568C15 IP_EG_BW_CONFIG RAN2106 license

M568C16 IP_EG_PEAK_THRPUT RAN2106 license

12 DN04143903




Measurement 594

Measurement 800

Measurement 801

M568C17 IP_IN_PEAK_THRPUT RAN2106 license


M594C0 WAC_GATE_REQ_TOTAL RAN773 FIFILE

M594C1 WAC_GATE_REQ_TOTAL_REJ RAN773 FIFILE


M800C0 RES_SUCCEEDED RAN773 FIFILE

M800C1 RES_EXT_CAP RAN773 FIFILE

M800C2 RES_INT_CAP RAN773 FIFILE

M800C3 RES_OTHER RAN773 FIFILE

M800C4 AAL2_SUCCEEDED RAN773 FIFILE

M800C5 AAL2_REJECTED RAN773 FIFILE

M800C6 AAL2_SUCCEEDED_HSDPA RAN773 FIFILE

M800C7 TRANSPORT_REJECTED_EXT_HSDPA

RAN773 FIFILE

M800C8 TRANSPORT_REJECTED_INT_HSDPA

RAN773 FIFILE

M800C9 OTHER_REJECTED_HSDPA RAN773 FIFILE

M800C10 ACTIVE_HSDPA_RES_TIME RAN773 FIFILE

M800C11 WAITING_HSDPA_RES_TIME RAN773 FIFILE

M800C12 RELEASE_TIMER_LENGTH RAN773 FIFILE

M800C13 RESERV_REL_DUE_TO_TIMER RAN773 FIFILE

M800C14 RESERV_REL_TIMER_STARTED RAN773 FIFILE

M800C15 RESERV_REL_TIMER_STOPPED RAN773 FIFILE

M800C16 RESERV_REL_DUE_TO_OTHER RAN773 FIFILE

M800C17 ACTIVE_TIME_CUMULATIVE RAN773 FIFILE

M800C18 WAITING_TIME_CUMULATIVE RAN773 FIFILE

M800C19 REJECT_HSDPA_TOO_MANY_USERS

RAN773 FIFILE


DN04143903 13



1.2 Measurement support in different controller typesThis document is common for IPA-RNC and mcRNC. Some measurement types are common for both RNC types and some are specific only for mcRNC or IPA-RNC. For details, see Table 1 Measurement support in different controller types.

PI ID Name Abbreviation Optionality control

M801C0 INPUT_BYTES_TOTAL_UDP RAN1163 FIFILE

M801C1 INPUT_IP_PACKETS_TOTAL RAN1163 FIFILE

M801C2 INPUT_TRAF_BYTES_TC_CONV RAN1163 FIFILE

M801C3 INPUT_TRAF_BYTES_TC_STREAM

RAN1163 FIFILE

M801C4 INPUT_TRAF_BYTES_TC_INTERAC

RAN1163 FIFILE

M801C5 INPUT_TRAF_BYTES_TC_BACKGR

RAN1163 FIFILE

M801C6 OUTPUT_BYTES_TOTAL_UDP RAN1163 FIFILE

M801C7 OUTPUT_IP_PACKETS_TOTAL RAN1163 FIFILE

M801C8 OUTPUT_TRAF_BYTES_TC_CONV

RAN1163 FIFILE

M801C9 OUTPUT_TRAF_BYTES_TC_STREAM

RAN1163 FIFILE

M801C10 OUTPUT_TRAF_BYTES_TC_INTERAC

RAN1163 FIFILE

M801C11 OUTPUT_TRAF_BYTES_TC_BACKGR

RAN1163 FIFILE

M801C12 ECHO_REQUEST_RECEIVED RAN1163 FIFILE

M801C13 ECHO_RESPONSE_RECEIVED RAN1163 FIFILE

M801C14 ECHO_RESPONSE_SENT RAN1163 FIFILE

M801C15 ERROR_INDICATIONS_RECEIVED

RAN1163 FIFILE

M801C16 ERROR_INDICATIONS_SENT RAN1163 FIFILE

M801C17 EXTENS_HEAD_NOTIF_RECEIVED

RAN1163 FIFILE

M801C18 AVERAGE_NBR_OF_GTP_TUNNELS

RAN1163 FIFILE

M801C19 MAX_NBR_OF_GTP_TUNNELS RAN1163 FIFILE

Measure-ment ID

Measurement name IPA-RNC mcRNC

145 PDH Statistics X -

Table 1 Measurement support in different controller types

14 DN04143903




208 MTP Signalling link availability X -

209 MTP signalling link performance X -

210 MTP signalling link utilization X -

211 MTP signalling point status X -

212 MTP Signalling link set and route set availabil-ity

X -

213 MTP Signalling traffic report of signalling points X -

214 MTP Signalling traffic report of user parts X -

215 MTP matrix signalling traffic X -

216 SCCP signalling point X -

217 SCCP subsystem X -

218 SCCP local subsystem availability X -

219 SCCP single meters X -

513 STM-1 Interface X -

514 IMA Logical Interface X -

516 SONET/SDH Protection Group meas X -

528 ATM layer performance X -

529 ATM Virtual Path Connection X -

530 ATM Virtual Channel Connection X -

531 ATM Route Load X -

532 ATM Interface X -

533 ATM VCC Bundle X -

546 SAAL signalling protocol at UNI X -

547 AAL5 Protocol Measurement in DMX X -

548 AAL2 signalling protocol at UNI X -

549 AAL5 Protocol Meas. in CHORUS X -

550 AAL2 path CAC resource X -

552 AAL2 signalling at NNI X -

553 AAL2 Scheduling Performance in RNC X -

563 TCP/IP Protocol X -

564 Ethernet Interface Performance X -

565 IP measurement on IP interface X -

566 UDP measurement on IP interface X -

567 IP QoS measurement X -

Measure-ment ID


Table 1 Measurement support in different controller types (Cont.)

DN04143903 15



1.3 Field descriptions of counter boxesThe table describes fields used in the counter boxes.

568 IP Based Route measurement X X

569 IP TWAMP Statistics X X

592 Unit Load X -

594 WAC overload control X -

608 Availability Performance X -

609 DSP service statistics X X

610 L2 Resource Utilization - X

612 DSP state changes X -

615 DSP Resource Utilization X -

617 DSP load X -

661 M3UA Association Set X -

800 AAL2 Resource Reservation X -

801 Iu-PS Performance X -

802 RNC capacity usage X X

803 RNC RTP/RTCP X X

804 RNC IP CAC X X

2002 CPU Usage - X

2004 Networking Logical - X

2007 Node Level CPU load - X

Measure-ment ID


Table 1 Measurement support in different controller types (Cont.)

Field name Description Example

Counter ID Counter identification Format: MxxxxCyyyy, where xxxx = measurement number, and yyyy = number which defines the counter within the measurement.

M1002C65

Network element name Counter name - long version. Used in the OMS Element Manager.

RT DCH ALLO FOR TRANS CS DATA CONV CLASS 64 KBPS IN SRNC

16 DN04143903




Version A database-internal version number of the counter. The version number may be dif-ferent in Operating Docu-mentation (NED) and in the Reference Information Service in Product Informa-tion Center (Nokia Siemens Networks Customer Extra-net) due to differences in the publishing of the database information. A change in the version number in itself does not indicate change in content. All content changes are explained in Operating Documentation (NED); for more information on content changes, see Counter changes or the Summary of changes page in the PDF version of the measurement document. Alternatively, use the Compare function in the Reference Information Service to export a list of counter changes in Excel format.

5.2

NetAct name Counter name - short version. Used as database view column name in NetAct. The maximum length of NetAct name is 31 characters.

ALLO_TRAN_CS_CONV_64_IN_SRNC

Description Describes what information this counter provides.

A number of RT DCH alloca-tions for a transparent CS Data Call with conversa-tional class 64 kbps in the SRNC. Transparent CS Calls are symmetric, i.e. there is no need for separate UL and DL counters.

Updated Describes when this counter is updated; that is, what is the triggering point.

When the DCH is accepted.

Logical type This field can be used for example to tell whether this counter provides minimum, maximum, average, sum, or cumulative values. "sum" and "cumulative" are inter-changeable terms, they both count the amount of some events or duration.

Sum


DN04143903 17



Trigger type This field provides informa-tion on whether the trigger-ing of the counter update is event based or periodical (sample based). The 3rd possibility is duration, in which case the triggering can be considered as a combination of start and stop events.

Event

Sampling interval If the trigger type is periodi-cal, this field provides the used sampling interval.

-

Unit The unit of the counter. The physical quantity is equal to the numerical value times the unit.

Integer number

Range This field can be used if the counter has minimum and maximum values which are not self-evident.

-

Example values This field can be used to further clarify what kind of values the counter may have. In most cases, this field is not needed.

-

Dependencies with other counters

Provides information on counters which are updated together with this counter.

M1002C69: RT DCH ALLO DUR FOR TRANS CS DATA CONV CLASS 64 KBPS IN SRNC

Operability class The operability class is used to map counters to basic network operability aspects. Example values: Mobility, Traffic, Resources, Admis-sion, Quality, and Security.

-

Related to feature Defines the feature which is the main reason for intro-ducing this counter.

RAN 1.029: Packet Sched-uler Algoritms

Related to standard The related standard, and its version number.

-

3GPP Measurement name (Clause header)

More detailed information on the related standard. Cust-omised for 3GPP purposes.

-

3GPP Measurement type More detailed information on the related standard. Cust-omised for 3GPP purposes.

-


18 DN04143903




Exceptions to related standard

In a fully compliant case, this field can be used, for example, to describe how the standard defined counter can be derived from Nokia Siemens Networks counters, or what additional information the counters provide. In a partially compli-ant case, this field can be used to describe the differ-ence between the standard defined and Nokia Siemens Networks counters. In that case, the 3GPP Measure-ment Type begins with 'VS'.

-

Used from release The first product release in which the counter was avail-able.

RN1.5.1

Definition updated in release The product release when the counter information has last been modified. This may happen, for example, due to a change in the measured functionality or due to a description clarification.

-


DN04143903 19

RNC Counters - Transport and HW Part Terminology


2 Terminology

2.1 Computer unit code valuesThe computer units can be referred by using the following numeric code values.

2.2 Signalling network code valuesThe signalling networks can be referred by using the following code values.

Unit type Unit name Unit type code in report

OMU Operation and mainte-nance unit

2

MXU Multiplexer Unit 268

NIS1P Protected Network Inter-face Unit STM-1

271

NPGE Network Processor Inter-face Unit Gigabit Ethernet

284

NPGEP Network Processor Inter-face Unit Gigabit Ethernet Protected

285

NPS1 Network Processor Inter-face Unit STM-1

286

NPS1P Network Processor Inter-face Unit STM-1 Protected

287

NIU Network Interface Unit 301

A2SP AAL2 Switching Processor 324

NIP1 Network Interface Unit PDH 325

NIS1 Network Interface Unit STM-1

326

RSMU Resource and Switch Man-agement Unit

327

ICSU Interface Control and Sig-nalling Unit

329

GTPU GPRS Tunneling Protocol Unit

330

DMPG Data and Macro Diversity Processor Group

331

SFU Switching Fabric Unit 337

A2SU AAL2 Switching Unit 1484

SET SDH Exchange Terminal 1485

PET PDH Exchange Terminal 1486

DMCU Data and Macro Diversity Combining Unit

1488

Table 2 Computer unit code values

20 DN04143903



Terminology

Signalling network codes Signalling network name Network code value in report

IN0 International network 0 0

IN1 International network 1 4

NA0 National network 0 8

NA1 National network 1 12

Table 3 Signalling network code values

DN04143903 21

RNC Counters - Transport and HW Part RNC Resource Measurements

Id:0900d80580a2147bConfidential

3 RNC Resource Measurements

3.1 RNC capacity usage measurement (802/322H)The RNC capacity usage measurement provides information on the amount of simulta-neous AMR calls, Iu-PS throughput and the number of users in different RRC connected mode states. The object of the measurement is the RNC itself.

When capacity licensing is used, the Iu-PS throughput and AMR amount distribution counters can be used to evaluate how close to the licensed limit the RNC is running, and thus predict the need for capacity upgrade.

The updating of some counters of this measurement is based on a sampling method. The sampling timer is approximately 1 second, but it must be noted that the timer is not absolutely accurate and thus the sample amount during one hour measurement interval does not match exactly 3600 seconds but slightly less, for example 3560.

Some counters in this measurement are supported only in certain RNC HW configura-tions. The support of counters is presented in table Support for M802 counters in differ-ent RNC HW configurations.

PI ID Name RNC196&450 without IP-

upgrade

RNC196&450 with IP-upgrade

(NPS1/NPGE)

RNC2600 mcRNC

M802C0 AMR_AVERAGE X X X

M802C1 AMR_MAX X X X

M802C2 AMR_DISTR_CLASS_0 X





M802C7 AMR_LIC_CAPACITY X

M802C8 IU_PS_THR_AVERAGE X X

M802C9 IU_PS_THR_PEAK X X

M802C10 IUB_PS_THR_DISTR_CLASS_0 (X)* X





M802C15 IUB_PS_THR_LIC_CAPACITY (X)* X

M802C16 IU_PS_THR_LIMIT_DURATION (X)* X

M802C17AVE_RRC_CONN_MODE_USERS X X X

Table 4 Support for M802 counters in different RNC HW configurations

22 DN04143903



RNC Resource Measurements

*) Updated only if the Iu-PS capacity license is installed, which is not mandatory except in RNC2600.

M802C18MAX_RRC_CONN_MODE_USERS X X X

M802C19 AVE_USERS_CELL_DCH X X X

M802C20 AVE_USERS_CELL_FACH X X X

M802C21 AVE_USERS_CELL_PCH X X X

M802C22 AVE_USERS_URA_PCH X X X

M802C23 AMR_OVER_HSPA_AVERAGE X X X

M802C24 AMR_OVER_HSPA_MAX X X X

M802C25 AVE_RRC_CONN_MODE_LFD_UE X X X

PI ID Name RNC196&450 without IP-

upgrade

RNC196&450 with IP-upgrade

(NPS1/NPGE)

RNC2600 mcRNC

Table 4 Support for M802 counters in different RNC HW configurations (Cont.)

Counter ID: M802C0 Network element name: AMR_AVERAGE

Version: 4.1 NetAct name: AMR_AVERAGE

Description: The average number of simultaneous AMR calls.

Updated: Sampled periodically with one second interval.

Logical type: Average Trigger type: Sample Sampling interval: 1 s

Unit: Integer number Range: Example values:

Dependencies on other counters:

Operability class:

Related to feature:

RAN1198: SW License Key Controlled RNC Capacity

Related to standard:

3GPP Measurement name (Clause header):

3GPP Measurement type:

Exceptions to related standard:

Used from release: RN4.0 Definition updated in release:

Counter ID: M802C1 Network element name: AMR_MAX

Version: 4.1 NetAct name: AMR_MAX

Description: The maximum number of simultaneous AMR calls. The maximum number of AMR calls is the maximum value among the samples during a measurement period.

Updated: Sampled periodically with one second interval.

DN04143903 23



Logical type: Max Trigger type: Sample Sampling interval: 1 s



Operability class:

Related to feature:

RAN1198: SW License Key Controlled RNC Capacity






Counter ID: M802C2 Network element name: AMR_DISTR_CLASS_0

Version: 1.0 NetAct name: AMR_DISTR_CLASS_0

Description: The distribution of time when the number of simultaneous AMR calls was within 0%-50% of the licensed capacity.

Updated: Sampled periodically with 1 second interval.

Logical type: Cumulative Trigger type: Sample Sampling interval: 1 s


Dependencies with other counters:

Operability class:

Related to feature:

RAN 1198: SW License Key Controlled RNC Capacity













Operability class:

Related to feature:



24 DN04143903















Operability class:

Related to feature:














Operability class:

Related to feature:








DN04143903 25




Description: The distribution of time when the number of simultaneous AMR calls was more than 90% of the licensed capacity.





Operability class:

Related to feature:







Counter ID: M802C7 Network element name: AMR_LIC_CAPACITY

Version: 1.0 NetAct name: AMR_LIC_CAPACITY

Description: Licensed AMR capacity.The counter value is zero in any configuration other than RNC2600 HW.

Updated: This counter is updated at the end of the measurement period.

Logical type: Current Trigger type: Event Sampling interval: 1 s



Operability class:

Related to feature:







Counter ID: M802C8 Network element name: IU_PS_THR_AVERAGE

Version: 1.1 NetAct name: IU_PS_THR_AVERAGE

Description: The average Iu-PS throughput in downlink direction from the core network to the RNC. Includes only user data, not GTP header.This counter is supported only when the NP8S1 or NP2GE interface unit is used in the Iu-PS interface.



Unit: kbit/s Range: Example values:

26 DN04143903





Operability class:

Related to feature:







Counter ID: M802C9 Network element name: IU_PS_THR_PEAK

Version: 1.2 NetAct name: IU_PS_THR_PEAK

Description: The maximum Iu-PS throughput in downlink direction from the core network to the RNC. Includes only user data, not GTP header.This counter is supported only when the NP8S1 or NP2GE interface unit is used in the Iu-PS interface.





Operability class:

Related to feature:







Counter ID: M802C10 Network element name: IUB_PS_THR_DISTR_CLASS_0

Version: 1.0 NetAct name: IUB_PS_THR_DISTR_CLASS_0

Description: The distribution of time when the Iub PS data throughput was within 0%-50% of the licensed capacity.





Operability class:

Related to feature:





DN04143903 27












Operability class:

Related to feature:














Operability class:

Related to feature:










28 DN04143903








Operability class:

Related to feature:









Description: The distribution of time when the Iub PS data throughput was more than 90% of the licensed capacity.





Operability class:

Related to feature:







Counter ID: M802C15 Network element name: IUB_PS_THR_LIC_CAPACITY

Version: 1.0 NetAct name: IUB_PS_THR_LIC_CAPACITY

Description: Licensed Iub PS data throughput capacity.The counter value is zero when the capacity licensing is not in use.


Logical type: Current Trigger type: Event Sampling interval: 1 s



Operability class:

Related to feature:



DN04143903 29







Counter ID: M802C16 Network element name: IU_PS_THR_LIMIT_DURATION

Version: 1.0 NetAct name: IU_PS_THR_LIMIT_DURATION

Description: The duration of time when the RNC Iu-PS interface throughput is limited because the usage has exceeded the licensed capacity.


Logical type: Sum Trigger type: Sample Sampling interval: 1 s

Unit: s Range: Example values:


Operability class:

Related to feature:







Counter ID: M802C17 Network element name: AVE_RRC_CONN_MODE_USERS

Version: 1.0 NetAct name: AVE_RRC_CONN_MODE_USERS

Description: The average number of RRC connected mode users in the RNC (all states) during the mea-surement period.


Logical type: Average Trigger type: Sample Sampling interval: 1s



Operability class:

Related to feature:







Counter ID: M802C18 Network element name: MAX_RRC_CONN_MODE_USERS

30 DN04143903




Version: 1.0 NetAct name: MAX_RRC_CONN_MODE_USERS

Description: The peak number of RRC connected mode users in the RNC (all states) during the measure-ment period.


Logical type: Max Trigger type: Sample Sampling interval: 1s



Operability class:

Related to feature:







Counter ID: M802C19 Network element name: AVE_USERS_CELL_DCH

Version: 1.0 NetAct name: AVE_USERS_CELL_DCH

Description: The average number of users in Cell-DCH state in the RNC during the measurement period.





Operability class:

Related to feature:







Counter ID: M802C20 Network element name: AVE_USERS_CELL_FACH

Version: 1.0 NetAct name: AVE_USERS_CELL_FACH

Description: The average number of users in Cell-FACH state in the RNC during the measurement period.





Operability class:

DN04143903 31



Related to feature:







Counter ID: M802C21 Network element name: AVE_USERS_CELL_PCH

Version: 1.0 NetAct name: AVE_USERS_CELL_PCH

Description: The average number of users in Cell-PCH state in the RNC during the measurement period.





Operability class:

Related to feature:







Counter ID: M802C22 Network element name: AVE_USERS_URA_PCH

Version: 1.0 NetAct name: AVE_USERS_URA_PCH

Description: The average number of users in URA-PCH state in the RNC during the measurement period.





Operability class:

Related to feature:

RAN 833: PS UE States: URA PCH







32 DN04143903




Counter ID: M802C23 Network element name: AMR_OVER_HSPA_AVERAGE

Version: 1.0 NetAct name: AMR_OVER_HSPA_AVERAGE

Description: The average number of CS Voice calls over HSPA users.The same users are included also in counter M802C0 AMR_AVERAGE because it counts both Rel99 and HSPA CS Voice users.

Updated: Sampled periodically with a 1 second interval.




M802C0: AMR_AVERAGE

Operability class:

Related to feature:

RAN1689: CS Voice Over HSPA





Used from release: RN5.0 EP1 Definition updated in release:

Counter ID: M802C24 Network element name: AMR_OVER_HSPA_MAX

Version: 1.0 NetAct name: AMR_OVER_HSPA_MAX

Description: The maximum number of CS Voice calls over HSPA users. The maximum number of calls is the maximum value among the samples during a measurement period.The same users are included also in counter M802C1 AMR_MAX because it counts both Rel99 and HSPA CS Voice users.

Updated: Sampled periodically with a 1 second interval.




M802C1: AMR_MAX

Operability class:

Related to feature:

RAN1689: CS Voice Over HSPA






Counter ID: M802C25 Network element name: AVE_RRC_CONN_MODE_LFD_UE

Version: 1.0 NetAct name: AVE_RRC_CONN_MODE_LFD_UE

DN04143903 33



Description: The average number of such UEs in RRC connected mode (any state) that have been iden-tified as Legacy Fast Dormancy UEs.

Updated: The number of UEs is sampled with one second interval.




Operability class:

Related to feature:

RAN2451: Fast Dormancy Profiling






34 DN04143903



Transport network resource measurements

4 Transport network resource measurementsThe resource measurements are targeted to indicate how much of the transport network capacity is used and how the resources are shared for different upper layer services.

4.1 AAL2 resource reservation measurement (800/320H)

4.1.1 Introduction to AAL2 resource reservation measurementThe AAL2 resource reservation measurement reports how successfully the transport resources are allocated for upper layer applications and different reasons for failures. The AAL2 resource reservation process is slightly different for each logical interface (Iub, Iur or Iu-CS). The resource reservation is described for each logical interface and the counter updating points are identified. To see how the transport resource reservation is related to the whole RRC or RAB connection setup, please refer to document RNC counters - RNW part.

The object identifiers of the measurement are AAL2 path (that is, ATM VCC used for AAL2 user plane type traffic), WBTS ID, and AAL usage. The measured paths are selected with ATM interface ID/VPI/VCI identifiers. The WBTS ID identifies the base station even though it is actually a transient measurement identifier because it can also have the not known value. The not known value is used when the connection is not an Iub connection. The only possible value for AAL usage in this measurement type is AAL2UD. The not known value is used for those ATM VC connections for which the service type is not known, that is, Iu and Iur VCCs.

The statistics for the whole RNC (that is, a sum of all configured AAL2 paths counters) are available by selecting the measurement object as interface-0/VPI-0/VCI-0. Also some failure situations, for example digit analysis failure, are updated only for 0/0/0 object because the actual VCI is not known.

This measurement is optional and available as a part of RAS05 feature AAL2 resource reservation statistics.

AAL2 resource reservation in IubFigure Transport resource reservation over Iub for mobile oriented call presents how AAL2 transport resources are reserved in Iub between RNC and BTS. The reservation is always initiated by RNC, which allocates own resources, before sending the AAL2 sig-nalling request to BTS. Instead of BTS, the other counterpart in resource reservation can also be AXC, if AAL2 multiplexing in BTS is activated, but the procedure is same in both cases, from RNC point of view.

DN04143903 35

RNC Counters - Transport and HW Part Transport network resource measurements


Figure 1 Transport resource reservation over Iub for mobile originated call

1. After the RNC internal reservation is successfully done, counter RES_SUCCEEDED (M800C0) is updated.

2. If the RNC internal reservation fails one of the following counters is updated, depending on the cause for failure.a) RES_EXT_CAP (M800C1). The reason for failure is that there is not enough

bandwidth in external ATM VCC.b) RES_INT_CAP (M800C2). The reason for failure is that there is not enough

capacity available inside RNC to terminate the connection.c) RES_OTHER (M800C3). The reason for failure is any other RNC internal

reason.The counters M800C0 - M800C5 are updated for all AAL2 reservations (also AAL2 reservations for HSDPA MAC-d flows), but shared HSDPA AAL2 alloca-tions are not included to the counters.If the shared HSDPA AAL2 allocation fails one of following counters is updated, depending on the cause for failure.

d) TRANSPORT_REJECTED_EXT_HSDPA (M800C7)e) TRANSPORT_REJECTED_INT_HSDPA (M800C8)f) OTHER_REJECTED_ HSDPA (M800C9)Note that counters M800C6 - M800C18 are updated only when a shared HSDPA transport solution is used. They are not updated when a dedicated ATM VCC is used for HSDPA.

3. There are detailed counters for AAL2 signalling in measurement AAL2 signalling protocol at UNI, refer to the description of the measurement for details.

4. Depending on the result of AAL2 signalling with BTS or AXC, the following counters are updated.a) AAL2_SUCCEEDED (M800C4)

BTS (WAM) RNC

UE AAL2SIG CAC AAL2SIG RRCATM RMCAC

RNC internal transportresource reservation

RRC: connection request

BTS internal transportresource reservation

1

2

3

4

AAL2 connection establishment:ERQ (SUGR)

Response to ERQ

RRC: connection setup

36 DN04143903




b) AAL2_REJECTED (M800C5)For shared HSDPA AAL2 allocation there is dedicated signaling counter.

c) AAL2_SUCCEEDED_HSDPA (M800C6)

AAL2 resource reservation in IurFigure Transport resource reservation over Iur in case new SHO branch is established presents how AAL2 resources are reserved in Iur for new SHO branch through DRNC.

Figure 2 Transport resource reservation over Iur in case new SHO branch is estab-lished

1. After the RNC internal reservation is successfully done, counter RES_SUCCEEDED (M800C0) is updated.

2. If the RNC internal reservation fails one of the following counters is updated, depending on the cause for failure.a) RES_EXT_CAP (M800C1)b) RES_INT_CAP (M800C2)c) RES_OTHER (M800C3)

3. The reservation in DRNC end does not update the counters for AAL2 resource res-ervation measurement.

4. There are detailed counters for AAL2 signalling in measurement AAL2 signalling at NNI, refer to the description of the measurement for details.

5. Depending on the result of AAL2 signalling with DRNC, the following counters are updated in SRNC.a) AAL2_SUCCEEDED (M800C4)b) AAL2_REJECTED (M800C5)

DRNC SRNC

RRC AAL2SIG CAC AAL2SIG RRCATM RMCAC

RNSAP asks DRNC toestablish Iub branchbefore the Iur branchis established.

1

2

3

4

AAL2 connectionestablishment:ERQ (SUGR)

Response to ERQ

SRNC internal transportresource reservation

ATMRM

DRNC internal transportresource reservation

5

Transport resource requestfrom RRC(after Iub in DRNS

is complete)

DN04143903 37



AAL2 resource reservation in Iu-CSThe transport resource reservation in Iu-CS interface is similar to Iur case, just the DRNC is replaced with MGW and upper layer signaling is different. The counters are updated in RNC similarly as in the Iur case.

4.1.2 AAL2 resource reservation measurement countersThe object of the measurement is AAL2 path (that is, ATM VCC used for AAL2 user plane type traffic) and the measured paths are selected with ATM interface ID/VP VCI identifiers. The statistics for the whole RNC (that is, a sum of all configured AAL2 paths counters) are available by selecting the measurement object as interface-0/VPI-0/VCI-0. Also some failure situations, for example digit analysis failure, are updated only for 0/0/0 object because the actual VCI is not known. The measurement identifier is 800/320H.

Counter ID: M800C0 Network element name: RES_SUCCEEDED

Version: 3.1 NetAct name: RES_SUCCEEDED

Description: The number of AAL2 resource requests that are successfully reserved to RNC, but still need to be signalled using AAL2 signalling protocol to be operational.

Updated: When resource reservation is completed and AAL2 signalling is started.

Logical type: Cumulative Trigger type: Event Sampling interval:



Operability class: Resources

Related to feature:

RAN 236: HSDPA Transport with Best Effort AAL2 QoS

RAN 773: AAL2 Resource Reservation Statistics






Counter ID: M800C1 Network element name: RES_EXT_CAP

Version: 3.1 NetAct name: RES_EXT_CAP

Description: The number of transport resource reservations rejected because of the lack of RNC-external AAL2 resources. This is the number of transport resource requests which are rejected by CAC since there is not enough capacity in the external AAL2 path.

Updated: When resource request is rejected because of RNC-external AAL2 resources.




Operability class:

38 DN04143903




Related to feature:








Counter ID: M800C2 Network element name: RES_INT_CAP

Version: 3.1 NetAct name: RES_INT_CAP

Description: The number of transport resource reservations rejected because of the lack of RNC-internal capacity. This is the number of resource reservations which are rejected by CAC since there are no RNC-internal AAL2 processing resources available.

Updated: When resource request is rejected because of RNC-internal AAL2 resources.





Related to feature:








Counter ID: M800C3 Network element name: RES_OTHER

Version: 3.1 NetAct name: RES_OTHER

Description: The number of AAL2 resource reservations that failed for any reason other than CAC or sig-nalling (for example route analysis, parameter or DSP resource allocation problem).

Updated: When resource reservation has failed for any reason other than CAC or signalling.





Related to feature:




DN04143903 39







Counter ID: M800C4 Network element name: AAL2_SUCCEEDED

Version: 3.1 NetAct name: AAL2_SUCCEEDED

Description: The number of AAL2 signalling requests that are successfully executed in A2SP.

Updated: When AAL2 signalling is successfully completed.





Related to feature:








Counter ID: M800C5 Network element name: AAL2_REJECTED

Version: 3.1 NetAct name: AAL2_REJECTED

Description: The number of AAL2 signalling requests that failed for any reason.

Updated: When AAL2 signalling fails for any reason.

Logical type: Sum Trigger type: Event Sampling interval:




Related to feature:








40 DN04143903




Counter ID: M800C6 Network element name: AAL2_SUCCEEDED_HSDPA

Version: 3.1 NetAct name: AAL2_SUCCEEDED_HSDPA

Description: The number of successfully signalled shared HSDPA AAL2 transport resource allocations.

Updated: When HSDPA transport resource setup is successful.




Operability class:

Related to feature:

RAN 821: HSDPA Resource Allocation








Counter ID: M800C7 Network element name: TRANSPORT_REJECTED_EXT_HSDPA

Version: 3.1 NetAct name: TRANSPORT_REJECTED_EXT_HSDPA

Description: The number of shared HSDPA AAL2 allocation attempts that were rejected because of external Connection Admission Control.

Updated: When transport resource request is rejected because of external Connection Admission Control.




Operability class:

Related to feature:









DN04143903 41



Counter ID: M800C8 Network element name: TRANSPORT_REJECTED_INT_HSDPA

Version: 3.1 NetAct name: TRANSPORT_REJECTED_INT_HSDPA

Description: The number of shared HSDPA AAL2 allocation attempts that were rejected because of the lack of RNC-internal AAL2 resources.

Updated: When transport resource request is rejected because of RNC-internal Connection Admission Control.




Operability class:

Related to feature:









Counter ID: M800C9 Network element name: OTHER_REJECTED_HSDPA

Version: 3.1 NetAct name: OTHER_REJECTED_HSDPA

Description: The number of shared HSDPA AAL2 allocation attempts that were rejected because of any reason other than internal or external Connection Admission Control, or too many users without AAL2 reservation.

Updated: When HSDPA shared AAL2 transport resource setup fails.




Operability class:

Related to feature:









42 DN04143903




Counter ID: M800C10 Network element name: ACTIVE_HSDPA_RES_TIME

Version: 3.1 NetAct name: ACTIVE_HSDPA_RES_TIME

Description: The sum of durations when at least one HSDPA user was utilizing the shared HSDPA AAL2 allocation.

Updated: When the last user of the shared HSDPA AAL2 allocation leaves the cell, the counter is updated with the allocation duration.

Logical type: Sum Trigger type: Duration Sampling interval:



Operability class:

Related to feature:









Counter ID: M800C11 Network element name: WAITING_HSDPA_RES_TIME

Version: 3.1 NetAct name: WAITING_HSDPA_RES_TIME

Description: The sum of durations when the shared HSDPA AAL2 path was allocated, but without any HSDPA user.

Updated: When the shared HSDPA AAL2 allocation is released because of the timer expiring or because of an HSDPA user entering the cell, this counter is updated with the duration that was allocated to the AAL2 resources, but without any user.




Operability class:

Related to feature:









DN04143903 43



Counter ID: M800C12 Network element name: RELEASE_TIMER_LENGTH

Version: 3.1 NetAct name: RELEASE_TIMER_LENGTH

Description: The value of the shared HSDPA AAL2 allocation reservation release timer, "ReleaseTim-erForSharedHSDPAallocation", at the end of the measurement interval. This counter is not valid and not updated for RNC-level sum because the release timer can be configured separately for each BTS.

Updated: When the measurement data is collected, the counter is updated with the current release timer value.

Logical type: Current Trigger type: Event Sampling interval:



Operability class:

Related to feature:









Counter ID: M800C13 Network element name: RESERV_REL_DUE_TO_TIMER

Version: 3.1 NetAct name: RESERV_REL_DUE_TO_TIMER

Description: The number of times when the shared HSDPA AAL2 allocation was released because the release timer expired. This counter is also updated if the release timer value is zero and the reservation is released after the last user leaves the cell.

Updated: When the release timer expires and the shared HSDPA AAL2 allocation is released. This counter is also updated if the release timer value is zero and the reservation is released after the last user leaves the cell.




Operability class:

Related to feature:








44 DN04143903




Counter ID: M800C14 Network element name: RESERV_REL_TIMER_STARTED

Version: 3.1 NetAct name: RESERV_REL_TIMER_STARTED

Description: The number of times when release timer for shared HSDPA AAL2 allocation, defined by parameter "ReleaseTimerForSharedHSDPAallocation", was started because there were no active AAL2 connections for HSDPA.

Updated: When the shared HSDPA AAL2 allocation release timer is started when the last HSDPA user leaves the cell.




Operability class:

Related to feature:








Counter ID: M800C15 Network element name: RESERV_REL_TIMER_STOPPED

Version: 3.1 NetAct name: RESERV_REL_TIMER_STOPPED

Description: The number of times when release timer for shared HSDPA AAL2 allocation, defined by parameter "ReleaseTimerForSharedHSDPAallocation", was stopped because a HSDPA user entered the cell.

Updated: When the shared HSDPA AAL2 allocation release timer is stopped because a HSDPA user enters the cell.




Operability class:

Related to feature:








DN04143903 45



Counter ID: M800C16 Network element name: RESERV_REL_DUE_TO_OTHER

Version: 3.1 NetAct name: RESERV_REL_DUE_TO_OTHER

Description: The number of times when the shared HSDPA AAL2 allocation was released because of any reason other than release timer expiration. This can happen, for example, because of ATM network failure or BTS reset.

Updated: When the shared HSDPA AAL2 allocation is released before release timer expiration.




Operability class:

Related to feature:








Counter ID: M800C17 Network element name: ACTIVE_TIME_CUMULATIVE

Version: 3.1 NetAct name: ACTIVE_TIME_CUMULATIVE

Description: The cumulative sum of durations when at least one HSDPA user has utilised the shared HSDPA AAL2 allocation during the measurement period.

Updated: When the measurement period ends, the counter is updated by the cumulative sum allocation duration.

Logical type: Cumulative Trigger type: Duration Sampling interval:



Operability class:

Related to feature:








Counter ID: M800C18 Network element name: WAITING_TIME_CUMULATIVE

46 DN04143903




Version: 3.1 NetAct name: WAITING_TIME_CUMULATIVE

Description: The cumulative sum of durations when there have been no HSDPA connections, but the shared HSDPA AAL2 allocation has been reserved because of the release timer period.

Updated: When the measurement period ends, this counter is updated by the cumulative sum of the waiting time duration.




Operability class:

Related to feature:








Counter ID: M800C19 Network element name: REJECT_HSDPA_TOO_MANY_USERS

Version: 3.1 NetAct name: REJECT_HSDPA_TOO_MANY_USERS

Description: The number of rejected HSDPA AAL2 reservations because of too many users. This includes occurrences where transport resource reservation for HSDPA MAC-d flow has been rejected because of too many users. This is related to the case where the shared HSDPA AAL2 allocation has failed and the number of users is limited to the number given by parameter "NbrOfOverbookedHSD-PAUsers".

Updated: When HSDPA AAL2 reservation is rejected because of too many users.




Operability class:

Related to feature:








DN04143903 47



4.2 AAL2 path CAC resource measurement (550/226H)

4.2.1 Introduction to AAL2 path CAC resource measurementThe AAL2 path CAC resource measurement reports the resource usage for AAL2 type ATM connections, which are used to transport all user plane traffic over Iub, Iur and Iu-CS interfaces. The AAL2 connection resources are allocated and released by CAC (Connection Admission Control) based on radio layer capacity request. The CAC controls that no more connections are established for AAL2 path than it can serve with its bandwidth. This measurement includes counters for RNC CAC capacity allocations. The RNC CAC controls resource usage in egress direction (that is, from RNC to BTS). There are also dedicated counters for HSDPA transport resource allocations and differ-ent failure reasons, which have caused rejection of resource reservation.

Note that the real traffic load can exceed the CAC reservation if there is HSDPA traffic (in case there is no RT/NRT reservation, HSDPA can use all the remaining bandwidth in the VCC) or there is CAC overbooking for the NRT traffic (the real NRT traffic load can exceed the CAC reservation).


The counter updating rules are slightly different depending on whether the measured connections are part of VCC bundle or not. Both alternatives are described below.

The measured ATM VC connection is not in VCC bundleThe measuring of AAL2 path allocated capacity is based on sampling the allocation size frequently (the default sampling interval is 1 second). The relation of sampling values, counter values and actual traffic volume of VCC is described in figure Example of AAL2 path capacity allocations and related counters. The object identifiers of the measure-ment are AAL2 type ATM VCC connection, WBTS ID, and AAL usage. The WBTS ID identifies the base station even though it is actually a transient measurement identifier because it can also have the not known value. The not known value is used when the connection is not an Iub connection. The only possible value for AAL usage in this mea-surement type is AAL2UD. The not known value is used for those ATM VC connections for which the service type is not known, that is, Iu and Iur VCCs.

48 DN04143903




Figure 3 Example of AAL2 path capacity allocations and related counters

1. Each sample for the total reserved capacity (blue line in figure) is summed together for the whole measurement period. The result is shown in counters:a) SUM_RESERVED_CELL_RATE (M550C1)b) NBR_SAMPLES (M550C7)

The same is done for the shared HSDPA allocation size (grey line in figure) and the related counter is:

c) SHARED_HSDPA_AAL2_ALLOCATION (M550C16)2. The peak and minimum sampled values for measurement period update the follow-

ing counters:a) MIN_RESERVED_CELL_RATE (M550C2)b) MAX_RESERVED_CELL_RATE (M550C3)

3. The peak cell rate of AAL2 path is given as a reference in counter:a) AAL2_PATH_GUAR_CELL_RATE (M550C0)

There are also similar counters for the number of AAL2 connections during measure-ment period. Those can be used to monitor the CID number usage and for HSDPA allo-cation to calculate the allocated capacity that is available per user.

Counters are updated differently depending on the VCC type, which can be DCH&HSDPA, DCH, DCH&HSPA, HSPA, HSDPA or HSUPA. The following para-graphs describe how counter values are updated when ATM VC connection is not part of VCC bundle.

The AAL2 resource reservations are divided here into three different groups:

1. The reservations for AAL2 connections that are used for common channels and DCH connections

2. The reservations for HSDPA connections that are used to transport the MAC-d flows3. The shared HSDPA AAL2 allocations

The counters should be updated based on the following rules:

• HSDPA connection specific counters are updated in the case of AAL2 resource res-ervation for MAC-d flow (2).

1

Time/sec.

Trafficrate

(cells/sec.)

ConfiguredPCR of VCC

VCC loadestimated byCAC

Real trafficload of ATMVCC

= sampledvalues

2 3

DN04143903 49



• The counters not dedicated to any specific connection type are updated for both cases 1 and 2.

• The counters for reserved cell rate (sum, max, min) are updated for all connection types (1, 2 and 3).

Table Updating of AAL2 CAC counters for different connection types that are not part of VCC bundle describes how each counter is updated for different AAL2 connection types.

Counter / VCC type DCH& HSDPA

DCH DCH& HSPA

HSPA HSDPA HSUPA

M550C0 AAL2_PATH_GUAR_CELL_RATE

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

M550C1 SUM_RESERVED_CELL_RATE

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

M550C2 MIN_RESERVED_CELL_RATE

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

M550C3 MAX_RESERVED_CELL_RATE

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

Y (Note1)

M550C4 SUM_AAL2_CONNECTIONS Y Y Y Y Y Y

M550C5 MIN_AAL2_CONNECTIONS Y Y Y Y Y Y

M550C6 MAX_AAL2_CONNECTIONS Y Y Y Y Y Y

M550C8 AAL2_RM_SUCCEEDED Y Y Y Y Y Y

M550C9 AAL2_CAC_REJECTED Y Y Y Y Y Y

M550C10 AAL2_HW_REJECTED Y Y Y Y Y Y

M550C11 SUM_AAL2_CONNECTIONS_HSDPA Y NR Y Y Y NR

M550C12 MIN_AAL2_CONNECTION_HSDPA Y NR Y Y Y NR

Table 5 Updating of AAL2 CAC counters for different connection types that are not part of VCC bundle

50 DN04143903




The symbols used in the table are the following:

• Y = The counter is updated. • NR = The counter is not updated or is not meaningful (i.e. always = 0). • • Note1: if this connection is using CBR VCC, the counter is available and value is

the maximum configured value for AAL2 path traffic and equal to the AAL2 VCC Peak Cell rate (PCR). For UBR+ VCC, Min Cell rate (MCR) is used instead of PCR as guaranteed cell rate, so the value of counter is updated to MCR.

The measured ATM VC connection is in VCC bundleThe measuring of AAL2 path allocated capacity is based on sampling the allocation size frequently (the default sampling interval is 1 second). The relation of capacity allocations inside one VCC bundle and counter values is described in Figure Example of AAL2 path capacity allocations and related counters for VCC bundle.

You should note that a VCC bundle is a shared resource for many ATM VCC connec-tions (for three VCCs in the figure), but all counters are still VCC-specific (although the capacity is shared dynamically between the VC connections). The VCC bundle is only used in the Iub interface. The Shared HSDPA allocation (SHA) related counters are not relevant and never updated, because SHA is not used in the VCC bundle configuration. The object of the measurement is AAL2 type ATM VCC connection.

M550C13 MAX_AAL2_CONNECTIONS_HSDPA Y NR Y Y Y NR

M550C14 AAL2_CAC_REJECTED_HSDPA Y NR Y Y Y NR

M550C15 AAL2_HW_REJECTED_HSDPA NR NR NR NR NR NR

M550C17 AAL2_RM_SUCCEEDED_HSDPA Y NR Y Y Y NR

Counter / VCC type DCH& HSDPA

DCH DCH& HSPA

HSPA HSDPA HSUPA

Table 5 Updating of AAL2 CAC counters for different connection types that are not part of VCC bundle (Cont.)

DN04143903 51



Figure 4 Example of AAL2 path capacity allocations and related counters for VCC bundle

1. For average capacity allocations measuring purposes, the following actions take place in every sampling instant:a) The value of the SUM_RESERVED_CELL_RATE (M550C1) counter is

increased by the value of capacity allocated for a specific VCC. In the case of RT or RT/NRT shared VCC, this value is equal to the capacity allo-cated by AAL2 CAC for RT/NRT connections. In the case of HSPA/HSDPA or NRT DCH VCC, the value is equal to the capacity available for the VCC (calcu-lated by the VCC bundle functionality). The available capacity changes dynam-ically and is affected by the amount of VCC bundle total bandwidth, capacity allocated for RT VCC, and excess bandwidth share parameter.

b) NBR_SAMPLES (M550C7)The number of samples counter is updated once for each sampling instant. It can be used to calculate the average allocations.

2. The peak sampled values for measurement period update the following counter:a) MAX_RESERVED_CELL_RATE (M550C3)

Also in this case, the RT VCC peak rate is equal to the peak capacity allocated by AAL2 CAC. For both HSDPA and NRT DCH VCC, the peak value is equal to the highest available capacity value sampled during measurement period (cal-culated by the VCC bundle functionality). The counter for minimum reserved cell rate (M550C2) is updated similarly with the smallest values during the measure-ment period.

3. The peak cell rate of the AAL2 path is given as a reference in the following counter:a) AAL2_PATH_GUAR_CELL_RATE (M550C0)

This counter value changes only when the VCC bandwidth (PCR) is changed and it is updated only for CBR service category VCC.

The counters for measuring the number of AAL2 connections during the measurement period are updated similarly as in the case the VCC bundle is not used. The counters can be used to monitor the CID number usage.

Counters are updated differently depending on the VCC type, which can be DCH, HSPA, HSDPA or HSUPA. Shared type VCC cannot be attached to the VCC bundle. The following paragraphs describe how counters are updated when ATM VC connection is part of VCC bundle.

trafficrate

[cells/sec.]

Time/sec= sampling instant

VCCbundle capacityavailable for HSDPA

VCCbundle capacityavailable for NRT DCH

VCCbundle PCR

Capacity allocated toRT ATM VCC by AAL2 CAC

RT (CBR) ATM VCCPCR

This line describes the sha-ring of available VCCbundlecapacity between NRT DCHand HSDPA VCC

3

1

2

1

1

Peak capacity availablefor HSDPA

2

Peak capacity availablefor NRT DCH

2

52 DN04143903




The AAL2 resource reservations are divided here into three different groups:

1. The reservations for AAL2 connections that are used for common channels and DCH connections

2. The reservations for HSDPA connections that are used to transport the MAC-d flows3. The shared HSDPA AAL2 allocations

The counters are updated based on the following rules:

• HSDPA connection specific counters are updated in the case of AAL2 resource res-ervation for MAC-d flow (2).

• The counters not dedicated to any specific connection type are updated for both cases 1 and 2.

• The counters for reserved cell rate (sum, max, min) are updated for all connection types (1, 2 and 3).

Table Updating of AAL2 CAC counters for different connection types that are part of VCC bundle describes how each counter is updated for different AAL2 connection types and HW configurations. A2SP refers to the older HW configuration with A2SP and NIS1/NIP1 units. NPS1 is the new HW configuration where A2SP does not exist.

VCC types DCH&HSDPA and DCH&HSPA VCC cannot be in the bundle.

Counter / VCC type DCH HSPA HSDPA HSUPA DCH&HSDPA

DCH&HSPA

M550C0 AAL2_PATH_GUAR_CELL_RATE Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1)

M550C1 SUM_RESERVED_CELL_RATE Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1)

M550C2 MIN_RESERVED_CELL_RATE Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1)

M550C3 MAX_RESERVED_CELL_RATE Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1) Y(Note1)

M550C4 SUM_AAL2_CONNECTIONS Y Y Y Y Y Y

M550C5 MIN_AAL2_CONNECTIONS Y Y Y Y Y Y

M550C6 MAX_AAL2_CONNECTIONS Y Y Y Y Y Y

M550C8 AAL2_RM_SUCCEEDED Y Y Y Y Y Y

M550C9 AAL2_CAC_REJECTED Y Y Y Y Y Y

Table 6 Updating of AAL2 CAC counters for different connection types that are part of VCC bundle

DN04143903 53



The symbols used in the table are the following:

• Y = The counter is updated. • NR = The counter is not updated or is not meaningful (e.g. always = 0). • Note1: If the VCC is configured CBR type, the counter is same as VCC PCR. For

UBR+ VCC the counter is not available.

4.2.2 AAL2 path CAC resource measurement countersThe object of the measurement is AAL2 path (that is, ATM VCC used for AAL2 user plane type traffic) and the measured paths are selected with ATM interface ID/VPI/VCI identifiers. The measurement identifier is 550/226H.

M550C10 AAL2_HW_REJECTED Y Y Y Y Y Y

M550C11 SUM_AAL2_CONNECTIONS_HSDPA NR Y Y NR Y Y

M550C12 MIN_AAL2_CONNECTION_HSDPA NR Y Y NR Y Y

M550C13 MAX_AAL2_CONNECTIONS_HSDPA NR Y Y NR Y Y

M550C14 AAL2_CAC_REJECTED_HSDPA NR Y Y NR Y Y

M550C15 AAL2_HW_REJECTED_HSDPA NR NR NR NR NR NR

M550C17 AAL2_RM_SUCCEEDED_HSDPA NR Y Y NR Y Y

Counter / VCC type DCH HSPA HSDPA HSUPA DCH&HSDPA

DCH&HSPA

Table 6 Updating of AAL2 CAC counters for different connection types that are part of VCC bundle (Cont.)

Counter ID: M550C0 Network element name: AAL2_PATH_GUAR_CELL_RATE

Version: 6.3 NetAct name: AAL2_PATH_GUAR_CELL_RATE

Description: The configured cell rate for the ATM VCC. For CBR type VC connections this is the AAL2 VCC Peak Cell rate (PCR). For UBR+ VCC in a bundle, this is the PCR of the bundle. For UBR+ VCC not in a bundle, this is the Minimum Desired Cell Rate (MDCR) of the VCC.

Updated: The counter is updated for CBR and UBR+ type VC connections. Stays constant throughout the AAL2 path lifecycle.


Unit: cell/s Range: Example values:


Operability class:

54 DN04143903




Related to feature:

RAN 236: HSDPA Transport with Best Effort AAL2 QoS RAN 773: AAL2 Resource Reservation Statistics





Used from release: RN2.1/U3 Definition updated in release: RN3.0

Counter ID: M550C1 Network element name: SUM_RESERVED_CELL_RATE

Version: 8.1 NetAct name: SUM_RESERVED_CELL_RATE

Description: The sum of reserved cell rate samples taken during measurement period. When divided by M550C7, it produces the average reserved cell rate. If the VC connection is part of a VC bundle, the counter is updated with the sampled available capacity value of the whole bundle capacity for NRT or HSDPA, depending on the VC type.This counter is not relevant to look at if the path type is Tolerant because there is no AAL2 CAC for such paths.

Updated: Added to previous value when data is sampled. This value is reset when the counters are col-lected at the end of measurement interval.

Logical type: Sum Trigger type: Sample Sampling interval:



M550C7: NBR_SAMPLES

Operability class:

Related to feature:

RAN952: Optimized Iub AAL2 Reservations for SRBs

RAN236: HSDPA Transport with Best Effort AAL2 QoS

RAN773: AAL2 Resource Reservation Statistics





Used from release: RN2.1/U3 Definition updated in release:

Counter ID: M550C2 Network element name: MIN_RESERVED_CELL_RATE

Version: 8.1 NetAct name: MIN_RESERVED_CELL_RATE

Description: The minimum reserved cell rate of AAL2 path during measurement interval. If the VC con-nection is part of a VC bundle, the counter is updated with the minimum available capacity value of the whole bundle capacity for the NRT or HSDPA, depending on the VC type.This counter is not relevant to look at if the path type is Tolerant because there is no AAL2 CAC for such paths.

DN04143903 55



Updated: Updated when the current reserved cell rate is less than the previous value. This value is reset when the counters are collected at the end of the measurement interval.

Logical type: Min Trigger type: Sample Sampling interval:



Operability class:

Related to feature:









Counter ID: M550C3 Network element name: MAX_RESERVED_CELL_RATE

Version: 8.1 NetAct name: MAX_RESERVED_CELL_RATE

Description: The maximum reserved cell rate of AAL2 path during measurement interval. If the VC con-nection is part of a VC bundle, the counter is updated with the maximum available capacity value of the whole bundle capacity for the NRT or HSDPA, depending on the VC type.This counter is not relevant to look at if the path type is Tolerant because there is no AAL2 CAC for such paths.

Updated: Updated when the current reserved cell rate exceeds the previous value. This value is reset when the counters are collected at the end of measurement interval.

Logical type: Max Trigger type: Sample Sampling interval:



Operability class:

Related to feature:









Counter ID: M550C4 Network element name: SUM_AAL2_CONNECTIONS

56 DN04143903




Version: 6.2 NetAct name: SUM_AAL2_CONNECTIONS

Description: The sum of sampled values for the number of AAL2 connections during the measurement period. This counter includes all AAL2 connections for specific ATM VCC, also HSDPA MAC-d flows in the RNC. When divided by M550C7, it produces the average number of AAL2 connections.

Updated: Updated as data is sampled by data provider. This value is reset when the counters are col-lected at the end of measurement interval.




M550C7: NBR_SAMPLES

Operability class:

Related to feature:







Counter ID: M550C5 Network element name: MIN_AAL2_CONNECTIONS

Version: 6.2 NetAct name: MIN_AAL2_CONNECTIONS

Description: The minimum number of simultaneously active connections in AAL2 path during measure-ment interval. This counter includes all AAL2 connections for specific ATM VCC, also HSDPA MAC-d flows in the RNC.

Updated: Updated when the current number of AAL2 connections is less than the previous value. This value is reset when the counters are collected at the end of the measurement interval.




Operability class:

Related to feature:







Counter ID: M550C6 Network element name: MAX_AAL2_CONNECTIONS

DN04143903 57



Version: 6.2 NetAct name: MAX_AAL2_CONNECTIONS

Description: The maximum number of connections in AAL2 path during measurement period. This counter includes all AAL2 connections reserved for specific ATM VCC, also HSDPA MAC-d flows in the RNC, and reflects the peak number of CID used during measurement period.

Updated: Updated when the current number of AAL2 connections is greater than previous value. This value is reset when the counters are collected at the end of the measurement interval.




Operability class:

Related to feature:







Counter ID: M550C7 Network element name: NBR_SAMPLES

Version: 3.1 NetAct name: NBR_SAMPLES

Description: The number of samples that can be used to calculate average values for AAL2 connections, HSDPA connections as well as the average allocation for HSDPA.

Updated: Incremented when data is sampled.




M550C1: SUM_RESERVED_CELL_RATE

M550C4: SUM_AAL2_CONNECTIONS

M550C11: SUM_AAL2_CONNECTIONS_HSDPA

Operability class:

Related to feature:








Counter ID: M550C8 Network element name: AAL2_RM_SUCCEEDED

58 DN04143903




Version: 3.1 NetAct name: AAL2_RM_SUCCEEDED

Description: The number of successful AAL2 resource reservations. The connection has successfully passed the AAL2 connection resource reservation stage, but may still fail in the DMPG/TPG resource reservation or in the signalling phase.

Updated: Incremented when an AAL2 resource reservation is successful.




Operability class:

Related to feature:








Counter ID: M550C9 Network element name: AAL2_CAC_REJECTED

Version: 3.1 NetAct name: AAL2_CAC_REJECTED

Description: The total number of rejected connections due to CAC.

Updated: Updated when a connection is rejected due to insufficient CAC resources.




Operability class:

Related to feature:








Counter ID: M550C10 Network element name: AAL2_HW_REJECTED

Version: 3.2 NetAct name: AAL2_HW_REJECTED

Description: The number of connection establishments, which are rejected due to failed HW request. This failure can occur after successful CAC resource reservation.

Updated: Updated when a connection is rejected for hardware reasons.

DN04143903 59






Operability class:

Related to feature:







Used from release: RN2.1/U3 Definition updated in release: RN3.0/U4.0

Counter ID: M550C11 Network element name: SUM_AAL2_CONNECTIONS_HSDPA

Version: 6.1 NetAct name: SUM_AAL2_CONNECTIONS_HSDPA

Description: The sum of sampled values for the number AAL2 connections used by HSDPA, during mea-surement period. When divided by M550C7, it produces the average number of HSDPA connections. The counter is updated for HSDPA Mac-d flow reservations only. This value stays 0 in MGW.

Updated: Added to previous value when data is sampled. This value is reset when the counters are col-lected at the end of the measurement interval.




M550C7: NBR_SAMPLES

Operability class:

Related to feature:








Counter ID: M550C12 Network element name: MIN_AAL2_CONNECTION_HSDPA

Version: 6.1 NetAct name: MIN_AAL2_CONNECTION_HSDPA

Description: The minimum number of HSDPA connections during the measurement period. The counter is updated for HSDPA Mac-d flow reservations only. This value stays 0 in MGW.

Updated: Updated when the current number of HSDPA Mac-d flow connections is less than the previous value. This value is reset when the counters are collected at the end of the measurement interval.

60 DN04143903







Operability class:

Related to feature:








Counter ID: M550C13 Network element name: MAX_AAL2_CONNECTIONS_HSDPA

Version: 6.1 NetAct name: MAX_AAL2_CONNECTIONS_HSDPA

Description: The maximum number of simultaneous HSDPA connections during the measurement period. This represents the highest value of samples taken. The counter is updated for HSDPA Mac-d flow reservations only and so this counter reports the peak number of HSDPA Mac-d flows during mea-surement period. This value stays 0 in MGW.

Updated: Updated when the current number of HSDPA Mac-d flow connections exceeds the previously maximum value; This value is reset when the counters are collected at the end of the measurement interval




Operability class:

Related to feature:








Counter ID: M550C14 Network element name: AAL2_CAC_REJECTED_HSDPA

Version: 6.1 NetAct name: AAL2_CAC_REJECTED_HSDPA

Description: The number of times AAL2 resource reservations for HSDPA connection have been rejected by AAL2 CAC. The counter is updated for rejected HSDPA Mac-d flow reservations only. This value stays 0 in MGW.

DN04143903 61



Updated: Updated when an HSDPA Mac-d flow connection is rejected due to insufficient CAC resources.




Operability class:

Related to feature:








Counter ID: M550C15 Network element name: AAL2_HW_REJECTED_HSDPA

Version: 6.1 NetAct name: AAL2_HW_REJECTED_HSDPA

Description: The number of times AAL2 resource reservation for HSDPA connection was rejected by HW. The counter is updated for rejected HSDPA Mac-d flow reservations only. This value stays 0 in MGW.

Updated: Updated when an HSDPA Mac-d flow connection is rejected by hardware.




Operability class:

Related to feature:








Counter ID: M550C16 Network element name: SHARED_HSDPA_AAL2_ALLOCATION

Version: 6.2 NetAct name: SHARED_HSDPA_AAL2_ALLOCATION

Description: The current value for the cell rate of shared HSDPA AAL2 allocation at the time of measure-ment data collection.

Updated: The value is sampled at the end of measurement interval.



62 DN04143903





Operability class:

Related to feature:







Counter ID: M550C17 Network element name: AAL2_RM_SUCCEEDED_HSDPA

Version: 6.1 NetAct name: AAL2_RM_SUCCEEDED_HSDPA

Description: The number of times downlink AAL2 resources have been successfully reserved for HSDPA MAC-D flow connections. This indicates that ATM resources were successfully reserved in RNC, but the connection may still fail in the AAL2 signalling with BTS. The counter is updated for HSDPA Mac-d flow reservations only. This value stays 0 in MGW.

Updated: Updated when AAL2 resources are successfully reserved for HSDPA Mac-d flow connection.




Operability class:

Related to feature:








Counter ID: M550C18 Network element name: MIN_SHARED_HSDPA_AAL2_ALLOC

Version: 3.1 NetAct name: MIN_SHARED_HSDPA_AAL2_ALLOC

Description: The minimum size of shared HSDPA AAL2 allocation during the measurement period.

Updated: Updated when the current reserved cell rate is less than the previous value. This value is reset when the counters are collected at the end of the measurement interval.




Operability class:

DN04143903 63



4.3 RNC IP CAC measurement (804/324H)The RNC IP CAC measurement provides information on the transport resource reser-vation success rate in IP routes used in Iu-CS, Iu-PS, Iur or Iub interfaces. An IP route can be, for example, an Iub link towards one base station.

Counters M804C0-M804C3 are supported for all RNC interfaces and show the success rate of IP Connection Admission Control reservations in egress direction, that is, the direction from the RNC to another network element. They are updated also in the DRNC side of the IP-based Iur interface when the resources are allocated in direction DRNC -> SRNC.

Counters M804C4-M804C6 are updated only for Iub routes. They provide the success rate of Iub reservations in ingress direction when seen from the RNC viewpoint, that is, the direction from WBTS to the RNC. Because the Connection Admission Control in this direction is done by the WBTS, the counters are based on NBAP cause codes returned by WBTS.

Related to feature:








Counter ID: M550C19 Network element name: MAX_SHARED_HSDPA_AAL2_ALLOC

Version: 3.1 NetAct name: MAX_SHARED_HSDPA_AAL2_ALLOC

Description: The maximum size of shared HSDPA AAL2 allocation during the measurement period.

Updated: Updated when the current reserved cell rate exceeds the previous value. This value is reset when the counters are collected at the end of measurement interval.




Operability class:

Related to feature:








64 DN04143903




Note that counters M804C4 - M804C6 can also be updated without the corresponding M804C0 SUCC_RNC_IP_RES update. This happens only when the Iub uplink direction is modified and the downlink transport configuration remains unchanged.

The object of the measurement is an IP route that is identified with a numeric route ID. In the measurement data sent to NetAct, also WBTS identifier is included if the route is used in the Iub interface.

Counter ID: M804C0 Network element name: SUCC_RNC_IP_RES

Version: 1.0 NetAct name: SUCC_RNC_IP_RES

Description: The number of successful IP transport resource reservations in the RNC.

Updated: When the IP resources are successfully reserved on the RNC side.




Operability class:

Related to feature:

RAN 76: IP Based Iur

RAN 750: IP Based Iu-PS

RAN 75: IP Based Iu-CS

RAN 74: IP Based Iub for Flexi WCDMA BTS






Counter ID: M804C1 Network element name: FAIL_RNC_IP_RES_EXT

Version: 1.0 NetAct name: FAIL_RNC_IP_RES_EXT

Description: The number of failed IP transport resource reservations in the RNC due to external connec-tion admission control.

Updated: When the RNC external IP connection admission control rejects the resource request.




Operability class:

Related to feature:








DN04143903 65





Counter ID: M804C2 Network element name: FAIL_RNC_IP_RES_INT

Version: 1.0 NetAct name: FAIL_RNC_IP_RES_INT

Description: The number of failed IP transport resource reservations in the RNC due to internal connec-tion admission control.

Updated: When the RNC internal IP connection admission control rejects the resource request.




Operability class:

Related to feature:










Counter ID: M804C3 Network element name: FAIL_RNC_IP_RES_OTHER

Version: 1.0 NetAct name: FAIL_RNC_IP_RES_OTHER

Description: The number of failed IP transport resource reservations in the RNC due to other than con-nection admission control reasons.

Updated: When the IP resource reservation fails due to any reason other than connection admission control failure. Such a reason could be for example route analysis failure caused by a configuration error.




Operability class:

Related to feature:









66 DN04143903





Counter ID: M804C4 Network element name: SUCC_BTS_IP_RES

Version: 1.0 NetAct name: SUCC_BTS_IP_RES

Description: The number of successful IP transport resource reservations in the BTS.

Updated: When the BTS returns NBAP: Radio Link Setup Response or NBAP: Radio Link Reconfigura-tion Ready indicating a successful radio link setup or reconfiguration with IP-based Iub interface.




Operability class:

Related to feature:







Counter ID: M804C5 Network element name: FAIL_BTS_IP_RES_EXT_TRANS

Version: 1.0 NetAct name: FAIL_BTS_IP_RES_EXT_TRANS

Description: The number of failed IP transport resource reservations in the BTS due to external connec-tion admission control.

Updated: When the BTS returns Transport Layer cause 'Transport resources Unavailable' in NBAP: Radio Link Setup Failure or NBAP: Radio Link Reconfiguration Failure.




Operability class:

Related to feature:







Counter ID: M804C6 Network element name: FAIL_BTS_IP_RES_OTHER_TRANS

Version: 1.3 NetAct name: FAIL_BTS_IP_RES_OTHER_TRANS

DN04143903 67



Description: The number of failed IP transport resource reservations in the BTS due to some other trans-port related failure than congestion. Also RNC internal failures after BTS successful response are included in this counter.

Updated: When the BTS returns Transport Layer cause 'Unspecified' in NBAP: Radio Link Setup Failure or NBAP: Radio Link Reconfiguration Failure. The counter is updated also if an RNC internal failure prevents the transport bearer establishment even if BTS would have returned a successful NBAP response.




Operability class:

Related to feature:







68 DN04143903



Signalling measurements

5 Signalling measurementsThe signalling measurements are used to collect information about the AAL2 signalling protocol, SAAL performance, and the SS7 signalling.

5.1 AAL2 signalling protocol at UNI measurement (548/224H)

5.1.1 Introduction to AAL2 signalling at UNI protocol measurementAAL2 Signalling Protocol at UNI interface Measurement provides information about control plane functions, which establish and release AAL2 connections at user network interface (UNI) for UNI signalling links.

The object identifiers are a signalling link, WBTS ID, and AAL usage. The signalling link is identified by interface, virtual path, and virtual channel identifiers of the signalling link. The measurement identifier is 548/224H.

AAL2 signalling over UNI is used to setup user plane connections over Iub. This mea-surement reports the signalling performance and different failures. See the AAL2 resource reservation measurement for the whole Iub transport reservation monitoring. This measurement reports only the signalling phase performance.

AAL2 signalling over IubThe signalling procedure between RNC and BTS and related counters are described in figure AAL2 signalling between RNC and BTS, RNC always initiates the signalling.

Figure 5 AAL2 signalling between RNC and BTS

1. The signalling is initiated by sending ERQ message from RNC towards BTS.a) Counter M548C24 COMMON is updated in RNC.

BTS (WAM) RNC

AAL2SIG CAC AAL2SIG RRCATM RMCAC

ERQ (SUGR)



ECF or possible NACK

1

2

3

Noresponse:Timeout

Requested circuit/channel notavailable #44, used if the CIDnumber is already in use.

Resource unavailable,unspecified #47, all other failuresin BTS.

DN04143903 69

RNC Counters - Transport and HW Part Signalling measurements


2. In the case AAL2 signalling request fails, failure counter is updated depending on the reason for failure that is informed from BTS to RNC.a) If the reason for failure is that the CID number is already in use in BTS, counter

M548C4 REQ_CHAN is updated.b) For all other failures (like uplink AAL2 CAC) the counter M548C5

RES_UNAVAIL is updated.3. If RNC does not receive any response within certain timeout period, it will update

related timeout counter.a) M548C12 TIMER_EXP_ERQ

AAL2 signalling over Iub, AAL2 multiplexing enabledThe signalling is basically the same for cases where AAL2 multiplexing is used. The error codes used by AXUB unit towards RNC are slightly different (see figure AAL2 sig-nalling between RNC and AXC (AAL2 multiplexing enabled in AXUB)) than those used by BTS.

Figure 6 AAL2 signalling between RNC and AXC (AAL2 multiplexing enabled in AXUB)

The signalling is basically the same for cases where AAL2 multiplexing is used in BTS. The error codes used by AXUB unit towards RNC are slightly different.

1. The signalling is initiated by sending ERQ message from RNC towards BTS.a) Counter M548C24 COMMON is updated in RNC.

2. In the case AAL2 signalling request fails, failure counter is updated depending on the reason for failure that is informed from AXC to RNC.

BTS (WAM) RNC

AAL2SIG CAC AAL2SIG RRCATM RMCAC

ERQ (SUGR)




1

2

3

Noresponse:Timeout

Requested circuit/channel not available#44, used if the CID number is already in use.

Resource unavailable, unspecified #47,all other failures.

Switching equipment congestion #42, if nointernal path to WAM can be allocated.

No route to destination #3, if routebetween WAM and AXC is not configured.

Parameter nonexistent or not implemented#99, if an unknown parameter is used.

70 DN04143903




a) If the reason for failure is that the CID number is already in use, counter M548C4 REQ_CHAN is updated.

b) If the signalling request is rejected because of unknown parameter, the counter M548C10 INFO_NOT_IMPL is updated.

c) If no internal AAL2 path from AXC to BTS can be allocated the counter M548C3 CONGESTION is updated.

d) All other failures are reported by AXC with error code #47 and the counter M548C5 RES_UNAVAIL is updated.

3. If RNC does not receive any response within certain timeout period, it will update the related timeout counter.a) M548C12 TIMER_EXP_ERQ

5.1.2 AAL2 signalling at UNI protocol measurement counters

Counter ID: M548C1 Network element name: NET_OUT

Version: 5.1 NetAct name: NET_OUT

Description: Network out of order (#38). This counter provides the number of connections terminated by Cause No. 38. It indicates that the network is not functioning correctly, and that the condition is likely to last a relatively long time and attempting the call immediately again is not likely to succeed.

Updated: All connections of the signalling link are released if the signalling link is dropped to 'unavailable' state. The counter is updated for each released connection.

Logical type: Cumulative Trigger type: Sampling interval:

Unit: Integer number Range: N/A Example values: 15


Operability class: Traffic

Related to feature: Related to standard:





Counter ID: M548C2 Network element name: TEMP_FAIL

Version: 5.1 NetAct name: TEMP_FAIL

Description: Temporary failure (#41). The number of connections terminated by Cause No. 41. Not in use.

Updated: Not updated.


Unit: Integer number Range: N/A Example values:



DN04143903 71








Counter ID: M548C3 Network element name: CONGESTION

Version: 8.3 NetAct name: CONGESTION

Description: Switching equipment congestion (#42). The number of connections terminated by Cause No. 42.

Updated: Updated when AAL2 multiplexing is used and the internal path to WAM cannot be allocated in AXC.










Counter ID: M548C4 Network element name: REQ_CHAN

Version: 5.1 NetAct name: REQ_CHAN

Description: Requested circuit/channel not available(#44).

Updated: Updated when response to AAL2 signalling request with error cause no. 44 is received by RNC.









Used from release: RN1.5 Definition updated in release: RN2.2

72 DN04143903




Counter ID: M548C5 Network element name: RES_UNAVAIL

Version: 5.1 NetAct name: RES_UNAVAIL

Description: Resource unavailable unspecified (#47). The number of connections terminated by Cause No. 47.

Updated: Updated when response to AAL2 signalling request with error cause no. 47 is received by RNC.










Counter ID: M548C6 Network element name: AAL_PARA

Version: 5.1 NetAct name: AAL_PARA

Description: AAL parameters cannot be supported (#93). Not in use.











Counter ID: M548C7 Network element name: INVALID_MSG

Version: 5.1 NetAct name: INVALID_MSG

Description: Invalid message (#95). This counter provides the number of connections terminated by Cause No. 95. This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Updated: When an AAL2 message has an invalid or unrecognized parameter.



DN04143903 73










Counter ID: M548C8 Network element name: MANDAT_INFO

Version: 5.1 NetAct name: MANDAT_INFO

Description: Mandatory information element is missing (#96). This counter provides the number of con-nections terminated by Cause No. 96. This cause indicates that the equipment sending this cause has received a message which is missing an information element which must be present in the message before it can be processed.

Updated: If a mandatory information is missing from an AAL2 message.










Counter ID: M548C9 Network element name: MSG_NOT_IMPL

Version: 5.1 NetAct name: MSG_NOT_IMPL

Description: Message type non-existent or not implemented (#97). This counter provides the number of connections terminated by Cause No. 97. This cause indicates that the equipment sending the cause has received a message with a message type it does not recognize either because the message type is not defined, or is defined but not implemented by the equipment sending this cause.

Updated: When an AAL2 message is received for an already established connection but the message is not recognized.







74 DN04143903







Counter ID: M548C10 Network element name: INFO_NOT_IMPL

Version: 5.1 NetAct name: INFO_NOT_IMPL

Description: Information element non-existent or not implemented (#99). This counter provides the number of connections terminated by Cause No. 99. It indicates that the equipment sending this cause has received a message which includes information elements/parameters not recognized because they are not defined, or are defined but not implemented by the equipment sending the cause. This cause indi-cates that the information elements/parameters were discarded. However, the information element is not required to be present in the message for the equipment sending the cause to process the message.

Updated: When a message which includes unrecognized or not implemented information ele-ments/parameters is received.










Counter ID: M548C11 Network element name: INVALID_INFO

Version: 5.1 NetAct name: INVALID_INFO

Description: Invalid information element contents (#100). Not in use.











DN04143903 75



Counter ID: M548C12 Network element name: TIMER_EXP_ERQ

Version: 8.2 NetAct name: TIMER_EXP_ERQ

Description: Recovery on ERQ timer expiry (#102). This counter provides the number of connections terminated by Cause No. 102 establish request. Estab-lish request Primitive is used by the AAL type 2 served user to initiate the establishment of a new AAL type 2 connection.

Updated: If the peer AAL type 2 signalling entity does not answer to the ERQ message within the defined timeframe. The time is 30 seconds by default, and it is configurable by PRFILE parameter 2:840 TIMER_ERQ.










Counter ID: M548C13 Network element name: TIMER_EXP_REL

Version: 8.2 NetAct name: TIMER_EXP_REL

Description: Recovery on REL_timer expiry (#102). This counter provides the number of connections terminated by Cause No. 102 release request. Release request Primitive is used by the AAL type 2 served user to initiate the clearing of an AAL type 2 connec-tion.

Updated: If the peer AAL type 2 signalling entity does not answer to the REL message within the defined timeframe. The time is 60 seconds by default, and it is configurable by PRFILE parameter 2:841 TIMER_REL.










Counter ID: M548C14 Network element name: TIMER_EXP_RES

76 DN04143903




Version: 5.1 NetAct name: TIMER_EXP_RES

Description: Recovery on RES_timer expiry (#102). This counter provides the number of connections ter-minated by Cause No. 102 reset request. Reset request is a Primitive to request the AAL type 2 signalling entity to reset a particular channel, all channels on a particular AAL type 2 path, or all channels on all AAL type 2 paths between two nodes to the "Idle" state and to indicate this to the peer AAL type 2 signalling entity.

Updated: If the peer AAL type 2 signalling entity does not answer to the RES message within the given timeframe. The time is adjustable by the user if the reset request is initiated by MML.










Counter ID: M548C15 Network element name: TIMER_EXP_BLO

Version: 5.1 NetAct name: TIMER_EXP_BLO

Description: Recovery on BLO_timer expiry (#102). This counter provides the number of connections ter-minated by Cause No. 102 block request. The block request is a Primitive to request the AAL type 2 sig-nalling entity to locally block a particular, unblocked AAL type 2 path and to indicate this to the peer AAL type 2 signalling entity.

Updated: If the peer AAL type 2 signalling entity does not answer to the BLO message within the given timeframe. The time is adjustable by the user if the blocking request is initiated by MML.










Counter ID: M548C16 Network element name: TIMER_EXP_UBL

Version: 5.1 NetAct name: TIMER_EXP_UBL

DN04143903 77



Description: Recovery on UBL_timer expiry (#102). This counter provides the number of connections ter-minated by Cause No. 102 unblock request. Unblock request is a Primitive to request the AAL type 2 sig-nalling entity to locally unblock a particular, blocked AAL type 2 path and to indicate this to the peer AAL type 2 signalling entity.

Updated: If the peer entity does not answer to the UBL message within the given timeframe. The time is adjustable by the user if the unblocking request is initiated by MML.










Counter ID: M548C17 Network element name: MSG_UNRECOG

Version: 5.1 NetAct name: MSG_UNRECOG

Description: Message with unrecognized parameter, discarded (#110). This counter provides the number of connections terminated by Cause No. 110. This cause indicates that the equipment sending the cause has discarded a received message which contains a parameter that is not recognized.

Updated: If an AAL2 signalling message is discarded because of an unrecognized parameter.










Counter ID: M548C18 Network element name: SAI_ALLOC

Version: 5.1 NetAct name: SAI_ALLOC

Description: Originating Signalling Association Identifier (OSAI) allocation failure. An internal resource reservation fails for AAL2 connection establishment. Internal (nonprotocol) error.

Updated: When internal resources for AAL2 signalling processing cannot be reserved.



78 DN04143903











Counter ID: M548C19 Network element name: CID_VERIF

Version: 5.1 NetAct name: CID_VERIF

Description: CID verification/allocation failure. Not in use.











Counter ID: M548C20 Network element name: AAL2PI_VERIF

Version: 5.1 NetAct name: AAL2PI_VERIF

Description: AAL type 2 ID verification/allocation failure. Not in use.











DN04143903 79



Counter ID: M548C21 Network element name: BINDING_ID_VERIF

Version: 5.1 NetAct name: BINDING_ID_VERIF

Description: Binding ID verification failure. Not in use.











Counter ID: M548C22 Network element name: LINK_CHAR_VERIF

Version: 5.1 NetAct name: LINK_CHAR_VERIF

Description: Required traffic characterization unavailable. Not in use.











Counter ID: M548C23 Network element name: ADJ_NODE_NOT_AVAIL

Version: 5.1 NetAct name: ADJ_NODE_NOT_AVAIL

Description: Adjacent node not available. The connection establishment is rejected because the signal-ling relation to the adjacent AAL type 2 node was not available. Internal (non-protocol) error.

Updated: When sending the ERQ message does not succeed because the signalling link is unavailable, for example, because of the wrong state of the link.



80 DN04143903











Counter ID: M548C24 Network element name: COMMON

Version: 5.1 NetAct name: COMMON

Description: The number of connection events started in the AAL2 signalling.

Updated: When ERQ message sending request is received.










Counter ID: M548C25 Network element name: OUT_ERQ_ATTEMPT

Version: 3.0 NetAct name: OUT_ERQ_ATTEMPT

Description: The number of outgoing AAL2 connection establishment requests.

Updated: When AAL2 Establishment Request (ERQ) message is sent.










Counter ID: M548C26 Network element name: OUT_ERQ_SUCCESS

DN04143903 81



Version: 3.0 NetAct name: OUT_ERQ_SUCCESS

Description: The number of successful outgoing AAL2 connection establishment.

Updated: When AAL2 Establishment Confirm (ECF) message is received.










Counter ID: M548C27 Network element name: IN_ERQ_ATTEMPT

Version: 3.0 NetAct name: IN_ERQ_ATTEMPT

Description: The number of incoming AAL2 connection establishment requests.

Updated: When AAL2 Establishment Request (ERQ) message is received.










Counter ID: M548C28 Network element name: IN_ERQ_SUCCESS

Version: 3.0 NetAct name: IN_ERQ_SUCCESS

Description: The number of successful incoming AAL2 connection establishment.

Updated: When AAL2 Establishment Confirm (ECF) message is sent.








82 DN04143903






Counter ID: M548C29 Network element name: OUT_MOD_ATTEMPT

Version: 3.0 NetAct name: OUT_MOD_ATTEMPT

Description: The number of outgoing AAL2 connection modification requests.

Updated: When AAL2 Modification Request (MOD) message is sent.










Counter ID: M548C30 Network element name: OUT_MOD_SUCCESS

Version: 3.0 NetAct name: OUT_MOD_SUCCESS

Description: The number of successful outgoing AAL2 connection modifications.

Updated: When AAL2 Modification Acknowledge (MOA) message is received.










Counter ID: M548C31 Network element name: IN_MOD_ATTEMPT

Version: 3.0 NetAct name: IN_MOD_ATTEMPT

Description: The number of incoming AAL2 connection modification requests.

Updated: When AAL2 Modification Request (MOD) message is received.



DN04143903 83










Counter ID: M548C32 Network element name: IN_MOD_SUCCESS

Version: 3.0 NetAct name: IN_MOD_SUCCESS

Description: The number of successful incoming AAL2 connection modifications.

Updated: When AAL2 Modification Acknowledge (MOA) message is sent.










Counter ID: M548C33 Network element name: MOD_FAIL_RES

Version: 3.0 NetAct name: MOD_FAIL_RES

Description: The number of failed AAL2 connection modifications because of resource unavailable.

Updated: When AAL2 modification fails due to unavailable internal ATM resource.










Counter ID: M548C34 Network element name: MOD_FAIL_INT

84 DN04143903




Version: 3.0 NetAct name: MOD_FAIL_INT

Description: The number of failed AAL2 connection modifications because of internal error.

Updated: When AAL2 modification fails due to internal error.










Counter ID: M548C35 Network element name: MOD_FAIL_COLL

Version: 3.0 NetAct name: MOD_FAIL_COLL

Description: The number of failed AAL2 connection modifications because of collision.

Updated: When AAL2 modification fails due to collision.










Counter ID: M548C36 Network element name: MOD_FAIL_REM

Version: 3.0 NetAct name: MOD_FAIL_REM

Description: The number of failed AAL2 connection modifications because of failed remote.

Updated: When AAL2 modification fails due to remote failed.








DN04143903 85



5.2 AAL2 signalling at NNI measurement (552/228H)

5.2.1 Introduction to AAL2 signalling at NNI measurementAAL2 Signalling at NNI interface Measurement provides information about control plane functions, which establish and release AAL2 connections at Network Node Interface (NNI) for signalling points.

The object is a signalling point that is identified with signalling network code and signal-ling point code (SPC). See Terminology for the available signalling network codes. The measurement identifier is 552/228H.

AAL2 signalling over NNI is used to setup user plane connections over Iur and Iu-CS interfaces. This measurement reports the signalling performance and different failures. See the AAL2 resource reservation measurement for the whole Iu interface transport reservation monitoring per user plane ATM VCC. This measurement reports only the signalling phase performance. The AAL2 signalling procedure between two RNC and related counters are described in figure AAL2 signalling between two RNC over Iur inter-face.



Counter ID: M548C37 Network element name: TIMER_EXP_MOD

Version: 3.0 NetAct name: TIMER_EXP_MOD

Description: The number of failed AAL2 connection modifications because timer waiting for Modify Acknowledge message expires.

Updated: When AAL2 modification fails because timer waiting for Modify Acknowledge message expires.










86 DN04143903




Figure 7 AAL2 signalling between two RNCs over Iur interface

1. The signalling is initiated by sending ERQ message to DRNC.a) Counter M552C24 COMMON_AT_NNI is updated in SRNC.

2. The DRNC arranges its resources for new AAL2 connection and if the reservation is successful ECF message is sent to SRNC.

3. In the case DRNC rejects the AAL2 connection setup, following counters will be updated.a) M552C3 CONGESTION_AT_NNI is updated in both DRNC and SRNC for every

failure.b) In addition, M552C29 RES_MAN_OVERLOAD_AT_NNI is updated in DRNC if

the reason for rejection is that there is no WAC ticket available (DRNC internal overload control).

c) In addition, M552C21 BINDING_ID_VERIF_AT_NNI is updated in DRNC if the reason for rejection is that there is no binding ID available.

d) In addition, M552C18 SAI_ALLOC_AT_NNI is updated in DRNC if the reason for rejection is that there is no AAL2 protocol hand available (DRNC internal fail-ure).

e) In addition, M552C2 TEMP_FAIL_AT_NNI is updated in DRNC if the AAL2 sig-nalling request fails in RNC application layer (DRNC internal failure).

DRNC SRNC

AAL2SIG AAL2SIG RRCATM RM

ERQ (SUGR)

DRNC transportresource reservation

SRNC internal transportresource reservation


Noresponse:Timeout

Switching equipment congestion #42, if IDbinding fails or there are no resources.

Transport resource requestfrom RRC (after Iub complete)

1

2

4

If the rejection was caused by no WACticket available in DRNC.

If the rejection was caused since there is nobinding ID in DRNC available.

3

No AAL2 connection protocol hand(DRNC internal failure).

If the AAL2 signalling fails in RNCapplication layer (DRNC internal failure).

M552C3

M552C29

M552C21

M552C18

M552C2

M552C3

RNSAP asks DRNC to establish Iubbranch before the Iur branch isestablished

DN04143903 87



4. If RNC does not receive any response within a certain timeout period, it will update the related timeout counter.a) M552C12 TIMER_EXP_ERQ_AT_NNI

g Counters M552C2, M552C25, M552C26, M552C27 and M552C28 are not relevant in RNC because they are related to functionality supported only by MGW using the same ATM switching platform.

5.2.2 AAL2 signalling at NNI measurement counters

Counter ID: M552C1 Network element name: NET_OUT_AT_NNI

Version: 3.1 NetAct name: NET_OUT_AT_NNI

Description: Network out of order (#38).

Updated: Not updated in NNI.




Operability class:






Counter ID: M552C3 Network element name: CONGESTION_AT_NNI

Version: 6.2 NetAct name: CONGESTION_AT_NNI

Description: Switching equipment congestion (#42). This counter provides the number of connections terminated by Cause No. 42. The cause code indicates that the switching equipment that generates this cause is experiencing a period of high traffic.

Updated: The counter is updated in MGW nodal function cases if the connection is requested to be released by Cause No. 42.In RNC and other cases of MGW, it is updated if the reservation of connection resources does not succeed for the incoming connection establishment. If Window Access Control (WAC) gate access token is rejected for the connection establishment, counter M552C29 RES_MAN_OVERLOAD_AT_NNI is also updated. If the verification of binding id does not succeed, counter M552C21 BINDING_ID_VERIF_AT_NNI is also updated.



88 DN04143903





M552C21: BINDING_ID_VERIF_AT_NNIM552C29: RES_MAN_OVERLOAD_AT_NNI

Operability class:






Counter ID: M552C4 Network element name: REQ_CHAN_AT_NNI

Version: 6.2 NetAct name: REQ_CHAN_AT_NNI

Description: This counter provides the number of connections terminated by cause No. 44. The cause code indicates that the AAL2 path state is inconsistent between network elements. e.g. AAL2 path is blocked in DRNC or MGW while the adjacent node's is unblocked.

Updated: The counter is updated in AAL2 signalling cases if the connection is requested to be released by Cause No.44. For example, if the path selected in ALCAP:ERQ is blocked, ATM interface related with the channel in ALCAP:ERQ is in non-ENABLED operational state or the interface/VP/VC related with the channel in ALCAP:ERQ is in non-UNLOCKED administrative state.




Operability class:






Counter ID: M552C5 Network element name: RES_UNAVAIL_AT_NNI

Version: 3.1 NetAct name: RES_UNAVAIL_AT_NNI

Description: Resource unavailable unspecified (#47). This counter provides the number of connections terminated by Cause No. 47. This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

Updated: When the requested AAL2 path is blocked and the checking of the path does not succeed, or when the requested AAL2 path is blocked and unblocking does not succeed.




DN04143903 89



Operability class:






Counter ID: M552C6 Network element name: AAL_PARA_AT_NNI

Version: 3.1 NetAct name: AAL_PARA_AT_NNI

Description: AAL parameters cannot be supported (#93). Not in use.





Operability class:






Counter ID: M552C7 Network element name: INVALID_MSG_AT_NNI

Version: 3.1 NetAct name: INVALID_MSG_AT_NNI

Description: Invalid message (#95). This counter provides the number of connections terminated by Cause No. 95. This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

Updated: When an AAL2 message has invalid or unrecognized parameters.




Operability class:






90 DN04143903




Counter ID: M552C8 Network element name: MANDAT_INFO_AT_NNI

Version: 3.1 NetAct name: MANDAT_INFO_AT_NNI

Description: Mandatory information element is missing (#96). This counter provides the number of con-nections terminated by Cause No. 96. This cause indicates that the equipment sending the cause has received a message which is missing an information element which must be present in the message before the message can be processed.

Updated: When a mandatory information element is missing from an AAL2 message.




Operability class:






Counter ID: M552C9 Network element name: MSG_NOT_IMPL_AT_NNI

Version: 3.1 NetAct name: MSG_NOT_IMPL_AT_NNI

Description: Message type non-existent or not implemented (#97). This counter provides the number of connections terminated by Cause No. 97. The cause indicates that the equipment sending the cause has received a message with a message type which it does not recognise either because it is not defined, or is defined but not implemented by the equipment.

Updated: When an AAL2 message is received for an already established connection, but is not recogn-ised.




Operability class:






Counter ID: M552C10 Network element name: INFO_NOT_IMPL_AT_NNI

Version: 3.1 NetAct name: INFO_NOT_IMPL_AT_NNI

DN04143903 91



Description: inated by Cause No. 99. This indicates that the equipment sending this cause has received a message which includes information elements/parameters not recognized because the information element identifiers/parameter names are not defined, or are defined but not implemented by the equip-ment sending the cause. This cause indicates that the information elements/parameters were discarded. However, the information element is not required in the message for the equipment sending the cause to process the message.

Updated: When a message which includes unrecognized not implemented information elements/param-eters is received.




Operability class:






Counter ID: M552C11 Network element name: INVALID_INFO_AT_NNI

Version: 3.1 NetAct name: INVALID_INFO_AT_NNI

Description: Invalid information element contents (#100). Not in use.





Operability class:






Counter ID: M552C12 Network element name: TIMER_EXP_ERQ_AT_NNI

Version: 6.2 NetAct name: TIMER_EXP_ERQ_AT_NNI

Description: Recovery on ERQ_timer expiry (#102). This counter provides the number of connections terminated by Cause No. 102 establish request. Estab-lish request Primitive is used by the AAL type 2 served user to start the establishment of a new AAL type 2 connection.

92 DN04143903




Updated: If the peer AAL type 2 signalling entity does not answer to an ERQ message within the defined timeframe. The time is 30 seconds by default, and it is configurable by PRFILE parameter 2:840 TIMER_ERQ.




Operability class:






Counter ID: M552C13 Network element name: TIMER_EXP_REL_AT_NNI

Version: 6.2 NetAct name: TIMER_EXP_REL_AT_NNI

Description: Recovery on REL_timer expiry (#102). This counter provides the number of connections terminated by Cause No. 102 release request. The Release request Primitive is used by the AAL type 2 served user to start the clearing of an AAL type 2 connection.

Updated: If the peer AAL type 2 signalling entity does not answer to a REL message within the defined timeframe. The time is 60 seconds by default, and it is configurable by PRFILE parameter 2:841 TIMER_REL.




Operability class:






Counter ID: M552C14 Network element name: TIMER_EXP_RES_AT_NNI

Version: 3.1 NetAct name: TIMER_EXP_RES_AT_NNI

Description: Recovery on RES_timer expiry (#102). This counter provides the number of connections ter-minated by Cause No. 102 reset request. Reset request is a Primitive to request the AAL type 2 signalling entity to reset a particular channel, all channels on a particular AAL type 2 path, or all channels on all AAL type 2 paths between two nodes to the "Idle" state and to indicate this to the peer AAL type 2 signalling entity.

DN04143903 93



Updated: If the peer AAL type 2 signalling entity does not answer to a RES message within the given timeframe. The time is adjustable by the user if the reset request is initiated by MML.




Operability class:






Counter ID: M552C15 Network element name: TIMER_EXP_BLO_AT_NNI

Version: 3.1 NetAct name: TIMER_EXP_BLO_AT_NNI

Description: Recovery on BLO_timer expiry (#102). This counter provides the number of connections ter-minated by Cause No. 102 block request. Block request is a Primitive to request the AAL type 2 signalling entity to locally block a particular, unblocked AAL type 2 path and to indicate this to the peer AAL type 2 signalling entity.

Updated: If the peer AAL type 2 signalling entity does not answer to a BLO message within the given timeframe. The time is adjustable by the user if the blocking request is initiated by MML.




Operability class:






Counter ID: M552C16 Network element name: TIMER_EXP_UBL_AT_NNI

Version: 3.1 NetAct name: TIMER_EXP_UBL_AT_NNI

Description: Recovery on UBL_timer expiry (#102). This counter provides the number of connections ter-minated by Cause No. 102 unblock request. Unblock request is a Primitive to request the AAL type 2 sig-nalling entity to locally unblock a particular, blocked AAL type 2 path and to indicate this to the peer AAL type 2 signalling entity.

Updated: If the peer entity does not answer to a UBL message within the given timeframe. The time is adjustable by the user if the unblocking request is initiated by MML.


94 DN04143903






Operability class:






Counter ID: M552C17 Network element name: MSG_UNRECOG_AT_NNI

Version: 3.1 NetAct name: MSG_UNRECOG_AT_NNI

Description: Message with an unrecognised parameter, discarded (#110). This counter provides the number of connections terminated by Cause No. 110. This cause indicates that the equipment sending this cause has discarded a received message which includes a parameter that is not recognised.

Updated: When an AAL2 signalling message is discarded because of an unrecognised parameter.




Operability class:






Counter ID: M552C18 Network element name: SAI_ALLOC_AT_NNI

Version: 3.1 NetAct name: SAI_ALLOC_AT_NNI

Description: Originating Signalling Association Identifier (OSAI) allocation failure. An internal resource reservation fails for AAL2 connection establishment. Internal (nonprotocol) error.

Updated: When internal resources for AAL2 signalling processing cannot be reserved.




Operability class:




DN04143903 95





Counter ID: M552C19 Network element name: CID_VERIF_AT_NNI

Version: 3.1 NetAct name: CID_VERIF_AT_NNI

Description: CID verification/allocation failure. Not in use.





Operability class:






Counter ID: M552C20 Network element name: AAL2PI_VERIF_AT_NNI

Version: 3.1 NetAct name: AAL2PI_VERIF_AT_NNI

Description: AAL type 2 Id verification/allocation failure. Not in use.





Operability class:






Counter ID: M552C21 Network element name: BINDING_ID_VERIF_AT_NNI

Version: 3.1 NetAct name: BINDING_ID_VERIF_AT_NNI

Description: Binding id verification failure. The requested binding identifier was not available in the des-tination AAL type 2 node. Internal (non-protocol) error.

96 DN04143903




Updated: If the verification of binding id does not succeed; the error code counter M552C3 CONGES-TION is also updated.




Operability class:






Counter ID: M552C22 Network element name: LINK_CHAR_VERIF_AT_NNI

Version: 3.1 NetAct name: LINK_CHAR_VERIF_AT_NNI

Description: Required traffic characterizations unavailable. Not in use.





Operability class:






Counter ID: M552C23 Network element name: ADJ_NODE_NOT_AVAIL_AT_NNI

Version: 3.1 NetAct name: ADJ_NODE_NOT_AVAIL_AT_NNI

Description: Adjacent node not available.





Operability class:




DN04143903 97





Counter ID: M552C24 Network element name: COMMON_AT_NNI

Version: 3.1 NetAct name: COMMON_AT_NNI

Description: The number of connection events started in the AAL2 signalling.

Updated: The counter is updated when an AAL2 connection establishment request ERQ (Establishment Request) message is received (incoming). The counter is updated also when an ERQ message sending request is received (outgoing).




Operability class:






Counter ID: M552C29 Network element name: RES_MAN_OVERLOAD_AT_NNI

Version: 3.1 NetAct name: RES_MAN_OVERLOAD_AT_NNI

Description: Resource manager overload. Connection establishment is rejected because resource manager overload protection is activated in the destination AAL type 2 node.

Updated: When a Window Access Control (WAC) gate access token is rejected for connection establish-ment. The error code counter M552C3 CONGESTION_AT_NNI is also updated.




Operability class:






Counter ID: M552C30 Network element name: OUT_ERQ_ATTEMPT_AT_NNI

Version: 3.1 NetAct name: OUT_ERQ_ATTEMPT_AT_NNI

98 DN04143903




Description: The number of outgoing AAL2 connection establishment requests.

Updated: When an AAL2 Establishment Request (ERQ) message is sent.









Used from release: RN4.0/U4.0 Definition updated in release:

Counter ID: M552C31 Network element name: OUT_ERQ_SUCCESS_AT_NNI

Version: 3.1 NetAct name: OUT_ERQ_SUCCESS_AT_NNI

Description: The number of successful outgoing AAL2 connection establishments.

Updated: When an AAL2 Establishment Confirm (ECF) message is received.










Counter ID: M552C32 Network element name: IN_ERQ_ATTEMPT_AT_NNI

Version: 3.1 NetAct name: IN_ERQ_ATTEMPT_AT_NNI

Description: The number of incoming AAL2 connection establishment requests.

Updated: When an AAL2 Establishment Request (ERQ) message is received.









DN04143903 99




Counter ID: M552C33 Network element name: IN_ERQ_SUCCESS_AT_NNI

Version: 3.1 NetAct name: IN_ERQ_SUCCESS_AT_NNI

Description: The number of successful incoming AAL2 connection establishments.

Updated: When an AAL2 Establishment Confirm (ECF) message is sent.










Counter ID: M552C34 Network element name: OUT_MOD_ATTEMPT_AT_NNI

Version: 3.1 NetAct name: OUT_MOD_ATTEMPT_AT_NNI

Description: The number of outgoing AAL2 connection modification requests.

Updated: When an AAL2 Modification Request (MOD) message is sent.










Counter ID: M552C35 Network element name: OUT_MOD_SUCCESS_AT_NNI

Version: 3.1 NetAct name: OUT_MOD_SUCCESS_AT_NNI

Description: The number of successful outgoing AAL2 connection modifications.

Updated: When an AAL2 Modification Acknowledge (MOA) message is received.




100 DN04143903










Counter ID: M552C36 Network element name: IN_MOD_ATTEMPT_AT_NNI

Version: 3.1 NetAct name: IN_MOD_ATTEMPT_AT_NNI

Description: The number of incoming AAL2 connection modification requests.

Updated: When an AAL2 Modification Request (MOD) message is received.










Counter ID: M552C37 Network element name: IN_MOD_SUCCESS_AT_NNI

Version: 3.1 NetAct name: IN_MOD_SUCCESS_AT_NNI

Description: The number of successful incoming AAL2 connection modifications.

Updated: When an AAL2 Modification Acknowledge (MOA) message is sent.










Counter ID: M552C38 Network element name: MOD_FAIL_RES_AT_NNI

Version: 3.1 NetAct name: MOD_FAIL_RES_AT_NNI

DN04143903 101



Description: The number of failed AAL2 connection modifications because of an unavailable resource.

Updated: When an AAL2 modification fails due to an unavailable internal ATM resource.










Counter ID: M552C39 Network element name: MOD_FAIL_INT_AT_NNI

Version: 3.1 NetAct name: MOD_FAIL_INT_AT_NNI

Description: The number of failed AAL2 connection modifications because of an internal error.

Updated: When an AAL2 modification fails due to an internal error.










Counter ID: M552C40 Network element name: MOD_FAIL_COLL_AT_NNI

Version: 3.1 NetAct name: MOD_FAIL_COLL_AT_NNI

Description: The number of failed ALL2 connection modifications because of a collision.

Updated: When AAL2 modification fails due to a collision.









102 DN04143903




5.3 SAAL signalling protocol at UNI measurement (546/222H)The SAAL signalling at UNI measurement provides information about the service-specific coordination function (SSCF), the service-specific connection-oriented protocol (SSCOP) errors, the AAL5 common part convergence sublayer (CPCS), and the seg-mentation and reassembly sublayer (SAR) for UNI signalling links.

On SSCF, the amount of radio protocols signalling data exchanged between layer 3 and transport layer, is measured for both transmitter and receiver sides. The SSCOP errors provide performance data about the end-to-end secured connection. On the AAL5 CPCS and SAR sublayers, the amount of radio transmitter and receive side signalling


Counter ID: M552C41 Network element name: MOD_FAIL_REM_AT_NNI

Version: 3.1 NetAct name: MOD_FAIL_REM_AT_NNI

Description: The number of failed AAL2 connection modifications because of a failed remote.

Updated: When an AAL2 modification fails due to a failed remote.










Counter ID: M552C42 Network element name: TIMER_EXP_MOD_AT_NNI

Version: 3.1 NetAct name: TIMER_EXP_MOD_AT_NNI

Description: The number of failed AAL2 connection modifications because of a timer expiring.

Updated: When an AAL2 modification fails because a timer waiting for a Modification Acknowledge (MOD) message expires.










DN04143903 103



data to and from the ATM Layer, as well as the errors during radio transmitter and receive side, are measured.

The object identifiers are a signalling link, WBTS ID, and AAL usage. The signalling link is identified by interface, virtual path and virtual channel identifiers of UNI signalling link. The link type can be AAL2SL, CNBAP or DNBAP.

The measurement identifier is 546/222H.

Counter ID: M546C0 Network element name: MSUS_RECEIVED

Version: 5.1 NetAct name: MSUS_RECEIVED

Description: The number of received signalling datamessages from Layer 3. The amount of assured sig-nalling data (AAL-data) messages received from the users of Layer 3 (NBAP or AAL2 signalling) via AAL-SAP of SSCF-UNI.

Updated: When a user of Layer 3 (NBAP or AAL2 signalling protocol) requests the sending of signalling data, for example, when AAL2 signalling protocol establishes a radio access bearer over Iub.










Counter ID: M546C1 Network element name: OCTETS_RECEIVED

Version: 5.2 NetAct name: OCTETS_RECEIVED

Description: The number of received octets from Layer 3. The number of the assured signalling data (AAL-data) message octets received from the users of Layer 3 (NBAP or AAL2 signalling) via AAL-SAP of SSCF-UNI.

Updated: When a user of layer 3 (NBAP or AAL2 signalling protocol) requests the sending of signalling data, for example, when AAL2 signalling protocol establishes a radio access bearer over Iub.


Unit: byte Range: N/A Example values: 15








104 DN04143903




Counter ID: M546C2 Network element name: SIG_COMMANDS_RECEIVED

Version: 5.1 NetAct name: SIG_COMMANDS_RECEIVED

Description: The number of received signalling command messages from Layer 3. The signalling commands are channel activation (AAL_establish_request) and channel release (AAL_release_request). The counter indicates the reliability of the link used by AAL2.

Updated: When a user of Layer 3 requests the sending of a signalling command, for example, when a SAAL UNI link is created and requested to be activated.










Counter ID: M546C3 Network element name: MSUS_TRANSMITTED

Version: 5.1 NetAct name: MSUS_TRANSMITTED

Description: The number of transmitted signalling data messages from Layer 3. The number of transmit-ted signalling data (AAL_data_indication) messages sent to Layer 3 by the user of the counterpart Layer 3.

Updated: When a signalling data message is received to transmit to the user of Layer 3, for example, when a peer AAL type 2 service endpoint confirms the establishing of a radio access bearer setup over Iub.










Counter ID: M546C4 Network element name: OCTETS_TRANSMITTED

Version: 5.2 NetAct name: OCTETS_TRANSMITTED

DN04143903 105



Description: The number of transmitted octets from Layer 3. The number of transmitted signalling data (AAL_data_indication) message octets sent to Layer 3 by the user of the counterpart Layer 3.

Updated: When a signalling data message is received to transmit to the user of Layer 3, for example, when a peer AAL type 2 service endpoint confirms the establishing of a radio access bearer setup over Iub.










Counter ID: M546C5 Network element name: SIG_NOTICES_TRANSMITTED

Version: 5.1 NetAct name: SIG_NOTICES_TRANSMITTED

Description: The number of transmitted signalling command messages from Layer 3. The signalling commands are channel activation confirmation (AAL_establish_confirm), channel activation indication (AAL_establish_indication), channel release confirmation (AAL_release_confirm) and channel release indication (AAL_release_indication). These commands are sent by the user of the counterpart Layer 3.

Updated: When a signalling command is received to transmit to the user of Layer 3, for example, when confirmation for the UNI signalling link activation is received.










Counter ID: M546C6 Network element name: ERROR_CODE_A

Version: 5.1 NetAct name: ERROR_CODE_A

Description: Receipt of unsolicited SSCOP SequencedData (SD PDU). SD PDU is received in a SSCOP connection state where it should not be received. SD PDU is used to transfer, across an SSCOP connec-tion, sequentially numbered PDUs containing information fields provided by the SSCOP user.

106 DN04143903




Updated: SD PDU is received in a SSCOP connection state where it should not be received. For example, the connection between SSCOP layers is not available but a SD PDU is still received for the connection.










Counter ID: M546C7 Network element name: ERROR_CODE_B

Version: 5.1 NetAct name: ERROR_CODE_B

Description: Receipt of unsolicited SSCOP Begin (BGN PDU). BGN PDU is received in a SSCOP con-nection state where it should not be received. SSCOP Begin (BGN PDU) is used to establish an SSCOP connection between two peer entities. The BGN PDU requests the clearing of the peer's transmitter and receiver buffers, and the initialization of the peer's transmitter and receiver state variables.

Updated: BGN PDU is received in a SSCOP connection state where it should not be received. For example, the RS PDU or ER PDU is sent to the peer node but a BGN PDU is received instead of acknowl-edgements (RSAK PDU or ERAK PDU).










Counter ID: M546C8 Network element name: ERROR_CODE_C

Version: 5.1 NetAct name: ERROR_CODE_C

Description: Receipt of unsolicited SSCOP BeginAcknowledge (BGAK PDU). BGAK PDU is received in a SSCOP connection state where it should not be received. Begin Acknowledge (BGAK PDU) is used to confirm the establishment of an SSCOP connection between two peer entities.

Updated: BGAK PDU is received in a SSCOP connection state where it should not be received. For example, the BGAK PDU is received from a peer node, although SSCOP has not requested connection establishment.

DN04143903 107












Counter ID: M546C9 Network element name: ERROR_CODE_D

Version: 5.1 NetAct name: ERROR_CODE_D

Description: Receipt of unsolicited SSCOP BeginReject (BGREJ PDU). BGREJ PDU is received in a SSCOP connection state where it should not be received. BGREJ PDU is used to reject the connection request of the peer SSCOP entity.

Updated: BGREJ PDU is received in a SSCOP connection state where it should not be received. For example, BGREJ PDU is received from a peer node although the connection between SSCOP layers is not established.










Counter ID: M546C10 Network element name: ERROR_CODE_E

Version: 5.1 NetAct name: ERROR_CODE_E

Description: Receipt of unsolicited SSCOP End (ENDPDU). END PDU is received in a SSCOP connec-tion state where it should not be received. END PDU is used to release an SSCOP connection between two peer entities.

Updated: END PDU is received in a SSCOP connection state where it should not be received. For example, END PDU is received for the unavailable connection between SSCOP layers.





108 DN04143903









Counter ID: M546C11 Network element name: ERROR_CODE_F

Version: 5.1 NetAct name: ERROR_CODE_F

Description: Receipt of unsolicited SSCOP End Acknowledge (ENDAK PDU). ENDAK PDU is received in a SSCOP connection state where it should not be received. ENDAK PDU is used to confirm the release of an SSCOP connection.

Updated: ENDAK PDU is received in a SSCOP connection state where it should not be received. For example, ENDAK PDU is received although SSCOP has not requested the connection release.










Counter ID: M546C12 Network element name: ERROR_CODE_G

Version: 5.1 NetAct name: ERROR_CODE_G

Description: Receipt of unsolicited SSCOP Polling (POLL PDU). POLL PDU is received in a SSCOP con-nection state where it should not be received. POLL PDU is used to request, across an SSCOP connec-tion, status information about the peer SSCOP entity.

Updated: POLL PDU is received in a SSCOP connection state where it should not be received. For example, POLL PDU is received when the connection between SSCOP layers is not established.









DN04143903 109




Counter ID: M546C13 Network element name: ERROR_CODE_H

Version: 5.1 NetAct name: ERROR_CODE_H

Description: Receipt of unsolicited SSCOP Status(STAT PDU). STAT PDU is received in a SSCOP con-nection state where it should not be received. STAT PDU is used to respond to a status request (POLL PDU) received from a peer SSCOP entity. It contains information regarding the reception status of SD PDUs, credit information for the peer transmitter, and the sequence number [N(PS)] of the POLL PDU to which it responds.

Updated: STAT PDU is received in a SSCOP connection state where it should not be received. For example, STAT PDU is received when the connection between SSCOP layers is not established.










Counter ID: M546C14 Network element name: ERROR_CODE_I

Version: 5.1 NetAct name: ERROR_CODE_I

Description: Receipt of unsolicited SSCOP Unsolicited Status Response (USTAT PDU). USTAT PDU is received in a SSCOP connection state where it should not be received. USTAT PDU is used to respond to the detection of one or more new missing SD PDUs, based on the examination of the sequence num-bering of the SD PDU. It contains information regarding the reception status of SD PDUs and credit infor-mation for the peer transmitter.

Updated: USTAT PDU is received in a SSCOP connection state where it should not be received. For example, USTAT PDU is received when the connection between SSCOP layers is not established.










110 DN04143903




Counter ID: M546C15 Network element name: ERROR_CODE_J

Version: 5.1 NetAct name: ERROR_CODE_J

Description: Receipt of unsolicited SSCOP Re-synchronization(RS PDU). RS PDU is received in a SSCOP connection state where it should not be received. RS PDU is used to re-synchronize the buffers and data transfer state variables.

Updated: RS PDU is received in a SSCOP connection state where it should not be received, for example, when the connection between SSCOP layers is not established.










Counter ID: M546C16 Network element name: ERROR_CODE_K

Version: 5.1 NetAct name: ERROR_CODE_K

Description: Receipt of unsolicited SSCOP Re-synchronization Acknowledge (RSAK PDU). RSAK PDU is received in a SSCOP connection state where it should not be received. RSAK PDU is used to acknowl-edge the acceptance of a re-synchronisation requested by the peer SSCOP entity.

Updated: RSAK PDU is received in a SSCOP connection state where it should not be received, for example, when the connection between SSCOP layers is not established.










Counter ID: M546C17 Network element name: ERROR_CODE_L

Version: 5.1 NetAct name: ERROR_CODE_L

DN04143903 111



Description: Receipt of unsolicited SSCOP Error Recovery (ER PDU). ER PDU is received in a SSCOP connection state where it should not be received. ER PDU is used to recover from protocol errors.

Updated: ER PDU is received in a SSCOP connection state where it should not be received, for example, when the connection between SSCOP layers is not established.










Counter ID: M546C18 Network element name: ERROR_CODE_M

Version: 5.1 NetAct name: ERROR_CODE_M

Description: Receipt of unsolicited SSCOP Error Recovery Acknowledge (ERAK PDU). ERAK PDU is received in a SSCOP connection state where it should not be received. ERAK PDU is used to acknowl-edge the recovery from protocol error.

Updated: ERAK PDU is received in a SSCOP connection state where it should not be received, for example, when the connection between SSCOP layers is not established.










Counter ID: M546C19 Network element name: ERROR_CODE_O

Version: 5.1 NetAct name: ERROR_CODE_O

Description: Unsuccessful retransmission. The number of transmissions of BGN, END, ER, or RS PDUs (SSCOP state variable VT(CC)) has reached the maximum value of retransmissions (SSCOP parameter MaxCC). When a BGN, END, ER, or RS PDU is sent, a timer is set (TimerCC) to wait for the acknowledge and the VT(CC) variable is set to 1. If the acknowledgement is not received, the PDU is retransmitted, TimerCC is set again, and VT(CC) is increased. If VT(CC) reaches the value of MaxCC, the PDU is no longer retransmitted. The default value for TimerCC is 1 second, and 4 seconds for MaxCC.

Updated: On every occasion of an unsuccessful PDU retransmission cycle.

112 DN04143903













Counter ID: M546C20 Network element name: ERROR_CODE_P

Version: 5.1 NetAct name: ERROR_CODE_P

Description: Timer_NO-RESPONSE expiry. The SSCOP connection has been released. The Timer_NO-RESPONSE is set when POLL PDU is sent to a peer SSCOP entity. When the peer acknowledges it with STAT PDU, the Timer_NO-RESPONSE is reset. If the peer does not send STAT PDU and the Timer_NO-RESPONSE expires, the SSCOP connection is released by SSCOP.

Updated: If the peer does not acknowledge POLL PDU with STAT PDU in the defined timeframe.










Counter ID: M546C21 Network element name: ERROR_CODE_Q

Version: 5.1 NetAct name: ERROR_CODE_Q

Description: SD or POLL, N(S) error. SD or POLL PDU sequence number (N(S)) error. SD or POLL PDU is received and the N(S) parameter is not valid. Either SD PDU with N(S) that is in the SSCOP receive buffer is received, or POLL PDU contains N(S) that is greater than the highest expected sequence number (SSCOP variable VR(H)).

Updated: When SD or POLL PDU is received and the N(S) parameter is not valid.





DN04143903 113








Counter ID: M546C22 Network element name: ERROR_CODE_R

Version: 5.1 NetAct name: ERROR_CODE_R

Description: STAT N(PS) error. STAT PDU is received for a POLL PDU that has not been sent. When POLL PDU is sent, the polling sequence number (SSCOP variable N(PS)) is increased and sent in the PDU. The peer SSCOP entity copies this value from POLL PDU into the appropriate STAT PDU. This error code is increased when STAT PDU with N(PS) that has not been sent in any POLL PDU is received.

Updated: This error code is increased when STAT PDU with N(PS) that has not been sent in any POLL PDU is received.










Counter ID: M546C23 Network element name: ERROR_CODE_S

Version: 5.1 NetAct name: ERROR_CODE_S

Description: USTAT N(R) or list elements error. STAT PDU is received with invalid data. The N(R) param-eter in STAT PDU tells the sequence number of SD PDU that the sender of STAT PDU is waiting to be received next. This error counter is increased when the N(R) is greater than the next sequence number to be sent (SSCOP variable VT(S)), or the acknowledgement for that SD PDU has already been received in an earlier STAT or USTAT PDU. The list elements in STAT PDU are used to request retransmission of SD PDUs. This error counter is increased, if such SD PDUs that are not sent or have been acknowl-edged to be received by the peer SSCOP entity, are requested to be retransmitted.

Updated: When the N(R) is greater than the next sequence number to be sent (SSCOP variable VT(S)), or the acknowledgement for that SD PDU has already been received in an earlier STAT or USTAT PDU.






114 DN04143903








Counter ID: M546C24 Network element name: ERROR_CODE_T

Version: 5.1 NetAct name: ERROR_CODE_T

Description: USTAT (N(R) or list elements error. USTAT PDU is received with invalid data. The N(R) parameter in STAT PDU tells the sequence number of SD PDU that the sender of STAT PDU is waiting to be received next. This error counter is increased when the N(R) is greater than the next sequence number to be sent (SSCOP variable VT(S)), or the acknowledgement for that SD PDU has already been received in an earlier STAT or USTAT PDU. The list elements in USTAT PDU are used to request retransmission of SD PDUs. This error counter is increased, if such SD PDUs that are not sent or have been acknowledged to be received by the peer SSCOP entity, are requested to be retransmitted.

Updated: When the N(R) is greater than the next sequence number to be sent (SSCOP variable VT(S)), or the acknowledgement for that SD PDU has already been received in an earlier STAT or USTAT PDU.










Counter ID: M546C25 Network element name: ERROR_CODE_U

Version: 5.1 NetAct name: ERROR_CODE_U

Description: PDU length violation. If the length of a PDU is not between the minimum and maximum length of a PDU, or if the PDU length is not 32-bit-aligned.

Updated: If SSCOP detects that the PDU to be sent has incorrect data length.









DN04143903 115




Counter ID: M546C26 Network element name: ERROR_CODE_V

Version: 5.1 NetAct name: ERROR_CODE_V

Description: SD PDUs must be retransmitted. If SD PDUs have been lost, the peer SSCOP entity can request them to be retransmitted with USTAT PDU or STAT PDU.

Updated: When SSCOP detects from the received (U)STAT PDU that the peer entity has not received all SD PDUs that the SSCOP has sent.










Counter ID: M546C27 Network element name: ERROR_CODE_W

Version: 5.1 NetAct name: ERROR_CODE_W

Description: Lack of credit. Credit is granted by the SSCOP receiver to allow the peer SSCOP transmitter to transmit new SD PDUs. The credit value is conveyed to the transmitter in the (N(MR) field of each BGN, BGAK, RS, RSAK, ER, ERAK, STAT and USTAT PDU sent by the receiver. The credit value sent to the transmitter is the sequence number of the first SD PDU that the receiver will not accept. The credit is assigned the value "No" when the SSCOP transmitter cannot send any SD PDUs because the receiver will not accept them.

Updated: When SSCOP wants to send SD PDUs to peer SSCOP, but the information obtained from the previous STAT PDU tells that the peer SSCOP will not receive this SD PDU (that is, the SD PDU sequence number is too high).










116 DN04143903




Counter ID: M546C28 Network element name: ERROR_CODE_X

Version: 5.1 NetAct name: ERROR_CODE_X

Description: Credit obtained. Credit is granted by the SSCOP receiver to allow the peer SSCOP trans-mitter to transmit new SD PDUs. The credit value is conveyed to the transmitter in the (N(MR) field of each BGN, BGAK, RS, RSAK, ER, ERAK, STAT and USTAT PDU sent by the receiver. The credit value sent to the transmitter is the sequence number of the first SD PDU that the receiver will not accept. The credit is assigned the value "Yes" when the SSCOP transmitter receives such BGN, BGAK, RS, RSAK, ER, ERAK, STAT or USTAT PDU that allows it to send SD PDUs to the SSCOP receiver.

Updated: If SSCOP has previously been declined credit and the next received STAT PDU N(MR) value indicates that the peer node is again willing to receive SD PDUs.










Counter ID: M546C29 Network element name: ERROR_CODE_LW

Version: 5.1 NetAct name: ERROR_CODE_LW

Description: Local credit window closed. This error counter is increased in the SSCOP receiver when it cannot accept any new SD PDUs. This happens when the receive buffer is full.

Updated: In the SSCOP receiver when it cannot accept any new SD PDUs.










Counter ID: M546C30 Network element name: ERROR_CODE_LX

Version: 5.1 NetAct name: ERROR_CODE_LX

DN04143903 117



Description: Local credit window opened. This error counter is increased in the SSCOP receiver when it can again accept new SD PDUs.

Updated: When the SSCOP receiver can again accept new SD PDUs after its local credit window had been closed.










Counter ID: M546C31 Network element name: ERROR_CODE_DEL

Version: 5.1 NetAct name: ERROR_CODE_DEL

Description: SD PDUs must be deleted. The SSCOP transmitter has discarded an AA-DATA request from the user because it cannot store it in its transmit buffer. This can happen if the SSCOP receiver closes the credit window and the SSCOP transmitter cannot send SD PDUs and has to store them in the transmit buffer. Also, if there is congestion in the lower layers, the SD PDUs cannot be sent.

Updated: When SSCOP discards AAL_data requests.










Counter ID: M546C32 Network element name: RX_ERR

Version: 5.1 NetAct name: RX_ERR

Description: The total sum of received errors. This counter is the sum of the following counters: UNEXP_ERR M546C34, BA_ERR M546C35, CRC_ERR M546C36, CPI_ERR M546C37, LEN_ERR M546C38, PAD_ERR M546C39, CRC_PAD_ERR M546C40, RSM_TIMEOUT M546C41, ABORT_DET M546C42, EARLY_DISC M546C43, STATUS_QF M546C44, VCC_FW M546C45, FBQ_UNDERF M546C46, STAT_Q_OVERF M546C47.

Updated: This counter is updated when a received AAL5 CPCS-PDU is reassembled and errors are detected.

118 DN04143903













Counter ID: M546C33 Network element name: NO_ERR

Version: 5.1 NetAct name: NO_ERR

Description: The number of reassembled AAL5 CPCS-PDUs which contain no errors. SAR Reassembly status.

Updated: AAL5 CPCS-PDU is reassembled, and no errors are detected.










Counter ID: M546C34 Network element name: UNEXP_ERR

Version: 5.1 NetAct name: UNEXP_ERR

Description: The number of reassembled AAL5 CPCS-PDUs which contain unexpected errors. Unex-pected errors are others than those reported in counters UNEXP_ERR M546C34, BA_ERR M546C35, CRC_ERR M546C36, CPI_ERR M546C37, LEN_ERR M546C38, PAD_ERR M546C39, CRC_PAD_ERR M546C40, RSM_TIMEOUT M546C41, ABORT_DET M546C42, EARLY_DISC M546C43, STATUS_QF M546C44, VCC_FW M546C45, FBQ_UNDERF M546C46, STAT_Q_OVERF M546C47.

Updated: AAL5 CPCS-PDU is reassembled and an unexpected error is detected.





DN04143903 119








Counter ID: M546C35 Network element name: BA_ERR

Version: 5.1 NetAct name: BA_ERR

Description: The number of reassembled AAL5 CPCS-PDUs whose total PDU length is over the maximum PDU length allowed. During the reassembly of the last cell (EOM cell) of the AAL5 CPCS-PDU, the maximum SDU delivery length (including trailer and PAD) is checked to ensure that the PDU under reassembly does not exceed the maximum SDU delivery length of 65535 bytes.

Updated: An AAL5 CPCS-PDU is reassembled, and the maximum length of 65535 bytes is exceeded during the processing of the EOM cell.










Counter ID: M546C36 Network element name: CRC_ERR

Version: 5.1 NetAct name: CRC_ERR

Description: The number of reassembled AAL5 CPCS-PDUs whose CRC-32 has been violated. When the EOM cell is processed, the reassembly coprocessor compares the calculated CRCREM value with the CRC-32 value in the trailer of the AAL5 PDU. If they are different, the reassembly coprocessor sets the CRC_ERROR bit in the status queue entry to logic 'high'.

Updated: An AAL5 CPCS-PDU is reassembled and a CRC-32 error is detected.









120 DN04143903





Counter ID: M546C37 Network element name: CPI_ERR

Version: 5.1 NetAct name: CPI_ERR

Description: The number of reassembled AAL5 CPCS-PDUs whose CPI is invalid. When the EOM cell is processed, the reassembly coprocessor performs the following check: If the CPI field in the AAL5 trailer is not at zero, the CPI_ERROR bit in the status queue entry is set to logic 'high'.

Updated: An AAL5 CPCS-PDU is reassembled and an invalid CPI detected.










Counter ID: M546C38 Network element name: LEN_ERR

Version: 5.1 NetAct name: LEN_ERR

Description: The number of reassembled AAL5 CPCS-PDUs whose length has been violated. During the reassembly of a non-EOM cell, the maximum SDU delivery length (including trailer and pad) is checked to ensure that the PDU under reassembly does not exceed the maximum SDU delivery length of 65535 bytes. If a non-EOM cell is received, where the maximum SDU delivery length is exceeded, Early Packet Discard is performed. The reassembly coprocessor reports this condition via a status queue entry, with the lenght error and EPD status bits set. The AAL5_DSC_CNT counter is also incremented.

Updated: AAL5 CPCS-PDU is reassembled, and a non-EOM cell exceeds the maximum SDU delivery length.










DN04143903 121



Counter ID: M546C39 Network element name: PAD_ERR

Version: 5.1 NetAct name: PAD_ERR

Description: The number of reassembled AAL5 CPCS-PDUs whose PAD field length is incorrect. When the EOM cell is processed, the reassembly coprocessor compares the value collected in the Length Counter with the value in the LENGTH field in the trailer of the AAL5 PDU. If the number of PAD bytes is less than zero or greater than 47, the PAD error bit in the status queue entry is set to a logic high.

Updated: AAL5 CPCS-PDU is reassembled, and an invalid PAD field length is detected.










Counter ID: M546C40 Network element name: CRC_PAD_ERR

Version: 5.1 NetAct name: CRC_PAD_ERR

Description: The number of reassembled AAL5 CPCS-PDUs in which either the CRC-32 has been violated or the PAD field length is invalid. See PAD_ERR M546C39 and CRC_ERR M546C36.

Updated: An AAL5 CPCS-PDU is reassembled and both CRC-32 and PAD field length errors are detected.










Counter ID: M546C41 Network element name: RSM_TIMEOUT

Version: 5.1 NetAct name: RSM_TIMEOUT

122 DN04143903




Description: The number of reassembled AAL5 CPCS-PDUs whose reassembly timer has expired. The reassembly coprocessor automatically detects active CPCS-PDU time-out for reassembly channels. A PDU time-out occurs when a partially received PDU is not complete within a set time period. The period is fixed by the system as 1 second. When the reassembly coprocessor detects this time-out condition, it provides a status queue indication to the host. This indication allows the host to recover the buffers held by the partially completed PDU.

Updated: When AAL5 CPCS-PDU reassembly time has expired.










Counter ID: M546C42 Network element name: ABORT_DET

Version: 5.1 NetAct name: ABORT_DET

Description: The number of AAL5 CPCS-PDUs whose sending has been aborted. When the EOM cell is processed, the reassembly coprocessor performs the following check: If the LENGTH field in the trailer of the AAL5 PDU is zero, the ABORT bit in the status queue entry is set to logic 'high'.

Updated: When sending an AAL5 CPCS-PDU has been aborted.










Counter ID: M546C43 Network element name: EARLY_DISC

Version: 5.1 NetAct name: EARLY_DISC

Description: The number of AAL5 CPCS-PDUs which have been discarded because free receive buffers was not available. A partially reassembled CPCS-PDU has been discarded because of buffer underflow, Cell Loss Priority (CLP) discard or Max PDU length exceeded.

Updated: When Early Packet Discard (EPD) occurs.

DN04143903 123












Counter ID: M546C44 Network element name: STATUS_QF

Version: 5.1 NetAct name: STATUS_QF

Description: The number of status queue fulfillments. A status queue overflow or full condition is entered when the last available status queue entry is written. When the reassembly coprocessor is in status full condition, it discards all cells. If a Continuation of Message (COM) or End Of Message (EOM) cell is received while the status queue is full, the channel is marked for status full packet discard. When a Single Segment Message (SSM), End Of Message (EOM), or Operation And Maintenance (OAM) cell is received during a status full condition, the cell is discarded and the status queue is checked. If there is now room in the status queue, the status full condition is exited.

Updated: This counter is incremented when the last entry of the reassembly status queue is written. This can occur when there is a big burst of AAL5 traffic coming to the unit and the AAL5 cannot clear the reas-sembly status queue fast enough.










Counter ID: M546C45 Network element name: VCC_FW

Version: 5.1 NetAct name: VCC_FW

Description: The number of AAL5 CPCS-PDUs which have been discarded because vcc firewall is crossed. Not in use.

Updated: Not updated, for future use.



124 DN04143903











Counter ID: M546C46 Network element name: FBQ_UNDERF

Version: 5.1 NetAct name: FBQ_UNDERF

Description: The number of AAL5 CPCS-PDUs which have been discarded because of free buffer queue underflows. An underflow condition occurs when the SAR attempts to retrieve a queue entry but the host has not yet supplied the entry. This condition only happens in free buffer queues. The SAR detects this condition by checking the queue entry VLD bit. Once detected, the SAR enters the "Underflow Detected" state on this queue only. Since this signifies that no data buffers are available for reassembly, the SAR initiates EPD on all channels assigned to this queue.

Updated: When AAL5 CPCS-PDUs are discarded because of free buffer queue underflows.










Counter ID: M546C47 Network element name: STAT_Q_OVERF

Version: 5.1 NetAct name: STAT_Q_OVERF

Description: The number of AAL5 CPCS-PDUs which have been discarded because the status queue of the receive buffers is full. See STATUS_QF M546C44.

Updated: When AAL5 CPCS-PDUs are discarded because the status queue of the receive buffers is full.







DN04143903 125






Counter ID: M546C48 Network element name: VCC_RESE

Version: 5.1 NetAct name: VCC_RESE

Description: The number of vcc re-reservations.

Updated: The counter is incremented if another client tries to obtain a vcc that is already reserved.










Counter ID: M546C49 Network element name: VCC_RELE

Version: 5.1 NetAct name: VCC_RELE

Description: The number of illegal vcc releasing attempts.

Updated: The counter is incremented if another client tries to obtain a vcc that is already reserved.










Counter ID: M546C50 Network element name: RX_PDU

Version: 5.1 NetAct name: RX_PDU_UNI

Description: The number of received error-free AAL5 CPCS-PDUs.

126 DN04143903




Updated: When an error-free AAL5 CPCS-PDU is received.










Counter ID: M546C51 Network element name: RX_SIZE

Version: 5.2 NetAct name: RX_SIZE_UNI

Description: The number of bytes in reassembled error-free AAL5 CPCS-PDUs.

Updated: When an error-free AAL5 CPCS-PDU is reassembled.










DN04143903 127

RNC Counters - Transport and HW Part SS7 signalling measurements

Id:0900d8058092e3d2Confidential

6 SS7 signalling measurementsThe SS7 signalling measurements can be used to find out the number and duration of signalling traffic events. The measurements also show the amount of signalling traffic and its distribution in the signalling network.

The measurements can be divided into message transfer part (MTP), signalling connec-tion control part (SCCP), and transaction capabilities application part (TC) measure-ments. The TC protocol is not supported. The TC measurements are, however, included in the SS7 statistics (available in MML outputs and reports), but the counters are not running. The logical files of TC reports are connected to the byte basket by default (BBU-0).

Each measurement report of the SS7 signalling contains information on the header, identification, and measurement of the signalling network entities to be measured. If the report is formed of several messages, the measurement report can consist of several subreports.

All measurements are based on the ITU-T Recommendation Q.752. There are two ways of interrogating SS7 signalling measurements. One way is to use MML commands and the other way is to use reporting. Using MML commands is reasonable when, for example, there is some kind of trouble situation and you just want to check some mea-surement data to find out the problem. Using reporting is reasonable for long time mon-itoring of the signalling network performance. By reporting, it is possible to collect measurement data from a certain period of time, from 30 minutes to one week.

With MML commands, you can interrogate cumulative and/or periodic measurements. The cumulative measurement includes all the measurement values accumulated since the start-up of statistical compilation. The periodic measurement includes the values accumulated during the most recent full measurement period. For periodic measure-ment, the period is either 5 minutes, 15 minutes (only for some of the measurements), or 30 minutes.

You can examine the SS7 measurements with the following command groups:

• MTP measurements: • OL - interrogation of signalling link statistical counters • ON - interrogation of signalling network statistical counters • OM - interrogation of auxiliary statistical counters

• SCCP measurements: • OT - interrogation of SCCP and TC statistical counters

The entities of the SS7 signalling network statistics are:

• numbers of occurring events and their logs • duration or time of the events • amount of data handled as messages or bytes

RNC supports only ASCII reports for SS7 measurements.

6.1 Functional parts of SS7 signalling measurements and reportingThe measurements are set in two phases. First you define which measurements will be activated and then you define the measurement periods.

128 DN04143903



SS7 signalling measurements

Figure 8 SS7 signalling statistics system

Explanation of the functional parts of the SS7 signalling statistics system:

Central Part of Statistics (CPS) Controls the statistics, collects measurement results from the distributed part of statistics and stores them. If the CPS is passive, the SS7 measurements, including 6.X measurements and SS7 interval logs, are not collected and are not reliable.

SS7 measurements Covers all SS7 measurements excluding the M.X measurements (M6163 and M6667).

Measurements 6.1 and 6.3 (M6163) Covers the measurements 6.1 (number of received SIF and SIO bytes listed by the originating points) and 6.3 (number of sent SIF and SIO bytes listed by the destination points), defined in ITU-T Recommendation Q.752. The measurements are col-lected into the CPS only if the CPS is active.

Measurements 6.6 and 6.7 (M6667) Covers the measurements 6.6 (number of SIF and SIO bytes on the specified OPC, DPC and SIO) and 6.7 (number of handled MSUs on the specified OPC, DPC and SIO), defined in ITU-T Recommendation Q.752. These measurements have to be activated when using MTP's traffic measurement matrix. The measurements are collected into the CPS only if the CPS is active.

SS7 interval log reporting The SS7 interval log reporting covers the measurements defined in the ITU-T Recommendation Q.752 which are implemented as 1st + interval measurements.

The SS7 interval log reporting includes only text format reports. These reports can be connected via logical files to different I/O devices, files, disks and databases. The SS7 interval log reporting is performed only if the central part of statistics (CPS) is active.

Changes in the configuration of signalling network are automatically configured to the SS7 interval log reporting.

SS7 reports (REP) The SS7 reporting forms both text format and binary reports. These reports can be connected via the logical files to different I/O devices, files, disks and databases. The reports are only generated when the CPS is active.

Central Part of Statistics(CPS)

States: Active/Passive

Displayedwith MMLs

Measurements6.1 and 6.3

(M6163)


Output vialogical files toI/O device(VDS-0)

Stored in NetActand viewed withNE MeasurementExplorer

Measurements6.6 and 6.7

(M6667)


SS7 reports(REP)


SS7 interval logreports

DN04143903 129



The most important part is the CPS. If CPS is passive, you cannot display measure-ments with MMLs or via logical files.

When the statistics are active, the changes in the configuration of the signalling network are also configured automatically into the statistics. This means that all signalling links, signalling points, SCCP signalling points and SCCP subsystems are included in the sta-tistics. Likewise, if you add a network item, such as a signalling link, it is automatically added into the statistics, and if you remove a network item, it is removed from the sta-tistics.

However, so called matrix measurements are exceptions to the statistics configuration. As these measurements cause a lot of load to the computer units and message buses, there are limited SI, OPC and DPC combinations for the measurements. The configura-tion of the measurement matrix is described in Configuring MTP's traffic measurement matrix.

6.2 Logical files of SS7 signalling measurementsThe SS7 measurements reporting includes text format reports. These reports can be connected via the logical files to different I/O devices, files and databases. The logical files of the SS7 measurement reports are listed in the tables below.

Number Report Logical file: (text)

1 MTP signalling link avail-ability

MTPSLAVAIA

2 MTP signalling link perfor-mance

MTPSLPERFA

3 MTP signalling link utilisa-tion

MTPSLUTILA

MTP signalling point related reports:

4 MTP signalling point status MTPSPSTATA

5 MTP signalling link set and route set availability

MTPSLSAVAA

MTP traffic distribution related reports:

6 MTP signalling traffic report of signalling points

MTPOCTHSPA

7 MTP signalling traffic report of user parts

MTPOCTSIOA

8 MTP matrix signalling traffic report

MTPOCTMATA

SCCP signalling point related report:

Table 7 The logical files of SS7 measurement reports

130 DN04143903




6.3 Reading instructions for tables containing MTP and SCCP measurement descriptionsThe measurements may be used one at a time, or in conjunction with other measure-ments. Each primitive measurement is classified for the purpose of guidance into one or more categories called fault management (F), configuration management (C), perfor-mance management (P) and network administration and planning (N). Some of these measurements are also for near real-time use (R).

• fault management (F)This category utilises on occurrence events and the 5-minute measurements to detect and report faults, and to monitor the signalling network responses under abnormal conditions.

• configuration management (C)This category is used for dynamic configuration changes associated with faults or administrative action. The measurements are usually used for near-real time.

• performance management (P)This category is used for near-real time, medium term and long term control. The purpose is to sustain network performance, over both short and long term.

9 SCCP signalling point mea-surements

SCCPSPA

SCCP subsystem related report:

10 SCCP subsystem mea-surements

SCCPSSA

SCCP and TC single reports:

11 SCCP local subsystem availability

SCCPLSSAVA

12 SCCP single meters SCCPSINGLA

Report Logical file: (text)

MTP signalling link log MTPSLLOGA

MTP signalling point log MTPSPLOGA

SCCP signalling point log SCCPSPLOGA

SCCP segmentation and reassembly log SCCPSGLOGA

SCCP GT translation error log SCCPGTLOGA

Table 8 The logical files of SS7 interval log reports

Number Report Logical file: (text)

Table 7 The logical files of SS7 measurement reports (Cont.)

DN04143903 131



• network administration and planning (N)This category involves measurements that are used on a long-term basis and are in general retained external to the signalling network resources. The activities include planning and dimensioning (engineering) the signalling network resources, such as determining the resource quantities, for example number of link sets, and resource configuration, for example routing.

• near real-time use (R)This category is applied in addition to the categories defined above for those mea-surements which are for use in near real time. Usually it is applied to those measure-ments which are marked as "on occurrence", or "5 minutes" in duration.

The Usage column indicates which categories apply to each measurement. Column Duration indicates intervals for measurements (measurement periods). Column MML indicates the MML command for interrogating each measurement.

The count items in the tables, identified in column Units as "event/SP", "MSUs/SL" and so on, imply the total count of items in the specified period, and implicitly indicate the identity of what is being counted, "event/SP" identifies the Signalling Point, "MSUs/SL" identifies the Signalling Link and so on.

The event items in the tables, which are recorded "on occurrence", are recorded with a time stamp, that gives the unique network time when the event indicator was generated.

6.4 MTP (message transfer part) measurements in RNCThe tables below present all MTP counters that are implemented and based on the ITU-T Recommendations Q.752 and Q.2144:

• signalling link faults and performance • signalling link availability • signalling link utilisation • signalling link set and route set availability • signalling point status • signalling traffic distribution

See Reading instructions for tables containing MTP and SCCP measurement descrip-tions.

Description of measurements Units Usage Duration MML

1. Duration of link in the In-service state s/SL F, P, N 30 min OLP

2. SL failure – All reasons (specific protocol errors events)

Event/SL F, R, P 30 min/On occur.

OLP

3. SL failure – No_RESPONSE Timer expiration (SSCOP)

Event/SL F, R, P 30 min/On occur.

OLP

4. SL failure – Excessive error rate Event/SL F, R, P 30 min/On occur.

OLP

5. SL failure – Excessive duration of congestion Event/SL F, R, P 30 min/On occur.

OLP

Table 9 Q.2144 MTP Signalling Link Faults and Performance, ATM links (The measurements with a 30-minute counter can also be reported with MTP Signalling Link Performance report.)

132 DN04143903




SL signalling link

* measurement deleted from Q.752

6. SL alignment failure Event/SL F, P 5 min/30 min

OLP

7. Number of MAA-ERROR.indications with Error Type SD loss

Event/SL F, P 5 min/30 min

OLP


Table 9 Q.2144 MTP Signalling Link Faults and Performance, ATM links (The measurements with a 30-minute counter can also be reported with MTP Signalling Link Performance report.) (Cont.)


2.1 Duration of SL unavailability (for any reason )

s/SL F, P, N 30 min OLA

2.2 Local manual changeovers * Event/SL P 30 min OLA, OLL

2.3 Remote initiative changeovers * Event/SL P 30 min OLA, OLL

2.5 Duration of SL inhibition due to local man-agement actions

s/SL P 30 min OLA

2.6 Duration of SL inhibition due to remote man-agement actions

s/SL P 30 min OLA

2.7 Duration of SL unavailability due to link failure

s/SL P 30 min OLA

2.8 Duration of SL unavailability due to local blocking *

s/SL P 30 min OLA

2.9 Duration of SL unavailability due to remote processor outage

s/SL P 30 min OLA

2.10 Start of remote processor outage Event/SL F, R, P, C 30 min/On occur.

OLA, OLL

2.11 Stop of remote processor outage Event/SL F, R, P, C 30 min/On occur.

OLA, OLL

2.13 Local management inhibit Event/SL P 5 min/30 min

OLA

2.14 Local management uninhibit Event/SL P 5 min/30 min

OLA

2.15 Duration of local busy ATM: s/SL F, R, P 5 min/30 min

OLA

2.16 Start of local inhibition Event/SL F, R, C On occur OLA

2.17 End of local inhibition Event/SL F, R, C On occur OLA

2.18 Start of remote inhibition Event/SL F, R, C 30 min/On occur

OLA, OLL

2.19 End of remote inhibition Event/SL F, R, C 30 min/On occur

OLA, OLL

Table 10 MTP Signalling Link Availability (The measurements with a 30-minute counter can also be reported with MTP Signalling Link Performance report.)

DN04143903 133



SL signalling link


3.1 Number of SIF and SIO octets transmitted Octets/SL P, N 5 min/30 min

OLU

3.2 Octets retransmitted Octets/SL P, N 5 min/30 min

OLU

3.3 Number of message signal units transmitted MSUs/SL P, N 5 min/30 min

OLU

3.4 Number of SIF and SIO octets received Octets/SL P, N 5 min/30 min

OLU

3.5 Number of message signal units received MSUs/SL P, N 5 min/30 min

OLU

3.6 SL congestion indications Event/SL P, R, F, N 1st∫/5 min/30 min

OLU, OLL

3.7 Cumulative duration of SL congestion s/SL F, P, N 5 min/30 min

OLU

3.9 Stop of SL congestion Event/SL F, P On occur. OLU

3.10 MSUs discarded due to SL congestion MSUs/SL F, P, N 5 min/30 min

OLU

3.11 Number of congestion events resulting in loss of MSUs

Event/SL F, P, N 1st∫/5 min/30 min

OLU

Table 11 MTP Signalling Link Utilisation (The measurements with a 30-minute counter can also be reported with MTP Signalling Link Performance report.)


4.2 Duration of unavailability of signalling linkset s/linkset F, P 30 min ONA

4.3 Start of linkset failure Event/link-set

F, R, C 30 min/On occur.

ONA, ONL

4.4 Stop of linkset failure Event/link-set

F, R, C 30 min/On occur

ONA, ONL

4.5 Init. of broadcast TFP due to failure of measured linkset

Event/link-set


ONA, ONL

4.6 Init. of broadcast TFA for recovery of measured linkset

Event/link-set


ONA, ONL

4.7 Unavailability of signalling route set due to TFP receipt *

Event/desti-nation

P, C, N 30 min ONA

4.8 Duration of measurement 4.7 * s/destina-tion

P, C, N 30 min ONA

4.9 Unavailability of route set to a given destina-tion or set of destinations

Event/desti-nation

P, C, N 30 min ONA

4.10 Duration of unavailability in 4.9 s/destina-tion

P, C, N 30 min ONA

Table 12 MTP Signalling Link Set and Route Set Availability (The measurements with a 30-minute counter can also be reported with MTP Signalling link set and Route set report.)

134 DN04143903





* measurements outside Q.752

SP signalling point

UP user part

4.11 Start of unavailability in 4.9 Event/desti-nation

F, R, C On occur. ONL

4.12 Stop of unavailability in 4.9 Event/desti-nation


4.13 Change in link set used to adjacent SP Destination and link set



Table 12 MTP Signalling Link Set and Route Set Availability (The measurements with a 30-minute counter can also be reported with MTP Signalling link set and Route set report.) (Cont.)


5.1 Adjacent SP inaccessible Event/SP F, P, R 5 min/30 min/On occur.

ONS, ONL

5.2 Duration of adjacent SP inaccessible s/SP P, R 5 min/30 min

ONS

5.4 Stop of adjacent SP inaccessible Event/SP F, R, C On occur. ONS

5.5 MSU discarded due to a routing data error MSUs/SP N, F, P 1st∫/5 min/30 min

ONS

5.6 User Part unavailable MSU transmitted Event/UP/SP

F, R, C, P 1st∫/5 min/30 min

ONS, ONL

5.7 User Part unavailable MSU received Event/UP/SP

F, R, C, P 1st∫/5 min/30 min

ONS, ONL

5.8 TFC received Event/SP/cong.level

F, P, R 1st∫/5 min/30 min

ONS

5.N1 Unauthorised STP MSUs count for inhib-ited OPC *

MSUs/SP N, P 30 min ONS

5.N2 Unauthorised STP MSUs count for inhib-ited DPC *


5.N3 Unauthorised STP MSUs count for inhib-ited STP *


Table 13 MTP Signalling Point Status (The measurements with a 30-minute counter can also be reported with MTP Signalling Point Status report.)


6.1 Number of SIF and SIO octets received with given OPC

Octets/OPC

P, A, N 15 min/30 min

ONP

Table 14 MTP Signalling Traffic Distribution (Signalling Route Utilisation) (The measurements with a 30-minute counter can also be reported with MTP Signalling Traffic reports.)

DN04143903 135



* Activation of these measurements is limited to a small number of OPC/DPC/SIO com-binations.

SI service information (for example SIF and SIO)

6.4.1 MTP fault and configuration management measurements

Detection of link failureLink failure means an event which causes a particular link to be unavailable for signal-ling. Signalling link (SL) failures are counted to determine preventive and corrective maintenance actions in order to restore network capabilities.

t In the following lists, the item numbers in parentheses refer to the item numbers in the tables in MTP (message transfer part) measurements in RNC.

Measurements:

• all reasons (Item 1.2) • abnormal FIBR/BSNR (Item 1.3) • excessive delay of acknowledgement (Item 1.4) • excessive error rate (Item 1.5) • excessive duration of congestion (Item 1.6) • signalling link restoration (Item 1.12)

Detection of increases in link Signal Unit (SU) error ratesThis activity ensures that the signalling data link error rate is not rising beyond specifi-cation. The SU Error Rate Monitor is the basic instrument for monitoring signalling data link performance.

Measurements:

• number of SIF and SIO octets transmitted (Item 3.1) • number of SIF and SIO octets received (Item 3.4)

Operational measurements counting error events provide supplementary information to warn of impending failures or give a running assessment of signalling data link quality.

Measurements:

• number of SUs in error (monitors incoming performance) (Item 1.8)

6.2 Number of SIF and SIO octets transmitted with given DPC

Octets/OPC


ONP

6.3 Number of SIF and SIO octets handled with given SIO

Octets/SI P, A, N 15 min/30 min

ONI

6.6 Number of SIF and SIO octets handled with given OPC, DPC and SIO *

Octets/SI/ OPC/DPC set


ONT

6.7 Number of MSUs handled with given OPC, DPC and SIO *

Octets/SI/ OPC/DPC set


ONT


Table 14 MTP Signalling Traffic Distribution (Signalling Route Utilisation) (The measurements with a 30-minute counter can also be reported with MTP Signalling Traffic reports.) (Cont.)

136 DN04143903




• number of Negative Acknowledgements (NACKS) received (monitors outgoing per-formance) (Item 1.9)

Counting total Signal Unit errors allows the estimation of Signalling Data Link bit error rates, assuming that errors are random. The estimate uses measurement 1.1, duration of link in the in-service state, multiplied by the link transmission rate.

Detection of marginal link faultsThe SU Error Rate Monitor applies to lost alignment as well as corrupted data. Usually both conditions are caused by degraded performance of the transmission facility. Align-ment and proving failures often indicate a marginally performing link.

Measurement:

• SL alignment or proving failure (Item 1.7)

Measurements:

• local automatic changeover (Item 1.10) • local automatic changeback (Item 1.11) • SL congestion indications (Item 3.6) • cumulative duration of SL congestions (Item 3.7) • number of congestion events resulting in loss of MSUs (Item 3.11)

Signalling link failure counters indicate the following error situations:

• Item 1.3 indicates complex failures in transmission or an intermittent hardware fault or even a design error.

• Item 1.4 may indicate a serious disturbance or an interruption of the signalling data link.

• Item 1.5 indicates a “noisy” link. • Item 1.6 may indicate serious congestion at the remote end of the signalling link. • Item 1.7 indicates a signalling data link fault which prevents the SdL moving into

service. • Item 1.8 indicates the incoming message error rate. • Item 1.9 indicates the outgoing message error rate.

Surveillance of network statusThis activity is concerned with surveillance of the network as a whole, in order to coor-dinate and assign priorities to the maintenance actions. The information to support this activity will come from indicators of the operational and congestion status.

Measurements to survey network status:

• local automatic changeover (Item 1.10) • local automatic changeback (Item 1.11) • start of remote processor outage (Item 2.10) • stop of remote processor outage (Item 2.11) • SL congestion indications (Item 3.6) • stop of SL congestion (Item 3.9) • number of congestion events resulting in loss of MSUs (Item 3.11) • start of link set failure (Item 4.3) • stop of link set failure (Item 4.4) • initiation of Broadcast TFP due to failure of measured link set (Item 4.5) • initiation of Broadcast TFA for recovery of measured link set (Item 4.6)

DN04143903 137



• start of unavailability in measurement 4.9 (Item 4.11) • stop of unavailability in measurement 4.9 (Item 4.12) • adjacent signalling point inaccessible (Item 5.1) • stop of adjacent signalling point inaccessible (Item 5.4) • start and end of local inhibition (Items 2.16 and 2.17) • start and end of remote inhibition (Items 2.18 and 2.19)

Detection of routing and distribution table errorsIn operation, the SS7 routing data will be updated frequently as the network changes. It is necessary to keep track of signalling point state and routing problems on a routine basis.

Measurements:

• duration of unavailability of signalling link set (Item 4.2) • start of link set failure (Item 4.3) • stop of link set failure (Item 4.4) • initiation of Broadcast TFP due to failure of measured link set (Item 4.5) • initiation of Broadcast TFA for recovery of measured link set (Item 4.6) • unavailability of route set to a given destination or set of destinations (Item 4.9) • duration of unavailability in measurement 4.9 (Item 4.10) • start of unavailability in measurement 4.9 (Item 4.11) • stop of unavailability in measurement 4.9 (Item 4.12) • adjacent SP inaccessible (Item 5.1) • duration of adjacent SP inaccessible (Item 5.2) • stop of adjacent SP inaccessible (Item 5.4) • number of MSUs discarded due to a routing data error (Item 5.5) • User Part Unavailable MSUs transmitted and received (Items 5.6 and 5.7)

6.4.2 MTP performance in RNC

Link, link set, signalling point, and route set utilisationThe MTP (message transfer part) utilisation measurement is concerned with evaluating message flows to ensure that they are not beginning to exceed stated link and signalling point capacities. It also ensures that the existing routing results in proportionate utilisa-tion of the available capacity.

t In the following lists, the item numbers in parentheses refer to item numbers in the tables in MTP (message transfer part) measurements in RNC.

Measurements by link:

• duration of link in the in-service state (Item 1.1) • duration of SL unavailable (for any reason) (Item 2.1) • duration of SL unavailability due to remote processor outage (Item 2.9) • duration of local busy (Item 2.15) • number of SIF and SIO octets transmitted (Item 3.1) • number of octets retransmitted (Item 3.2) • number of message signal units transmitted (Item 3.3) • number of SIF and SIO octets received (Item 3.4)

138 DN04143903




• number of message signal units received (Item 3.5) • SL congestion indications (Item 3.6) • cumulative duration of SL congestions (Item 3.7) • MSUs discarded due to SL congestion (Item 3.10) • number of congestion events resulting in loss of MSUs (Item 3.11)

Measurements by link set:

• duration of unavailability of signalling link set (Item 4.2)

Measurements by signalling point:

• number of SIF and SIO octets received: with given origination point code (OPC) (Item 6.1)

• number of SIF and SIO octets transmitted: with given destination point code (DPC) (Item 6.2)

• number of MSUs handled: with given OPC, DPC and SIO (Item 6.7)

Signalling link loadThere are statistical counters that collect information on MTP signalling link availability, performance, and utilisation. You can use utilisation counters for finding out signalling link loads. You can read measurement values with the OLU command, and signalling link load in Erlangs with the OLT command.

ATM-based signalling link load in Erlangs (OLT) is calculated from octets used by ATM cells for SS7 traffic. This gives more realistic result of ATM link occupancy. You should also read samples of 30-minute periods of measurements 3.1 and 3.2 (transmitted SIF+SIO octets), 3.3 (transmitted MSUs), 3.4 (received SIF+SIO octets), and 3.5 (received MSUs) especially during the busy hour.

The recommended link occupancy for ATM-based signalling link is 0.2 Erlangs (speci-fied in the ETSI 300 008 specifications). If the occupancy is higher, consider adding a new link.

g An alarm "Signalling link load over threshold" (0026) is set if the threshold is exceeded during a 5-minute measurement period. You can change the threshold value with the NOM command (parameter group E, parameter E13).

Congestion levels indicate the number of MSUs in the transmission buffer. Congestion counters are collected in 5-minute periods, and also the result of the latest 30-minute period is stored. If the signalling load is momentarily very heavy (peak load), the con-gestion threshold might be exceeded although the average link load during a longer period is low. If counters 3.6 to 3.11 increase during every 5- or 30-minute period, you should consider a new link, especially if counter 3.10 shows that the MSUs have been discarded due to congestion.

SAAL-level countersYou can examine momentary values of signalling link SAAL (signalling ATM adaptation layer) measurements of ATM-based signalling links with the command OMS.

6.4.3 MTP signalling link availability report (208/D0H)Link failure means an event which causes a particular link to be unavailable for signal-ling. Signalling link (SL) failures are counted to determine preventive and corrective maintenance actions in order to restore network capabilities.

DN04143903 139



g In the following lists, the item numbers in parentheses refer to the item numbers in the tables in MTP (message transfer part) measurements in RNC.

Counter ID: M208B2C1 Network element name: DUR_OF_UNAVAIL

Version: 2.0 NetAct name: DUR_OF_UNAVAIL

Description: Duration of signalling link unavailability for any reason, 2.1 in ITU-T Q.752. This counter is the sum of ITU-T Q.752 counters 2.7 + 2.8 + 2.9 + 2.5 + 2.6.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C2 Network element name: DUR_OF_UNAVAIL_LINK_FAILURE

Version: 2.0 NetAct name: DUR_OF_UNAVAIL_LINK_FAILURE

Description: Duration of signalling link unavailability due to link failure, 2.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C3 Network element name: DUR_OF_UNAVAIL_LOCAL_BLOCKING

Version: 2.0 NetAct name: DUR_OF_UNAVAIL_LOCAL_BLOCKING

140 DN04143903




Description: Duration of signalling link unavailability due to local blocking, 2.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C4 Network element name: DUR_OF_UNAVAIL_REM_PROC_OUTAGE

Version: 2.0 NetAct name: DUR_OF_UNAVAIL_REM_PROC_OUTAGE

Description: Duration of signalling link unavailability due to remote processor outage, 2.9 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C5 Network element name: DUR_OF_INHIBIT_LOC_MANAG_ACT

Version: 2.0 NetAct name: DUR_OF_INHIBIT_LOC_MANAG_ACT

Description: Duration of signalling link inhibition due to local management actions, 2.5 in ITU-T Q.752.

Updated:




DN04143903 141



Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C6 Network element name: DUR_OF_INHIBIT_REM_MANAG_ACT

Version: 2.0 NetAct name: DUR_OF_INHIBIT_REM_MANAG_ACT

Description: Duration of signalling link inhibition due to remote management actions, 2.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C7 Network element name: DUR_OF_LOCAL_BUSY

Version: 2.0 NetAct name: DUR_OF_LOCAL_BUSY

Description: Duration of local busy (number of SIBs), 2.15 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97




142 DN04143903





Counter ID: M208B2C8 Network element name: LOCAL_MANUAL_CHANGEOVERS

Version: 2.0 NetAct name: LOCAL_MANUAL_CHANGEOVERS

Description: Number of local manual changeovers and changeovers due to system recovery actions, 2.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C9 Network element name: REMOTE_INITIATIVE_CHANGEOVERS

Version: 2.0 NetAct name: REMOTE_INITIATIVE_CHANGEOVERS

Description: Number of remote initiative changeovers, 2.3 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C10 Network element name: REM_PROC_OUTAGE_START

Version: 2.0 NetAct name: REM_PROC_OUTAGE_START

DN04143903 143



Description: Start of remote processor outage, 2.10 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C11 Network element name: REM_PROC_OUTAGE_STOP

Version: 2.0 NetAct name: REM_PROC_OUTAGE_STOP

Description: Stop of remote processor outage, 2.11 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C12 Network element name: LOC_MANAG_INHIBIT

Version: 2.0 NetAct name: LOC_MANAG_INHIBIT

Description: Number of local management inhibits, 2.13 in ITU-T Q.752.

Updated:




Operability class:

144 DN04143903





ITU-T Q.752, 06/97





Counter ID: M208B2C13 Network element name: LOC_MANAG_UNINHIBITED

Version: 2.0 NetAct name: LOC_MANAG_UNINHIBITED

Description: Number of local management uninhibits, 2.14 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C14 Network element name: REM_INHIBIT

Version: 2.0 NetAct name: REM_INHIBIT

Description: Start of remote inhibition, 2.18 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 145



6.4.4 MTP signalling link performance report (209/D1H)

Counter ID: M208B2C15 Network element name: REM_UNINHIBITED

Version: 2.0 NetAct name: REM_UNINHIBITED

Description: Stop of remote inhibition, 2.19 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M208B2C16 Network element name: DURAT_LOC_BUSY_ATM

Version: 2.0 NetAct name: DURAT_LOC_BUSY_ATM

Description: Duration of local busy for ATM, 2.15 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B2C1 Network element name: DUR_IN_SERVICE_STATE

Version: 2.1 NetAct name: DUR_IN_SERVICE_STATE

Description: Duration of signalling link in service state, 1.1 in ITU-T Q.752 (TDM) and 1 in ITU-T Q.2144 (ATM).

Updated:

146 DN04143903







Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B2C2 Network element name: LINK_FAILURES_ALL_REASONS

Version: 2.1 NetAct name: LINK_FAILURES_ALL_REASONS

Description: Number of link failure caused by all reasons, 1.2 in ITU-T Q.752 (TDM) 2 in ITU-T Q.2144 (ATM).

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B2C3 Network element name: LINK_FAILURES_ABNORM_FIBR_BSNR

Version: 2.1 NetAct name: LINK_FAILURES_ABNORM_FIBR_BSNR

Description: Number of link failures caused by abnormal fibr and bsnr, 1.3 in ITU-T Q.752 only TDM.

Updated:




Operability class:

DN04143903 147




ITU-T Q.752, 06/97





Counter ID: M209B2C4 Network element name: LINK_FAILURES_EXC_DEL_OF_ACK

Version: 2.1 NetAct name: LINK_FAILURES_EXC_DEL_OF_ACK

Description: TDM: number of link failures caused by excessive delay of acknowledgement, 1.4 in ITU-T Q.752 ATM: number of link failures caused by NO_RESPONSE timer expiration 3 in ITU-T Q.2144.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B2C5 Network element name: LINK_FAILURES_EXC_ERROR_RATE

Version: 2.1 NetAct name: LINK_FAILURES_EXC_ERROR_RATE

Description: Number of link failures caused by excessive error rate, 1.5 in ITU-T Q.752 (TDM) and 4 in ITU-T Q.2144 (ATM).

Updated:




Operability class:


ITU-T Q.752, 06/97



148 DN04143903






Counter ID: M209B2C6 Network element name: LINK_FAILURES_EXC_DUR_OF_CONG

Version: 2.1 NetAct name: LINK_FAILURES_EXC_DUR_OF_CONG

Description: Number of link failures caused by excessive duration of congesition, 1.6 in ITU-T Q.752 (TDM) and 5 in ITU-T Q.2144 (ATM).

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B2C7 Network element name: LINK_FAILURES_ALI_OR_PROV_FAIL

Version: 2.1 NetAct name: LINK_FAILURES_ALI_OR_PROV_FAIL

Description: Number of alignment failures, 1.7 in ITU-T Q.752 (TDM) and 6 in ITU-T Q.2144 (ATM).

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 149



Counter ID: M209B3C1 Network element name: SIGN_UNITS_RECEIVED_IN_ERROR

Version: 2.1 NetAct name: SIGN_UNITS_RECEIVED_IN_ERROR

Description: Number of signal units received in error, 1.8 in ITU-T Q.752 only TDM.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B3C2 Network element name: NEGATIVE_ACKS

Version: 2.1 NetAct name: NEGATIVE_ACKS

Description: Number of negative acknowledgements, 1.9 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B3C3 Network element name: AUTOMATIC_CHANGEOVERS

Version: 2.1 NetAct name: AUTOMATIC_CHANGEOVERS

Description: Number of automatic changeovers, 1.10 in ITU-T Q.752.

Updated:


150 DN04143903






Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B3C4 Network element name: AUTOMATIC_CHANGEBACKS

Version: 2.1 NetAct name: AUTOMATIC_CHANGEBACKS

Description: Number of automatic changebacks, 1.11 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M209B3C5 Network element name: LINK_RESTORATIONS

Version: 2.1 NetAct name: LINK_RESTORATIONS

Description: Number of link restorations, 1.12 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97



DN04143903 151



6.4.5 MTP signalling link utilization report (210/D2H)



Counter ID: M209B3C6 Network element name: SD_LOSS

Version: 2.1 NetAct name: SD_LOSS

Description: Number of MAA_ERROR.indications, with error type SD loss 7 in ITU-T Q.2144 (ATM).

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M210B1C2 Network element name: BIT_RATE

Version: 2.0 NetAct name: BIT_RATE

Description: Signalling link bit rate.

Updated:




Operability class:






Counter ID: M210B2C1 Network element name: SIF_AND_SIO_OCTETS_TRANSMITTED

Version: 2.0 NetAct name: SIF_AND_SIO_OCTETS_TRANSMITTED

152 DN04143903




Description: Number of sif and sio octets transmitted, 3.1 in ITU-T Q.752.

Updated:


Unit: byte Range: Example values:


Operability class:


ITU-T Q.752, 06/97





Counter ID: M210B2C2 Network element name: SIF_AND_SIO_OCTETS_RECEIVED

Version: 2.0 NetAct name: SIF_AND_SIO_OCTETS_RECEIVED

Description: Number of sif and sio octets received, 3.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M210B2C3 Network element name: MSUS_TRANSMITTED

Version: 2.0 NetAct name: MSUS_TRANSMITTED

Description: Number of transmitted message signal units, 3.3 in ITU-T Q.752.

Updated:




Operability class:

DN04143903 153




ITU-T Q.752, 06/97





Counter ID: M210B2C4 Network element name: MSUS_RECEIVED

Version: 2.0 NetAct name: MSUS_RECEIVED

Description: Number of received message signal units, 3.5 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M210B2C5 Network element name: OCTETS_RETRANSMITTED

Version: 2.0 NetAct name: OCTETS_RETRANSMITTED

Description: Number of octets retransmitted, 3.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





154 DN04143903




Counter ID: M210B2C6 Network element name: SL_CONGESTION_LEVEL1

Version: 2.0 NetAct name: SL_CONGESTION_LEVEL1

Description: Number of times congestion onset level 1 threshold exceeded.

Updated:




Operability class:









Updated:




Operability class:









Updated:




DN04143903 155



Operability class:






Counter ID: M210B2C9 Network element name: MSUS_DISCARDED_LEVEL1

Version: 2.0 NetAct name: MSUS_DISCARDED_LEVEL1

Description: Number of message signal units (MSUs) discarded due to signalling link congestion (level 1), 3.10 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97







Description: Number of message signal units (MSUs) discarded due to signalling link congestion (level 2).

Updated:




Operability class:


ITU-T Q.752, 06/97





156 DN04143903






Description: Number of message signal units (MSUs) discarded due to signalling link congestion (level 3).

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M210B2C12 Network element name: EVENTS_RES_IN_LOSS_OF_MSUS_L1

Version: 2.0 NetAct name: EVENTS_RES_IN_LOSS_OF_MSUS_L1

Description: Number of times congestion discard level 1 threshold exceeded.

Updated:




Operability class:









Updated:


DN04143903 157





Operability class:









Updated:




Operability class:






Counter ID: M210B2C15 Network element name: CUMULATIVE_DURATION_LEVEL1

Version: 2.0 NetAct name: CUMULATIVE_DURATION_LEVEL1

Description: Cumulative duration of signalling link congestion level 1, 3.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97




158 DN04143903







Description: Cumulative duration of signalling link congestion level 2.

Updated:




Operability class:


ITU-T Q.752, 06/97







Description: Cumulative duration of signalling link congestion level 3.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M210B3C1 Network element name: 30_MIN_PEAKLOAD_TRAFFIC_IN

Version: 2.1 NetAct name: 30_MIN_PEAKLOAD_TRAFFIC_IN

Description: Peak load in milliErlangs for 30 minutes periods for incoming traffic.

DN04143903 159



Updated:

Logical type: Max Trigger type: Event Sampling interval:

Unit: milliErlangs Range: Example values:


Operability class:






Counter ID: M210B3C2 Network element name: 30_MIN_PEAK_TRAF_IN_STARTED

Version: 2.1 NetAct name: 30_MIN_PEAK_TRAF_IN_STARTED

Description: Start time of the peak load of 30 minutes freezing period for incoming traffic (measured as minutes from measurement period start time).

Updated:

Logical type: non-cumulative Trigger type: Duration Sampling interval:



Operability class:






Counter ID: M210B3C3 Network element name: 30_MIN_PEAKLOAD_TRAFFIC_OUT

Version: 2.1 NetAct name: 30_MIN_PEAKLOAD_TRAFFIC_OUT

Description: Peak load in milliErlangs for 30 minutes periods for outgoing traffic.

Updated:




Operability class:


160 DN04143903








Counter ID: M210B3C4 Network element name: 30_MIN_PEAK_TRAF_OUT_STARTED

Version: 2.1 NetAct name: 30_MIN_PEAK_TRAF_OUT_STARTED

Description: Start time of the peak load of 30 minutes freezing period for outgoing traffic (measured as minutes from measurement period start time).

Updated:




Operability class:






Counter ID: M210B3C5 Network element name: 5_MIN_PEAKLOAD_TRAFFIC_IN

Version: 2.1 NetAct name: 5_MIN_PEAKLOAD_TRAFFIC_IN

Description: Peak load in milliErlangs for 5 minutes periods for incoming traffic.

Updated:




Operability class:






Counter ID: M210B3C6 Network element name: 5_MIN_PEAK_TRAF_IN_STARTED

DN04143903 161



Version: 2.1 NetAct name: 5_MIN_PEAK_TRAF_IN_STARTED

Description: Start time of the peak load of 5 minutes freezing period for incoming traffic (measured as minutes from measurement period start time).

Updated:




Operability class:






Counter ID: M210B3C7 Network element name: 5_MIN_PEAKLOAD_TRAFFIC_OUT

Version: 2.1 NetAct name: 5_MIN_PEAKLOAD_TRAFFIC_OUT

Description: Peak load in milliErlangs for 5 minutes periods for outgoing traffic.

Updated:




Operability class:






Counter ID: M210B3C8 Network element name: 5_MIN_PEAK_TRAF_OUT_STARTED

Version: 2.1 NetAct name: 5_MIN_PEAK_TRAF_OUT_STARTED

Description: Start time of the peak load of 5 minutes freezing period for outgoing traffic (measured as minutes from measurement period start time).

Updated:




162 DN04143903




6.4.6 MTP signalling point status report (211/D3H)

Operability class:






Counter ID: M211B2C1 Network element name: ADJACENT_SP_INA_DURATION

Version: 2.0 NetAct name: ADJACENT_SP_INA_DURATION

Description: Duration of adjacent signal point inaccessible, 5.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M211B2C2 Network element name: ADJACENT_SP_INACCESSIBLE

Version: 2.0 NetAct name: ADJACENT_SP_INACCESSIBLE

Description: Number of adjacent signal point inaccessible, 5.1 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 163



Counter ID: M211B2C3 Network element name: NBR_OF_RECEIVED_TFC

Version: 2.0 NetAct name: NBR_OF_RECEIVED_TFC

Description: Number of transfer controlled messages received, 5.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M211B2C4 Network element name: MSU_DISCARDED_TRANS_MSUS

Version: 2.0 NetAct name: MSU_DISCARDED_TRANS_MSUS

Description: Number of message signal units (MSU) discarded due to routing data error for transmitted msus, part of 5.5 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M211B2C5 Network element name: MSU_DISCARDED_REC_MSUS

Version: 2.0 NetAct name: MSU_DISCARDED_REC_MSUS

Description: Number of message signal units (MSU) discarded due to routing data error for received msus, part of 5.5 in ITU-T Q.752.

Updated:

164 DN04143903







Operability class:


ITU-T Q.752, 06/97





Counter ID: M211B2C6 Network element name: UNAUTHORIZED_STP_MSUS_INH_DPC

Version: 2.0 NetAct name: UNAUTHORIZED_STP_MSUS_INH_DPC

Description: Unauthorized STP MSU count for inhibited DPC.

Updated:




Operability class:






Counter ID: M211B2C7 Network element name: UNAUTHORIZED_STP_MSUS_INH_OPC

Version: 2.0 NetAct name: UNAUTHORIZED_STP_MSUS_INH_OPC

Description: Unauthorized STP MSU count for inhibited OPC.

Updated:




Operability class:



DN04143903 165






Counter ID: M211B2C8 Network element name: UNAUTHORIZED_STP_MSUS_INH_STP

Version: 2.0 NetAct name: UNAUTHORIZED_STP_MSUS_INH_STP

Description: Unauthorized STP MSU count for inhibited STP.

Updated:




Operability class:






Counter ID: M211B2C9 Network element name: UPUS_TRANSMITTED

Version: 2.0 NetAct name: UPUS_TRANSMITTED

Description: User part unavailable MSU transmitted, 5.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M211B2C10 Network element name: UPUS_RECEIVED

166 DN04143903




6.4.7 MTP signalling set and route set availability report (212/D4H)

Version: 2.0 NetAct name: UPUS_RECEIVED

Description: User part unavailable MSU received, 5.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C1 Network element name: SL_SET_START_FAILURE

Version: 2.0 NetAct name: SL_SET_START_FAILURE

Description: Start of signalling link set failure, 4.3 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C2 Network element name: SL_SET_STOP_FAILURE

Version: 2.0 NetAct name: SL_SET_STOP_FAILURE

Description: Stop of signalling link set failure, 4.4 in ITU-T Q.752.

Updated:




DN04143903 167



Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C3 Network element name: SL_SET_DURATION_OF_UNA

Version: 2.0 NetAct name: SL_SET_DURATION_OF_UNA

Description: Duration of signalling link set unavailability, 4.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C4 Network element name: INITIATION_OF_BROADCAST_TFP

Version: 2.0 NetAct name: INITIATION_OF_BROADCAST_TFP

Description: Transmission of transfer prohibited message started due to signalling link failure ,4.5 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97




168 DN04143903





Counter ID: M212B2C5 Network element name: INITIATION_OF_BROADCAST_TFA

Version: 2.0 NetAct name: INITIATION_OF_BROADCAST_TFA

Description: Transmission of transfer allowed message started due to signalling link restoration, 4.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C6 Network element name: SR_SET_UNA_DUE_TO_TFP_REC

Version: 2.0 NetAct name: SR_SET_UNA_DUE_TO_TFP_REC

Description: Unavailability of signalling route set due to transfer prohibited message received, 4.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C7 Network element name: SR_SET_UNA_TO_GIVEN_DEST

Version: 2.0 NetAct name: SR_SET_UNA_TO_GIVEN_DEST

DN04143903 169



Description: Unavailability of signalling route set, 4.9 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C8 Network element name: SR_SET_UNA_DURA_DUE_TO_TFP_REC

Version: 2.0 NetAct name: SR_SET_UNA_DURA_DUE_TO_TFP_REC

Description: Duration of signalling route set due to transfer prohibited message received, 4.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M212B2C9 Network element name: SR_SET_UNA_DURA_TO_GIVEN_DEST

Version: 2.0 NetAct name: SR_SET_UNA_DURA_TO_GIVEN_DEST

Description: Duration of unavailability of signalling route set, 4.10 in ITU-T Q.752.

Updated:



170 DN04143903




6.4.8 MTP signalling traffic report of signalling points (213/D5H)


Operability class:


ITU-T Q.752, 06/97





Counter ID: M213B2C1 Network element name: SIF_AND_SIO_OCT_REC_WITH_OPC

Version: 2.0 NetAct name: SIF_AND_SIO_OCT_REC_WITH_OPC

Description: Number of SIF and SIO octets received from OPC, 6.1 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M213B2C2 Network element name: TOTAL_OCTETS_TRANS_TO_DPC

Version: 2.0 NetAct name: TOTAL_OCTETS_TRANS_TO_DPC

Description: Number for transmitted SIF and SIO octets to DPC (total), 6.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97


DN04143903 171






Counter ID: M213B3C1 Network element name: STP_1

Version: 2.0 NetAct name: STP_1

Description: Signalling Transfer Point 1 identifier.

Updated:

Logical type: non-cumulative Trigger type: Sampling interval:



Operability class:






Counter ID: M213B3C2 Network element name: TRANSMITTED_OCTETS_1

Version: 2.0 NetAct name: TRANSMITTED_OCTETS_1

Description: Number for transmitted SIF and SIO octets to DPC via STP 1, 6.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97







172 DN04143903





Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


DN04143903 173










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:







174 DN04143903






Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:




Operability class:

DN04143903 175




ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97





176 DN04143903







Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




DN04143903 177



6.4.9 MTP signalling traffic report of user parts (214/D6H)

Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M214B2C1 Network element name: RECEIVED_OCTETS

Version: 2.1 NetAct name: RECEIVED_OCTETS

Description: Number of SIF and SIO received with given SIO, 6.3 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





178 DN04143903




6.4.10 MTP matrix signalling traffic report (215/D7H)

Counter ID: M214B2C2 Network element name: TRANSMITTED_OCTETS

Version: 2.1 NetAct name: TRANSMITTED_OCTETS

Description: Number of SIF and SIO transmitted with given SIO, 6.3 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M215B2C1 Network element name: NBR_OF_SIF_AND_SIO_OCTETS

Version: 2.0 NetAct name: NBR_OF_SIF_AND_SIO_OCTETS

Description: Number of SIF and SIO octets handled with given OPD, DPC, SIO, 6.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M215B2C2 Network element name: NBR_OF_MSUS

Version: 2.0 NetAct name: NBR_OF_MSUS

Description: Number of MSUs handled with given OPD, DPC, SIO, 6.7 in ITU-T Q.752.

Updated:

DN04143903 179



6.5 SCCP (signalling connection control part) measurementsThe tables below present all SCCP (signalling connection control part) counters that are implemented and that are based on the ITU-T Recommendation Q.752:

• SCCP error performance indicators • SCCP and subsystem availability indicators • SCCP utilisation indicators • SCCP quality of service measurements

See also Reading instructions for tables containing MTP and SCCP measurement descriptions.




Operability class:


ITU-T Q.752, 06/97






7.1 Routing Failure – No translation for address of such nature

Events/SP F, R, P, N 1st&int/5 min/30 min/On occur.

OTN, OTR

7.2 Routing Failure – No translation for this specific address

Events/SP 1st&int/5 min/30 min/On occur.

OTN, OTR

7.3 Routing Failure – Network Failure (Point Code not available)

Events/SP F,P,N 1st&int/5 min/30 min/On occur.

OTN

7.4 Routing Failure – Network Congestion Events/SP F, P, N 1st&int/5 min/30 min/On occur.

OTN

7.5 Routing Failure – Subsystem Failure (unavailable)

Events/SP F,P,C,N 1st&int/5 min/30 min/On occur.

OTN

Table 15 SCCP Error Performance (SP Signalling Point) (The measurements with a 30-minute counter can also be reported with SCCP Signalling Point measurement report.)

180 DN04143903




SP signalling point

CGPA calling party address

CDPA called party address

SSN subsystem number

7.6 Routing Failure – Subsystem Congestion Events/SP F, P, N 1st&int/5 min/30 min/On occur.

OTN

7.7 Routing Failure – Unequipped user (Subsys-tem)

Events/SP F, R, C, N 1st&int/5 min/30 min/On occur.

OTN, OTR

7.8 Syntax Error Detected Events/SP F, P 1st&int/5 min/30 min/On occur.

OTN

7.9 Routing Failure – Reason unknown Events/SP F, P, C, N 1st&int/5 min/30 min/On occur.

OTN

7.10 Reassembly error - Timer Treass expiry Events/CGPA/seg.LR

F, R, P 1st&int/5 min/30 min

OTG, OTR

7.11 Reassembly error - Segment received out of sequence

Events/CGPA/seg.LR


OTG, OTR

7.12 Reassembly error - No reassembly space Events R, P, N 1st&int/5 min/30 min

OTG, OTR

7.13 Hop counter violation Events/CGPA/CDPA


OTG, OTR

7.14 Message too large for segmentation Events/SSN F, R, P 1st&int/5 min/30 min

OTS, OTL

7.15 Failure of release complete Events/DPC/prot.class


OTN, OTO

7.16 Timer T(iar) expiry Events/DPC/prot.class


OTN, OTO

7.17 Provider initiated reset of a connection Events/DPC F, R, P 1st&int/5 min/30 min

OTN, OTO

7.18 Provider initiated release of a connection Events/DPC F, R, P 1st&int/5 min/30 min

OTN, OTO

7.19 Segmentation error - Segmenting not sup-ported

Events F, R, P 1st&int/5 min/30 min

OTG, OTR

7.20 Segmentation error - Segmentation failed Events F, R, P 1st&int/5 min/30 min

OTG, OTR

7.21 Reassembly error - Reassembly failed Events F, R, P 1st&int/5 min/30 min

OTG, OTR


Table 15 SCCP Error Performance (SP Signalling Point) (The measurements with a 30-minute counter can also be reported with SCCP Signalling Point measurement report.) (Cont.)

DN04143903 181



seg. LR sequence local reference


SP signalling point



8.1 Start of local SCCP unavailable – Failure Event/Net-work

F, R, P, C 5 min/30 min/On occur.

OTA, OTL

8.2 Start of local SCCP unavailable – Mainte-nance made busy

Event/Net-work

R, P, C 5 min/30 min/On occur.

OTA, OTL

8.3 Start of local SCCP unavailable - Congestion Event/Net-work


OTA, OTL

8.4 Stop of local SCCP unavailable – All reasons Event/Net-work


OTA, OTL

8.5 Duration of local SCCP unavailable – All reasons *

s/Network P, N 5 min/30 min

OTA

8.6 Subsystem out-of-service request granted Event/SSN C, R 5 min/30 min/On occur.

OTS, OTL

8.7 Subsystem out-of-service request denied Event/SSN C, R 5 min/30 min/On occur

OTS, OTL

8.8 SCCP/subsystem congested message received

Events/SSN, affected SP/ cong.level


OTJ, OTO

8.9 Start of local subsystem prohibited Events/SSN F, R, P, C On occur/5 min/30 min

OTS, OTL

8.10 Stop of local subsystem prohibited Events/SSN F, R, P, C On occur/5 min/30 min

OTS, OTL

8.11 Subsystem prohibited message received Events/SSN/affected SP

F, R, P, C 1st&int/5 min/30 min

OTJ, OTO

8.12 Subsystem allowed message received Events/SSN/affected SP

F, R, P, C On occur/5 min/30 min

OTJ, OTO

Table 16 SCCP Subsystem Availability (The measurements with a 30-minute counter can also be reported with SCCP Subsystem measurement report and with SCCP Local Subsystem availability report.)


9.3 Total messages handled (from local or remote subsystems)

Msgs P, N 5 min/30 min

OTI

Table 17 SCCP – Utilisation (The measurements with a 30-minute counter can also be reported with SCCP Subsystem measurement report and with SCCP Single measurement report.)

182 DN04143903




* measurement outside Q.752

Msgs messages


9.4 Total messages intended for local subsys-tems

Msgs/SSN P, N 5 min/30 min

OTS

9.N1 Total messages intended from local sub-systems *


OTS

9.5 Total messages requiring global title transla-tion

Msgs P, N 5 min/30 min

OTI

9.6 Total messages originating (for connection-less classes 0,1 only) per source SSN

Msgs/SSN prot.class

P, N 5 min/30 min

OTS

9.7 Total messages received (for connectionless classes 0,1 only) per sink SSN

Msgs/SSN prot.class

P, N 5 min/30 min

OTS

9.8 Messages sent to a backup subsystem Msgs/SSN P, N 5 min/30 min

OTS

9.9 DT1 messages received from MTP per sink SSN


OTS

9.10 DT1 messages sent to MTP per source SSN


OTS

9.11 DT2 messages received from MTP per sink SSN


OTS

9.12 DT2 messages sent to MTP per source SSN


OTS

9.13 ED messages sent to MTP per source SSN Msgs/SSN P, N 5 min/30 min

OTS

9.14 ED messages received from MTP per sink SSN


OTS


Table 17 SCCP – Utilisation (The measurements with a 30-minute counter can also be reported with SCCP Subsystem measurement report and with SCCP Single measurement report.) (Cont.)


9 bis.1 UDT messages sent Msgs/SP P 5 min/30 min

OTQ

9 bis.2 UDTS messages sent Msgs/SP P, F 5 min/30 min

OTQ

9 bis.3 UDT messages received Msgs/SP P 5 min/30 min

OTQ

9 bis.4 UDTS messages received Msgs/SP P, F 5 min/30 min

OTQ

9 bis.5 CR messages sent to MTP plus ISDN-UP embedded CRs (ffs)

Msgs/SP P 5 min/30 min

OTQ

Table 18 SCCP – Quality of Service (The measurements with a 30-minute counter can also be reported with SCCP Signalling Point measurement report.)

DN04143903 183



Msgs messages

SP signalling point

6.5.1 SCCP fault management

Routing failuresThe monitoring of routing failures allows the SCCP Routing and Translation function to detect any abnormal number of messages which cannot be routed, independent of the originator being informed through message return.

t In the following lists, the item numbers in parentheses refer to the item numbers in the tables in SCCP (Signalling connection control part) measurements.

9 bis.6 CREF messages sent to MTP Msgs/SP P 5 min/30 min

OTQ

9 bis.7 CR messages received from MTP plus ISDN-UP embedded CRs (ffs)

Msgs/SP P 5 min/30 min

OTQ

9 bis.8 CREF messages received from MTP Msgs/SP P 5 min/30 min

OTQ

9 bis.9 RSR messages sent to MTP Msgs/SP P 5 min/30 min

OTQ

9 bis.10 RSR messages received from MTP Msgs/SP P 5 min/30 min

OTQ

9 bis.11 ERR messages sent to MTP Msgs/SP P 5 min/30 min

OTQ

9 bis.12 ERR messages received from MTP Msgs/SP P 5 min/30 min

OTQ

9 bis.13 XUDT messages sent (ffs) Msgs/SP P 5 min/30 min

OTQ

9 bis.14 XUDTS messages sent (ffs) Msgs/SP P, F 5 min/30 min

OTQ

9 bis.15 XUDT messages received (ffs) Msgs/SP P 5 min/30 min

OTQ

9 bis.16 XUDTS messages received (ffs) Msgs/SP P, F 5 min/30 min

OTQ

9 bis.17 LUDT messages sent (Only in IPA2800 based network elements.)

Msgs/SP P, F 5 min/30 min

OTQ

9 bis.18 LUDTS messages sent (Only in IPA2800 based network elements.)


OTQ

9 bis.19 LUDT messages received (Only in IPA2800 based network elements.)


OTQ

9 bis.20 LUDTS messages received (Only in IPA2800 based network elements.)


OTQ


Table 18 SCCP – Quality of Service (The measurements with a 30-minute counter can also be reported with SCCP Signalling Point measurement report.) (Cont.)

184 DN04143903




Measurements:

Routing failure due to

• no translation for address of such nature (Item 7.1) • no translation for this specific address (Item 7.2) • network failure (point code not available) (Item 7.3) • network congestion (Item 7.4) • subsystem failure (unavailable) (Item 7.5) • subsystem congestion (Item 7.6) • unequipped user (subsystem) (Item 7.7) • reason unknown (Item 7.9) • syntax error detected (Item 7.8).

The last item, Item 7.8, could occur if there were protocol interworking problems.

In addition, you can use the following measurements as a consistency check or a network protection mechanism:

• hop counter violation (Item 7.13) (indicates a possible SCCP circular route) • UDTS messages sent (Item 9 bis.2) • XUDTS messages sent (Item 9 bis.14) • LUDTS messages sent (Item 9 bis.18) • UDTS messages received (Item 9 bis.4) • XUDTS messages received (Item 9 bis.16) • LUDTS messages received (Item 9 bis.20)

6.5.2 SCCP performance

UtilisationBy monitoring the SCCP utilisation you can analyse the current network and design future network configurations. One way to monitor the SCCP utilisation is to measure the amount of SCCP traffic.

t In the following lists, the item numbers in parentheses refer to the item numbers in the tables in SCCP (Signalling connection control part) measurements.

Measurements:

SCCP traffic received

• UDTS messages (Item 9 bis.4) • UDT messages (Item 9 bis.3) • XUDT messages (Item 9 bis.15) • DT1 messages/SSN (Item 9.9) • DT2 messages/SSN (Item 9.11) • ED messages/SSN (Item 9.14) • XUDTS messages (Item 9 bis.16) • LUDTS messages received (Item 9 bis.20) • total messages (connectionless classes 0 and 1 only) per SSN (Item 9.7)

SCCP traffic sent

• UDTS messages (Item 9 bis.2)

DN04143903 185



• UDT messages (Item 9 bis.1) • XUDT messages (Item 9 bis.13) • DT1 messages/SSN (Item 9.10) • DT2 messages/SSN (Item 9.12) • ED messages/SSN (Item 9.13) • XUDTS messages (Item 9 bis.14) • LUDTS messages sent (Item 9 bis.18) • total messages (connectionless classes 0 and 1 only) per SSN (Item 9.6)

General

• total messages handled (from local or remote subsystems) (Item 9.3) • total messages intended for local subsystems (Item 9.4) • total messages requiring global title translation (Item 9.5) • total messages sent to a backup subsystem (Item 9.8)

6.5.3 SCCP quality of serviceIn the following lists, the item numbers in parentheses refer to the item numbers in the tables in SCCP (Signalling connection control part) measurements.

You can estimate the SCCP (signalling connection control part) quality of service by comparing

• the number of unsuccessful UDT transfers (Items 9 bis.2 and 9 bis.4) to the total number of UDT transfers (9 bis.1 and 9 bis.3),

• the number of unsuccessful connection establishments (9 bis.6 and 9 bis.8) to the total number of establishment attempts (9 bis.5 and 9 bis.7),

• the number of resets and syntax errors detected on the existing signalling connec-tions (9 bis.9 to 9 bis.12) to the total number of successful connection establish-ments, and

• the number of unsuccessful XUDT transfers (Items 9 bis.14 and 9 bis.16) to the total number of XUDT transfers (9 bis.13 and 9 bis.15).

Connectionless outgoing traffic:

• UDT messages sent (Item 9 bis.1) • XUDT messages sent (Item 9 bis.13) • UDTS messages received (Item 9 bis.4) • XUDTS messages received (Item 9 bis.16) • LUDTS messages received (Item 9 bis.20)

Connectionless incoming traffic:

• UDT messages received (Item 9 bis.3) • XUDT messages received (Item 9 bis.15) • UDTS messages sent (Item 9 bis.2) • XUDTS messages sent (Item 9 bis.14) • LUDTS messages sent (Item 9 bis.18)

Connection oriented establishments:

Outgoing:

• CR messages sent (Item 9 bis.5) • CREF messages received (Item 9 bis.8)

186 DN04143903




Incoming:

• CR messages received (Item 9 bis.7) • CREF messages sent (Item 9 bis.6)

Connection oriented syntax/protocol errors:

• RSR messages sent/received (Items 9 bis.9 and 9 bis.10) • ERR messages sent/received (Items 9 bis.11 and 9 bis.12)

6.5.4 SCCP signalling point report (216/D8H)

Counter ID: M216B2C1 Network element name: ROUTING_FAILURE_OF_GT_TYPE_1

Version: 2.0 NetAct name: ROUTING_FAILURE_OF_GT_TYPE_1

Description: Routing error - no translation of GT type 1, 7.1 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97







Description: Routing error - no translation of GT type 2.

Updated:




Operability class:






DN04143903 187






Updated:




Operability class:









Updated:




Operability class:






Counter ID: M216B2C5 Network element name: ROUTING_FAILURE_OF_UNKNOWN_GT

Version: 2.0 NetAct name: ROUTING_FAILURE_OF_UNKNOWN_GT

Description: Routing error - no translation of unknown GT, 7.1 in ITU-T Q.752.

Updated:


188 DN04143903






Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C6 Network element name: ROUTING_FAILURE_OF_SPECIFIC_GT

Version: 2.0 NetAct name: ROUTING_FAILURE_OF_SPECIFIC_GT

Description: Routing error - no translation of specific GT, 7.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C7 Network element name: ROUTING_FAILURE_NET_FAILURE

Version: 2.0 NetAct name: ROUTING_FAILURE_NET_FAILURE

Description: Routing error - due to failure in network, 7.3 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97

DN04143903 189







Counter ID: M216B2C8 Network element name: ROUTING_FAILURE_NET_CONGESTION

Version: 2.0 NetAct name: ROUTING_FAILURE_NET_CONGESTION

Description: Routing error - due to network overload, 7.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C9 Network element name: ROUTING_FAILURE_SUBSYS_FAILURE

Version: 2.0 NetAct name: ROUTING_FAILURE_SUBSYS_FAILURE

Description: Routing error - due to failure in sussystem 7.5 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





190 DN04143903




Counter ID: M216B2C10 Network element name: ROUTING_FAILURE_SS_CONGESTION

Version: 2.0 NetAct name: ROUTING_FAILURE_SS_CONGESTION

Description: Routing error - due to subsystem overload, 7.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C11 Network element name: ROUTING_FAILURE_UNEQUIPPED_USR

Version: 2.0 NetAct name: ROUTING_FAILURE_UNEQUIPPED_USR

Description: Routing error - unequipped user, 7.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C12 Network element name: ROUTING_FAILURE_REASON_UNKNOWN

Version: 2.2 NetAct name: ROUTING_FAILURE_REASON_UNKNOWN

Description: Routing error - unknown reason, 7.9 in ITU-T Q.752.

Updated:

DN04143903 191






Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C13 Network element name: SYNTAX_ERROR_DETECTED

Version: 2.0 NetAct name: SYNTAX_ERROR_DETECTED

Description: Observed syntax errors, 7.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C14 Network element name: UDT_MESSAGES_SENT

Version: 2.0 NetAct name: UDT_MESSAGES_SENT

Description: UDT messages sent, 9bis.1 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97


192 DN04143903







Counter ID: M216B2C15 Network element name: UDT_MESSAGES_RECEIVED

Version: 2.0 NetAct name: UDT_MESSAGES_RECEIVED

Description: UDT messages received, 9bis.3 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C16 Network element name: UDTS_MESSAGES_SENT

Version: 2.0 NetAct name: UDTS_MESSAGES_SENT

Description: UDTS messages sent, 9bis.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C17 Network element name: UDTS_MESSAGES_RECEIVED

DN04143903 193



Version: 2.0 NetAct name: UDTS_MESSAGES_RECEIVED

Description: UDTS messages received, 9bis.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C18 Network element name: XUDT_MESSAGES_SENT

Version: 2.0 NetAct name: XUDT_MESSAGES_SENT

Description: XUDT messages sent, 9bis.13 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C19 Network element name: XUDT_MESSAGES_RECEIVED

Version: 2.0 NetAct name: XUDT_MESSAGES_RECEIVED

Description: XUDT messages received, 9bis.15 in ITU-T Q.752.

Updated:




194 DN04143903




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C20 Network element name: XUDTS_MESSAGES_SENT

Version: 2.0 NetAct name: XUDTS_MESSAGES_SENT

Description: XUDTS messages sent, 9bis.14 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C21 Network element name: XUDTS_MESSAGES_RECEIVED

Version: 2.0 NetAct name: XUDTS_MESSAGES_RECEIVED

Description: XUDTS messages received, 9bis.16 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 195



Counter ID: M216B2C22 Network element name: LUDT_MESSAGES_SENT

Version: 2.0 NetAct name: LUDT_MESSAGES_SENT

Description: LUDT messages sent, 9bis.17 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C23 Network element name: LUDT_MESSAGES_RECEIVED

Version: 2.0 NetAct name: LUDT_MESSAGES_RECEIVED

Description: LUDT messages received, 9bis.19 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C24 Network element name: LUDTS_MESSAGES_SENT

Version: 2.0 NetAct name: LUDTS_MESSAGES_SENT

Description: LUDTS messages sent, 9bis.18 in ITU-T Q.752.

Updated:


196 DN04143903






Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B2C25 Network element name: LUDTS_MESSAGES_RECEIVED

Version: 2.0 NetAct name: LUDTS_MESSAGES_RECEIVED

Description: LUDTS messages received, 9bis.20 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C1 Network element name: CR_MESSAGES_SENT_TO_MTP

Version: 2.0 NetAct name: CR_MESSAGES_SENT_TO_MTP

Description: ISUP embedded CRs plus CRs sent to MTP, 9bis.5 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97



DN04143903 197





Counter ID: M216B3C2 Network element name: CR_MESSAGES_RECEIVED_FROM_MTP

Version: 2.0 NetAct name: CR_MESSAGES_RECEIVED_FROM_MTP

Description: ISUP embedded CRs plus CRs received from MTP, 9bis.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C3 Network element name: CREF_MESSAGES_SENT_TO_MTP

Version: 2.0 NetAct name: CREF_MESSAGES_SENT_TO_MTP

Description: CREF messages sent to MTP, 9bis.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





198 DN04143903




Counter ID: M216B3C4 Network element name: CREF_MESSAGES_RECEIV_FROM_MTP

Version: 2.0 NetAct name: CREF_MESSAGES_RECEIV_FROM_MTP

Description: CREF messages received from MTP, 9bis.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C5 Network element name: RSR_MESSAGES_SENT_TO_MTP

Version: 2.0 NetAct name: RSR_MESSAGES_SENT_TO_MTP

Description: RSR messages sent to MTP, 9bis.9 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C6 Network element name: RSR_MESSAGES_RECEIVED_FROM_MTP

Version: 2.0 NetAct name: RSR_MESSAGES_RECEIVED_FROM_MTP

Description: RSR messages received from MTP, 9bis.10 in ITU-T Q.752.

Updated:

DN04143903 199






Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C7 Network element name: ERR_MESSAGES_SENT_TO_MTP

Version: 2.0 NetAct name: ERR_MESSAGES_SENT_TO_MTP

Description: ERR messages sent to MTP, 9bis.11 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C8 Network element name: ERR_MESSAGES_RECEIVED_FROM_MTP

Version: 2.0 NetAct name: ERR_MESSAGES_RECEIVED_FROM_MTP

Description: ERR messages received from MTP, 9bis.12 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97

200 DN04143903








Counter ID: M216B3C9 Network element name: FAILURE_REL_COMPL_SUP_DPC_CL_2

Version: 2.0 NetAct name: FAILURE_REL_COMPL_SUP_DPC_CL_2

Description: Failure of realease complete supervision, class 2, 7.15 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C10 Network element name: FAILURE_REL_COMPL_SUP_DPC_CL_3

Version: 2.0 NetAct name: FAILURE_REL_COMPL_SUP_DPC_CL_3

Description: Failure of realease complete supervision, class 3, 7.15 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 201



Counter ID: M216B3C11 Network element name: TIMER_TIAR_EXPIRY_FOR_DPC_CL_2

Version: 2.0 NetAct name: TIMER_TIAR_EXPIRY_FOR_DPC_CL_2

Description: Timer T(iar) expiry, class 2, 7.16 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C12 Network element name: TIMER_TIAR_EXPIRY_FOR_DPC_CL_3

Version: 2.0 NetAct name: TIMER_TIAR_EXPIRY_FOR_DPC_CL_3

Description: Timer T(iar) expiry, class 3, 7.16 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C13 Network element name: RESET_OF_CONNECTION_TO_DPC

Version: 2.0 NetAct name: RESET_OF_CONNECTION_TO_DPC

Description: Provider initiated reset of a connection, 7.17 in ITU-T Q.752.

Updated:

202 DN04143903







Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C14 Network element name: RELEASE_OF_CONNECTION_TO_DPC

Version: 2.0 NetAct name: RELEASE_OF_CONNECTION_TO_DPC

Description: Provider initiated release of a connection, 7.18 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C15 Network element name: SUBSYSTEM_NUMBER_1

Version: 2.0 NetAct name: SUBSYSTEM_NUMBER_1

Description: Identifier of subsystem 1

Updated:

Logical type: non-cumulative Trigger type: Event Sampling interval:



Operability class:



DN04143903 203






Counter ID: M216B3C16 Network element name: SS_CONGESTED_MESSAGES_RXED_1

Version: 2.0 NetAct name: SS_CONGESTED_MESSAGES_RXED_1

Description: SCCP / Subsystem 1 congested messages received, 8.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M216B3C17 Network element name: SS_PROHIBITED_MESSAGES_RXED_1

Version: 2.0 NetAct name: SS_PROHIBITED_MESSAGES_RXED_1

Description: Subsystem 1 prohibited messages received, 8.11 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





204 DN04143903




Counter ID: M216B3C18 Network element name: SS_ALLOWED_MESSAGES_RXED_1

Version: 2.0 NetAct name: SS_ALLOWED_MESSAGES_RXED_1

Description: Subsystem 1 allowed messages received, 8.12 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:


DN04143903 205





Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97

206 DN04143903











Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 207






Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:

208 DN04143903







Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97

DN04143903 209










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:






210 DN04143903







Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:

DN04143903 211






Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97


212 DN04143903










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 213






Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:


214 DN04143903






Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:




DN04143903 215








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97





216 DN04143903







Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:


DN04143903 217





Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97

218 DN04143903











Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 219






Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:

220 DN04143903







Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97

DN04143903 221










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:






222 DN04143903







Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:

DN04143903 223






Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97


224 DN04143903










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 225






Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:


226 DN04143903






Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:




DN04143903 227








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97





228 DN04143903







Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:


DN04143903 229





Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97

230 DN04143903











Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 231






Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:

232 DN04143903







Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97

DN04143903 233










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:






234 DN04143903







Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:

DN04143903 235






Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:









Updated:




Operability class:


ITU-T Q.752, 06/97


236 DN04143903










Updated:




Operability class:


ITU-T Q.752, 06/97








Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 237



6.5.5 SCCP subsystem report (217/D9H)

Counter ID: M217B2C1 Network element name: SS_OOS_REQUEST_GRANTED_LOCAL

Version: 2.1 NetAct name: SS_OOS_REQUEST_GRANTED_LOCAL

Description: Acceptance of a coordinated state modification request by a local subsystem, 8.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C2 Network element name: SS_OOS_REQUEST_GRANTED_REMOTE

Version: 2.1 NetAct name: SS_OOS_REQUEST_GRANTED_REMOTE

Description: Acceptance of a coordinated state modification request by a remote subsystem, 8.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C3 Network element name: SS_OOS_REQUEST_DENIED_LOCAL

Version: 2.1 NetAct name: SS_OOS_REQUEST_DENIED_LOCAL

238 DN04143903




Description: Rejection of a coordinated state modification request by a local subsystem, 8.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C4 Network element name: SS_OOS_REQUEST_DENIED_REMOTE

Version: 2.1 NetAct name: SS_OOS_REQUEST_DENIED_REMOTE

Description: Rejection of a coordinated state modification request by a remote subsystem, 8.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C5 Network element name: TOTAL_MSGS_TO_LOC_SS_NO_GT

Version: 2.1 NetAct name: TOTAL_MSGS_TO_LOC_SS_NO_GT

Description: Messages addressed to a local subsystem that do not require GT translation, 9.4 in ITU-T Q.752.

Updated:


DN04143903 239





Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C6 Network element name: TOTAL_MSGS_TO_LOC_SS_WITH_GT

Version: 2.1 NetAct name: TOTAL_MSGS_TO_LOC_SS_WITH_GT

Description: Messages addressed to a local subsystem that require GT translation, , 9.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C7 Network element name: TOTAL_MSGS_FROM_LOC_SS_NO_GT

Version: 2.1 NetAct name: TOTAL_MSGS_FROM_LOC_SS_NO_GT

Description: Messages from local subsystem that do not require GT translation, , 9.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97

240 DN04143903








Counter ID: M217B2C8 Network element name: TOTAL_MSGS_FROM_LOC_SS_WITH_GT

Version: 2.1 NetAct name: TOTAL_MSGS_FROM_LOC_SS_WITH_GT

Description: Messages from local subsystem that require GT translation, 9.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C9 Network element name: TOTAL_MESSAGES_FOR_LOCAL_SS

Version: 2.1 NetAct name: TOTAL_MESSAGES_FOR_LOCAL_SS

Description: All messages related to a local subsystem, 9.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 241



Counter ID: M217B2C10 Network element name: TOTAL_MSGS_SENT_TO_BACKUP_SS

Version: 2.1 NetAct name: TOTAL_MSGS_SENT_TO_BACKUP_SS

Description: All messages transmitted to the redundant subsystem, 9.8 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C11 Network element name: TOTAL_MESSAGES_SENT_CLASS_0

Version: 2.1 NetAct name: TOTAL_MESSAGES_SENT_CLASS_0

Description: All transmitted messages in protocol class 0, 9.6 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C12 Network element name: TOTAL_MESSAGES_SENT_CLASS_1

Version: 2.1 NetAct name: TOTAL_MESSAGES_SENT_CLASS_1

Description: All transmitted messages in protocol class 1.

Updated:

242 DN04143903







Operability class:






Counter ID: M217B2C13 Network element name: TOTAL_MESSAGES_RXED_CLASS_0

Version: 2.1 NetAct name: TOTAL_MESSAGES_RXED_CLASS_0

Description: All messages received in protocol class 0, 9.7 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C14 Network element name: TOTAL_MESSAGES_RXED_CLASS_1

Version: 2.1 NetAct name: TOTAL_MESSAGES_RXED_CLASS_1

Description: All messages received in protocol class 1.

Updated:




Operability class:



DN04143903 243






Counter ID: M217B2C15 Network element name: DT_1_MESSAGES_RECEIV_FROM_MTP

Version: 2.1 NetAct name: DT_1_MESSAGES_RECEIV_FROM_MTP

Description: DT1 messages received from MTP per sink SSN, 9.9 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C16 Network element name: DT_1_MESSAGES_SENT_TO_MTP

Version: 2.1 NetAct name: DT_1_MESSAGES_SENT_TO_MTP

Description: DT1 messages sent to MTP per source SSN, 9.10 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





244 DN04143903




Counter ID: M217B2C17 Network element name: DT_2_MESSAGES_RECEIV_FROM_MTP

Version: 2.1 NetAct name: DT_2_MESSAGES_RECEIV_FROM_MTP

Description: DT2 messages received from MTP per sink SSN, 9.11 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C18 Network element name: DT_2_MESSAGES_SENT_TO_MTP

Version: 2.1 NetAct name: DT_2_MESSAGES_SENT_TO_MTP

Description: DT2 messages sent to MTP per source SSN, 9.12 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C19 Network element name: ED_MESSAGES_RECEIVED_FROM_MTP

Version: 2.1 NetAct name: ED_MESSAGES_RECEIVED_FROM_MTP

Description: ED messages received from MTP per sink SSN, 9.14 in ITU-T Q.752.

Updated:

DN04143903 245






Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C20 Network element name: ED_MESSAGES_SENT_TO_MTP

Version: 2.1 NetAct name: ED_MESSAGES_SENT_TO_MTP

Description: ED messages sent to MTP per source SSN, 9.13 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C21 Network element name: LOCAL_SS_PROHIBITED_START

Version: 2.1 NetAct name: LOCAL_SS_PROHIBITED_START

Description: Start of local subsystem prohibited, 8.9 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97


246 DN04143903







Counter ID: M217B2C22 Network element name: LOCAL_SS_PROHIBITED_STOP

Version: 2.1 NetAct name: LOCAL_SS_PROHIBITED_STOP

Description: Stop of local subsystem prohibited, 8.10 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M217B2C23 Network element name: MSGS_TOO_BIG_FOR_SEGMENTATION

Version: 2.1 NetAct name: MSGS_TOO_BIG_FOR_SEGMENTATION

Description: Messages too large for segmentation, 7.14 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





DN04143903 247



6.5.6 SCCP local subsystem availability report (218/DAH)

Counter ID: M218B2C1 Network element name: START_LOC_SCCP_UNAV_FAILURE

Version: 2.0 NetAct name: START_LOC_SCCP_UNAV_FAILURE

Description: Start of unavailability of a local SCCP due to failure, 8.1 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M218B2C2 Network element name: START_LOC_SCCP_UNAV_MAINT_BUSY

Version: 2.0 NetAct name: START_LOC_SCCP_UNAV_MAINT_BUSY

Description: Start of unavailability of a local SCCP due to maintenance busy, 8.2 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M218B2C3 Network element name: START_LOC_SCCP_UNAV_MAINT_CONG

Version: 2.0 NetAct name: START_LOC_SCCP_UNAV_MAINT_CONG

Description: Start of unavailability of a local SCCP due to congestion, 8.3 in ITU-T Q.752.

248 DN04143903




Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M218B2C4 Network element name: STOP_OF_LOCAL_SCCP_UNAVAILABLE

Version: 2.0 NetAct name: STOP_OF_LOCAL_SCCP_UNAVAILABLE

Description: Stop of unavailability of a local SCCP, 8.4 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M218B2C5 Network element name: DURA_OF_LOCAL_SCCP_UNAVAILABLE

Version: 2.0 NetAct name: DURA_OF_LOCAL_SCCP_UNAVAILABLE

Description: Duration of the unavailability of a local SCCP, 8.5 in ITU-T Q.752.

Updated:




Operability class:

DN04143903 249



6.5.7 SCCP single meters' report (219/DBH)


ITU-T Q.752, 06/97





Counter ID: M219B2C1 Network element name: SCCP_MSGS_TO_LOCAL_SUBSYSTEM

Version: 2.0 NetAct name: SCCP_MSGS_TO_LOCAL_SUBSYSTEM

Description: Processed SCCP messages to local subsystem.

Updated:




Operability class:






Counter ID: M219B2C2 Network element name: SCCP_MSGS_FROM_LOCAL_SUBSYSTEM

Version: 2.0 NetAct name: SCCP_MSGS_FROM_LOCAL_SUBSYSTEM

Description: Processed SCCP messages from local subsystem.

Updated:




Operability class:






250 DN04143903




Counter ID: M219B2C3 Network element name: SCCP_STP_MESSAGES_HANDLED

Version: 2.0 NetAct name: SCCP_STP_MESSAGES_HANDLED

Description: Processed STP messages to local subsystem.

Updated:




Operability class:






Counter ID: M219B2C4 Network element name: USER_INDEPENDENT_MESSAGES

Version: 2.0 NetAct name: USER_INDEPENDENT_MESSAGES

Description: Processed user independent SCCP messages.

Updated:




Operability class:






Counter ID: M219B2C5 Network element name: TOTAL_SCCP_MESSAGES_HANDLED

Version: 2.0 NetAct name: TOTAL_SCCP_MESSAGES_HANDLED

Description: Processed SCCP messages, total. 9.3 in ITU-T Q.752.

Updated:


DN04143903 251





Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C6 Network element name: MSGS_REQ_GTT_TO_LOCAL_SUBSYS

Version: 2.0 NetAct name: MSGS_REQ_GTT_TO_LOCAL_SUBSYS

Description: Messages requiring GT translation to local subsystem.

Updated:




Operability class:






Counter ID: M219B2C7 Network element name: MSGS_REQ_GTT_FROM_LOCAL_SUBSYS

Version: 2.0 NetAct name: MSGS_REQ_GTT_FROM_LOCAL_SUBSYS

Description: Messages requiring GT translation from local subsystem.

Updated:




Operability class:




252 DN04143903






Counter ID: M219B2C8 Network element name: SCCP_STP_MSGS_REQUIRING_GTT

Version: 2.0 NetAct name: SCCP_STP_MSGS_REQUIRING_GTT

Description: STP messages requiring GT translation.

Updated:




Operability class:






Counter ID: M219B2C9 Network element name: TOTAL_MESSAGES_REQUIRING_GTT

Version: 2.0 NetAct name: TOTAL_MESSAGES_REQUIRING_GTT

Description: Messages requiring GT translation, total. 9.5 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C10 Network element name: REASS_ERRORS_TIMER_EXPIRES

DN04143903 253



Version: 2.0 NetAct name: REASS_ERRORS_TIMER_EXPIRES

Description: Reassembly error, Timer T(reass) expiry, 7.10 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C11 Network element name: REASS_ERRORS_SEGM_OUT_OF_SEQ

Version: 2.0 NetAct name: REASS_ERRORS_SEGM_OUT_OF_SEQ

Description: Reassembly error, Segment received out of sequence, 7.11 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C12 Network element name: REASS_ERRORS_NO_REASS_SPACE

Version: 2.0 NetAct name: REASS_ERRORS_NO_REASS_SPACE

Description: Reassembly error, no reassembly space, 7.12 in ITU-T Q.752.

Updated:



254 DN04143903





Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C13 Network element name: REASS_ERRORS_REASSEMBLY_FAILED

Version: 2.0 NetAct name: REASS_ERRORS_REASSEMBLY_FAILED

Description: Reassembly error, Reassembly failed, 7.21 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C14 Network element name: SEGM_ERRORS_SEGM_NOT_SUPPORTED

Version: 2.0 NetAct name: SEGM_ERRORS_SEGM_NOT_SUPPORTED

Description: Segmentation error - Segmenting not supported, 7.19 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97


DN04143903 255






Counter ID: M219B2C15 Network element name: SEGM_ERRORS_SEGMENTATION_FAIL

Version: 2.0 NetAct name: SEGM_ERRORS_SEGMENTATION_FAIL

Description: Segmentation error - Segmentation failed, 7.20 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





Counter ID: M219B2C16 Network element name: HOP_COUNTER_VIOLATIONS

Version: 2.0 NetAct name: HOP_COUNTER_VIOLATIONS

Description: Hop counter violation, 7.13 in ITU-T Q.752.

Updated:




Operability class:


ITU-T Q.752, 06/97





256 DN04143903




6.6 1st+ interval log reports 1st + interval log reports are used to report and detect faults, and monitor the signalling network response to abnormal conditions. They are generated 5min periods only if there is an error event occurrence during the period.

The following is an example of a 1st+ Interval log report:

Example: XXX 1ST+INTERVAL LOG REPORT PART n, LAST PART

INTERVAL LOG REPORT NAME

MEASUREMENT PERIOD START : 2004-01-09 16:00:00 END : 2004-01-09 16:05:00

. . log information . .

END OF LAST PART

END OF REPORT

Identification data

• XXX 1ST+INTERVAL LOG REPORTIdentification of the CCS 1st + interval log report, XXX being either MTP, SCCP, or TC

• PART n, LAST PARTInternal sequence number of the report. The outputs of the report have been inter-nally numbered. The last output is separated from the others (LAST PART). Thus the report can end in one of the following ways: • END OF PART n, REPORT CONTINUES • END OF LAST PART

• INTERVAL LOG REPORT NAMEStandard name of the report

• MEASUREMENT PERIOD STARTTime when the measurement period begins

• MEASUREMENT PERIOD STOPTime when the measurement period ends

6.6.1 Signalling link log report

MTP 1ST+INTERVAL LOG REPORT PART 1, LAST PART

SIGNALLING LINK LOG

MEASUREMENT PERIOD START : 2001-02-26 16:00:00

DN04143903 257



END : 2001-02-26 16:05:00

SIGNALLING LINK NUMBER : 0SIGNALLING LINK TYPE : TDM BASED

NETWORK NAME : IN0SIGNALLING POINT NUMBER : 240HSIGNALLING LINK SET NAME : MSC1

SIGNALLING LINK LOAD THRESHOLD EXCEEDED (0.100 ERLANGS) INCOMING TRAFFIC : 0.079 ERLANGS OUTGOING TRAFFIC : 0.079 ERLANGS

SIGNALLING LINK CONGESTION LEVELS : L1 L2 L3 INDICATIONS : 1 0 0 EVENTS RESULTING IN LOSS OF MSUS: 1 0 0

END OF LAST PART

END OF REPORT

6.6.2 MTP signalling point log report

MTP 1ST+INTERVAL LOG REPORT PART 1, LAST PART

SIGNALLING POINT LOG


NETWORK NAME : NA0

SIGNALLING POINT NUMBER : 240H

NUMBER OF RECEIVED TFC CONCERNING SP : 2 AT CONGESTION LEVEL(S) : 1 2

MSU DISCARD DUE TO ROUTING DATA ERROR FOR TRANSMITTED MSUS : 2 RECEIVED MSUS : 1

UPUS TRANSMITTED : 1FOR SIO NB/ : 85H/ISUPUSER PART NAME

UPUS RECEIVED : 3FOR SIO NB/ : 85H/ISUPUSER PART NAME

258 DN04143903




END OF LAST PART

END OF REPORT

6.6.3 SCCP signalling point log report

SCCP 1ST+INTERVAL LOG REPORT PART 1, LAST PART

SCCP SIGNALLING POINT LOG


NETWORK NAME : NA0

SIGNALLING POINT NUMBER : 240H

PROTOCOL CLASS : CLASS 2FAILURE OF RELEASE COMPLETE SUPERVISION FOR DPC : 1TIMER T(IAR) EXPIRY FOR DPC : 3

PROVIDER INITIATED RESET OF A CONNECTION TO DPC : 1PROVIDER INITIATED RELEASE OF A CONNECTION TO DPC : 1

ROUTING FAILURE(S) : NO TRANSLATION FOR GLOBAL TITLE TYPE 1 : 1 FIRST EVENT : MESSAGE TYPE : UDT MESSAGE DIRECTION : FROM NETWORK CALLED PARTY ADDRESS: STANDARD : ITU-T ROUTING : ROUTE ON SSN SP CODE : 240H SSN : 4H TREATMENT : SPC INSERTED TO ADDRESS GT INDICATOR : 4 TRANSLATION TYPE : 1 ENCODING SCHEME : BCD ODD NUMBER OF DIGITS NUMBERING PLAN : 6 LAND MOBILE (REC. E.212) NATURE OF ADDRESS : 1 SUBSCRIBER NUMBER GT DIGITS : 123 CALLING PARTY ADDRESS: STANDARD : ITU-T ROUTING : ROUTE ON GT SP CODE : 270H SSN : 6H TREATMENT : SPC INSERTED TO ADDRESS GT INDICATOR : 1 TRANSLATION TYPE : -

DN04143903 259



ENCODING SCHEME : - NUMBERING PLAN : - NATURE OF ADDRESS : 1 SUBSCRIBER NUMBER GT DIGITS : 123456789012345678901234

NO TRANSLATION FOR GLOBAL TITLE TYPE 2 : 1 FIRST EVENT : . . .



NO TRANSLATION FOR UNKNOWN GLOBAL TITLE TYPE : 1 FIRST EVENT : . . .

NO TRANSLATION FOR SPECIFIC GLOBAL TITLE : 1 FIRST EVENT : . . .

NETWORK FAILURE : 1 FIRST EVENT : . . .

NETWORK CONGESTION : 1 FIRST EVENT : . . .

SUBSYSTEM FAILURE : 1 FIRST EVENT : . .

260 DN04143903




.

SUBSYSTEM CONGESTION : 1 FIRST EVENT : . . .

UNEQUIPPED USER : 1 FIRST EVENT : . . .

REASON UNKNOWN : 1 FIRST EVENT : . . .

SYNTAX ERROR DETECTED : 1 FIRST EVENT : . . .

SUBSYSTEM METERS :SUBSYSTEM NUMBER : 4 HSUBSYSTEM NAME : OMAP SUBSYSTEM PROHIBITED MESSAGES RECEIVED : 3 SCCP/SUBSYSTEM CONGESTED MESSAGES RECEIVED : 1 FIRST EVENT CONGESTION LEVEL : 1

END OF LAST PART

END OF REPORT

6.6.4 SCCP reassembly and segmentation errors log report

SCCP 1ST+INTERVAL LOG REPORT PART 1, LAST PART

SCCP REASSEMBLY AND SEGMENTATION LOG


REASSEMBLY ERRORS: NO REASSEMBLY SPACE : 0 FIRST EVENT :

DN04143903 261



NETWORK : NA0 DPC : 240H MESSAGE TYPE : UDT MESSAGE DIRECTION : FROM NETWORK SEGMENTATION LOCAL REFERENCE : 563412H CALLED PARTY ADDRESS: STANDARD : ITU-T ROUTING : ROUTE ON SSN SP CODE : 260H SSN : - TREATMENT : SPC INSERTED TO ADDRESS GT INDICATOR : 4 TRANSLATION TYPE : 1 ENCODING SCHEME : BCD ODD NUMBER OF DIGITS NUMBERING PLAN : 6 LAND MOBILE (REC. E.212) NATURE OF ADDRESS : 1 SUBSCRIBER NUMBER GT DIGITS : 123 CALLING PARTY ADDRESS: STANDARD : ITU-T ROUTING : ROUTE ON GT SP CODE : 270H SSN : 6H TREATMENT : SPC INSERTED TO ADDRESS GT INDICATOR : - TRANSLATION TYPE : - ENCODING SCHEME : - NUMBERING PLAN : - NATURE OF ADDRESS : - GT DIGITS : -

REASSEMBLY FAILED : 0 FIRST EVENT : . . .

TIMER T(REASS) EXPIRY : 0 FIRST EVENT : . . .

SEGMENT RECEIVED OUT OF SEQUENCE : 0 FIRST EVENT : . . .

HOP COUNTER VIOLATION : 0 FIRST EVENT :

262 DN04143903




. . .

SEGMENTATION ERRORS: SEGMENTING NOT SUPPORTED : 0 FIRST EVENT : . . .

SEGMENTATION FAILED : 0 FIRST EVENT : . . .

MESSAGES TOO LARGE FOR SEGMENTATION : 0 CALLING SUBSYSTEM : 04H CALLING SUBSYSTEM NAME : OMAP FIRST EVENT : . . .

END OF LAST PART

END OF REPORT

DN04143903 263

RNC Counters - Transport and HW Part ATM transport measurements

Id:0900d805809a87dfConfidential

7 ATM transport measurementsThe transport layer protocol measurements provide performance statistics for specific ATM and IP layer protocols.

The figure RAN ATM connections shows the different ATM connections used in the radio access networks (RAN). The table Measurements used for ATM connections describes which measurements can be used to measure the ATM connections shown in the figure.

Figure 9 RAN ATM connections

AXC

AAL2UP

AAL2UP

AAL2SL

MTP3SL (AAL5)

IPOA (AAL5)

CNBAP (AAL5)

DNBAP (AAL5)

MGW MSS

AAL2UP

DNBAP

CNBAP

AAL2SL

IPOA O&M

BTS

IPOA UD

DRNC

MTP3SL

AAL2UP

SGSN

MTP3SL

MTP3SL

RNC

lub

lur

lu-PS lu-CS

DN05154093

ID AAL2UP AAL2SL MTP3SL IPOA CNBAP DNBAP

529/211H X X X X X X

530/212H X X X X X X

531/213H X

532/214H X X X X X X

546/222H X X X

548/224H X

550/226H X

Table 19 Measurements used for ATM connections

264 DN04143903



ATM transport measurements

7.1 ATM layer performance measurement (528/210H)The ATM layer performance measurement provides statistics about ATM layer traffic management actions. It also provides information about the amount of traffic passing through the ATM switching units.

The object is computer unit that is identified by unit type and index. The supported computer units are MXU, NIP and NIS. Note however that the MXU variant used in RNC2600 does not support this measurement and therefore the measurement is not usable at all in RNC2600 as there are no NIS or NIP units either.

552/228H X

553/229H X

800/320H X

ID AAL2UP AAL2SL MTP3SL IPOA CNBAP DNBAP

Table 19 Measurements used for ATM connections (Cont.)

Counter ID: M528C2 Network element name: I_CLP1_DROP

Version: 5.1 NetAct name: I_CLP1_DROP

Description: Total ingress CLP1 cells discarded because of thresholding. This counter tells how many low priority cells buffer management has discarded on ingress. When the buffer fill level exceeds the CLP1 threshold, only CLP0 cells are accepted to the buffer and CLP1 cells are discarded. When the buffer fill level exceeds the CLP0+1 threshold, no cells are accepted to the buffer (all cells are discarded). The CLP1 cells that are discarded because of CLP1 and CLP0+1 thresholds are counted by this counter. CLP1 and CLP0+1 thresholding parameters are fixed by the system.

Updated: When an ingress cell is discarded because of thresholding.









Used from release: U1.5/RN1.5 Definition updated in release:

Counter ID: M528C3 Network element name: I_PPD_DROP

Version: 5.1 NetAct name: I_PPD_DROP

Description: Total cells discarded to PPD on ingress. Partial Packet Discard (PPD) discards all the cells associated with the packet discarded during buffer overflow.

Updated: When PPD in buffer management discards an ingress cell.



DN04143903 265










Counter ID: M528C4 Network element name: I_EPD_DROP

Version: 5.1 NetAct name: I_EPD_DROP

Description: Total cells discarded to EPD on ingress. When congestion occurs and buffers are filling up, Early Packet Discard (EPD) discards new packets arriving in the queue. All cells associated with a new packet are discarded. The remaining buffer space can then be used for ATM cells belonging to packets that are already in the queue.

Updated: When EPD in buffer management discards a packet on ingress.










Counter ID: M528C5 Network element name: I_FRAMES_EPD_DROP

Version: 5.1 NetAct name: I_FRAMES_EPD_DROP

Description: Total frames discarded to EPD on ingress. Total number of frames (AAL5 packets) that Early Packet Discard (EPD) discards. EPD counts discarded AAL5 frames, that is, the packet objects to which EPD discarding refers.

Updated: When the cells that belong to the frame to be discarded are entering the ATM cell buffer.








266 DN04143903






Counter ID: M528C8 Network element name: E_CLP1_DROP

Version: 5.1 NetAct name: E_CLP1_DROP

Description: Total egress CLP1 cells discarded because of thresholding. This counter tells how many low priority cells buffer management has discarded on egress. When the buffer fill level exceeds the CLP1 threshold, only CLP0 cells are accepted to the buffer and CLP1 cells are discarded. When the buffer fill level exceeds the CLP0+1 threshold, no cells are accepted to the buffer (all cells are discarded). The CLP1 cells that are discarded because of CLP1 and CLP0+1 thresholds are counted by this counter. CLP1 and CLP0+1 thresholding parameters are fixed by the system.

Updated: When an egress cell is discarded because of thresholding.










Counter ID: M528C9 Network element name: E_PPD_DROP

Version: 5.1 NetAct name: E_PPD_DROP

Description: Total cells discarded by PPD on egress. Partial Packet Discard (PPD) discards all the cells associated with the packet discarded during buffer overflow.

Updated: When PPD of buffer management discards an egress cell.










DN04143903 267



Counter ID: M528C10 Network element name: E_EPD_DROP

Version: 5.1 NetAct name: E_EPD_DROP

Description: Total cells discarded to EPD on egress. When congestion occurs and buffers are filling up, Early Packet Discard (EPD) discards new packets arriving in the queue. All cells associated with a new packet are discarded. The remaining buffer space can then be used for ATM cells belonging to packets that are already in the queue.

Updated: When EPD in buffer management discards a packet on egress.










Counter ID: M528C11 Network element name: E_FRAMES_EPD_DROP

Version: 5.1 NetAct name: E_FRAMES_EPD_DROP

Description: Total frames discarded to EPD on egress. The total number of frames (AAL5 packets) that Early Packet Discard (EPD) discards. EPD counts discarded AAL5 frames, that is, the packet objects to which EPD discarding refers.

Updated: When cells that belong to the frame to be discarded are entering the ATM cell buffer.










Counter ID: M528C16 Network element name: I_CLP0_DROP

Version: 5.1 NetAct name: I_CLP0_DROP

268 DN04143903




Description: Total ingress CLP0 cells discarded because of thresholding. This counter tells how many high priority cells buffer management has discarded on ingress. When the buffer fill level exceeds the CLP0+1 threshold, no cells are accepted to the buffer. Both CLP0 and CLP1 cells are discarded. Dis-carded CLP1 cells are counted in counter I_CLP1_DROP M528C2. CLP0+1 thresholding parameters are fixed by the system.

Updated: When an ingress cell is discarded because of thresholding.










Counter ID: M528C17 Network element name: I_TRANSMIT_TO_FABRIC

Version: 5.1 NetAct name: I_TRANSMIT_TO_FABRIC

Description: The total number of ingress cells successfully transmitted to the multiplexer or to the switch fabric. In NIP1 unit, the counter also includes egress cells due to hardware implementation issues.

Updated: When an ingress cell is successfully transmitted to the multiplexer or to the switch fabric. In NIP1 unit, due to hardware implementation issues, this counter is also updated when an egress cell trans-mitted.










Counter ID: M528C18 Network element name: I_TAGGED

Version: 5.1 NetAct name: I_TAGGED

Description: Ingress cells tagged because of policing action. This counter tells how many higher priority cells have been tagged to lower priority by Usage Parameter Control (UPC) or Network Parameter Control (NPC).

Updated: When an ingress cell is tagged.

DN04143903 269












Counter ID: M528C19 Network element name: I_POLICING_DROP

Version: 5.1 NetAct name: I_POLICING_DROP

Description: Ingress cells discarded because of policing action. Policing discards the cells which can affect the QoS of established connections (cells which violate traffic contract). Policing at UNI is referred to as UPC (usage parameter control). Policing at NNI is referred to as NPC (network parameter control).

Updated: When an ingress cell violates the traffic contract (for example, Peak Cell Rate exceeds the max-imum). Discarding is done according to generic cell rate algorithm (GCRA).










Counter ID: M528C20 Network element name: I_ERR_BRAM

Version: 5.1 NetAct name: I_ERR_BRAM

Description: Ingress cells discarded because of a checksum error. If a checksum error is detected when a cell is read from the buffer memory, the cell is discarded.

Updated: If an ingress cell is corrupted.







270 DN04143903







Counter ID: M528C21 Network element name: I_UTOPIA_ERR

Version: 5.1 NetAct name: I_UTOPIA_ERR

Description: Ingress cells discarded because of parity errors on the UTOPIA interface. The number of cells when an error was detected as a result of a parity check on the Universal Test & Operations Inter-face for ATM.

Updated: When an ingress cell is discarded on the UTOPIA interface.










Counter ID: M528C22 Network element name: I_ERR_CRC

Version: 5.1 NetAct name: I_ERR_CRC

Description: Ingress cells discarded because of a Cyclic Redundancy Check (CRC) error. The number of Operations, Administration and Maintenance (OAM) and Resource Management (RM) cells detecting errors in the transmission of data using a polynomial code and a cyclic check character.

Updated: When an ingress OAM or RM cell is discarded because of a CRC error.










DN04143903 271



Counter ID: M528C23 Network element name: I_ERR_HEADER

Version: 5.1 NetAct name: I_ERR_HEADER

Description: Total ATM header errors. This bit indicates that an invalid VPI/VCI was detected in an ingress cell. Invalid VPI/VCI includes: VPI values greater than the configured maximum, VCI values greater than the configured maximum, and VCI values less than 32 for which the valid bit is not set in the Look-up Compression Table.

Updated: If an ingress cell with a header error is detected on lookup.










Counter ID: M528C24 Network element name: E_CLP0_DROP

Version: 5.1 NetAct name: E_CLP0_DROP

Description: Total egress CLP0 cells discarded because of thresholding. This counter tells how many high priority cells buffer management has discarded on egress. When the buffer fill level exceeds the CLP0+1 threshold, no cells are accepted to the buffer. Both CLP0 and CLP1 cells are discarded. Dis-carded CLP1 cells are counted in counter E_CLP1_DROP M528C8. The CLP0+1 thresholding parame-ters are fixed by the system.

Updated: When an egress cell is discarded because of thresholding.










Counter ID: M528C25 Network element name: E_TRANSMIT_TO_PHY

Version: 5.1 NetAct name: E_TRANSMIT_TO_PHY

272 DN04143903




Description: Total number of egress cells successfully transmitted to the PHY devices. The count of cells transmitted to the physical layer. In NIP1 unit, the counter also includes ingress cells due to hardware implementation issues.

Updated: When an egress cell is successfully transmitted to PHY. In NIP1 unit, due to hardware imple-mentation issues, this counter is also updated when an ingress cell transmitted.










Counter ID: M528C26 Network element name: E_ERR_BRAM

Version: 5.1 NetAct name: E_ERR_BRAM

Description: Egress cells discarded because of a checksum error. If a checksum error is detected when a cell is read from the buffer memory, the cell is discarded.

Updated: If an egress cell is corrupted.










Counter ID: M528C27 Network element name: E_RCV_FROM_FI

Version: 5.1 NetAct name: E_RCV_FROM_FI

Description: Total egress cells received at the fabric interface. In NIP1 unit, the fabric interface is an internal concept and due to hardware implementation issues, this counter includes all ingress and egress cells and are counted twice.

Updated: When an egress cell is received from the switching fabric. In NIP1 unit, the switching fabric is an internal concept and due to hardware implementation issues, this counter is updated twice for every ingress and egress cell.


DN04143903 273











Counter ID: M528C28 Network element name: E_ERR_FI

Version: 5.1 NetAct name: E_ERR_FI

Description: Total number of egress cells discarded because of parity errors in the fabric interface.

Updated: If a parity error in internal proprietary packets is detected.










Counter ID: M528C29 Network element name: E_ERR_LOOKUP

Version: 5.1 NetAct name: E_ERR_LOOKUP

Description: Egress cells discarded on connection lookup. When a cell is received, the information about the connection is read from the header. The cell is discarded because of a wrong destination or erroneous source parameters.

Updated: If an egress cell is discarded on lookup because of an error.









274 DN04143903




7.2 ATM virtual path connection measurement (529/211H)This measurement reports the average traffic rate of ATM virtual path connection during the measurement period. All types of ATM VP connections that are switched through or terminated into RNC ATM interface units can be selected as measured objects.

The object of the measurement is ATM virtual path and the measured paths are selected with ATM interface ID/VPI identifiers. The measurement identifier is 529/211H.

This measurement is optional and available as a part of RAS05 feature ATM VP/VC traffic measurement.


Counter ID: M529C0 Network element name: IN_TOT_CELLS_VP

Version: 3.3 NetAct name: IN_TOT_CELLS_VP

Description: The number of ingress cells transmitted through a virtual path connection in the ingress direction. The received cells are partly stored in the buffer, the other cells will be transmitted. But some cells are dropped without transmitted.

Updated: When an ATM cell is transmitted through a virtual path connection in the ingress direction.


Unit: cell Range: Example values: 200



Related to feature:

RAN 224: ATM VP/VC traffic measurement

RAN 1.037: ATM based Iub/Iur






Counter ID: M529C1 Network element name: EG_TOT_CELLS_VP

Version: 3.3 NetAct name: EG_TOT_CELLS_VP

Description: The number of egress cells transmitted to a virtual path connection in the egress direc-tion.The received cells are partly stored in the buffer, the other cells will be transmitted. But some cells are dropped without transmitted.

Updated: When an ATM cell is transmitted to a virtual path connection in the egress direction.





DN04143903 275



Related to feature:








Counter ID: M529C2 Network element name: IN_REC_CELLS_VP

Version: 1.0 NetAct name: IN_REC_CELLS_VP

Description: The number of ingress cells received from a virtual path connection.

Updated: When an ATM cell is received to the ATM interface unit for the ATM VP connection (ingress).


Unit: cell Range: Example values:



Related to feature:

RAN 1095: UBR+ for Iub User Plane








Counter ID: M529C3 Network element name: IN_QUEUED_CELLS_VP

Version: 1.0 NetAct name: IN_QUEUED_CELLS_VP

Description: The number of ingress cells in virtual path connection level queue(s).

Updated: The counter is updated at the end of the measurement period by the number of ATM cells in the ingress virtual path level queue(s).





276 DN04143903




Related to feature:









Counter ID: M529C4 Network element name: IN_CAP_VP

Version: 1.0 NetAct name: IN_CAP_VP

Description: The configured ingress bandwidth for the virtual path connection. This counter is always zero for virtual path connection termination points since the ingress peak cell rate is not defined for those con-nections.

Updated: This value is sampled at the end of the measurement period.




Operability class:

Related to feature:

RAN 759: Path Selection








Counter ID: M529C5 Network element name: EG_REC_CELLS_VP

Version: 1.0 NetAct name: EG_REC_CELLS_VP

Description: The number of egress cells received from a virtual path connection.

Updated: When an ATM cell is received from the switch fabric direction to the ATM interface unit for the ATM VP connection (egress).





DN04143903 277



Related to feature:









Counter ID: M529C6 Network element name: EG_QUEUED_CELLS_VP

Version: 1.0 NetAct name: EG_QUEUED_CELLS_VP

Description: The number of egress cells in virtual path connection level queue(s).

Updated: The counter is updated at the end of the measurement period by the number of ATM cells in the egress virtual path level queue(s).





Related to feature:









Counter ID: M529C7 Network element name: EG_CAP_VP

Version: 1.0 NetAct name: EG_CAP_VP

Description: The configured egress bandwidth for the virtual path connection.





Operability class:

278 DN04143903




7.3 ATM virtual channel connection measurement (530/212H)This measurement reports the average traffic rate of ATM virtual channel connection (VCC) during measurement period. All types of ATM VC connections that are switched through or terminated into RNC ATM interface units can be selected as measured objects. The measurement identifier is 530/212H. This measurement is optional and available as a part of RAS05 feature ATM VP/VC traffic measurement.

The object identifiers are ATM interface-ID/VPI/VCI, WBTS ID, and AAL usage.

The WBTS ID identifies the base station even though it is actually a transient measure-ment identifier because it can also have the not known value. The not known value is used when the connection is not an Iub connection or it is an Iub O&M link.

The possible AAL2 usage values for this measurement are AAL2UD, AAL2SL, CNBAP, DNBAP and not known. The not known value is used for those ATM VC connections for which the service type is not known, that is, IP-over-ATM O&M link in the Iub-interface Iu and Iur VCCs.

The measurement is done from RNC ATM interface unit as shown in figure An example of ATM VC connections between RNC and BTS that can be selected for the ATM virtual channel connection measurement. so for the egress the traffic has passed through ATM and AAL2 layer traffic management actions and for ingress the traffic management is not done for measured ATM VC connection.

The ATM VCC measurement enables monitoring the ATM layer traffic load of for example NBAP signalling, NodeB O&M traffic and AAL2 multiplexed user plane traffic since these all have one or more dedicated VCC between the RNC and NodeB. The object of the measurement is ATM virtual channel connection and the measured con-nections are selected with ATM interface ID/VPI/VCI identifiers. The measurement iden-tifier is 530/212H.

One possible ATM VC configuration for one BTS through RNC external interface is pre-sented in figure An example of ATM VC connections between RNC and BTS that can be selected for the ATM virtual channel connection measurement.

Related to feature:

RAN 759: Path Selection








DN04143903 279



Figure 10 An example of ATM VC connections between RNC and BTS that can be selected for the ATM virtual channel connection measurement

Counters M530C8-M530C21, related to feature RAN2105 Bandwidth utilization classes counters for VC and bundle, are available only if the RNC license for RAN2105 is installed (feature code 1898).

ATM interface

ATM interface

ATM

interface

unit

(NIP1/NIS(P)/NPS1(P))

MGW/RNC

AXC

MGW ATM VCC forAAL2UD

ATM VCC forMTP3

ATM VCC forPVC

Counter ID: M530C0 Network element name: IN_TOT_CELLS_VC

Version: 3.3 NetAct name: IN_TOT_CELLS_VC

Description: The number of ingress cells transmitted through a virtual channel connection in the ingress direction. The received cells are partly stored in the buffer, the other cells will be transmitted. But some cells are dropped without transmitted.

Updated: When an ATM cell is transmitted through a virtual channel connection in the ingress direction.





Related to feature:








Counter ID: M530C1 Network element name: EG_TOT_CELLS_VC

Version: 3.3 NetAct name: EG_TOT_CELLS_VC

280 DN04143903




Description: The number of egress cells transmitted to a virtual channel connection in the egress direc-tion. The received cells are partly stored in the buffer, the other cells will be transmitted. But some cells are dropped without transmitted.

Updated: When an ATM cell is transmitted to a virtual channel connection in the egress direction.





Related to feature:








Counter ID: M530C2 Network element name: IN_REC_CELLS_VC

Version: 1.0 NetAct name: IN_REC_CELLS_VC

Description: The number of ingress cells received from a virtual channel connection.

Updated: When an ATM cell is received to the ATM interface unit for the ATM VC connection (ingress).





Related to feature:









Counter ID: M530C3 Network element name: IN_QUEUED_CELLS_VC

Version: 1.0 NetAct name: IN_QUEUED_CELLS_VC

Description: The number of ingress cells in virtual channel connection level queue(s).

Updated: This counter is updated at the end of the measurement period by the number of ATM cells in the ingress virtual channel level queue(s).

DN04143903 281







Related to feature:









Counter ID: M530C4 Network element name: IN_CAP_VC

Version: 4.2 NetAct name: IN_CAP_VC

Description: The configured ingress bandwidth for the virtual channel connection. For UBR+ VCC the value is MDCR.





Operability class:

Related to feature:

RAN 759: Path SelectionRAN 224: ATM VP/VC traffic measurement RAN 1.037: ATM based Iub/Iur






Counter ID: M530C5 Network element name: EG_REC_CELLS_VC

Version: 1.0 NetAct name: EG_REC_CELLS_VC

Description: The number of egress cells received from a virtual channel connection.

Updated: When an ATM cell is received from the switch fabric direction to the ATM interface unit for the ATM VC connection (egress).



282 DN04143903






Related to feature:









Counter ID: M530C6 Network element name: EG_QUEUED_CELLS_VC

Version: 1.0 NetAct name: EG_QUEUED_CELLS_VC

Description: The number of egress cells in virtual channel connection level queue(s).

Updated: This counter is updated at the end of the measurement period by the number of ATM cells in the egress virtual channel level queue(s).





Related to feature:









Counter ID: M530C7 Network element name: EG_CAP_VC

Version: 4.2 NetAct name: EG_CAP_VC

Description: The configured egress bandwidth for the virtual channel connection. For UBR+ VCC the value is MDCR.





Operability class:

DN04143903 283



Related to feature:

RAN 759: Path SelectionRAN 224: ATM VP/VC traffic measurement RAN 1.037: ATM based Iub/Iur






Counter ID: M530C8 Network element name: VC_EG_BW_UTI_CLASS_1

Version: 4.1 NetAct name: VC_EG_BW_UTI_CLASS_1

Description: The number of samples where the ATM VC egress throughput was less than 26% of the con-figured bandwidth shown by counter M530C18. The counter remains as zero for UBR VCCs because they don't have PCR defined.

Updated: The throughput is sampled with 60 second interval.




Operability class:

Related to feature:

RAN2105: Bandwidth utilization classes counters for VC and bundle

RAN224: ATM VP/VC traffic measurement

RAN1.037: ATM based Iub/Iur








Description: The number of samples where the ATM VC egress throughput was (26<=throughput<51%) of the configured bandwidth shown by counter M530C18. The counter remains as zero for UBR VCCs because they don't have PCR defined.





Operability class:

284 DN04143903




Related to feature:
















Operability class:

Related to feature:
















Operability class:

DN04143903 285



Related to feature:











Description: The number of samples where the ATM VC egress throughput was 88% or more of the con-figured bandwidth shown by counter M530C18. The counter remains as zero for UBR VCCs because they don't have PCR defined.





Operability class:

Related to feature:









Counter ID: M530C13 Network element name: VC_IN_BW_UTI_CLASS_1

Version: 4.1 NetAct name: VC_IN_BW_UTI_CLASS_1

Description: The number of samples where the ATM VC ingress throughput was less than 26% of the configured bandwidth shown by counter M530C19. The counter remains as zero for UBR VCCs because they don't have PCR defined.





Operability class:

286 DN04143903




Related to feature:











Description: The number of samples where the ATM VC ingress throughput was (26<=throughput<51%) of the configured bandwidth shown by counter M530C19. The counter remains as zero for UBR VCCs because they don't have PCR defined.





Operability class:

Related to feature:
















Operability class:

DN04143903 287



Related to feature:
















Operability class:

Related to feature:











Description: The number of samples where the ATM VC ingress throughput was 88% or more of the config-ured bandwidth shown by counter M530C19. The counter remains as zero for UBR VCCs because they don't have PCR defined.





Operability class:

288 DN04143903




Related to feature:









Counter ID: M530C18 Network element name: VC_EG_BW_CONFIG

Version: 4.1 NetAct name: VC_EG_BW_CONFIG

Description: The configured egress peak cell rate of the VCC. The counter remains as zero for UBR VCCs because they don't have PCR defined.

Updated: The value is sampled in the end of the measurement period.




Operability class:

Related to feature:









Counter ID: M530C19 Network element name: VC_IN_BW_CONFIG

Version: 4.1 NetAct name: VC_IN_BW_CONFIG

Description: The configured ingress peak cell rate of the VCC. The counter remains as zero for UBR VCCs because they don't have PCR defined.





Operability class:

DN04143903 289



Related to feature:









Counter ID: M530C20 Network element name: VC_EG_PEAK_THRPUT

Version: 4.1 NetAct name: VC_EG_PEAK_THRPUT

Description: The peak egress throughput of the VCC.





Operability class:

Related to feature:









Counter ID: M530C21 Network element name: VC_IN_PEAK_THRPUT

Version: 4.1 NetAct name: VC_IN_PEAK_THRPUT

Description: The peak ingress throughput of the VCC.





Operability class:

Related to feature:






290 DN04143903




7.4 ATM VCC Bundle (533/215H)The ATM VCC Bundle measurement reports the utilization and peak throughput of the ATM VCC bundles used in the Iub interface. The throughput is sampled with 60 second period. The measurement is supported only in RNC2600.

The object of the measurement is ATM VC bundle ID. The measurement identifier is 533/215H and it can be used only if the RNC license for feature RAN2105 is installed (feature code 1898).




Counter ID: M533C0 Network element name: BUN_EG_BW_UTI_CLASS_1

Version: 4.1 NetAct name: BUN_EG_BW_UTI_CLASS_1

Description: The number of samples where the bundle throughput was less than 26% of the configured bandwidth shown by counter M533C5.





Operability class:

Related to feature:









Description: The number of samples where the bundle throughput was (26<=throughput<51%) of the con-figured bandwidth shown by counter M533C5.





Operability class:

Related to feature:




DN04143903 291








Description: The number of samples where the bundle throughput was within (51<=throughput<76%) of the configured bandwidth shown by counter M533C5.





Operability class:

Related to feature:









Description: The number of samples where the bundle throughput was within (76<=throughput<88%) of the configured bandwidth shown by counter M533C5.





Operability class:

Related to feature:









292 DN04143903




Description: The number of samples where the bundle throughput was 88% or more of the configured bandwidth shown by counter M533C5.





Operability class:

Related to feature:







Counter ID: M533C5 Network element name: BUN_EG_BW_CONFIG

Version: 4.1 NetAct name: BUN_EG_BW_CONFIG

Description: The configured egress peak cell rate of the bundle.





Operability class:

Related to feature:







Counter ID: M533C6 Network element name: BUN_EG_PEAK_THRPUT

Version: 4.1 NetAct name: BUN_EG_PEAK_THRPUT

Description: The peak egress throughput of the bundle.





Operability class:

DN04143903 293



7.5 ATM route load measurement (531/213H)The ATM route load measurement reports the AAL2 layer capacity allocations on the ATM route level. The counters of this measurement are similar to the counters of AAL2 path CAC resource measurement (M550/226H). This measurement can be used in trunk interfaces, where many AAL2 paths use the same ATM route, to see the total resource usage, for example, between two network elements.

It must be noted that when routes including UBR+ VCCs in a bundle are measured, all counters do not provide relevant values because UBR+ VCCs in a bundle are counted into bandwidth statistics based on the bundle capacity. Therefore the route level statis-tics can show higher values than the actual physical bandwidth.

The object of the measurement is ATM route and the measured routes are selected with the ATM route ID. The maximum number of measured routes is 256. The measurement identifier is 531/213H.

Related to feature:







Counter ID: M531C0 Network element name: GRT_CELL_RATE

Version: 4.2 NetAct name: GRT_CELL_RATE

Description: The total configured bandwidth of the ATM route. This is the same as the sum of M550C0 AAL2_PATH_GUAR_CELL_RATE calculated over each VCC of which the route consists. When UBR+ VCCs are used in a bundle, this counter can show higher value than the physical capacity of the AAL2 path because M550C0 shows bundle peak cell rate for bundled UBR+ VCCs.

Updated: Stays constant throughout the ATM route lifecycle.




M550C0: AAL2_PATH_GUAR_CELL_RATE

Operability class:






Counter ID: M531C1 Network element name: HSDPA_CELL_RATE_MAX

Version: 1.0 NetAct name: HSDPA_CELL_RATE_MAX

294 DN04143903




Description: The maximum HSDPA shared AAL2 allocation reserved cell rate during the measurement period.

Updated: When the HSDPA shared AAL2 allocation reserved cell rate is at maximum during the mea-surement period.




Operability class:






Counter ID: M531C2 Network element name: HSDPA_CELL_RATE_MIN

Version: 1.0 NetAct name: HSDPA_CELL_RATE_MIN

Description: The minimum HSDPA shared AAL2 allocation reserved cell rate during the measurement period.

Updated: When the HSDPA shared AAL2 allocation reserved cell rate is at minimum during the measure-ment period.

Logical type: Min Trigger type: Sample Sampling interval: 1 s



Operability class:






Counter ID: M531C3 Network element name: HSDPA_CELL_RATE_AVG

Version: 1.0 NetAct name: HSDPA_CELL_RATE_AVG

Description: The average HSDPA shared AAL2 allocation reserved cell rate.

Updated: The average value is sampled constantly during the measurement period.




Operability class:

DN04143903 295








Counter ID: M531C4 Network element name: RES_CELL_RATE_MAX

Version: 4.2 NetAct name: RES_CELL_RATE_MAX

Description: The maximum reserved cell rate for AAL2 connections during the measurement period. This is the same as the sum of M550C3 MAX_RESERVED_CELL_RATE calculated over each VCC of which the route consists.If the UBR+ VC connection is part of a VC bundle, it is counted based on the maximum available capacity value of the whole bundle capacity for the NRT or HSDPA, depending on the VC type.

Updated: When the reserved cell rate is highest during the measurement period.




M550C3: MAX_RESERVED_CELL_RATE

Operability class:






Counter ID: M531C5 Network element name: RES_CELL_RATE_MIN

Version: 4.2 NetAct name: RES_CELL_RATE_MIN

Description: The minimum reserved cell rate for AAL2 connections during the measurement period. This is the same as the sum of M550C2 MIN_RESERVED_CELL_RATE calculated over each VCC of which the route consists.If the UBR+ VC connection is part of a VC bundle, it is counted based on the maximum available capacity value of the whole bundle capacity for the NRT or HSDPA, depending on the VC type.

Updated: When the reserved cell rate is at minimum during the measurement period.




M550C2: MIN_RESERVED_CELL_RATE

Operability class:


296 DN04143903








Counter ID: M531C6 Network element name: RES_CELL_RATE_AVG

Version: 4.2 NetAct name: RES_CELL_RATE_AVG

Description: The average reserved cell rate for AAL2 connections during the measurement period. This is the same as the sum of average value (M550C1 MIN_RESERVED_CELL_RATE / M550C7 NBR_SAMPLES) calculated over each VCC of which the route consists.If the UBR+ VC connection is part of a VC bundle, it is counted based on the maximum available capacity value of the whole bundle capacity for the NRT or HSDPA, depending on the VC type.





M550C1: SUM_RESERVED_CELL_RATEM550C7: NBR_SAMPLES

Operability class:






Counter ID: M531C7 Network element name: ACTIVE_AAL2_CONN_MAX

Version: 1.0 NetAct name: ACTIVE_AAL2_CONN_MAX

Description: The maximum number of active AAL2 cross-connections including HSDPA connections during the measurement period.

Updated: When the number of active AAL2 cross-connections including HSDPA connections is highest during the measurement period.




Operability class:





DN04143903 297




Counter ID: M531C8 Network element name: ACTIVE_AAL2_CONN_MIN

Version: 1.0 NetAct name: ACTIVE_AAL2_CONN_MIN

Description: The minimum number of active AAL2 cross-connections including HSDPA connections during the measurement period.

Updated: When the number of active AAL2 cross-connections including HSDPA connections is at minimum during the measurement period.




Operability class:






Counter ID: M531C9 Network element name: ACTIVE_AAL2_CONN_AVG

Version: 1.0 NetAct name: ACTIVE_AAL2_CONN_AVG

Description: The average number of active AAL2 cross-connections including HSDPA connections.





Operability class:






Counter ID: M531C10 Network element name: SUCC_AAL2_CONN

Version: 1.0 NetAct name: SUCC_AAL2_CONN

Description: The number of successful AAL2 cross-connections including HSDPA connections.

Updated: When an AAL2 cross-connection is successfully created.

298 DN04143903







Operability class:






Counter ID: M531C11 Network element name: AAL2_REJECT_BY_CAC

Version: 1.0 NetAct name: AAL2_REJECT_BY_CAC

Description: The number of AAL2 cross-connections rejected by CAC, including HSDPA connections.

Updated: When an AAL2 cross-connection is rejected by CAC.




Operability class:






Counter ID: M531C12 Network element name: AAL2_REJECT_BY_HW

Version: 1.0 NetAct name: AAL2_REJECT_BY_HW

Description: The number of AAL2 cross-connections rejected by hardware, including HSDPA connec-tions.

Updated: When an AAL2 cross-connection is rejected by hardware.




Operability class:





DN04143903 299




Counter ID: M531C13 Network element name: ACTIVE_HSDPA_CONN_MAX

Version: 1.0 NetAct name: ACTIVE_HSDPA_CONN_MAX

Description: The maximum number of active HSDPA connections during the measurement period.

Updated: When the number of active HSDPA connections is highest during the measurement period.




Operability class:






Counter ID: M531C14 Network element name: ACTIVE_HSDPA_CONN_MIN

Version: 1.0 NetAct name: ACTIVE_HSDPA_CONN_MIN

Description: The minimum number of active HSDPA connections during the measurement period.

Updated: When the number of active HSDPA connections is at minimum during the measurement period.




Operability class:






Counter ID: M531C15 Network element name: ACTIVE_HSDPA_CONN_AVG

Version: 1.0 NetAct name: ACTIVE_HSDPA_CONN_AVG

Description: The average number of active HSDPA connections.



300 DN04143903






Operability class:






Counter ID: M531C16 Network element name: SUCC_HSDPA_CONN

Version: 1.0 NetAct name: SUCC_HSDPA_CONN

Description: The number of successful HSDPA connections.

Updated: When an HSDPA connection is successfully created.




Operability class:






Counter ID: M531C17 Network element name: HSDPA_REJECT_BY_CAC

Version: 1.0 NetAct name: HSDPA_REJECT_BY_CAC

Description: The number of HSDPA connections rejected by CAC.

Updated: When an HSDPA connection is rejected by CAC.




Operability class:






DN04143903 301



7.6 ATM interface measurement (532/214H)The ATM interface measurement reports ATM layer traffic statistics for a specific inter-face inside an ATM interface unit. The measurement gives indication of the ATM inter-face traffic load by reporting the traffic volumes and the bandwidth available for a specific interface. The measurement can also be used to detect interfaces that are con-gested and cause traffic loss. Congestion can be detected by following the number of ATM cells going in and coming out from the interface. Note that there is one limitation related to the ATM cell loss: if ATM OAM CC has been activated, the cells generated by this functionality are inserted to ATM cell flow inside the interface unit and they are not counted as input cells, but only as output cells. The counters' location for a single ATM interface is shown in figure ATM layer counters inside an ATM interface.

The object of the measurement is ATM interface and the measured interfaces are selected with the ATM interface ID. The measurement identifier is 532/214H.

Figure 11 ATM layer counters inside an ATM interface

Counter ID: M531C18 Network element name: HSDPA_REJECT_BY_HW

Version: 1.0 NetAct name: HSDPA_REJECT_BY_HW

Description: The number of HSDPA connections rejected by hardware.

Updated: When an HSDPA connection is rejected by hardware.




Operability class:






302 DN04143903




Counter ID: M532C0 Network element name: IN_CBR_REC_CELL

Version: 4.2 NetAct name: IN_CBR_REC_CELL

Description: The number of received ingress CBR cells per interface. The cells discarded due to DISC_HEC (M532C26) are not counted here, because those cells are dropped in the physical layer before the ingress direction cells are counted to statistics.

Updated: When an ATM cell of a CBR connection is received to the ATM interface (ingress).





Related to feature:







Counter ID: M532C1 Network element name: IN_CBR_TRANS_CELL

Version: 1.0 NetAct name: IN_CBR_TR_CELL

Description: The number of transmitted ingress CBR cells per interface.

Updated: When an ATM cell of a CBR connection is transmitted from the ATM interface towards switch fabric (ingress).





Related to feature:







Counter ID: M532C2 Network element name: IN_CBR_QUEUED_CELL

Version: 1.0 NetAct name: IN_CBR_QUEUED_CELL

Description: The number of ingress CBR cells in queue per interface.

DN04143903 303



Updated: The counter is updated at the end of the measurement period by the number of CBR connec-tion(s) ATM cells in the ingress queue.





Related to feature:







Counter ID: M532C3 Network element name: EG_CBR_REC_CELL

Version: 1.0 NetAct name: EG_CBR_REC_CELL

Description: The number of received egress CBR cells per interface.

Updated: When an ATM cell of a CBR connection is received from the switch fabric direction to the ATM interface (egress).





Related to feature:







Counter ID: M532C4 Network element name: EG_CBR_TR_CELL

Version: 1.0 NetAct name: EG_CBR_TR_CELL

Description: The number of transmitted egress CBR cells per interface.

Updated: When an ATM cell is transmitted out from the interface for a CBR connection (egress).





304 DN04143903




Related to feature:







Counter ID: M532C5 Network element name: EG_CBR_QUEUED_CELL

Version: 1.0 NetAct name: EG_CBR_QUEUED_CELL

Description: The number of egress CBR cells in queue per interface.

Updated: The counter is updated at the end of the measurement period by the number of CBR connec-tion(s) ATM cells in the egress queue.





Related to feature:







Counter ID: M532C6 Network element name: IN_UBR_PLUS_REC_CELL

Version: 4.3 NetAct name: IN_UBR_PLUS_REC_CELL

Description: The number of received ingress UBR+ cells per interface. The cells discarded due to DISC_HEC (M532C26) are not counted here, because those cells are dropped in the physical layer before the ingress direction cells are counted to statistics.

Updated: When an ATM cell of an UBR+ connection is received to the ATM interface (ingress).





Related to feature:

RAN1192: UBR+ for Control Plane and Iu/Iur User Plane





DN04143903 305





Counter ID: M532C7 Network element name: IN_UBR_PLUS_TR_CELL

Version: 1.0 NetAct name: IN_UBR_PLUS_TR_CELL

Description: The number of transmitted ingress UBR+ cells per interface.

Updated: When an ATM cell of an UBR+ connection is transmitted from the ATM interface towards switch fabric (ingress).





Related to feature:







Counter ID: M532C8 Network element name: IN_UBR_PLUS_QUEUED_CELL

Version: 1.0 NetAct name: IN_UBR_PLUS_QUEUED_CELL

Description: The number of ingress UBR+ cells in queue per interface.

Updated: The counter is updated at the end of the measurement period by the number of UBR+ connec-tion(s) ATM cells in the ingress queue.





Related to feature:







Counter ID: M532C9 Network element name: EG_UBR_PLUS_REC_CELL

306 DN04143903




Version: 1.0 NetAct name: EG_UBR_PLUS_REC_CELL

Description: The number of received egress UBR+ cells per interface.

Updated: When an ATM cell of an UBR+ connection is received from the switch fabric direction to the ATM interface (egress).





Related to feature:







Counter ID: M532C10 Network element name: EG_UBR_PLUS_TRANS_CELL

Version: 1.0 NetAct name: EG_UBR_PLUS_TR_CELL

Description: The number of transmitted egress UBR+ cells per interface.

Updated: When an ATM cell is transmitted out from the interface for an UBR+ connection (egress).





Related to feature:







Counter ID: M532C11 Network element name: EG_UBR_PLUS_QUEUED_CELL

Version: 1.0 NetAct name: EG_UBR_PLUS_QUEUED_CELL

Description: The number of egress UBR+ cells in queue per interface.

Updated: The counter is updated at the end of the measurement period by the number of UBR+ connec-tion(s) ATM cells in the egress queue.



DN04143903 307





Related to feature:







Counter ID: M532C12 Network element name: IN_UBR_REC_CELL

Version: 4.2 NetAct name: IN_UBR_REC_CELL

Description: The number of received ingress UBR cells per interface. The cells discarded due to DISC_HEC (M532C26) are not counted here, because those cells are dropped in the physical layer before the ingress direction cells are counted to statistics.

Updated: When an ATM cell of an UBR connection is received to the ATM interface (ingress).





Related to feature:







Counter ID: M532C13 Network element name: IN_UBR_TR_CELL

Version: 1.0 NetAct name: IN_UBR_TR_CELL

Description: The number of transmitted ingress UBR cells per interface.

Updated: When an ATM cell of an UBR connection is transmitted from the ATM interface towards switch fabric (ingress).





Related to feature:




308 DN04143903







Counter ID: M532C14 Network element name: IN_UBR_QUEUED_CELL

Version: 1.0 NetAct name: IN_UBR_QUEUED_CELL

Description: The number of ingress UBR cells in queue per interface.

Updated: The counter is updated at the end of the measurement period by the number of UBR connec-tion(s) ATM cells in the ingress queue.





Related to feature:







Counter ID: M532C15 Network element name: EG_UBR_REC_CELL

Version: 1.0 NetAct name: EG_UBR_REC_CELL

Description: The number of received egress UBR cells per interface.

Updated: When an ATM cell of an UBR connection is received from the switch fabric direction to the ATM interface (egress).





Related to feature:







DN04143903 309



Counter ID: M532C16 Network element name: EG_UBR_TR_CELL

Version: 1.0 NetAct name: EG_UBR_TR_CELL

Description: The number of transmitted egress UBR cells per interface.

Updated: When an ATM cell is transmitted out from the interface for an UBR connection (egress).





Related to feature:







Counter ID: M532C17 Network element name: EG_UBR_QUEUED_CELL

Version: 1.0 NetAct name: EG_UBR_QUEUED_CELL

Description: The number of egress UBR cells in queue per interface.

Updated: The counter is updated at the end of the measurement period by the number of UBR connec-tion(s) ATM cells in the egress queue.





Related to feature:







Counter ID: M532C18 Network element name: IN_TOT_REC_CELL

Version: 4.2 NetAct name: IN_TOT_REC_CELL

Description: The total number of received ingress ATM cells per interface. The cells discarded due to DISC_HEC (M532C26) are not counted here, because those cells are dropped in the physical layer before the ingress direction cells are counted to statistics.

Updated: When an ATM cell is received to the ATM interface (ingress).

310 DN04143903








Related to feature:







Counter ID: M532C19 Network element name: IN_TOT_TR_CELL

Version: 1.0 NetAct name: IN_TOT_TR_CELL

Description: The total number of transmitted ingress ATM cells per interface.

Updated: When an ATM cell is transmitted from the ATM interface towards switch fabric (ingress).





Related to feature:







Counter ID: M532C20 Network element name: IN_TOT_QUEUED_CELL

Version: 1.0 NetAct name: IN_TOT_QUEUED_CELL

Description: The total number of ingress ATM cells in queue per interface.

Updated: The counter is updated at the end of measurement period by the number of ATM cells in the ingress queue.





Related to feature:



DN04143903 311







Counter ID: M532C21 Network element name: EG_TOT_REC_CELL

Version: 1.0 NetAct name: EG_TOT_REC_CELL

Description: The total number of received egress ATM cells per interface.

Updated: When an ATM cell is received from the switch fabric direction to the ATM interface (egress).





Related to feature:







Counter ID: M532C22 Network element name: EG_TOT_TR_CELL

Version: 1.0 NetAct name: EG_TOT_TR_CELL

Description: The total number of transmitted egress ATM cells per interface.

Updated: When an ATM cell is transmitted out from the interface (egress).





Related to feature:







312 DN04143903




Counter ID: M532C23 Network element name: EG_TOT_QUEUED_CELL

Version: 1.0 NetAct name: EG_TOT_QUEUED_CELL

Description: The total number of egress ATM cells in queue per interface.

Updated: The counter is updated at the end of the measurement period by the number of ATM cells in the egress queue.





Related to feature:







Counter ID: M532C24 Network element name: IN_CAP

Version: 1.0 NetAct name: IN_CAP

Description: The configured ingress bandwidth for CLP=0+1 ATM cells.

Updated: The counter is sampled at the end of the measurement period.





Related to feature:







Counter ID: M532C25 Network element name: EG_CAP

Version: 1.0 NetAct name: EG_CAP

Description: The configured egress bandwidth for CLP=0+1 ATM cells.

Updated: The counter is sampled at the end of the measurement period.


DN04143903 313






Related to feature:







Counter ID: M532C26 Network element name: DISC_HEC

Version: 4.2 NetAct name: DISC_HEC

Description: The number of ingress cells discarded due to HEC violation. This counter counts the ATM cells with header error (HEC) on the physical layer and those dropped cells will not be counted into counters M532C0, M532C6, M532C12 and M532C18.

Updated: When ingress cells are discarded in the ATM interface due to an HEC violation.





Related to feature:







Counter ID: M532C27 Network element name: ERR_HEC

Version: 1.0 NetAct name: ERR_HEC

Description: The number of ingress cells with HEC violation, both corrected and discarded cells.

Updated: When an ingress cell with an HEC violation is received to the ATM interface, includes both cor-rected and discarded cells.





Related to feature:



314 DN04143903




7.7 AAL2 scheduling performance in RNC measurement (553/229H)

7.7.1 Introduction to AAL2 scheduling performance in RNC measurementThe AAL2 Scheduling Performance measurement follows Iub capability to serve downlink traffic towards BTS. The ATM and AAL2 scheduling inside RNC is presented in figure RNC ATM and AAL2 scheduling as a conceptual representation.

The kind of AAL2 scheduling structure used in RNC depends on the selected Iub ATM configuration. The basic AAL2 VCC carrying DCH and HSDPA traffic at Iub configura-tion uses four AAL2 scheduling queues. In the default configuration, the transport bearers are allocated to the queues in the following way:

• Q1: Common channels, RT DCH, Conversational HSPA and SRBs (highest priority queue)

• Q2: Streaming HSPA (second highest priority queue) • Q3: NRT DCH (third highest priority queue) • Q4: NRT HSPA (lowest priority queue)

If optional feature RAN1253 Iub Transport QoS is enabled, the operator can configure how the different radio bearer types are mapped to the queues.

The counters of AAL2 Scheduling Performance measurement are divided into four groups, one for each AAL2 priority queue. Each group contains counters for measuring the number of AAL2 CPS packets (A2SP unit) or ATM cells (NPS1 unit) in the queue, queuing delay and the number of times when packets were dropped from the queue.

In case the AAL2 scheduler cannot serve all traffic coming from upper layer users to the ATM VCC, the Iub becomes congested and scheduling actions are required to prevent loss of user data. The usage of scheduling messages can be monitored using counters M553C38-M553C40.

The object identifiers of the AAL2 Scheduling Performance measurement are ATM virtual channel connection, WBTS ID, and AAL usage. The ATM virtual channel connec-tion is identified with the ATM interface ID/VPI/VCI identifiers. All AAL2 user plane type ATM VC connections can be selected as an object for this measurement. The only possible AAL2 Usage object in this measurement type is AAL2UD.

This measurement is supported by both NPS1 and A2SP unit based ATM transport solu-tions, except for some scheduling message counters that are unit type specific; see the counter descriptions for details.

It must be noted that the AAL2 data processing in NPS1 is quite different when compared to A2SP. In the A2SP unit all data goes through physical queues, but in the NPS1 unit traffic not controlled by the Internal Flow Control (IFC) is handled via a virtual queue. If data is dropped from this virtual queue, it is not visible in M553 counters. Examples of traffic types handled by this virtual queue is the interactive/background





DN04143903 315



QoS class data received by DRNC from the Iur interface, or the NRT/HSDPA traffic gen-erated by the SRNC itself to an Iub interface where IFC is disabled.

Figure 12 RNC ATM and AAL2 scheduling as a conceptual representation

7.7.2 AAL2 scheduling performance in RNC counters

L3 data flows to certain BTS AAL2 scheduling

ATM layer scheduling; trafficrate is shaped to the ATMinterface PCR. Also other ATMlayer traffic management canbe applied.

RNC ATM interface

Schedulingmessages

ATM VCCCBR type

toBTS

AAL2 scheduling; trafficrate is shaped to the ATMVCC PCR.

Queue-1

Queue-2

Queue-3

Queue-4

Counter ID: M553C10 Network element name: Q1_QUE_USAGE_PEAK

Version: 1.1 NetAct name: Q1_QUE_USAGE_PEAK

Description: The peak amount of sent AAL2 CPS packets (A2SP) or ATM cells (NPS1) in the scheduling queue1 during the measurement period.

Updated: When the sample of sent AAL2 CPS packets or ATM cells in the priority queue is highest. Sampled once per second in A2SP and once per 10 seconds in NPS1, but not during periods when the AAL2 priority queue is empty (i.e. no traffic).

Logical type: Max Trigger type: Sample Sampling interval: 1 s / 10 s



Operability class:

Related to feature:

RAN 1253: Iub Transport QoS RAN 1099: Dynamic scheduling for HSDPA with Path selection





316 DN04143903





Counter ID: M553C11 Network element name: Q1_QUE_PACKETS_SUM

Version: 1.1 NetAct name: Q1_QUE_PACKETS_SUM

Description: The sum of sent AAL2 CPS packets (A2SP) or ATM cells (NPS1) in the scheduling queue1 during the measurement period.This counter, divided by the denominator M553C12, provides the average scheduling queue length.

Updated: Added to the previous value when data is sampled. Updated once per second in A2SP and once per 10 seconds in NPS1, but not during periods when the AAL2 priority queue is empty (i.e. no traf-fic).

Logical type: Sum Trigger type: Sample Sampling interval: 1 s / 10 s



M553C12: Q1_QUE_SAMPLES

Operability class:

Related to feature:







Counter ID: M553C12 Network element name: Q1_QUE_SAMPLES

Version: 1.1 NetAct name: Q1_QUE_SAMPLES

Description: The number of scheduling queue1 samples during the measurement period.

Updated: Updated once per second in A2SP and once per 10 seconds in NPS1 by the value 1 when sta-tistics data is sampled from the AAL2 priority queue, but not during periods when the queue is empty (i.e. no traffic).




M553C11: Q1_QUE_PACKETS_SUM

Operability class:

Related to feature:






DN04143903 317




Counter ID: M553C13 Network element name: Q1_QUE_DELAY_PEAK

Version: 1.1 NetAct name: Q1_QUE_DELAY_PEAK

Description: The peak value of delay caused by AAL2 layer buffering in the scheduling queue1.

Updated: When the sample of delay in the priority queue is highest. Sampled once per second in A2SP and once per 10 seconds in NPS1, but not during periods when the AAL2 priority queue is empty (i.e. no traffic).


Unit: ms Range: Example values:


Operability class:

Related to feature:







Counter ID: M553C14 Network element name: Q1_QUE_DELAY_SUM

Version: 1.1 NetAct name: Q1_QUE_DELAY_SUM

Description: The sum of delay values of AAL2 layer buffering in the scheduling queue1 during the mea-surement period.This counter, divided by the denominator M553C15, provides the average scheduling delay.





M553C15: Q1_QUE_DELAY_SAMPLES

Operability class:

Related to feature:

RAN 1253: Iub Transport QoS

RAN 1099: Dynamic scheduling for HSDPA with Path selection





318 DN04143903





Counter ID: M553C15 Network element name: Q1_QUE_DELAY_SAMPLES

Version: 1.1 NetAct name: Q1_QUE_DELAY_SAMPLES

Description: The number of sampled delay values in the scheduling queue1.





M553C14: Q1_QUE_DELAY_SUM

Operability class:

Related to feature:







Counter ID: M553C16 Network element name: Q1_QUE_DRP_EVENTS

Version: 1.1 NetAct name: Q1_QUE_DRP_EVENTS

Description: This counter indicates that packets were dropped from the scheduling queue1.In NPS1 the unit is "number of dropped packets". In A2SP the counter tells the number of events when packets were dropped, but not the number of packets.

Updated: When AAL2 CPS packets are dropped from the AAL2 buffer due to delay being too high or buffer overflow in the priority Queue.




Operability class:

Related to feature:








DN04143903 319










Operability class:

Related to feature:















Operability class:

Related to feature:








320 DN04143903












Operability class:

Related to feature:















Operability class:

Related to feature:








DN04143903 321










Operability class:

Related to feature:















Operability class:

Related to feature:








322 DN04143903










Operability class:

Related to feature:














Operability class:

Related to feature:









DN04143903 323









Operability class:

Related to feature:
















Operability class:

Related to feature:








324 DN04143903










Operability class:

Related to feature:










Updated: Added to the previous value when data is sampled. Updated once per second in A2SP and once per 10 seconds in NPS1, but not during periods when the AAL2 priority queue is empty (i.e. no traffic).





Operability class:

Related to feature:









DN04143903 325









Operability class:

Related to feature:RAN 1253: Iub Transport QoS RAN 1099: Dynamic scheduling for HSDPA with Path selection













Operability class:

Related to feature:










326 DN04143903








Operability class:

Related to feature:















Operability class:

Related to feature:









DN04143903 327









Operability class:

Related to feature:














Operability class:

Related to feature:










328 DN04143903









Operability class:

Related to feature:















Operability class:

Related to feature:










DN04143903 329







Operability class:

Related to feature:







Counter ID: M553C38 Network element name: AAL2_PATH_QUE_DOWN_MSGS

Version: 1.0 NetAct name: AAL2_PATH_QUE_DOWN_MSGS

Description: The number of "slow down" messages sent to the MAC layer in AAL2 path.

Updated: When a "slow down" message is sent to the MAC layer to speed down data transmission.




Operability class:

Related to feature:








Counter ID: M553C39 Network element name: AAL2_PATH_QUE_UP_MSGS

Version: 1.0 NetAct name: AAL2_PATH_QUE_UP_MSGS

Description: The number of "speed up" messages sent to the MAC layer in AAL2 path.This counter is supported only by A2SP unit.

Updated: When a "speed up" message is sent to the MAC layer to speed up data transmission.




Operability class:

330 DN04143903




Related to feature:








Counter ID: M553C40 Network element name: AAL2_PATH_QUE_STOP_MSGS

Version: 1.0 NetAct name: AAL2_PATH_QUE_STOP_MSGS

Description: The number of "full stop" messages sent to the MAC layer in AAL2 path.This counter is supported only by A2SP unit.

Updated: When a "full stop" message is sent to the MAC layer to stop data transmission.




Operability class:

Related to feature:








Counter ID: M553C41 Network element name: AAL2_PATH_QUE_FULL_MSGS

Version: 1.1 NetAct name: AAL2_PATH_QUE_FULL_MSGS

Description: This counter is currently not supported.

Updated: Never.




Operability class:

Related to feature:






Used from release: not supported Definition updated in release:

DN04143903 331



7.8 AAL5 protocol measurement in Chorus (549/225H)The AAL5 protocol measurement in Chorus provides information about the amount of traffic between the ATM layer and AAL5 in Chorus units. It also informs about any protocol abnormalities detected in the data reassembling from ATM cells to CPCS data units.

The object is a computer unit that is identified by unit type and index.

The measurement identifier is 549/225H

Counter ID: M553C42 Network element name: AAL2_PATH_QUE_HALF_MSGS

Version: 1.1 NetAct name: AAL2_PATH_QUE_HALF_MSGS


Updated: Never.




Operability class:

Related to feature:







Counter ID: M549C0 Network element name: UTOPIAE

Version: 5.1 NetAct name: UTOPIAE

Description: The number of cells dropped as a result of an internal UTOPIA bus parity error or a state machine error.

Updated: The counter is incremented if a cell id is dropped as result of an internal UTOPIA bus parity error or a state machine error (short or long cells).









Used from release: U1/RN1 Definition updated in release:

332 DN04143903




Counter ID: M549C1 Network element name: MIC_COUNT

Version: 5.1 NetAct name: MIC_COUNT

Description: The number of misinserted cells dropped as a result of an address look-up failure. The VPI/VCI of the cell header was not in accord with any initialized channel.

Updated: When received cells are discarded if the Virtual Channel Connection (VCC) to which the cells are mapped is not active in SAR.










Counter ID: M549C2 Network element name: TX_PDU

Version: 5.1 NetAct name: TX_PDU

Description: The number of transmitted AAL5 CPCS-PDUs.

Updated: When an AAL5 CPCS-PDU is transmitted.










Counter ID: M549C3 Network element name: TX_SIZE

Version: 5.2 NetAct name: TX_SIZE

Description: The number of transmitted bytes in AAL5 frames (CPCS-PDUs).

Updated: When an AAL5 CPCS-PDU is transmitted.



DN04143903 333










Counter ID: M549C4 Network element name: RX_PDU

Version: 5.1 NetAct name: RX_PDU

Description: The number of received AAL5 CPCS-PDUs.

Updated: When an AAL5 CPCS-PDU is received.










Counter ID: M549C5 Network element name: RX_SIZE

Version: 5.2 NetAct name: RX_SIZE

Description: The number of received bytes in AAL5 frames.

Updated: When an AAL5 CPCS-PDU is received.










334 DN04143903




Counter ID: M549C6 Network element name: RX_ERROR

Version: 5.1 NetAct name: RX_ERROR

Description: The overall number of rx errors. The total sum of received AAL5 CPCS-PDU errors. Counters UTOPIAE M549C0 and MIC_COUNT M549C1 are not included here.

Updated: When AAL5 PCPS-PDU is received and an error is detected.




M549C0: UTOPIAE







Counter ID: M549C7 Network element name: BSY_COUNT

Version: 5.1 NetAct name: BSY_COUNT

Description: Rx buffers exhausted (busy condition). Receiving an AAL5 frame fails because of a lack of free buffers. The processing time for received frames is too long and/or there are not enough buffers available. If the counter value does not increase constantly, increasing the number of receive buffers might correct the situation.

Updated: The counter is incremented when no free receive buffers are available.










Counter ID: M549C8 Network element name: ABRTE_COUNT

Version: 5.1 NetAct name: ABRTE_COUNT

Description: Abort message indication error counter. The number of AAL5 frames received with a field length of zero.

DN04143903 335



Updated: When the LENGTH field in the trailer of an AAL5 PDU is zero.










Counter ID: M549C9 Network element name: LNE_COUNT

Version: 5.1 NetAct name: LNE_COUNT

Description: RX length error. The number of received AAL5 CPCS-PDUs whose length is incorrect.

Updated: When a received AAL5 CPCS-PDU exceeds the length defined in the length field.










Counter ID: M549C10 Network element name: CRC32E_COUNT

Version: 5.1 NetAct name: CRC32E_COUNT

Description: The number of RX CRC errors. A CRC32 parity error in AAL5 PDU. The loss of ATM cells or the occurrence of bit errors has caused the corruption of the received AAL5 frame.

Updated: When a CRC-32 violation in the received AAL5 CPCS-PDU is detected.








336 DN04143903




7.9 AAL5 protocol measurement in DMX (547/223H)The AAL5 protocol measurement in DMX provides information about the amount of traffic between the ATM layer and AAL5 in DMX units. It also informs about any protocol abnormalities detected in the data reassembling from ATM cells to CPCS data units.



AAL5 provides counters and attributes for the performance monitoring, which are based on maintaining counts of errors in received Segmentation and Reassembly (SAR) and Convergence Sublayer (CS) Protocol Data Units (PDUs).



Counter ID: M547C0 Network element name: CELL_TX_CNT

Version: 5.1 NetAct name: CELL_TX_CNT

Description: Transmitted cells. The number of cells sent by Segmentation and Reassembly (SAR).

Updated: When a cell is transmitted.










Counter ID: M547C1 Network element name: CELL_RX_CNT

Version: 5.1 NetAct name: CELL_RX_CNT

Description: Received cells. The amount of cells received for active virtual channel connections (VCC) by Segmentation and Reassembly (SAR).

Updated: When a cell is received for an active channel.








DN04143903 337





Counter ID: M547C2 Network element name: CELL_DISCARD_CNT

Version: 5.1 NetAct name: CELL_DISCARD_CNT

Description: Discarded cells. Cells discarded by Segmentation and Reassembly (SAR) in the unit. Received cells are discarded if the Virtual Channel Connection (VCC) on which the cells are mapped is not active in SAR.

Updated: When a cell with inactive channel VPI/VCI is received.










Counter ID: M547C3 Network element name: AAL5_PDU_DISCARD_CNT

Version: 5.1 NetAct name: AAL5_PDU_DISCARD_CNT

Description: Discarded AAL5 CPCS-PDUs. The number of discarded Common Part Convergence Sublayer Protocol Data Units. This counter indicates the discarding of received AAL5 CPCS-PDUs. AAL5 CPCS-PDUs are discarded because of an overflow of the receiving buffer, an overflow of the receiving FIFO, an overflow of the status queue or the received packet being larger than the maximum packet size. This counter does not include errors reported by counters INVALID_FIELDS M547C4, INCORRECT_FIELDS M547C5 and RSM_TIMER_EXP M547C6.

Updated: When AAL5 CPCS-PDUs are discarded because of an overflow of the receiving buffer, an overflow of the receiving FIFO, an overflow of the status queue or the received packet being larger than the maximum packet size.










338 DN04143903




Counter ID: M547C4 Network element name: INVALID_FIELDS

Version: 5.1 NetAct name: INVALID_FIELDS

Description: Invalid Fields. The number of reassembled AAL5 CPCS-PDUs whose Common Part Indica-tor (CPI) is invalid, the number of reassembled AAL5 CPCS-PDUs whose length is violated, and the number of reassembled AAL5 CPCS-PDUs whose PAD field length is incorrect.

Updated: The counter is updated because of an invalid Common Part Indicator (CPI) in the AAL5 trailer, an oversized received SDU, or the received packet being larger than the maximum packet size (length violation).










Counter ID: M547C5 Network element name: INCORRECT_FIELDS

Version: 5.1 NetAct name: INCORRECT_FIELDS

Description: Incorrect fields. The number of reassembled AAL5 CPCS-PDUs whose CRC-32 has been violated. On the other hand the number of reassembled AAL5 CPCS-PDUs in which both CRC-32 has been violated and PAD field length has been invalid

Updated: The counter is updated because of the incorrect length of the received Common Part Conver-gence Sublayer Protocol Data Unit (CPSC-PDU) PAD field; cells disappeared on the way or Cyclic Redundancy Check - 32 (CRC-32) violation of trailer i.e. data disappeared or bit error.










Counter ID: M547C6 Network element name: RSM_TIMER_EXP

Version: 5.1 NetAct name: RSM_TIMER_EXP

DN04143903 339



7.10 PDH interface measurements

7.10.1 PDH interface statistics permanent measurement (145/91H)The plesiochronous digital hierarchy (PDH) interface statistics permanent measurement automatically produces disturbance statistics on all active trunk circuits which are con-nected to the network element. From the PDH interface statistics report, you can check the transmission quality of the trunk circuits.

The PDH interface statistics report contains all disturbances which are detected in the supervised PDH interfaces. You can set your own circuit-specific threshold values for the reporting of PDH interface disturbances. This allows you to discard a certain level of short disturbances and make the system report the more serious disturbances only.

The PDH interface statistics permanent measurement is always active as a background process. Its measurement period starts at 00:00 hours and lasts 24 hours. A new mea-surement period starts automatically when the previous one ends. At the end of the measurement period, at 00:20 hours, the system writes out the measurement report that is transferred to OMS and from there to NetAct.

g At system start-up, the first permanent measurement covers the period from the start-up moment to 00:00 hours.

The following actions start a new measurement period of PDH interfaces:

• a restart or a switchover of a PDH supervision computer (CM or RSMU) • modifying measurement settings (the MML command group YE) • a restart of a parent unit of a PDH interface (for example, ETGR, NIP1, STER, or

VETGR) • working state change of a PDH interface to WO-EX (for example, ET or PET)

For more information on permanent measurements, see the commands YMP and YES.

Description: Reassembly timer expirations (STR-NM-M4NE-REQ-02.00). The number of reassembled AAL5 Common Part Convergence Sublayer Protocol Data Units (CPCS-PDU) whose reassembly timer has expired. When a reassembly timer expires, the current CPCS-PDU is discarded. A PDU time-out occurs when a partially received PDU is not complete within a set time period. The period is fixed by the system as 1 second.

Updated: When AAL5 CPCS-PDU reassembly time has expired.










Counter ID: M145B2C1 Network element name: TOTAL_ERROR_CODE

340 DN04143903




Version: 2.1 NetAct name: TOTAL_ERROR_CODE

Description: Error code concerning the whole report. Zero value means a successful report, non-zero value indicates that no counters are present. The value is a general DX error code in decimal format.

Updated:




Operability class:






Counter ID: M145B2C2 Network element name: DIST_ERROR_CODE

Version: 2.1 NetAct name: DIST_ERROR_CODE

Description: Error code concerning the short disturbances counters. Zero value means a successful report, non-zero value indicates that no disturbance counters are present. The value is a general DX error code in decimal format.

Updated:




Operability class:






Counter ID: M145B2C3 Network element name: FRA_ERROR_CODE

Version: 2.1 NetAct name: FRA_ERROR_CODE

Description: Error code concerning the frame alignment error counters. Zero value means a successful report, non-zero value indicates that no frame alignment counters are present. The value is a general DX error code in decimal format.

Updated:



DN04143903 341




Operability class:






Counter ID: M145B2C4 Network element name: SLIP_ERROR_CODE

Version: 2.1 NetAct name: SLIP_ERROR_CODE

Description: Error code concerning the slip counters. Zero value means a successful report, non-zero value indicates that no slip counters are present. The value is a general DX error code in decimal format.

Updated:




Operability class:






Counter ID: M145B2C5 Network element name: CRC_ERROR_CODE

Version: 2.1 NetAct name: CRC_ERROR_CODE

Description: Error code concerning the CRC counters. Zero value means a successful report, non-zero value indicates that no CRC counters are present. The value is a general DX error code in decimal format.

Updated:




Operability class:






342 DN04143903




Counter ID: M145B2C6 Network element name: DISTURB_CTR_1_LOWER_LIMIT

Version: 2.1 NetAct name: DISTURB_CTR_1_LOWER_LIMIT

Description: The limits for statistics counters of disturbances. The disturbances are recorded according to the duration of the disturbance. This field indicates the limits expressed in milliseconds.

Updated:

Logical type: Min Trigger type: Duration Sampling interval:



Operability class:






Counter ID: M145B2C7 Network element name: DISTURB_CTR_1_UPPER_LIMIT

Version: 2.2 NetAct name: DISTURB_CTR_1_UPPER_LIMIT


Updated:

Logical type: Max Trigger type: Duration Sampling interval:



Operability class:









Updated:


DN04143903 343





Operability class:









Updated:




Operability class:









Updated:




Operability class:





344 DN04143903








Updated:




Operability class:









Updated:




Operability class:






Counter ID: M145B2C13 Network element name: IN_SIGNAL_MISSING_CTR_1

Version: 2.1 NetAct name: IN_SIGNAL_MISSING_CTR_1

DN04143903 345



Description: The number of 'incoming signal missing' disturbances of group 1. Disturbances are divided into four groups according to the duration of the disturbance. The disturbance limits are defined in the M145B2C6-M145B2C12 fields.

Updated:




Operability class:









Updated:




Operability class:









Updated:



346 DN04143903





Operability class:









Updated:




Operability class:






Counter ID: M145B2C17 Network element name: FRAME_ALIGNMENT_LOST_CTR_1

Version: 2.1 NetAct name: FRAME_ALIGNMENT_LOST_CTR_1

Description: The number of 'frame alignment signal lost' disturbances of group 1. Disturbances are divided into four groups according to the duration of the disturbance. The disturbance limits are defined in the M145B2C6-M145B2C12 fields.

Updated:




Operability class:




DN04143903 347








Updated:




Operability class:









Updated:




Operability class:






348 DN04143903







Updated:




Operability class:






Counter ID: M145B2C21 Network element name: AIS_RECEIVED_CTR_1

Version: 2.1 NetAct name: AIS_RECEIVED_CTR_1

Description: The number of 'AIS received' disturbances of group 1. Disturbances are divided into four groups according to the duration of the disturbance. The disturbance limits are defined in the M145B2C6-M145B2C12 fields.

Updated:




Operability class:









DN04143903 349



Updated:




Operability class:









Updated:




Operability class:









Updated:




Operability class:


350 DN04143903








Counter ID: M145B2C25 Network element name: REMOTE_END_ALARM_CTR_1

Version: 2.1 NetAct name: REMOTE_END_ALARM_CTR_1

Description: The number of 'remote end alarm' disturbances of group 1. Disturbances are divided into four groups according to the duration of the disturbance. The disturbance limits are defined in the M145B2C6-M145B2C12 fields.

Updated:




Operability class:









Updated:




Operability class:






DN04143903 351






Updated:




Operability class:









Updated:




Operability class:






Counter ID: M145B2C49 Network element name: FRA_CTR_1_LOWER_LIMIT

Version: 2.1 NetAct name: FRA_CTR_1_LOWER_LIMIT

Description: Limits for the statistics counters of frame alignment loss. The bit error ratio is based on the erroneous frame alignment signals received during five seconds. The field indicates the counter limits (errors/5 seconds).

Updated:

352 DN04143903




Logical type: Min Trigger type: Event Sampling interval:

Unit: errors/ 5 seconds Range: Example values:


Operability class:






Counter ID: M145B2C50 Network element name: FRA_CTR_1_UPPER_LIMIT

Version: 2.1 NetAct name: FRA_CTR_1_UPPER_LIMIT


Updated:




Operability class:









Updated:




Operability class:



DN04143903 353









Updated:




Operability class:









Updated:




Operability class:






354 DN04143903







Updated:




Operability class:









Updated:




Operability class:






Counter ID: M145B2C56 Network element name: FRAME_ALIGNMENT_ERROR_CTR_1

Version: 2.1 NetAct name: FRAME_ALIGNMENT_ERROR_CTR_1

Description: Counter 1 for frame alignment errors. The errors are counted using four counters depending on the number of errors within five seconds. The error limits are defined in the M145B2C49-M145B2C55 fields.

DN04143903 355



Updated:




Operability class:









Updated:




Operability class:









Updated:




356 DN04143903




Operability class:









Updated:




Operability class:






Counter ID: M145B2C60 Network element name: NEGATIVE_SLIPS

Version: 2.1 NetAct name: NEGATIVE_SLIPS

Description: The counter value for negative slips.

Updated:

Logical type: Cumulative Trigger type: Sample Sampling interval:



Operability class:






DN04143903 357



Counter ID: M145B2C61 Network element name: POSITIVE_SLIPS

Version: 2.1 NetAct name: POSITIVE_SLIPS

Description: The counter value for positive slips.

Updated:

Logical type: Cumulative Trigger type: Sample Sampling interval:



Operability class:






Counter ID: M145B2C62 Network element name: LOCAL_END_TOTAL_TIME

Version: 2.1 NetAct name: LOCAL_END_TOTAL_TIME

Description: CRC measurement: total time at the local end, given in 1/100 seconds.

Updated:

Logical type: Cumulative Trigger type: Duration Sampling interval: 1 s

Unit: 10 ms Range: Example values:


Operability class:






Counter ID: M145B2C63 Network element name: LOCAL_END_AVAIL_TIME

Version: 2.1 NetAct name: LOCAL_END_AVAIL_TIME

Description: CRC measurement: availability time at the local end, given in 1/100 seconds.

Updated:




358 DN04143903




Operability class:






Counter ID: M145B2C64 Network element name: LOCAL_END_UNAVAIL_TIME

Version: 2.1 NetAct name: LOCAL_END_UNAVAIL_TIME

Description: CRC measurement: unavailability time at the local end, given in 1/100 seconds.

Updated:




Operability class:






Counter ID: M145B2C65 Network element name: LOCAL_END_DEGRADED_MINUTES

Version: 2.1 NetAct name: LOCAL_END_DEGRADED_MINUTES

Description: CRC measurement: percentage of degraded minutes at the local end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:


Unit: 0.01*% Range: Example values:


Operability class:






DN04143903 359



Counter ID: M145B2C66 Network element name: LOCAL_END_ERRORED_SECONDS

Version: 2.1 NetAct name: LOCAL_END_ERRORED_SECONDS

Description: CRC measurement: percentage of errored seconds at the local end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:






Counter ID: M145B2C67 Network element name: LOCAL_END_ERROR_FREE_SEC

Version: 2.1 NetAct name: LOCAL_END_ERROR_FREE_SEC

Description: CRC measurement: percentage of error free seconds at the local end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:






Counter ID: M145B2C68 Network element name: LOCAL_END_SER_ERRORED_SEC

Version: 2.1 NetAct name: LOCAL_END_SER_ERRORED_SEC

Description: CRC measurement: percentage of seriously errored seconds at the local end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:

360 DN04143903







Operability class:






Counter ID: M145B2C69 Network element name: LOCAL_END_BBE

Version: 2.1 NetAct name: LOCAL_END_BBE

Description: CRC measurement: percentage of background block errors at the local end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:






Counter ID: M145B2C70 Network element name: REMOTE_END_TOTAL_TIME

Version: 2.1 NetAct name: REMOTE_END_TOTAL_TIME

Description: CRC measurement: total time at the remote end, given in 1/100 seconds.

Updated:

Logical type: Cumulative Trigger type: Duration Sampling interval: 1 s



Operability class:





DN04143903 361




Counter ID: M145B2C71 Network element name: REMOTE_END_AVAIL_TIME

Version: 2.1 NetAct name: REMOTE_END_AVAIL_TIME

Description: CRC measurement: availability time at the remote end, given in 1/100 seconds.

Updated:




Operability class:






Counter ID: M145B2C72 Network element name: REMOTE_END_UNAVAIL_TIME

Version: 2.1 NetAct name: REMOTE_END_UNAVAIL_TIME

Description: CRC measurement: unavailability time at the remote end, given in 1/100 seconds.

Updated:




Operability class:






Counter ID: M145B2C73 Network element name: REMOTE_END_DEGRADED_MINUTES

Version: 2.1 NetAct name: REMOTE_END_DEGRADED_MINUTES

Description: CRC measurement: percentage of degraded minutes at the remote end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:

362 DN04143903







Operability class:






Counter ID: M145B2C74 Network element name: REMOTE_END_ERRORED_SECONDS

Version: 2.1 NetAct name: REMOTE_END_ERRORED_SECONDS

Description: CRC measurement: percentage of errored seconds at the remote end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:






Counter ID: M145B2C75 Network element name: REMOTE_END_ERROR_FREE_SEC

Version: 2.1 NetAct name: REMOTE_END_ERROR_FREE_SEC

Description: CRC measurement: percentage of error free seconds at the remote end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:



DN04143903 363






Counter ID: M145B2C76 Network element name: REMOTE_END_SER_ERRORED_SEC

Version: 2.1 NetAct name: REMOTE_END_SER_ERRORED_SEC

Description: CRC measurement: percentage of seriously errored seconds at the remote end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:






Counter ID: M145B2C77 Network element name: REMOTE_END_BBE

Version: 2.1 NetAct name: REMOTE_END_BBE

Description: CRC measurement: percentage of background block errors at the remote end, given in 1/100 percents (the percentage value multiplied with 100).

Updated:




Operability class:






364 DN04143903




7.10.2 PDH interface statistics temporary measurementYou can define temporary measurements to monitor the performance of any single trunk circuit for a shorter period of time. At the end of a measurement period, the system writes out the results of the temporary measurement to the logical file ETTEMP.

The following actions cancel ongoing temporary measurements:

• a restart or a switchover of a PDH supervision computer (CM or RSMU) • modifying of measurement settings (the MML command group YE) • a restart of a parent unit of a PDH interface (for example, ETGR, NIP1, STER, or

VETGR) • working state change of a PDH interface to WO-EX (for example, ET or PET)

For more information on creating temporary measurements, see the command YMS.

7.10.3 PDH interface disturbance measurement reportThe system saves a disturbance measurement report for every operational trunk circuit of the network element after the measurement period has ended. You can also, at any time, manually output a report on the currently ongoing permanent measurement. The report on a temporary measurement is first available, when the measurement period has ended.

For a sample of a PDH interface disturbance measurement report, see the command YMO of the PCM Statistics Measurement and Output MML.

The PDH interface disturbance measurement report contains the following information:

• For each disturbance type, the system stores the following data in four different counters according to the duration of the fault (the default values are as follows: Counter 1: duration 10–50 ms / Counter 2: 50–200 ms / Counter 3: 200–1000 ms / Counter 4: 1000< ms): • incoming signal missing • frame alignment lost • AIS received • alarm from the remote endIf needed, the counter limits of disturbance duration and frame alignment signal errors count can be adjusted with MML command YES. Use the YEL command to find out the current values. For more information on command syntax, see the cor-responding Command Reference Manual.

• The system collects statistics on frame alignment signal errors in periods of 5 seconds into four different counters according to the number of errors observed (for example Counter 1: 1–39 / Counter 2: 40–79 / Counter 3: 80–159 / Counter 4: 160–).

• The system collects statistics on positive and negative slips into two separate counters (Exception: slips are not monitored in PDH-based ATM interfaces, PETs).

• The system collects the CRC errors from the near and the remote end into separate counters and calculates the following identifying figures from them: • TOTAL TIME, total time measured • AVAIL TIME, availability time • UNAVAIL TIME, unavailability time • error-free seconds EFS, (%) • errored seconds ES, (%) • severely errored seconds SES, (%)

DN04143903 365



• degraded minutes DM, (%). • background block errors BBE, (%)

The object of the measurement is PDH Exchange Terminal (PET) for E1/T1/JT1 PDH based ATM interfaces that is identified with exchange terminal type and index.


7.10.4 PCM statistics permanent measurement PCM STATISTICS PERMANENT MEASUREMENT

UNIT START TIME ET-14 2000-06-16 00:00

DISTURBANCES:

DISTTYPE COUNTER LIMITS (MS): 0010-0050 0050-0200 0200-1000 1000-

NOINSGN 0 0 0 0 FALOST 0 0 0 0 AIS 0 0 0 0 REMOTE 0 0 0 0

FRAME ALIGNMENT SIGNAL ERRORS:

COUNTER LIMITS (ERRORS/ 5 SEC) 001-0039 040-079 080-159 160-

1 0 0 0

SLIPS: POSITIVE NEGATIVE 0 0

CRC PERFORMANCE MONITORING:

TOTAL AVAIL UNVAIL TIME TIME TIME

LOCAL END 23:57:44 23:57:44 00:00:00 REMOTE END 23:57:44 23:57:44 00:00:00

( % ) EFS ES SES DM EB BBE

LOCAL END 100.00 0.00 0.00 0.00 0.00 0.00 REMOTE END 100.00 0.00 0.00 0.00 0.00 0.00

END OF REPORT

Explanations of the fields:

366 DN04143903




UNIT Identifies the exchange terminal; ET or PET and its index.

START TIME Starting date and time of measurement.

DISTTYPE Header for disturbances.

COUNTER LIMITS (MS) Header for counter limits of disturbances, MS = milliseconds (ms). Disturbances are divided into four counters according to their lasting time.

NOINSGN No incoming signal = cut offs of a signal.

FALOST Frame Alignment Lost.

AIS AIS signal received (all bits in one “1” state).

FRAME ALIGNMENT SIGNAL ERRORS Self explanatory header for FAS.

COUNTER LIMITS (ERRORS/ 5 SEC) Header for counter limits of FAS. FASs are divided into four counters according to how many there have been during a 5 seconds interval.

SLIPS Positive and negative slips. Exchange terminal type PET does not supervise slips and an notice text is output here instead of slips in that case.

CRC PERFORMANCE MONITORING Header for CRC4 (E1) or CRC6(T1 and JT1) measurements. If frame alignment mode does not support CRC, a notice text is output here instead of the actual measurement results.

TOTAL TIME The whole measurement time.

AVAIL TIME The availability time.

UNAVAIL TIME The unavailability time.

LOCAL END ET in own network element.

REMOTE END “ET” in the other end of the trunk.

EFS Error free seconds.

ES Errored seconds.

SES Seriously errored seconds.

DM Deteriorated minutes.

BBE Background block errors.

7.11 IMA logical interface measurement (514/202H)The IMA (Inverse Multiplexing for ATM) logical interface measurement measures a transmission path's ability to provide agreed quality between Far End and Near End for IMA interfaces. If satisfactory quality is not provided, the transmission path cannot be used.

The IMA measurement measures both link-specific and group-specific parameters: some of the measurement counters are provided per physical link and some per IMA group.

g In this document the counter descriptions are presented only for IMA link 1, but there are identical counters for all 8 links, see table Counters for IMA links 2–8.

The object is IMA group that is identified by IMA group id.


DN04143903 367



IMA related performance parameters are monitored and performance data is collected for all ATM interfaces that are based on IMA.

IMA group specific counters

Counter ID: M514C0 Network element name: GR_UAS_IMA

Version: 5.2 NetAct name: GR_UAS_IMA

Description: Unavailable seconds of IMA Group. An interval when the IMA group is unable to transfer cells. The number of one second intervals when the Group Traffic State Machine (GTSM) is down.

Updated: The counter is updated for every second that the IMA group is unavailable.


Unit: s Range: N/A Example values: 15




AF-PHY-0086.001, 1.1





Counter ID: M514C1 Network element name: GR_FC

Version: 5.1 NetAct name: GR_FC

Description: The number of Near End group failures in the IMA Group. The number of possible Near End group failure alarms when conditions are config-abort and there are insufficient links.

Updated: The counter is incremented when Config-Aborted (the FE tries to use unacceptable configura-tion parameters) or Insufficient-Links (when less than the minimum number of transmit (PTx) or receive (PRx) links are Active) conditions occur.






AF-PHY-0086.001, 1.1





368 DN04143903




IMA group link specific dataThere are 8 physical links in each IMA group, the next counters are used for each physical link.

Counter ID: M514C2 Network element name: UNIT_INDEX1

Version: 5.1 NetAct name: UNIT_INDEX1

Description: IMA link identification number.

Updated: Not updated, not a counter.




Operability class:






Counter ID: M514C3 Network element name: IV_IMA1

Version: 5.1 NetAct name: IV_IMA1

Description: ICP violations of the IMA link. The number of errored, invalid or missing IMA Control Protocol (ICP) cells on an IMA link, except during seconds where a SES-IMA or UAS-IMA condition is reported.

Updated: When an ICP violation is detected. The counter is updated when a cell with good HEC, CRC and CID is received. This means that the ICP is in the expected frame position with unexpected IMA OAM Label, unexpected LID, unexpected IMA ID, unexpected IMA frame number, unexpected ICP cell offset, or the received M not equal to the expected M of the IMA group.






AF-PHY-0086.001, 1.1





Counter ID: M514C4 Network element name: SES_IMA1

DN04143903 369



Version: 5.2 NetAct name: SES_IMA1

Description: Severely errored seconds at the near end of the IMA link. The number of one second inter-vals at Near End containing >=30% of the ICP cells counted as IV-IMA or one or more link defects (for example, LOS, OOF/LOF, AIS or LCD), LIF or LODS defects. This does not include defects during the UAS-IMA condition.

Updated: SES_IMA counter is updated (meaning that a second is defined as a severely errored second) when 30% or more of the ICP cells received from the link are errored. The errored ICP cells are counted as errored according to the IV-IMA (IV is ICP cell violation) definition. Also the more severe errors in the link, such as LOS, OOF/LOF,AIS,LCD,LIF or LODS, automatically cause the second to be considered as severely errored.






AF-PHY-0086.001, 1.1





Counter ID: M514C5 Network element name: SES_IMA_FE1

Version: 5.2 NetAct name: SES_IMA_FE1

Description: Severely errored seconds at the far end of the IMA link. The number of one second intervals at the far end containing one or more RDI-IMA defects. This does not include defects during UAS-IMA-FE conditions.

Updated: The counter is updated when one or more RDI-IMA defects are detected.






AF-PHY-0086.001, 1.1





Counter ID: M514C6 Network element name: UAS_IMA1

Version: 5.2 NetAct name: UAS_IMA1

370 DN04143903




Description: Unavailable seconds at the near end of the IMA link. At the near end the period of unavail-able time begins at the start of ten consecutive SES-IMAs. This includes the first ten seconds to enter the UAS-IMA condition and ends at the start of the first ten consecutive seconds with no SES-IMA. This does not include the last ten seconds to exit the UAS-IMA condition.

Updated: A count of 1-second intervals for which the near end IMA link is unavailable. The near end IMA link becomes unavailable at the onset of 10 contiguous SES-IMAs. The 10 SES-IMAs are included in the unavailable time. Once unavailable, the near end IMA link becomes available at the onset of 10 contigu-ous seconds with no SES-IMAs. The 10 seconds with no SES-IMAs are excluded from the unavailable time.






AF-PHY-0086.001, 1.1





Counter ID: M514C7 Network element name: UAS_IMA_FE1

Version: 5.2 NetAct name: UAS_IMA_FE1

Description: Unavailable seconds at the far end of the IMA link. At the far end the period of unavailable time begins at the start of ten consecutive SES-IMA-FE. This includes the first ten seconds to enter the UAS-IMA-FE condition and ends at the start of ten consecutive seconds with no SES-IMA-FE. This does not include the last ten seconds to exit the UAS-IMA-FE condition.

Updated: A count of 1-second intervals for which the far end IMA link is unavailable. The far end IMA link becomes unavailable at the onset of 10 contiguous SES-IMAs. The 10 SES-IMAs are included in the unavailable time. Once unavailable, the far end IMA link becomes available at the onset of 10 contiguous seconds with no SES-IMAs. The 10 seconds with no SES-IMAs are excluded from the unavailable time.






AF-PHY-0086.001, 1.1





DN04143903 371



Counter ID: M514C8 Network element name: TX_UUS_IMA1

Version: 5.2 NetAct name: TX_UUS_IMA1

Description: Tx unusable seconds at the near end of the IMA link. The number of seconds that the Near End Link State Machine (LSM) is in the 'unusable' state, which means that the IMA link is unable to transfer traffic.

Updated: The counter is updated when a link is unusable: the link is configured, but not in use because of a fault, inhibition, etc. There are many reasons for transmit link states: test failed (mis-connectivity has been found as a result of a test), Fault (a fault has been detected either on the link or in the link protocol), Inhibited (the operation of the link is blocked because of a locally defined application-dependent or imple-mentation-dependent reason. Otherwise, the link may be used.






AF-PHY-0086.001, 1.1





Counter ID: M514C9 Network element name: RX_UUS_IMA1

Version: 5.2 NetAct name: RX_UUS_IMA1

Description: Rx unusable seconds at the near end of the IMA link. The number of seconds that the Near End Link State Machine (LSM) is in the 'unusable' state, which means that the IMA link is unable to receive traffic.

Updated: Unusable means that the link is configured, but cannot be used. The receive link states include: idle (insufficient information to start link establishment), failed (the receiver has failed because of the per-sistence of a defined defect (examples of defects are LCD, LIF, and LODS)), inhibited (the operation of the link is blocked because of a locally defined application-dependent or implementation-dependent reason (the link may be used for testing)).






AF-PHY-0086.001, 1.1





372 DN04143903




Counter ID: M514C10 Network element name: TX_UUS_IMA_FE1

Version: 5.2 NetAct name: TX_UUS_IMA_FE1

Description: Tx unusable seconds at the far end of the IMA link. The number of seconds that the Far End Link State Machine (LSM) is in the 'unusable' state, which means that the IMA link is unable to transfer traffic.

Updated: The counter is updated when a link is unusable: the link is configured, but not in use because of a fault, inhibition, etc. There are many reasons for the transmit link state: Test failed (mis-connectivity has been found as a result of a test), Fault (a fault has been detected either on the link or in the link pro-tocol), Inhibited (the operation of the link is blocked because of a locally defined application-dependent or implementation-dependent reason. Otherwise, the link may be used.






AF-PHY-0086.001, 1.1





Counter ID: M514C11 Network element name: RX_UUS_IMA_FE1

Version: 5.2 NetAct name: RX_UUS_IMA_FE1

Description: Rx unusable seconds at the far end of the IMA link. The number of seconds that the Far End Link State Machine (LSM) is in the 'unusable' state, which means that the IMA link is unable to receive traffic.

Updated: Unusable means that the link is configured, but cannot be used. The receive link states include: idle (insufficient information to start link establishment), failed (the receiver has failed because of the per-sistence of a defined defect (examples of defects are LCD, LIF, and LODS)), inhibited (the operation of the link is blocked for a locally defined application-dependent or implementation-dependent reason (the link may be used for testing)).






AF-PHY-0086.001, 1.1




DN04143903 373




Counter ID: M514C12 Network element name: TX_FC1

Version: 5.1 NetAct name: TX_FC1

Description: Near End Tx link failure of the IMA link. The number of Near End Tx link failures (Tx-miscon-nected and Tx-Fault alarm condition entries). Not in use, the counter value is always zero.







AF-PHY-0086.001, 1.1





Counter ID: M514C13 Network element name: RX_FC1

Version: 5.1 NetAct name: RX_FC1

Description: Near End Rx link failure count of the IMA link. The number of Near End Rx link failures, Loss of IMA Frame (LIF), Link Out of Delay Synchronization (LODS) and Rx-Fault alarm condition entries.

Updated: When the Rx link is detected as misconnected. This is reported when the IMA unit has deter-mined that the Rx link is not connected to the same FE IMA unit as the other Rx links in the group.






AF-PHY-0086.001, 1.1





Counter ID: M514C14 Network element name: UNIT_INDEX2

374 DN04143903




The counters with similar descriptions are available for all IMA links; see counters listed in the table below.

Version: 5.1 NetAct name: UNIT_INDEX2

Description: IMA link identification number.

Updated: Not updated, not a counter.




Operability class:






No Counter name

M514C15 IV_IMA2

M514C16 SES_IMA2

M514C17 SES_IMA_FE2

M514C18 UAS_IMA2

M514C19 UAS_IMA_FE2

M514C20 TX_UUS_IMA2

M514C21 RX_UUS_IMA2

M514C22 TX_UUS_IMA_FE2

M514C23 RX_UUS_IMA_FE2

M514C24 TX_FC2

M514C25 RX_FC2

M514C26 UNIT_INDEX3

M514C27 IV_IMA3

M514C28 SES_IMA3

M514C29 SES_IMA_FE3

M514C30 UAS_IMA3

M514C31 UAS_IMA_FE3

M514C32 TX_UUS_IMA3

M514C33 RX_UUS_IMA3



Table 20 Counters for IMA links 2–8

DN04143903 375



M514C36 TX_FC3

M514C37 RX_FC3

M514C38 UNIT_INDEX4

M514C39 IV_IMA4

M514C40 SES_IMA4

M514C41 SES_IMA_FE4

M514C42 UAS_IMA4

M514C43 UAS_IMA_FE4

M514C44 TX_UUS_IMA4

M514C45 RX_UUS_IMA4



M514C48 TX_FC4

M514C49 RX_FC4

M514C50 UNIT_INDEX5

M514C51 IV_IMA5

M514C52 SES_IMA5

M514C53 SES_IMA_FE5

M514C54 UAS_IMA5

M514C55 UAS_IMA_FE5

M514C56 TX_UUS_IMA5

M514C57 RX_UUS_IMA5



M514C60 TX_FC5

M514C61 RX_FC5

M514C62 UNIT_INDEX6

M514C63 IV_IMA6

M514C64 SES_IMA6

M514C65 SES_IMA_FE6

M514C66 UAS_IMA6

M514C67 UAS_IMA_FE6

M514C68 TX_UUS_IMA6

M514C69 RX_UUS_IMA6



No Counter name

Table 20 Counters for IMA links 2–8 (Cont.)

376 DN04143903




7.12 STM-1 interface measurement (513/201H)The measurement measures the ability of different hierarchical levels of SDH connec-tion to provide agreed quality at the speed of STM-1 per SDH exchange terminal (SET). The measurement provides information about the amount of errored background blocks (EBB), amount of errored seconds (ES), amount of severely errored seconds (SES) and amount of unavailable seconds (UAS). The measurement counters are collected from the SDH termination equipment on physical interface (SET).

The object is SDH exchange terminal (SET) that is identified by exchange terminal type (SET) and index. There are also counters for SDH paths terminated to a certain SDH exchange terminal. Because VC-4 mapping is used, the STM-1 interface contains one path. The counters of PATH1 are updated and others are left to zero.

M514C72 TX_FC6

M514C73 RX_FC6

M514C74 UNIT_INDEX7

M514C75 IV_IMA7

M514C76 SES_IMA7

M514C77 SES_IMA_FE7

M514C78 UAS_IMA7

M514C79 UAS_IMA_FE7

M514C80 TX_UUS_IMA7

M514C81 RX_UUS_IMA7



M514C84 TX_FC7

M514C85 RX_FC7

M514C86 UNIT_INDEX8

M514C87 IV_IMA8

M514C88 SES_IMA8

M514C89 SES_IMA_FE8

M514C90 UAS_IMA8

M514C91 UAS_IMA_FE8

M514C92 TX_UUS_IMA8

M514C93 RX_UUS_IMA8



M514C96 TX_FC8

M514C97 RX_FC8

No Counter name

Table 20 Counters for IMA links 2–8 (Cont.)

DN04143903 377




The figure below describes how different defect types cause the increment of counters.

Figure 13 Relation between defect types and counters

There is a restriction in defects that effect far-end counters. If there is a near-end SES caused by near-end defect then far-end path at same stage is assumed error free. This is because the far-end error indications and counts got from SDH frame are possibly cor-rupted because of near-end defects.

Some of the measurement counters are for the whole interface and some are defined by path. Because only VC-4 mapping is used, the STM-1 interface contains one path. The counters of PATH1 are updated and others are left to zero.

Line LOS / LOF

Line AIS

High order path AIS / LOP / tracemismatch / LCD / Payload labelmismatch / unequipped

Line RDI

High order path RDI

Reg

ener

ator

section

SES

Nea

r end

multip

laye

r section

SES

Nea

r end

high

orde

r path

SES

Faren

dm

ultip

lexse

ction

SES

Faren

dhigh

orde

r path

SES

Counter ID: M513C0 Network element name: REG_BBE

Version: 5.1 NetAct name: REG_BBE

Description: Regenerator section background block errors. An errored block is a block in which one or more bits have an error. B1 byte in the section overhead header (SOH) is used for regenerator section error monitoring using the Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous STM frame after scrambling, and is placed in byte B1 of the current frame before scrambling. In this case the block means STM-1 frame.

Updated: The counter is incremented when one or more bit errors are detected in a block (STM-1 frame). The counter is not updated during the SES and UAS conditions.





378 DN04143903




Related to feature:

RAN 1.032: STM-1 Physical Interface (Japan)

RAN 1.035: STM-1 Physical Interface

RAN 1.5024: RNC STM-1/3xVC-3 interface

RAN 1.5026: RNC STM-1/VC-4 interface


ITU-T G.826, 12/2002





Counter ID: M513C1 Network element name: REG_ES

Version: 5.2 NetAct name: REG_ES

Description: Regenerator section errored seconds. This is the number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the regeneration section (B1) errors and LOS or LOF events. In this case the block means STM-1 frame.

Updated: The counter is incremented when a second contains one or more errored blocks or at least one defect. The counter is not updated during the UAS condition.




M513C2: REG_SES


Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C2 Network element name: REG_SES

Version: 5.2 NetAct name: REG_SES

DN04143903 379



Description: Regenerator section severely errored seconds. The number of one second periods which contained >= threshold errored blocks or at least one defect. The threshold can be handled by the Exchange terminal configuration handling YAN-MML. The default value of the threshold is 30%. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the regenerator section (B1) errors and regenerator section LOF/LOS events. In this case the block means STM-1 frame.

Updated: The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect.





Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C9 Network element name: REG_UAS

Version: 5.2 NetAct name: REG_UAS

Description: Regenerator section is unavailable for a number of seconds (ITU-T G.826). The period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time.

Updated: The counter is updated after ten consecutive severely errored second (SES) events are detected. These ten seconds are included in the counter. Updating the counter is stopped when ten con-secutive non-SES events are detected. These ten seconds are not included in the counter.





Related to feature:








380 DN04143903






Counter ID: M513C10 Network element name: NE_MUX_UAS

Version: 5.2 NetAct name: MUX_UAS

Description: Multiplex section unavailable seconds at the near end A period of unavailable time begins at the start of ten consecutive SES events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time.






Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C11 Network element name: NE_MUX_BBE

Version: 5.1 NetAct name: NE_MUX_BBE

Description: Multiplex section background block errors at the near end. An errored block is a block in which one or more bits have an error. B2 byte in the section overhead header (SOH) is used for multiplex section error monitoring using Bit Interleaved Parity 24 (BIP-24) code, in an even parity. The BIP-24 is computed over all the bits of the previous STM frame, excluding RSOH, and is placed in byte B2 of the current frame before scrambling. In this case the block means STM-1 frame.

Updated: The counter is incremented when one or more bit errors are detected in a block (STM-1 frame, excluding RSOH). The counter is not updated during the SES and UAS conditions.





DN04143903 381



Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C12 Network element name: NE_MUX_ES

Version: 5.2 NetAct name: NE_MUX_ES

Description: Multiplex section errored seconds at the near end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are multiplex section (B2) errors and MS-AIS.





M513C13: NE_MUX_SES


Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C13 Network element name: NE_MUX_SES

Version: 5.2 NetAct name: NE_MUX_SES

Description: Multiplex section severely errored seconds at the near end. The number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are multiplex section (B2) errors and MS-AIS. In this case the block means STM-1 frame. During the SES condition, counter NE_MUX_ES M513C12 is also incremented.

382 DN04143903




Updated: The counter is incremented when a second contains errored blocks more or equal to that in the defined threshold or at least one defect. The counter is not updated during the UAS condition.





Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C14 Network element name: NE_PATH1_UAS

Version: 5.2 NetAct name: NE_PATH1_UAS

Description: Path termination section unavailable seconds at the near end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are con-sidered to be part of the unavailable time. A new period of available time begins at the start of ten con-secutive non-SES events. These ten seconds are considered to be part of the available time.






Related to feature:






ITU-T G.826, 12/2002





DN04143903 383



Counter ID: M513C15 Network element name: NE_PATH1_BBE

Version: 5.1 NetAct name: NE_PATH1_BBE

Description: Path termination section background block errors at the near end. An errored block is a block in which one or more bits have an error. B3 byte in the higher order path overhead header (HO-POH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-4) and is placed in byte B3 of the current frame. In this case the block means virtual container.

Updated: The counter is incremented when one or more bit errors are detected in a block (virtual con-tainer). The counter is not updated during the SES and UAS conditions.





Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C16 Network element name: NE_PATH1_ES

Version: 5.2 NetAct name: NE_PATH1_ES

Description: Path termination section errored second at the near end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container.





M513C17: NE_PATH1_SES


Related to feature:






ITU-T G.826, 12/2002

384 DN04143903








Counter ID: M513C17 Network element name: NE_PATH1_SES

Version: 5.2 NetAct name: NE_PATH1_SES

Description: Path termination section severely errored seconds at the near end. The number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container. During the SES condition, counter NE_PATH1_ES M513C16 is also incremented.






Related to feature:






ITU-T G.826, 12/2002












DN04143903 385




Related to feature:






ITU-T G.826, 12/2002







Description: Path termination section background block errors at the near end An errored block is a block in which one or more bits have an error. B3 byte in the higher order path overhead header (HO-POH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-4) and is placed in byte B3 of the current frame. In this case the block means virtual container.






Related to feature:






ITU-T G.826, 12/2002







Description: Path termination section errored seconds at the near end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container.

386 DN04143903










Related to feature:






ITU-T G.826, 12/2002













Related to feature:






ITU-T G.826, 12/2002





DN04143903 387











Related to feature:






ITU-T G.826, 12/2002







Description: Path termination section background block errors at the near end. An errored block is a block in which one or more bits have an error. B3 byte in the higher order path overhead header (HO-POH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-4) and is placed in byte B3 of the current frame. In this case the block means virtual container.






Related to feature:






ITU-T G.826, 12/2002

388 DN04143903










Description: Path termination section errored seconds at the near end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (B3) errors, AU-AIS, LOP, PLM, TIM, UNEQ and LCD. In this case the block means virtual container.







Related to feature:






ITU-T G.826, 12/2002











DN04143903 389





Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C26 Network element name: FE_MUX_UAS

Version: 5.2 NetAct name: FE_MUX_UAS

Description: Multiplex section unavailable seconds at the Far End. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are considered to be part of the unavailable time. A new period of available time begins at the start of ten consecutive non-SES events. These ten seconds are considered to be part of the available time.






Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C27 Network element name: FE_MUX_BBE

Version: 5.1 NetAct name: FE_MUX_BBE

390 DN04143903




Description: Multiplex section background block errors at the far end. An errored block is a block in which one or more bits have an error. M1 byte conveys the count of errored blocks which is calculated by the far end from its receiving blocks by using B2 bytes at multiplexer level. B2 bytes are the bytes allocated for a multiplex section error monitoring function which is Bit Interleaved Parity 24 (BIP-24) code using even parity. The BIP-24 is computed over all bits of the previous STM frame excluding RSOH and is placed in byte B2 of the current frame. In this case the block means STM-1 frame.

Updated: The counter is incremented when one or more bit errors are detected in a block (STM-1 frame excluding the RSOH). The counter is not updated during SES and UAS conditions.





Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C28 Network element name: FE_MUX_ES

Version: 5.2 NetAct name: FE_MUX_ES

Description: Multiplex section errored second at the far end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are multiplex section (M1) errors and MS-RDI. In this case the block means STM-1 frame.





M513C29: FE_MUX_SES


Related to feature:






ITU-T G.826, 12/2002



DN04143903 391





Counter ID: M513C29 Network element name: FE_MUX_SES

Version: 5.2 NetAct name: FE_MUX_SES

Description: Multiplex section severely errored seconds at the far end. The number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are multiplex section (M1) errors and MS-RDI. In this case the block means STM-1 frame. During SES condition also counter FE_MUX_ES M513C28 is incremented.






Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C30 Network element name: FE_PATH1_UAS

Version: 5.2 NetAct name: FE_PATH1_UAS

Description: Path termination section unavailable seconds at the far end. A period of unavailable time begins at the start of ten consecutive severely errored second (SES) events. These ten seconds are con-sidered to be part of the unavailable time. A new period of available time begins at the start of ten con-secutive non-SES events. These ten seconds are considered to be part of the available time.






392 DN04143903




Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C31 Network element name: FE_PATH1_BBE

Version: 5.1 NetAct name: FE_PATH1_BBE

Description: Path termination section background block errors at the far end. An errored block is a block in which one or more bits have an error. G1 byte in the section overhead header (SOH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-4) and is placed in byte B3 of the current frame. In this case the block means virtual container.






Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C32 Network element name: FE_PATH1_ES

Version: 5.2 NetAct name: FE_PATH1_ES

Description: Path termination section errored seconds at the far end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are path termination section (G1) errors and HP-RDI. In this case the block means virtual container.

DN04143903 393







M513C33: FE_PATH1_SES


Related to feature:






ITU-T G.826, 12/2002





Counter ID: M513C33 Network element name: FE_PATH1_SES

Version: 5.2 NetAct name: FE_PATH1_SES

Description: Path termination section severely errored seconds at the far end. The number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path ter-mination section (G1) errors and HP-RDI. In this case the block means virtual container. During the SES condition also counter FE_PATH1_ES M513C32 is incremented.






Related to feature:






ITU-T G.826, 12/2002





394 DN04143903












Related to feature:






ITU-T G.826, 12/2002







Description: Path termination section background block errors at the far end. An errored block is a block in which one or more bits have an error. G1 byte in the section overhead header (SOH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all bits of the previous virtual container (VC-4) and is placed in byte B3 of the current frame. In this case the block means virtual container.






Related to feature:






ITU-T G.826, 12/2002

DN04143903 395









Description: Path termination section errored seconds at the far end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP-RDI. In this case the block means virtual container.







Related to feature:






ITU-T G.826, 12/2002







Description: Path termination section severely errored seconds at the far end. The number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path ter-mination section (G1) errors and HP- RDI. In this case the block means virtual container. During the SES condition counter FE_PATH2_ES M513C36 is also incremented.




396 DN04143903






Related to feature:






ITU-T G.826, 12/2002













Related to feature:






ITU-T G.826, 12/2002







DN04143903 397



Description: Path termination section background block errors at the far end. An errored block is a block in which one or more bits have an error. G1 byte in the section overhead header (SOH) is used for path termination section error monitoring using Bit Interleaved Parity 8 (BIP-8) code, in an even parity. The BIP-8 is computed over all the bits of the previous virtual container (VC-4) and is placed in byte B3 of the current frame. In this case the block means virtual container.






Related to feature:






ITU-T G.826, 12/2002







Description: Path termination section errored seconds at the far end. The number of seconds with one or more errored blocks or at least one defect. At the end of each one second interval the contents of the counters are obtained by the relevant managed objects. The objects are the path termination section (G1) errors and HP-RDI. In this case the block means virtual container.







Related to feature:






ITU-T G.826, 12/2002




398 DN04143903




7.13 SONET/SDH protection group measurement (516/204H)This measurement monitors the usage of protection groups configured for SONET or SDH transmission sections. The statistics can be used to follow transmission network quality.

The measurement provides information on the switchover events between the working SONET/SDH link and the protection SONET/SDH link in one SONET/SDH protection group. If there are multiple switchover events in one measured SONET/SDH protection group during one measurement period or successive measurement periods, the trans-mission network is unstable. The switchover events in the SONET/SDH protection group may be caused by, for example:

• given external switch commands • maintenance work of transmission network • maintenance work of far-end network element

Also check the active alarms for the sections of the protection group. The regenerator and multiplex section counters of the STM-1 measurement also maintain information about the condition of the sections. To improve the stability of the network, repair the




Description: Path termination section severely errored seconds at the far end. The number of one second periods which contain >= threshold errored blocks or at least one defect. The threshold can be handled by Exchange terminal configuration handling YAN-MML. At the end of each one second interval the contents of the counters may be obtained by the relevant managed objects. The objects are the path ter-mination section (G1) errors and HP-RDI. In this case the block means virtual container. The path termi-nation section is one of the SDH layers (regeneration, multiplex and path) (ITU-T G.707). During the SES condition counter FE_PATH3_ES M513C40 is also incremented.






Related to feature:






ITU-T G.826, 12/2002





DN04143903 399



transmission network failures according to the active alarms or investigate the reasons for the network failure more thoroughly with the help of the STM-1 measurement coun-ters.

The object of the measurement is SDH exchange terminal (SET) that is identified by exchange terminal type (SET) and index. The measurement identifier is 516/204H.

Counter ID: M516C0 Network element name: PROT_GR_PSC

Version: 3.1 NetAct name: PROT_GR_PSC

Description: Protection Switch Count of Protection Group. This counter contains the number of switches to the protection section and switches to the working section.

Updated: The counter is updated when traffic is switched from working section to protection section or from protection section to working section.

Logical type: Sum Trigger type: Sampling interval:

Unit: Integer number Range: Example values: 13




ITU-T G774.1, 2001.02





Counter ID: M516C1 Network element name: PROT_GR_PSD

Version: 3.1 NetAct name: PROT_GR_PSD

Description: Protection Switch Duration of Protection Group. The value of this counter is the number of seconds the traffic is in protection section.

Updated: The counter is updated at one second intervals when the traffic is in protection section.


Unit: s Range: Example values: 13




ITU-T G774.1, 2001.02





400 DN04143903



IP transport measurements

8 IP transport measurements

8.1 TCP/IP protocol measurement (563/233H)The TCP/IP protocol measurement provides information about the TCP/IP stack of dif-ferent units of the network element. The TCP/IP protocol measurement measures the transactions of UDP, ICMP, and IP versions 4 and 6. It also measures TCP transactions.

The object is a computer unit that is identified by unit type and index. The measurement identifier is 563/233H.

g The counters of M563 measurement do not show the user plane and control plane traffic in NPGE or NPS1 because the traffic is forwarded by APP hardware and therefore not visible to the computer unit's IP-stack that M563 measures. Examples of protocols whose traffic is visible in NPGE and NPS1 are OSPF, ARP, BFD and ICMP.

Counter ID: M563C0 Network element name: IPS_TOTAL

Version: 4.1 NetAct name: IPS_TOTAL

Description: Received IP datagrams. The total number of input IP datagrams received from interfaces, including those received in error.

Updated: When receiving IPv4 datagrams, this counter will be updated before further processing.










Counter ID: M563C1 Network element name: IPS_BADSUM

Version: 4.1 NetAct name: IPS_BADSUM

Description: Received IP datagrams with errored checksum. The number of input IP datagrams dis-carded because of errors in their checksum.

Updated: When an IPv4 datagram is received with errored checksum.







DN04143903 401

RNC Counters - Transport and HW Part IP transport measurements





Counter ID: M563C2 Network element name: IPS_TOOSMALL

Version: 4.1 NetAct name: IPS_TOOSMALL

Description: Too small IP datagrams received. The number of discarded IP datagrams because they are too small to contain an IP packet.

Updated: When an IPv4 datagram is received, but its length is less than 20 bytes, which is too little to contain the IP header part, this counter will be updated.










Counter ID: M563C3 Network element name: IPS_TOOSHORT

Version: 4.1 NetAct name: IPS_TOOSHORT

Description: Too short IP datagrams received. The number of discarded IP datagrams with invalid data length.

Updated: When an IPv4 datagram is received, and the received data length does not equal the length value in the IP header, this counter will be updated.










402 DN04143903




Counter ID: M563C4 Network element name: IPS_TOOLONG

Version: 4.1 NetAct name: IPS_TOOLONG

Description: Too long IP datagrams received. The number of discarded IP datagrams the length of which exceeds the maximum IP packet size.

Updated: This counter is updated when the length of a received IPv4 datagram (including the assembled datagrams from IP fragments) exceeds 65535.










Counter ID: M563C5 Network element name: IPS_BADHLEN

Version: 4.1 NetAct name: IPS_BADHLEN

Description: Received IP datagrams with bad header length. The number of input IP datagrams dis-carded because of invalid header length.

Updated: When an IPv4 datagram with invalid header length is received.










Counter ID: M563C6 Network element name: IPS_BADLEN

Version: 4.1 NetAct name: IPS_BADLEN

Description: Received IP datagrams with bad length. The number of input IP datagrams discarded because of inconsistent IP header and IP data length.

Updated: When the length of a received IPv4 datagram is not consistent with the IP header and IP data length.

DN04143903 403












Counter ID: M563C7 Network element name: IPS_BADOPTIONS

Version: 4.1 NetAct name: IPS_BADOPTIONS

Description: Received IP datagrams with errors in IP options. The number of input IP datagrams dis-carded because of errors discovered in processing their header IP options.

Updated: When an error is found during the processing of the options field for a received IPv4 datagram










Counter ID: M563C8 Network element name: IPS_BADVERS

Version: 4.1 NetAct name: IPS_BADVERS

Description: Received IP datagrams with version errors. The number of input IP datagrams discarded because of version number mismatch.

Updated: When an IPv4 datagram is received but its version value in the header is not 4.








404 DN04143903






Counter ID: M563C9 Network element name: IPS_FRAGMENTS

Version: 4.1 NetAct name: IPS_FRAGMENTS

Description: IP fragments received.

Updated: When an IPv4 fragment is received.










Counter ID: M563C10 Network element name: IPS_FRAGDROPPED

Version: 4.1 NetAct name: IPS_FRAGDROPPED

Description: IP fragments dropped. The number of discarded IP fragments because of duplicates or insuf-ficient space.

Updated: When an IPv4 fragment is dropped, for example, because of duplicates or insufficient space.










Counter ID: M563C11 Network element name: IPS_FRAGTIMEOUT

Version: 4.1 NetAct name: IPS_FRAGTIMEOUT

Description: IP fragments timed out. The number of IP fragments dropped after time-out.

DN04143903 405



Updated: When an IPv4 fragment is dropped after time-out.










Counter ID: M563C12 Network element name: IPS_RCVMEMDROP

Version: 4.1 NetAct name: IPS_RCVMEMDROP

Description: The number of IP fragments dropped because of insufficient memory.

Updated: When an IPv4 fragment is dropped because of insufficient memory.










Counter ID: M563C13 Network element name: IPS_BADFRAGS

Version: 4.1 NetAct name: IPS_BADFRAGS

Description: Malformed IP fragments dropped.

Updated: The length of an IP fragment should be non-zero multiple of 8 bytes. If one IP fragment is received, but its length is not in accord with this rule, the IP fragment is dropped and the counter is updated.







406 DN04143903







Counter ID: M563C14 Network element name: IPS_REASSEMBLED

Version: 4.1 NetAct name: IPS_REASSEMBLED

Description: Reassembled IP datagrams. The number of IP datagrams successfully reassembled.

Updated: When an IPv4 datagram has been successfully reassembled.










Counter ID: M563C15 Network element name: IPS_DELIVERED

Version: 4.1 NetAct name: IPS_DELIVERED

Description: Received IP datagrams delivered successfully. The total number of input IP datagrams suc-cessfully delivered.

Updated: When an IPv4 datagram has been successfully delivered to upper level (TCP,UDP..) without errors.










Counter ID: M563C16 Network element name: IPS_NOPROTO

Version: 4.1 NetAct name: IPS_NOPROTO

DN04143903 407



Description: Received IP datagrams with unknown protocol. The number of locally addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.

Updated: When a locally addressed IPv4 datagram has been dropped because of an unknown or unsup-ported protocol.










Counter ID: M563C17 Network element name: IPS_FORWARD

Version: 4.1 NetAct name: IPS_FORWARD

Description: Forwarded IP datagrams. The number of input IP datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to the correct final destination.

Updated: When an IPv4 datagram is received and it is not locally addressed, it will be forwarded on the basis of the route configuration, and this counter will be updated.










Counter ID: M563C18 Network element name: IPS_CANTFORWARD

Version: 4.1 NetAct name: IPS_CANTFORWARD

Description: Received IP datagrams not forwardable. The number of input datagrams discarded because the IP address in their IP header destination field was not a valid address to be forwarded to.

Updated: When an IPv4 datagram is received and needs to be forwarded, but cannot be forwarded because, for example, the address is not valid, forwarding is not enabled, the interface is not UP, the datagram will be dropped and the counter will be updated.


408 DN04143903












Counter ID: M563C19 Network element name: IPS_REDIRECTSENT

Version: 4.1 NetAct name: IPS_REDIRECTSENT

Description: The number of redirect messages sent.

Updated: When an IPv4 datagram is forwarded and a redirect message is sent.










Counter ID: M563C20 Network element name: IPS_LOCALOUT

Version: 4.1 NetAct name: IPS_LOCALOUT

Description: IP datagrams sent from this host. The total number of IP datagrams generated by the system, not forwarded.

Updated: When an IPv4 datagram is generated by the entity and sent out (not forwarded).










DN04143903 409



Counter ID: M563C21 Network element name: IPS_RAWOUT

Version: 4.1 NetAct name: IPS_RAWOUT

Description: Raw IP datagrams. The total number of IP datagrams generated. The number of packets sent with the fabricated IP header.

Updated: When an IPv4 datagram is generated on the basis of the fabricated IP header.










Counter ID: M563C22 Network element name: IPS_ODROPPED

Version: 4.1 NetAct name: IPS_ODROPPED

Description: Outgoing IP datagrams discarded. The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded for resource shortages, for example, lack of buffer space.

Updated: When an outgoing IPv4 datagram is discarded, for example, because of insufficient buffer space.










Counter ID: M563C23 Network element name: IPS_NOROUTE

Version: 4.1 NetAct name: IPS_NOROUTE

Description: Outgoing IP datagrams, no route found. The number of IP datagrams discarded because no route could be found to transmit them to their destination.

410 DN04143903




Updated: When an outgoing IPv4 datagram is discarded because no route for the destination could be found.










Counter ID: M563C24 Network element name: IPS_FRAGMENTED

Version: 4.1 NetAct name: IPS_FRAGMENTED

Description: Outgoing IP datagrams fragmented. The number of outgoing IP datagrams that have been successfully fragmented at this entity.

Updated: When an outgoing IPv4 datagram is successfully fragmented.










Counter ID: M563C25 Network element name: IPS_OFRAGMENTS

Version: 4.1 NetAct name: IPS_OFRAGMENTS

Description: Outgoing IP datagram fragments created. The number of outgoing IP datagram fragments that have been generated as a result of fragmentation at this entity.

Updated: When an outgoing IPv4 datagram fragment is generated.






DN04143903 411







Counter ID: M563C26 Network element name: IPS_FASTFORWARD

Version: 4.1 NetAct name: IPS_FASTFORWARD

Description: IP datagrams fast-forwarded.

Updated: Fast-forwarding is not currently supported, so this counter is not updated.










Counter ID: M563C27 Network element name: IPS_CANTFRAG

Version: 4.1 NetAct name: IPS_CANTFRAG

Description: IP datagrams fragment failed. The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but the fragmenting failed.

Updated: When an outgoing IPv4 datagram needs to be fragmented at this entity, but its DF in the header has been set as 1 (Fragments not allowed).










Counter ID: M563C28 Network element name: IPS_NOGIF

412 DN04143903




Version: 4.1 NetAct name: IPS_NOGIF

Description: No match gif IP datagrams. Tunneling IP datagrams that cannot find match gif.

Updated: Tunneling is not currently supported, so this counter is not updated.










Counter ID: M563C29 Network element name: IPS_BADADDR

Version: 4.1 NetAct name: IPS_BADADDR

Description: The number of discarded IP datagrams because source address is internal loopback address but the receiving interface is not loopback.

Updated: When an IPv4 datagram's source IP address is an internal host loopback address but its receiv-ing interface is not loopback.










Counter ID: M563C30 Network element name: ICPS_ERROR

Version: 4.1 NetAct name: ICPS_ERROR

Description: The number of ICMPv4 error messages sent out, excluding the ICMPv4 Redirect message.

Updated: When an ICMPv4 error message other than Redirect is sent out.





DN04143903 413








Counter ID: M563C31 Network element name: ICPS_OLDICMP

Version: 4.1 NetAct name: ICPS_OLDICMP

Description: The number of received IP datagrams including ICMP error messages.

Updated: When an IP datagram with ICMP error message is received. The error is not reported to upper layers because the datagram is an ICMP error message.










Counter ID: M563C32 Network element name: ICPS_INECHOREPLY

Version: 4.1 NetAct name: ICPS_INECHOREPLY

Description: Received ICMPv4 Echo Reply messages. The number of ICMP Echo Reply messages received.

Updated: When an ICMPv4 Echo reply message is received.










414 DN04143903




Counter ID: M563C33 Network element name: ICPS_INUNREACH

Version: 4.1 NetAct name: ICPS_INUNREACH

Description: Received ICMPv4 Destination Unreachable messages. The number of ICMP Destination Unreachable messages received.

Updated: When an ICMPv4 destination unreachable message is received.










Counter ID: M563C34 Network element name: ICPS_INSOURCEQUENCH

Version: 4.1 NetAct name: ICPS_INSOURCEQUENCH

Description: Received ICMPv4 Source Quench messages The number of ICMP Source Quench messages received.

Updated: When an ICMPv4 source quench message is received.










Counter ID: M563C35 Network element name: ICPS_INREDIRECT

Version: 4.1 NetAct name: ICPS_INREDIRECT

Description: Received ICMPv4 Redirect messages The number of ICMP Redirect messages received.

Updated: When an ICMPv4 redirect message is received.



DN04143903 415










Counter ID: M563C36 Network element name: ICPS_INECHO

Version: 4.1 NetAct name: ICPS_INECHO

Description: Received ICMPv4 Echo messages The number of ICMP Echo (request) messages received.

Updated: When an ICMPv4 echo message is received.










Counter ID: M563C37 Network element name: ICPS_INROUTERADVERT

Version: 4.1 NetAct name: ICPS_INROUTERADVERT

Description: Received ICMPv4 Router Advertisement messages The number of ICMP Router Advertise-ment messages received.

Updated: When an ICMPv4 router advertisement message is received.










416 DN04143903




Counter ID: M563C38 Network element name: ICPS_INROUTERSOLICIT

Version: 4.1 NetAct name: ICPS_INROUTERSOLICIT

Description: Received ICMPv4 Router Solicitation messages. The number of ICMP Router Solicitation messages received.

Updated: When an ICMPv4 router solicitation message is received.










Counter ID: M563C39 Network element name: ICPS_INTIMXCEED

Version: 4.1 NetAct name: ICPS_INTIMXCEED

Description: Received ICMPv4 Time Exceeded messages. The number of ICMP Time Exceeded messages received.

Updated: When an ICMPv4 time exceeded message is received.










Counter ID: M563C40 Network element name: ICPS_INPARAMPROB

Version: 4.1 NetAct name: ICPS_INPARAMPROB

Description: Received ICMPv4 Parameter Problem messages. The number of ICMP Parameter Problem messages received.

Updated: When an ICMPv4 parameter problem message is received.


DN04143903 417











Counter ID: M563C41 Network element name: ICPS_INTSTAMP

Version: 4.1 NetAct name: ICPS_INTSTAMP

Description: Received ICMPv4 Timestamp messages. The number of ICMP Timestamp (request) messages received.

Updated: When an ICMPv4 timestamp message is received.










Counter ID: M563C42 Network element name: ICPS_INTSTAMPREPLY

Version: 4.1 NetAct name: ICPS_INTSTAMPREPLY

Description: Received ICMPv4 Timestamp Reply messages. The number of ICMP Timestamp Reply messages received.

Updated: When an ICMPv4 timestamp reply message is received.









418 DN04143903





Counter ID: M563C43 Network element name: ICPS_INIREQ

Version: 4.1 NetAct name: ICPS_INIREQ

Description: Received ICMPv4 Information Request messages. The number of ICMP Information Request messages received.

Updated: When an ICMPv4 information request message is received.










Counter ID: M563C44 Network element name: ICPS_INIREQREPLY

Version: 4.1 NetAct name: ICPS_INIREQREPLY

Description: Received ICMPv4 Information Reply messages. The number of ICMP Information Reply messages received.

Updated: When an ICMPv4 information reply message is received.










Counter ID: M563C45 Network element name: ICPS_INMASKREQ

Version: 4.1 NetAct name: ICPS_INMASKREQ

Description: Received ICMPv4 Address Mask Request messages. The number of ICMP Address Mask Request messages received.

DN04143903 419



Updated: When an ICMPv4 address mask request message is received.










Counter ID: M563C46 Network element name: ICPS_INMASKREPLY

Version: 4.1 NetAct name: ICPS_INMASKREPLY

Description: Received ICMPv4 Address Mask Reply messages. The number of ICMP Address Mask Reply messages received.

Updated: When an ICMPv4 address mask reply message is received.










Counter ID: M563C47 Network element name: ICPS_BADCODE

Version: 4.1 NetAct name: ICPS_BADCODE

Description: ICMPv4 messages with bad code fields. Number of ICMP messages that have bad code fields.

Updated: When an ICMPv4 message with a bad code field is found.







420 DN04143903







Counter ID: M563C48 Network element name: ICPS_TOOSHORT

Version: 4.1 NetAct name: ICPS_TOOSHORT

Description: Too short ICMP messages. The number of ICMP messages with the length of the ICMP header shorter than the minimum length.

Updated: When an ICMPv4 message is received with the length of the ICMP header shorter than the minimum length.










Counter ID: M563C49 Network element name: ICPS_CHECKSUM

Version: 4.1 NetAct name: ICPS_CHECKSUM

Description: ICMP message bad checksum. The number of ICMP messages with an invalid ICMP check-sum.

Updated: When an ICMPv4 message with a bad checksum is received.










Counter ID: M563C50 Network element name: ICPS_BADLEN

DN04143903 421



Version: 4.1 NetAct name: ICPS_BADLEN

Description: ICMP messages with bad length. The number of ICMP messages with an invalid ICMP body.

Updated: When an ICMPv4 message is received with bad length.










Counter ID: M563C51 Network element name: ICPS_OUTECHOREPLY

Version: 4.1 NetAct name: ICPS_OUTECHOREPLY

Description: Sent ICMPv4 Echo Reply messages. The number of ICMP Echo Reply messages sent.

Updated: When an ICMPv4 echo reply message is sent.










Counter ID: M563C52 Network element name: ICPS_OUTUNREACH

Version: 4.1 NetAct name: ICPS_OUTUNREACH

Description: Sent ICMPv4 Destination Unreachable messages. The number of ICMP Destination Unreachable messages sent.

Updated: When an ICMPv4 destination unreachable message is sent.






422 DN04143903








Counter ID: M563C53 Network element name: ICPS_OUTSOURCEQUENCH

Version: 4.1 NetAct name: ICPS_OUTSOURCEQUENCH

Description: Sent ICMPv4 Source Quench messages. The number of ICMP Source Quench messages sent.

Updated: When an ICMPv4 source quench message is sent.










Counter ID: M563C54 Network element name: ICPS_OUTREDIRECT

Version: 4.1 NetAct name: ICPS_OUTREDIRECT

Description: Sent ICMPv4 Redirect messages. The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirect messages.

Updated: When an ICMPv4 redirect message is sent.










Counter ID: M563C55 Network element name: ICPS_OUTECHO

DN04143903 423



Version: 4.1 NetAct name: ICPS_OUTECHO

Description: Sent ICMPv4 Echo messages. The number of ICMP Echo (request) messages sent.

Updated: When an ICMPv4 echo message is sent.










Counter ID: M563C56 Network element name: ICPS_OUTROUTERADVERT

Version: 4.1 NetAct name: ICPS_OUTROUTERADVERT

Description: Sent ICMPv4 Router Advertisement messages. The number of ICMP Router Advertisement messages sent.

Updated: When an ICMPv4 router advertisement message is sent.










Counter ID: M563C57 Network element name: ICPS_OUTROUTERSOLICIT

Version: 4.1 NetAct name: ICPS_OUTROUTERSOLICIT

Description: Sent ICMPv4 Router Solicitation messages. The number of ICMP Router Solicitation messages sent.

Updated: When an ICMPv4 router solicitation message is sent.





424 DN04143903









Counter ID: M563C58 Network element name: ICPS_OUTTIMXCEED

Version: 4.1 NetAct name: ICPS_OUTTIMXCEED

Description: Sent ICMPv4 Time Exceeded messages. The number of ICMP Time Exceeded messages sent.

Updated: When an ICMPv4 time exceeded message is sent.










Counter ID: M563C59 Network element name: ICPS_OUTPARAMPROB

Version: 4.1 NetAct name: ICPS_OUTPARAMPROB

Description: Sent ICMPv4 Parameter Problem messages. The number of ICMP Parameter Problem messages sent.

Updated: When an ICMPv4 parameter problem message is sent.










DN04143903 425



Counter ID: M563C60 Network element name: ICPS_OUTTSTAMP

Version: 4.1 NetAct name: ICPS_OUTTSTAMP

Description: Sent ICMPv4 Timestamp messages. The number of ICMP Timestamp (request) messages sent.

Updated: When an ICMPv4 timestamp message is sent.










Counter ID: M563C61 Network element name: ICPS_OUTTSTAMPREPLY

Version: 4.1 NetAct name: ICPS_OUTTSTAMPREPLY

Description: Sent ICMPv4 Timestamp Reply messages. The number of ICMP Timestamp Reply messages sent.

Updated: When an ICMPv4 timestamp reply message is sent.










Counter ID: M563C62 Network element name: ICPS_OUTIREQ

Version: 4.1 NetAct name: ICPS_OUTIREQ

Description: Sent ICMPv4 Information Request messages. The number of ICMP Information Request messages sent.

Updated: When an ICMPv4 information request message is sent.



426 DN04143903











Counter ID: M563C63 Network element name: ICPS_OUTIREQREPLY

Version: 4.1 NetAct name: ICPS_OUTIREQREPLY

Description: Sent ICMPv4 Information Reply messages. The number of ICMP Information Reply messages sent.

Updated: When an ICMPv4 information reply message is sent.










Counter ID: M563C64 Network element name: ICPS_OUTMASKREQ

Version: 4.1 NetAct name: ICPS_OUTMASKREQ

Description: Sent ICMPv4 Address Mask Request messages. The number of ICMP Address Mask Request messages sent.

Updated: When an ICMPv4 address mask request message is sent.










DN04143903 427



Counter ID: M563C65 Network element name: ICPS_OUTMASKREPLY

Version: 4.1 NetAct name: ICPS_OUTMASKREPLY

Description: Sent ICMPv4 Address Mask Reply messages. The number of ICMP Address Mask Reply messages sent.

Updated: When an ICMPv4 address mask reply message is sent.










Counter ID: M563C66 Network element name: ICPS_REFLECT

Version: 4.1 NetAct name: ICPS_REFLECT

Description: ICMP message reflects. The number of ICMP message responses generated.

Updated: When an ICMPv4 response message is generated.










Counter ID: M563C67 Network element name: TCPS_SNDTOTAL

Version: 4.1 NetAct name: TCPS_SNDTOTAL

Description: Total TCP segments sent. The total number of sent TCP segments.

Updated: When a TCP segment is sent.



428 DN04143903











Counter ID: M563C68 Network element name: TCPS_SNDPACK

Version: 4.1 NetAct name: TCPS_SNDPACK

Description: TCP data segments sent. The number of TCP segments sent (data length > 0).

Updated: When a TCP segment whose length is more than zero is sent.










Counter ID: M563C69 Network element name: TCPS_SNDBYTE

Version: 4.2 NetAct name: TCPS_SNDBYTE

Description: Sent TCP data bytes.

Updated: When a TCP segment is sent, this counter will tell how many bytes have been sent, not includ-ing the TCP header part.


Unit: byte Range: Example values: 13








DN04143903 429



Counter ID: M563C70 Network element name: TCPS_SNDREXMITPACK

Version: 4.1 NetAct name: TCPS_SNDREXMITPACK

Description: Retransmitted TCP segments. The number of retransmitted TCP data segments sent.

Updated: When a retransmitted TCP segment is sent.










Counter ID: M563C71 Network element name: TCPS_SNDREXMITBYTE

Version: 4.2 NetAct name: TCPS_SNDREXMITBYTE

Description: Retransmitted TCP data bytes. The number of retransmitted TCP data bytes sent.

Updated: When a TCP retransmitted segment is sent, this counter will be updated to tell how many bytes have been sent, not including the TCP header part.










Counter ID: M563C72 Network element name: TCPS_SNDACKS

Version: 4.1 NetAct name: TCPS_SNDACKS

Description: Sent ACK-only TCP segments. The number of sent ACK-only (acknowledgement-only) TCP segments (data length = 0).

Updated: When a TCP ACK segment is sent.


430 DN04143903












Counter ID: M563C73 Network element name: TCPS_DELACK

Version: 4.1 NetAct name: TCPS_DELACK

Description: Delayed ack-only TCP segments. The number of sent delayed ACK-only (acknowledge-ment-only) TCP segments.

Updated: When a delayed TCP ack segment is sent.










Counter ID: M563C74 Network element name: TCPS_SNDURG

Version: 4.1 NetAct name: TCPS_SNDURG

Description: URG only TCP segments. The number of TCP segments sent with Urgent Pointer (URG) only (data length = 0).

Updated: When a TCP segment with urgent pointer only (data length = 0) is sent.









DN04143903 431




Counter ID: M563C75 Network element name: TCPS_SNDPROBE

Version: 4.1 NetAct name: TCPS_SNDPROBE

Description: TCP Window probes. The number of sent window probes. 1 byte of data forced by the persist timer.

Updated: When a TCP window probes segment is sent with 1 byte of data forced by the persist timer.










Counter ID: M563C76 Network element name: TCPS_SNDWINUP

Version: 4.1 NetAct name: TCPS_SNDWINUP

Description: Window update TCP segments. The number of sent window update-only TCP segments (data length = 0).

Updated: When a TCP window-updated segment (data length = 0) is sent.










Counter ID: M563C77 Network element name: TCPS_SNDCTRL

Version: 4.1 NetAct name: TCPS_SNDCTRL

Description: Control TCP segments. The number of sent control (SYN, FIN, RST) TCP segments (data length = 0).

432 DN04143903




Updated: When a TCP control segment is sent (SYN, FIN, or RST).










Counter ID: M563C78 Network element name: TCPS_RCVTOTAL

Version: 4.1 NetAct name: TCPS_RCVTOTAL

Description: The total number of received TCP segments.

Updated: When a TCP segment is received.










Counter ID: M563C79 Network element name: TCPS_RCVACKPACK

Version: 4.1 NetAct name: TCPS_RCVACKPACK

Description: Received ACK (acknowledgement) TCP segments.

Updated: When a TCP ACK segment is received.








DN04143903 433





Counter ID: M563C80 Network element name: TCPS_RCVACKBYTE

Version: 4.2 NetAct name: TCPS_RCVACKBYTE

Description: Received ACK TCP bytes. The number of received bytes acknowledged by received ACK (acknowledgement) TCP packets.

Updated: When a TCP ACK segment is received, this counter will be updated to tell how many bytes have been received, not including the TCP header.










Counter ID: M563C81 Network element name: TCPS_RCVDUPACK

Version: 4.1 NetAct name: TCPS_RCVDUPACK

Description: Duplicated ACK TCP segments. The number of duplicated ACK (acknowledgement) segments received.

Updated: When a duplicated TCP ACK segment is received.










Counter ID: M563C82 Network element name: TCPS_RCVACKTOOMUCH

Version: 4.1 NetAct name: TCPS_RCVACKTOOMUCH

434 DN04143903




Description: Too many ACKs. The number of received ACKs (acknowledgements) for unsent TCP data.

Updated: When a TCP ACK segment is received for an unsent TCP segment (errored ACK).










Counter ID: M563C83 Network element name: TCPS_RCVPACK

Version: 4.1 NetAct name: TCPS_RCVPACK

Description: Received in-sequence TCP segments. The number of received segments in-sequence.

Updated: When TCP segments are received in-sequence (window sizing more than 1).










Counter ID: M563C84 Network element name: TCPS_RCVBYTE

Version: 4.2 NetAct name: TCPS_RCVBYTE

Description: Received in-sequence TCP bytes. The number of bytes received in sequence.

Updated: When a TCP segment s received in sequence, this counter will be updated to tell how many bytes have been received, not including TCP header part.







DN04143903 435






Counter ID: M563C85 Network element name: TCPS_RCVDUPPACK

Version: 4.1 NetAct name: TCPS_RCVDUPPACK

Description: Duplicate TCP segments. The number of completely duplicated segments received.

Updated: When a duplicated TCP segment is received.










Counter ID: M563C86 Network element name: TCPS_RCVDUPBYTE

Version: 4.2 NetAct name: TCPS_RCVDUPBYTE

Description: Received duplicate TCP bytes. The number of completely duplicated bytes received.

Updated: When a duplicated TCP segment is received, this counter will be updated to tell how many bytes have been received, not including the TCP header part.










Counter ID: M563C87 Network element name: TCPS_PAWSDROP

Version: 4.1 NetAct name: TCPS_PAWSDROP

436 DN04143903




Description: TCP segments dropped because of PAWs. The number of TCP segments dropped because of PAWs (protection against wrapped sequence numbers).

Updated: When a TCP segment is dropped because of PAWs (protection against wrapped sequence numbers).










Counter ID: M563C88 Network element name: TCPS_RCVPARTDUPPACK

Version: 4.1 NetAct name: TCPS_RCVPARTDUPPACK

Description: Received TCP segments with duplicated data.

Updated: When a TCP segment is received with some IP datagrams (not all, counter TCP_RCVDUPPACK is for all) duplicated, this counter will be updated.










Counter ID: M563C89 Network element name: TCPS_RCVPARTDUPBYTE

Version: 4.2 NetAct name: TCPS_RCVPARTDUPBYTE

Description: Received TCP bytes with partially duplicated data. The number of duplicate bytes in part-duplicate segments.

Updated: When a TCP segment is received with some IP datagrams (not all, counter TCP_RCVDUPPACK is for all) duplicated, this counter will be updated to tell how many bytes have been received.



DN04143903 437










Counter ID: M563C90 Network element name: TCPS_RCVOOPACK

Version: 4.1 NetAct name: TCPS_RCVOOPACK

Description: Received out-of-order TCP segments.

Updated: When a TCP segment with an out-of-order sequence is received.










Counter ID: M563C91 Network element name: TCPS_RCVOOBYTE

Version: 4.2 NetAct name: TCPS_RCVOOBYTE

Description: Received out-of-order TCP bytes.

Updated: When a TCP segment is received with an out-of-order sequence, this counter will be updated to tell how many bytes have been received, not including the TCP header part.










438 DN04143903




Counter ID: M563C92 Network element name: TCPS_RCVPACKAFTERWIN

Version: 4.1 NetAct name: TCPS_RCVPACKAFTERWIN

Description: Received TCP segments of data after window. The number of received segments with data beyond the advertised window.

Updated: When a TCP segment which is already over the size of the setting window is received.










Counter ID: M563C93 Network element name: TCPS_RCVBYTEAFTERWIN

Version: 4.2 NetAct name: TCPS_RCVBYTEAFTERWIN

Description: Received TCP bytes of data after window. The number of received bytes beyond the adver-tised window.

Updated: When a TCP segment is received which is already over the setting window's size, this counter will be updated to tell how many bytes have been received, not including the TCP header part.










Counter ID: M563C94 Network element name: TCPS_RCVWINPROBE

Version: 4.1 NetAct name: TCPS_RCVWINPROBE

Description: Received TCP window probes. The number of window probe segments received.

Updated: When a TCP window probe segment is received.


DN04143903 439











Counter ID: M563C95 Network element name: TCPS_RCVWINUPD

Version: 4.1 NetAct name: TCPS_RCVWINUPD

Description: Received window update TCP segments.

Updated: When a TCP window-updated segment is received.










Counter ID: M563C96 Network element name: TCPS_RCVAFTERCLOSE

Version: 4.1 NetAct name: TCPS_RCVAFTERCLOSE

Description: TCP segments received after close. The number of segments received after the connection is closed.

Updated: When a TCP segment is received after the connection is closed.










440 DN04143903




Counter ID: M563C97 Network element name: TCPS_RCVBADSUM

Version: 4.1 NetAct name: TCPS_RCVBADSUM

Description: Received TCP segments with bad checksum. Received TCP segments discarded with checksum errors.

Updated: When a TCP segment is received with bad checksum.










Counter ID: M563C98 Network element name: TCPS_RCVBADOFF

Version: 4.1 NetAct name: TCPS_RCVBADOFF

Description: Received bad header offset TCP segments. Received TCP segments discarded because of invalid header offset fields or header length.

Updated: When a TCP segment received, and its header offset or header length is invalid.










Counter ID: M563C99 Network element name: TCPS_RCVSHORT

Version: 4.1 NetAct name: TCPS_RCVSHORT

Description: Received too short TCP segments. Received TCP segments discarded because of the TCP segment is too short.

Updated: When a received TCP segment received is too short (shorter than the header part).


DN04143903 441











Counter ID: M563C100 Network element name: TCPS_CONNATTEMPT

Version: 4.1 NetAct name: TCPS_CONNATTEMPT

Description: The number of sent TCP connection requests.

Updated: When the host sends a TCP connection request to initiate TCP connection.










Counter ID: M563C101 Network element name: TCPS_ACCEPTS

Version: 4.1 NetAct name: TCPS_ACCEPTS

Description: TCP connection accepts. The number of synchronize sequence numbers (SYN) received in LISTEN state.

Updated: When a TCP connection is accepted.










442 DN04143903




Counter ID: M563C102 Network element name: TCPS_CONNECTS

Version: 4.1 NetAct name: TCPS_CONNECTS

Description: TCP connection established. The number of TCP connections that have been established (actively or passively), including accepted connections (TCPS_ACCEPTS M563C101).

Updated: When a TCP connection has been established (actively or passively).










Counter ID: M563C103 Network element name: TCPS_CLOSED

Version: 4.1 NetAct name: TCPS_CLOSED

Description: Closed TCP connections. The number of closed connections. Includes the number of dropped connections TCPS_DROPS M563C104.

Updated: When a TCP connection is closed (including those that are dropped, M563C104).










Counter ID: M563C104 Network element name: TCPS_DROPS

Version: 4.1 NetAct name: TCPS_DROPS

Description: Dropped TCP connections. The number of dropped TCP connections after synchronize sequence number (SYN) is received.

Updated: When a TCP connection is dropped after synchronize sequence number (SYN) is received.


DN04143903 443











Counter ID: M563C105 Network element name: TCPS_CONNDROPS

Version: 4.1 NetAct name: TCPS_CONNDROPS

Description: Dropped embryonic TCP connections. The number of TCP connections that have been dropped before synchronize sequence number (SYN) is received.

Updated: When a TCP connection is dropped before synchronize sequence number (SYN) is received.










Counter ID: M563C106 Network element name: TCPS_RTTUPDATED

Version: 4.1 NetAct name: TCPS_RTTUPDATED

Description: RTT updates. The number of times when Round trip time (RTT) estimators are updated.

Updated: When an RTT (Round trip time) estimator is updated.










444 DN04143903




Counter ID: M563C107 Network element name: TCPS_SEGSTIMED

Version: 4.1 NetAct name: TCPS_SEGSTIMED

Description: Segments measure RTT. The number of segments for which TCP tried to measure Round trip time (RTT).

Updated: When a TCP segment trying to measure RTT (Round trip time) is received.










Counter ID: M563C108 Network element name: TCPS_REXMTTIMEO

Version: 4.1 NetAct name: TCPS_REXMTTIMEO

Description: Retransmit timeouts.

Updated: When a retransmission is timed out.










Counter ID: M563C109 Network element name: TCPS_TIMEOUTDROP

Version: 4.1 NetAct name: TCPS_TIMEOUTDROP

Description: Timeout drops. The number of TCP connections dropped in retransmission timeout.

Updated: When a TCP connection is dropped because of retransmission timeout.



DN04143903 445










Counter ID: M563C110 Network element name: TCPS_PERSISTTIMEO

Version: 4.1 NetAct name: TCPS_PERSISTTIMEO

Description: Persist timeouts. The number of times that the persist timer expires.

Updated: When a TCP's persist timer expires.










Counter ID: M563C111 Network element name: TCPS_KEEPTIMEO

Version: 4.1 NetAct name: TCPS_KEEPTIMEO

Description: Keep timeout. The number of times when the keep-alive timer or connection-establishment timer expires.

Updated: When a TCP's keep-alive timer or connection-establishment timer expires.










446 DN04143903




Counter ID: M563C112 Network element name: TCPS_KEEPPROBE

Version: 4.1 NetAct name: TCPS_KEEPPROBE

Description: Keep-alive probes sent.

Updated: When TCP keep-alive probes segment is sent, this counter will be updated.










Counter ID: M563C113 Network element name: TCPS_KEEPDROPS

Version: 4.1 NetAct name: TCPS_KEEPDROPS

Description: Dropped in keep-alive. The number of TCP connections dropped by the keep-alive timer, when the connection is in established or awaiting synchronize sequence numbers (SYN) state.

Updated: If the TCP connection is in established or synchronize sequence numbers (SYN) waiting state when the keep-alive timer expires, the connection is dropped and this counter is updated.










Counter ID: M563C114 Network element name: TCPS_PREDACK

Version: 4.1 NetAct name: TCPS_PREDACK

Description: Prediction correct for ACKs. The number of times when the TCP segment header prediction is correct for ACKs (acknowledgements).

Updated: When a TCP segment header prediction is correct for ACKs.


DN04143903 447











Counter ID: M563C115 Network element name: TCPS_PREDDAT

Version: 4.1 NetAct name: TCPS_PREDDAT

Description: Prediction correct for TCP data packets. The number of times when the TCP segment header prediction is correct for the TCP data segments.

Updated: When a TCP segment header prediction is correct for the TCP data segments.










Counter ID: M563C116 Network element name: TCPS_PCBHASHMISS

Version: 4.1 NetAct name: TCPS_PCBHASHMISS

Description: PCB hash miss. The number of times when the protocol control block (PCB) cache compar-ison fails.

Updated: When PCB (protocol control block) cache comparison fails.









448 DN04143903





Counter ID: M563C117 Network element name: TCPS_NOPORT

Version: 4.1 NetAct name: TCPS_NOPORT

Description: Dropped TCP packets. The number of discarded TCP segments that are dropped because no socket is available.

Updated: When a TCP segment is dropped because no socket is available.










Counter ID: M563C118 Network element name: TCPS_BADSYN

Version: 4.1 NetAct name: TCPS_BADSYN

Description: Bad TCP connection attempts. Received acknowledgements for which this entity has no synchronize sequence numbers (SYN) in compressed state.

Updated: When a received TCP connection attempts an acknowledgement, but this entity has no syn-chronize sequence numbers (SYN) in compressed state (no connection has been attempted), this counter will be updated.










Counter ID: M563C119 Network element name: TCPS_SC_ADDED

Version: 4.1 NetAct name: TCPS_SC_ADDED

DN04143903 449



Description: TCP segment SYN cache entries added.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache entry is added.










Counter ID: M563C120 Network element name: TCPS_SC_COLLISIONS

Version: 4.1 NetAct name: TCPS_SC_COLLISIONS

Description: TCP segment SYN cache hash collisions.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache has collided.










Counter ID: M563C121 Network element name: TCPS_SC_COMPLETED

Version: 4.1 NetAct name: TCPS_SC_COMPLETED

Description: TCP segment SYN cache completed.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache is completed.







450 DN04143903







Counter ID: M563C122 Network element name: TCPS_SC_ABORTED

Version: 4.1 NetAct name: TCPS_SC_ABORTED

Description: TCP segment SYN cache aborted. The number of TCP segment synchronize sequence numbers (SYN) caches aborted because of no space to build the protocol control block (PCB).

Updated: When a TCP segment synchronize sequence numbers (SYN) cache is aborted.










Counter ID: M563C123 Network element name: TCPS_SC_TIMED_OUT

Version: 4.1 NetAct name: TCPS_SC_TIMED_OUT

Description: TCP segment SYN cache timed out.

Updated: When Ta CP segment synchronize sequence numbers (SYN) cache is timed out.










Counter ID: M563C124 Network element name: TCPS_SC_OVERFLOWED

Version: 4.1 NetAct name: TCPS_SC_OVERFLOWED

DN04143903 451



Description: TCP segment SYN caches dropped because of overflow.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache is dropped because of overflow.










Counter ID: M563C125 Network element name: TCPS_SC_BUCKETOVERFLOW

Version: 4.1 NetAct name: TCPS_SC_BUCKETOVERFLOW

Description: TCP segment SYN cache dropped because of bucket overflow.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache is dropped because of bucket overflow.










Counter ID: M563C126 Network element name: TCPS_SC_RESET

Version: 4.1 NetAct name: TCPS_SC_RESET

Description: TCP segment SYN caches dropped because of RST.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache is dropped because of RST (Reset).





452 DN04143903









Counter ID: M563C127 Network element name: TCPS_SC_UNREACH

Version: 4.1 NetAct name: TCPS_SC_UNREACH

Description: TCP segment SYN cache dropped because ICMP is unreachable.

Updated: When a TCP segment synchronize sequence numbers (SYN) cache is dropped because ICMP is unreachable.










Counter ID: M563C128 Network element name: TCPS_SC_DUPESYN

Version: 4.1 NetAct name: TCPS_SC_DUPESYN

Description: Duplicate TCP segment SYNs received for entries already in the cache.

Updated: When a duplicated TCP synchronize sequence numbers (SYN) packet is received for entries already in the cache.










DN04143903 453



Counter ID: M563C129 Network element name: TCPS_SC_DROPPED

Version: 4.1 NetAct name: TCPS_SC_DROPPED

Description: TCP segment SYNs dropped because of no route or no space.

Updated: When a TCP segment synchronize sequence numbers (SYNs) is dropped because of no route or no space.










Counter ID: M563C130 Network element name: TCPS_SC_RETRANSMITTED

Version: 4.1 NetAct name: TCPS_SC_RETRANSMITTED

Description: TCP segment SYNs and ACKs (acknowledgements) retransmitted.

Updated: When TCP segment synchronize sequence numbers (SYNs) and ACKs are retransmitted.










Counter ID: M563C131 Network element name: UDPS_IPACKETS

Version: 4.1 NetAct name: UDPS_IPACKETS

Description: Received UDP datagrams. The total number of received UDP datagrams delivered to UDP users.

Updated: When a UDPv4 datagram is received, including errored datagrams.



454 DN04143903











Counter ID: M563C132 Network element name: UDPS_HDROPS

Version: 4.1 NetAct name: UDPS_HDROPS

Description: Incomplete UDP datagram header. The number of received UDP datagrams not delivered because the datagram is shorter than the header.

Updated: When a UDPv4 datagram which is shorter than the header is received.










Counter ID: M563C133 Network element name: UDPS_BADLEN

Version: 4.1 NetAct name: UDPS_BADLEN

Description: The number of received UPD datagrams not delivered to upper layers because the data is longer than the datagram itself.

Updated: When a UDPv4 datagram is received and the length in UDP header is bigger than the length in IP header.









DN04143903 455




Counter ID: M563C134 Network element name: UDPS_BADSUM

Version: 4.1 NetAct name: UDPS_BADSUM

Description: Bad checksum of the UDP datagram. The number of received UPD datagrams not delivered because of checksum errors.

Updated: When a UDPv4 datagram with bad checksum is received.










Counter ID: M563C135 Network element name: UDPS_NOPORT

Version: 4.1 NetAct name: UDPS_NOPORT

Description: Received UDP datagrams with no port. The number of received UDP datagrams with no process on the destination port.

Updated: When a UDPv4 datagram is received, but there is no process bundled to the port in the UDP header.










Counter ID: M563C136 Network element name: UDPS_NOPORTBCAST

Version: 4.1 NetAct name: UDPS_NOPORTBCAST

456 DN04143903




Description: Broadcast/multicast UPD datagrams with no port. The number of received broadcast/multi-cast UPD datagrams with no process on the destination port.

Updated: When a broadcast/multicast UDP datagram is received, but there is no process bundled to the port in the UDP header.










Counter ID: M563C137 Network element name: UDPS_FULLSOCK

Version: 4.1 NetAct name: UDPS_FULLSOCK

Description: UDP packets dropped because of full socket buffers. The number of received UDP data-grams not delivered because input socket buffers are full.

Updated: When a UDPv4 datagram is dropped because input socket buffers are full.










Counter ID: M563C138 Network element name: UDPS_PCBHASHMISS

Version: 4.1 NetAct name: UDPS_PCBHASHMISS

Description: UDP datagram PCB hash misses. The number of UPD datagrams with Process Control Block (PCB) hash misses.

Updated: When a UDPv4 datagram with a missed PCB (Process Control Block) is received.





DN04143903 457








Counter ID: M563C139 Network element name: UDPS_OPACKETS

Version: 4.1 NetAct name: UDPS_OPACKETS

Description: UDP datagrams output. The total number of UDP datagrams sent.

Updated: When a UDP datagram is sent.










Counter ID: M563C140 Network element name: IP6S_TOTAL

Version: 4.1 NetAct name: IP6S_TOTAL

Description: IPv6 datagrams received. The total number of input datagrams received by the interface, including those received in error.

Updated: When an IPv6 datagram is received, including the ones that are received in error.










458 DN04143903




Counter ID: M563C141 Network element name: IP6S_TOOSHORT

Version: 4.1 NetAct name: IP6S_TOOSHORT

Description: Too short IPv6 datagrams. The number of discarded IPv6 datagrams with invalid data length.

Updated: When an IPv6 datagram is received, but the received data length does not equal the length value in the IP header.










Counter ID: M563C142 Network element name: IP6S_TOOSMALL

Version: 4.1 NetAct name: IP6S_TOOSMALL

Description: Too small IPv6 datagrams. The number of discarded IPv6 datagrams that are too small to contain an IP packet.

Updated: When an IPv6 datagram is received, but its length is too short to contain the IP header part.










Counter ID: M563C143 Network element name: IP6S_BADOPTIONS

Version: 4.1 NetAct name: IP6S_BADOPTIONS

Description: Incoming IPv6 datagrams with option errors. The number of input IPv6 datagrams discarded because of errors discovered when processing their IPv6 options.

Updated: When an error is found in a received IPv6 datagram when processing its options.


DN04143903 459











Counter ID: M563C144 Network element name: IP6S_BADVERS

Version: 4.1 NetAct name: IP6S_BADVERS

Description: Incoming IPv6 datagrams with version errors. The number of input datagrams discarded because of version number mismatch in their IPv6 headers.

Updated: When an IPv6 datagram with errored version number is received.










Counter ID: M563C145 Network element name: IP6S_FRAGMENTS

Version: 4.1 NetAct name: IP6S_FRAGMENTS

Description: Received IPv6 fragments.

Updated: When an IPv6 fragment is received.










460 DN04143903




Counter ID: M563C146 Network element name: IP6S_FRAGDROPPED

Version: 4.1 NetAct name: IP6S_FRAGDROPPED

Description: IPv6 fragments dropped. The number of discarded IP fragments because of duplicates or insufficient space.

Updated: When IPv6 fragments are dropped because of duplication or insufficient space.










Counter ID: M563C147 Network element name: IP6S_FRAGTIMEOUT

Version: 4.1 NetAct name: IP6S_FRAGTIMEOUT

Description: IPv6 fragments timed out. The number of IPv6 fragments dropped after time-out.

Updated: When an IPv6 fragment is dropped because of time-out.










Counter ID: M563C148 Network element name: IP6S_FRAGOVERFLOW

Version: 4.1 NetAct name: IP6S_FRAGOVERFLOW

Description: Overflowed IPv6 fragments. IPv6 fragments that exceeded the limit.

Updated: When an IPv6 fragment exceeds the limit.



DN04143903 461










Counter ID: M563C149 Network element name: IP6S_REASSEMBLED

Version: 4.1 NetAct name: IP6S_REASSEMBLED

Description: IPv6 datagrams reassembled ok. The number of IPv6 datagrams successfully reassembled.

Updated: When an IPv6 fragment has been successfully reassembled.










Counter ID: M563C150 Network element name: IP6S_DELIVERED

Version: 4.1 NetAct name: IP6S_DELIVERED

Description: Incoming IPv6 datagrams delivered. The total number of datagrams successfully delivered to IPv6 user protocols (including ICMP). This counter is incremented at the interface to which these data-grams were addressed, which might not necessarily be the input interface for some of the datagrams.

Updated: When an incoming IPv6 datagram has been successfully delivered to upper level.










462 DN04143903




Counter ID: M563C151 Network element name: IP6S_FORWARD

Version: 4.1 NetAct name: IP6S_FORWARD

Description: Outgoing IPv6 datagram forwarded. The number of output datagrams which this entity received and forwarded to their final destinations. In entities which do not act as IPv6 routers, this counter will include only those packets which were Source-Routed via this entity, and the Source-Route process-ing was successful.

Updated: When forwarding IPv6 datagram to their destination, this counter will be updated. In entities which do not act as IPv6 routers, this counter will be updated only for those datagrams which were Source-Routed via this entity, and the Source-Route processing was successful.










Counter ID: M563C152 Network element name: IP6S_CANTFORWARD

Version: 4.1 NetAct name: IP6S_CANTFORWARD

Description: Received IPv6 datagrams not forwardable. The number of input datagrams discarded because the IP address in their IPv6 header destination field was not a valid address to be forwarded to.

Updated: When a received IPv6 datagram is not addressed to this entity, but its destination address is invalid, the forwarding function is forbidden or the interface is not up, this counter will be updated.










Counter ID: M563C153 Network element name: IP6S_REDIRECTSEND

Version: 4.1 NetAct name: IP6S_REDIRECTSEND

DN04143903 463



Description: IPv6 redirects sent. The number of redirect datagrams sent.

Updated: When a redirect IPv6 datagram is sent.










Counter ID: M563C154 Network element name: IP6S_LOCALOUT

Version: 4.1 NetAct name: IP6S_LOCALOUT

Description: IPv6 datagrams sent from this host. The total number of IPv6 datagrams generated in the system, not forwarded.

Updated: When an IPv6 datagram is generated at this entity and sent out.










Counter ID: M563C155 Network element name: IP6S_RAWOUT

Version: 4.1 NetAct name: IP6S_RAWOUT

Description: Raw IPv6 datagrams. The total number of IPv6 datagrams generated. The number of data-grams sent with the fabricated IPv6 header.

Updated: When an IPv6 datagram is generated with the fabricated IPv6 header.






464 DN04143903








Counter ID: M563C156 Network element name: IP6S_ODROPPED

Version: 4.1 NetAct name: IP6S_ODROPPED

Description: Discarded outgoing IPv6 datagrams. The number of output IPv6 datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded, for example, because of insufficient buffer space.

Updated: When an outgoing IPv6 datagram is discarded although there is no problem to prevent its trans-mission to its destination, but it is discarded, for example, because of insufficient buffer space.










Counter ID: M563C157 Network element name: IP6S_NOROUTE

Version: 4.1 NetAct name: IP6S_NOROUTE

Description: Incoming IPv6 datagrams with no route. The number of input datagrams discarded because no route could be found to transmit them to their destination.

Updated: When an outgoing IPv6 datagram is discarded because there is no route available.










DN04143903 465



Counter ID: M563C158 Network element name: IP6S_FRAGMENTED

Version: 4.1 NetAct name: IP6S_FRAGMENTED

Description: Outgoing IPv6 datagrams fragmented. The number of outgoing IPv6 datagrams that have been successfully fragmented at this entity.

Updated: When an outgoing IPv6 datagram is successfully fragmented at this entity.










Counter ID: M563C159 Network element name: IP6S_OFRAGMENTS

Version: 4.1 NetAct name: IP6S_OFRAGMENTS

Description: Outgoing IPv6 datagram fragments created. The number of outgoing IPv6 datagram frag-ments that have been generated as a result of fragmentation at this entity.

Updated: When an outgoing IPv6 datagram fragment is generated.










Counter ID: M563C160 Network element name: IP6S_CANTFRAG

Version: 4.1 NetAct name: IP6S_CANTFRAG

Description: IPv6 datagram fragment failed. The number of IPv6 datagrams that have been discarded because they needed to be fragmented at this entity but the fragmenting failed.

Updated: When an outgoing IPv6 datagram needs to be fragmented at this entity, but the fragmenting failed (MF at setting 1), this counter is updated.


466 DN04143903












Counter ID: M563C161 Network element name: IP6S_BADSCOPE

Version: 4.1 NetAct name: IP6S_BADSCOPE

Description: The number of IPv6 datagrams that violated scope rules.

Updated: When an IPv6 datagram violates scope rules.










Counter ID: M563C162 Network element name: IP6S_NOTMEMBER

Version: 4.1 NetAct name: IP6S_NOTMEMBER

Description: Multicast IPv6 datagrams which do not join.

Updated: When a IPv6 multicast datagram is received, but this entity does not join the multicast group.










DN04143903 467



Counter ID: M563C163 Network element name: IP6S_M1

Version: 4.1 NetAct name: IP6S_M1

Description: The usage of one memory buffer. The number of times that one memory buffer has been used by the networking protocols.

Updated: When one memory buffer has been used by the IPv6 protocol.










Counter ID: M563C164 Network element name: IP6S_M2M

Version: 4.1 NetAct name: IP6S_M2M

Description: The usage of two or more memory buffers. The number of times that two or more memory buffers have been used by the networking protocols.

Updated: When two or more memory buffers have been used by the IPv6 protocol.










Counter ID: M563C165 Network element name: IP6S_MEXT1

Version: 4.1 NetAct name: IP6S_MEXT1

Description: The usage of one external memory buffer. The number of times that one external memory buffer has been used by the networking protocols.

Updated: When one external memory buffer has been used by the IPv6 protocol.


468 DN04143903












Counter ID: M563C166 Network element name: IP6S_MEXT2M

Version: 4.1 NetAct name: IP6S_MEXT2M

Description: The usage of two or more external memory buffers. The number of times that two or more external memory buffers have been used by the networking protocols.

Updated: When two or more external memory buffers have been used by the IPv6 networking protocol.










Counter ID: M563C167 Network element name: IP6S_EXTHDRTOOLONG

Version: 4.1 NetAct name: IP6S_EXTHDRTOOLONG

Description: IPv6 datagrams whose headers are not continuous.

Updated: When an IPv6 datagram whose headers are not continuous is received.










DN04143903 469



Counter ID: M563C168 Network element name: IP6S_NOGIF

Version: 4.1 NetAct name: IP6S_NOGIF

Description: The number of tunneling IPv6 datagrams that cannot find gif.

Updated: Since tunneling is not supported, this counter is not updated.










Counter ID: M563C169 Network element name: IP6S_TOOMANYHDR

Version: 4.1 NetAct name: IP6S_TOOMANYHDR

Description: IPv6 datagrams discarded because of too many headers.

Updated: When an IPv6 datagram is discarded because of too many headers.










Counter ID: M563C170 Network element name: ICP6S_ERROR

Version: 4.1 NetAct name: ICP6S_ERROR

Description: The number of sent ICMPv6 error messages.

Updated: When an ICMPv6 error message is sent out.




470 DN04143903










Counter ID: M563C171 Network element name: ICP6S_CANTERROR

Version: 4.1 NetAct name: ICP6S_CANTERROR

Description: The number of sent ICMPv6 error message with ICMP type lower than 128 or for redirection

Updated: When an ICMPv6 error message is sent with the ICMP type value being lower than 128 or the ICMPv6 error message being used for redirection, this counter will be incremented and the ICMPv6 error message will be ignored consequently.










Counter ID: M563C172 Network element name: ICP6S_TOOFREQ

Version: 4.1 NetAct name: ICP6S_TOOFREQ

Description: Errors not generated because of rate limitation. The number of times when errors were not generated because of rate limitation.

Updated: When an ICMPv6 error is not generated because of rate limitation.










DN04143903 471



Counter ID: M563C173 Network element name: ICP6S_OUTDSTUNREACH

Version: 4.1 NetAct name: ICP6S_OUTDSTUNREACH

Description: Sent ICMPv6 Destination Unreachable messages. The number of ICMP Destination Unreachable messages sent.

Updated: When an ICMPv6 destination unreachable message is sent.










Counter ID: M563C174 Network element name: ICP6S_OUTPKTTOOBIG

Version: 4.1 NetAct name: ICP6S_OUTPKTTOOBIG

Description: Sent ICMPv6 Too Big messages. The number of ICMP Too Big messages sent.

Updated: When an ICMPv6 message that is too large is sent.










Counter ID: M563C175 Network element name: ICP6S_OUTTIMEEXCEED

Version: 4.1 NetAct name: ICP6S_OUTTIMEEXCEED

Description: Sent ICMPv6 Time Exceeded messages. The number of ICMP Time Exceeded messages sent.

Updated: When an ICMPv6 time exceeded message is sent.


472 DN04143903












Counter ID: M563C176 Network element name: ICP6S_OUTPARAMPROB

Version: 4.1 NetAct name: ICP6S_OUTPARAMPROB

Description: Sent ICMPv6 Parameter Problem messages. The number of ICMP Parameter Problem messages sent.

Updated: When an ICMPv6 parameter problem message is sent.










Counter ID: M563C177 Network element name: ICP6S_OUTECHO

Version: 4.1 NetAct name: ICP6S_OUTECHO

Description: Sent ICMPv6 Echo Request messages. The number of ICMP Echo Request messages sent.

Updated: When an ICMPv6 echo request message is sent.










DN04143903 473



Counter ID: M563C178 Network element name: ICP6S_OUTECHOREPLY

Version: 4.1 NetAct name: ICP6S_OUTECHOREPLY

Description: Sent ICMPv6 Echo Reply messages. The number of ICMP Echo Reply messages sent.

Updated: When an ICMPv6 echo reply message is sent.










Counter ID: M563C179 Network element name: ICP6S_OUTMLDQUERY

Version: 4.1 NetAct name: ICP6S_OUTMLDQUERY

Description: Sent ICMPv6 Multicast Listener Query messages. The number of ICMP Multicast Listener Query messages sent.

Updated: When an ICMPv6 multicast listener query message is sent.










Counter ID: M563C180 Network element name: ICP6S_OUTMLDREPORT

Version: 4.1 NetAct name: ICP6S_OUTMLDREPORT

Description: Sent ICMPv6 Multicast Listener Report messages. The number of ICMP Multicast Listener Report messages sent.

Updated: When an ICMPv6 multicast listener report message is sent.


474 DN04143903












Counter ID: M563C181 Network element name: ICP6S_OUTMLDDONE

Version: 4.1 NetAct name: ICP6S_OUTMLDDONE

Description: Sent ICMPv6 Multicast Listener Done messages. The number of ICMP Multicast Listener Done messages sent.

Updated: When an ICMPv6 multicast listener done message is sent.










Counter ID: M563C182 Network element name: ICP6S_OUTROUTERSOLICIT

Version: 4.1 NetAct name: ICP6S_OUTROUTERSOLICIT

Description: Sent ICMPv6 Router Solicitation messages. The number of ICMP Router Solicitation messages sent.

Updated: When an ICMPv6 router solicitation message is sent.









DN04143903 475




Counter ID: M563C183 Network element name: ICP6S_OUTROUTERADVERT

Version: 4.1 NetAct name: ICP6S_OUTROUTERADVERT

Description: Sent ICMPv6 Router Advertisement messages. The number of ICMP Router Advertisement messages sent.

Updated: When an ICMPv6 router advertisement message is sent.










Counter ID: M563C184 Network element name: ICP6S_OUTNEIGHBORSOLICIT

Version: 4.1 NetAct name: ICP6S_OUTNEIGHBORSOLICIT

Description: Sent ICMPv6 Neighbor Solicitation messages. The number of ICMP Neighbor Solicitation messages sent.

Updated: When an ICMPv6 neighbor solicitation message is sent.










Counter ID: M563C185 Network element name: ICP6S_OUTNEIGHBORADVERT

Version: 4.1 NetAct name: ICP6S_OUTNEIGHBORADVERT

Description: Sent ICMPv6 Neighbor Advertisement messages. The number of ICMP Neighbor Advertise-ment messages sent.

476 DN04143903




Updated: When an ICMPv6 neighbor advertisement message is sent.










Counter ID: M563C186 Network element name: ICP6S_OUTREDIRECT

Version: 4.1 NetAct name: ICP6S_OUTREDIRECT

Description: Sent ICMPv6 Redirect messages. The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirect messages.

Updated: When an ICMPv6 redirect message is sent. Note that only a router can send this kind of an ICMP message.










Counter ID: M563C187 Network element name: ICP6S_OUTROUTERRENUMBER

Version: 4.1 NetAct name: ICP6S_OUTROUTERRENUMBER

Description: Sent ICMPv6 Router Renumbering messages. The number of ICMP Router Renumbering messages sent.

Updated: When an ICMPv6 router renumber message is sent.






DN04143903 477







Counter ID: M563C188 Network element name: ICP6S_OUTNIQUERY

Version: 4.1 NetAct name: ICP6S_OUTNIQUERY

Description: Sent ICMPv6 Node Information Query messages. The number of ICMP Node Information Query messages sent.

Updated: When an ICMPv6 node information query message is sent.










Counter ID: M563C189 Network element name: ICP6S_OUTNIREPLY

Version: 4.1 NetAct name: ICP6S_OUTNIREPLY

Description: Sent ICMPv6 Node Information Reply messages. The number of ICMP Node Information Reply messages sent.

Updated: When an ICMPv6 node information reply message is sent.










Counter ID: M563C190 Network element name: ICP6S_BADCODE

478 DN04143903




Version: 4.1 NetAct name: ICP6S_BADCODE

Description: ICMPv6 messages with bad code fields. The number of ICMP messages with an invalid code.

Updated: When an ICMPv6 message with bad code fields is found.










Counter ID: M563C191 Network element name: ICP6S_TOOSHORT

Version: 4.1 NetAct name: ICP6S_TOOSHORT

Description: Too short ICMPv6 messages. The number of ICMP messages with the length of the ICMPv6 header shorter than the minimum length.

Updated: When an ICMPv6 message with the length of the header shorter than the minimum length is received.










Counter ID: M563C192 Network element name: ICP6S_CHECKSUM

Version: 4.1 NetAct name: ICP6S_CHECKSUM

Description: ICMPv6 message bad checksum. The number of ICMP messages with an invalid ICMPv6 checksum.

Updated: When an ICMPv6 message with an invalid checksum is received.




DN04143903 479









Counter ID: M563C193 Network element name: ICP6S_BADLEN

Version: 4.1 NetAct name: ICP6S_BADLEN

Description: The number of MLD, WRU, ND or Router Renumbering ICMPv6 messages whose length is too short.

Updated: When the length of the received MLD, WRU, ND or Router Renumbering ICMPv6 message is too short and the message is therefore invalid.










Counter ID: M563C194 Network element name: ICP6S_REFLECT

Version: 4.1 NetAct name: ICP6S_REFLECT

Description: ICMPv6 message reflects. The number of ICMPv6 message responses generated.

Updated: When an ICMPv6 reflect response message is generated.










480 DN04143903




Counter ID: M563C195 Network element name: ICP6S_INDSTUNREACH

Version: 4.1 NetAct name: ICP6S_INDSTUNREACH

Description: Received ICMPv6 Destination Unreachable messages. The number of ICMP Destination Unreachable messages received.

Updated: When an ICMPv6 destination unreachable message is received.










Counter ID: M563C196 Network element name: ICP6S_INPKTTOOBIG

Version: 4.1 NetAct name: ICP6S_INPKTTOOBIG

Description: Received ICMPv6 Too Big messages. The number of ICMP Too Big messages received.

Updated: When an ICMPv6 too big message is received.










Counter ID: M563C197 Network element name: ICP6S_INTIMEEXCEED

Version: 4.1 NetAct name: ICP6S_INTIMEEXCEED

Description: Received ICMPv6 Time Exceeded messages. The number of ICMP Time Exceeded messages received.

Updated: When an ICMPv6 time exceeded message is received.



DN04143903 481










Counter ID: M563C198 Network element name: ICP6S_INPARAMPROB

Version: 4.1 NetAct name: ICP6S_INPARAMPROB

Description: Received ICMPv6 Parameter Problem messages. The number of ICMP Parameter Problem messages received.

Updated: When an ICMPv6 parameter problem message is received.










Counter ID: M563C199 Network element name: ICP6S_INECHO

Version: 4.1 NetAct name: ICP6S_INECHO

Description: Received ICMPv6 Echo Request messages. The number of ICMP Echo Request messages received.

Updated: When an ICMPv6 echo request message is received.










482 DN04143903




Counter ID: M563C200 Network element name: ICP6S_INECHOREPLY

Version: 4.1 NetAct name: ICP6S_INECHOREPLY

Description: Received ICMPv6 Echo Reply messages. The number of ICMP Echo Reply messages received.

Updated: When an ICMPv6 echo reply message is received.










Counter ID: M563C201 Network element name: ICP6S_INMLDQUERY

Version: 4.1 NetAct name: ICP6S_INMLDQUERY

Description: Received ICMPv6 Multicast Listener Query messages. The number of ICMP Multicast Listener Query messages received.

Updated: When an ICMPv6 multicast listener query message is received.










Counter ID: M563C202 Network element name: ICP6S_INMLDREPORT

Version: 4.1 NetAct name: ICP6S_INMLDREPORT

Description: Received ICMPv6 Multicast Listener Report messages. The number of ICMP Multicast Listener Report messages received.

Updated: When an ICMPv6 multicast listener report message is received.


DN04143903 483











Counter ID: M563C203 Network element name: ICP6S_INMLDDONE

Version: 4.1 NetAct name: ICP6S_INMLDDONE

Description: Received ICMPv6 Multicast Listener Done messages. The number of ICMP Multicast Listener Done messages received.

Updated: When an ICMPv6 multicast listener done message is received.










Counter ID: M563C204 Network element name: ICP6S_INROUTERSOLICIT

Version: 4.1 NetAct name: ICP6S_INROUTERSOLICIT

Description: Received ICMPv6 Router Solicitation messages. The number of ICMP Router Solicitation messages received.

Updated: When an ICMPv6 router solicitation message is received.









484 DN04143903





Counter ID: M563C205 Network element name: ICP6S_INROUTERADVERT

Version: 4.1 NetAct name: ICP6S_INROUTERADVERT

Description: Received ICMPv6 Router Advertisement messages. The number of ICMP Router Advertise-ment messages received.

Updated: When an ICMPv6 router advertisement message is received.










Counter ID: M563C206 Network element name: ICP6S_INNEIGHBORSOLICIT

Version: 4.1 NetAct name: ICP6S_INNEIGHBORSOLICIT

Description: Received ICMPv6 Neighbor Solicitation messages. The number of ICMP Neighbor Solicita-tion messages received.

Updated: When an ICMPv6 neighbor solicitation message is received.










Counter ID: M563C207 Network element name: ICP6S_INNEIGHBORADVERT

Version: 4.1 NetAct name: ICP6S_INNEIGHBORADVERT

Description: Received ICMPv6 Neighbor Advertisement messages. The number of ICMP Neighbor Advertisement messages received.

DN04143903 485



Updated: When an ICMPv6 neighbor advertisement message is received.










Counter ID: M563C208 Network element name: ICP6S_INREDIRECT

Version: 4.1 NetAct name: ICP6S_INREDIRECT

Description: Received ICMPv6 Redirect messages. The number of ICMP Redirect messages received.

Updated: When an ICMPv6 redirect message is received.










Counter ID: M563C209 Network element name: ICP6S_INROUTERRENUMBER

Version: 4.1 NetAct name: ICP6S_INROUTERRENUMBER

Description: Received ICMPv6 Router Renumbering messages. The number of ICMPv6 Router Renum-bering messages received.

Updated: When an ICMP router renumbering message is received.








486 DN04143903






Counter ID: M563C210 Network element name: ICP6S_INNIQUERY

Version: 4.1 NetAct name: ICP6S_INNIQUERY

Description: Received ICMPv6 Node Information Query messages. The number of ICMP Node Informa-tion Query messages received.

Updated: When an ICMPv6 node information query message is received.










Counter ID: M563C211 Network element name: ICP6S_INNIREPLY

Version: 4.1 NetAct name: ICP6S_INNIREPLY

Description: Received ICMPv6 Node Information Reply messages. The number of ICMP Node Informa-tion Reply messages received.

Updated: When an ICMPv6 node information reply message is received.










Counter ID: M563C212 Network element name: ICP6S_DSTUNREACHNOROUTE

Version: 4.1 NetAct name: ICP6S_DSTUNREACHNOROUTE

DN04143903 487



Description: The number of ICMPv6 Destination Unreachable messages with the 'no route to destination' (0) code.

Updated: When an ICMPv6 destination unreachable message with the 'no route to destination' (0) code is sent.










Counter ID: M563C213 Network element name: ICP6S_DSTUNREACHADMIN

Version: 4.1 NetAct name: ICP6S_DSTUNREACHADMIN

Description: The number of ICMPv6 Destination Unreachable messages with the 'communication with destination administratively prohibited' (1) code.

Updated: When an ICMPv6 destination unreachable message with the 'communication with destination administratively prohibited' (1) code is sent.










Counter ID: M563C214 Network element name: ICP6S_DSTUNREACHBEYONDSCOPE

Version: 4.1 NetAct name: ICP6S_DSTUNREACHBEYONDSCOPE

Description: The number of ICMPv6 Destination Unreachable messages with the 'beyond scope' (2) code.

Updated: When an ICMPv6 destination unreachable message with the 'beyond scope' (2) code is sent.



488 DN04143903











Counter ID: M563C215 Network element name: ICP6S_DSTUNREACHADDR

Version: 4.1 NetAct name: ICP6S_DSTUNREACHADDR

Description: The number of ICMPv6 Destination Unreachable messages with address unreachable (3) code.

Updated: When an ICMPv6 destination unreachable message with address unreachable (3) code is sent.










Counter ID: M563C216 Network element name: ICP6S_DSTUNREACHNOPORT

Version: 4.1 NetAct name: ICP6S_DSTUNREACHNOPORT

Description: The number of ICMPv6 Destination Unreachable messages with the 'port unreachable' (4) code.

Updated: When an ICMPv6 destination unreachable message with the 'port unreachable' (4) code is sent.









DN04143903 489




Counter ID: M563C217 Network element name: ICP6S_PACKETTOOBIG

Version: 4.1 NetAct name: ICP6S_PACKETTOOBIG

Description: The number of ICMPv6 Too Big messages (with code 0).

Updated: When an ICMPv6 too big (code=0) message is sent.










Counter ID: M563C218 Network element name: ICP6S_TIMEEXCEEDTRANSIT

Version: 4.1 NetAct name: ICP6S_TIMEEXCEEDTRANSIT

Description: The number of ICMPv6 Time Exceeded messages with the 'hop limit exceeded in transit' code (0).

Updated: When an ICMPv6 time exceeded message with the 'hop limit exceeded in transit' code (0) is sent.










Counter ID: M563C219 Network element name: ICP6S_TIMEEXCEEDREASSEMBLY

Version: 4.1 NetAct name: ICP6S_TIMEEXCEEDREASSEMBLY

490 DN04143903




Description: The number of ICMPv6 Time Exceeded messages with the 'fragment reassembly time exceeded' code (1).

Updated: When an ICMPv6 time exceeded message with the 'fragment reassembly time exceeded' code (1) is sent.










Counter ID: M563C220 Network element name: ICP6S_PARAMPROBHEADER

Version: 4.1 NetAct name: ICP6S_PARAMPROBHEADER

Description: The number of ICMPv6 Parameter Problem messages with the 'erroneous header field encountered' code (0).

Updated: When an ICMPv6 parameter problem message with the 'erroneous header field encountered' code (0) is sent.










Counter ID: M563C221 Network element name: ICP6S_PARAMPROBNEXTHEADER

Version: 4.1 NetAct name: ICP6S_PARAMPROBNEXTHEADER

Description: The number of ICMPv6 Parameter Problem messages with the 'unrecognized Next Header type encountered' code (1).

Updated: When an ICMPv6 parameter problem message with the 'unrecognized next header type encountered' code (1) is sent.



DN04143903 491










Counter ID: M563C222 Network element name: ICP6S_PARAMPROBOPTION

Version: 4.1 NetAct name: ICP6S_PARAMPROBOPTION

Description: The number of ICMPv6 Parameter Problem messages with the 'unrecognized IPv6 option encountered' code (2).

Updated: When an ICMPv6 parameter problem message with the 'unrecognized IPv6 option encoun-tered' code (2) is sent.










Counter ID: M563C223 Network element name: ICP6S_REDIRECT

Version: 4.1 NetAct name: ICP6S_REDIRECT

Description: The number of ICMPv6 Redirect messages.

Updated: When an ICMPv6 redirect message is sent.










492 DN04143903




Counter ID: M563C224 Network element name: ICP6S_UNKNOWN

Version: 4.1 NetAct name: ICP6S_UNKNOWN

Description: The number of unknown ICMPv6 messages.

Updated: When an unknown ICMPv6 message is received.










Counter ID: M563C225 Network element name: ICP6S_ND_TOOMANYOPT

Version: 4.1 NetAct name: ICP6S_ND_TOOMANYOPT

Description: The number of ICMPv6 messages with too many ND options.

Updated: When an ICMPv6 message with too many ND options is received.










Counter ID: M563C226 Network element name: UDP6S_IPACKETS

Version: 4.1 NetAct name: UDP6S_IPACKETS

Description: Received UDPv6 datagrams. The total number of received UDP datagrams delivered to UDPv6 users.

Updated: When a UDPv6 datagram is received, including errored ones.



DN04143903 493










Counter ID: M563C227 Network element name: UDP6S_HDROPS

Version: 4.1 NetAct name: UDP6S_HDROPS

Description: Incomplete UDPv6 datagram header. The number of received UDPv6 datagrams not deliv-ered because the packet is shorter than the header.

Updated: When a UDPv6 datagram that is shorter than the UDP's header is received.










Counter ID: M563C228 Network element name: UDP6S_BADLEN

Version: 4.1 NetAct name: UDP6S_BADLEN

Description: Bad data length of a UDPv6 datagram. The number of received UPDv6 datagrams not deliv-ered because the data is longer than the packet.

Updated: When a UDPv6 datagram with the data longer than the received packet is received.










494 DN04143903




Counter ID: M563C229 Network element name: UDP6S_BADSUM

Version: 4.1 NetAct name: UDP6S_BADSUM

Description: Bad checksum of a UDPv6 datagram. The number of received UPDv6 datagrams not deliv-ered because of checksum errors.

Updated: When a UDPv6 datagram with errored checksum is received.










Counter ID: M563C230 Network element name: UDP6S_NOSUM

Version: 4.1 NetAct name: UDP6S_NOSUM

Description: Received UDPv6 datagrams without checksum.

Updated: When a UDPv6 datagram is received without checksum.










Counter ID: M563C231 Network element name: UDP6S_NOPORT

Version: 4.1 NetAct name: UDP6S_NOPORT

Description: Received UDPv6 datagrams with no process on the destination port.

Updated: When a UDPv6 datagram received, but there is no process-provided service on the destination port.


DN04143903 495











Counter ID: M563C232 Network element name: UDP6S_NOPORTMCAST

Version: 4.1 NetAct name: UDP6S_NOPORTMCAST

Description: Multicast UPDv6 datagrams with no port. The number of received UPDv6 multicast/broad-cast datagrams discarded because of no process on the destination port.

Updated: When a UDPv6 multicast/broadcast datagram is received, but there is no process serving on the destination port.










Counter ID: M563C233 Network element name: UDP6S_FULLSOCK

Version: 4.1 NetAct name: UDP6S_FULLSOCK

Description: UDPv6 datagrams dropped because of full socket buffers. The number of received UDPv6 datagrams not delivered because input socket buffers are full.

Updated: When a UDPv6 datagram is received, but there is no input socket buffer available.








496 DN04143903






Counter ID: M563C234 Network element name: UDP6S_PCBCACHEMISS

Version: 4.1 NetAct name: UDP6S_PCBCACHEMISS

Description: UDPv6 PCB hash misses. The number of UPDv6 datagrams with Process Control Block (PCB) hash misses.

Updated: When a UDPv6 datagram with a missed process control block (PCB) is received.










Counter ID: M563C235 Network element name: UDP6S_OPACKETS

Version: 4.1 NetAct name: UDP6S_OPACKETS

Description: UDPv6 datagrams output. Total number of UDPv6 datagrams sent.

Updated: When a UDPv6 datagram is sent.










Counter ID: M563C236 Network element name: SCTP_CURRENT_ESTABLISHMENT

Version: 4.1 NetAct name: SCTP_CURRENT_ESTABLISHMENT

Description: The number of associations for which the current state is either ESTABLISHED, SHUTDOWN-RECEIVED or SHUTDOWN-PENDING.

DN04143903 497



Updated: The number of associations is sampled at the end of measurement interval.










Counter ID: M563C237 Network element name: SCTP_ACTIVE_ESTABLISHMENT

Version: 3.1 NetAct name: SCTP_ACTIVE_ESTABLISHMENT

Description: The number of times that associations have made a direct transition to the ESTABLISHED state from the COOKIE-ECHOED state: COOKIE-ECHOED -> ESTABLISHED. The upper layer initiated the association attempt.

Updated: When association is established actively.










Counter ID: M563C238 Network element name: SCTP_PASSIVE_ESTABLISHMENT

Version: 3.1 NetAct name: SCTP_PASSIVE_ESTABLISHMENT

Description: The number of times that associations have made a direct transition to the ESTABLISHED state from the CLOSED state: CLOSED -> ESTABLISHED. The remote endpoint initiated the association attempt.

Updated: When association is established passively.







498 DN04143903







Counter ID: M563C239 Network element name: SCTP_RESTARTED

Version: 3.1 NetAct name: SCTP_RESTARTED

Description: The number of restarted SCTP associations due to peer dropped.

Updated: When association is restarted.










Counter ID: M563C240 Network element name: SCTP_ABORTED

Version: 3.1 NetAct name: SCTP_ABORTED

Description: The number of times that associations have made a direct transition to the CLOSED state from any state using the primitive 'ABORT': AnyState --Abort--> CLOSED. Ungraceful termination of the association.

Updated: When association is closed with ABORT.










Counter ID: M563C241 Network element name: SCTP_SHUTDOWNS

Version: 3.1 NetAct name: SCTP_SHUTDOWNS

Description: The number of times that associations have made a direct transition to the CLOSED state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state. Graceful termination of the association.

DN04143903 499



Updated: When association is closed with SHUTDOWN.










Counter ID: M563C242 Network element name: SCTP_TOO_MANY_RETRANSMISSIONS

Version: 3.1 NetAct name: SCTP_TOO_MANY_RETRANSMISSIONS

Description: The number of associations closed due to excessive retransmissions.

Updated: When association is closed due to excessive retransmissions.










Counter ID: M563C243 Network element name: SCTP_RECEIVED_BYTES

Version: 3.1 NetAct name: SCTP_RECEIVED_BYTES

Description: The number of bytes received in sequence.

Updated: When an SCTP segment is received in sequence, this counter will be updated to tell how many bytes have been received.








500 DN04143903






Counter ID: M563C244 Network element name: SCTP_RECEIVED_PACKETS

Version: 3.1 NetAct name: SCTP_RECEIVED_PACKETS

Description: The number of SCTP packets received. Duplicates and invalid packets are included.

Updated: When an SCTP packet is received.










Counter ID: M563C245 Network element name: SCTP_RECEIVED_DATAGRAMS

Version: 3.1 NetAct name: SCTP_RECEIVED_DATAGRAMS

Description: The number of received valid packets.

Updated: When a valid packet is received.










Counter ID: M563C246 Network element name: SCTP_RECEIVED_CONTROL

Version: 3.1 NetAct name: SCTP_RECEIVED_CONTROL

Description: The number of SCTP control chunks received (no duplicate chunks included).

Updated: When an SCTP segment with control chunks is received.



DN04143903 501










Counter ID: M563C247 Network element name: SCTP_RECEIVED_OOTB

Version: 3.1 NetAct name: SCTP_RECEIVED_OOTB

Description: The number of out of the blue packets received by the host. An out of the blue packet is an SCTP packet correctly formed, including the proper checksum, but for which the receiver was unable to identify an appropriate association.

Updated: When an SCTP segment with an out of the blue sequence is received.










Counter ID: M563C248 Network element name: SCTP_RECEIVED_DUPLICATED_TSN

Version: 3.1 NetAct name: SCTP_RECEIVED_DUPLICATED_TSN

Description: The number of received duplicated TSN.

Updated: When an SCTP segment with duplicate TSN is received.










502 DN04143903




Counter ID: M563C249 Network element name: SCTP_DROPPED_FRAGMENT

Version: 3.1 NetAct name: SCTP_DROPPED_FRAGMENT

Description: The number of dropped invalid fragments.

Updated: When an invalid fragment is dropped.










Counter ID: M563C250 Network element name: SCTP_BAD_SSN

Version: 3.1 NetAct name: SCTP_BAD_SSN

Description: The number of dropped chunks due to bad stream sequence number.

Updated: When dropped due to bad stream sequence number.










Counter ID: M563C251 Network element name: SCTP_BAD_CSUM

Version: 3.1 NetAct name: SCTP_BAD_CSUM

Description: The number of SCTP packets received with an invalid checksum.

Updated: When dropped due to bad checksum.






DN04143903 503







Counter ID: M563C252 Network element name: SCTP_BAD_VTAG

Version: 3.1 NetAct name: SCTP_BAD_VTAG

Description: The number of dropped SCTP packets due to bad verification tag.

Updated: When dropped due to bad verification tag.










Counter ID: M563C253 Network element name: SCTP_BAD_STREAM_NBR

Version: 3.1 NetAct name: SCTP_BAD_STREAM_NBR

Description: The number of dropped chunks due to bad stream number.

Updated: When dropped due to bad stream number.










Counter ID: M563C254 Network element name: SCTP_IN_MULTICAST

Version: 3.1 NetAct name: SCTP_IN_MULTICAST

Description: The number of dropped multicast SCTP packets (SCTP cannot be multicast).

Updated: When dropped multicast (SCTP cannot be multicast).

504 DN04143903













Counter ID: M563C255 Network element name: SCTP_HEADER_DROPS

Version: 3.1 NetAct name: SCTP_HEADER_DROPS

Description: The number of dropped SCTP packets due to bad header.

Updated: When dropped due to bad header.










Counter ID: M563C256 Network element name: SCTP_RECEIVE_WINDOW_DROPS

Version: 3.1 NetAct name: SCTP_RECEIVE_WINDOW_DROPS

Description: The number of dropped SCTP packets due to no receive window.

Updated: When dropped due to no receive window.










DN04143903 505



Counter ID: M563C257 Network element name: SCTP_NO_PORTS

Version: 3.1 NetAct name: SCTP_NO_PORTS

Description: The number of dropped SCTP packets due to no endpoint found.

Updated: When dropped due to no endpoint found.










Counter ID: M563C258 Network element name: SCTP_NO_MEMORY

Version: 3.1 NetAct name: SCTP_NO_MEMORY

Description: The number of SCTP chunks dropped due to no memory.

Updated: When dropped due to no memory.










Counter ID: M563C259 Network element name: SCTP_SENT_BYTES

Version: 3.1 NetAct name: SCTP_SENT_BYTES

Description: The number of SCTP bytes sent.

Updated: When an SCTP segment is sent, this counter will tell how many bytes have been sent.






506 DN04143903








Counter ID: M563C260 Network element name: SCTP_SENT_DATAGRAMS

Version: 3.1 NetAct name: SCTP_SENT_DATAGRAMS

Description: The number of SCTP packets sent. Retransmitted DATA chunks are included.

Updated: When an SCTP segment whose length is more than zero is sent.










Counter ID: M563C261 Network element name: SCTP_SENT_CONTROL

Version: 3.1 NetAct name: SCTP_SENT_CONTROL

Description: The number of SCTP control chunks sent (retransmissions are not included). Control chunks are those chunks different from DATA.

Updated: When an SCTP control segment is sent.










Counter ID: M563C262 Network element name: SCTP_SENT_RETRANSMISSIONS

Version: 3.1 NetAct name: SCTP_SENT_RETRANSMISSIONS

Description: The number of retransmitted SCTP chunks.

Updated: When retransmitted SCTP data is sent.

DN04143903 507












Counter ID: M563C263 Network element name: SCTP_SENT_FAST_RETRANSMISSIONS

Version: 3.1 NetAct name: SCTP_SENT_FAST_RETRANSMISSIONS

Description: The number of fast retransmitted SCTP chunks.

Updated: When fast retransmission is sent.










Counter ID: M563C264 Network element name: SCTP_SENT_WINDOW_PROBE

Version: 3.1 NetAct name: SCTP_SENT_WINDOW_PROBE

Description: The number of SCTP chunks sent for window probes.

Updated: When window probe is sent.










508 DN04143903




Counter ID: M563C265 Network element name: SCTP_RECEIVED_CHUNK_DATA

Version: 3.1 NetAct name: SCTP_RECEIVED_CHUNK_DATA

Description: The number of SCTP DATA chunks received.

Updated: When DATA chunk is received.










Counter ID: M563C266 Network element name: SCTP_SENT_CHUNK_DATA

Version: 3.1 NetAct name: SCTP_SENT_CHUNK_DATA

Description: The number of SCTP DATA chunks sent.

Updated: When DATA chunk is sent.










Counter ID: M563C267 Network element name: SCTP_RECEIVED_CHUNK_SACK

Version: 3.1 NetAct name: SCTP_RECEIVED_CHUNK_SACK

Description: The number of SCTP SACK chunks received.

Updated: When SACK chunk is received.






DN04143903 509







Counter ID: M563C268 Network element name: SCTP_SENT_CHUNK_SACK

Version: 3.1 NetAct name: SCTP_SENT_CHUNK_SACK

Description: The number of SCTP SACK chunks sent.

Updated: When SACK chunk is sent.










Counter ID: M563C269 Network element name: SCTP_RECEIVED_CHUNK_HBREQ

Version: 3.1 NetAct name: SCTP_RECEIVED_CHUNK_HBREQ

Description: The number of SCTP HEARTBEAT-REQ chunks received.

Updated: When HEARTBEAT-REQ chunk is received.










Counter ID: M563C270 Network element name: SCTP_SENT_CHUNK_HBREQ

Version: 3.1 NetAct name: SCTP_SENT_CHUNK_HBREQ

Description: The number of SCTP HEARTBEAT-REQ chunks sent.

Updated: When HEARTBEAT-REQ chunk is sent.

510 DN04143903













Counter ID: M563C271 Network element name: SCTP_RECEIVED_CHUNK_HBACK

Version: 3.1 NetAct name: SCTP_RECEIVED_CHUNK_HBACK

Description: The number of SCTP HEARTBEAT-ACK chunks received.

Updated: When HEARTBEAT-ACK chunk is received.










Counter ID: M563C272 Network element name: SCTP_SENT_CHUNK_HBACK

Version: 3.1 NetAct name: SCTP_SENT_CHUNK_HBACK

Description: The number of SCTP HEARTBEAT-ACK chunks sent.

Updated: When HEARTBEAT-ACK chunk is sent.










DN04143903 511



8.2 Iu-PS performance measurement (801/321H)

8.2.1 Introduction to Iu-PS performance measurementThe Iu-PS performance measurement provides statistics of the Iu-PS interface traffic load and the GTP protocol specific events between the RNC and the PS core.

The measurement provides counters that are updated per GTPU unit in the RNC, it is not supported for NPS1 and NPGE based Iu-PS interfaces. The RNC-specific or RAN total Iu-PS statistics can be calculated by summing the GTPU-specific counters in NetAct. The Iu-PS interface termination in the RNC and the relation to the GTPU units is described in the figure Iu-PS interface termination in the RNC.

Figure 14 Iu-PS interface termination in the RNC

The throughput of Iu-PS interface can be followed for each UMTS traffic class (TC) sep-arately in both the uplink and downlink. The measured throughput values do not include any transport headers, only the payload data.

This measurement is optional and available as a part of feature AAL2 Resource Reser-vation Statistics.


8.2.2 Iu-PS performance measurement counters

GTPU-1

GTPU-2

GTPU-n

Iu-PSPS core

RNC

Counter ID: M801C0 Network element name: INPUT_BYTES_TOTAL_UDP

Version: 2.2 NetAct name: INPUT_BYTES_TOTAL_UDP

Description: The total number of user data bytes received from the PS core network to the RNC GTPU unit. Includes both the user data and the control messages payload. Does not include the IP, UDP or GTP headers.

Updated: When data is received from the PS core network.


Unit: 10 bytes Range: Example values:


Operability class:

Related to feature:

RAN 1163: Iu-PS Throughput Measurement for GTP Traffic





512 DN04143903




Used from release: RN2.2ED Definition updated in release:

Counter ID: M801C1 Network element name: INPUT_IP_PACKETS_TOTAL

Version: 2.2 NetAct name: INPUT_IP_PACKETS_TOTAL

Description: The number of IP packets received from the PS core network to the RNC GTPU unit.





Operability class:

Related to feature:







Counter ID: M801C2 Network element name: INPUT_TRAF_BYTES_TC_CONV

Version: 2.2 NetAct name: INPUT_TRAF_BYTES_TC_CONV

Description: The number of user data bytes received from the PS core network to the RNC GTPU unit for conversational class connections. Does not include the IP, UDP or GTP headers.

Updated: Not updated, since conversational class is not supported for the PS.




Operability class:

Related to feature:







Counter ID: M801C3 Network element name: INPUT_TRAF_BYTES_TC_STREAM

Version: 2.2 NetAct name: INPUT_TRAF_BYTES_TC_STREAM

DN04143903 513



Description: The number of user data bytes received from the PS core network to the RNC GTPU unit for streaming class connections. Does not include the IP, UDP or GTP headers.





Operability class:

Related to feature:







Counter ID: M801C4 Network element name: INPUT_TRAF_BYTES_TC_INTERAC

Version: 2.2 NetAct name: INPUT_TRAF_BYTES_TC_INTERAC

Description: The number of user data bytes received from the PS core network to the RNC GTPU unit for interactive class connections. Does not include the IP, UDP or GTP headers.





Operability class:

Related to feature:







Counter ID: M801C5 Network element name: INPUT_TRAF_BYTES_TC_BACKGR

Version: 2.2 NetAct name: INPUT_TRAF_BYTES_TC_BACKGR

Description: The number of user data bytes received from the PS core network to the RNC GTPU unit for background class connections. Does not include the IP, UDP or GTP headers.



514 DN04143903






Operability class:

Related to feature:







Counter ID: M801C6 Network element name: OUTPUT_BYTES_TOTAL_UDP

Version: 2.2 NetAct name: OUTPUT_BYTES_TOTAL_UDP

Description: The total number of traffic bytes sent from the RNC GTPU unit to the PS core network. Includes both the user data and the control messages payload. Does not include the IP, UDP or GTP headers.

Updated: When data is sent to the PS core network.




Operability class:

Related to feature:







Counter ID: M801C7 Network element name: OUTPUT_IP_PACKETS_TOTAL

Version: 2.2 NetAct name: OUTPUT_IP_PACKETS_TOTAL

Description: The number of IP packets sent from the RNC GTPU unit to the PS core network.





Operability class:

Related to feature:



DN04143903 515







Counter ID: M801C8 Network element name: OUTPUT_TRAF_BYTES_TC_CONV

Version: 2.2 NetAct name: OUTPUT_TRAF_BYTES_TC_CONV

Description: The number of user data bytes sent from the RNC GTPU unit to the PS core network for conversational class connections. Does not include the IP, UDP or GTP headers.

Updated: Not updated, since conversational class is not supported for the PS.




Operability class:

Related to feature:







Counter ID: M801C9 Network element name: OUTPUT_TRAF_BYTES_TC_STREAM

Version: 2.2 NetAct name: OUTPUT_TRAF_BYTES_TC_STREAM

Description: The number of user data bytes sent from the RNC GTPU unit to the PS core network for streaming class connections. Does not include the IP, UDP or GTP headers.





Operability class:

Related to feature:







516 DN04143903




Counter ID: M801C10 Network element name: OUTPUT_TRAF_BYTES_TC_INTERAC

Version: 2.2 NetAct name: OUTPUT_TRAF_BYTES_TC_INTERAC

Description: The number of user data bytes sent from the RNC GTPU unit to the PS core network for interactive class connections. Does not include the IP, UDP or GTP headers.





Operability class:

Related to feature:







Counter ID: M801C11 Network element name: OUTPUT_TRAF_BYTES_TC_BACKGR

Version: 2.2 NetAct name: OUTPUT_TRAF_BYTES_TC_BACKGR

Description: The number of user data bytes sent from the RNC GTPU unit to the PS core network for background class connections. Does not include the IP, UDP or GTP headers.





Operability class:

Related to feature:







Counter ID: M801C12 Network element name: ECHO_REQUEST_RECEIVED

Version: 2.2 NetAct name: ECHO_REQUEST_RECEIVED

DN04143903 517



Description: The number of GTP: Echo Request messages received from the SGSN.

Updated: When a GTP: Echo Request message is received from the SGSN.




Operability class:

Related to feature:







Counter ID: M801C13 Network element name: ECHO_RESPONSE_RECEIVED

Version: 2.2 NetAct name: ECHO_RESPONSE_RECEIVED

Description: The number of GTP: Echo Response messages received from the SGSN.

Updated: When a GTP: Echo Response message is received from the SGSN.




Operability class:

Related to feature:







Counter ID: M801C14 Network element name: ECHO_RESPONSE_SENT

Version: 2.3 NetAct name: ECHO_RESPONSE_SENT

Description: The number of GTP: Echo Response messages sent to the SGSN.

Updated: When a GTP: Echo Response message is sent to the SGSN.




Operability class:

518 DN04143903




Related to feature:







Counter ID: M801C15 Network element name: ERROR_INDICATIONS_RECEIVED

Version: 2.2 NetAct name: ERROR_INDICATIONS_RECEIVED

Description: The number of GTP: Error Indication messages received from the SGSN.

Updated: When a GTP: Error Indication message is received from the SGSN.




Operability class:

Related to feature:







Counter ID: M801C16 Network element name: ERROR_INDICATIONS_SENT

Version: 2.2 NetAct name: ERROR_INDICATIONS_SENT

Description: The number of GTP: Error Indication messages sent to the SGSN.

Updated: When a GTP: Error Indication message is sent to the SGSN.




Operability class:

Related to feature:







DN04143903 519



Counter ID: M801C17 Network element name: EXTENS_HEAD_NOTIF_RECEIVED

Version: 2.2 NetAct name: EXTENS_HEAD_NOTIF_RECEIVED

Description: The number of GTP: Supported Extension Headers Notification messages received from the SGSN.

Updated: When a GTP: Extension Headers Notification message is received from the SGSN.




Operability class:

Related to feature:







Counter ID: M801C18 Network element name: AVERAGE_NBR_OF_GTP_TUNNELS

Version: 2.2 NetAct name: AVERAGE_NBR_OF_GTP_TUNNELS

Description: The average number of GTP tunnels during a measurement period.

Updated: The number of GTP tunnels is sampled continuously with one second intervals and this counter provides the average of the sampled values.




Operability class:

Related to feature:







Counter ID: M801C19 Network element name: MAX_NBR_OF_GTP_TUNNELS

Version: 2.2 NetAct name: MAX_NBR_OF_GTP_TUNNELS

Description: The maximum number of GTP tunnels during a measurement period.

520 DN04143903




8.3 IP Based Route measurement (568/238H)The IP based route measurement provides information on the throughput and number of connections in the IP routes used in Iu-CS, Iu-PS, Iur or Iub interfaces. An IP route can be, for example, an Iub link towards one base station.

The object of the measurement is an IP route that is identified with a numeric route ID. In the measurement data that is sent to NetAct, a WBTS identifier is also included if the route is used in the Iub interface.

Counters M568C10-M568C17, related to the RAN2106: Bandwidth utilization classes counters for IP and Ethernet feature, are available only if the RNC license for RAN2106 is installed (feature code 1897).

Updated: When a new GTP tunnel is established, the total number of tunnels is checked, and if the number exceeds the previous maximum value, this counter is updated.




Operability class:

Related to feature:







Counter ID: M568C0 Network element name: OUT_DATA_IP_ROUTE

Version: 1.2 NetAct name: OUT_DATA_IP_ROUTE

Description: The IP datagram data volume sent out to IP route (egress). Includes both the payload and IP datagram header bytes.

Updated: When an IP datagram is sent.




Operability class:

Related to feature:

RAN 74: IP Based Iub for Flexi WCDMA BTSRAN 75: IP Based Iu-CSRAN 76: IP Based IurRAN 750: IP Based Iu-PS






DN04143903 521



Counter ID: M568C1 Network element name: IN_DATA_IP_ROUTE

Version: 1.2 NetAct name: IN_DATA_IP_ROUTE

Description: The IP datagram data volume received from IP route (ingress). Includes both the payload and IP datagram header bytes.

Updated: When an IP datagram is received.




Operability class:

Related to feature:

RAN 74: IP Based Iub for Flexi WCDMA BTSRAN 75: IP Based Iu-CSRAN 76: IP Based IurRAN 750: IP Based Iu-PS






Counter ID: M568C2 Network element name: COMMITTED_BIT_RATE_IP_ROUTE

Version: 4.0 NetAct name: COMMITTED_BIT_RATE_IP_ROUTE

Description: IP Based Route configured bandwidth available for user connections at the end of the mea-surement interval. This is calculated with "committed bit rate" - "signaling bandwidth" - "DCN bandwidth".

Updated: The counter is updated by the currently configured bit rate at the end of the measurement inter-val.

Logical type: Current Trigger type: Sample Sampling interval:



Operability class:

Related to feature:

RAN74: IP Based Iub for Flexi WCDMA BTS

RAN75: IP Based Iu-CS

RAN76: IP Based Iur

RAN750: IP Based Iu-PS






Counter ID: M568C3 Network element name: SUM_RESERVED_RATE_IP_ROUTE

522 DN04143903




Version: 4.1 NetAct name: SUM_RESERVED_RATE_IP_ROUTE

Description: Sum of samples for reserved IP layer bit rate for IP based route.This counter, divided by the denominator M568C9, provides the average reserved bit rate. If the IP based route is bound with IP addresses on multiple NPGE units, the counter provides the sum over all the units.

Updated: The bit rate is sampled at 5 second intervals.




M568C9: NBR_SAMPLES_IP_ROUTE

Operability class:

Related to feature:



RAN76: IP Based Iur







Counter ID: M568C4 Network element name: MIN_RESERVED_RATE_IP_ROUTE

Version: 4.1 NetAct name: MIN_RESERVED_RATE_IP_ROUTE

Description: The minimum value of reserved IP layer bit rate during the measurement interval. If the IP based route is bound with IP addresses on multiple NPGE units, the counter shows the minimum reser-vation calculated over all the units.





Operability class:

Related to feature:



RAN76: IP Based Iur







DN04143903 523



Counter ID: M568C5 Network element name: MAX_RESERVED_RATE_IP_ROUTE

Version: 4.1 NetAct name: MAX_RESERVED_RATE_IP_ROUTE

Description: The maximum value of reserved IP layer bit rate during the measurement interval. If the IP based route is bound with IP addresses on multiple NPGE units, the counter shows the maximum res-ervation calculated over all the units.





Operability class:

Related to feature:



RAN76: IP Based Iur







Counter ID: M568C6 Network element name: SUM_IP_UDP_CONN_IP_ROUTE

Version: 4.1 NetAct name: SUM_IP_UDP_CONN_IP_ROUTE

Description: The sum of UDP/IP connections for IP based route. This counter, divided by the denomina-tor M568C9, provides the average number of connections. If the IP based route is bound with IP addresses on multiple NPGE units, the counter provides the sum over all the units.

Updated: The number of connections is sampled at 5 second interval.




Operability class:

Related to feature:



RAN76: IP Based Iur







524 DN04143903




Counter ID: M568C7 Network element name: MIN_IP_UDP_CONN_IP_ROUTE

Version: 7.1 NetAct name: MIN_IP_UDP_CONN_IP_ROUTE

Description: The minimum number of IP/UDP connections during the measurement interval. If the IP based route is bound with IP addresses on multiple NPGE units, the counter shows the minimum con-nection amount calculated over all the units.

Updated: The number of connections is sampled with 5 second interval.




Operability class:

Related to feature:



RAN76: IP Based Iur







Counter ID: M568C8 Network element name: MAX_IP_UDP_CONN_IP_ROUTE

Version: 7.1 NetAct name: MAX_IP_UDP_CONN_IP_ROUTE

Description: The maximum number of IP/UDP connections during the measurement interval. If the IP based route is bound with IP addresses on multiple NPGE units, the counter shows the maximum con-nection amount calculated over all the units.

Updated: The number of connections is sampled with 5 second interval.




Operability class:

Related to feature:



RAN76: IP Based Iur







DN04143903 525



Counter ID: M568C9 Network element name: NBR_SAMPLES_IP_ROUTE

Version: 4.0 NetAct name: NBR_SAMPLES_IP_ROUTE

Description: The number of samples used for calculating the average number of IP/UDP connections and the average reserved bit rate.

Updated: Sampled at 5 second intervals.




M568C9: NBR_SAMPLES_IP_ROUTE

Operability class:

Related to feature:



RAN76: IP Based Iur







Counter ID: M568C10 Network element name: IP_EG_BW_UTI_CLASS_1

Version: 4.1 NetAct name: IP_EG_BW_UTI_CLASS_1

Description: The number of samples where the IP based route egress throughput was less than 26% of the configured bandwidth shown by counter M568C15. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing), internal flow control is enabled and the route band-width is defined.





Operability class:

Related to feature:

RAN2106: Bandwidth utilization classes counters for IP





Used from release: RN7.0 / mcRNC3.0

Definition updated in release:

526 DN04143903






Description: The number of samples where the IP based route egress throughput is less than (26<=throughput<51%) of the configured bandwidth shown by counter M568C15. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing), internal flow control is enabled and the route bandwidth is defined.





Operability class:

Related to feature:










Description: The number of samples where the IP based route egress throughput was (51<=through-put<76%) of the configured bandwidth shown by counter M568C15. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing), internal flow control is enabled and the route bandwidth is defined.





Operability class:

Related to feature:










DN04143903 527



Description: The number of samples where the IP based route egress throughput was (76<=through-put<88%) of the configured bandwidth shown by counter M568C15. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing), internal flow control is enabled and the route bandwidth is defined.





Operability class:

Related to feature:










Description: The number of samples where the IP based route egress throughput was 88% or more of the configured bandwidth shown by counter M568C15. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing), internal flow control is enabled and the route band-width is defined.





Operability class:

Related to feature:








Counter ID: M568C15 Network element name: IP_EG_BW_CONFIG

Version: 4.0 NetAct name: IP_EG_BW_CONFIG

Description: The IP based route egress bandwidth used for shaping. If the route bandwidth is not defined, the counter shows a value of zero.

Updated: The value is sampled at the end of the measurement period.

528 DN04143903




Logical type: Current Trigger type: Sample Sampling interval:



Operability class:

Related to feature:








Counter ID: M568C16 Network element name: IP_EG_PEAK_THRPUT

Version: 4.1 NetAct name: IP_EG_PEAK_THRPUT

Description: The peak egress throughput of the IP based route. The counter shows the highest through-put calculated over a 5 second averaging window. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing).





Operability class:

Related to feature:








Counter ID: M568C17 Network element name: IP_IN_PEAK_THRPUT

Version: 4.1 NetAct name: IP_IN_PEAK_THRPUT

Description: The peak ingress throughput of the IP based route. The counter shows the highest through-put calculated over a 5 second averaging window. The counter is updated only if the IP-based route goes via one network interface unit (no load sharing).





Operability class:

DN04143903 529



Related to feature:








Counter ID: M568C18 Network element name: IN_MUX_PACKETS_IP_ROUTE

Version: 1.0 NetAct name: IN_MUX_PACKETS_IP_ROUTE

Description: The number of multiplex IP packets received in the IP based route. This is the amount of the combined packets with possibly multiple end user data packets inside.

Updated: When a multiplex IP packet is received by the RNC.




Operability class:

Related to feature:

RAN1886: Efficient Transport for small IP packets






Counter ID: M568C19 Network element name: IN_MUXED_PACKETS_IP_ROUTE

Version: 1.0 NetAct name: IN_MUXED_PACKETS_IP_ROUTE

Description: The number of multiplexed IP packets received in the IP based route. This is the number of the original user data packets.

Updated: When a multiplexed IP packet is received by the RNC.




Operability class:

Related to feature:







530 DN04143903




Counter ID: M568C20 Network element name: IN_DISC_MUX_PACKETS_IP_ROUTE

Version: 1.0 NetAct name: IN_DISC_MUX_PACKETS_IP_ROUTE

Description: The number of multiplex IP packets discarded in the IP based route.

Updated: When either the entire multiplex packet or part of user data must be discarded by the UDP mul-tiplexing function in the RNC.




Operability class:

Related to feature:







Counter ID: M568C21 Network element name: OUT_MUX_PACKETS_IP_ROUTE

Version: 1.0 NetAct name: OUT_MUX_PACKETS_IP_ROUTE

Description: The number of multiplex IP packets sent in the IP based route. This is the number of the combined packets with possibly multiple end user data packets inside.

Updated: When a multiplex IP packet is sent by the RNC.




Operability class:

Related to feature:







Counter ID: M568C22 Network element name: OUT_MUXED_PACKETS_IP_ROUTE

Version: 1.0 NetAct name: OUT_MUXED_PACKETS_IP_ROUTE

Description: The number of multiplexed IP packets sent in the IP based route. This is the number of the original user data packets.

Updated: When a multiplexed IP packet is sent by the RNC.


DN04143903 531



8.4 IP measurement on IP interface (565/235H)IP traffic can be terminated on Network Processor Interface Unit Gigabit Ethernet (NPGE(P)) and Network Processor Interface Unit STM-1 (NPS1 (P)). NPGE(P) and NPS1(P) units support optimized IP transport and packet environment, and provide IP-based Iub, Iur, Iu-PS and Iu-CS interfaces for IP, GTP-U and RTP protocol processing. The IP measurement on IP interface provides statistical information on IPv4 and IPv6 traffic volume and errors, for example, the number of sent and received IPv4 and IPv6 datagrams.

Only NPGE(P) and NPS1(P) can be selected as measured units. The object of the mea-surement is an IP interface that is identified with a unit type, a unit index and an IP inter-face name. The measurement identifier (MID) is 565/235H.

g This measurement is supported by both physical and VLAN IP interfaces with IP addresses.



Operability class:

Related to feature:







Counter ID: M565C0 Network element name: IP4_IN_BYTES

Version: 2.1 NetAct name: IP4_IN_BYTES

Description: The amount of data received in IPv4 datagrams.

Updated: When an IPv4 datagram is received.




Operability class:






Counter ID: M565C1 Network element name: IP4_IN_RECEIVES

532 DN04143903




Version: 2.1 NetAct name: IP4_IN_RECEIVES

Description: The number of received IPv4 datagrams

Updated: When receiving IPv4 datagrams, the counter will be increased by the number of those data-grams.




Operability class:






Counter ID: M565C2 Network element name: IP4_IN_HDR_ERRORS

Version: 5.1 NetAct name: IP4_IN_HDR_ERRORS

Description: The number of received IPv4 datagrams with IP header checksum error

Updated: When receiving IPv4 datagrams with header error, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C3 Network element name: IP4_IN_FORW_DATAGRAMS

Version: 2.1 NetAct name: IP4_IN_FORW_DATAGRAMS

Description: The number of forwarded IPv4 datagrams

Updated: When forwarding IPv4 datagrams, the counter will be increased by the number of those data-grams.




DN04143903 533



Operability class:






Counter ID: M565C4 Network element name: IP4_IN_DELIVERS

Version: 5.1 NetAct name: IP4_IN_DELIVERS

Description: The number of IPv4 datagrams delivered to L4 processing

Updated: When delivering IPv4 datagrams to L4 processing, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C5 Network element name: IP4_IN_NO_ROUTES

Version: 7.2 NetAct name: IP4_IN_NO_ROUTES

Description: The number of received IPv4 datagrams with a destination address for which there is no matching route in the routing table.

Updated: When an IPv4 datagram is received and there is no route found in the routing table matching the destination address.




Operability class:






534 DN04143903




Counter ID: M565C6 Network element name: IP4_IN_REAS_REQDS

Version: 5.1 NetAct name: IP4_IN_REAS_REQDS

Description: The number of IPv4 datagrams for which reassembly was required

Updated: When receiving IPv4 datagrams for which reassembly of fragments was required, the counter will be increased by the number of those fragments.




Operability class:






Counter ID: M565C7 Network element name: IP4_OUT_BYTES

Version: 9.1 NetAct name: IP4_OUT_BYTES

Description: The amount of data sent in IPv4 datagrams.

Updated: When an IPv4 datagram is sent.




Operability class:






Counter ID: M565C8 Network element name: IP4_OUT_REQUESTS

Version: 9.1 NetAct name: IP4_OUT_REQUESTS

Description: The number of locally sent IPv4 datagrams.

Updated: When sending IPv4 datagrams locally, the counter will be increased by the number of those datagrams.


DN04143903 535





Operability class:






Counter ID: M565C9 Network element name: IP4_OUT_NO_L2_ROUTES

Version: 2.1 NetAct name: IP4_OUT_NO_L2_ROUTES

Description: The number of sent IPv4 datagrams for which the L2 gateway was not found

Updated: When sending IPv4 datagrams, but could not find L2 gateway for them, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C10 Network element name: IP4_OUT_FRAG_OKS

Version: 2.1 NetAct name: IP4_OUT_FRAG_OKS

Description: The number of sent IPv4 datagrams which could be successfully fragmented

Updated: When sending IPv4 datagrams, and they could be fragmented successfully, the counter will be increased by the number of those datagrams.




Operability class:





536 DN04143903





Counter ID: M565C11 Network element name: IP4_OUT_FRAG_FAILS

Version: 2.1 NetAct name: IP4_OUT_FRAG_FAILS

Description: The number of sent IPv4 datagrams which could not be successfully fragmented

Updated: When sending IPv4 datagrams, but they could not be fragmented successfully, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C12 Network element name: IP4_OUT_FRAGREATES

Version: 5.1 NetAct name: IP4_OUT_FRAGREATES

Description: The number of fragments created for sent IPv4 datagrams.

Updated: When successfully fragmenting IPv4 datagrams, the counter will be increased by the number of those fragments.When successfully fragmenting IPv4 datagrams, the counter will be increased by 2 in NPGE unit.




Operability class:






Counter ID: M565C13 Network element name: IP6_IN_BYTES

Version: 2.1 NetAct name: IP6_IN_BYTES

Description: The amount of data received in IPv6 datagrams.

DN04143903 537



Updated: When an IPv6 datagram is received.




Operability class:






Counter ID: M565C14 Network element name: IP6_IN_RECEIVES

Version: 2.1 NetAct name: IP6_IN_RECEIVES

Description: The number of received IPv6 datagrams

Updated: When receiving IPv6 datagrams, the counter will be increased by the number of those data-grams.




Operability class:






Counter ID: M565C15 Network element name: IP6_IN_HDR_ERRORS

Version: 2.1 NetAct name: IP6_IN_HDR_ERRORS

Description: The number of received IPv6 datagrams with header error

Updated: When receiving IPv6 datagrams with header error, the counter will be increased by the number of those datagrams.




Operability class:



538 DN04143903







Counter ID: M565C16 Network element name: IP6_IN_FORW_DATAGRAMS

Version: 2.1 NetAct name: IP6_IN_FORW_DATAGRAMS

Description: The number of forwarded IPv6 datagrams

Updated: When forwarding IPv6 datagrams, the counter will be increased by the number of those data-grams.




Operability class:






Counter ID: M565C17 Network element name: IP6_IN_DELIVERS

Version: 2.1 NetAct name: IP6_IN_DELIVERS

Description: The number of IPv6 datagrams delivered to L4 processing

Updated: When delivering IPv6 datagrams to L4 processing, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C18 Network element name: IP6_IN_NO_ROUTES

Version: 2.1 NetAct name: IP6_IN_NO_ROUTES

DN04143903 539



Description: The number of IPv6 datagrams in which there was no IP route defined

Updated: When receiving IPv6 datagrams without IP route, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C19 Network element name: IP6_IN_REAS_REQDS

Version: 2.1 NetAct name: IP6_IN_REAS_REQDS

Description: The number of IPv6 datagrams for which reassembly was required

Updated: When receiving IPv6 datagrams for which reassembly was required, the counter will be increased by the number of those datagrams.




Operability class:






Counter ID: M565C20 Network element name: IP6_IN_TOO_BIG_ERRORS

Version: 2.1 NetAct name: IP6_IN_TOO_BIG_ERRORS

Description: The number of IPv6 datagrams which exceed MTU

Updated: When receiving IPv6 datagrams which exceed MTU, the counter will be increased by the number of those datagrams.




Operability class:

540 DN04143903









Counter ID: M565C21 Network element name: IP6_IN_TRUNCATED_PKTS

Version: 2.1 NetAct name: IP6_IN_TRUNCATED_PKTS

Description: The number of discarded IPv6 datagrams which do not carry enough data.

Updated: When an IPv6 datagram with not enough data is received.




Operability class:






Counter ID: M565C22 Network element name: IP6_OUT_BYTES

Version: 2.1 NetAct name: IP6_OUT_BYTES

Description: The amount of data sent in IPv6 datagrams.

Updated: When an IPv6 datagram is sent.




Operability class:






Counter ID: M565C23 Network element name: IP6_OUT_REQUESTS

DN04143903 541



Version: 2.1 NetAct name: IP6_OUT_REQUESTS

Description: The number of IPv6 datagrams which are locally sent.

Updated: When an IPv6 datagram is sent locally.




Operability class:






Counter ID: M565C24 Network element name: IP6_OUT_NO_L2_ROUTES

Version: 2.1 NetAct name: IP6_OUT_NO_L2_ROUTES

Description: The number of sent IPv6 datagrams for which the L2 gateway was not found.

Updated: When an IPv6 datagram, for which the L2 gateway could not be found, is sent.




Operability class:






Counter ID: M565C25 Network element name: IP6_OUT_FRAG_OKS

Version: 2.1 NetAct name: IP6_OUT_FRAG_OKS

Description: The number of sent IPv6 datagrams which could be successfully fragmented.

Updated: When an IPv6 datagram, which could be successfully fragmented, is sent.




Operability class:


542 DN04143903




8.5 UDP measurement on IP interface (566/236H)The UDP measurement on IP interface provides statistical information on UDP protocol traffic volume and errors: the number of sent UDP datagrams, received UDP datagrams and erroneous UDP datagrams. As UDP traffic is terminated on Network Processor





Counter ID: M565C26 Network element name: IP6_OUT_FRAG_FAILS

Version: 2.1 NetAct name: IP6_OUT_FRAG_FAILS

Description: The number of sent IPv6 datagrams which could not be successfully fragmented.

Updated: When an IPv6 datagram, which could not be successfully fragmented, is sent.




Operability class:






Counter ID: M565C27 Network element name: IP6_OUT_FRAGREATES

Version: 2.1 NetAct name: IP6_OUT_FRAGREATES

Description: The number of fragments which are created for the sent IPv6 datagrams.

Updated: When an IPv6 datagram has been successfully fragmented.




Operability class:






DN04143903 543



Interface Unit Gigabit Ethernet (NPGE(P)) and Network Processor Interface Unit STM-1 (NPS1 (P)), only NPGE(P) and NPS1(P) can be selected as measured units.

The object of the measurement is an IP interface that is identified with a unit type, a unit index and an IP interface name. The measurement identifier (MID) is 566/236H.

g This measurement is supported by both physical and VLAN IP interfaces with IP addresses.

Counter ID: M566C0 Network element name: IN_DATAGRAMS

Version: 5.1 NetAct name: IN_DATAGRAMS

Description: The number of UDP datagrams received.

Updated: When a UDP datagram is received.




Operability class:






Counter ID: M566C1 Network element name: NO_PORTS

Version: 5.0 NetAct name: NO_PORTS

Description: The number of UDP datagrams for which there is no application at the destination port.

Updated: When a UDP datagram, for which there is no application listening at the destination UDP port, is received by the interface unit.




Operability class:






Counter ID: M566C2 Network element name: IN_ERRORS

544 DN04143903




8.6 IP QoS measurement (567/237H)The IP QoS measurement provides information on the amount of IP packets and bytes transmitted in an NPGE(P) unit, classified by Per Hop Behaviour code used for service differentiation in IP networks.

The object of the measurement is identified with unit type, unit index, IP interface name, and PHB code. The PHB code is one of the following:

• EF = Expedited Forwarding • AF4 = Assured Forwarding Class 4 • AF3 = Assured Forwarding Class 3 • AF2 = Assured Forwarding Class 2 • AF1 = Assured Forwarding Class 1

Version: 5.1 NetAct name: IN_ERRORS

Description: The number of UDP datagrams received with errors.

Updated: When a UDP datagram with errors is received.




Operability class:






Counter ID: M566C3 Network element name: OUT_DATAGRAMS

Version: 5.0 NetAct name: OUT_DATAGRAMS

Description: The number of UDP datagrams locally sent.The datagrams generated by the host processor are not included.

Updated: When a UDP datagram is sent.




Operability class:






DN04143903 545



• BE = Best Effort

g This measurement is not supported for VLAN interfaces but only for such IP-interfaces that have a physical IP-address.

Counter ID: M567C0 Network element name: INGRESS_RECEIVED_PACKETS

Version: 1.0 NetAct name: INGRESS_RECEIVED_PACKETS

Description: The number of IP packets received.

Updated: When an IP packet is received.




Operability class:






Counter ID: M567C1 Network element name: INGRESS_RECEIVED_BYTES

Version: 1.0 NetAct name: INGRESS_RECEIVED_BYTES

Description: The amount of data received in IP packets.

Updated: When an IP packet is received.




Operability class:






Counter ID: M567C2 Network element name: EGRESS_SENT_PACKETS

Version: 3.1 NetAct name: EGRESS_SENT_PACKETS

Description: The number of IP packets sent out from the IP interface. Additionally the counter includes packets that were dropped in the IP packet scheduler.

Updated: When an IP packet is sent out from the IP interface or dropped in the packet scheduler.


546 DN04143903






Operability class:






Counter ID: M567C3 Network element name: EGRESS_SENT_BYTES

Version: 1.1 NetAct name: EGRESS_SENT_BYTES

Description: The amount of data attempted to send out in IP packets. Includes also data that was dropped in the IP packet scheduler.

Updated: When an IP packet is sent to the IP packet scheduler.




Operability class:






Counter ID: M567C4 Network element name: DISCARDED_PACKETS

Version: 3.1 NetAct name: DISCARDED_PACKETS

Description: The number of received IP packets that were discarded and therefore not sent out from the IP interface.

Updated: When an IP packet is discarded.




Operability class:






DN04143903 547



8.7 M3UA association set measurement (661/295H)The MTP3 User Adaptation Layer (M3UA) association set measurement can be used to monitor M3UA traffic. It provides information on traffic throughput and the quality of M3UA connections, as well as on the M3UA layer and M3UA Stream Control Transmis-sion Protocol (SCTP) layer traffic.

M3UA layer counters report on the payload of the SCTP connection. SCTP layer counters can be used to follow the traffic of the SCTP layer used by an M3UA associa-tion. The SCTP layer counters give more accurate information on real load required for sending M3UA traffic through SCTP by including a number of retransmitted SCTP packets and an SCTP header. Unavailability counters can be used for fault monitoring, for example, if the association is in ASP-INACTIVE state.

The object of the measurement is an M3UA association set that is identified with an association set name and an association index. The measurement identifier is 661/295H.

Counter ID: M661C1 Network element name: M3UA_ASSO_SET_UNAVAILABLE_TIME

Version: 7.2 NetAct name: M3UA_ASSO_SET_UNAVAILABLE_TIME

Description: Association set unavailability in seconds. This calculates the cumulative duration of unavail-ability of the association set. The counter is updated with the same value for all associations that belong to the same association set.

Updated: The period of unavailable time begins when the association set becomes unavailable. This means that none of the associations of the association set are in ASP-ACTIVE state. Updating of the counter ends when the state of the association set becomes available. The association set is available if even one association of the association set is in ASP-ACTIVE state.




Operability class:






Counter ID: M661C2 Network element name: M3UA_ASSO_SET_UNAVAILABLE

Version: 7.2 NetAct name: M3UA_ASSO_SET_UNAVAILABLE

Description: The number of times the association set has become unavailable. The counter is updated with the same value for all associations that belong to the same association set.

Updated: The counter is updated every time the association set is unavailable. This means that none of the associations of the association set are in ASP-ACTIVE state.



548 DN04143903





Operability class:






Counter ID: M661C3 Network element name: M3UA_CUMUL_UNAVAILABLE_TIME

Version: 2.1 NetAct name: M3UA_CUMUL_UNAVAILABLE_TIME

Description: Association unavailability in seconds. This calculates cumulative duration of unavailability of a single association.

Updated: The period of unavailable time begins when the state of the association changes from ASP-ACTIVE to something else. Updating of the counter ends when the state of the association becomes ASP-ACTIVE again.




Operability class:






Counter ID: M661C4 Network element name: M3UA_UNAVAILABLE

Version: 7.2 NetAct name: M3UA_UNAVAILABLE

Description: The number of times the association has become unavailable.

Updated: When the state of the association changes back to ASP-ACTIVE.




Operability class:





DN04143903 549




Counter ID: M661C5 Network element name: M3UA_MESSAGES_RECEIVED

Version: 2.1 NetAct name: M3UA_MESSAGES_RECEIVED

Description: The number of received messages on the M3UA association. This includes all the received messages of M3UA.

Updated: When an M3UA message is received.




Operability class:






Counter ID: M661C6 Network element name: M3UA_MESSAGES_SENT

Version: 2.1 NetAct name: M3UA_MESSAGES_SENT

Description: The number of sent messages on the M3UA association. This includes all the sent messages of M3UA.

Updated: When an M3UA message is sent.




Operability class:






Counter ID: M661C7 Network element name: M3UA_OCTETS_RECEIVED

Version: 2.1 NetAct name: M3UA_OCTETS_RECEIVED

550 DN04143903




Description: The number of octets received on the M3UA association. This counter calculates the number of bytes received in M3UA messages. It consist of all the M3UA messages including M3UA header and M3UA payload.

Updated: When an M3UA message is received.




Operability class:






Counter ID: M661C8 Network element name: M3UA_OCTETS_SENT

Version: 2.1 NetAct name: M3UA_OCTETS_SENT

Description: The number of octets sent on the M3UA association. This counter calculates the number of bytes sent in M3UA messages. It consist of all the M3UA messages including M3UA header and M3UA payload.

Updated: When an M3UA message is sent.




Operability class:






Counter ID: M661C9 Network element name: M3UA_SCTP_PACKETS_RECEIVED

Version: 2.1 NetAct name: M3UA_SCTP_PACKETS_RECEIVED

Description: The number of data packets received on SCTP per M3UA association, excluding SCTP control packets.

Updated: When an SCTP data packet is received per M3UA association.



DN04143903 551




Operability class:






Counter ID: M661C10 Network element name: M3UA_SCTP_PACKETS_SENT

Version: 2.1 NetAct name: M3UA_SCTP_PACKETS_SENT

Description: The number of data packets sent on SCTP per M3UA association, excluding SCTP control packets.

Updated: When an SCTP data packet is sent per M3UA association.




Operability class:






Counter ID: M661C11 Network element name: M3UA_SCTP_OCTETS_RECEIVED

Version: 2.1 NetAct name: M3UA_SCTP_OCTETS_RECEIVED

Description: The number of octets received on SCTP per M3UA association. This counter calculates the number of bytes sent in SCTP packets. It consist of all the SCTP packets including SCTP control packets and SCTP header and SCTP payload.

Updated: When an SCTP packet is received per M3UA association.




Operability class:





552 DN04143903





Counter ID: M661C12 Network element name: M3UA_SCTP_OCTETS_SENT

Version: 2.1 NetAct name: M3UA_SCTP_OCTETS_SENT

Description: The number of octets sent on SCTP per M3UA association. This counter calculates the number of bytes sent in SCTP packets. It consist of all the SCTP packets including SCTP control packets and retransmitted packets and SCTP header and SCTP payload.

Updated: When an SCTP packet is sent per M3UA association.




Operability class:






Counter ID: M661C13 Network element name: M3UA_SCTP_PACKETS_RETRANSMIT

Version: 2.1 NetAct name: M3UA_SCTP_PACKETS_RETRANSMIT

Description: The number of packets re-transmitted on SCTP per M3UA association.

Updated: When an SCTP packet is re-transmitted per M3UA association.




Operability class:






Counter ID: M661C14 Network element name: M3UA_SCTP_DUPLICATED_TSN

Version: 2.1 NetAct name: M3UA_SCTP_DUPLICATED_TSN

Description: The number of duplicated TSNs received on SCTP per M3UA association.

DN04143903 553



Updated: When a duplicated TSN is received on SCTP per M3UA association.




Operability class:






Counter ID: M661C15 Network element name: M3UA_ASSO_SET_DURATION_OF_CONG

Version: 6.0 NetAct name: M3UA_ASSO_SET_DURATION_OF_CONG

Description: The duration of association set congestion in milliseconds.

Updated: The period of congestion time begins when the association set becomes congested. Associa-tion set is congested if any association of the association set is in congested. Updating of the counter ends when the congestion of the association set ends.


Unit: Milliseconds Range: Example values:


Operability class:





Used from release: U5.0 EP2/RN7.0


Counter ID: M661C16 Network element name: M3UA_ASSO_SET_CONG_TIMES

Version: 6.0 NetAct name: M3UA_ASSO_SET_CONG_TIMES

Description: The number of times the association set has become congested.

Updated: The counter is updated every time when the association set has been congested. Associa-tion set is congested if any association of the association set is in congested.




Operability class:


554 DN04143903









Counter ID: M661C17 Network element name: M3UA_DURATION_OF_CONGESTION

Version: 6.0 NetAct name: M3UA_DURATION_OF_CONGESTION

Description: The duration of association congestion in milliseconds. This calculates duration of con-gestion of a single association.

Updated: The period of congestion time begins when the association becomes congested. Updating of the counter ends when the congestion of the association ends.


Unit: Milliseconds Range: Example values:


Operability class:







Counter ID: M661C18 Network element name: M3UA_CONGESTION_TIMES

Version: 6.0 NetAct name: M3UA_CONGESTION_TIMES

Description: The number of times the association has become congested.

Updated: The counter is updated every time when the association has been congested.




Operability class:







DN04143903 555



8.8 RNC RTP/RTCP measurement (803/323H)The RNC RTP/RTCP measurement provides information on the RTP and RTCP protocol used in the IP based Iu-CS interface. The measured items are the amount of RTP and RTCP protocol data and jitter of the user data.

The object of the measurement is IP based route identifier.

Counter ID: M803C0 Network element name: REC_RTP_PACKETS

Version: 1.0 NetAct name: REC_RTP_PACKETS

Description: The number of received RTP packets. The actual number of packets can be calculated by multiplying this counter value by 10.

Updated: When an RTP packet is received from the core network.


Unit: 10 packets Range: Example values:


Operability class:

Related to feature:







Counter ID: M803C1 Network element name: REC_RTP_PAYLOAD

Version: 1.0 NetAct name: REC_RTP_PAYLOAD

Description: The RTP payload data received during the measurement interval. Header and padding data is not included.

Updated: When an RTP packet is received from the core network.




Operability class:

Related to feature:







Counter ID: M803C2 Network element name: SENT_RTP_PACKETS

556 DN04143903




Version: 1.0 NetAct name: SENT_RTP_PACKETS

Description: The number of sent RTP packets. The actual number of packets can be calculated by mul-tiplying this counter value by 10.

Updated: When an RTP packet is sent to the core network.


Unit: 10 packets Range: Example values:


Operability class:

Related to feature:







Counter ID: M803C3 Network element name: SENT_RTP_PAYLOAD

Version: 1.0 NetAct name: SENT_RTP_PAYLOAD

Description: The RTP payload data sent during the measurement interval. Header and padding data is not included.

Updated: When an RTP packet is sent to the core network.




Operability class:

Related to feature:







Counter ID: M803C4 Network element name: LOST_RTP_PACKETS

Version: 4.1 NetAct name: LOST_RTP_PACKETS

Description: The number of lost ingress direction RTP data packets that are not received according to the received sequence numbers. This means that either the packet was lost in the Iu-CS transport or the packet arrived too late to the RTP buffer of RNC. Too late arrival can be caused by excessive jitter in the transport path.

Updated: When an RTP packet is detected to be missing.



DN04143903 557




Operability class:

Related to feature:







Counter ID: M803C5 Network element name: SENT_RTCP_PACKETS

Version: 1.2 NetAct name: SENT_RTCP_PACKETS

Description: The number of sent RTCP Sender Reports.

Updated: When an RTCP packet containing Sender Report is sent to the core network.




Operability class:

Related to feature:







Counter ID: M803C6 Network element name: REC_RTCP_PACKETS

Version: 1.2 NetAct name: REC_RTCP_PACKETS

Description: The number of received RTCP Sender Reports.

Updated: When an RTCP packet containing Sender Report is received from the core network.




Operability class:

Related to feature:







558 DN04143903




Counter ID: M803C7 Network element name: RTP_JITTER_CLASS_1

Version: 1.2 NetAct name: RTP_JITTER_CLASS_1

Description: The number of 5 second sampling intervals where the average ingress direction RTP jitter in the Iu-CS interface is below 1 ms.

Updated: The jitter is sampled with 5 second intervals for each RTP connection.




Operability class:

Related to feature:









Description: The number of 5 second sampling intervals where the average ingress direction RTP jitter in the Iu-CS interface is in range 1...2 ms.





Operability class:

Related to feature:












DN04143903 559





Operability class:

Related to feature:














Operability class:

Related to feature:














Operability class:

Related to feature:




560 DN04143903














Operability class:

Related to feature:














Operability class:

Related to feature:









DN04143903 561








Operability class:

Related to feature:














Operability class:

Related to feature:














Operability class:

562 DN04143903




Related to feature:














Operability class:

Related to feature:














Operability class:

Related to feature:







DN04143903 563










Operability class:

Related to feature:














Operability class:

Related to feature:












564 DN04143903






Operability class:

Related to feature:














Operability class:

Related to feature:














Operability class:

Related to feature:





DN04143903 565












Operability class:

Related to feature:














Operability class:

Related to feature:









Description: The number of 5 second sampling intervals where the average ingress direction RTP jitter in the Iu-CS interface is in larger than 55 ms.

566 DN04143903








Operability class:

Related to feature:







Counter ID: M803C27 Network element name: MAX_RTP_JITTER

Version: 1.2 NetAct name: MAX_RTP_JITTER

Description: The maximum ingress direction jitter value within the collected 5 second samples during the measurement interval.





Operability class:

Related to feature:







Counter ID: M803C28 Network element name: LOST_EGRESS_RTP_PACKETS

Version: 1.0 NetAct name: LOST_EGRESS_RTP_PACKETS

Description: The number of lost egress direction RTP data packets that are reported to be missing by MGW using RTCP protocol messages.This counter is supported only if RTCP protocol usage is enabled in the Iu-CS interface using IUCS object parameter RtcpActivation.

Updated: When the RNC receives information from MGW via RTCP messages that egress direction RTP packets are missing.




Operability class:

DN04143903 567



8.9 Ethernet interface performance measurement (564/234H)The Ethernet interface performance measurement provides information on the traffic in the external Ethernet port of the NPGE computer unit and the backplane Ethernet ports of NPGE and NPS1 units.

The object of the measurement is identified by unit type, unit index and the name of the Ethernet interface.

Related to feature:







Counter ID: M564C0 Network element name: ETHER_RX_FRAME

Version: 1.0 NetAct name: ETHER_RX_FRAME

Description: The total number of Ethernet frames received.

Updated: When an Ethernet frame is received.




Operability class:

Related to feature:

RAN 77: RNC Ethernet Physical Interface






Counter ID: M564C1 Network element name: ETHER_RX_KILOBYTE

Version: 1.1 NetAct name: ETHER_RX_KILOBYTE

Description: The total Ethernet layer data volume received.

Updated: When the data is received over Ethernet interface.




Operability class:

Related to feature:



568 DN04143903








Counter ID: M564C2 Network element name: ETHER_RX_MULTICAST_FRAME

Version: 1.0 NetAct name: ETHER_RX_MULTICAST_FRAME

Description: The number of Ethernet frames transmitted with multicast address.

Updated: When an Ethernet multicast frame is received.




Operability class:

Related to feature:







Counter ID: M564C3 Network element name: ETHER_RX_BROADCAST_FRAME

Version: 1.0 NetAct name: ETHER_RX_BROADCAST_FRAME

Description: The number of Ethernet frames transmitted with broadcast address.

Updated: When an Ethernet broadcast frame is received.




Operability class:

Related to feature:







Counter ID: M564C4 Network element name: ETHER_RX_UNICAST_FRAME

Version: 1.0 NetAct name: ETHER_RX_UNICAST_FRAME

Description: The number of Ethernet frames received with physical MAC address.

DN04143903 569



Updated: When an Ethernet frame is received.




Operability class:

Related to feature:







Counter ID: M564C5 Network element name: ETHER_RX_64_FRAME

Version: 1.0 NetAct name: ETHER_RX_64_FRAME

Description: The number of Ethernet frames received with a length of exactly 64 bytes

Updated: When an Ethernet frame with a length of exactly 64 bytes is received.




Operability class:

Related to feature:







Counter ID: M564C6 Network element name: ETHER_RX_65_127_FRAME

Version: 1.0 NetAct name: ETHER_RX_65_127_FRAME

Description: The number of Ethernet frames received with a length between 65 and 127 bytes.

Updated: When an Ethernet frame with a length between 65 and 127 bytes is received.




Operability class:

Related to feature:




570 DN04143903














Operability class:

Related to feature:














Operability class:

Related to feature:











DN04143903 571






Operability class:

Related to feature:







Counter ID: M564C10 Network element name: ETHER_RX_1024_MAX_FRAME

Version: 1.0 NetAct name: ETHER_RX_1024_MAX_FRAME

Description: The number of Ethernet frames received with a length between 1024 and the maximum number of bytes.

Updated: When an Ethernet frame with a length between 1024 and the maximum number of bytes is received.




Operability class:

Related to feature:







Counter ID: M564C11 Network element name: ETHER_RX_FRAME_ALIGMENT_ERR

Version: 1.0 NetAct name: ETHER_RX_FRAME_ALIGMENT_ERR

Description: The number of Ethernet frames that have an error which occurred because the frame does not end on a byte boundary are received.

Updated: When an Ethernet frame that have an error which occurred because the frame does not end on a byte boundary is received.




Operability class:


572 DN04143903








Counter ID: M564C12 Network element name: ETHER_RX_TOO_LONG_FRAME

Version: 1.0 NetAct name: ETHER_RX_TOO_LONG_FRAME

Description: The number of Ethernet frames received with a length greater than the maximum frame size.

Updated: When an Ethernet frame with a length greater than the maximum frame size is received.




Operability class:






Counter ID: M564C13 Network element name: ETHER_RX_TOO_SHORT_FRAME

Version: 1.0 NetAct name: ETHER_RX_TOO_SHORT_FRAME

Description: The number of Ethernet frames received with a length of less than 64 bytes.

Updated: When an Ethernet frame with a length of less than 64 bytes is received.




Operability class:






Counter ID: M564C14 Network element name: ETHER_RX_CRC_ERR

Version: 1.0 NetAct name: ETHER_RX_CRC_ERR

Description: The number of Ethernet frames received that have a CRC error.

Updated: When an Ethernet frame that have a CRC error is received.

DN04143903 573






Operability class:






Counter ID: M564C15 Network element name: ETHER_RX_BUFFER_OVERFLOW

Version: 1.0 NetAct name: ETHER_RX_BUFFER_OVERFLOW

Description: The number of Ethernet frames dropped due to RX buffer overflow.

Updated: When an Ethernet frame is dropped.




Operability class:






Counter ID: M564C16 Network element name: ETHER_RX_VLAN_TAGGED

Version: 2.1 NetAct name: ETHER_RX_VLAN_TAGGED

Description: The number of received packets that are VLAN tagged. This counter is currently not sup-ported.

Updated: The counter is never updated because it is not supported.




Operability class:

Related to feature:

RAN77: RNC Ethernet Physical Interface





574 DN04143903





Counter ID: M564C17 Network element name: ETHER_TX_FRAME

Version: 1.0 NetAct name: ETHER_TX_FRAME

Description: The total number of Ethernet frames transmitted.

Updated: When an Ethernet frame is transmitted.




Operability class:






Counter ID: M564C18 Network element name: ETHER_TX_KILOBYTE

Version: 1.1 NetAct name: ETHER_TX_KILOBYTE

Description: The total Ethernet layer data volume transmitted.

Updated: When the data is transmitted over Ethernet interface.




Operability class:






Counter ID: M564C19 Network element name: ETHER_TX_MULTICAST_FRAME

Version: 1.0 NetAct name: ETHER_TX_MULTICAST_FRAME

Description: The number of Ethernet frames transmitted with multicast address.

Updated: When an Ethernet frame with multicast address is transmitted.




DN04143903 575



Operability class:






Counter ID: M564C20 Network element name: ETHER_TX_BROADCAST_FRAME

Version: 1.0 NetAct name: ETHER_TX_BROADCAST_FRAME

Description: The number of Ethernet frames transmitted with broadcast address.

Updated: When an Ethernet frame with broadcast address is transmitted.




Operability class:






Counter ID: M564C21 Network element name: ETHER_TX_UNICAST_FRAME

Version: 1.0 NetAct name: ETHER_TX_UNICAST_FRAME

Description: The number of Ethernet frames transmitted with physical MAC address.

Updated: When an Ethernet frame physical MAC address is transmitted.




Operability class:






Counter ID: M564C22 Network element name: ETHER_TX_64_FRAME

Version: 1.0 NetAct name: ETHER_TX_64_FRAME

576 DN04143903




Description: The number of Ethernet frames transmitted with a length of exactly 64 bytes.

Updated: When an Ethernet frame with a length of exactly 64 bytes is transmitted.




Operability class:






Counter ID: M564C23 Network element name: ETHER_TX_65_127_FRAME

Version: 1.0 NetAct name: ETHER_TX_65_127_FRAME

Description: The number of Ethernet frames transmitted with a length between 65 and 127 bytes.

Updated: When an Ethernet frame with a length between 65 and 127 bytes is transmitted.




Operability class:













Operability class:





DN04143903 577











Operability class:













Operability class:






Counter ID: M564C27 Network element name: ETHER_TX_1024_MAX_FRAME

Version: 1.0 NetAct name: ETHER_TX_1024_MAX_FRAME

Description: The number of Ethernet frames transmitted with a length between 1024 and the maximum number of bytes.

Updated: When an Ethernet frame with a length between 1024 and the maximum number of bytes is transmitted.



578 DN04143903





Operability class:






Counter ID: M564C28 Network element name: ETHER_TX_ABORT_FOR_COLL

Version: 5.1 NetAct name: ETHER_TX_ABORT_FOR_COLL


Updated: Never




Operability class:

Related to feature:







Counter ID: M564C29 Network element name: ETHER_TX_LATE_COLL

Version: 5.1 NetAct name: ETHER_TX_LATE_COLL


Updated: Never




Operability class:

Related to feature:







DN04143903 579



8.10 IP TWAMP Statistics (569/239H)IP TWAMP Statistics measurement introduces means for actively measuring and super-vising the IP network conditions through the mobile backhaul between two points. The counters provide information about round trip time and packet loss ratio.

M569 produces data when the RNC works as a TWAMP sender, sending probing packets to another network element works as a responder. The responder is, for example, FlexiBTS. The responder functionality is supported by feature RAN1900: IP Transport Network Measurement.

Activating the M569 measurement in the RNC does not start data production. Addition-ally, TWAMP sessions need to be created using sCLI/MML commands or IP plan down-load. For more information, see Activating RAN2255: IP Transport Network Measurement Initiated from RNC and Flexi Direct BTS.

The measurement object of M569, visible in the RNW Measurement Presentation GUI, is the TWAMP session identifier. Additionally, when sending measurement data to NetAct, the OMS adds more object levels. These object levels are based on the TWAMP session configuration received by OMS from the RNC by IP-plan upload. The additional object levels are represented in Table 21.

Counter ID: M564C30 Network element name: ETHER_DROP_EVENTS

Version: 4.2 NetAct name: ETHER_DROP_EVENTS

Description: The number of packet-drop events caused either by a CRC error or too long or short Ethernet frame.

Updated: When an Ethernet frame is dropped.




Operability class:

Related to feature:







Object identifier Description

TWsession TWAMP session ID

IP-plan parameter: TWAMPS-ipSender-SessId

SRCIP Source IP address

IP-plan parameter: TWAMPS-srcIpAddr

Table 21 Additional object levels

580 DN04143903




g OMS performs IP-plan upload periodically and therefore, if TWAMP session parameters are changed, it may take up to one hour before the updated parameters are visible in the measurement object. If the OMS is not able to upload the IP-plan or cannot find TWAMP session information from the plan, object UNKNOWN is used in the additional object levels.

DSTIP/DSTPORT Destination IP address and UDP port

IP-plan parameters: TWAMPS-destIpAddr, TWAMPS-destIpPort

DSCP/PKTLEN DSCP and packet length

IP-plan parameters: TWAMPS-dscpVal, TAWMPS-lenOfPacket

Object identifier Description

Table 21 Additional object levels (Cont.)

Counter ID: M569C0 Network element name: TWAMP_RTT_AVERAGE

Version: 1.0 NetAct name: TWAMP_RTT_AVERAGE

Description: The average round-trip-time calculated over the measurement interval.

Updated: The average round-trip-time is calculated at the end of measurement interval as an average over all RTT values measured during the interval.

Logical type: Average Trigger type: Sample Sampling interval:

Unit: microseconds Range: Example values:


Operability class:

Related to feature:

RAN2255: IP Transport Network Measurement Initiated from RNC and I-BTS






Counter ID: M569C1 Network element name: TWAMP_RTT_MIN

Version: 1.0 NetAct name: TWAMP_RTT_MIN

Description: The minimum round-trip-time during the measurement interval.

Updated: The round-trip-time is calculated every time when TWAMP response packet is received.




Operability class:

DN04143903 581



Related to feature:







Counter ID: M569C2 Network element name: TWAMP_RTT_MAX

Version: 1.0 NetAct name: TWAMP_RTT_MAX

Description: The maximum round-trip-time during the measurement interval. Request packets for which no response was received until timeout expired, are not included in the maximum value calculation.

Updated: The round-trip-time is calculated every time when TWAMP response packet is received.




Operability class:

Related to feature:







Counter ID: M569C3 Network element name: TWAMP_REQ_PACKETS_SENT

Version: 1.0 NetAct name: TWAMP_REQ_PACKETS_SENT

Description: The number of sent TWAMP measurement request packets.

Updated: When the RNC works as a TWAMP sender and sends TWAMP measurement request packet.




Operability class:

Related to feature:






582 DN04143903





Counter ID: M569C4 Network element name: TWAMP_PACKETS_LOST

Version: 1.0 NetAct name: TWAMP_PACKETS_LOST

Description: The number of sent TWAMP measurement request packets for which no response was received until the timeout expired. The timeout is the same as packet sending interval, that is either 1 second or 100 milliseconds depending on the operator configured TWAMP session parameter.

Updated: When the RNC works as a TWAMP sender and does not receive response to TWAMP mea-surement request packet and timeout expires.




Operability class:

Related to feature:







DN04143903 583

RNC Counters - Transport and HW Part Computing unit measurements

Id:0900d805809a80e9Confidential

9 Computing unit measurementsThe computing unit measurements describe the performance and load of RNC internal computer units.

9.1 Availability performance measurement (608/260H)Availability performance measurement collects information about restarts of computer units and process families in IPA2800. It also collects information about state changes of computer units. From the received information, it calculates the time the unit has been out of service.



Counter ID: M608C0 Network element name: UNIT_RESTARTS

Version: 5.1 NetAct name: UNIT_RESTARTS

Description: The number of computer unit restarts.

Updated: When a unit is restarted.










Counter ID: M608C1 Network element name: ADMIN_RESTARTS

Version: 5.1 NetAct name: ADMIN_RESTARTS

Description: The number of computer unit restarts which are made by the user with MML commands.

Updated: When a unit is restarted with MML commands.









584 DN04143903



Computing unit measurements


Counter ID: M608C2 Network element name: DUPLEX_RESTARTS

Version: 5.1 NetAct name: DUPLEX_RESTARTS

Description: The number of duplicated computer unit restarts, when both units have been restarted at the same time. The value is updated in a field of the unit that is the working unit after the restart.

Updated: When duplicated units are both restarted.










Counter ID: M608C3 Network element name: DUPLEX_DISCONNECT_TIME

Version: 5.2 NetAct name: DUPLEX_DISCONNECT_TIME

Description: This counter shows in seconds the disconnect time of duplicated computer units when both units are not in WO-EX or SP-EX state.

Updated: The time starts when both units are changed to another state than WO-EX or SP-EX state. The time ends when the working unit returns to WO-EX state. The time is updated only for an active unit.










Counter ID: M608C4 Network element name: DISCONNECT_TIME

Version: 5.2 NetAct name: DISCONNECT_TIME

DN04143903 585



9.2 Unit load measurement (592/250H)The unit load measurement is used to collect information about the processor load in computer units.

The unit load measurement provides information about the average and peak load of both DMX and Chorus computer units. The information also includes the time of the peak load in the unit. If the load is too high, some functionality should be replaced to other units or new plug-in units should be added.

The object is a computer unit that is identified by unit type and index and the measure-ment ID is 592/250H.

Description: This counter shows in seconds the disconnect time when the computer unit is not in WO-EX or SP-EX state.

Updated: The time starts when a unit is not in WO-EX or SP-EX state, and ends when the unit is in WO-EX or SP-EX state. If the unit is not in WO-EX or SP-EX state when the measurement report is generated, the time between the starting time and the result accumulation end time is updated. If the unit is not in WO-EX or SP-EX state for the whole result accumulation period, the same time as the results accumu-lation period is updated.










Counter ID: M608C5 Network element name: FAMILY_RESTARTS

Version: 5.1 NetAct name: FAMILY_RESTARTS

Description: The total number of process family restarts in the computer unit.

Updated: When a process family is restarted. The counter is not updated when the complete unit restart takes place.










586 DN04143903




Counter ID: M592C0 Network element name: AVERAGE_LOAD

Version: 8.2 NetAct name: AVERAGE_LOAD

Description: The average load for a monitored computer unit. The value is the arithmetical average of samples taken from the processor load. The length of the sampling interval is 4 seconds.

Updated: The sample of the load rate is updated every 4 seconds. The average value is calculated at the end of measurement period.

Logical type: Average Trigger type: Sample Sampling interval: 4 seconds

Unit: % Range: 0-100 Example values: 50








Counter ID: M592C1 Network element name: PEAK_LOAD

Version: 8.2 NetAct name: PEAK_LOAD

Description: The peak load of the monitored computer unit. This is the highest recorded value of the processor load during a measurement period. The length of the sampling interval is 4 seconds.

Updated: When the sample of the load rate is the highest. Checked every 4 seconds.

Logical type: Max Trigger type: Sample Sampling interval: 4 seconds

Unit: % Range: 0-100 Example values: 50








Counter ID: M592C2 Network element name: PEAK_LOAD_DATE

Version: 8.3 NetAct name: PEAK_LOAD_DATE

DN04143903 587



9.3 WAC overload control measurement (594/252H)This measurement reports the performance of WAC (Window Access Control) mecha-nism, which is used to limit the number of simultaneous AAL2 or RRC type resource res-ervations inside RNC. The measurement indicates if WAC rejects the set up of new radio or transport layer connections. WAC is used for AAL2 connection requests only when the drift RNC receives AAL2 establishment request (ERQ) from the serving RNC.

The object of the measurement is WAC gate type that is identified by unit type/unit index/WAC gate type. The measurement identifier is 594/252H.

Description: The date of the peak load. The value is stored as an integer number in such format that e.g. 23rd December 2008 would produce value 23122008.

Updated: When the sample of the load rate is the highest.


Unit: date Range: N/A Example values: 23122008







Used from release: U1/RN1 Definition updated in release: RN4.0

Counter ID: M592C3 Network element name: PEAK_LOAD_TIME

Version: 8.3 NetAct name: PEAK_LOAD_TIME

Description: The time of the peak load. The time indicates the sampling moment that followed the observation period with the highest load rate. At unit restart when there is no load, which means that the peak load is zero, the time is the unit restart time. Otherwise, when the peak load is zero, the time shows when the peak load was last observed.

The value is stored as an integer number in such format that e.g. 12:30:59 would produce value 123059.

Updated: When the sample of the load rate is the highest.


Unit: time Range: N/A Example values: 123059







Used from release: U1/RN1 Definition updated in release: RN4.0

588 DN04143903





Counter ID: M594C0 Network element name: WAC_GATE_REQ_TOTAL

Version: 3.1 NetAct name: WAC_GATE_REQ_TOTAL

Description: The total number of WAC (Windows Access Control) Gate requests that has been released and rejected. When an entity wants to establish some kind of a signalling connection, such as an AAL2 signalling connection, it should firstly ask permission from WAC Gate. If the maximum number of accesses is reached, the request is rejected or put into a queue, waiting for resources to be released by other. With WAC in place, it is possible to protect system resources and prevent overload situations.

Updated: When a resource request is released or rejected in WAC Gate, this counter will be updated.





Related to feature:







Counter ID: M594C1 Network element name: WAC_GATE_REQ_TOTAL_REJ

Version: 3.1 NetAct name: WAC_GATE_REQ_TOTAL_REJ

Description: The total number of rejected WAC (Windows Access Control) Gate requests. When an entity wants to establish some kind of a signalling connection, such as an AAL2 signalling connection, it should first ask permission from WAC Gate. If the maximum number of accesses is reached, the request will be rejected or put into a queue, waiting for resources to be released. With WAC in place, it is possible to protect system resources and prevent overload situations.

Updated: When a resource request is rejected in WAC Gate.





Related to feature:







DN04143903 589

RNC Counters - Transport and HW Part DSP resource measurements


10 DSP resource measurements

10.1 DSP service statistics measurement (609/261H)The DSP service statistics measurement provides information on the resource alloca-tion for each DSP service type. This measurement can be used, for example, to evaluate the number of simultaneous HSDPA users in RNC level.

The object of the measurement is one of the DSP service names presented in the table DSP service names used in M609 measurement.

Service name Description

AMR ATM based Iu-interface real time speech service.

CCH Common channel service. One CCH service is allocated per cell, but when HS-FACH feature is enabled then two CCH services are allocated.

HSCCH HSDPA common channel service.

ALLHSDPA Sum of all HSDPA services. Includes both HSDPA NRT and HSDPA RT. HSUPA call does not update counters for this object even if it uses HSDPA in downlink.

HSDPANR HSDPA NRT service. HSUPA call does not update counters for this object even if it uses HSDPA in downlink.

HSDPART HSDPA RT service. HSUPA call does not update counters for this object even if it uses HSDPA in downlink.

HS16H HSDPA NRT 16 kbps uplink return channel, high HS-DSCH peak rate.

HS16L HSDPA NRT 16 kbps uplink return channel, low HS-DSCH peak rate.







HS16ALL The total number of HSDPA 16 kbps return channel users, including both NRT and RT.




HSPASWI HSUPA and HSDPA service used temporarily during channel type switching. Includes both NRT and RT.

ALLHSUPA Sum of all HSUPA services. Includes both HSUPA NRT and HSUPA RT.

HSUPANR HSUPA NRT service.

Table 22 DSP service names used in M609 measurement

590 DN04143903



DSP resource measurements

HSUPART HSUPA RT service using 10 ms TTI.

HSUPART2 HSUPA RT service using 2 ms TTI.

ALLHSPA Sum of all HSDPA and HSUPA services, including both RT and NRT.

IPIUAMR IP based Iu-interface real time speech service.

Note: In case of a CS-over-HSPA call and the IP-based Iu-CS interface, the M609C2 DSP_SERVICE_SUCC_RES_ALLOC counter is updated twice for IPIUAMR object when one call is established. This is because of the DSP resource reservation principle.

IPIURTCS IP based Iu-interface real time circuit switched data service.

NRTPSR99 Rel99 non real time packet switched data service, including both Rel99 DCH and Cell_FACH user plane. Does not include HSDPA uplink return channel.

RTCSDATA ATM-based Iu-interface real time circuit switched data service.

RTHSPASW Real-time HSUPA and HSDPA service used temporarily during channel type switching.

RTPSR99 Rel99 real time packed switched data service. Does not include HSDPA uplink return channel.

SL Signalling link service.

PSCONV Not supported, counters always remain zero.

Service name Description

Table 22 DSP service names used in M609 measurement (Cont.)

Counter ID: M609C0 Network element name: DSP_SERVICE_CURR_RES_ALLOC

Version: 1.0 NetAct name: DSP_SERVICE_CURR_RES_ALLOC

Description: The current number of resources allocated for a specific DSP service type.

Updated: When the measurement period ends.




Operability class:






Counter ID: M609C1 Network element name: DSP_SERVICE_PEAK_RES_ALLOC

Version: 1.0 NetAct name: DSP_SERVICE_PEAK_RES_ALLOC

Description: The peak number of resources allocated for a specific DSP service type.

DN04143903 591







Operability class:






Counter ID: M609C2 Network element name: DSP_SERVICE_SUCC_RES_ALLOC

Version: 1.0 NetAct name: DSP_SERVICE_SUCC_RES_ALLOC

Description: The total cumulative number of the resources allocated for a specific DSP service type.

Updated: When the DSP resource is successfully allocated.




Operability class:






Counter ID: M609C3 Network element name: DSP_SERVICE_FAIL_RES_ALLOC

Version: 1.0 NetAct name: DSP_SERVICE_FAIL_RES_ALLOC

Description: The number of DSP resource allocation failures.

Updated: When the DSP resource allocation fails.




Operability class:




592 DN04143903




10.2 DSP state changes measurement (612/264H)The DSP state changes measurement counts the number of essential DSP restarts caused by the system or the operator. The measurement counts DSP internal state changes from WO-RE to TE or from WO-EX to TE. Note that the DSP internal states (WO-RE, WO-EX, and TE) are not equal to the external states (WO, BL, TE, and SE). The measurement can be used, for example, to find out which DSP is faulty.

The object of the measurement is a Data and Macro Diversity Processor Group (DMPG) unit that is identified with a unit type and a unit index. The measurement identifier (MID) is 612/ 264H.



Counter ID: M609C4 Network element name: DSP_SERVICE_FAIL_RES_MODIFY

Version: 1.0 NetAct name: DSP_SERVICE_FAIL_RES_MODIFY

Description: The number of DSP resource modification failures.

Updated: When the DSP resource modification fails.




Operability class:






Counter ID: M612C0 Network element name: RESTART_SYS

Version: 2.1 NetAct name: RESTART_SYS

Description: The number of times a DSP is restarted by the system.

Updated: When a DSP is restarted by the system.




Operability class:




DN04143903 593



10.3 DSP resource utilization measurement (615/267H)The DSP resource utilization measurement provides statistical information on success-ful and failed resource allocations, and resource availability level in the network element, measured on service pool level. Peaks are evaluated by measuring the lowest available capacity during a reporting period, and the average counters give more accurate infor-mation on the usage of reserved DSP services in the network element. The measure-ment data can be used to follow the service volume trends, to analyze faults, and to plan the hardware configuration.

The object of the measurement is a DSP service pool that is identified with a service pool name. The table DSP service pool names used in M615 measurement describes the meaning of each pool.



Counter ID: M612C1 Network element name: RESTART_USER

Version: 2.1 NetAct name: RESTART_USER

Description: The number of times a DSP is restarted by a command operator.

Updated: When a DSP is restarted by a command operator.




Operability class:






Pool name Description

DCH1 DCH DSPs in CDSP-C DMPGs assigned to DCH DMPG setup.

DCH2 DCH DSPs in CDSP-C DMPGs assigned to HS DMPG setup.

HSPA HSPA DSPs in CDSP-C DMPGs assigned HS DMPG setup.

HSPA2 Overbooking DSP pool for HSPA in CDSP-C.

CCH CCH DSPs in CDSP-DH DMPGs.

DCH_HS DCH_HS DSPs in CDSP-DH DMPGs.

CCH_REP CCH DSPs in CDSP-C replacement CDSP-DH DMPGs (DCH DMPG setup).

DCH_REP DCH DSPs in CDSP-C replacement CDSP-DH DMPGs (DCH DMPG setup).

Table 23 DSP service pool names used in M615 measurement

594 DN04143903




DCH_HS_R DCH_HS DSPs in CDSP-C replacement CDSP-DH DMPGs (HS DMPG setup).

HS_DCH HS_DCH DSPs in CDSP-DH DMPGs.

FEA_UPGR DSPs in feature upgrade CDSP-DH DMPGs.

DSP_POOL CDSP-DH (and feature upgrade CDSP-DH) DMPGs DMPG capacity

DCH_DMPG DMPG capacity in CDSP-C (and replacement CDSP-DH) DMPGs in DCH DMPG setup.

HS_DMPG DMPG capacity in CDSP-C (and replacement CDSP-DH) DMPGs in HS DMPG setup.

HS2_DMPG Overbooking DMPG-setup for HSPA in CDSP-C.

HS_CCH HS-FACH pool.

RNC This object is an RNC-wide indicator of the DMCU resource availability across all service pools. This indicator can be used to estimate how many more calls can be carried by the RNC, if the current proportions of different radio bearers remain the same. Only counters M615C0 AVAILABLE_CAPA_ON_NE and M615C1 LOWEST_CAP_ON_NE are updated for this object, the other counters show zero value.

Pool name Description

Table 23 DSP service pool names used in M615 measurement (Cont.)

Counter ID: M615C0 Network element name: AVAILABLE_CAP_ON_NE

Version: 2.1 NetAct name: AVAILABLE_CAP_ON_NE

Description: The percentage of resources available in a service pool (or the total percentage of available shared TPG resources in the MGW).

Updated: When the value of available capacity changes.


Unit: % Range: Example values:


Operability class:






Counter ID: M615C1 Network element name: LOWEST_CAP_ON_NE

Version: 3.2 NetAct name: LOWEST_CAP_ON_NE

Description: The lowest measured percentage of resources available in a service pool (or the lowest measured percentage of total shared TPG resources in the MGW).

Updated: The resource status is checked every time when a new service request arrives or a service is released.

DN04143903 595






Operability class:






Counter ID: M615C2 Network element name: CURR_RES_ALLOC_ON_NE

Version: 9.1 NetAct name: CURR_RES_ALLOC_ON_NE

Description: The current number of resources allocated from a service pool at the moment of measure-ment data collection.

Updated: When a service is allocated or a service is released.




Operability class:






Counter ID: M615C3 Network element name: PEAK_RES_ALLOC_ON_NE

Version: 9.1 NetAct name: PEAK_RES_ALLOC_ON_NE

Description: The peak number of resources allocated from a service pool.

Updated: When a service is allocated and current number of services exceeds peak value.




Operability class:





596 DN04143903





Counter ID: M615C4 Network element name: SUCC_RES_ALLOC_ON_NE

Version: 9.1 NetAct name: SUCC_RES_ALLOC_ON_NE

Description: The total cumulative number of the resources allocated from a service pool.

Updated: When a service is allocated.




Operability class:






Counter ID: M615C5 Network element name: FAIL_ALLOC_DSP_ON_NE

Version: 2.1 NetAct name: FAIL_ALLOC_DSP_ON_NE

Description: The number of times resource allocation failed due to lack of DSP resources in a service pool.

Updated: When a request fails because the DSP is busy.




Operability class:






Counter ID: M615C6 Network element name: FAIL_ALLOC_PPC_ON_NE

Version: 2.1 NetAct name: FAIL_ALLOC_PPC_ON_NE

Description: The number of times resource allocation failed due to lack of shared TPG resources.

Updated: When a request fails because the PPC is busy.

DN04143903 597






Operability class:






Counter ID: M615C7 Network element name: FAIL_MODIFY_ON_NE

Version: 2.1 NetAct name: FAIL_MODIFY_ON_NE

Description: The number of times modification of a resource failed due to lack of DSP/TPG resources.

Updated: When a Modify request fails.




Operability class:






Counter ID: M615C8 Network element name: SER_POOL_OVERFLOW_ON_NE

Version: 2.1 NetAct name: SER_POOL_OVERFLOW_ON_NE

Description: The number of times a resource was allocated from a secondary pool instead of the primary pool. This can mean either that the primary pool was full or that it was more optimal from the resource consumption point-of-view to allocate the resource from another pool.

Updated: When a service pool overflows.




Operability class:




598 DN04143903




10.4 DSP load measurement (617/269H)The DSP load measurement provides information on DSP load such as memory usage, CPU load (in percentage), and the number of active processes. This information can be used, for example, to check the load balance of each Data and Macro Diversity Proces-sor Group (DMPG) unit and is especially useful in troubleshooting situations in a live network.

The object of the measurement is a DMPG unit that is identified with a unit type and a unit index. The measurement identifier (MID) is 617/269H.



Counter ID: M617C0 Network element name: PROC_NUM_AVG

Version: 2.1 NetAct name: PROC_NUM_AVG

Description: The average number of application processes.


Logical type: Average Trigger type: Event Sampling interval:



Operability class:






Counter ID: M617C1 Network element name: CPU_LOAD_AVG

Version: 6.2 NetAct name: CPU_LOAD_AVG

Description: The average CPU load value of the DSPs controlled by the reporting DMPG/TPG unit. The load is sampled at four second intervals and each sample represents a 100 millisec-ond load measuring window. This counter shows the average of the sampled values.


Logical type: Average Trigger type: Event Sampling interval: 4 s



Operability class:




DN04143903 599




Used from release: RN4.0/U4.0


Counter ID: M617C2 Network element name: MEM_USE_INTER_AVG

Version: 2.1 NetAct name: MEM_USE_INTER_AVG

Description: The average value of internal memory usage.





Operability class:






Counter ID: M617C3 Network element name: MEM_USE_EXTER_AVG

Version: 2.1 NetAct name: MEM_USE_EXTER_AVG

Description: The average value of external memory usage.





Operability class:






Counter ID: M617C4 Network element name: PROC_NUM_MAX

Version: 2.1 NetAct name: PROC_NUM_MAX

Description: The maximum number of application processes.

600 DN04143903








Operability class:






Counter ID: M617C5 Network element name: CPU_LOAD_MAX_PROC_NUM

Version: 2.1 NetAct name: CPU_LOAD_MAX_PROC_NUM

Description: The CPU load value when a maximum number of applications is running in the DSP.

Updated: When the number of application processes changes.




Operability class:






Counter ID: M617C6 Network element name: MEM_USE_INTER_MAX_PROC_NUM

Version: 2.1 NetAct name: MEM_USE_INTER_MAX_PROC_NUM

Description: The internal memory usage value when a maximum number of applications is running in the DSP.





Operability class:



DN04143903 601






Counter ID: M617C7 Network element name: MEM_USE_EXTER_MAX_PROC_NUM

Version: 2.1 NetAct name: MEM_USE_EXTER_MAX_PROC_NUM

Description: The external memory usage value when a maximum number of applications is running in the DSP.





Operability class:






Counter ID: M617C8 Network element name: CPU_LOAD_MAX

Version: 7.2 NetAct name: CPU_LOAD_MAX

Description: The maximum CPU load value of the DSPs controlled by the reporting DMPG/TPG unit. The load is sampled with four second intervals and each sample represents a 100 millisecond load measuring window. This counter shows the maximum of the sampled values.


Logical type: Max Trigger type: Event Sampling interval: 4 s



Operability class:





Used from release: RN4.0/U4.0


602 DN04143903




Counter ID: M617C9 Network element name: PROC_NUM_MAX_CPU_LOAD

Version: 2.1 NetAct name: PROC_NUM_MAX_CPU_LOAD

Description: The number of application processes at the time of maximum CPU load.





Operability class:






Counter ID: M617C10 Network element name: MEM_USE_INTER_MAX_CPU_LOAD

Version: 2.1 NetAct name: MEM_USE_INTER_MAX_CPU_LOAD

Description: The internal memory usage value at the time of maximum CPU load.





Operability class:






Counter ID: M617C11 Network element name: MEM_USE_EXTER_MAX_CPU_LOAD

Version: 2.1 NetAct name: MEM_USE_EXTER_MAX_CPU_LOAD

Description: The external memory usage value at the time of maximum CPU load.



DN04143903 603





Operability class:






Counter ID: M617C12 Network element name: MEM_USE_INTER_MAX

Version: 2.1 NetAct name: MEM_USE_INTER_MAX

Description: The maximum value of internal memory usage.





Operability class:






Counter ID: M617C13 Network element name: PROC_NUM_MAX_MEM_USE_INTER

Version: 2.1 NetAct name: PROC_NUM_MAX_MEM_USE_INTER

Description: The number of application processes at the time of maximum internal memory usage.





Operability class:






604 DN04143903




Counter ID: M617C14 Network element name: CPU_LOAD_MAX_MEM_USE_INTER

Version: 2.1 NetAct name: CPU_LOAD_MAX_MEM_USE_INTER

Description: The CPU load value at the time of maximum internal memory usage.





Operability class:






Counter ID: M617C15 Network element name: MEM_USE_EXTER_MAX_MEM_USE_INT

Version: 2.1 NetAct name: MEM_USE_EXTER_MAX_MEM_USE_INT

Description: The external memory usage value at the time of maximum internal memory usage.





Operability class:






Counter ID: M617C16 Network element name: MEM_USE_EXTER_MAX

Version: 2.1 NetAct name: MEM_USE_EXTER_MAX

Description: The maximum value of external memory usage.



DN04143903 605





Operability class:






Counter ID: M617C17 Network element name: PROC_NUM_MAX_MEM_USE_EXTER

Version: 2.1 NetAct name: PROC_NUM_MAX_MEM_USE_EXTER

Description: The number of application processes at the time of maximum external memory usage.





Operability class:






Counter ID: M617C18 Network element name: CPU_LOAD_MAX_MEM_USE_EXTER

Version: 2.2 NetAct name: CPU_LOAD_MAX_MEM_USE_EXTER

Description: The CPU load value at the time of maximum external memory usage.





Operability class:





606 DN04143903





Counter ID: M617C19 Network element name: MEM_USE_INTER_MAX_MEM_USE_EXT

Version: 2.1 NetAct name: MEM_USE_INTER_MAX_MEM_USE_EXT

Description: The internal memory usage value at the time of maximum external memory usage.





Operability class:






DN04143903 607

RNC Counters - Transport and HW Part Multicontroller RNC measurements

Id:0900d805809a80ebConfidential

11 Multicontroller RNC measurementsThis section describes measurements specific for the mcRNC.

11.1 Measurement: Logical Resource Usage (M610)The Logical Resource Usage measurement provides information about the mcRNC filling level from the user plane resource point of view.

The object of this measurement is the up type. It refers to the user plane processing pools. The following objects are created:

• up_type-CSUP: Cell specific services user plane processing pool • up_type-USUP: UE specific user plane processing pool

Counter ID: M610C0 Network element name: DSP_RES_AVER_USAGE_PERCENT

Version: 3.1 NetAct name: DSP_RES_AVER_USAGE_PERCENT

Description: The average resource usage percentage during the measurement inter-val.

Updated: The average value is calculated in the end of measurement interval.

Logical type: Average Trigger type: Sample Sampling interval:



Operability class:





Used from release: Definition updated in release:

Counter ID: M610C1 Network element name: DSP_RES_MAX_USAGE_PERCENT

Version: 1.0 NetAct name: DSP_RES_MAX_USAGE_PERCENT

Description: The maximum resource usage percentage during the measurement interval.

Updated: The resource status is checked every time when a new service request arrivesor a service is released.




Operability class:

608 DN04143903



Multicontroller RNC measurements

11.2 Measurement: CPU Usage Core Level (M2002)The CPU Usage Core Level measurement provides information about the CPU load of the mcRNC separately for each processor core. The object of this measurement is FPNODE (computing node) + FPCPU (processor core). The statistics are reported both for control and user plane processor cores. The following table presents the available FPNODE objects:






Counter ID: M610C2 Network element name: DSP_RES_MIN_USAGE_PERCENT

Version: 1.0 NetAct name: DSP_RES_MIN_USAGE_PERCENT

Description: The minimum resource usage percentage during the measurement inter-val.





Operability class:






FPNODE Description Operating system

CFPU Centralized functions pro-cessing unit that handles O&M, and centralized telecom functionality.

Linux

CSPU Cell specific control plane functional unit.

Linux

CSUP Cell specific user plane functional unit.

Simple Executive

Table 24 Available FPNODE objects

DN04143903 609



EIPU External Interface Process-ing Unit, the CPU cores running on Linux.

Linux

EITP External Interface Trans-port Plane, the CPU cores of EIPU processing unit running on Simple Execu-tive.

Simple Executive

USPU UE specific control plane functional unit.

Linux

USSR Transport termination CPU core in the CFPU unit.

Simple Executive

USUP UE specific user plane functional unit.

Simple Executive

Counter ID: M2002C3 Network element name: Minimum CPU Usage

Version: 1.0 NetAct name: MIN_CPU_USAGE_CORE

Description: The minimum CPU usage value sampled during the measurement inter-val.

Updated: CPU usage is sampled periodically.

Logical type: Min Trigger type: Sampling interval: 30 s



Operability class:






Counter ID: M2002C4 Network element name: Maximum CPU Usage

Version: 1.0 NetAct name: MAX_CPU_USAGE_CORE

Description: The maximum CPU usage value sampled during the measurement inter-val.


Logical type: Max Trigger type: Sampling interval: 30 s


FPNODE Description Operating system

Table 24 Available FPNODE objects (Cont.)

610 DN04143903




11.3 Measurement: Networking Logical (M2004)The Networking Logical measurement provides statistics about logical network inter-faces of the mcRNC. The object of the measurement is FPNODE (computing node) + FPIFC (interface-ID).

The measured interface can be one of the following:

• Physical external Ethernet interface of the mcRNC, for example, ethsfp22. This works so that the external interface of the mcRNC Ethernet switch is mapped with internal VLAN to an Ethernet interface seen by the processing nodes. M2004 measures the interface seen by the node.

• VLAN interface • Internal interface within the mcRNC box (for example xaui0) • Ethernet link aggregation interface. When the Ethernet link aggregation is used, it is

not possible to measure separately the physical interfaces that belong to the aggre-gation group, but only the total traffic carried by the aggregation group.

When interfaces are stacked so that VLAN is built on top of a physical Ethernet interface, the counters of the physical interface show both untagged Ethernet frames carried through it as well as VLAN tagged frames. Because of this, the sum of VLAN interfaces


Operability class:






Counter ID: M2002C5 Network element name: Average CPU Usage

Version: 1.0 NetAct name: AVG_CPU_USAGE_CORE

Description: The average CPU usage value during the measurement interval.


Logical type: Average Trigger type: Sampling interval: 30 s



Operability class:






DN04143903 611



and the underlying physical interface counters does not tell about the total data amount but shows more than the actual traffic (as a result of double-counting).

To report the RNC-level total Ethernet traffic, the sum of ethsfp interfaces and possible Ethernet link aggregation interfaces is calculated.

The counters measuring the amount of received and transferred octets include also the VLAN header used in the internal transport between the Octeon nodes and the mcRNC Ethernet switch. These header bytes are not transferred in the mcRNC external inter-faces because the mcRNC switch removes the internal VLAN header.

Counter ID: M2004C1 Network element name: Received Ethernet Packets

Version: 1.0 NetAct name: RECV_PACKETS

Description: The number of packets received by the logical interface.

Updated: When a packet is received on the logical interface.




Operability class:






Counter ID: M2004C2 Network element name: Received Ethernet Octets

Version: 1.0 NetAct name: RECV_OCTETS

Description: The number of octets received by the logical interface.

Updated: When a packet is received on the logical interface.




Operability class:






Counter ID: M2004C3 Network element name: Received Ethernet Drops

612 DN04143903




Version: 1.0 NetAct name: RECV_DROPS

Description: The number of received packets dropped.

Updated: When a packet received by the logical interface is dropped.




Operability class:






Counter ID: M2004C4 Network element name: Received Ethernet Errors

Version: 1.0 NetAct name: RECV_ERRORS

Description: The number of erroneous packets received by the logical interface.

Updated: When an erroneous packet is received on the logical interface.




Operability class:






Counter ID: M2004C5 Network element name: Transmitted Ethernet Packets

Version: 1.0 NetAct name: TRANSMIT_PACKETS

Description: The number of packets transmitted by the logical interface.

Updated: When a packet is transmitted on the logical interface.




Operability class:


DN04143903 613







Counter ID: M2004C6 Network element name: Transmitted Ethernet Octets

Version: 1.0 NetAct name: TRANSMIT_OCTETS

Description: The number of octets transmitted by the logical interface.

Updated: When a packet is transmitted on the logical interface.




Operability class:






Counter ID: M2004C7 Network element name: Transmitted Ethernet Drops

Version: 1.0 NetAct name: TRANSMIT_DROPS

Description: The number of packet transmissions dropped by the logical interface.

Updated: When a packet to be transmitted by the logical interface is dropped.




Operability class:






Counter ID: M2004C8 Network element name: Transmitted Ethernet Errors

Version: 1.0 NetAct name: TRANSMIT_ERRORS

614 DN04143903




11.4 Measurement: CPU Usage Node Level (M2007)The CPU Usage Node Level measurement provides information about the CPU load of the mcRNC on the node level averaged over all processor cores under the node that run the Linux operating system.

The object of this measurement is FPNODE (computing node), for example, CSPU-0. The FPNODE objects are the same as in measurement M2002 (see Table 24 Available FPNODE objects) with the exception that USUP and CSUP objects are not supported. The CPU load of cell and user specific user plane can be measured only on CPU core level using M2002.

Description: The number of packets transmission failed by the logical interface.

Updated: When a packet is transmission fails on the logical interface.




Operability class:






Counter ID: M2007C3 Network element name: Minimum CPU Usage in Node

Version: 1.0 NetAct name: MIN_CPU_USAGE_NODE

Description: The minimum CPU usage value sampled during the measurement interval on node level.


Logical type: Min Trigger type: Sampling interval: 30 s



Operability class:






Counter ID: M2007C4 Network element name: Maximum CPU Usage in Node

DN04143903 615



Version: 1.0 NetAct name: MAX_CPU_USAGE_NODE

Description: The maximum CPU usage value sampled during the measurement interval on node level.


Logical type: Max Trigger type: Sampling interval: 30 s



Operability class:






Counter ID: M2007C5 Network element name: Average CPU Usage in Node

Version: 1.0 NetAct name: AVG_CPU_USAGE_NODE

Description: The average CPU usage value during the measurement interval on node level.


Logical type: Average Trigger type: Sampling interval: 30 s



Operability class:






Documents

Transport HW Counters d