4motion ver.2.5m_performance management_090908

8/7/2019 4Motion Ver.2.5M_Performance Management_090908

1/83

Reference GuideSoftware Version: 2.5.2September 2009P/N 215342

4Motion Performance Management


2/83

Document History

4Motion Performance Management ii Reference Guide

Do c u m e n t H is t o r y

Topic Description Date IssuedThis is the manuals first publication Release 2.5,

December 2008

NPU Data (Backhaul) PortSection 3.1.1.1

Following counters have been changed to typeCounter64:

cntNpuBckhlPortInOctet

cntNpuBckhlPortOutOctet

Release 2.5.2,May 2009

NPU Management Port

Section 3.1.1.2

Following counters have been changed to type

Counter64:

cntNpuMgmtPortInOctet

cntNpuMgmtPortOutOctet

Release 2.5.2,

May 2009

NPU Cascade PortSection 3.1.1.3


cntNpuCascPortInOctet

cntNpuCascPortOutOctet


NPU AU Port Section 3.1.1.4


cntAuPortInOctet

cntAuPortOutOctet


NPU Internal Management InterfaceSection 3.1.1.5


cntNpuIntMgmtInOctet

cntNpuIntMgmtOutOctet


NPU External Management InterfaceSection 3.1.1.6


cntNpuExtMgmtInOctet

cntNpuExtMgmtOutOctet



3/83

Document History

4Motion Performance Management iii Reference Guide

NPU Local Management InterfaceSection 3.1.1.7


cntNpuLclMgmtInOctet

cntNpuLclMgmtOutOctet


NPU Bearer InterfaceSection 3.1.1.8


cntNpuBearerInOctet

cntNpuBearerOutOctet


AAA ClientSection 3.1.3.3

New counter: adAaaSwitchoverRetryFail Release 2.5.2,May 2009

TrafficSection 3.2.3

New counters added (6 parameters, startingfrom bsTotalConnectionsUgs). These countersare available only in collected files (notsupported in the MIB, not available for real-timemonitoring).


MobilitySection 3.2.4

New counters added (4 parameters, startingfrom bsHoMSHoReqReceived). The newcounters are available also for real-timemonitoring and are supported by MIB.


UtilizationSection 3.2.5

New counters added: bsActiveMsPeak.

Error correction: AllocatedSlotsDataZoneUlcounter appeared twice. The secondappearance was corrected toUsedSlotsDataZoneUl.


Idle ModeSection 3.2.7

New counters group Release 2.5.2,May 2009

Fast Feedback CQI HandlingSection 3.2.8


Ack/Nack Channel HandlingSection 3.2.9


End Transaction UpdateSection 3.2.10


DL Frame Data Zone HistogramsSection 3.2.11


TxR1 Net Traffic countersSection 3.2.12


Topic Description Date Issued


4/83

Document History

4Motion Performance Management iv Reference Guide

RxR1 Net Traffic countersSection 3.2.13


TxR1 Total Traffic countersSection 3.2.14


RxR1 Total Traffic countersSection 3.2.15


Traffic CountersSection 3.2.3

DL HARQ Sub-Bursts Drops countersSection 3.2.16

DL HARQ Transmissions countersSection 3.2.17

11 BS DL HARQ Transmissions counters perAll Services were removed. Replaced by 55per service type counters in the new DL HARQSub-Bursts Drops counters group

11 BS DL HARQ SB Drops counters per All

Services were removed. Replaced by 55 perservice type counters in the new DL HARQTransmissions counters group.


All MS Basic ModeSection 3.2.19

Does not include MSs included in Specific MSAdvanced Mode list


Specific MS Advanced ModeSection 3.2.20


Collection controlSection 2.2.2

Updated names, added support for new groups,updated syntax of commands.


Real-Time Monitoring Using CLI Added throughout the book. Release 2.5.2,May 2009

Counters that are not fully supported incurrent release

Add indications on counters that are not fullysupported in current release and should not beused.


Authenticator countersSection 3.1.3.4

All counters (including eapIdReqRtx,eapInvalidNaiRealm) are supported in MIB andavailable for real-time monitoring.


SFA CountersSection 3.1.3.1

Added new Multicast counters (not applicablefor current release).

Release 2.5.2May 2009

Traffic CountersSection 3.2.3

The following changed from counter32 togauge32:bsTotalConnectionsUgs,bsTotalConnectionsRtvr,bsTotalConnectionsNrtvr,bsTotalConnectionsBe,bsTotalConnectionsErtvr,bsTotalRegistationsMss.

Release 2.5.2June 2009



5/83

Document History

4Motion Performance Management v Reference Guide

AAA Client CountersSection 3.1.3.3

Added 6 new counters for volume accounting:

radAccStartReqTx

radAccStopReqTx

radAccInterimReqTx

radAccExpTx

radAccAcceptRx

radAccDropRx

Release 2.5.2July 2009



6/83

Legal Rights

4Motion Performance Management vi Reference Guide

Lega l R igh t s

Copyright 2009 Alvarion Ltd. All rights reserved.

The material contained herein is proprietary, privileged, and confidential andowned by Alvarion or its third party licensors. No disclosure thereof shall be madeto third parties without the express written permission of Alvarion Ltd.

Alvarion Ltd. reserves the right to alter the equipment specifications anddescriptions in this publication without prior notice. No part of this publicationshall be deemed to be part of any contract or warranty unless specificallyincorporated by reference into such contract or warranty.

Trade Names

Alvarion

, BreezeCOM

, WALKair

, WALKnet

, BreezeNET

, BreezeACCESS

,BreezeLINK , BreezeMAX , BreezeLITE , BreezePHONE , 4Motion ,

BreezeCONFIG , MGW , eMGW and/or other products and/or servicesreferenced here in are either registered trademarks, trademarks or service marksof Alvarion Ltd.

All other names are or may be the trademarks of their respective owners.

WiMAX Forum is a registered trademark of the WiMAX Forum. WiMAX, theWiMAX Forum logo, WiMAX Forum Certified, and the WiMAX Forum Certifiedlogo are trademarks of the WiMAX Forum.

St a t e m e n t o f C o n di t i o n s

The information contained in this manual is subject to change without notice.Alvarion Ltd. shall not be liable for errors contained herein or for incidental orconsequential damages in connection with the furnishing, performance, or use of this manual or equipment supplied with it.

Warr an t i e s and Disc la imers

All Alvarion Ltd. (Alvarion) products purchased from Alvarion or through any of Alvarion's authorized resellers are subject to the following warranty and product

liability terms and conditions.

Exclus ive War r an ty

(a) Alvarion warrants that the Product hardware it supplies and the tangiblemedia on which any software is installed, under normal use and conditions, willbe free from significant defects in materials and workmanship for a period of fourteen (14) months from the date of shipment of a given Product to Purchaser(the Warranty Period). Alvarion will, at its sole option and as Purchaser's sole


7/83

Legal Rights

4Motion Performance Management vii Reference Guide

remedy, repair or replace any defective Product in accordance with Alvarion'standard R&R procedure.

(b) With respect to the Firmware, Alvarion warrants the correct functionalityaccording to the attached documentation, for a period of fourteen (14) month frominvoice date (the Warranty Period). During the Warranty Period, Alvarion mayrelease to its Customers firmware updates, which include additional performanceimprovements and/or bug fixes, upon availability (the Warranty). Bug fixes,temporary patches and/or workarounds may be supplied as Firmware updates.

Additional hardware, if required, to install or use Firmware updates must bepurchased by the Customer. Alvarion will be obligated to support solely the two (2)most recent Software major releases.

ALVARION SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTINGAND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY PURCHASER'S OR ANY THIRDPERSON'S MISUSE, NEGLIGENCE, IMPROPER INSTALLATION OR IMPROPERTESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR ANY OTHER CAUSEBEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE,LIGHTNING OR OTHER HAZARD.

Disc la imer

(a) The Software is sold on an AS IS basis. Alvarion, its affiliates or its licensors

MAKE NO WARRANTIES, WHATSOEVER, WHETHER EXPRESS OR IMPLIED,WITH RESPECT TO THE SOFTWARE AND THE ACCOMPANYINGDOCUMENTATION. ALVARION SPECIFICALLY DISCLAIMS ALL IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE AND NON-INFRINGEMENT WITH RESPECT TO THE SOFTWARE.UNITS OF PRODUCT (INCLUDING ALL THE SOFTWARE) DELIVERED TOPURCHASER HEREUNDER ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE OR RESALE INAPPLICATIONS WHERE THE FAILURE, MALFUNCTION OR INACCURACY OFPRODUCTS CARRIES A RISK OF DEATH OR BODILY INJURY OR SEVERE

PHYSICAL OR ENVIRONMENTAL DAMAGE (HIGH RISK ACTIVITIES). HIGHRISK ACTIVITIES MAY INCLUDE, BUT ARE NOT LIMITED TO, USE AS PART OFON-LINE CONTROL SYSTEMS IN HAZARDOUS ENVIRONMENTS REQUIRINGFAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEARFACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIRTRAFFIC CONTROL, LIFE SUPPORT MACHINES, WEAPONS SYSTEMS OROTHER APPLICATIONS REPRESENTING A SIMILAR DEGREE OF POTENTIAL HAZARD. ALVARION SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIEDWARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES.


8/83

Legal Rights

4Motion Performance Management viii Reference Guide

(b) PURCHASER'S SOLE REMEDY FOR BREACH OF THE EXPRESSWARRANTIES ABOVE SHALL BE REPLACEMENT OR REFUND OF THEPURCHASE PRICE AS SPECIFIED ABOVE, AT ALVARION'S OPTION. TO THE

FULLEST EXTENT ALLOWED BY LAW, THE WARRANTIES AND REMEDIES SET FORTH IN THIS AGREEMENT ARE EXCLUSIVE AND IN LIEU OF ALL OTHERWARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BYOPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES, TERMS OR CONDITIONS OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY,CORRESPONDENCE WITH DESCRIPTION, NON-INFRINGEMENT, ANDACCURACY OF INFORMATION GENERATED. ALL OF WHICH ARE EXPRESSLYDISCLAIMED. ALVARION' WARRANTIES HEREIN RUN ONLY TO PURCHASER,AND ARE NOT EXTENDED TO ANY THIRD PARTIES. ALVARION NEITHER

ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANYOTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION,MAINTENANCE OR USE OF ITS PRODUCTS.

L i m i t a t i o n o f L i ab i l i t y

(a) ALVARION SHALL NOT BE LIABLE TO THE PURCHASER OR TO ANY THIRDPARTY, FOR ANY LOSS OF PROFITS, LOSS OF USE, INTERRUPTION OFBUSINESS OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE ORCONSEQUENTIAL DAMAGES OF ANY KIND, WHETHER ARISING UNDERBREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY

OR OTHERWISE AND WHETHER BASED ON THIS AGREEMENT OROTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

(b) TO THE EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE LIABILITY FOR DAMAGES HEREUNDER OF ALVARION OR ITS EMPLOYEESOR AGENTS EXCEED THE PURCHASE PRICE PAID FOR THE PRODUCT BYPURCHASER, NOR SHALL THE AGGREGATE LIABILITY FOR DAMAGES TO ALL PARTIES REGARDING ANY PRODUCT EXCEED THE PURCHASE PRICE PAIDFOR THAT PRODUCT BY THAT PARTY (EXCEPT IN THE CASE OF A BREACH OFA PARTY'S CONFIDENTIALITY OBLIGATIONS).

Disposa l o f Elec t ron ic and E lec t r i ca l Was te

Disposal of Electronic and Electrical Waste

Pursuant to the WEEE EU Directive electronic and electrical waste must not be disposed of withunsorted waste. Please contact your local recycling authority for disposal of this product.


9/83

Important Notice

4Motion Performance Management ix Reference Guide

I m p o r t a n t N o t i c e

This user manual is delivered subject to the following conditions and restrictions:

This manual contains proprietary information belonging to Alvarion Ltd. Suchinformation is supplied solely for the purpose of assisting properly authorizedusers of the respective Alvarion products.

No part of its contents may be used for any other purpose, disclosed to anyperson or firm or reproduced by any means, electronic and mechanical,without the express prior written permission of Alvarion Ltd.

The text and graphics are for the purpose of illustration and reference only.

The specifications on which they are based are subject to change withoutnotice.

The software described in this document is furnished under a license. Thesoftware may be used or copied only in accordance with the terms of thatlicense.

Information in this document is subject to change without notice. Corporateand individual names and data used in examples herein are fictitious unlessotherwise noted.

Alvarion Ltd. reserves the right to alter the equipment specifications anddescriptions in this publication without prior notice. No part of thispublication shall be deemed to be part of any contract or warranty unlessspecifically incorporated by reference into such contract or warranty.

The information contained herein is merely descriptive in nature, and does notconstitute an offer for the sale of the product described herein.

Any changes or modifications of equipment, including opening of the

equipment not expressly approved by Alvarion Ltd. will void equipmentwarranty and any repair thereafter shall be charged for. It could also void theuser's authority to operate the equipment.


10/83

Contents

4Motion Performance Management x Reference Guide

C o n t e n t s

1. Perf or m anc e Para m et er s Ty pes .. . .. . . .. . . .. . . .. . .. . . .. . . .. . . .. . .. . . .. . . .. . . .. . . .. . . .. . . 1

2. Pe rf or m an c e Ma nag em en t Met ho ds .. . . .. . .. . . .. . . .. . . .. . . .. . . .. . .. . . .. . . .. . .. . . .. . . .. 1

2.1 Real-Time Performance Monitoring............................................................................1

2.2 Performance Parameters Collection ..........................................................................3

2.2.1 Aggregation Period ............................................................................................. 3

2.2.2 Collection Control................................................................................................ 3

2.2.3 Collected Data Manipulation ...............................................................................9

2.2.4 Collected Files Creation and Storage ................................................................. 9

3. Performance Parameters .................................................................. 11

3.1 Parameters Managed by the NPU.............................................................................11

3.1.1 Connectivity....................................................................................................... 11

3.1.2 NPU................................................................................................................... 22

3.1.3 ASNGW.............................................................................................................22

3.2 Parameters Managed by AU......................................................................................32

3.2.1 De-Registration ................................................................................................. 33

3.2.2 Network Entry (NE) ........................................................................................... 33

3.2.3 Traffic ................................................................................................................35

3.2.4 Mobility ..............................................................................................................38

3.2.5 Utilization........................................................................................................... 42

3.2.6 Integrity .............................................................................................................43

3.2.7 Idle Mode .......................................................................................................... 49

3.2.8 Fast Feedback CQI Handling............................................................................ 51

3.2.9 Ack/Nack Channel Handling .............................................................................51


11/83

Contents

4Motion Performance Management xi Reference Guide

3.2.10 End Transaction Update ...................................................................................52

3.2.11 DL Frame Data Zone Histograms .....................................................................53

3.2.12 TxR1 Net Traffic ................................................................................................ 54

3.2.13 RxR1 Net Traffic................................................................................................56

3.2.14 TxR1 Total Traffic..............................................................................................58

3.2.15 RxR1 Total Traffic ............................................................................................. 59

3.2.16 DL HARQ Sub-Bursts Drops.............................................................................60

3.2.17 DL HARQ Transmissions ..................................................................................62

3.2.18 Genera ..............................................................................................................64

3.2.19 All MS Basic Mode ............................................................................................ 67

3.2.20 Specific MS Advanced Mode ............................................................................70


12/83

Performance Parameters Types Real-Time Performance Monitoring

4Motion Performance Management 1 Reference Guide

1 . Pe r fo rm anc e Param e t e r s TypesThe current release of 4Motion system supports two types of performance

parameters:

Counter : A counter is a cumulative count of the monitored event, incrementedby one for each occurrence of the event and wraps around after reaching themaximum value.

Gauge : A gauge represents a dynamic variables that may change in eitherdirection. A Gauge can be either an integer or a real value. In the currentrelease all gauges are 32 bits.

Performance parameters are not reset or initialized, with the following exceptions:

1 After NPU restart.

2 After AU restart (applicable only to performance parameters managed by theAU).

3 If specifically defined, at the end of each collection interval (see PerformanceParameters Collection on page 3 ).

2 . Pe r fo rm anc e Managem en t Me t hods

The 4Motion system supports two methods of performance management:

Real-Time Performance Monitoring

Performance Parameters Collection

2 .1 Re al -T im e Pe rfo r m an c e M on it o r i ng

The operator of a management system may request a view of on-line selectedperformance parameters, to be on-line gathered from the device and presented atalmost real-time. The operator may select the polling interval for theseparameters, as well as their presentation mode. This function is mainly used formaintenance and troubleshooting purposes.

Real-time retrieval of performance parameters by a management system is basedon standard SNMP GET (and GET NEXT) requests using the relevant OIDs.

Each SNMP GET request may refer to one or more performance parameters.


13/83

Performance Management Methods Real-Time Performance Monitoring


Performance parameters are defined by their MIB OIDs. A series of OIDs is used todefine the corresponding series of performance parameters.

The NPU responds to SNMP GET and GETBULK requests with the actualsnapshot of current values of the requested parameters, captured on all requestedparameters as close as possible to the reception of the SNMP GET (or GETBULK)request.

Data may not be available for real-time performance monitoring, due to severalreasons such as: AU plug-out, AU restart, non-associated BS, etc. Such conditioncauses SNMP GET response that includes the failure reason (standard SNMPvalues).

Real-time display of all counters in a selected group is available also via CLI (for

most of the counter groups managed by the NPU).Note that the real-time counters display the cumulative count since lastreset/power-up, with the effect of wrap-around after reaching the maximumvalue.


14/83

Performance Management Methods Performance Parameters Collection


2 .2 Per fo r m an c e Pa ra m et e rs Col le c t io n

This section includes:

Aggregation Period

Collection Control

Collected Data Manipulation

Collected Files Creation and Storage

2.2.1 Aggregation PeriodThe Performance Parameters Collection capability of the 4Motion system enablescollection of data by the NPU during some aggregation period and storing it infiles. The management system can then upload the data files and store them forlater analysis.

The NPU manages the aggregation period start and end, according to the NPURTC (Real Time Clock) and the 1PPS signal. The requested performance data isaccumulated over fixed periods of 900 seconds (15 minutes). The aggregationperiods are aligned to the end of each quarter of an hour period, with accuracy of

better than 10 seconds (10:00, 10:15, 10:30,...

NPU restart due to any cause during the aggregation period results in the totalelimination of all historical performance data, including the data of the relevantperiod.

The following events cause the elimination of the specific AU-related data for thisperiod:

Specific AU restart due to any cause.

Specific AU or BS association / de-association.

2.2.2 Collection Control

2.2.2.1 General

The definition of each performance parameter includes assignment to a specificgroup (table) of a specific MO type. The collection of performance data is doneaccording to the parameters groups.


15/83



The collection of performance data is subject to enabling/disabling at the grouplevel, using standard configuration management actions. Any enabling/disablingof a group takes effect starting at the beginning of the next aggregation period.

The data of parameters of "disabled collection" groups is not included in the filegenerated at the end of the aggregation period.

Enabling/disabling collection and storage of groups of parameters can be done byany of the following options:

Using AlvariSTAR

Using SNMP

Using CLI

Collection and storage of all counters groups except All MS Basic Mode counters,is enabled by default.

2.2.2.2 Using AlvariSTAR

The Performance tab of the Management page contains a list of the groups thatcan be enabled or disabled for performance collection. If a check-box is selected,then collection and storage of the corresponding group of parameters is enabled.

2.2.2.3 Using SNMP

2.2.2.3.1 Parameters Managed by the NPU:The pmNpuCardRelatedCounterGroupsTable contains several entries, one foreach group that can be enabled or disabled. Each entry has two parameters:


16/83



2.2.2.3.2 Parameters Managed by the AU:The pmAuCardRelatedCounterGroupsTable contains several entries, one for eachgroup that can be enabled or disabled. Each entry has the following parameters:

Table 1: pmNpuCardRelatedCounterGroupsEntry Parameters

Parameter Description

pmCounterGroupId Read-only ID of a counter group. Serves also as the tablesindex.:

pmNpuBckhlPort(1)

pmNpuMgmtPort(2)

pmNpuCascPort(3)

pmAuPort(4)

pmNpuIntMgmtIf(5)

pmNpuExtMgmtIf(6)

pmNpuLclMgmtIf(7)

pmNpuBearerIf(8)

pmSfa(9)

pmDataPathFn(10)

pmAaaClient(11)

pmAuthenticator(12)

pmContextFn(13)

pmDHCP-Proxy(14)

pmDHCP-Relay(15)

pmDHCP-Server(16)

pmMSStateChangeFn(20)

groupActivation Activate / Deactivate collection for the specific group:

Activate (1)

Deactivate (2)


17/83



2.2.2.4 Using CLI

2.2.2.4.1 Parameters Managed by the NPU:To enable collection and storage of performance data for a group, run thefollowing command:

Table 2: pmAuCardRelatedCounterGroupsTable Parameters


pmAuCardRelatedCounterGroupId Read-only ID of a counter group. Serves alsoas the tables index.:

pmBsDeRegistrationTable(108)

pmBsIntegrity(109)

pmBsMobilityTable(110)

pmBsNetworkEntryTable(111)

pmBsTrafficTable(112)

pmBsUtilizationTable(113)

pmBsIdleModeTable(114)

pmBsFastFeedbackCQIHandlingTable(115)

pmBsAckNackChannelHandlingTable(116)

pmBsEndTransactionUpdateTable(117)

pmDlDataZoneFrameHistogramsTable(118)

pmBsTxR1NetTrafficTable(119)

pmBsRxR1NetTrafficTable(120)

pmBsTxR1TotalTrafficTable(121)

pmBsRxR1TotalTrafficTable(122)

pmBsDLHARQSbDropsTable(123)

pmBsDLHARQTransmissionTable(124)

pmBsGeneral(151)

pmBsAllMsBasicMode(201)

pmBsSpecificMsAdvancedMode(202)

pmAuCardRelatedGroupActivation Activate / Deactivate collection for the specificgroup:

Activate (1)

Deactivate (2)


18/83



npu(config)# pm-group enable npu {BckhlPort | MgmtPort | CascPort |AuPortTable | IntMgmtIf | ExtMgmtIf | LclMgmtIf | BearerIf | Sfa | DatapathFn| AaaClient | Authenticator | ContextFn | ProxyDhcp | RelayDhcp | ServerDhcp

| MsStateChangeFn}

To disable collection and storage of performance data for one or all groups, runthe following command:

npu(config)# no pm-group enable npu {BckhlPort | MgmtPort | CascPort |AuPortTable | IntMgmtIf | ExtMgmtIf | LclMgmtIf | BearerIf | Sfa | DatapathFn| AaaClient | Authenticator | ContextFn | ProxyDhcp | RelayDhcp | ServerDhcp| MsStateChangeFn}

To display whether collection and storage of performance data is enabled/disabledfor a group, run the following command:

npu# show npu pm-group status {BckhlPort | MgmtPort | CascPort |AuPortTable | IntMgmtIf | ExtMgmtIf | LclMgmtIf | BearerIf | Sfa | DatapathFn| AaaClient | Authenticator | ContextFn | ProxyDhcp | RelayDhcp | ServerDhcp| MsStateChangeFn}

2.2.2.4.2 Parameters Managed by the AU:To enable collection and storage of performance data for a group, run thefollowing command:

npu(config)# pm-group enable au { BsDeRegistrationTable | BsIntegrity |BsMobilityTable | BsNetworkEntryTable | BsTrafficTable | BsUtilizationTable |BsIdleModeTable | BsFastFeedbackCQIHandlingTable |BsAckNackChannelHandlingTable | BsEndTransactionUpdateTable |BsDlDataZoneFrameHistogramsTable | BsTxR1NetTrafficTable |BsRxR1NetTrafficTable | BsTxR1TotalTrafficTable | BsRxR1TotalTrafficTable |

NOTE

Using this command, you can enable collection of performance data for only one group at a time.For example, run the following command if you want to enable performance data collection andstorage for the data path function:

npu(config)# pm-group enable npu DatapathFn

NOTE

Using this command, you can disable collection of performance data for only one group at a time.For example, run the following command if you want to disable performance data collection andstorage for the data path function:

npu(config)# no pm-group enable npu DatapathFn


19/83



BsDLHARQSbDropsTable | BsDLHARQTransmissionTable | BsGeneral |Bsallmsbasicmode | Bsspecificmsadvancedmode}.

To disable collection and storage of performance data for one or all groups, run

the following command:npu(config)# no pm-group enable au { BsDeRegistrationTable | BsIntegrity |BsMobilityTable | BsNetworkEntryTable | BsTrafficTable | BsUtilizationTable |BsIdleModeTable | BsFastFeedbackCQIHandlingTable |BsAckNackChannelHandlingTable | BsEndTransactionUpdateTable |BsDlDataZoneFrameHistogramsTable | BsTxR1NetTrafficTable |BsRxR1NetTrafficTable | BsTxR1TotalTrafficTable | BsRxR1TotalTrafficTable |BsDLHARQSbDropsTable | BsDLHARQTransmissionTable | BsGeneral |Bsallmsbasicmode | Bsspecificmsadvancedmode}.

To display whether collection and storage of performance data is enabled/disabledfor a group, run the following command:

npu# show au group status { BsDeRegistrationTable | BsIntegrity |BsMobilityTable | BsNetworkEntryTable | BsTrafficTable | BsUtilizationTable |BsIdleModeTable | BsFastFeedbackCQIHandlingTable |BsAckNackChannelHandlingTable | BsEndTransactionUpdateTable |BsDlDataZoneFrameHistogramsTable | BsTxR1NetTrafficTable |BsRxR1NetTrafficTable | BsTxR1TotalTrafficTable | BsRxR1TotalTrafficTable |BsDLHARQSbDropsTable | BsDLHARQTransmissionTable | BsGeneral |Bsallmsbasicmode | Bsspecificmsadvancedmode}.

NOTE

Using this command, you can enable collection of performance data for only one group at a time.For example, run the following command if you want to enable performance data collection andstorage for traffic counters:

npu(config)# pm-group enable au BsTrafficTable.

Collection of Bsallmsbasicmode and Bsspecificmsadvancedmode counters is disabledby default.

NOTE

Using this command, you can disable collection of performance data for only one group at a time.For example, run the following command if you want to disable performance data collection andstorage for traffic counters:

npu(config)# no pm-group enable au BsTrafficTable


20/83



2.2.3 Collected Data Manipulation

At the end of each aggregation period, the following actions are carried:

For each performance parameter of the "Counter" type managed by the NPU:The current value of counter is be sampled and stored.

For each performance parameter of the "Counter" type managed by an AU: Thedifference between the current counter value and the previous one (start of theaggregation period) is calculated. The difference calculation takes into accountpossible counter wraparound during the aggregation period (detection rule:current value is less than previous one). The calculated difference is set as thespecific counter data of the specific period.

For each performance parameter of the "Gauge" type: Calculate the gaugerepresentative value for the whole period, as specifically defined for eachspecific performance gauge. The calculated value is set as the specific gaugedata of the specific period.

2.2.4 Collected Files Creation and Storage

The NPU creates a file of the collected performance parameters after the expirationof each aggregation period. The file includes the performance data gathered by theNPU itself, as well as the data gathered by each AU, during the same aggregationperiod.

Performance files use XML format. The XML file structure is compliant with the3GPP standard TS-32.435-v7.2.0.

The NPU compresses the combined file using GZip algorithm and name itaccording to the UTC time stamp of the aggregation period end, having the formatof "prf__YYYYMMDDhhmm.xml.gz, where:

YYYY: Year (2007 to 9999)

MM: Month of year (01 to 12)

DD: Day of month (01 to 31)

hh: Hour of day (00 to 23)

mm: Minute of hour, may have the following values only: 00, 15, 30, 45.


21/83



The NPU stores up to 24 hours of long-term performance data (96 files) in the path/tftpboot/management/performance. Files are erased from the storage(overwritten) using a FIFO mechanism. Data is not erased as a result of any

management-initiated action. All data is erased after NPU reset.

Stored performance files can be uploaded to a management system using TFTP asmany times as required. If a TFTP session has started, deletion of that file causedby the FIFO mechanism does not affect the upload.


22/83

Performance Parameters Parameters Managed by the NPU


3 . Pe r form anc e Param et er sThis section includes:

Parameters Managed by the NPU

Parameters Managed by AU

3 .1 Par am et e rs Ma na ge d b y t he NPU

All the parameters that are managed by the NPU support both real-timemonitoring (SNMP based retrieval) and File Collection, excluding the followingparameters that are supported only for real-time (SNMP-based or via CLI)Monitoring (not available in collected files):

Rate Limiting Counters for Pre-Defined Applications (see Section 3.1.1.9 )

Rate Limiting Counters for User-Defined Applications (see Section 3.1.1.10 )

L3 Rule Performance Parameters (see Section 3.1.1.11 ) (not available via CLI)

NPU Usages Gauges (see Section 3.1.2.1 ).

The performance parameters managed by the NPU include the following ManagedObjects:

Connectivity

NPU

ASNGW

3.1.1 Connectivity

The Connectivity performance parameters include the following groups:

NPU Data (Backhaul) Port

CAUTION

Certain counters or counters groups are marked as Not Fully Supported in Current Release. Donot use these counters as their values may be inaccurate or meaningless.


23/83



NPU Management Port

NPU Cascading Port

AU Ports (Internal Ethernet Ports)

NPU Internal Management Interface

NPU External Management Interface

NPU Local Management Interface

NPU Bearer Interface

Rate Limiting Counters for Pre-Defined Applications

Rate Limiting Counters for User-Defined Applications

L3 Rule Performance Parameters

3.1.1.1 NPU Data (Backhaul) Port

Group Name (in XML file and MIB): pmNpuBckhlPort

Command for real-time monitoring via CLI:npu# show interfaces gigabitethernet 0/10 counters

Table 3: Data (Backhaul) Port Performance Parameters

Parameter CLI Display Name Type Counts the Number of...

cntNpuBckhlPortInOctet rxBytes Counter64 Octets received on this interface

cntNpuBckhlPortInUcastPkt rxUnicast Packets Counter32 Multicast packets received on thisinterface

cntNpuBckhlPortInMulticastPkt rxMulticast Packets Counter32 Multicast packets received on thisinterface

cntNpuBckhlPortInBroadcastPkt rxBroadcast Packets Counter32 Broadcast packets received on thisinterface

cntNpuBckhlPortInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had noerrors

cntNpuBckhlPortInErrors rxError Packets Counter32 Received packets with errors onthis interface


24/83



3.1.1.2 NPU Management Port

Group Name (in XML file and MIB): pmNpuMgmtPortCommand for real-time monitoring via CLI:npu# show interfaces fastethernet 0/8 counters

cntNpuBckhlPortInUnknownProtos rxUnknown Packets Counter32 Not fully supported incurrent release.

Packets received with unknownprotocol on this interface

cntNpuBckhlPortOutOctet txBytes Counter64 Octets transmitted from theinterface

cntNpuBckhlPortOutUcastPkt txUnicast Packets Counter32 Unicast packets transmitted fromthis interface

cntNpuBckhlPortOutMulticastPkt txMulticast Packets Counter32 Multicast packets transmitted fromthis interface

cntNpuBckhlPortOutBroadcastPkt txBroadcast Packets Counter32 Broadcast packets transmittedfrom this interface

cntNpuBckhlPortOutDiscards txDiscarded Packets Counter32 Transmitted packets discarded onthis interface, though these had noerrors

cntNpuBckhlPortOutErrors txError Packets Counter32 Not fully supported incurrent release.

Transmitted packets with errors onthis interface

CAUTION

NPU Management Port counters are not fully supported in current release. Do not use thesecounters as their values may be inaccurate or meaningless.

Table 4: NPU Management Port Performance Parameters


cntNpuMgmtPortInOctet rxBytes Counter64 Octets received on this interface

cntNpuMgmtPortInUcastPkt rxUnicast Packets Counter32 Unicast packets received on thisinterface

cntNpuMgmtPortInMulticastPkt rxMulticast Packets Counter32 Multicast packets received on thisinterface

Table 3: Data (Backhaul) Port Performance Parameters


25/83



3.1.1.3 NPU Cascading Port

Group Name (in XML file and MIB): pmNpuCascPortCommand for real-time monitoring via CLI:npu# show interfaces gigabitethernet 0/9 counters

cntNpuMgmtPortInBroadcastPkt2 rxBroadcast Packets Counter32 Broadcast packets received on thisinterface

cntNpuMgmtPortInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had no errors

cntNpuMgmtPortInErrors rxError Packets Counter32 Received packets with errors on thisinterface

cntNpuMgmtPortInUnknownProtos rxUnknown Packets Counter32 Packets received with unknownprotocol on this interface

cntNpuMgmtPortOutOctet txBytes Counter64 Octets transmitted from the interface

cntNpuMgmtPortOutUcastPkt txUnicast Packets Counter32 Unicast packets transmitted from thisinterface

cntNpuMgmtPortOutMulticastPkt txMulticast Packets Counter32 Multicast packets transmitted fromthis interface

cntNpuMgmtPortOutBroadcastPkt txBroadcast Packets Counter32 Broadcast packets transmitted fromthis interface

cntNpuMgmtPortOutDiscards txDiscarded Packets Counter32 Transmitted packets discarded onthis interface, though these had noerrors

cntNpuMgmtPortOutErrors txError Packets Counter32 Transmitted packets with errors onthis interface

CAUTION

NPU Cascading Port counters are not fully supported in current release. Do not use these countersas their values may be inaccurate or meaningless.

Table 5: NPU Cascading Port Performance Parameters


cntNpuCascPortInOctet rxBytes Counter64 Octets received on this interface

cntNpuCascPortInUcastPkt rxUnicast Packets Counter32 Unicast packets received on thisinterface

cntNpuCascPortInMulticastPkt rxMulticast Packets Counter32 Multicast packets received on thisinterface

Table 4: NPU Management Port Performance Parameters


26/83



3.1.1.4 AU Ports (Internal Ethernet Ports)

This group includes counters of events on the internal ports between the NPU andeach of the AUs.

Group Name (in XML file and MIB): pmAuPortTable

Each AU (pmAuPortEntry) is identified by its Slot ID (pmnpuAuPortNo) that isused also as the index for the entry.

Command for real-time monitoring via CLI:npu# show interfaces fastethernet 0/N counters (N=1 to 7)

The following parameters are available for each of the AUs.

cntNpuCascPortInBroadcastPkt rxBroadcast Packets Counter32 Broadcast packets received onthis interface

cntNpuCascPortInDiscards rxDiscarded Packets Counter32 Received packets discarded onthis interface, though these hadno errors

cntNpuCascPortInErrors rxError Packets Counter32 Received packets with errors onthis interface

cntNpuCascPortInUnknownProtos rxUnknown Packets Counter32 Packets received with unknownprotocol on this interface

cntNpuCascPortOutOctet txBytes Counter64 Octets transmitted from theinterface

cntNpuCascPortOutUcastPkt txUnicast Packets Counter32 Unicast packets transmitted fromthis interface

cntNpuCascPortOutMulticastPkt txMulticast Packets Counter32 Multicast packets transmitted fromthis interface

cntNpuCascPortOutBroadcastPkt txBroadcast Packets Counter32 Broadcast packets transmittedfrom this interface

cntNpuCascPortOutDiscards txDiscarded Packets Counter32 Transmitted packets discarded onthis interface, though these hadno errors

cntNpuCascPortOutErrors txError Packets Counter32 Transmitted packets with errors onthis interface

CAUTION

AU Ports counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 5: NPU Cascading Port Performance Parameters


27/83



3.1.1.5 NPU Internal Management Interface

Group Name (in XML file and MIB): pmNpuIntMgmtIf

Command for real-time monitoring via CLI:npu# show interfaces internal-mgmt counters

Table 6: AU Port Performance Management

Parameter CLI Display Name Type For the Number of...

cntAuPortInOctet rxBytes Counter64 Octets received on this interface

cntAuPortInUcastPkt rxUnicast Packets Counter32 Unicast packets received on this interface

cntAuPortInMulticastPkt rxMulticast Packets Counter32 Multicast packets received on thisinterface

cntAuPortInBroadcastPkt rxBroadcast Packets Counter32 Broadcast packets received on thisinterface

cntAuPortInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had no errors

cntAuPortInErrors rxError Packets Counter32 Received packets with errors on thisinterface

cntAuPortInUnknownProtos rxUnknown Packets Counter32 Packets received with unknown protocolon this interface

cntAuPortOutOctet txBytes Counter64 Octets transmitted from the interface

cntAuPortOutUcastPkt txUnicast Packets Counter32 Unicast packets transmitted from thisinterface

cntAuPortOutMulticastPkt txMulticast Packets Counter32 Multicast packets transmitted from thisinterface

cntAuPortOutBroadcastPkt txBroadcast Packets Counter32 Broadcast packets transmitted from this

interface

cntAuPortOutDiscards txDiscarded Packets Counter32 Transmitted packets discarded on thisinterface, though these had no errors

cntAuPortOutErrors txError Packets Counter32 Transmitted packets with errors on thisinterface

CAUTION

NPU Internal Management counters are not fully supported in current release. Do not use thesecounters as their values may be inaccurate or meaningless.


28/83



3.1.1.6 NPU External Management Interface

Group Name (in XML file and MIB): pmNpuExtMgmtIf

Command for real-time monitoring via CLI:npu# show interfaces external-mgmt counters

Table 7: NPU Internal Management Interface Performance Parameters


cntNpuIntMgmtInOctet rxBytes Counter64 Octets received on this interface

cntNpuIntMgmtInPkt rxUnicast Packets Counter32 Packets received on this interface

cntNpuIntMgmtInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had no errors

cntNpuIntMgmtInErrors rxError Packets Counter32 Received packets with errors on thisinterface

cntNpuIntMgmtOutOctet txBytes Counter64 Octets transmitted from this interface

cntNpuIntMgmtOutPkt txUnicast Packets Counter32 Packets transmitted from this interface

CAUTION

NPU External Management counters are not fully supported in current release. Do not use thesecounters as their values may be inaccurate or meaningless.

Table 8: NPU External Management Interface Performance Parameters


cntNpuExtMgmtInOctet rxBytes Counter64 Octets received on this interface

cntNpuExtMgmtInPkt rxUnicast Packets Counter32 Packets received on this interface

cntNpuExtMgmtInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had no errors

cntNpuExtMgmtInErrors rxError Packets Counter32 Received packets with errors on thisinterface

cntNpuExtMgmtOutOctet txBytes Counter64 Octets transmitted from this interface

cntNpuExtMgmtOutPkt txUnicast Packets Counter32 Packets transmitted from this interface


29/83



3.1.1.7 NPU Local Management Interface

Group Name (in XML file and MIB): pmNpuLclMgmtIf

Command for real-time monitoring via CLI:npu# show interfaces local-mgmt counters

3.1.1.8 NPU Bearer Interface

Group Name (in XML file and MIB): pmNpuBeareIf

Command for real-time monitoring via CLI:npu# show interfaces bearer counters

CAUTION

NPU Local Management counters are not fully supported in current release. Do not use thesecounters as their values may be inaccurate or meaningless.

Table 9: NPU Local Management Interface Performance Parameters


cntNpuLclMgmtInOctet rxBytes Counter64 Octets received on this interface

cntNpuLclMgmtInPkt rxUnicast Packets Counter32 Packets received on this interface

cntNpuLclMgmtInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had no errors

cntNpuLclMgmtInErrors rxError Packets Counter32 Received packets with errors on thisinterface

cntNpuLclMgmtOutOctet txBytes Counter64 Octets transmitted from this interface

cntNpuLclMgmtOutPkt txUnicast Packets Counter32 Packets transmitted from this interface

CAUTION

NPU Bearer Interface counters are not fully supported in current release. Do not use these countersas their values may be inaccurate or meaningless.

Table 10: NPU Bearer Interface Performance Parameters


cntNpuBearerInOctet rxBytes Counter64 Octets received on this interface

cntNpuBearerInPkt rxUnicast Packets Counter32 Packets received on this interface


30/83



3.1.1.9 Rate Limiting Counters for Pre-Defined Applications

These counters are supported only for real-time (SNMP-based or via CLI)Monitoring (not available in collected files).

Table in MIB: pmNpuPreDefRateLmtTable

Each entry in the table (PmNpuPreDefRateLmtEntry) includes the followingparameters:

cntNpuBearerInDiscards rxDiscarded Packets Counter32 Received packets discarded on thisinterface, though these had no errors

cntNpuBearerInErrors rxError Packets Counter32 Received packets with errors on thisinterface

cntNpuBearerOutOctet txBytes Counter64 Octets transmitted from this interface

cntNpuBearerOutPkt txUnicast Packets Counter32 Packets transmitted from this interface

CAUTION

Rate Limiting counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 10: NPU Bearer Interface Performance Parameters


31/83



Command for real-time monitoring via CLI:

npu# show rate-limit counters { ftp | telnet | tftp | ssh | icmp | snmp |R4-R6 | igmp | eap | arp | all-others | | all }

You can use this command to view all rate-limiting counters, including thecounters for user-defined applications.

3.1.1.10 Rate Limiting Counters for User-Defined Applications

These counters are supported only for real-time (SNMP-based or via CLI)Monitoring (not available in collected files).

Table in MIB: pmNpuUserDefRateLmtTable

Table 11: Rate Limiting Performance Parameters for Pre-Defined Applications


npuRateLmtIndex Indicates the type of application and serves also as an index for the entry:

ftp(1)

telnet(2)

tftp(3)

ssh(4)

icmp(5)

snmp(6)

r6r4(7)

igmp(8)

eap(9)

arp(10)

allOthers(11)

cntNpuPreDefAppDiscards The number of packets discarded by rate limiting for the pre-defined application.

Counter 32.

CAUTION

Rate Limiting counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.


32/83



Each entry in the table (PmNpuUserDefRateLmtEntry) includes the followingparameters:

3.1.1.11 L3 Rule Performance Parameters

These counters are supported only for SNMP-based real-time Monitoring (notavailable in collected files, not available via CLI).

Table in MIB: pmNpuL3RuleTable

Each entry in the table (pmNpuL3RuleEntry) includes the following parameters:

Command for real-time monitoring via CLI:

npu# show access-lists [ { |


33/83



3.1.2 NPU

3.1.2.1 NPU Usages Gauges

The NPU performance parameters are supported only for real-time (SNMP-basedor via CLI) Monitoring (not available in collected files). The NPU Usageperformance parameters include the following:

Command for real-time monitoring via CLI: npu# show resource usage

3.1.3 ASNGW

The ASNGW performance parameters include the following groups:

SFA (Service Flow Authorization)

Data Path

AAA Client

Authenticator

Context Function

DHCP Proxy

DHCP Relay

DHCP Server

MS State Change Functionality

CAUTION

NPU Usage Gauges are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 14: NPU Usage Performance Parameters


npuCpuUsage Average NPU CPU usage, in percents. Gauge 32

npuMemoryUsage Average NPU Memory usage, in percents. Gauge 32.


34/83



3.1.3.1 SFA (Service Flow Authorization)

Group Name (in XML file and MIB): pmSfa

All Data Path counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show sfa statistics

Command for resetting the counters: npu# clear sfa statistics

* McFlow counters are available in current release only via CLI. These countersare for future use when the Multicast/Broadcast feature will be fully supported.

3.1.3.2 Data Path

Group Name (in XML file and MIB): pmDataPathFn.

All Data Path counters are of type Counter32.

CAUTION

SFA counters are not fully supported in current release. Do not use these counters as their valuesmay be inaccurate or meaningless.

Table 15: Performance Parameters for SFA Functionality

Parameter Counts the Number of...

sfaQosMappingFail Authentication failures due to QoS mapping failure

sfaSfDescMissing Authentication failures due to missing service flow descriptor

sfaDfltLpApplied MS for which default local policy has been applied

sfaRejMsDueMissingProf MS rejected due to missing service profile

sfaRejMs MS rejected

sfaLocalServProfApplied MS for which local service profile has been applied

McFlowAttachRRrequestSuccessCount*

Successfull multicast flow attachments. It is incremented at the receipt of asuccessful RR_Rsp .

McFlowAttachRRrequestFailCount*

Multicast flow attachments rejected. Incremented when Reservation ResultTLV in RR-RSP/ SF Info indicates some failure.

McFlowAttachRRrequestTimeoutCount*

Multicast transaction failures. Incremented when Anchor SFA fails to completeRR transaction i.e. fails to receive RR-RSP message after maximumRR-Req retries.

CAUTION

Data Path counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.


35/83



Command for real-time monitoring via CLI: npu# show datapath statistics

Table 16: Performance Parameters for Data Path Functionality


dpPathRegReqRx Path registration request messages received

dpPathRegReqTx Path registration request messages transmitted

dpPathRegReqRtx Path registration request message retransmissions

dpPathRegReqDrop Path registration request message dropped

dpPathRegRprtRx Path registration report messages received

dpPathRegRprtTx Path registration report messages transmitted

dpPathRegRprtRtx Path registration report message retransmissionsdpPathRegRprtDrop Path registration report message dropped

dpPathRegRprtAckRx Path registration report ack messages received

dpPathRegRprtAckTx Path registration report ack messages transmitted

dpPathRegRprtAckDrop Path registration report ack message dropped

dpPathPreRegReqRx Path pre-registration request messages received

dpPathPreRegReqTx Path pre-registration request messages transmitted

dpPathPreRegReqRtx Path pre-registration request message retransmissions

dpPathPreRegReqRx Path pre-registration request messages received

dpPathPreRegRprtRx Path pre-registration report messages received

dpPathPreRegRprtTx Path pre-registration report messages transmitted

dpPathPreRegRprtRtx Path pre-registration report message retransmissions

dpPathPreRegRprtDrop Path pre-registration report message dropped

dpPathPreRegRprtAckRx Path pre-registration report ack messages received

dpPathPreRegRprtAckTx Path pre-registration report ack messages transmitted

dpPathPreRegRprtAckDrop Path pre-registration report ack message dropped

dpPathDeRegReqRx Path deregistration request messages received

dpPathDeRegReqTx Path deregistration request messages transmitted

dpPathDeRegReqRtx Path deregistration request message retransmissions

dpPathDeRegReqDrop Path deregistration request message dropped

dpPathDeRegRprtRx Path deregistration report messages received

dpPathDeRegRprtTx Path deregistration report messages transmitted

dpPathDeRegRprtRtx Path deregistration report message retransmissions


36/83



3.1.3.3 AAA Client

Group Name (in XML file and MIB): pmAaaClient.

All AAA Client counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show radius statistics

Command for resetting the counters: npu# clear radius statistics

dpPathDeRegRprtDrop Path deregistration report message droppeddpPathDeRegRprtAckRx Path deregistration report ack messages received

dpPathDeRegRprtAckTx Path deregistration report ack messages transmitted

dpPathDeRegRprtAckDrop Path deregistration report ack message dropped

dpActiveSF Active Service Flows in the system

dpActiveGRESessions Active GRE Sessions in the system

dpInvalidEvent Invalid events occurred due to reception of datapath messages

CAUTION

Only volume accounting counters (radAccStartReqTx, radAccStopReqTx, radAccInterimReqTx,radAccExpTx, radAccAcceptRx, radAccDropRx) are fully supported.

All other AAA Client counters are not fully supported in current release. Do not use these countersas their values may be inaccurate or meaningless.

Table 17: Performance Parameters for AAA Client Functionality


radAccessReqTx Radius access request messages transmitted

radAccessReqRtx Radius access request message retransmissions

radAccessChallengeRx Radius access challenge messages received

radAccessAcceptRx Radius access accept messages received

radAccessRejectRx Radius access reject messages received

radAccessChallengeDrop Radius access challenge messages dropped

radAccessAcceptDrop Radius access accept messages dropped

radAccessRejectDrop Radius access reject messages dropped

radTimerAccessReqExp Timer expiries while awaiting response for Radius access request message sent

Table 16: Performance Parameters for Data Path Functionality



37/83



3.1.3.4 Authenticator

Group Name (in XML file and MIB): pmAuthenticator.

All Authenticator counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show authenticatorstatistics

radInvalidEvent invalid events occurred due to reception of Radius messages

radMsProfileChange MS reauthentications with different MS profile received in access accept messageradEapMismatch Radius access accept/reject messages received with EAP status mismatch

radCounterAccessReqExp Radius access request retry failures

radAaaSwitchoverRetryFail Number of AAA switchover retry failures

radAccStartReqTx Number of radius accounting start messages Transmitted

radAccStopReqTx Number of radius accounting stop messages Transmitted

radAccInterimReqTx Number of radius accounting interim messages Transmitted

radAccExpTx Number of Retransmissions

radAccAcceptRx Accepted Accounting Responses

radAccDropRx Dropped Accounting Responses

CAUTION

Authenticator counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 18: Performance Parameters for Authenticator Functionality

Parameter Counts the Number of ....

eapIdReqRtx EAP ID request retransmissions

eapIdRspRx EAP ID response messages receivedeapIdRspDrop EAP ID response messages dropped

eapTransferTx EAP transfer message transmissions

eapTransferRtx EAP transfer message retransmissions

eapTransferRx EAP transfer messages received

eapTransferDrop EAP transfer messages dropped

eapStartRx EAP start messages received

eapStartDrop EAP start messages dropped

Table 17: Performance Parameters for AAA Client Functionality


38/83



3.1.3.5 Context Function

Group Name (in XML file and MIB): pmContextFn.

All Context Function counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show contextfn statistics

eapCounterIdReqExp EAP ID request retries failureeapCounterTransferExp EAP transfer retries failure

eapRndOver Times EAP transfer rounds counter exceeds threshold

eapAuthSuccess Successful MS authentications

eapAuthFailure Failed MS authentications

eapAuthAttempts MS authentication attempts

eapReauthSuccess Successful MS re-authentications

eapReauthFailure Failed MS re-authentications

eapReauthAttempts MS re-authentication attempts

eapInvalidNai Times an invalid NAI is received in EAP ID response message

eapInvalidNaiLen Times an NAI with invalid length is received in EAP ID response message

eapInvalidNaiRealm Times an NAI with invalid realm is received in EAP ID response message

eapInvalidNaiPseudoId Times an NAI with invalid pseudo identifier is received in EAP ID responsemessage

eapNaiMismatchAuthMode Times an NAI with invalid authentication mode is received in EAP ID responsemessage

authUnauthMS Un-authenticated MS entries

arpEapTransferTx ARP transfer message (EAP-ID / EAP transfer) transmissions

arpEapTransferRx ARP transfer message (EAP-ID / EAP transfer) received

eapIdReqTx EAP ID request transmissions

arpEapTransferDrop ARP transfer message (EAP-ID / EAP transfer) dropped

arpEapStartRx ARP (EAP start) messages received

arpEapStartDrop ARP (EAP start) messages dropped

CAUTION

Context Function counters are not fully supported in current release. Do not use these counters astheir values may be inaccurate or meaningless.

Table 18: Performance Parameters for Authenticator Functionality

Parameter Counts the Number of ....


39/83



3.1.3.6 DHCP Proxy

Group Name (in XML file and MIB): pmDhcpProxy.

All DHCP Proxy counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show dhcp-proxy statistics

Command for resetting the counters: npu# clear dhcp-proxy statistics

Table 19: Performance Parameters for the Context Function

Parameter Counts the Number of ...

ctxtfnCtxtReqTx Context request messages transmitted

ctxtfnCtxtReqRtx Context request messages retransmissions

ctxtfnCtxtReqRx Context request messages received

ctxtfnCtxtReqDrop Context request messages dropped

ctxtfnCtxtRprtTx Context report messages transmitted

ctxtfnCtxtRprtRtx Context report message retransmissions

ctxtfnCtxtRprtRx Context report messages received

ctxtfnCtxtRprtDrop Context report messages dropped

ctxtfnCtxtRprtAckTx Context report ack messages transmitted

ctxtfnCtxtRprtAckRx Context report ack messages received

ctxtfnCtxtRprtAckDrop Context report ack messages dropped

ctxtfnPkmv2Failure MS network entry failures due to PKMv2 handshake failure

CAUTION

DHCP Proxy counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 20: Performance Parameters for DHCP Proxy Functionality


dhcpProxyDiscoverRx DHCP discover messages received at DHCP proxy

dhcpProxyDiscoverDrop DHCP discover messages dropped at DHCP proxy

dhcpProxyRequestRx DHCP request messages received at DHCP proxy

dhcpProxyRequestDrop DHCP request messages dropped at DHCP proxy

dhcpProxyLeaseTimerExp DHCP lease timer expiries at DHCP proxy

dhcpProxyInvalidEvent Invalid events occurred due to reception of DHCP messages at DHCP proxy


40/83



3.1.3.7 DHCP Relay

Group Name (in XML file and MIB): pmDhcpRelay.

All DHCP Relay counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show dhcp-relay statistics

Command for resetting the counters: npu# clear dhcp-relay statistics

3.1.3.8 DHCP Server

dhcpProxyReleaseRx DHCP release messages received at DHCP proxy

dhcpProxyReleaseDrop DHCP release messages dropped at DHCP proxy

CAUTION

DHCP Relay counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 21: Performance Parameters for DHCP Relay Functionality


dhcpRelayDiscoverRx DHCP discover messages received at DHCP relay

dhcpRelayDiscoverDrop DHCP discover messages dropped at DHCP relay

dhcpRelayOfferRx DHCP offer messages received at DHCP relay

dhcpRelayOfferDrop DHCP offer messages dropped at DHCP relay

dhcpRelayRequestRx DHCP request messages received at DHCP relay

dhcpRelayRequestDrop DHCP request messages dropped at DHCP relay

dhcpRelayAckRx DHCP Ack messages received at DHCP relay

dhcpRelayAckDrop DHCP Ack messages dropped at DHCP relay

dhcpRelayNakRx DHCP Nack messages received at DHCP relay

dhcpRelayNakDrop DHCP Nack messages dropped at DHCP relay

dhcpRelayIpAllocFailed IP allocation failures at DHCP relay

dhcpRelayInvalidEvent Invalid events occurred due to reception of DHCP messages at DHCP server

CAUTION

DHCP Server counters are not fully supported in current release. Do not use these counters as theirvalues may be inaccurate or meaningless.

Table 20: Performance Parameters for DHCP Proxy Functionality


41/83



Group Name (in XML file and MIB): pmDhcpServer.

All DHCP Server counters are of type Counter32.

Command for real-time monitoring via CLI: npu# show dhcp-serverstatistics

Command for resetting the counters: npu# clear dhcp-server statistics

3.1.3.9 MS State Change Functionality

Group Name (in XML file and MIB): pmMsStateChangeFn

Command for real-time monitoring via CLI: npu# show msscfn statistics

Table 22: Performance Parameters for DHCP Server Functionality


dhcpServerDiscoverRx DHCP discover messages received at DHCP server

dhcpServerDiscoverDrop DHCP discover messages dropped at DHCP server

dhcpServerRequestRx DHCP request messages received at DHCP server

dhcpServerRequestDrop DHCP request messages dropped at DHCP server

dhcpServerReleaseRx DHCP release messages received at DHCP server

dhcpServerServerReleaseDrop DHCP release messages dropped at DHCP server

dhcpServerLeaseTimerExp DHCP lease timer expiries at DHCP server

dhcpServerInvalidEvent Invalid events occurred due to reception of DHCP messages at DHCP server

CAUTION

MS State Change counters are not fully supported in current release. Do not use these counters astheir values may be inaccurate or meaningless.

Table 23: Performance Parameters for MS State Change Functionality

Parameter For the Number of ...

msscfnMsscReqTx MS state change request messages transmitted

msscfnMsscReqRtx MS state change request message retransmissions

msscfnMsscReqRx MS state change request messages received

msscfnMsscReqDrop MS state change request messages dropped

msscfnMsscRspTx MS state change response messages transmitted

msscfnMsscRspRtx MS state change response message retransmissions


42/83



msscfnMsscRspRx MS state change response messages receivedmsscfnMsscRspDrop MS state change response messages dropped

msscfnMsscRspAckTx MS state change response ack messages transmitted

msscfnMsscRspAckRx MS state change response ack messages received

msscfnMsscRspAckDrop MS state change response ack messages dropped

msscfnMsscDrctvTx MS state change directive messages transmitted

msscfnMsscDrctvRtx MS state change directive message retransmissions

msscfnMsscDelDrctvTx MS state change delete directive messages transmitted

msscfnMsscDelDrctvRtx MS state change delete directive message retransmissions

msscfnMsscDelDrctvRx MS state change delete directive messages received

msscfnMsscDelDrctvDrop MS state change delete directive messages dropped

msscfnMsscDelDrctvAckTx MS state change delete directive ack messages transmitted

msscfnMsscDelDrctvAckRx MS state change delete directive ack messages received

msscfnMsscDelDrctvAckDrop MS state change delete directive ack messages dropped

msscfnMsUnsuppSecCap MS network entry failures due to unsupported security capabilities

msscfnMsSecCapMismatch MS network entry failures due to security capability mismatch

Table 23: Performance Parameters for MS State Change Functionality

Parameter For the Number of ...


43/83

Performance Parameters Parameters Managed by AU


3 .2 Par am et er s Mana ged by AU

In the current release:

All parameters managed by an AU belong to the BS Managed Object.

All BS parameters excluding All MS Basic Mode and Specific MS AdvancedMode counters are collected by default.

The BS groups are collected for each existing BS, identified by the BsId.

The current groups are:

De-Registration

Network Entry (NE)

Traffic

Mobility

Utilization

Integrity

Idle Mode

Fast Feedback CQI Handling

Ack/Nack Channel Handling

End Transaction Update

DL Frame Data Zone Histograms

TxR1 Net Traffic

RxR1 Net Traffic

TxR1 Total Traffic

RxR1 Total Traffic


44/83



DL HARQ Sub-Bursts Drops

DL HARQ Transmissions

Genera

All MS Basic Mode

Specific MS Advanced Mode

3.2.1 De-Registration

Group Name (in XML file and MIB): pmBsDeRegistrationTable

3.2.2 Network Entry (NE)

Group Name (in XML file and MIB): pmBsNetworkEntryTable

CAUTION

Excvept to bsBsDreg counter, all other De-Registration counters are not fully supported in currentrelease. Do not use these counters as their values may be inaccurate or meaningless.

Table 24: BS De-Registration Performance Parameters

Parameter Type Description

bsMsDreg Counter32 Total number of DREG-REQ received with deregistration request code equal to0x00

bsAsnDreg Counter32 Total number of NW_Exit_MS_State _Change Directive with deregistrationaction code messages received. Duplicates are not counted

bsAsnPathDreg Counter32 Total number of PATH DREG ACK messages with MS deregistration typereceived

bsBsDreg Gauge32 Total number of NW_Exit_MS_State _Change ACK with deregistration eventcode messages received. Retransmissions are not counted

bsBsPathDreg Counter32 Total number of PATH DREG REQ messages with MS deregistration type sent.Retransmissions are not counted

CAUTION

Network Entry counters are not fully supported in current release. Do not use these counters astheir values may be inaccurate or meaningless.


45/83



Table 25: BS Network Entry Performance Parameters

Parameter Type Description

bsSbcReqTimeouts Counter32 The number of times T9 timer expired

bsRngReq Counter32 The number of RNG-REQ messages received

bsInitialRngReqNonHo Counter32 The number of RNG-REQ messages without CMAC headerreceived

bsInitialRngReqNonHoPeak Gauge32 The peak number of bsInitialRngReqNonHo during 1 secsliding measuring intervals

bsInitialRngRspSuccessNonHo Counter32 The number of RNG-RSP messages with 'success' code sentto MS in network entry ranging phase, for MS not in handover

bsInitialRngRspSuccess Counter32 The number of RNG-RSP messages with 'success' code sentto MS in network entry ranging phase

bsRegRsp Counter32 The number of REG-RSP messages sent

bsRegRspNonHo Counter32 The number of REG-RSP messages sent for MS not in HO

bsMsPathRegAckIne Counter32 The number of PATH-REG-ACK messages received fromASN-GW with registration type equal INE


46/83



3.2.3 Traffic

Group Name (in XML file and MIB): pmBsTrafficTable

All Traffic parameters are of type Counter32.

Table 26: BS Traffic Performance Parameters

Parameter Type Counts the Number of ...

bsUlHarqSbDropsQpskOneOverTwoTimesSix Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqSbDropsQpskOneOverTwoTimesFour Counter32 Ul HARQ sub-bursts transmitted by the MS at

the specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqSbDropsQpskOneOverTwoTimesTwo Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqSbDropsQpskOneOverTwo Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by the

BSbsUlHarqSbDropsQpskThreeOverFour Counter32 Ul HARQ sub-bursts transmitted by the MS at


bsUlHarqSbDropsQamSixteenOneOverTwo Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqSbDropsQamSixteenThreeOverFour Counter32 Ul HARQ sub-bursts transmitted by the MS at


bsUlHarqSbDropsQamSixtyFourOneOverTwo Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS


47/83



bsUlHarqSbDropsQamSixtyFourTwoOverThree Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqSbDropsQamSixtyFourThreeOverFour Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqSbDropsQamSixtyFourFiveOverSix Counter32 Ul HARQ sub-bursts transmitted by the MS atthe specific MCS that were dropped (notretransmitted) although NAK was sent by theBS

bsUlHarqTransmissionsQpskOneOverTwoTimesSix

Counter32 UL HARQ transmissions over the specific MCS

bsUlHarqTransmissionsQpskOneOverTwoTimesFour


bsUlHarqTransmissionsQpskOneOverTwoTimesTwo


bsUlHarqTransmissionsQpskOneOverTwo Counter32 UL HARQ transmissions over the specific MCS

bsUlHarqSTransmissionsQpskThreeOverFour Counter32 UL HARQ transmissions over the specific MCS

bsUlHarqSTransmissionsQamSixteenOneOverTwo


bsUlHarqTransmissionsQamSixteenThreeOverFour


bsUlHarqTransmissionsQamSixtyFourOneOverTwo


bsUlHarqTransmissionsQamSixtyFourTwoOverThree


bsUlHarqTransmissionsQamSixtyFourThreeOver

Four


bsUlHarqTransmissionsQamSixtyFourFiveOverSix


bsMapLengthTwoSymbols Counter32 Frames for which map length was two symbols

bsMapLengthFourSymbols Counter32 Frames for which map length was four symbols

bsMapLengthSixSymbols Counter32 Frames for which map length was six symbols

bsMapLengthEightSymbols Counter32 Frames for which map length was eightsymbols




48/83



* Downlink Retransmissions Histograms (dlRetransHistogramZeroRetrans,dlRetransHistogramOneRetrans, dlRetransHistogramTwoRetrans,dlRetransHistogramThreeRetrans, dlRetransHistogramFourRetrans,dlRetransHistogramOverFourRetrans) are available only in collected files (notsupported in the MIB, not available for real-time monitoring). This applies also tothe new parameters added in version 2.5.2 (bsTotalConnectionsUgs,

bsMapLengthTenSymbols Counter32 Frames for which map length was ten symbolsbsMapLengthMoreThanTenSymbols Counter32 Frames for which map length was more than

ten symbols

dlRetransHistogramZeroRetrans* Counter32 Downlink transaction with zero retransmissions

dlRetransHistogramOneRetrans* Counter32 Downlink transaction with one retransmission

dlRetransHistogramTwoRetrans* Counter32 Downlink transaction with two retransmissions

dlRetransHistogramThreeRetrans* Counter32 Downlink transaction with threeretransmissions

dlRetransHistogramFourRetrans* Counter32 Downlink transaction with four retransmissions

dlRetransHistogramOverFourRetrans* Counter32 Downlink transaction with over fourretransmissions

bsTotalConnectionsUgs* Gauge32 Not fully supported in current release.

Total number of transport connections mappedto the UGS service type.

bsTotalConnectionsRtvr* Gauge32 Not fully supported in current release.

Total number of transport connections mappedto the RTVR service type.

bsTotalConnectionsNrtvr* Gauge32 Not fully supported in current release.Total number of transport connections mappedto the NRTVR service type.

bsTotalConnectionsBe* Gauge32 Not fully supported in current release.

Total number of transport connections mappedto the BE service type.

bsTotalConnectionsErtvr* Gauge32 Not fully supported in current release.

Total number of transport connections mappedto the ERTVR service type.

bsTotalRegistrationsMss* Gauge32 Not fully supported in current release.

Total number of registered MSs.




49/83



bsTotalConnectionsRtvr, bsTotalConnectionsNrtvr, bsTotalConnectionsBe,bsTotalConnectionsErtvr, bsTotalRegistrationsMss).

3.2.4 MobilityGroup Name in XML file and MIB: pmBsMobilityTable

Most of the Mobility parameters are available only in collected files (not supportedin the MIB, not available for real-time monitoring). The following parameters areavailable for real-time monitoring and are supported in the MIB:

bsHoMSHoReqReceived

bsHoPreparationCompleted

bsHoCancelled

bsHOReqRTxPerTbs

The Per SBS parameters are collected for each existing SBS, identified by the SBSBsId.

The Per TBS parameters are collected for each existing TBS, identified by the TBSBsId.

All Mobility parameters are of type Counter32.

Table 27: BS Mobility Performance Parameters


bsHoAttemptsUnpredictivePerSbs Counts number of RNG-REQ messages with specific SBS BS-IDreceived while in NUlL state. Duplicate RNG-REQ messages (i.e.RNG-REQ messages received from MS after RNG-RSP was sentto that MS and before end of the MS NE process) are not counted

bsHoAttemptsEarlyPerSbs Counts number of RNG-REQ messages with specific SBS BS-ID

received while in "Awaiting Auth. Context", "Awaiting DP Pre-Reg"or "Standby for HO Confirmation" states. Duplicate RNG-REQmessages (i.e. RNG-REQ messages received from MS afterRNG-RSP was sent

bsHoAttemptsPredictivePerSbs Counts number of RNG-REQ messages with specific SBS BS-IDreceived while in "Standby for HO" state. Duplicate RNG-REQmessages (i.e. RNG-REQ messages received from MS afterRNG-RSP was sent to that MS and before end of the MS NEprocess) are not counted


50/83



bsHoDpRegPerSbs Counts number of PATH-REG-RES messages with registration typeHHO received from ASN-GW, for MS coming from specific SBS

bsHoNotificationTimeOutPerSbs Not fully supported in current release.

Counts number of times BS timer expired waiting for MS to sendre-entry notification, for MS coming from specific SBS

bsHoCmacKeyCountUpdateAckPerSbs Counts number of CMAC Key Count Update ACK received at R6

bsHoBsContextUnavailablePerSbs Not fully supported in current release.

Counts number of times "BS context unavailable" trigger isgenerated, due to timer and retransmissions expiry or BS Context

Report receipt with "context unavailable", for MS coming from thespecific SBS

bsHoAuthContextUnavailablePerSbs Not fully supported in current release.

Counts number of times "Auth context unavailable" trigger isgenerated, due to timer and retransmissions expiry or Auth ContextReport receipt with "context unavailable" , for MS coming from thespecific SBS

bsHoDpPreRegistrationFailurePerSbs Not fully supported in current release.

Counts number of times "DP Pre-Registration Failure" trigger isgenerated, due to timer and retransmissions expiry orPATH-REG-RES receipt with "reject" code, for MS coming from thespecific SBS

bsHoDpRegistrationFailurePerSbs Not fully supported in current release.

Counts number of times "DP Registration Failure" trigger isgenerated, due to timer and retransmissions expiry orPATH-REG-RES receipt with "reject" code, for MS coming from thespecific SBS

bsHoReEntryTimeoutPerSbs Not fully supported in current release.

Counts number of times MS Re-entry timer (T_ReEntry) expires, for

MS coming from the specific SBS

bsHoIndicatedPerTbs Not fully supported in current release.

Counts number of MOB_HO-IND received with "SBS release" type,with specific TBS

bsHoResPosPerTbs Counts number of HO Positive Response messages received fromspecific TBS. Does not count duplicates

Table 27: BS Mobility Performance Parameters



51/83



bsHoAttemptsUnpredictivePerInterSite Not fully supported in current release.bsHoAttemptsUnpredictive (SBS) added over all SBS not includedin the sector association table

bsHoAttemptsUnpredictivePerInterSector Not fully supported in current release.

bsHoAttemptsUnpredictive (SBS) added over all SBS associated toa sector different than the one this BS is associated to

bsHoAttemptsUnpredictivePerIntraSector Not fully supported in current release.

bsHoAttemptsUnpredictive (SBS) added over all SBS associated tothe same sector this BS is associated to

bsHoAttemptsEarlyPerInterSite Not fully supported in current release.

bsHoAttemptsEarly(SBS) added over all SBS not included in thesector association table

bsHoAttemptsEarlyPerInterSector Not fully supported in current release.

bsHoAttemptsEarly(SBS) added over all SBS associated to asector different than the one th

4motion ver.2.5m_performance management_090908

Documents