NN-20500-028P3 (MSS Counters) 08.03 Standard November 2007

NN-20500-028

Wireless Service Provider Solutions

W-CDMAUMTS Access Network Counters Reference -Volume 3: MSS CountersNN-20500-028 08.03 Standard November 2007

Wireless Service Provider Solutions

W-CDMAUMTS Access Network Counters Reference - Volume 3:MSS Counters

Document number: NN-20500-028Document issue: 08.03Document status: StandardSystem release: OAM05.2Date: November 2007

Copyright © 2003-2007 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "writeprotected"; it may be altered only by authorized persons. While copies may be printed, it is notrecommended. Viewing of the master electronically ensures access to the current issue. Any hardcopiestaken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property ofAlcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a needto know, and shall protect the information from disclosure and dissemination to third parties. Except asexpressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the informationcontained herein. If you have received this document in error, please notify the sender and destroy itimmediately.

PUBLICATION HISTORYSYSTEM RELEASE OAM05.2

November 2007

Issue 08.03/EN Standard

Update for DR5.

September 2007

Issue 08.02/EN Preliminary

Update for OAM05.2 after internal review.

August 2007

Issue 08.01/EN Draft

Update for OAM05.2

SYSTEM RELEASE UMTS 5.1

July 2007


Update for UA 5.0 Channel Readiness.

March 2007


Update after internal review.

November 2006


Update for OAM 5.1.0 / UA 5.0 [UMTS 5.1]

SYSTEM RELEASE UMTS V5.0

November 2006


Update for OAM V5.0.0.6/UA 4.2.6 [UMTS V5.0 Post-ChR Load]

Alcatel-Lucent Confidential Publication history i

Copyright © 2003-2007 Alcatel-Lucent UMTS Access Network Counters Reference - Volume 3: MSSCounters

October 2006

Issue 06.07 N/A

October 2006


Update for OAM V5.0.0.5/UA 4.2.5 [UMTS V5.0 Post-ChR Load]

July 2006


Update for Post-Channel Readiness

Resolution of the following CR :

• Q01408175

June 2006


Update for Post-Channel Readiness

April 2006


Update for Channel Readiness

November 2005


Update for RANV4.2 after internal review

October 2005


Update for RAN V4.2


October 2005


Update for RAN V4.1

August 2005

Alcatel-Lucent Confidential Publication history ii

NN-20500-028 08.03 Standard November 2007 Copyright © 2003-2007 Alcatel-Lucent


Update for RAN V4.1

Resolution of the following CRs :

• Q01173557

• Q01173549

• Q01173564

• Q01173750

June 2005


Update for RAN V4.1

Change of the NTP structure: review of the content and split into 3 volumes

March 2005


Update for Customer Readness after internal review

Resolution of the following CRs:

• Q00862233

• Q01033167

• Q01033176

• Q01034927

• Q01039681

February 2005


Update for RAN V4.1


February 2005


Update for Channel Readness

November 2004


Alcatel-Lucent Confidential Publication history iii



October 2004

Issue 04.04/EN Pre-standard

Update for Pre-Channel Readness

Resolution of the CR Q00982652

June 2004



May 2004


Update for RAN V4.0


March 2004



February 2004


Update for RAN V3.2


February 2004

Issue 03.04a/EN Standard


November 2003



May 2003

Alcatel-Lucent Confidential Publication history iv




April 2003


Update for RAN V3.1

March 2003


Update for RAN V3.1

Alcatel-Lucent Confidential Publication history v


1 About this publication................................................................................................................................................... 1

2 Road map to UTRAN documentation........................................................................................................................... 4

3 What's new......................................................................................................................................................................5

4 Access Network observation counters........................................................................................................................6

4.1 How Access Network observation counters are defined........................................................................................... 7

4.2 How Access Network observation counters are described......................................................................................14

5 RNC MSS Platform counter families...........................................................................................................................17

5.1 ATM port..................................................................................................................................................................18

5.2 Logical Processor Use.............................................................................................................................................63

5.3 Adjunct Processor Stats.......................................................................................................................................... 78

5.4 ACCOUNT ATM Vcc............................................................................................................................................... 92

5.5 ACCOUNT ATM Vpc............................................................................................................................................. 100

6 MSS Counters Index.................................................................................................................................................. 108

Alcatel-Lucent Confidential Table of contents vi


Figure 1 - MSS containment tree.......................................................................................................... ............. ........... 8

Alcatel-Lucent Confidential List of figures vii


Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 12

Table 2 - VS.ProvRate - #20001........................................................................................................... ............. ......... 19

Table 3 - VS.ActualRate - #20002...................................................................................................................... ......... 20

Table 4 - VS.TxUtilization - #20003.................................................................................................................... ......... 21

Table 5 - VS.RxUtilization - #20004...................................................................................................... ............. ......... 22

Table 6 - VS.TxMaxCellRate - #20005............................................................................................................... ......... 23

Table 7 - VS.TxMinCellRate - #20006................................................................................................................ ......... 24

Table 8 - VS.TxAvgCellRate - #20007.................................................................................................. ............. ......... 25

Table 9 - VS.RxMaxCellRate - #20008................................................................................................. ............. ......... 25

Table 10 - VS.RxMinCellRate - #20009................................................................................................ ............. ......... 26

Table 11 - VS.RxAvgCellRate - #20010................................................................................................ ............. ......... 27

Table 12 - VS.TxMaxCellRateClp - #20011.......................................................................................... ............. ......... 28

Table 13 - VS.TxMinCellRateClp - #20012........................................................................................... ............. ......... 29

Table 14 - VS.TxAvgCellRateClp - #20013........................................................................................... ............. ......... 30

Table 15 - VS.RxMaxCellRateClp - #20014.......................................................................................... ............. ......... 30

Table 16 - VS.RxMinCellRateClp - #20015........................................................................................... ............. ......... 31

Table 17 - VS.RxAvgCellRateClp - #20016.......................................................................................... ............. ......... 32

Table 18 - VS.TxCellDiscards - #20017................................................................................................ ............. ......... 33

Table 19 - VS.RxCellDiscards - #20018............................................................................................................. ......... 34

Table 20 - VS.TxFrameDiscards - #20019............................................................................................ ............. ......... 35

Table 21 - VS.RxFrameDiscards - #20020........................................................................................... ............. ......... 35

Table 22 - VS.TxCellDiscardsClp - #20021........................................................................................................ ......... 36

Table 23 - VS.RxCellDiscardsClp - #20022.......................................................................................... ............. ......... 37

Table 24 - VS.TxFrameDiscardsClp - #20023...................................................................................... ............. ......... 38

Table 25 - VS.RxFrameDiscardsClp - #20024...................................................................................... ............. ......... 39

Table 26 - VS.TxMaxCellRate - #20025............................................................................................................. ......... 40

Table 27 - VS.TxMinCellRate - #20026.............................................................................................................. ......... 41

Table 28 - VS.TxAvgCellRate - #20027................................................................................................ ............. ......... 42

Table 29 - VS.RxMaxCellRate - #20028............................................................................................... ............. ......... 43

Table 30 - VS.RxMinCellRate - #20029................................................................................................ ............. ......... 44

Table 31 - VS.RxAvgCellRate - #20030................................................................................................ ............. ......... 45

Table 32 - VS.TxMaxCellRateClp - #20031.......................................................................................... ............. ......... 46

Table 33 - VS.TxMinCellRateClp - #20032........................................................................................... ............. ......... 48

Table 34 - VS.TxAvgCellRateClp - #20033........................................................................................... ............. ......... 49

Table 35 - VS.RxMaxCellRateClp - #20034.......................................................................................... ............. ......... 50

Table 36 - VS.RxMinCellRateClp - #20035........................................................................................... ............. ......... 51

Table 37 - VS.RxAvgCellRateClp - #20036.......................................................................................... ............. ......... 52

Table 38 - VS.TxCellDiscards - #20037................................................................................................ ............. ......... 53

Table 39 - VS.RxCellDiscards - #20038............................................................................................................. ......... 54

Table 40 - VS.TxFrameDiscards - #20039............................................................................................ ............. ......... 55

Table 41 - VS.RxFrameDiscards - #20040........................................................................................... ............. ......... 57

Alcatel-Lucent Confidential List of tables viii


Table 42 - VS.TxCellDiscardsClp - #20041........................................................................................................ ......... 58

Table 43 - VS.RxCellDiscardsClp - #20042.......................................................................................... ............. ......... 59

Table 44 - VS.TxFrameDiscardsClp - #20043...................................................................................... ............. ......... 60

Table 45 - VS.RxFrameDiscardsClp - #20044...................................................................................... ............. ......... 61

Table 46 - VS.CpuUtilAvg - #20103...................................................................................................... ............. ......... 63

Table 47 - VS.CpuUtilAvgMin - #20104................................................................................................ ............. ......... 64

Table 48 - VS.CpuUtilAvgMax - #20105............................................................................................... ............. ......... 65

Table 49 - VS.MemoryCapacity - #20106............................................................................................. ............. ......... 66

Table 50 - VS.MemoryUsageAvg - #20107........................................................................................................ ......... 67

Table 51 - VS.MemoryUsageAvgMin - #20108..................................................................................... ............. ......... 68

Table 52 - VS.MemoryUsageAvgMax - #20109.................................................................................... ............. ......... 69

Table 53 - VS.SharedMsgBlockCapacity - #20110............................................................................... ............. ......... 70

Table 54 - VS.SharedMsgBlockUsageAvg - #20111............................................................................ ............. ......... 71

Table 55 - VS.SharedMsgBlockUsageAvgMin - #20112.................................................................................... ......... 71

Table 56 - VS.SharedMsgBlockUsageAvgMax - #20113................................................................................... ......... 72

Table 57 - VS.LocalMsgBlockCapacity - #20114.................................................................................. ............. ......... 73

Table 58 - VS.LocalMsgBlockUsageAvg - #20115............................................................................... ............. ......... 74

Table 59 - VS.LocalMsgBlockUsageMin - #20116................................................................................ ............. ......... 75

Table 60 - VS.LocalMsgBlockUsageMax - #20117............................................................................... ............. ......... 76

Table 61 - VS.ApCpuUtilizationHistogram - #20201............................................................................. ............. ......... 78

Table 62 - VS.ApCpuUtilizationAvg - #20202....................................................................................... ............. ......... 80

Table 63 - VS.ApMemoryCapacity - #20203......................................................................................... ............. ......... 80

Table 64 - VS.ApMemoryUtilization - #20204....................................................................................... ............. ......... 81

Table 65 - VS.ApMemoryUsageAvgMin - #20205................................................................................ ............. ......... 82

Table 66 - VS.ApMemoryUsageAvgMax - #20206............................................................................... ............. ......... 83

Table 67 - VS.ApSharedMsgBlockCapacity - #20207........................................................................................ ......... 84

Table 68 - VS.ApSharedMsgBlockUsageAvg - #20208........................................................................ ............. ......... 85

Table 69 - VS.ApSharedMsgBlockUsageAvgMin - #20209.................................................................. ............. ......... 85

Table 70 - VS.ApSharedMsgBlockUsageAvgMax - #20210................................................................. ............. ......... 86

Table 71 - VS.ApLocalMsgBlockCapacity - #20211........................................................................................... ......... 87

Table 72 - VS.ApLocalMsgBlockUsageAvg - #20212........................................................................... ............. ......... 88

Table 73 - VS.ApLocalMsgBlockUsageAvgMin - #20213..................................................................... ............. ......... 89

Table 74 - VS.ApLocalMsgBlockUsageAvgMax - #20214.................................................................... ............. ......... 90

Table 75 - VS.AcVccIngressCellCountClp0 - #30001........................................................................... ............. ......... 92

Table 76 - VS.AcVccIngressCellCountClp01 - #30002......................................................................... ............. ......... 93

Table 77 - VS.AcVccEgressCellCountClp0 - #30003......................................................................................... ......... 94

Table 78 - VS.AcVccEgressCellCountClp01 - #30004....................................................................................... ......... 94

Table 79 - VS.AcVccIngressDiscardedClp0 - #30005........................................................................................ ......... 95

Table 80 - VS.AcVccIngressDiscardedClp01 - #30006...................................................................................... ......... 96

Table 81 - VS.AcVccEgressDiscardedClp0 - #30007........................................................................... ............. ......... 97

Table 82 - VS.AcVccEgressDiscardedClp01 - #30008......................................................................... ............. ......... 98

Table 83 - VS.AcVpcIngressCellCountClp0 - #30101........................................................................... ............. ....... 100

Alcatel-Lucent Confidential List of tables ix


Table 84 - VS.AcVpcIngressCellCountClp01 - #30102......................................................................... ............. ....... 101

Table 85 - VS.AcVpcEgressCellCountClp0 - #30103........................................................................... ............. ....... 102

Table 86 - VS.AcVpcEgressCellCountClp01 - #30104......................................................................... ............. ....... 102

Table 87 - VS.AcVpcIngressDiscardedClp0 - #30105.......................................................................... ............. ....... 103

Table 88 - VS.AcVpcIngressDiscardedClp01 - #30106........................................................................ ............. ....... 104

Table 89 - VS.AcVpcEgressDiscardedClp0 - #30107........................................................................... ............. ....... 105

Table 90 - VS.AcVpcEgressDiscardedClp01 - #30108......................................................................... ............. ....... 106

Alcatel-Lucent Confidential List of tables x


1 About this publication

This publication provides a list of UMTS Access Network observation counters collected by theAPM/ADI applications of the Performance server.

This section consists of the following topics:

• "Applicability"

• "Audience"

• "Prerequisites"

• "Related publications"

• "How this publication is organized"

• "Vocabulary conventions"

Applicability

This publication applies to OAM05.2 System Release.

Audience

This publication is intended for network controllers responsible for the Performance Management ofthe UMTS Access Network.

Prerequisites

It is recommended that readers become familiar with the following Technical Publications :

• UMTS Access Network Performance Management (NN-20500-034)

• UMTS Access Network Overview (NN-20500-031) provides a functional overview of theOperation, Administration and Maintenance (OAM) subsystem of the Access Network.

Related publications• UMTS Access Network Performance Management (NN-20500-033)

How this publication is organized

This publication consists of the following modules:

• "Road map to Utran" presents the documents in the UTRAN documentation suite.

• "What is new in Access Network Observation Counters" presents the changes and, or thenew features introduced for the UMTS 5.1 release.

• "Access Network observation counters" is split into the following sections:

— "How Access Network observation counters are defined" provides information about the

Alcatel-Lucent Confidential 1


counter definition template, counter types on the OAM GUI, and counter hierarchy.

— "How Access Network observation counters are described" describes the AccessNetwork observation counters.

• "MSS Platform counter families" lists MSS platform counter families and presents theircounters. Each counter is described separately in a table, and these tables are arranged inalphanumerical order.

• Index presents the index of each Access Network observation counter.

Vocabulary conventions

For a list of UMTS terms used in this document, see the UMTS Access Terminology (NN-20500-002).

The specific acronyms used in this publication are the following:

A. Release Available Release

CC Cumulative Counter

CFN Connection Frame Number

CUM CUMulative

DER Discrete Event Registration counter

DTD Document Type Definition

mW milliWatt

NEI NEIghboring

SI Status Inspection

VAL VALue counter

The specific terms used in this publication are the following:

Access Stratum Config-uration

Pointer to a pre-defined set of Radio Bearers providing a given Ra-dio Access Bearer service.

For example:

• the Downlink (DL) access stratum configuration which number is1 is dedicated to voice support; it comprises the following RadioBearers : 3 x 12.2 Kbps CS RBs on DTCH and 3 x 3.4 KbpsSRB on DCCH.

• the DL access stratum configuration which number is 2 is dedic-ated to packet support at 64 Kbps; it comprises the following Ra-dio Bearers : 1 x 64 Kbps PS RB on DTCH and 3 x 3.4 KbpsSRB for DCCH.

Refer to the following configurations:

— Downlink Access Stratum Configuration (DASC)

— Downlink Radio Bearer Set Configuration (DRBS)



— Uplink Access Stratum Configuration (UASC)

— Uplink Radio Bearer Set Configuration (URBS)

Connection Frame Num-ber (CFN)

CFN is the frame counter used for the L2/transport channel syn-chronisation between UE and UTRAN. A CFN value is associated toeach Transport Block Set (TBS) and it is passed together with itthrough the MAC-L1 SAP. CFN provides a common frame reference(at L2) to be used that is for synchronized transport channel recon-figuration.

Measurement Term used in 3GPP TS 32.104 specifications. It has the samemeaning as the word 'counter' and is used in this publication to dis-tinguish a counter from a '(radio) measurement'.

Reference cell Cell ranking first in a UE active set considering a radio criteria , thatmeans the cell supposed to provide on average the best radio qual-ity for the reception of the next frames.

The reference cell is the primary cell considered in RRM.



2 Road map to UTRAN documentation

For collection roadmaps information, see UMTS Access Document Collection - Overview and updatesummary (NN-20500-050).



3 What's new

For information about What's new section, see : UTRAN 5.0 / W-NMS 5.1 Release OperationalImpactsNN-20500-052, Vol3, Annex C



4 Access Network observation counters

This section includes the following topics:

• "How Access Network observation counters are defined"

• "How Access Network observation counters are described"



4.1 How Access Network observation counters are defined

A standard observation counter is a device used in Performance Management to calculate thenumber of occurrences of an event. For further definitions for observation counters, refer to 3GPP TS32.104 specifications.

This section describes the following topics:

• "Counter families"

• "Object hierarchy"

• "Wording assumption"

• "Counter definition template"

• "Counter types on the OAM GUI"

• "Counter hierarchy"

• "Aggregation rules"

Counter families

The counters specified in this publication are grouped into families of counters. A family of countersis attached to a given UMTS feature. For example the "Radio Link Management Family" groupstogether counters involved with Radio Link Management (i.e.: Setup, Addition, Deletion,Reconfiguration..).

Object hierarchy

Counters are reported on objects (that is location) according to their hierarchy.

The following figure show the hierarchy of objects.



Figure 1 MSS containment tree

Note: Objects that report counters are in bold underlined.

For more information about UTRAN objects and their relationships, refer to the UMTS AccessNetwork Overview (NN-20500-031) publication.

Wording assumption

Both wordings counter and measurement are equally used in this document to identify the sameconcept. Usually, Alcatel-Lucent uses the term counter to distinguish a counter from a (radio)measurement

3GPP Performance Management specifications preferably use measurement. When the contextrefers to 3GPP specifications, measurement is used, while counter is used in Alcatel-Lucentspecific part, but both wordings are equivalent.

Counter definition template

The following template used to describe the counters is extracted from 3GPP TS 32.104specifications.

Measurement name (section header)

This is a descriptive name of the measurement type.

A-Description



This section contains an explanation of the measurement operation.

B-Collection

This section contains the form of the obtained measurement data:

• CC (Cumulative Counter) is incremented by 1 each time the counted event occurs.

• GAUGE (dynamic variable), data being measured can vary during the period of measurement.

• DER (Discrete Event Registration), data related to a particular event is captured every nth event,where n can be 1 or larger.

• SI (Status Inspection), data related to the mean value is captured every nth sampling, where ncan be 1 or larger.

C-Condition (Event)

This section contains the condition that causes the measurement result data to be updated.

The condition is defined by identifying protocol related triggering events that either start or stop themeasurement processes or by updating the current measurement result value. When a precisecondition cannot be provided, the conditional circumstances behind the update are stated.

D-Result

This section contains a description of expected result value(s) (for example, a single integer value). Ifmore than one value is provided, the measurement is screened according to criteria, for example, anumber of call releases may be screened according to the cause of the call releases.

The number of call releases related to a given cause can be considered a subcounter. In that case,the measurement result specification item includes a 'screening paragraph' that specifies the varioussubcounters and their meanings.

E-Type

This section contains a short form of the measurement name specified in the header, which is usedto identify the measurement type in the result files.

F-Object Instance

This section contains the object class and its instance. The "measObjInstId" field identifies themeasured object class and its instance; for example, trunk1 means that object class trunk instance#1 is being measured. The object class and instance values used for this purpose will be inaccordance with 3GPP TS 32.106. This means the NE or resource object model (defined in the BasicCM IRP Information Model - 3GPP TS 32.106-5) and naming conventions (defined in the NamingConvention for Managed Objects - 3GPP TS 32.106-8). This parameter, if applicable, will beprovided in the measurement job.



G-Switching

This section contains the Switching domain(s). Its measurement is applicable to Circuit Switchedand, or Packet Switched domains.

Note: Two counter specification items have been added to the seven preceding 3GPP items byAlcatel-Lucent.

H-3GPP Compliance

This section states the compliance of the Alcatel-Lucent measurement with 3GPP specifications:

• the statement is "3GPP specified counter" if the Alcatel-Lucent implementation is fully compliantwith the 3GPP specification.

• the statement is "Alcatel-Lucent specified counter" if the counter is not considered by the 3GPPspecification.

I-Range

This section contains the range of the counter.

J-Unit

This section contains the unit of the counter.

K-Available Release

This section states the Alcatel-Lucent UMTS system release(s) in which the counter had beenintroduced.

L-Aggregation Rule

This section contains one of these three values :RLoad, RVal and Rtotal. Each value defines theaggregation rule type. The counter type defines the aggregation rule value.

M-Notes

This section contains notes and FRS numbers associated with the counters.

Counter types on the OAM GUI

The three types of user-accessible observation counters available on the OAM GUI are as follows:

• CUMULATIVE (or TOTAL)

• VALUE

• LOAD

CUMULATIVE counters



CUMULATIVE counters provide raw counts. A CUMULATIVE counter is a CUM (CC) type counter,as identified in 3GPP TS 32.104 specifications. It is incremented by 1 each time the counted eventoccurs, and it provides the cumulated value. One NE cumulative counter provides one counter at theOAM GUI level.

VALUE counters

VALUE counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order toimplement a DER (VAL) type measurement. This mechanism provides average values from rawcounts obtained by internal events (the time interval between two events is random and is notaccessible to users). The counter is incremented by a value attached to the event itself.Alcatel-Lucent provides the following:

• the cumulated value (.Cum in XML files)

• the number of events (.NbEvt in XML files)

Note: This value is sampled once per hour and is indicated in the XML observation file.

• the averaged value (.Avg in XML files)

• the maximum added value (.Max in XML files)

• the minimum added value (.Min in XML files)

Note: The averaged value is equal to cumulated value over number of events

LOAD counters

LOAD counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order toimplement an SI type measurement. This mechanism provides average values from raw countsobtained by internal sampling (the time interval between two events is constant and is not accessibleto users). The counter is incremented by a sampled value on the sampling event occurrence.Alcatel-Lucent provides the following:

• the cumulated value (.Cum in XML files)

• the number of samplings (.NbEvt in XML files)

• the averaged value (.Avg in XML files)

• the maximum sampled value (.Max in XML files)

• the minimum sampled value (.Min in XML files)

Note: The averaged value is equal to cumulated value/number of samplings.

Note: Alcatel-Lucent does not generally implement GAUGE type measurements becauseproviding the current value of a measurement by incrementing it by 1 when a positive event occursand by decrementing it by 1 when a negative event occurs, can lead to some shifts if an event ismissed.

Note: The reported value counter is collected by a non real time task at the end of eachobservation period. The collection period (usually one hour) for the Performance Management filedoes not imply that all .NbEvt of LOAD counters are exactly equal to the number of counter



periods included in one collection (12 for counters with 5mn granularity). Due to the low priority ofthe Performance Management task, it is possible when the PM file is built that some samples canmiss. They will be included in the next file. This can lead to one file with NbEvt equal to 11 (for a5mn counter), followed later by one with 13 (possibly with some 12 between). The averagesvalues calculated by computing .Cum/.NbEvt are still meaningful, as the samples added in .Cumare coherent with the .NbEvt value.

Counter hierarchy

An observation counter stored in XML files can contain one or several levels.

A dot (.) separates two successive levels.

The following example shows the counter hierarchy with five levels.

Example:

radioLink.establishment.failure.cause<Name>.Avg

Counters with one level do not end with a dot.

Example:

droppedLastRadioLink

Aggregation rules

When aggregating counters from different periods of observation (temporal aggregation) you mustfollow the following rules.

Let X1,X2,...,Xn the measurements from periods 1,2,...,n and X the resulting value over the totalperiod.

The following table presents a rule for each counter.

Table 1 Table of aggregation rules

Rule Results Apply to

Rtotal X.cum = X1.cum + X2.cum + ... + Xn.cum CUM (CC) counters

Rload/Rval X.cum = X1.cum + ... + Xn.cum

X.nbevt = X1.nbevt + ... + Xn.nbevt

X.avg = (X1.cum + ... + Xn.cum) / (X1.nbevt + ... +Xn.nbevt)

X.min = min (X1.min,...,Xn.min)

X.max = max (X1.max,...,Xn.max)

Some LOAD and VALcounters

Rload* Same as Rload but resulting X.cum has no phys-ical meaning due to the nature of the measure-ment (like percents) and is not interpreted but isnecessary for intermediate computations.

Some LOAD counters

Ravg X = Xi / n MSS counters



Rule Results Apply to

where Xi (i = 1 to n) represent average values

Radd X = ΣXi

where Xi (i = 1 to n) represent cumulative values

MSS counters

Rmin X = min (Xi)

where Xi (i = 1 to n) represent minimum values

MSS counters

Rmax X = max (Xi)

where Xi (i = 1 to n) represent maximum values

MSS counters



4.2 How Access Network observation counters are described

An observation counter is a measurement used to report data for network PerformanceManagement.

Observation counters are stored in XML record files.

Each record file contains the counters produced by a single NE collection.

Access Network observation counters handled by the ADI application for the UMTS 5.1 systemrelease are as follows:

• C-Node application counters

• I-Node platform counters

• Node B counters

These counters have been divided into the three following sets of families:

• "RNC counter families"

• "BTS counter families"

• "MSS counter families"

Each counter family is attached to a given UMTS feature (for example, Handover counters, wherehard handover performances are reported) or to a Performance Management purpose for example,User Plane Traffic counters, where counters related to traffic observation are grouped together).

Access observation file structure

Some observation counters are processed in order to provide temporal and spatial aggregations. Thefollowing observation counter records are available:

• single period

• hourly aggregated

• daily aggregated

Each observation file produces single, hourly and daily observation counter records. At the dedicatedNE level, a predetermined subset of these data are aggregated.

The file name convention for an observation is as follows:

<type><startdate>.<starttime>-<endtime>_<NE>[-<RC>].

Where:

type is set to A which indicates one of the following aggregated observations:

• the observation file contains data originated from a single NE for a unique time period.



• the observation file contains data originated from a single NE for an hourly aggregated file.

• the observation file contains data originated from a single NE for a daily aggregated file.

startdate is the beginning date of the granularity period; its format must be <YYYYMMDD>.

starttime is the beginning time of the granularity period; its format must be <hhmm+#GMT>.

endtime is the end time of the granularity period; its format must be <hhmm+#GMT>.

NE is the Network Element type ID that means a unique numerical identifier as 3GPP using<node Type>-<NE userlabel> pattern (for example, "ANode-rnc1" or "RNCCN-rnc10" or "INode-rnc12").

List of possible NE types:

• RNCCN

• INode

• ANode

• NodeB

• POCOr the BTS name using the NE userLabel as a NE ID (for example "NodeB-A10km215").

RC is an optional running count. In case of PPT aggressive mode collection,the value is 2+.Note : If the RC is absent, the "-" separator is absent as well.

Refer to the following table for an interpretation of the codes:

Code Description

YYYY The 4-digit year

MM The month of the year (01, 02,..., 12) for file creation time at RNC level

DD The day of the month (01, 02,..., 31) for file creation time at RNC level

hh The 2-digit hour (00, 01,..., 23). In the case of daily aggregation files, hh is al-ways 00.

mm The 2-digit minute of the hour. Possible values are by increments of fiveminutes: 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55. In the case ofhourly or daily aggregation files, mm is always 00.

#GMT Difference between local time and Greenwich Meridian Time (+/-hhmm). At10:15:02 in Paris, the 13 April 2005 in Paris, the #GMT is +0100 = thehhmm#GMT is 1015+0100.At 18:12:11 in New York, the 13 April 2005, the#GMT is #0500 = the hhmm#GMT is 1812-0500.

RNC observation XML file

The XML format is compliant with 3 GPP dtd file: 32.401-02.dtd. The granularity period defines, inminutes, the periodicity of the generation of the counter; the values supported for accounting is 60



and for stats are 15, 30 and 60.

The directory of the RNC I-Node observation XML file for statistic counters on PerfServer is asfollows:

•For Stats:/opt/nortel/data/utran/observation/stats/<YYYYMMDD>/INode-<RNC><PPUserLabel>

•For Accounting:/opt/nortel/data/utran/observation/account/<YYYYMMDD>/INode-<RNC><PPUserLabel>

For more information about RNC XML record files, refer to the UMTS Access Network PerformanceManagement (NN-20500-033) publication.



5 RNC MSS Platform counter families

• ATM port

• Logical Processor Use

• Adjunct Processor Stats

• ACCOUNT ATM Vcc

• ACCOUNT ATM Vpc



5.1 ATM port

These counters apply to both I-node and A-node Lp (Logical Processor) and AtmPort locations. All ofthem are vendor-specific, and none of them are used to compute 3GPP counters. In UMTS 04.1,with UTRAN version UA04.1, MSS release is PCR6.1. Therefore the ultimate reference fordescription of counters provided by NTPs MSS are to be found in the adequate NTP, see references[R4], [R6], [R7], and [R8]. The counters of the family ATM port come from MSS, componentATMInterface (ATMIf). GROUP ATMIf Statistics (Stats). The MSS Attribute e.g. ATTRIBUTE AtmIftxCellDiscardClp maps directly to the name of the counter VS.TxCellDiscardsClp. RNC provides onlya subset of the ATM statistics available on MSS. Note that some counters are not available on someconfigurations (see Chapter 3 Monitoring ATM interfaces in MSS Monitoring and TroubleshootingGuide). On 16-port OC3/STM1 FP statistics per port (AtmIf) txCellDiscardCLP0+1, txCellDiscardCLP1, rxCellDiscardCLP0+1, rxCellDiscardCLP1 are NOT available. , and On 4-portOC12/STM4 channelized FP statistics per port on an unchannelized basis (ATmIf) txCellCLP1,txCellDiscardCLP1, rxCellCLP1, rxCellDiscardCLP1 are NOT available. Ref: NTP 241-5701-060Volume 2 (MSS Components)

Alcatel-Lucentcounter number

Counter name

#20001 VS.ProvRate

#20002 VS.ActualRate

#20003 VS.TxUtilization

#20004 VS.RxUtilization

#20005 VS.TxMaxCellRate

#20006 VS.TxMinCellRate

#20007 VS.TxAvgCellRate

#20008 VS.RxMaxCellRate

#20009 VS.RxMinCellRate

#20010 VS.RxAvgCellRate

#20011 VS.TxMaxCellRateClp

#20012 VS.TxMinCellRateClp

#20013 VS.TxAvgCellRateClp

#20014 VS.RxMaxCellRateClp

#20015 VS.RxMinCellRateClp

#20016 VS.RxAvgCellRateClp

#20017 VS.TxCellDiscards

#20018 VS.RxCellDiscards




Counter name

#20019 VS.TxFrameDiscards

#20020 VS.RxFrameDiscards

#20021 VS.TxCellDiscardsClp

#20022 VS.RxCellDiscardsClp

#20023 VS.TxFrameDiscardsClp

#20024 VS.RxFrameDiscardsClp

#20025 VS.TxMaxCellRate

#20026 VS.TxMinCellRate

#20027 VS.TxAvgCellRate

#20028 VS.RxMaxCellRate

#20029 VS.RxMinCellRate

#20030 VS.RxAvgCellRate

#20031 VS.TxMaxCellRateClp

#20032 VS.TxMinCellRateClp

#20033 VS.TxAvgCellRateClp

#20034 VS.RxMaxCellRateClp

#20035 VS.RxMinCellRateClp

#20036 VS.RxAvgCellRateClp

#20037 VS.TxCellDiscards

#20038 VS.RxCellDiscards

#20039 VS.TxFrameDiscards

#20040 VS.RxFrameDiscards

#20041 VS.TxCellDiscardsClp

#20042 VS.RxCellDiscardsClp

#20043 VS.TxFrameDiscardsClp

#20044 VS.RxFrameDiscardsClp

Table 2 VS.ProvRate - #20001

A-Description

AtmIf s provisioned link rate in cells per second

B-Collection

CUM

CUMulative

C-Condition (Event)

-



D-Result

one measurement

E-Type

VS.ProvRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20001

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 3 VS.ActualRate - #20002

A-Description

AtmIf 's actual bandwidth in cells per second. Equals provRate when no errors occur.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ActualRate

F-Object Instance

AtmPort



G-Switching

NA

H-3GPP Compliance

N-#20002

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 4 VS.TxUtilization - #20003

A-Description

This attribute indicates the average transmit traffic rate over the most recent collection intervalexpressed as a percentage of the ATM link bandwidth. On AtmIfs linked to MPLS POS inter-faces, the ATM link is the LSP. Many LSPs could share the same POS link. If the POS link isunderutilized it is possible for an LSP to carry more traffic than it has been assigned. This oc-curs as bandwidth on an LSP is allocated based on determining whether the requested band-width exceeds the available bandwidth on an LSP, not on whether the actual bandwidth ex-ceeds the available bandwidth. When the actual bandwidth is higher than the requested band-with it is possible that this extra traffic will be carried over the LSP. Since this is possible, thevalue of this attribute may exceed 100%. If the utilization exceeds 65535% then 65535 is dis-played. If the Lsp has a bandwidth of 0, then 0 is displayed for the utilization.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxUtilization

F-Object Instance

AtmPort



G-Switching

NA

H-3GPP Compliance

N-#20003

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 5 VS.RxUtilization - #20004

A-Description

This attribute indicates the average receive traffic rate over the most recent collection intervalexpressed as a percentage of the ATM link bandwidth. On AtmIfs linked to MPLS POS inter-faces, the ATM link is the LSP. Many LSPs could share the same POS link. If the POS link isunderutilized it is possible for an LSP to carry more traffic than it has been assigned. This oc-curs as bandwidth on an LSP is allocated based on determining whether the requested band-width exceeds the available bandwidth on an LSP, not on whether the actual bandwidth ex-ceeds the available bandwidth. When the actual bandwidth is higher than the requested band-with it is possible that this extra traffic will be carried over the LSP. Since this is possible, thevalue of this attribute may exceed 100%. If the utilization exceeds 65535% then 65535 is dis-played. If the Lsp has a bandwidth of 0, then 0 is displayed for the utilization.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxUtilization

F-Object Instance

AtmPort



G-Switching

NA

H-3GPP Compliance

N-#20004

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 6 VS.TxMaxCellRate - #20005

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the busiest minute of the col-lection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMaxCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20005

I-Range



0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 7 VS.TxMinCellRate - #20006

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the least busy minute of thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMinCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20006

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0



L-Aggregation Rule

Rmin

Table 8 VS.TxAvgCellRate - #20007

A-Description

This attribute indicates the average transmitted cell rate (CLP=0+1) during the collection inter-val.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxAvgCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20007

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 9 VS.RxMaxCellRate - #20008

A-Description



This attribute indicates the received cell rate (CLP=0+1) during the busiest minute of the collec-tion interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxMaxCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20008

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 10 VS.RxMinCellRate - #20009

A-Description

This attribute indicates the received cell rate (CLP=0+1) during the least busy minute of thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)



-

D-Result

one measurement

E-Type

VS.RxMinCellRate

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20009

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 11 VS.RxAvgCellRate - #20010

A-Description

This attribute indicates the average received cell rate (CLP=0+1) during the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxAvgCellRate

F-Object Instance



AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20010

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 12 VS.TxMaxCellRateClp - #20011

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the busiest minute of the col-lection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMaxCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20011



I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 13 VS.TxMinCellRateClp - #20012

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the least busy minute of thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxMinCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20012

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release



V2v0

L-Aggregation Rule

Rmin

Table 14 VS.TxAvgCellRateClp - #20013

A-Description

This attribute indicates the average transmitted cell rate (CLP=1) during the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxAvgCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20013

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 15 VS.RxMaxCellRateClp - #20014

A-Description



This attribute indicates the received cell rate (CLP=1) during the busiest minute of the collec-tion interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxMaxCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20014

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 16 VS.RxMinCellRateClp - #20015

A-Description

This attribute indicates the received cell rate (CLP=1) during the least busy minute of the col-lection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)



-

D-Result

one measurement

E-Type

VS.RxMinCellRateClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20015

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 17 VS.RxAvgCellRateClp - #20016

A-Description

This attribute indicates the average received cell rate (CLP=1) during the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxAvgCellRateClp

F-Object Instance



AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20016

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 18 VS.TxCellDiscards - #20017

A-Description

This attribute counts the cells (CLP=0+1) which are discarded before being transmitted duringthe collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxCellDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20017



I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 19 VS.RxCellDiscards - #20018

A-Description

This attribute counts the cells (CLP=0+1) which are discarded after being received during thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxCellDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20018

I-Range

0..2^64-1

J-Unit

cell

K-Available Release



V2v0

L-Aggregation Rule

Radd

Table 20 VS.TxFrameDiscards - #20019

A-Description

This attribute counts the frames (CLP=0+1) which are discarded before being transmitted dur-ing the collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxFrameDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20019

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 21 VS.RxFrameDiscards - #20020



A-Description

This attribute counts the frames (CLP=0+1) which are discarded after being received duringthe collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxFrameDiscards

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20020

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 22 VS.TxCellDiscardsClp - #20021

A-Description

This attribute counts the cells (CLP=1) which are discarded before being transmitted during thecollection interval.

B-Collection

CUM

CUMulative



C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxCellDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20021

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 23 VS.RxCellDiscardsClp - #20022

A-Description

This attribute counts the cells (CLP=1) which are discarded after being received during the col-lection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type



VS.RxCellDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20022

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 24 VS.TxFrameDiscardsClp - #20023

A-Description

This attribute counts the frames (CLP=1) which are discarded before being transmitted duringthe collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.TxFrameDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA



H-3GPP Compliance

N-#20023

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 25 VS.RxFrameDiscardsClp - #20024

A-Description

This attribute counts the frames (CLP=1) which are discarded after being received during thecollection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.RxFrameDiscardsClp

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20024

I-Range

0..2^64-1

J-Unit



frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 26 VS.TxMaxCellRate - #20025

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the busiest minute of the col-lection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

A set of subcounters screened on: ATM Service Category

• Sub-Counter #0 : Cbr

• Sub-Counter #1 : Rtvbr

• Sub-Counter #2 : Nrtvbr

• Sub-Counter #3 : Abr

• Sub-Counter #4 : Ubr

E-Type

• VS.TxMaxCellRate.Cbr

• VS.TxMaxCellRate.Rtvbr

• VS.TxMaxCellRate.Nrtvbr

• VS.TxMaxCellRate.Abr

• VS.TxMaxCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance



N-#20025

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 27 VS.TxMinCellRate - #20026

A-Description

This attribute indicates the transmitted cell rate (CLP=0+1) during the least busy minute of thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxMinCellRate.Cbr

• VS.TxMinCellRate.Rtvbr

• VS.TxMinCellRate.Nrtvbr

• VS.TxMinCellRate.Abr

• VS.TxMinCellRate.Ubr

F-Object Instance



AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20026

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 28 VS.TxAvgCellRate - #20027

A-Description

This attribute indicates the average transmitted cell rate (CLP=0+1) during the collection inter-val by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxAvgCellRate.Cbr

• VS.TxAvgCellRate.Rtvbr



• VS.TxAvgCellRate.Nrtvbr

• VS.TxAvgCellRate.Abr

• VS.TxAvgCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20027

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 29 VS.RxMaxCellRate - #20028

A-Description

This attribute indicates the received cell rate (CLP=0+1) during the busiest minute of the collec-tion interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result









E-Type

• VS.RxMaxCellRate.Cbr

• VS.RxMaxCellRate.Rtvbr

• VS.RxMaxCellRate.Nrtvbr

• VS.RxMaxCellRate.Abr

• VS.RxMaxCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20028

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 30 VS.RxMinCellRate - #20029

A-Description

This attribute indicates the received cell rate (CLP=0+1) during the least busy minute of thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result









E-Type

• VS.RxMinCellRate.Cbr

• VS.RxMinCellRate.Rtvbr

• VS.RxMinCellRate.Nrtvbr

• VS.RxMinCellRate.Abr

• VS.RxMinCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20029

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 31 VS.RxAvgCellRate - #20030

A-Description

This attribute indicates the average received cell rate (CLP=0+1) during the collection intervalby ATM service category.

B-Collection

CUM

CUMulative



C-Condition (Event)

-

D-Result







E-Type

• VS.RxAvgCellRate.Cbr

• VS.RxAvgCellRate.Rtvbr

• VS.RxAvgCellRate.Nrtvbr

• VS.RxAvgCellRate.Abr

• VS.RxAvgCellRate.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20030

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 32 VS.TxMaxCellRateClp - #20031

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the busiest minute of the col-



lection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxMaxCellRateClp.Cbr

• VS.TxMaxCellRateClp.Rtvbr

• VS.TxMaxCellRateClp.Nrtvbr

• VS.TxMaxCellRateClp.Abr

• VS.TxMaxCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20031

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax



Table 33 VS.TxMinCellRateClp - #20032

A-Description

This attribute indicates the transmitted cell rate (CLP=1) during the least busy minute of thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxMinCellRateClp.Cbr

• VS.TxMinCellRateClp.Rtvbr

• VS.TxMinCellRateClp.Nrtvbr

• VS.TxMinCellRateClp.Abr

• VS.TxMinCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20032

I-Range

0..2^32-1

J-Unit

cell/s



K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 34 VS.TxAvgCellRateClp - #20033

A-Description

This attribute indicates the average transmitted cell rate (CLP=1) during the collection intervalby ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxAvgCellRateClp.Cbr

• VS.TxAvgCellRateClp.Rtvbr

• VS.TxAvgCellRateClp.Nrtvbr

• VS.TxAvgCellRateClp.Abr

• VS.TxAvgCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20033



I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 35 VS.RxMaxCellRateClp - #20034

A-Description

This attribute indicates the received cell rate (CLP=1) during the busiest minute of the collec-tion interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.RxMaxCellRateClp.Cbr

• VS.RxMaxCellRateClp.Rtvbr

• VS.RxMaxCellRateClp.Nrtvbr

• VS.RxMaxCellRateClp.Abr

• VS.RxMaxCellRateClp.Ubr

F-Object Instance

AtmPort



G-Switching

NA

H-3GPP Compliance

N-#20034

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 36 VS.RxMinCellRateClp - #20035

A-Description

This attribute indicates the received cell rate (CLP=1) during the least busy minute of the col-lection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.RxMinCellRateClp.Cbr

• VS.RxMinCellRateClp.Rtvbr

• VS.RxMinCellRateClp.Nrtvbr



• VS.RxMinCellRateClp.Abr

• VS.RxMinCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20035

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 37 VS.RxAvgCellRateClp - #20036

A-Description

This attribute indicates the average received cell rate (CLP=1) during the collection interval byATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result









E-Type

• VS.RxAvgCellRateClp.Cbr

• VS.RxAvgCellRateClp.Rtvbr

• VS.RxAvgCellRateClp.Nrtvbr

• VS.RxAvgCellRateClp.Abr

• VS.RxAvgCellRateClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20036

I-Range

0..2^32-1

J-Unit

cell/s

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 38 VS.TxCellDiscards - #20037

A-Description

This attribute counts the cells (CLP=0+1) which are discarded before being transmitted duringthe collection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result









E-Type

• VS.TxCellDiscards.Cbr

• VS.TxCellDiscards.Rtvbr

• VS.TxCellDiscards.Nrtvbr

• VS.TxCellDiscards.Abr

• VS.TxCellDiscards.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20037

I-Range

0..2^32-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 39 VS.RxCellDiscards - #20038

A-Description

This attribute counts the cells (CLP=0+1) which are discarded after being received during thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)



-

D-Result







E-Type

• VS.RxCellDiscards.Cbr

• VS.RxCellDiscards.Rtvbr

• VS.RxCellDiscards.Nrtvbr

• VS.RxCellDiscards.Abr

• VS.RxCellDiscards.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20038

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 40 VS.TxFrameDiscards - #20039

A-Description

This attribute counts the frames (CLP=0+1) which are discarded before being transmitted dur-ing the collection interval by ATM service category.



B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxFrameDiscards.Cbr

• VS.TxFrameDiscards.Rtvbr

• VS.TxFrameDiscards.Nrtvbr

• VS.TxFrameDiscards.Abr

• VS.TxFrameDiscards.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20039

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd



Table 41 VS.RxFrameDiscards - #20040

A-Description

This attribute counts the frames (CLP=0+1) which are discarded after being received duringthe collection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.RxFrameDiscards.Cbr

• VS.RxFrameDiscards.Rtvbr

• VS.RxFrameDiscards.Nrtvbr

• VS.RxFrameDiscards.Abr

• VS.RxFrameDiscards.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20040

I-Range

0..2^64-1

J-Unit

frame

K-Available Release



V2v0

L-Aggregation Rule

Radd

Table 42 VS.TxCellDiscardsClp - #20041

A-Description

This attribute counts the cells (CLP=1) which are discarded before being transmitted during thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxCellDiscardsClp.Cbr

• VS.TxCellDiscardsClp.Rtvbr

• VS.TxCellDiscardsClp.Nrtvbr

• VS.TxCellDiscardsClp.Abr

• VS.TxCellDiscardsClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20041

I-Range



0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 43 VS.RxCellDiscardsClp - #20042

A-Description

This attribute counts the cells (CLP=1) which are discarded after being received during the col-lection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.RxCellDiscardsClp.Cbr

• VS.RxCellDiscardsClp.Rtvbr

• VS.RxCellDiscardsClp.Nrtvbr

• VS.RxCellDiscardsClp.Abr

• VS.RxCellDiscardsClp.Ubr

F-Object Instance

AtmPort

G-Switching



NA

H-3GPP Compliance

N-#20042

I-Range

0..2^64-1

J-Unit

cell

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 44 VS.TxFrameDiscardsClp - #20043

A-Description

This attribute counts the frames (CLP=1) which are discarded before being transmitted duringthe collection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type

• VS.TxFrameDiscardsClp.Cbr

• VS.TxFrameDiscardsClp.Rtvbr

• VS.TxFrameDiscardsClp.Nrtvbr

• VS.TxFrameDiscardsClp.Abr



• VS.TxFrameDiscardsClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20043

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd

Table 45 VS.RxFrameDiscardsClp - #20044

A-Description

This attribute counts the frames (CLP=1) which are discarded after being received during thecollection interval by ATM service category.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result







E-Type



• VS.RxFrameDiscardsClp.Cbr

• VS.RxFrameDiscardsClp.Rtvbr

• VS.RxFrameDiscardsClp.Nrtvbr

• VS.RxFrameDiscardsClp.Abr

• VS.RxFrameDiscardsClp.Ubr

F-Object Instance

AtmPort

G-Switching

NA

H-3GPP Compliance

N-#20044

I-Range

0..2^64-1

J-Unit

frame

K-Available Release

V2v0

L-Aggregation Rule

Radd



5.2 Logical Processor Use

These counters apply to both I-node and A-node Lp (Logical Processor) locations. All of them arevendor-specific, and none of them are used to compute 3GPP counters. In UMTS 04.1, with UTRANversion UA04.1, Passport release is PCR6.1. Therefore the ultimate reference for description ofcounters provided by NTPs Passport are to be found in the adequate NTP, see references [R5], [R6],[R7].and [R8]. A subset of the Passport statistics described in Component LP (Logical Processor),Group LP Utilization (Util), and Group Lp Capacity is provided. The Passport Attributes are directlymapped to the counter name: e.g. ATTRIBUTE Lp cpuUtilAvg becomes VS.CpuUtiAvg.


Counter name

#20103 VS.CpuUtilAvg

#20104 VS.CpuUtilAvgMin

#20105 VS.CpuUtilAvgMax

#20106 VS.MemoryCapacity

#20107 VS.MemoryUsageAvg

#20108 VS.MemoryUsageAvgMin

#20109 VS.MemoryUsageAvgMax

#20110 VS.SharedMsgBlockCapacity

#20111 VS.SharedMsgBlockUsageAvg

#20112 VS.SharedMsgBlockUsageAvgMin

#20113 VS.SharedMsgBlockUsageAvgMax

#20114 VS.LocalMsgBlockCapacity

#20115 VS.LocalMsgBlockUsageAvg

#20116 VS.LocalMsgBlockUsageMin

#20117 VS.LocalMsgBlockUsageMax

Table 46 VS.CpuUtilAvg - #20103

A-Description

This attribute indicates an average processor utilization level over the specified time period,timeInterval. This average is calculated based on one minute CPU utilization averages.

B-Collection

CUM

CUMulative

C-Condition (Event)



-

D-Result

one measurement

E-Type

VS.CpuUtilAvg

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20103

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 47 VS.CpuUtilAvgMin - #20104

A-Description

This attribute indicates the minimum processor utilization level over a specified time period,timeInterval. This is based on one minute CPU utilization averages.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.CpuUtilAvgMin



F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20104

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 48 VS.CpuUtilAvgMax - #20105

A-Description

This attribute indicates the maximum processor utilization level over a specified time period,timeInterval. This is based on one minute CPU utilization averages.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.CpuUtilAvgMax

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance



N-#20105

I-Range

0..100

J-Unit

percent

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 49 VS.MemoryCapacity - #20106

A-Description

This attribute indicates the processor cards memory capacity for each type of memory.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

A set of subcounters screened on: Memory type

• Sub-Counter #0 : FastRAM

• Sub-Counter #1 : NormalRAM

• Sub-Counter #2 : SharedRAM

E-Type

• VS.MemoryCapacity.FastRAM

• VS.MemoryCapacity.NormalRAM

• VS.MemoryCapacity.SharedRAM

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance



N-#20106

I-Range

0..2^32-1

J-Unit

event

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 50 VS.MemoryUsageAvg - #20107

A-Description

This attribute indicates the processor's average memory utilization for each type of memory inthe specified collection interval. This is calculated using 15 second samples.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result





E-Type

• VS.MemoryUsageAvg.FastRAM

• VS.MemoryUsageAvg.NormalRAM

• VS.MemoryUsageAvg.SharedRAM

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance



N-#20107

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 51 VS.MemoryUsageAvgMin - #20108

A-Description

This attribute indicates the processor's minimum memory utilization for each type of memory inthe specified collection interval. This is calculated using 15 second samples.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result





E-Type

• VS.MemoryUsageAvgMin.FastRAM

• VS.MemoryUsageAvgMin.NormalRAM

• VS.MemoryUsageAvgMin.SharedRAM

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance



N-#20108

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 52 VS.MemoryUsageAvgMax - #20109

A-Description

This attribute indicates the processor's maximum memory utilization for each type of memory inthe specified collection interval. This is calculated using 15 second samples.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result





E-Type

• VS.MemoryUsageAvgMax.FastRAM

• VS.MemoryUsageAvgMax.NormalRAM

• VS.MemoryUsageAvgMax.SharedRAM

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance



N-#20109

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 53 VS.SharedMsgBlockCapacity - #20110

A-Description

This attribute indicates the processor's shared message block memory capacity.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.SharedMsgBlockCapacity

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20110

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release



V2v0

L-Aggregation Rule

Ravg

Table 54 VS.SharedMsgBlockUsageAvg - #20111

A-Description

This attribute indicates the processor's average shared message block memory utilization overa specified collection interval. This is calculated using 15 second samples.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.SharedMsgBlockUsageAvg

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20111

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 55 VS.SharedMsgBlockUsageAvgMin - #20112



A-Description

This attribute indicates the processor's minimum shared message block memory utilizationover a specified collection interval. This is calculated using 15 second samples.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.SharedMsgBlockUsageAvgMin

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20112

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 56 VS.SharedMsgBlockUsageAvgMax - #20113

A-Description

This attribute indicates the processor's maximum shared message block memory utilizationover a specified collection interval. This is calculated using 15 second samples.

B-Collection

CUM

CUMulative



C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.SharedMsgBlockUsageAvgMax

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20113

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Rmax

Table 57 VS.LocalMsgBlockCapacity - #20114

A-Description

This attribute indicates the processor's local message block memory capacity. These messageblocks are used for local messaging on the card.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type



VS.LocalMsgBlockCapacity

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20114

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 58 VS.LocalMsgBlockUsageAvg - #20115

A-Description

This attribute indicates the processor's average memory utilization of message blocks used forlocal messaging on the card, calculated over a specified collection interval. This is calculatedusing 15 second samples.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.LocalMsgBlockUsageAvg

F-Object Instance

Lp

G-Switching



NA

H-3GPP Compliance

N-#20115

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Ravg

Table 59 VS.LocalMsgBlockUsageMin - #20116

A-Description

This attribute indicates the processor's minimum memory utilization of message blocks usedfor local messaging on the card, calculated over a specified collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.LocalMsgBlockUsageMin

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20116

I-Range

0..2^32-1



J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule

Rmin

Table 60 VS.LocalMsgBlockUsageMax - #20117

A-Description

This attribute indicates the processor's maximum memory utilization of message blocks usedfor local messaging on the card, calculated over a specified collection interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.LocalMsgBlockUsageMax

F-Object Instance

Lp

G-Switching

NA

H-3GPP Compliance

N-#20117

I-Range

0..2^32-1

J-Unit

kbyte

K-Available Release

V2v0

L-Aggregation Rule



Rmax



5.3 Adjunct Processor Stats


Counter name

#20201 VS.ApCpuUtilizationHistogram

#20202 VS.ApCpuUtilizationAvg

#20203 VS.ApMemoryCapacity

#20204 VS.ApMemoryUtilization

#20205 VS.ApMemoryUsageAvgMin

#20206 VS.ApMemoryUsageAvgMax

#20207 VS.ApSharedMsgBlockCapacity

#20208 VS.ApSharedMsgBlockUsageAvg

#20209 VS.ApSharedMsgBlockUsageAvgMin

#20210 VS.ApSharedMsgBlockUsageAvgMax

#20211 VS.ApLocalMsgBlockCapacity

#20212 VS.ApLocalMsgBlockUsageAvg

#20213 VS.ApLocalMsgBlockUsageAvgMin

#20214 VS.ApLocalMsgBlockUsageAvgMax

Table 61 VS.ApCpuUtilizationHistogram - #20201

A-Description

This attribute indicates a histogram of Adjunct Processor's CPU utilization. Every 100 milli-seconds, the average CPU utilization for the previous 100 millisecond interval is used to selecta bin from the vector and the bin is incremented. The elements of the vector correlate withCPU utilization as follows: index 0, CPU utilization from 0% to less than 50%; index 1, CPUutilization from 50% to less than 60%, index 2, from 60% to less than 70%, index 3, from 70%to less than 80%, index 4 from 80% to less than 85%; element 5, from 85% to less than 90%;element 6, form 90% to less than 95%; index 7, from 95% to less than 100%; index 8, 100%.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

A set of subcounters screened on: ap_cpu_histogram



• Sub-Counter #0 : less than 50%

• Sub-Counter #1 : greater or equal than 50% and less than 60%







• Sub-Counter #8 : equal to 100 %

E-Type

• VS.ApCpuUtilizationHistogram.LT050








• VS.ApCpuUtilizationHistogram.EQ100

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20201

I-Range

0..10000

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Radd



Table 62 VS.ApCpuUtilizationAvg - #20202

A-Description

This attribute indicates the processor average CPU utilization over the collection interval. Thisis calculated using data sampled every 100 milliseconds.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApCpuUtilizationAvg

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20202

I-Range

0..100

J-Unit

percentage

K-Available Release

V5.0

L-Aggregation Rule

Ravg

Table 63 VS.ApMemoryCapacity - #20203

A-Description

This attribute indicates the total amount of memory present on the Adjunct Processor.

B-Collection



CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApMemoryCapacity

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20203

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Ravg

Table 64 VS.ApMemoryUtilization - #20204

A-Description

This attribute indicates the processor's average memory utilization in the collection interval.This is calculated using data sampled every second.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result



one measurement

E-Type

VS.ApMemoryUtilization

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20204

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Ravg

Table 65 VS.ApMemoryUsageAvgMin - #20205

A-Description

This attribute indicates the Adjunct Processor's minimum memory utilization in the collection in-terval. This is calculated using data sampled every second.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApMemoryUsageAvgMin

F-Object Instance

Ap



G-Switching

NA

H-3GPP Compliance

N-#20205

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Rmin

Table 66 VS.ApMemoryUsageAvgMax - #20206

A-Description

This attribute indicates the Adjunct Processor's maximum memory utilization in the collectioninterval. This is calculated using data sampled every second.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApMemoryUsageAvgMax

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20206

I-Range



0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Rmax

Table 67 VS.ApSharedMsgBlockCapacity - #20207

A-Description

This attribute indicates the Adjunct Processor's shared message block memory capacity.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApSharedMsgBlockCapacity

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20207

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule



Ravg

Table 68 VS.ApSharedMsgBlockUsageAvg - #20208

A-Description

This attribute indicates the Adjunct processor's average shared message block memory utiliza-tion over the collection interval. This is calculated using data sampled every second.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApSharedMsgBlockUsageAvg

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20208

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Ravg

Table 69 VS.ApSharedMsgBlockUsageAvgMin - #20209

A-Description

This attribute indicates the Adjunct Processor's minimum shared message block memory utiliz-ation over the collection interval. This is calculated using data sampled every second.



B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApSharedMsgBlockUsageAvgMin

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20209

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Rmin

Table 70 VS.ApSharedMsgBlockUsageAvgMax - #20210

A-Description

This attribute indicates the Adjunct Processor's maximum shared message block memory util-ization over the collection interval. This is calculated using data sampled every second.

B-Collection

CUM

CUMulative

C-Condition (Event)

-



D-Result

one measurement

E-Type

VS.ApSharedMsgBlockUsageAvgMax

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20210

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Rmax

Table 71 VS.ApLocalMsgBlockCapacity - #20211

A-Description

This attribute indicates the Adjunct Processor's local message block memory capacity. Thesemessage blocks are used for local messaging on the card.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApLocalMsgBlockCapacity

F-Object Instance



Ap

G-Switching

NA

H-3GPP Compliance

N-#20211

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Ravg

Table 72 VS.ApLocalMsgBlockUsageAvg - #20212

A-Description

This attribute indicates the Adjunct Processor's average memory utilization of message blocksused for local messaging, calculated over the collection interval using the data sampled everysecond.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApLocalMsgBlockUsageAvg

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance



N-#20212

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule

Ravg

Table 73 VS.ApLocalMsgBlockUsageAvgMin - #20213

A-Description

This attribute indicates the Adjunct Processor's minimum memory utilization of message blocksused for local messaging, calculated over the collection interval using data sampled everysecond.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApLocalMsgBlockUsageAvgMin

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20213

I-Range

0..2^31-1

J-Unit



kbyte

K-Available Release

V5.0

L-Aggregation Rule

Rmin

Table 74 VS.ApLocalMsgBlockUsageAvgMax - #20214

A-Description

This attribute indicates the Adjunct Processor's maximum memory utilization of messageblocks used for local messaging, calculated over the collection interval using data sampledevery second.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.ApLocalMsgBlockUsageAvgMax

F-Object Instance

Ap

G-Switching

NA

H-3GPP Compliance

N-#20214

I-Range

0..2^31-1

J-Unit

kbyte

K-Available Release

V5.0

L-Aggregation Rule



Rmax



5.4 ACCOUNT ATM Vcc


Counter name

#30001 VS.AcVccIngressCellCountClp0

#30002 VS.AcVccIngressCellCountClp01

#30003 VS.AcVccEgressCellCountClp0

#30004 VS.AcVccEgressCellCountClp01

#30005 VS.AcVccIngressDiscardedClp0

#30006 VS.AcVccIngressDiscardedClp01

#30007 VS.AcVccEgressDiscardedClp0

#30008 VS.AcVccEgressDiscardedClp01

Table 75 VS.AcVccIngressCellCountClp0 - #30001

A-Description

This Attribute contains the number of high priority cells (with CLP=0) received from the link dur-ing the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccIngressCellCountClp0

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30001

I-Range



0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 76 VS.AcVccIngressCellCountClp01 - #30002

A-Description

This Attribute indicates the total number of cells (with CLP=0 or CLP=1) received from the linkduring the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccIngressCellCountClp01

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30002

I-Range

0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0



L-Aggregation Rule

Radd

Table 77 VS.AcVccEgressCellCountClp0 - #30003

A-Description

This Attribute contains the number of high priority cells (with CLP=0) transmitted on the linkduring the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccEgressCellCountClp0

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30003

I-Range

0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 78 VS.AcVccEgressCellCountClp01 - #30004

A-Description



This Attribute indicates the total number of cells (with CLP=0 or CLP=1) transmitted on the linkduring the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccEgressCellCountClp01

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30004

I-Range

0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 79 VS.AcVccIngressDiscardedClp0 - #30005

A-Description

This Attribute indicates the number of high priority cells or frames (with CLP=0) received fromthe link and discarded (not transmitted to the switch) during the accounting interval. - For con-sistency with other operational measurements for various applications, the count is expressedeither as number of cells or as number of frames. - For applications: Loop, CES, Wireless,PVG, and ABS, the count is expressed in cells. - For applications: FrAtm, PORS, ATMMPE,and control channels for SVCs, the count is expressed in frames. - For applications: Test,SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 isused, the count is expressed in frames.



B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccIngressDiscardedClp0

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30005

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 80 VS.AcVccIngressDiscardedClp01 - #30006

A-Description

This Attribute indicates the total number of cells or frames (with CLP=0 or CLP=1) receivedfrom the link and discarded (not transmitted to the switch) during the accounting interval. Forconsistency with other operational measurements for various applications, the count is ex-pressed either as number of cells or as number of frames. For applications: Loop, CES, Wire-less, PVG, and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATM-MPE, and control channels for SVCs, the count is expressed in frames. For applications: Test,SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 isused, the count is expressed in frames.

B-Collection



CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccIngressDiscardedClp01

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30006

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 81 VS.AcVccEgressDiscardedClp0 - #30007

A-Description

This Attribute indicates the number of high priority cells or frames (with CLP=0) received fromthe switch and discarded (not transmitted on the link) during the accounting interval. For con-sistency with other operational measurements for various applications, the count is expressedeither as number of cells or as number of frames. For applications: Loop, CES, Wireless, PVG,and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATMMPE, and con-trol channels for SVCs, the count is expressed in frames. For applications: Test, SVCs, SVPs,and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 is used, the countis expressed in frames.

B-Collection

CUM



CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccEgressDiscardedClp0

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30007

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 82 VS.AcVccEgressDiscardedClp01 - #30008

A-Description

This Attribute indicates the total number of cells or frames (with CLP=0 or CLP=1) receivedfrom the switch and discarded (not transmitted on the link) during the accounting interval. Forconsistency with other operational measurements for various applications, the count is ex-pressed either as number of cells or as number of frames. For applications: Loop, CES, Wire-less, PVG, and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATM-MPE, and control channels for SVCs, the count is expressed in frames. For applications: Test,SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 isused, the count is expressed in frames.

B-Collection

CUM

CUMulative



C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVccEgressDiscardedClp01

F-Object Instance

Vcc

G-Switching

NA

H-3GPP Compliance

No-#30008

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd



5.5 ACCOUNT ATM Vpc


Counter name

#30101 VS.AcVpcIngressCellCountClp0

#30102 VS.AcVpcIngressCellCountClp01

#30103 VS.AcVpcEgressCellCountClp0

#30104 VS.AcVpcEgressCellCountClp01

#30105 VS.AcVpcIngressDiscardedClp0

#30106 VS.AcVpcIngressDiscardedClp01

#30107 VS.AcVpcEgressDiscardedClp0

#30108 VS.AcVpcEgressDiscardedClp01

Table 83 VS.AcVpcIngressCellCountClp0 - #30101

A-Description

This Attribute contains the number of high priority cells (with CLP=0) received from the link dur-ing the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcIngressCellCountClp0

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30101

I-Range



0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 84 VS.AcVpcIngressCellCountClp01 - #30102

A-Description

This Attribute indicates the total number of cells (with CLP=0 or CLP=1) received from the linkduring the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcIngressCellCountClp01

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30102

I-Range

0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0



L-Aggregation Rule

Radd

Table 85 VS.AcVpcEgressCellCountClp0 - #30103

A-Description

This Attribute contains the number of high priority cells (with CLP=0) transmitted on the linkduring the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcEgressCellCountClp0

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30103

I-Range

0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 86 VS.AcVpcEgressCellCountClp01 - #30104

A-Description



This Attribute indicates the total number of cells (with CLP=0 or CLP=1) transmitted on the linkduring the accounting interval.

B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcEgressCellCountClp01

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30104

I-Range

0..2^63-1

J-Unit

ATM cells

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 87 VS.AcVpcIngressDiscardedClp0 - #30105

A-Description

This Attribute indicates the number of high priority cells or frames (with CLP=0) received fromthe link and discarded (not transmitted to the switch) during the accounting interval. - For con-sistency with other operational measurements for various applications, the count is expressedeither as number of cells or as number of frames. - For applications: Loop, CES, Wireless,PVG, and ABS, the count is expressed in cells. - For applications: FrAtm, PORS, ATMMPE,and control channels for SVCs, the count is expressed in frames. - For applications: Test,SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 isused, the count is expressed in frames.



B-Collection

CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcIngressDiscardedClp0

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30105

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 88 VS.AcVpcIngressDiscardedClp01 - #30106

A-Description

This Attribute indicates the total number of cells or frames (with CLP=0 or CLP=1) receivedfrom the link and discarded (not transmitted to the switch) during the accounting interval. Forconsistency with other operational measurements for various applications, the count is ex-pressed either as number of cells or as number of frames. For applications: Loop, CES, Wire-less, PVG, and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATM-MPE, and control channels for SVCs, the count is expressed in frames. For applications: Test,SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 isused, the count is expressed in frames.

B-Collection



CUM

CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcIngressDiscardedClp01

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30106

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 89 VS.AcVpcEgressDiscardedClp0 - #30107

A-Description

This Attribute indicates the number of high priority cells or frames (with CLP=0) received fromthe switch and discarded (not transmitted on the link) during the accounting interval. For con-sistency with other operational measurements for various applications, the count is expressedeither as number of cells or as number of frames. For applications: Loop, CES, Wireless, PVG,and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATMMPE, and con-trol channels for SVCs, the count is expressed in frames. For applications: Test, SVCs, SVPs,and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 is used, the countis expressed in frames.

B-Collection

CUM



CUMulative

C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcEgressDiscardedClp0

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30107

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd

Table 90 VS.AcVpcEgressDiscardedClp01 - #30108

A-Description

This Attribute indicates the total number of cells or frames (with CLP=0 or CLP=1) receivedfrom the switch and discarded (not transmitted on the link) during the accounting interval. Forconsistency with other operational measurements for various applications, the count is ex-pressed either as number of cells or as number of frames. For applications: Loop, CES, Wire-less, PVG, and ABS, the count is expressed in cells. For applications: FrAtm, PORS, ATM-MPE, and control channels for SVCs, the count is expressed in frames. For applications: Test,SVCs, SVPs, and MPLS, the count is expressed in cells unless AAL5 is used. When AAL5 isused, the count is expressed in frames.

B-Collection

CUM

CUMulative



C-Condition (Event)

-

D-Result

one measurement

E-Type

VS.AcVpcEgressDiscardedClp01

F-Object Instance

Vpc

G-Switching

NA

H-3GPP Compliance

No-#30108

I-Range

0..2^63-1

J-Unit

ATM cells or frames

K-Available Release

V5.0

L-Aggregation Rule

Radd



6 MSS Counters Index

• #20001 VS.ProvRate

• #20002 VS.ActualRate

• #20003 VS.TxUtilization

• #20004 VS.RxUtilization

• #20005 VS.TxMaxCellRate

• #20006 VS.TxMinCellRate

• #20007 VS.TxAvgCellRate

• #20008 VS.RxMaxCellRate

• #20009 VS.RxMinCellRate

• #20010 VS.RxAvgCellRate

• #20011 VS.TxMaxCellRateClp

• #20012 VS.TxMinCellRateClp

• #20013 VS.TxAvgCellRateClp

• #20014 VS.RxMaxCellRateClp

• #20015 VS.RxMinCellRateClp

• #20016 VS.RxAvgCellRateClp

• #20017 VS.TxCellDiscards

• #20018 VS.RxCellDiscards

• #20019 VS.TxFrameDiscards

• #20020 VS.RxFrameDiscards

• #20021 VS.TxCellDiscardsClp

• #20022 VS.RxCellDiscardsClp

• #20023 VS.TxFrameDiscardsClp

• #20024 VS.RxFrameDiscardsClp

• #20025 VS.TxMaxCellRate

• #20026 VS.TxMinCellRate

• #20027 VS.TxAvgCellRate

• #20028 VS.RxMaxCellRate

• #20029 VS.RxMinCellRate

• #20030 VS.RxAvgCellRate

• #20031 VS.TxMaxCellRateClp



• #20032 VS.TxMinCellRateClp

• #20033 VS.TxAvgCellRateClp

• #20034 VS.RxMaxCellRateClp

• #20035 VS.RxMinCellRateClp

• #20036 VS.RxAvgCellRateClp

• #20037 VS.TxCellDiscards

• #20038 VS.RxCellDiscards

• #20039 VS.TxFrameDiscards

• #20040 VS.RxFrameDiscards

• #20041 VS.TxCellDiscardsClp

• #20042 VS.RxCellDiscardsClp

• #20043 VS.TxFrameDiscardsClp

• #20044 VS.RxFrameDiscardsClp

• #20103 VS.CpuUtilAvg

• #20104 VS.CpuUtilAvgMin

• #20105 VS.CpuUtilAvgMax

• #20106 VS.MemoryCapacity

• #20107 VS.MemoryUsageAvg

• #20108 VS.MemoryUsageAvgMin

• #20109 VS.MemoryUsageAvgMax

• #20110 VS.SharedMsgBlockCapacity

• #20111 VS.SharedMsgBlockUsageAvg

• #20112 VS.SharedMsgBlockUsageAvgMin

• #20113 VS.SharedMsgBlockUsageAvgMax

• #20114 VS.LocalMsgBlockCapacity

• #20115 VS.LocalMsgBlockUsageAvg

• #20116 VS.LocalMsgBlockUsageMin

• #20117 VS.LocalMsgBlockUsageMax

• #20201 VS.ApCpuUtilizationHistogram

• #20202 VS.ApCpuUtilizationAvg

• #20203 VS.ApMemoryCapacity

• #20204 VS.ApMemoryUtilization

• #20205 VS.ApMemoryUsageAvgMin

• #20206 VS.ApMemoryUsageAvgMax



• #20207 VS.ApSharedMsgBlockCapacity

• #20208 VS.ApSharedMsgBlockUsageAvg

• #20209 VS.ApSharedMsgBlockUsageAvgMin

• #20210 VS.ApSharedMsgBlockUsageAvgMax

• #20211 VS.ApLocalMsgBlockCapacity

• #20212 VS.ApLocalMsgBlockUsageAvg

• #20213 VS.ApLocalMsgBlockUsageAvgMin

• #20214 VS.ApLocalMsgBlockUsageAvgMax

• #30001 VS.AcVccIngressCellCountClp0

• #30002 VS.AcVccIngressCellCountClp01

• #30003 VS.AcVccEgressCellCountClp0

• #30004 VS.AcVccEgressCellCountClp01

• #30005 VS.AcVccIngressDiscardedClp0

• #30006 VS.AcVccIngressDiscardedClp01

• #30007 VS.AcVccEgressDiscardedClp0

• #30008 VS.AcVccEgressDiscardedClp01

• #30101 VS.AcVpcIngressCellCountClp0

• #30102 VS.AcVpcIngressCellCountClp01

• #30103 VS.AcVpcEgressCellCountClp0

• #30104 VS.AcVpcEgressCellCountClp01

• #30105 VS.AcVpcIngressDiscardedClp0

• #30106 VS.AcVpcIngressDiscardedClp01

• #30107 VS.AcVpcEgressDiscardedClp0

• #30108 VS.AcVpcEgressDiscardedClp01



Wireless Service Provider SolutionsW-CDMAUMTS Access Network Counters Reference - Volume 3: MSS Counters

Copyright © 2003-2007 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be alteredonly by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures accessto the current issue. Any hardcopies taken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except asexpressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose theinformation only to its employees with a need to know, and shall protect the information from disclosure and dissemination to thirdparties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information containedherein. If you have received this document in error, please notify the sender and destroy it immediately.

Document number: NN-20500-028Document issue: 08.03Document status: StandardSystem Release: OAM05.2Date: November 2007

Documents

NN-20500-028P3 (MSS Counters) 08.03 Standard November 2007