DSR Alarms, KPIs, and Measurements

DSR Alarms, KPIs, and Measurements
EAGLE® XG Diameter Signaling
Router
DSR Alarms, KPIs, and Measurements
910-6528-001 Revision D
December 2012
Copyright 2012 Tekelec. All Rights Reserved. Printed in USA.
Legal Information can be accessed from the Main Menu of the optical disc or on the
Tekelec Customer Support web site in the Legal Information folder of the Product Support tab.
Table of Contents
Chapter 1: Introduction.....................................................................29
Overview..................................................................................................................................30
Scope and Audience...............................................................................................................30
Documentation Admonishments..........................................................................................30
Customer Care Center............................................................................................................31
Emergency Response..............................................................................................................33
Locate Product Documentation on the Customer Support Site.......................................33
Chapter 2: Alarms and Events, KPIs, and Measurements
Overview...........................................................................................35
Purpose of this documentation.............................................................................................36
Documentation organization.................................................................................................36
Displaying the file list.............................................................................................................36
Export Server...........................................................................................................................37
Export Server elements...............................................................................................37
Configuring an export server....................................................................................39
Tasks..........................................................................................................................................39
Active Tasks.................................................................................................................39
Scheduled Tasks..........................................................................................................43
Chapter 3: Alarms and Events..........................................................45
General alarms information...................................................................................................46
Alarms and events overview.....................................................................................46
Alarm and event ID ranges .......................................................................................47
Alarm and event types...............................................................................................48
Viewing active alarms................................................................................................49
Active alarms data export elements ........................................................................50
Exporting active alarms..............................................................................................50
Generating a report of active alarms........................................................................52
Viewing alarm and event history.............................................................................52
Historical events data export elements ...................................................................52
Exporting alarm and event history...........................................................................53
Generating a report of historical alarms and events..............................................55
IP Front End, IPFE (5000-5999)..............................................................................................55
910-6528-001 Revision D, December 2012
ii
5001 - IPFE Backend Unavailable.............................................................................55
5002 - IPFE address configuration error..................................................................55
5003 - IPFE state sync run error................................................................................56
5004 - IPFE IP tables configuration error.................................................................57
5005 - IPFE Backend In Stasis....................................................................................57
5006 - Error reading from Ethernet device. Restart IPFE process. ......................57
5007 - Out of Balance: Low .......................................................................................58
5008 - Out of Balance: High ......................................................................................58
5009 - No available servers in target set...................................................................59
5010 - Unknown Linux iptables command error ...................................................59
5011 - System or platform error prohibiting operation.........................................60
5100 - Traffic overload................................................................................................60
OAM (10000-10999).................................................................................................................60
Alarms formatting information.................................................................................60
10000 - Incompatible database version....................................................................61
10001 - Database backup started...............................................................................61
10002 - Database backup completed........................................................................61
10003 - Database backup failed.................................................................................62
10004 - Database restoration started.........................................................................62
10005 - Database restoration completed..................................................................62
10006 - Database restoration failed...........................................................................63
10008 - Database provisioning manually disabled ................................................63
10009 - Config and Prov db not yet synchronized ................................................63
10010 - Stateful db from mate not yet synchronized..............................................64
10011 - Cannot monitor table....................................................................................64
10012 - Table change responder failed ....................................................................64
10013 - Application restart in progress ...................................................................65
10020 - Backup failure ................................................................................................65
10074 - Standby server degraded while mate server stabilizes............................65
10075 - Application processes have been manually stopped...............................66
10078 - Application not restarted on standby server due to disabled failure
cleanup mode ........................................................................................................66
10100 - Log export started..........................................................................................66
10101 - Log export successful....................................................................................67
10102 - Log export failed............................................................................................67
10103 - Log export already in progress....................................................................67
10151 - Login successful.............................................................................................68
10152 - Login failed.....................................................................................................68
10153 - Logout successful...........................................................................................68
10154 - User Account Disabled.................................................................................69
10200 - Remote database reinitialization in progress.............................................69
910-6528-001 Revision D, December 2012
iii
Session Binding Repository, SBR (12000-12999).................................................................70
12003 - SBR Congestion State....................................................................................70
12007 - SBR Active Sess Binding Threshold............................................................70
12010 - SBR Proc Term................................................................................................71
Communication Agent, ComAgent (19800-19909).............................................................71
19800 - Communication Agent Connection Down................................................72
19801 - Communication Agent Connection Locally Blocked...............................72
19802 - Communication Agent Connection Remotely Blocked...........................73
19803 - Communication Agent stack event queue utilization..............................74
19804 - Communication Agent configured connection waiting for remote
client to establish connection...............................................................................75
19805 - Communication Agent Failed To Align Connection................................76
19806 - Communication Agent CommMessage mempool utilization................77
19807 - Communication Agent User Data FIFO Queue utilization.....................77
19808 - Communication Agent Connection FIFO Queue utilization..................78
19810 - Communication Agent Egress Message Discarded..................................79
19811 - Communication Agent Ingress Message Discarded.................................79
19814 - Communication Agent Peer has not responded to heartbeat.................80
19816 - Communication Agent Connection State Changed..................................80
19817 - Communication Agent DB Responder detected a change in
configurable control option parameter..............................................................81
19820 - Communication Agent Routed Service Unavailable................................81
19821 - Communication Agent Routed Service Degraded...................................82
19822 - Communication Agent Routed Service Congested..................................82
19823 - Communication Agent Routed Service Using Low-Priority
Connection Group.................................................................................................83
19824 - Communication Agent Pending Transaction Utilization........................83
19825 - Communication Agent Transaction Failure Rate......................................84
19826 - Communication Agent Connection Congested.........................................84
19830 - Communication Agent Service Registration State Change.....................85
19831 - Communication Agent Service Operational State Changed...................85
19832 - Communication Agent Reliable Transaction Failed.................................86
19833 - Communication Agent Service Egress Message Discarded....................86
19842 - Communication Agent Resource-Provider Registered............................87
19843 - Communication Agent Resource-Provider Resource State
Changed..................................................................................................................87
19844 - Communication Agent Resource-Provider Stale Status Received.........87
19845 - Communication Agent Resource-Provider Deregistered........................88
19846 - Communication Agent Resource Degraded..............................................88
19847 - Communication Agent Resource Unavailable..........................................88
19848 - Communication Agent Resource Error......................................................89
910-6528-001 Revision D, December 2012
iv
19850 - Communication Agent Resource-User Registered...................................89
19851 - Communication Agent Resource-User Deregistered...............................90
19852 - Communication Agent Resource Routing State Changed.......................90
19853 - Communication Agent Resource Egress Message Discarded.................90
19854 - Communication Agent Resource-Provider Tracking Table Audit
Results ....................................................................................................................91
19855 - Communication Agent Resource Has Multiple Actives..........................91
19900 - Process CPU Utilization................................................................................91
19901 - CFG-DB Validation Error.............................................................................92
19902 - CFG-DB Update Failure................................................................................92
19903 - CFG-DB post-update Error...........................................................................93
19904 - CFG-DB post-update Failure.......................................................................93
19905 - Measurement Initialization Failure.............................................................94
Diameter Signaling Router (DSR) Diagnostics (19910-19999)..........................................94
19910 - Message Discarded at Test Connection......................................................94
19911 - Test message discarded ................................................................................95
Diameter Signaling Router, DSR (22000-22999)..................................................................95
22001 - Message Decoding Failure............................................................................95
22002 - Peer Routing Rules with Same Priority......................................................95
22003 - Application ID Mismatch with Peer...........................................................96
22004 - Maximum pending transactions allowed exceeded.................................96
22005 - No peer routing rule found..........................................................................97
22006 - Forwarding Loop Detected..........................................................................97
22007 - Inconsistent Application ID Lists from a Peer...........................................98
22008 - Orphan Answer Response Received...........................................................98
22009 - Application Routing Rules with Same Priority.........................................99
22011 - Copy message size exceeded the system set limit....................................99
22013 - DAS Peer Number of Retransmits Exceeded for Copy............................99
22015 - Connection Operational Status Inconsistency May Exist......................100
22016 - Peer Node Alarm Aggregation Threshold...............................................100
22017 - Route List Alarm Aggregation Threshold...............................................101
22051 - Peer Unavailable..........................................................................................101
22052 - Peer Degraded..............................................................................................101
22053 - Route List Unavailable................................................................................102
22054 - Route List Degraded....................................................................................102
22055 - Non-Preferred Route Group in Use..........................................................103
22056 - Connection Admin State Inconsistency Exists........................................104
22101 - Connection Unavailable..............................................................................104
22102 - Connection Degraded.................................................................................104
22103 - SCTP Connection Impaired........................................................................105
22104 - SCTP peer is operating with a reduced IP address set...........................105
910-6528-001 Revision D, December 2012
v
22200 - Local MP Congestion..................................................................................105
22201 - Ingress Message Rate..................................................................................106
22202 - PDU Buffer Pool Utilization.......................................................................106
22203 - PTR Buffer Pool Utilization........................................................................107
22204 - Request Message Queue Utilization.........................................................108
22205 - Answer Message Queue Utilization.........................................................108
22206 - Reroute Queue Utilization..........................................................................109
22207 - All-Connections Event Queue Utilization................................................109
22209 - Message Copy Disabled..............................................................................110
22214 - Message Copy Queue Utilization..............................................................110
22220 - Connection Congestion Level change.......................................................111
22221 - Routing MPS Rate .......................................................................................112
22300 - Connection Unavailable: Socket configuration failure...........................112
22301 - Connection Unavailable: Connection initiation failure..........................113
22302 - Connection Unavailable: Received malformed message.......................113
22303 - Connection Unavailable: Peer closed connection...................................113
22304 - Connection Unavailable: Proving Failure................................................114
22305 - Connection Admin State change...............................................................114
22306 - Connection Unavailable: Timeout waiting for CER/CEA ...................114
22307 - Connection Unavailable: Timeout waiting for DPA..............................115
22308 - Received Unexpected CER/CEA..............................................................115
22309 - Received Unexpected DWR/DWA...........................................................115
22310 - Received Unexpected DPR/DPA..............................................................115
22311 - Invalid Diameter message received..........................................................116
22312 - Socket send failure.......................................................................................116
22313 - Connection Unavailable: Transport failure..............................................116
22314 - Connection Unavailable: CEA Realm/Host validation failure............117
22315 - Connection Unavailable: Peer IP address validation failure.................117
22316 - Connection Unavailable: No common apps............................................117
22317 - Connection Rejected: Connection already established...........................118
22318 - Connection Rejected: Connection not Enabled.......................................118
22319 - Connection Unavailable: Diameter Watchdog .......................................118
22320 - Invalid peer initiated connection...............................................................119
22321 - Connection Unavailable: DNS Resolution Failure..................................119
22322 - Connection Proving Success......................................................................119
22323 - Connection Degraded: Diameter Watchdog ...........................................120
22324 - Connection Unavailable: CER validation failure....................................120
22325 - Host-IP-Address AVP(s) in CER/CEA do not match peer IP
address(es)............................................................................................................120
22326 - Connection Established...............................................................................121
22327 - Initiator function disabled..........................................................................121
910-6528-001 Revision D, December 2012
vi
22329 - SCTP Connection Impaired: A path has become unreachable.............121
22330 - SCTP Connection Cfg Mismatch: The peer advertised a different
number of IP addresses than configured.........................................................122
22331 - SCTP Connection Partial Matching: SCTP connection accepted but
the IP addresses advertised by the peer match only partially those
configured for the peer in the connection object............................................122
22332 - Connection Rejected: Max Connections Exceeded.................................122
22334 - Unexpected Message Priority in ingress Request...................................123
22335 - Peer does not support Message Priority...................................................123
22336 - Connection Rejected: Multihomed SCTP connection attempt..............124
22343 - Connection Unavailable: Duplicate Connection Released....................124
22344 - Failed to process ingress message: Processor Unavailable or
Congested.............................................................................................................124
22345 - Connection Priority Level changed...........................................................125
22346 - MP Reserved Ingress MPS Oversubscribed.............................................125
22349 - IPFE Connection Alarm Aggregation Threshold....................................126
22350 - Fixed Connection Alarm Aggregation Threshold..................................126
22400 - Message Decoding Failure..........................................................................127
22401 - Unknown Application ID...........................................................................127
22402 - Unknown Command Code........................................................................127
22403 - No Routing Entity Address AVPs.............................................................128
22404 - No valid Routing Entity Addresses found...............................................128
22405 - Valid address received didn’t match a provisioned address or
address range.......................................................................................................128
22406 - Routing attempt failed due to internal resource exhaustion.................129
22407 - Routing attempt failed due to internal database inconsistency
failure....................................................................................................................129
22500 - DSR Application Unavailable....................................................................130
22501 - DSR Application Degraded........................................................................130
22502 - DSR Application Request Message Queue Utilization..........................131
22503 - DSR Application Answer Message Queue Utilization...........................131
22504 - Ingress Message Rate..................................................................................132
25510 - Multiple DA-MP Leader Detected Alarm................................................132
22520 - DSR Application Enabled...........................................................................132
22521 - DSR Application Disabled..........................................................................133
22600 - Message Decoding Failure..........................................................................133
22601 - Unknown Application ID...........................................................................133
22602 - Unknown Command Code........................................................................134
22603 - No Routing Entity Address AVPs.............................................................134
22604 - No valid User Identity Addresses found ................................................134
910-6528-001 Revision D, December 2012
vii
22605 - No Destination address is found to match the valid User Identity
address..................................................................................................................135
22606 - Database or DB connection error ..............................................................135
22607 - Routing attempt failed due to DRL queue exhaustion .........................136
22608 - Database query could not be sent due to DB congestion.......................136
22609 - Database connection exhausted.................................................................136
22631 - FABR DP Response Task Message Queue Utilization...........................137
22632 - COM Agent Registration Failure...............................................................137
22804 - Number of cSBR Unavailable Subresources at Threshold.....................137
22805 - Message Decoding Failure..........................................................................138
22806 - Unknown Diameter Application Id..........................................................138
22807 - Unknown Command Code........................................................................139
22808 - Session Not Found.......................................................................................139
22809 - Undelivered SBR Query..............................................................................139
22810 - Routing attempt failed due to internal resource exhaustion.................140
22811 - CPA Application Event Task Queue Utilization ....................................140
22812 - Missing AVP.................................................................................................140
22813 - Received an error response to an SBR Query..........................................141
22814 - HA Sub-Resource Unavailable..................................................................141
22815 - Unexpected Session.....................................................................................141
22816 - One or more cSBR Subresources Unavailable.........................................142
22950 - Connection Status Inconsistency Exists....................................................142
Tekelec Virtual Operating Environment, TVOE (24400-24499).....................................142
24400 - TVOE libvirtd is down ...............................................................................143
24401 - TVOE libvirtd is hung ................................................................................143
24402 - all TVOE libvirtd connections are in use .................................................143
Computer Aided Policy Making, CAPM (25000-25499)..................................................143
25000 - Rule Template failed to be updated..........................................................144
25001 - Action failed within the Rule Template ..................................................144
25002 - Stop Rule Template processing after action failure................................144
25003 - Exit Trigger point after action failure.......................................................145
OAM Alarm Management (25500-25899)..........................................................................145
25500 - No DA-MP Leader Detected Alarm..........................................................145
25510 - Multiple DA-MP Leader Detected Alarm................................................145
Platform (31000-32700).........................................................................................................146
Alarms formatting information...............................................................................146
31000 - S/W fault.......................................................................................................146
31001 - S/W status....................................................................................................146
31002 - Process watchdog failure............................................................................147
31003 - Tab thread watchdog failure......................................................................147
31100 - Database replication fault...........................................................................147
910-6528-001 Revision D, December 2012
viii
31101 - Database replication to slave failure.........................................................147
31102 - Database replication from master failure.................................................148
31103- DB Replication update fault........................................................................148
31104 - DB Replication latency over threshold.....................................................148
31105 - Database merge fault...................................................................................148
31106 - Database merge to parent failure..............................................................149
31107 - Database merge from child failure............................................................149
31108 - Database merge latency over threshold...................................................149
31109 - Topology config error.................................................................................150
31110 - Database audit fault.....................................................................................150
31111 - Database merge audit in progress.............................................................150
31112 - Stateful db synchronization from mate server .......................................150
31113 - DB replication manually disabled.............................................................151
31114 - DB replication over SOAP has failed........................................................151
31115 - Database service fault..................................................................................151
31116 - Excessive shared memory..........................................................................151
31117 - Low disk free................................................................................................152
31118 - Database disk store fault.............................................................................152
31119 - Database updatelog overrun......................................................................152
31120 - Database updatelog write fault..................................................................152
31121 - Low disk free early warning......................................................................153
31122 - Excessive shared memory early warning.................................................153
31123 - Database replication audit command complete......................................153
31124 - Database replication audit command error.............................................153
31125 - Database durability degraded...................................................................154
31126- Audit blocked................................................................................................154
31130 - Network health warning............................................................................154
31140 - Database perl fault.......................................................................................154
31145 - Database SQL fault......................................................................................155
31146- DB mastership fault......................................................................................155
31147- DB upsynclog overrun.................................................................................155
31200 - Process management fault..........................................................................155
31201 - Process not running.....................................................................................156
31202 - Unkillable zombie process..........................................................................156
31206 - Process mgmt monitoring fault.................................................................156
31207 - Process resource monitoring fault.............................................................156
31208 - IP port server fault.......................................................................................157
31209 - Hostname lookup failed.............................................................................157
31213 - Process scheduler fault................................................................................157
31214 - Scheduled process fault..............................................................................157
31215 - Process resources exceeded........................................................................158
910-6528-001 Revision D, December 2012
ix
31216 - SysMetric configuration error....................................................................158
31220 - HA configuration monitor fault................................................................158
31221 - HA alarm monitor fault..............................................................................158
31222 - HA not configured.......................................................................................159
31223 - HA Heartbeat transmit failure...................................................................159
31224 - HA configuration error...............................................................................159
31225 - HA service start failure...............................................................................159
31226 - HA availability status degraded................................................................160
31227 - HA availability status failed.......................................................................160
31228 - HA standby offline......................................................................................160
31229 - HA score changed........................................................................................161
31230 - Recent alarm processing fault....................................................................161
31231 - Platform alarm agent fault..........................................................................161
31232- Late heartbeat warning................................................................................161
31240 - Measurements collection fault...................................................................162
31250 - RE port mapping fault................................................................................162
31260 - Database SNMP Agent................................................................................162
31270 - Logging output.............................................................................................162
31280 - HA Active to Standby transition...............................................................163
31281 - HA Standby to Active transition...............................................................163
32113 - Uncorrectable ECC memory error.............................................................163
32114 - SNMP get failure..........................................................................................163
32300 – Server fan failure.........................................................................................164
32301 - Server internal disk error............................................................................164
32302 – Server RAID disk error...............................................................................164
32303 - Server Platform error...................................................................................165
32304 - Server file system error...............................................................................165
32305 - Server Platform process error....................................................................165
32307 - Server swap space shortage failure...........................................................165
32308 - Server provisioning network error............................................................166
32312 - Server disk space shortage error................................................................166
32313 - Server default route network error...........................................................166
32314 - Server temperature error............................................................................167
32315 – Server mainboard voltage error................................................................167
32316 – Server power feed error.............................................................................167
32317 - Server disk health test error.......................................................................168
32318 - Server disk unavailable error.....................................................................168
32319 – Device error..................................................................................................169
32320 – Device interface error.................................................................................169
32321 – Correctable ECC memory error................................................................169
32322 – Power Supply A error.................................................................................169
910-6528-001 Revision D, December 2012
x
32323 – Power Supply B error.................................................................................170
32324 – Breaker panel feed error.............................................................................170
32325 – Breaker panel breaker error.......................................................................170
32326 – Breaker panel monitoring error................................................................173
32327 – Server HA Keepalive error........................................................................173
32331 – HP disk problem.........................................................................................174
32332 – HP Smart Array controller problem.........................................................174
32333 – HP hpacucliStatus utility problem...........................................................174
32334 - Multipath device access link problem......................................................175
32335 - Switch link down error...............................................................................175
32336– Half Open TCP Socket Limit......................................................................175
32403 – PM&C backup failed..................................................................................176
32500 – Server disk space shortage warning.........................................................176
32501 – Server application process error...............................................................176
32502 – Server hardware configuration error.......................................................176
32503 – Server RAM shortage warning..................................................................177
32505 – Server swap space shortage warning.......................................................177
32506 – Server default router not defined.............................................................177
32507 – Server temperature warning.....................................................................178
32508 – Server core file detected.............................................................................178
32509 – Server NTP Daemon not synchronized...................................................178
32510 – CMOS battery voltage low.........................................................................179
32511 – Server disk self test warning.....................................................................179
32512 – Device warning............................................................................................179
32513 – Device interface warning...........................................................................179
32514 – Server reboot watchdog initiated..............................................................180
32515 – Server HA failover inhibited.....................................................................180
32516 – Server HA Active to Standby transition..................................................180
32517 – Server HA Standby to Active transition..................................................180
32518 – Platform Health Check failure..................................................................181
32519 – NTP Offset Check failure...........................................................................181
32520 – NTP Stratum Check failure........................................................................181
32521 – SAS Presence Sensor Missing....................................................................181
32522 – SAS Drive Missing......................................................................................182
32523 – DRBD failover busy....................................................................................182
32524 – HP disk resync.............................................................................................182
32525 – Telco Fan Warning......................................................................................183
32526 – Telco Temperature Warning......................................................................183
32527 – Telco Power Supply Warning...................................................................183
32528 – Invalid BIOS value......................................................................................183
32529– Server Kernel Dump File Detected............................................................184
910-6528-001 Revision D, December 2012
xi
32530– TPD Upgrade Failed....................................................................................184
32531– Half Open Socket Warning Limit..............................................................184
32532– Server Upgrade Pending Accept/Reject...................................................184
32603 – PM&C backup to remote server failed.....................................................185
Chapter 4: Key Performance Indicators (KPIs)...........................186
General KPIs information....................................................................................................187
KPIs overview............................................................................................................187
KPIs.............................................................................................................................187
Viewing KPIs ............................................................................................................187
KPIs data export elements ......................................................................................187
Exporting KPIs...........................................................................................................188
KPIs server elements ............................................................................................................189
Computer Aided Policy Making (CAPM) KPIs................................................................190
Charging Proxy Application (CPA) KPIs..........................................................................190
Communication Agent (ComAgent) KPIs.........................................................................191
Connection Maintenance KPIs............................................................................................191
Diameter (DIAM) KPIs.........................................................................................................191
IP Front End (IPFE) KPIs......................................................................................................192
Message Processor (MP) KPIs.............................................................................................192
Full Address Based Resolution (FABR) KPIs....................................................................193
Range Based Address Resolution (RBAR) KPIs...............................................................193
Session Binding Repository (SBR) KPIs.............................................................................194
Chapter 5: Measurements................................................................195
General measurements information...................................................................................197
Measurements............................................................................................................197
Measurement elements ............................................................................................197
Generating a measurements report........................................................................198
Measurements data export elements .....................................................................199
Exporting measurements reports...........................................................................200
Application Routing Rules measurements........................................................................201
RxApplRuleSelected.................................................................................................202
RxApplRuleFwdFailAll............................................................................................202
RxApplRuleFwdFailUnavail...................................................................................202
RxApplRuleDuplicatePriority.................................................................................203
Computer Aided Policy Making (CAPM) measurements..............................................203
CAPM_Temp_Invoked.............................................................................................203
CAPM_CondSet_True..............................................................................................204
CAPM_Action_Set_Fails..........................................................................................204
910-6528-001 Revision D, December 2012
xii
Communication Agent (ComAgent) Performance measurements................................205
CAAvgDataFIFOQueueUtil....................................................................................207
CAAvgMxFIFOQueueUtil.......................................................................................208
CAAvgQueueUtil .....................................................................................................208
CAAvgRsrcPoolUtil .................................................................................................209
CAAvgRxStackEvents .............................................................................................209
CAAvgTxStackEvents .............................................................................................209
CADSTx .....................................................................................................................210
CAHSTxRsrc..............................................................................................................210
CAHSTxRsrcRateAvg...............................................................................................210
CAHSTxRsrcRateMax..............................................................................................211
CAPeakDataFIF0QueueUtil....................................................................................211
CAPeakMxFIFOQueueUtil......................................................................................211
CAPeakQueueUtil ....................................................................................................212
CAPeakRsrcPoolUtil ................................................................................................212
CAPeakRxStackEvents ............................................................................................213
CAPeakTxStackEvents ............................................................................................213
CARSTx .....................................................................................................................213
CARx...........................................................................................................................214
CARxSuccess..............................................................................................................214
CATransEndAbnorm ..............................................................................................215
CATransEndAbnormRateAvg ...............................................................................215
CATransEndAbnormRateMax ...............................................................................215
CATransEndNorm ...................................................................................................216
CATransPendingAvg ..............................................................................................216
CATransPendingMax ..............................................................................................217
CATransRateAvg .....................................................................................................217
CATransRateMax .....................................................................................................217
CATransStarted ........................................................................................................218
CATransTimeAvg ....................................................................................................218
CATransTimeMax ....................................................................................................218
CATx...........................................................................................................................219
CATxSuccess..............................................................................................................219
Communication Agent (ComAgent) Exception measurements.....................................219
CADSTxDscrdCong .................................................................................................224
CAHSTxDscrdCongSR.............................................................................................224
CAHSRsrcErr.............................................................................................................225
CAHSTxDscrdUnavailSR........................................................................................225
CAHSTxDscrdUnknownSR.....................................................................................226
CAHSTxDscrdUnkwnRsrc......................................................................................226
CAHSTxRsrc..............................................................................................................227
910-6528-001 Revision D, December 2012
xiii
CARsrcPoolFul .........................................................................................................227
CARSTxDscrdCong .................................................................................................227
CARSTxDscrdSvcUnavail .......................................................................................228
CARxDiscUnexpEvent ............................................................................................228
CARxDscrdConnUnavail ........................................................................................229
CARxDscrdDecodeFailed .......................................................................................229
CARxDscrdIncompat ...............................................................................................230
CARxDscrdInternalErr ............................................................................................230
CARxDscrdLayerSendFail ......................................................................................230
CARxDscrdMsgLenErr ...........................................................................................231
CARxDscrdUnkServer ............................................................................................231
CARxDscrdUnkStkLyr ............................................................................................232
CARxMsgUnknown ................................................................................................232
CAStackQueueFul ....................................................................................................232
CATransDscrdInvCorrId ........................................................................................233
CATransDscrdStaleErrRsp .....................................................................................233
CATransEndAbnorm ..............................................................................................234
CATransEndAbnormRateAvg ...............................................................................234
CATransEndAbnormRateMax ...............................................................................235
CATransEndAnsErr .................................................................................................235
CATransEndErr ........................................................................................................235
CATransEndNoResources ......................................................................................236
CATransEndNoResponse .......................................................................................236
CATransEndUnkwnSvc ..........................................................................................237
CATransEndUnregSvc ............................................................................................237
CATransRetx .............................................................................................................238
CATransStaleSuccessRsp ........................................................................................238
CATxDscrdConnUnAvail........................................................................................239
CATxDscrdDestUserIncmpat..................................................................................239
CATxDscrdEncodeFail.............................................................................................239
CATxDscrdInternalErr ............................................................................................240
CATxDscrdMxSendFail...........................................................................................240
CATxDscrdUnknownSvc ........................................................................................241
CATxDscrdUnkServer .............................................................................................241
CATxDscrdUnregSvc ..............................................................................................241
Connection Congestion measurements.............................................................................242
ConnOnsetCL1..........................................................................................................243
ConnOnsetCL2..........................................................................................................243
ConnOnsetCL3..........................................................................................................243
ConnOnsetCL4..........................................................................................................244
EvRemoteBusyCongested........................................................................................244
910-6528-001 Revision D, December 2012
xiv
EvSmoothedEmrAvg................................................................................................244
EvSmoothedEmrPeak...............................................................................................245
RxRejectedConnCongestion....................................................................................245
TmConnInCL1...........................................................................................................245
TmConnInCL2...........................................................................................................246
TmConnInCL3...........................................................................................................246
TmConnInCL4...........................................................................................................246
Connection Exception measurements................................................................................247
EvConnCerValFail....................................................................................................248
EvConnCexIpChkFail...............................................................................................248
EvConnCnxFail..........................................................................................................249
EvConnDnsFail..........................................................................................................249
EvConnFarEndClose................................................................................................249
EvConnManClose.....................................................................................................250
EvConnPeerNumIpFail............................................................................................250
EvConnRejMultiHomedSCTPAtt...........................................................................250
EvConnRelease..........................................................................................................251
EvConnSockInitFail..................................................................................................251
EvConnTransFail.......................................................................................................251
TxConnSendFail........................................................................................................252
Connection Performance measurements...........................................................................252
EvConnCnxSuccess...................................................................................................255
EvPerConnQueueCongestionChange....................................................................255
RxConnAvgMPS.......................................................................................................256
RxConnMsgs..............................................................................................................256
RxConnOctets............................................................................................................257
RxConnPeakMPS......................................................................................................257
RxConnRecvBufAvg.................................................................................................257
RxConnRecvBufPeak................................................................................................258
RxMsgRateAvg..........................................................................................................258
RxMsgRatePeak.........................................................................................................259
TmRxMPSDelay_MaxCapacity...............................................................................260
TmRxMPSDelay_SharedCapacity..........................................................................260
TXConnMsgs.............................................................................................................261
TxConnOctets............................................................................................................261
TxConnSendBufAvg.................................................................................................262
TxConnSendBufPeak................................................................................................262
TxPerConnQueueAvg..............................................................................................262
TxPerConnQueuePeak.............................................................................................263
Diameter Signaling Router (DSR) Application Exception measurements...................264
RxApplRequestNoRoutes........................................................................................265
910-6528-001 Revision D, December 2012
xv
RxApplUnavailable...................................................................................................265
RxApplUnavailableForAnswer...............................................................................266
RxApplUnavailableForRequest..............................................................................266
TxFabrFullDRLRequestReject.................................................................................267
TxFabrFullDRLAnswerDiscard..............................................................................268
TxRbarFullDRLRequestReject.................................................................................268
TxRbarFullDRLAnswerDiscard..............................................................................269
Diameter Signaling Router (DSR) Application Performance measurements..............269
RxApplRequestFwdSuccess....................................................................................271
RxApplAnswerFwdSuccess....................................................................................272
RxApplRequestReceived..........................................................................................272
RxApplAnswerReceived..........................................................................................272
RxCpaAnswerMsgQueueAvg.................................................................................273
RxCpaAnswerMsgQueuePeak................................................................................273
RxCpaAnswerProcessed..........................................................................................273
RxCpaEventMsgQueueAvg....................................................................................274
RxCpaEventMsgQueuePeak...................................................................................274
RxCpaMsgRateAvg..................................................................................................274
RxCpaMsgRatePeak..................................................................................................275
RxCpaRequestMsgQueueAvg................................................................................275
RxCpaRequestMsgQueuePeak...............................................................................275
RxCpaRequestProcessed..........................................................................................276
RxFabrMsgRateAvg..................................................................................................276
RxFabrMsgRatePeak.................................................................................................276
RxFabrRequestMsgQueueAvg................................................................................277
RxFabrRequestMsgQueuePeak...............................................................................277
RxFabrRequestProcessed.........................................................................................278
RxRbarMsgRateAvg.................................................................................................278
RxRbarMsgRatePeak................................................................................................279
RxRbarRequestMsgQueueAvg...............................................................................279
RxRbarRequestMsgQueuePeak..............................................................................280
RxRbarRequestProcessed.........................................................................................280
TxApplTransSuccess.................................................................................................281
Diameter Egress Transaction measurements....................................................................281
RxAnswerExpectedAll.............................................................................................282
RxAnswerMsgQueueFullDiscard...........................................................................282
TxAnswerTimeout....................................................................................................283
TxConnAnswerMsgs................................................................................................283
TxConnectionFailed..................................................................................................284
TxConnRequestMsgs................................................................................................284
TxRequestSuccessAllConn.......................................................................................284
910-6528-001 Revision D, December 2012
xvi
Diameter Exception measurements....................................................................................285
EvApplIdListInconsistency.....................................................................................288
EvConnCeaIdValFail................................................................................................289
EvConnCexTO...........................................................................................................290
EvConnDpaTO..........................................................................................................290
EvConnNoComnApps.............................................................................................290
EvConnPrvFail..........................................................................................................291
EvConnRejected........................................................................................................291
EvConnRejInsufficientIngressMps.........................................................................291
EvConnRejMaxConnExceeded...............................................................................292
EvConnWdFail..........................................................................................................292
EvConnWdSuspect...................................................................................................293
EvMpCerIDValFail...................................................................................................293
EvTransLifetimeExceededMp.................................................................................293
RxAnswerMsgQueueFullDiscard...........................................................................294
RxAnswerUnexpected..............................................................................................294
RxConnCeaError.......................................................................................................295
RxConnFailMalfMsg.................................................................................................295
RxConnInvalidMsg...................................................................................................295
RxMaxMpsRejectConn.............................................................................................296
RxMpCongestionDiscardMp...................................................................................296
RxMpCongestionRejectConn..................................................................................297
RxMpCongestionRejectMp......................................................................................298
RxConnUnexpCex.....................................................................................................298
RxConnUnexpDpx....................................................................................................299
RxConnUnexpDwx...................................................................................................299
RxMaxMpsRejectMp................................................................................................299
RxPduPoolEmptyDiscard........................................................................................300
RxRoutableRejectMsgsMp.......................................................................................300
TmConnDegraded....................................................................................................301
TmConnEnabledNotAvail.......................................................................................302
TxAllConnQueueFullAnswerDiscard....................................................................302
TxConnCeaError.......................................................................................................303
TxReqMsgApplMismatch........................................................................................303
TxReqMsgPerConnPtrMax......................................................................................303
TxRequestEgressLoop..............................................................................................304
Diameter Ingress Transaction Exception measurements................................................304
RxAnsFwdFailed.......................................................................................................307
RxDecodeFailure.......................................................................................................307
RxMaxMpsDiscardConn..........................................................................................308
RxMaxMpsDiscardMp.............................................................................................308
910-6528-001 Revision D, December 2012
xvii
RxMessageLooping...................................................................................................309
RxMpCongestionDiscardConn...............................................................................309
RxNoRoutesFound....................................................................................................310
RxNoRulesFailure.....................................................................................................311
RxPrtRuleRejection...................................................................................................312
RxRejectedAll.............................................................................................................312
RxRejectedOther........................................................................................................313
RxRequestMsgQueueFullDiscard...........................................................................313
RxRoutableDiscardedMsgsMp...............................................................................313
RxTransactionTimeout.............................................................................................314
TxAllConnQueueFullRequestReject.......................................................................315
TxPerConnQueueFullAnswerDiscard...................................................................315
TxPerConnQueueFullRequestDiscard...................................................................316
TxPtrListEmpty.........................................................................................................316
TxRerouteQueueFullReject......................................................................................317
Diameter Ingress Transaction Performance measurements...........................................317
RxConnRequestMsgs................................................................................................319
TxAnswer1xxx...........................................................................................................319
TxAnswer2xxx...........................................................................................................319
TxAnswer3xxx...........................................................................................................320
TxAnswer4xxx...........................................................................................................320
TxAnswer5xxx...........................................................................................................320
TxAnswerFailure.......................................................................................................321
TxAnswerLocalNode................................................................................................321
TxAnswerOther.........................................................................................................321
Diameter Performance measurements...............................................................................322
EvConnPrvSuccess....................................................................................................325
EvPerConnPtrQueueAvg.........................................................................................326
EvPerConnPtrQueuePeak........................................................................................326
RoutingMsgs..............................................................................................................327
RxAcceptedRequestsMp..........................................................................................327
RxAnswerExpectedAll.............................................................................................327
RxAnswerExpectedAllMp.......................................................................................328
RxAnswerExpectedRoutedMp................................................................................328
RxAnswerMsgsMp...................................................................................................329
RxConnAnswerMsgs................................................................................................329
RxConnCea................................................................................................................329
RxConnCer.................................................................................................................330
RxConnDpa................................................................................................................330
RxConnDpr................................................................................................................330
RxConnDwa...............................................................................................................330
910-6528-001 Revision D, December 2012
xviii
RxConnDwr...............................................................................................................331
RxConnOtherNonRoutable.....................................................................................331
RxConnRequestMsgs................................................................................................331
RxConnRoutableMsgs..............................................................................................332
RxMaxMpsAcceptedMp..........................................................................................332
RxMaxMpsAcceptedRequestsMp...........................................................................332
RxMsgSize..................................................................................................................333
RxMsgSizeAvg..........................................................................................................333
RxMsgSizePeak.........................................................................................................334
RxRequestMsgsMp...................................................................................................334
RxRequestNoErrors..................................................................................................334
RxRequestNoErrorsMp............................................................................................335
RxRoutableAcceptedMsgsMp.................................................................................335
RxRoutableMsgsMp.................................................................................................336
TmConnAvail............................................................................................................336
TmConnPrvRspAvg.................................................................................................336
TmResponseTimeDownstream...............................................................................337
TmResponseTimeDownstreamMp.........................................................................337
TmResponseTimeUpstream....................................................................................338
TxAnswerMsgsMp....................................................................................................338
TxConnAnswerMsgs................................................................................................338
TxConnCea.................................................................................................................339
TxConnCer.................................................................................................................339
TxConnDpa................................................................................................................339
TxConnDpr................................................................................................................340
TxConnDwa...............................................................................................................340
TxConnDwr...............................................................................................................340
TxConnRequestMsgs................................................................................................340
TxMsgSize..................................................................................................................341
TxMsgSizeAvg...........................................................................................................341
TxMsgSizePeak..........................................................................................................342
TxRequestMsgsMp...................................................................................................342
TxRequestSuccessAllMp..........................................................................................342
Diameter Rerouting measurements....................................................................................343
RxRerouteAnswerRsp..............................................................................................343
RxRerouteAnswerRspMp........................................................................................344
TxRerouteAnswerResponse....................................................................................344
TxRerouteAnswerTimeout......................................................................................344
TxRerouteAttempts...................................................................................................345
TxRerouteConnFailure.............................................................................................345
TxRerouteSuccessSent..............................................................................................346
910-6528-001 Revision D, December 2012
xix
Message Priority measurements.........................................................................................346
ExConnPeerUnsuppMp...........................................................................................347
ExConnUnexpMp.....................................................................................................348
RxMsgPri0Ingress.....................................................................................................349
RxMsgPri0PeerRule..................................................................................................349
RxMsgPri1Ingress.....................................................................................................349
RxMsgPri1PeerRule..................................................................................................349
RxMsgPri2Ingress.....................................................................................................350
RxMsgPri2PeerRule..................................................................................................350
Message Processor (MP) Performance measurements....................................................350
EvDiameterProcessAvg............................................................................................353
EvDiameterProcessPeak...........................................................................................354
EvMpCongestionEntered.........................................................................................354
EvPduPoolAvg..........................................................................................................355
EvPduPoolPeak.........................................................................................................355
EvPtrListAvg.............................................................................................................356
EvPtrListPeak............................................................................................................356
EvStasisModeMaxConnections...............................................................................357
EvStasisModeMpCongestion..................................................................................358
RxAnswerMsgQueueAvg........................................................................................358
RxAnswerMsgQueuePeak.......................................................................................359
RxMsgRateAvgMp....................................................................................................359
RxMsgRatePeakMp...................................................................................................359
RxRequestMsgQueueAvg........................................................................................360
RxRequestMsgQueuePeak.......................................................................................360
TmAnswerTimeAvg.................................................................................................361
TmAnswerTimePeak................................................................................................361
TmMpCongestion.....................................................................................................362
TmRequestTimeAvg.................................................................................................363
TMRequestTimePeak................................................................................................363
TxAllConnQueueAvg...............................................................................................364
TxAllConnQueuePeak..............................................................................................364
TxRerouteQueueAvg................................................................................................365
TxRerouteQueuePeak...............................................................................................365
OAM Alarm measurements................................................................................................366
OAM System measurements...............................................................................................366
Peer Node Performance measurements.............................................................................368
RxPeerAnswers.........................................................................................................368
RxPeerRequests.........................................................................................................369
TxPeerAnswers..........................................................................................................369
TxPeerRequests.........................................................................................................369
910-6528-001 Revision D, December 2012
xx
Peer Routing Rules measurements.....................................................................................370
RxPrtSelected.............................................................................................................370
RxRuleDuplicatePriority..........................................................................................371
RxRuleFwdFailActionSendAns..............................................................................371
RxRuleFwdFailAll.....................................................................................................372
RxRuleSelected..........................................................................................................372
Charging Proxy Application (CPA) Performance measurements.................................373
RxCpaAcaEvent.........................................................................................................374
RxCpaAcaInterim......................................................................................................374
RxCpaAcaStart...........................................................................................................375
RxCpaAcaStop...........................................................................................................375
RxCpaAccounting.....................................................................................................375
RxCpaAcrEvent.........................................................................................................376
RxCpaAcrInterim......................................................................................................376
RxCpaAcrStart...........................................................................................................376
RxCpaAcrStop...........................................................................................................377
RxCpaMsgProcessed................................................................................................377
TxCpaAnswerMsgToDrl..........................................................................................377
TxCpaMsgCopyInd..................................................................................................378
TxCpaRequestMsgToDrl..........................................................................................378
TxCpaTraceInd..........................................................................................................378
Charging Proxy Application (CPA) Exception measurements......................................379
EvCpaMessageDecodeFail.......................................................................................380
EvCpaMissingAvp....................................................................................................380
EvCpaOOS.................................................................................................................380
EvCpaSubResourceCongested................................................................................381
EvCpaUnexpectedSess.............................................................................................381
EvCpaUnkDiameterAppId......................................................................................381
RxCpaHaSubResourceUnavail...............................................................................382
RxCpaNon2xxAnswer..............................................................................................382
RxCpaOpStatusUnavail...........................................................................................382
RxCpaUnexpected.....................................................................................................383
TxCpaAnswerByCpa................................................................................................383
TxCpaFullDRLAnswerDiscard...............................................................................383
TxCpaFullDRLRequestReject..................................................................................384
TxCpaRteFailure........................................................................................................384
Charging Proxy Application (CPA) Session DB measurements....................................385
EvCpaNoSbrAccess..................................................................................................386
EvCpaSbrAvgRespTime..........................................................................................386
EvCpaSbrCreateSess.................................................................................................387
EvCpaSbrDeleteSess.................................................................................................387
910-6528-001 Revision D, December 2012
xxi
EvCpaSbrPeakRespTime..........................................................................................387
EvCpaSbrQryError....................................................................................................388
EvCpaSbrQryMatch..................................................................................................388
EvCpaSbrQryNoMatch............................................................................................388
EvCpaSbrRespTime..................................................................................................389
EvCpaSbrUpdateSess...............................................................................................389
RxCpaUndeliveredMsg............................................................................................389
TxCpaSbrQueryTot...................................................................................................390
Message Copy measurements.............................................................................................390
DASCopyAnswerRx.................................................................................................391
DASCopyDiscarded..................................................................................................392
DASCopyFailureMPCong.......................................................................................392
DASCopyFailureSizeExceeded...............................................................................393
DASCopyFailurePeerApplIdUnsup.......................................................................393
DASCopyFailureRLNotProv...................................................................................393
DASCopyRetransmits...............................................................................................394
DASCopyRetransmitsExceeded..............................................................................394
DASCopyTx...............................................................................................................395
DASCopyValidAnswer............................................................................................395
TxMsgCopyQueueAve.............................................................................................396
TxMsgCopyQueueFullDiscard...............................................................................396
TxMsgCopyQueuePeak...........................................................................................396
IP Front End (IPFE) Exception measurements..................................................................397
PcapDroppedPackets................................................................................................397
TsaUnexpctedSctp.....................................................................................................398
TsaUnexpctedTcp......................................................................................................398
TxReject.......................................................................................................................398
TxRejectSctp...............................................................................................................399
IP Front End (IPFE) Performance measurements.............................................................399
AsNewAssociations..................................................................................................400
AsNewAssociationsSctp..........................................................................................401
IpfeNewAssociations................................................................................................401
IpfeNewAssociationsSctp........................................................................................401
RxIpfeBytes................................................................................................................401
RxIpfeBytesSctp.........................................................................................................402
RxIpfePackets.............................................................................................................402
RxTsaBytes.................................................................................................................402
RxTsaBytesSctp..........................................................................................................402
RxTsaPackets.............................................................................................................403
RxTsaPacketsSctp......................................................................................................403
TsaNewAssociations.................................................................................................403
910-6528-001 Revision D, December 2012
xxii
TsaNewAssociationsSctp.........................................................................................404
TxAsBytes...................................................................................................................404
TxAsBytesSctp...........................................................................................................404
TxAsPackets...............................................................................................................405
TxAsPacketsSctp.......................................................................................................405
Full Address Based Resolution (FABR) Application Performance
measurements..................................................................................................................405
RxDpResponseTimeAvg..........................................................................................407
RxFabrAvgMsgSize..................................................................................................407
RxFabrDpResponseMsgQueueAvg.......................................................................407
RxFabrDpResponseMsgQueuePeak.......................................................................408
RxFabrMsgs................................................................................................................408
RxFabrResolAll..........................................................................................................409
RxFabrResolAllMp....................................................................................................409
RxFabrResolImpi.......................................................................................................409
RxFabrResolImpu......................................................................................................409
RxFabrResolImsi........................................................................................................410
RxFabrResolMsisdn..................................................................................................410
RxFabrResolRateAvg................................................................................................410
RxFabrResolRatePeak...............................................................................................411
TxFabrAbandonRequest..........................................................................................411
TxFabrFwdDefaultDest............................................................................................411
TxFabrFwdNochange...............................................................................................412
TxFabrFwdSuccess....................................................................................................412
TxFabrMsgAttempt...................................................................................................412
Full Address Based Resolution (FABR) Application Exception measurements..........413
RxFabrDecodeFailureResol.....................................................................................414
RxFabrResolFailAll...................................................................................................414
RxFabrResolFailCmdcode........................................................................................415
RxFabrResolFailImpiMatch.....................................................................................415
RxFabrResolFailImpuMatch....................................................................................415
RxFabrResolFailImsiMatch......................................................................................416
RxFabrResolFailMsisdnMatch................................................................................416
RxFabrResolFailNoAddrAvps................................................................................416
RxFabrResolFailNoValidAddr................................................................................417
RxFabrUnkApplId....................................................................................................417
TxFabrDbConFail......................................................................................................418
TxFabrFwdFail...........................................................................................................418
Range Based Address Resolution (RBAR) Application Performance
measurements..................................................................................................................418
RxRbarAvgMsgSize..................................................................................................420
910-6528-001 Revision D, December 2012
xxiii
RxRbarMsgs...............................................................................................................420
RxRbarResolAll.........................................................................................................421
RxRbarResolAllMp...................................................................................................421
RxRbarResolImpi......................................................................................................421
RxRbarResolImpu.....................................................................................................422
RxRbarResolImsi.......................................................................................................422
RxRbarResolIpv4.......................................................................................................422
RxRbarResolIpv6prefix............................................................................................423
RxRbarResolMsisdn..................................................................................................423
RxRbarResolRateAvg...............................................................................................423
RxRbarResolRatePeak..............................................................................................424
RxRbarResolSingleAddr..........................................................................................424
RxRbarResolUnsigned16..........................................................................................424
TxRbarFwdDefaultDest...........................................................................................425
TxRbarFwdNoChange..............................................................................................425
TxRbarFwdSuccess...................................................................................................425
TxRbarMsgAttempt..................................................................................................426
Range Based Address Resolution (RBAR) Application Exception measurements.....426
RxRbarDecodeFailureResol.....................................................................................427
RxRbarResolFailAll...................................................................................................428
RxRbarResolFailCmdcode.......................................................................................428
RxRbarResolFailDbFail............................................................................................429
RxRbarResolFailImpiMatch.....................................................................................429
RxRbarResolFailImpuMatch...................................................................................429
RxRbarResolFailImsiMatch.....................................................................................430
RxRbarResolFailIpv4Match.....................................................................................430
RxRbarResolFailIpv6prefixMatch...........................................................................431
RxRbarResolFailMsisdnMatch................................................................................431
RxRbarResolFailNoAddrAvps................................................................................431
RxRbarResolFailNoValidAddr................................................................................432
RxRbarResolFailUnsigned16Match........................................................................432
RxRbarUnkApplId....................................................................................................433
Route List measurements.....................................................................................................433
RxRouteListFailure...................................................................................................434
RxRouteListSelected.................................................................................................434
RxRouteListUnavailable...........................................................................................435
TmRouteListOutage..................................................................................................435
Routing Usage measurements.............................................................................................436
RxRoutedIntraMPAttempt......................................................................................436
RxRoutedPeerDirect.................................................................................................437
RxRoutedPeerRouteList...........................................................................................437
910-6528-001 Revision D, December 2012
xxiv
RxRoutedPrt...............................................................................................................437
Session Binding Repository (SBR) Exception measurements.........................................438
Sbr.TxError ................................................................................................................438
Sbr.TxShedCreates....................................................................................................439
Sbr.TxShedWrites......................................................................................................440
Sbr.TxShedReads.......................................................................................................440
Sbr.TxShedAll............................................................................................................440
Sbr.StackQueueFull...................................................................................................441
Session Binding Repository (SBR) Performance measurements....................................441
Sbr.RxCreate..............................................................................................................443
Sbr.RxUpdate.............................................................................................................443
Sbr.RxRead.................................................................................................................443
Sbr.RxDelete...............................................................................................................444
Sbr.RxStatus...............................................................................................................444
Sbr.TxSuccess ............................................................................................................444
Sbr.RxReqRatePeak ..................................................................................................444
Sbr.RxServTimeAvg .................................................................................................445
Sbr.RxServTimePeak ................................................................................................445
Sbr.EvStaleRecRemoved..........................................................................................445
Sbr.EvCreateUpdateMod.........................................................................................446
Sbr.EvAvgSessionAge .............................................................................................446
Sbr.RxReqRateAvg ...................................................................................................446
Sbr.EvSchdStaleRec...................................................................................................446
Sbr.EvStaleRecRevived ............................................................................................447
Sbr.EvMostlyStaleSessPartition .............................................................................447
Sbr.EvAvgSessionAgePartition ..............................................................................447
Sbr.RxIngressMsgQueuePeak.................................................................................448
Sbr.RxIngressMsgQueueAvg..................................................................................448
Chapter 6: Copyright, notice, trademarks, and patents.............449
EAGLE XG Diameter Signaling Router (DSR) - Copyright, Notice, Trademarks,
and Patents.......................................................................................................................450
Glossary..................................................................................................................451
910-6528-001 Revision D, December 2012
xxv
List of Figures
Figure 1: Flow of Alarms....................................................................................................................46
Figure 2: Alarm Indicators Legend...................................................................................................47
Figure 3: Trap Count Indicator Legend...........................................................................................47
Figure 4: Breaker Panel LEDs..........................................................................................................171
Figure 5: Breaker Panel Setting.......................................................................................................172
910-6528-001 Revision D, December 2012
xxvi
List of Tables
Table 1: Admonishments...................................................................................................................30
Table 2: Export Server Elements.......................................................................................................37
Table 3: Active Tasks Elements.........................................................................................................40
Table 4: Active Tasks Report Elements............................................................................................42
Table 5: Scheduled Tasks Elements..................................................................................................43
Table 6: Alarm/Event ID Ranges .....................................................................................................47
Table 7: Alarm and Event Types ......................................................................................................48
Table 8: Schedule Active Alarm Data Export Elements................................................................50
Table 9: Schedule Event Data Export Elements..............................................................................53
Table 10: Congestion Thresholds......................................................................................................70
Table 11: Schedule KPI Data Export Elements..............................................................................187
Table 12: KPIs Server Elements.......................................................................................................189
Table 13: CAPM KPIs.......................................................................................................................190
Table 14: Charging Proxy Application (CPA) KPIs.....................................................................190
Table 15: Communication Agent KPIs...........................................................................................191
Table 16: Connection Maintenance KPIs.......................................................................................191
Table 17: DIAM KPIs........................................................................................................................191
Table 18: IPFE KPIs...........................................................................................................................192
Table 19: MP KPIs.............................................................................................................................192
Table 20: FABR KPIs.........................................................................................................................193
Table 21: RBAR KPIs.........................................................................................................................193
Table 22: SBR KPIs............................................................................................................................194
Table 23: Measurements Elements..................................................................................................198
Table 24: Schedule Measurement Data Export Elements............................................................199
Table 25: Application Routing Rule Measurements....................................................................201
Table 26: Communication Agent Performance Measurement Report Fields...........................205
Table 27: Communication Agent Exception Measurement Report Fields................................220
Table 28: Connection Congestion Measurement Report Fields.................................................242
Table 29: Connection Exception Measurement Report Fields....................................................247
Table 30: Connection Performance Measurement Report Fields...............................................252
Table 31: DSR Application Exception Measurement Report Fields..........................................264
Table 32: DSR Application Performance Measurement Report Fields.....................................269
Table 33: Diameter Egress Transaction Measurement Report Fields........................................281
Table 34: Diameter Exception Measurement Report Fields........................................................285
Table 35: Diameter Ingress Transaction Exception Measurement Report Fields....................305
Table 36: Diameter Ingress Transaction Performance Measurement Report Fields...............318
Table 37: DiameterPerformance Measurement Report Fields....................................................322
910-6528-001 Revision D, December 2012
xxvii
Table 38: Diameter Rerouting Measurement Report Fields........................................................343
Table 39: Message Priority Measurement Report Fields.............................................................346
Table 40: MP Performance Measurement Report Fields.............................................................351
Table 41: OAM Alarm measurements............................................................................................366
Table 42: OAM System measurements..........................................................................................366
Table 43: Peer Routing Rules Measurement Report Fields.........................................................368
Table 44: Peer Routing Rules Measurement Report Fields.........................................................370
Table 45: CPA Performance Measurement Report Fields...........................................................373
Table 46: CPA Exception Measurement Report Fields................................................................379
Table 47: CPA Session DB Measurement Report Fields..............................................................385
Table 48: Message Copy Measurement Report Fields.................................................................390
Table 49: IPFE Exception Measurement Report Fields................................................................397
Table 50: IPFE Performance Measurement Report Fields...........................................................399
Table 51: DSR Application Performance Measurement Report Fields.....................................405
Table 52: FABR Application Exception Measurement Report Fields........................................413
Table 53: RBAR Performance Measurement Report Fields........................................................419
Table 54: RBAR Exception Measurement Report Fields.............................................................426
Table 55: Route List Measurement Report Fields.........................................................................433
Table 56: Routing Usage Measurement Report Fields.................................................................436
Table 57: SBR Exception Measurement Report Fields.................................................................438
Table 58: SBR Performance Measurement Report Fields............................................................441
910-6528-001 Revision D, December 2012
xxviii
Chapter
1
Introduction
Topics:
•
•
•
•
•
•
Overview.....30
Scope and Audience.....30
Documentation Admonishments.....30
Customer Care Center.....31
Emergency Response.....33
Locate Product Documentation on the Customer
Support Site.....33
910-6528-001 Revision D, December 2012
This section contains an overview of the available
information for DSR alarms and events. The contents
include sections on the scope and audience of the
documentation, and how to contact Tekelec for
assistance.
29
Introduction
Overview
The DSR Alarms, KPIs, and Measurements documentation provides information about DSR alarms
and events, provides corrective maintenance procedures, and other information used in maintaining
the system.
This documentation provides:
• Information relevant to understanding alarms and events that may occur on the application
• Recovery procedures for addressing alarms and events, as necessary
• Procedures for viewing alarms and events, generating alarms reports, and viewing and exporting
alarms and events history
• Information relevant to understanding KPIs in the application
• The procedure for viewing KPIs
• Lists of KPIs
• Information relevant to understanding measurements in the application
• Measurement report elements, and the procedures for printing and exporting measurements
• Lists of measurements by function
Scope and Audience
This manual does not describe how to install or replace software or hardware.
This manual is intended for personnel who must maintain operation of the DSR. The manual provides
preventive and corrective procedures that will aid personnel in maintaining the DSR.
The corrective maintenance procedures are those used in response to a system alarm or output message.
These procedures are used to aid in the detection, isolation, and repair of faults.
Documentation Admonishments
Admonishments are icons and text throughout this manual that alert the reader to assure personal
safety, to minimize possible service interruptions, and to warn of the potential for equipment damage.
Table 1: Admonishments
DANGER:
(This icon and text indicate the possibility of personal injury.)
WARNING:
(This icon and text indicate the possibility of equipment damage.)
910-6528-001 Revision D, December 2012
30
Introduction
CAUTION:
(This icon and text indicate the possibility of service interruption.)
Customer Care Center
The Tekelec Customer Care Center is your initial point of contact for all product support needs. A
representative takes your call or email, creates a Customer Service Request (CSR) and directs your
requests to the Tekelec Technical Assistance Center (TAC). Each CSR includes an individual tracking
number. Together with TAC Engineers, the representative will help you resolve your request.
The Customer Care Center is available 24 hours a day, 7 days a week, 365 days a year, and is linked
to TAC Engineers around the globe.
Tekelec TAC Engineers are available to provide solutions to your technical questions and issues 7
days a week, 24 hours a day. After a CSR is issued, the TAC Engineer determines the classification of
the trouble. If a critical problem exists, emergency procedures are initiated. If the problem is not critical,
normal support procedures apply. A primary Technical Engineer is assigned to work on the CSR and
provide a solution to the problem. The CSR is closed when the problem is resolved.
Tekelec Technical Assistance Centers are located around the globe in the following locations:
Tekelec - Global
Email (All Regions): [email protected]
• USA and Canada
Phone:
1-888-FOR-TKLC or 1-888-367-8552 (toll-free, within continental USA and Canada)
1-919-460-2150 (outside continental USA and Canada)
TAC Regional Support Office Hours:
8:00 a.m. through 5:00 p.m. (GMT minus 5 hours), Monday through Friday, excluding holidays
• Caribbean and Latin America (CALA)
Phone:
USA access code +1-800-658-5454, then 1-888-FOR-TKLC or 1-888-367-8552 (toll-free)
TAC Regional Support Office Hours (except Brazil):
10:00 a.m. through 7:00 p.m. (GMT minus 6 hours), Monday through Friday, excluding holidays
• Argentina
Phone:
0-800-555-5246 (toll-free)
• Brazil
Phone:
910-6528-001 Revision D, December 2012
31
Introduction
0-800-891-4341 (toll-free)
TAC Regional Support Office Hours:
8:00 a.m. through 5:48 p.m. (GMT minus 3 hours), Monday through Friday, excluding holidays
• Chile
Phone:
1230-020-555-5468
• Colombia
Phone:
01-800-912-0537
• Dominican Republic
Phone:
1-888-367-8552
• Mexico
Phone:
001-888-367-8552
• Peru
Phone:
0800-53-087
• Puerto Rico
Phone:
1-888-367-8552 (1-888-FOR-TKLC)
• Venezuela
Phone:
0800-176-6497
• Europe, Middle East, and Africa
Regional Office Hours:
8:30 a.m. through 5:00 p.m. (GMT), Monday through Friday, excluding holidays
• Signaling
Phone:
+44 1784 467 804 (within UK)
• Software Solutions
Phone:
+33 3 89 33 54 00
• Asia
910-6528-001 Revision D, December 2012
32
Introduction
• India
Phone:
+91 124 436 8552 or +91 124 436 8553
TAC Regional Support Office Hours:
10:00 a.m. through 7:00 p.m. (GMT plus 5 1/2 hours), Monday through Saturday, excluding
holidays
• Singapore
Phone:
+65 6796 2288
TAC Regional Support Office Hours:
9:00 a.m. through 6:00 p.m. (GMT plus 8 hours), Monday through Friday, excluding holidays
Emergency Response
In the event of a critical service situation, emergency response is offered by the Tekelec Customer Care
Center 24 hours a day, 7 days a week. The emergency response provides immediate coverage, automatic
escalation, and other features to ensure that the critical situation is resolved as rapidly as possible.
A critical situation is defined as a problem with the installed equipment that severely affects service,
traffic, or maintenance capabilities, and requires immediate corrective action. Critical situations affect
service and/or system operation resulting in one or several of these situations:
• A total system failure that results in loss of all transaction processing capability
• Significant reduction in system capacity or traffic handling capability
• Loss of the system’s ability to perform automatic system reconfiguration
• Inability to restart a processor or the system
• Corruption of system databases that requires service affecting corrective actions
• Loss of access for maintenance or recovery operations
• Loss of the system ability to provide any required critical or major trouble notification
Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilities
may be defined as critical by prior discussion and agreement with the Tekelec Customer Care Center.
Locate Product Documentation on the Customer Support Site
Access to Tekelec's Customer Support site is restricted to current Tekelec customers only. This section
describes how to log into the Tekelec Customer Support site and locate a document. Viewing the
document requires Adobe Acrobat Reader, which can be downloaded at www.adobe.com.
1. Log into the Tekelec Customer Support site.
910-6528-001 Revision D, December 2012
33
Introduction
Note: If you have not registered for this new site, click the Register Here link. Have your customer
number available. The response time for registration requests is 24 to 48 hours.
2. Click the Product Support tab.
3. Use the Search field to locate a document by its part number, release number, document name, or
document type. The Search field accepts both full and partial entries.
4. Click a subject folder to browse through a list of related files.
5. To download a file to your location, right-click the file name and select Save Target As.
910-6528-001 Revision D, December 2012
34
Chapter
2
Alarms and Events, KPIs, and Measurements Overview
Topics:
•
•
•
•
•
Purpose of this documentation.....36
Documentation organization.....36
Displaying the file list.....36
Export Server.....37
Tasks.....39
910-6528-001 Revision D, December 2012
This section provides general information about the
application's alarms and events, KPIs, and
measurements.
35
Alarms and Events, KPIs, and Measurements
Overview
Purpose of this documentation
This documentation provides:
• Information relevant to understanding alarms and events that may occur on the application
• Recovery procedures for addressing alarms and events, as necessary
• Procedures for viewing alarms and events, generating alarms reports, and viewing and exporting
alarms and events history
• Information relevant to understanding KPIs in the application
• The procedure for viewing KPIs
• Lists of KPIs
• Information relevant to understanding measurements in the application
• Measurement report elements, and the procedures for printing and exporting measurements
• Lists of measurements by function
Documentation organization
Information in this document is organized into the following sections :
Introduction
Contains general information about the scope of this manual, its targeted
audience, and Tekelec Customer Care Center contact information
Alarms and Events, KPIs, and
Measurements Overview
Documentation purpose and organization, alarms and
event overview information and tasks
Alarms
Information and recovery procedures for alarms and events, organized first
by alarm category, then numerically by the number that appears in the
application
KPIs
Detailed KPI information, organized alphabetically by KPI name
Measurements
Detailed measurement information, organized alphabetically by measurement
category
Displaying the file list
Use this procedure to view the list of files located in the file management storage area of a server. The
amount of storage space currently in use can also be viewed on the Files page.
1. From the Main menu, select Status & Manage > Files.
The Status & Manage Files page appears.
2. Select a server.
All files stored on the selected server are displayed.
910-6528-001 Revision D, December 2012
36
Alarms and Events, KPIs, and Measurements
Overview
Export Server
From the Export Server page you can set an export target to receive exported performance data. Several
types of performance data can be filtered and exported using this feature. For more information about
how to create data export tasks, see:
•
•
•
•
Exporting active alarms
Exporting alarm and event history
Exporting KPIs
Exporting measurements reports
From the Export Server page you can manage file compression strategy and schedule the frequency
with which data files are exported.
Export Server elements
This table describes the elements on the Export Server page.
Table 2: Export Server Elements
Element
Hostname
Description
Data Input Notes
The server that automatically
receives exported performance
data
Format: Unique name for the
export server; may use either a
valid IP address, or hostname.
Range:
• IP address: dotted quad
decimal (IPv4) or colon hex
(IPv6)
• Hostname: Maximum length
is 20 characters;
alphanumeric characters (a-z,
A-Z, and 0-9) and minus sign
(-). Hostname must begin and
end with an alphanumeric
character. Hostname is case
sensitive.
Default: None
Username
Username used to access the
export server
Format: Textbox
Range: Maximum length is 32
characters; alphanumeric
characters (a-z, A-Z, and 0-9).
Default: None
910-6528-001 Revision D, December 2012
37
Alarms and Events, KPIs, and Measurements
Overview
Element
Description
Directory Path on Export Server Directory path string on the
export server
Data Input Notes
Format: Textbox
Range: Maximum length is 255
characters; valid value is any
UNIX string.
Default: None
Path to rsync on Export Server
Optional path to the rsync binary Format: Textbox
on the export server
Range: Maximum length is 4096
characters; alphanumeric
characters (a-z, A-Z, and
0-9),dash, underscore, period,
and forward slash.
Default: If no path is specified,
the "--rsync-path" option will not
be used
File Compression
Compression algorithm for
exported data
Format: Radio button
Range: gzip, bzip2, or none
Default: None
Upload Frequency
Frequency at which the export
occurs
Format: Radio button
Range: hourly, daily or weekly
Minute
If hourly is selected for Upload Format: Scrolling list
Frequency, this is the minute of
Range: 0 to 59
each hour when the transfer is
set to begin
Time of Day
Time of day the export occurs
Format: Time textbox
Range: 15-minute increments
Day of Week
If weekly is selected for Upload Format: Radio button
Frequency, this is the day of the
Range: Sunday through Saturday
week when exported data files
will be transferred to the export Default: Sunday
server
SSH Key Exchange
This button launches a dialog
box. The dialog requests
username and password and
initiates SSH key exchange.
Format: Button
Transfer Now
This button intiates an
immediate attempt to transfer
any data files in the export
directory to the export server.
Format: Button
910-6528-001 Revision D, December 2012
38
Alarms and Events, KPIs, and Measurements
Overview
Configuring an export server
The Export Server page enables you to configure a server to receive exported performance and
configuration data. Use this procedure to configure an export server.
1. Select Administration > Export Server.
The Export Server page appears.
2. Enter a Hostname.
See Export Server elements for details about the Hostname field and other fields that appear on
this page.
3. Enter a Username.
4. Enter a Directory Path on the Export server.
5. Enter the Path to Rsync on the Export server.
6. Select the File Compression type.
7. Select the Upload Frequency.
8. If you selected hourly for the upload frequency, select the Minute intervals.
9. If you selected daily or weekly for the upload frequency, select the Time of Day.
10. If you selected weekly for the upload frequency, select the Day of the Week.
11. Click Exchange SSH Key to transfer the SSH keys to the export server.
A password dialog box appears.
12. Enter the password.
The server will attempt to exchange keys with the specified export server. After the SSH keys are
successfully exchanged, continue with the next step.
13. Click OK or Apply.
The export server is now configured and available to receive performance and configuration data.
Tasks
The Tasks pages display the active, long running tasks and scheduled tasks on a selected server. The
Active Tasks page provides information such as status, start time, progress, and results for long
running tasks, while the Scheduled Tasks page provides a location to view, edit, and delete tasks that
are scheduled to occur.
Active Tasks
The Active Tasks page displays the long running tasks on a selected server. The Active Tasks page
provides information such as status, start time, progress, and results, all of which can be generated
into a report. Additionally, you can pause, restart, or delete tasks from this page.
Active Tasks elements
The Active Tasks page displays information in a tabular format where each tab represents a unique
server. By default, the current server's tab is selected when the page is loaded. This table describes
elements on the Active Tasks page.
910-6528-001 Revision D, December 2012
39
Alarms and Events, KPIs, and Measurements
Overview
Table 3: Active Tasks Elements
Active Tasks Element
Description
ID
Task ID
Name
Task name
Status
Current status of the task. Status values include:
running, paused, completed, exception, and
trapped.
Start Time
Time and date when the task was started
Update Time
Time and date the task's status was last updated
Result
Integer return code of the task. Values other than
0 (zero) indicate abnormal termination of the task.
Each value has a task-specific meaning.
Result Details
Details about the result of the task
Progress
Current progress of the task
Deleting a task
Use this procedure to delete one or more tasks.
1. Select Status & Manage > Tasks > Active Tasks.
The Active Tasks page appears.
2. Select a server.
Note: Hovering the cursor over any tab displays the name of the server.
All active tasks on the selected server are displayed.
3. Select one or more tasks.
Note: To delete a single task or multiple tasks, the status of each task selected must be one of the
following: completed, exception, or trapped.
Note: You can select multiple rows to delete at one time. To select multiple rows, press and hold
Ctrl as you click to select specific rows.
4. Click Delete.
A confirmation box appears.
5. Click OK to delete the selected task(s).
The selected task(s) are deleted from the table.
Deleting all completed tasks
Use this procedure to delete all completed tasks.
1. Select Status & Manage > Tasks > Active Tasks.
The Active Tasks page appears.
910-6528-001 Revision D, December 2012
40
Alarms and Events, KPIs, and Measurements
Overview
2. Select a server.
Note: Hovering the cursor over any tab displays the name of the server.
All active tasks on the selected server are displayed.
3. Click Delete all Completed.
A confirmation box appears.
4. Click OK to delete all completed tasks.
All tasks with the status of completed are deleted.
Canceling a running or paused task
Use this procedure to cancel a task that is running or paused.
1. Select Status & Manage > Tasks > Active Tasks.
The Active Tasks page appears.
2. Select a server.
Note: Hovering the cursor over any tab displays the name of the server.
All active tasks on the selected server are displayed.
3. Select a task.
4. Click Cancel.
A confirmation box appears.
5. Click OK to cancel the selected task.
The selected task is canceled.
Pausing a task
Use this procedure to pause a task.
1. Select Status & Manage > Tasks > Active Tasks.
The Active Tasks page appears.
2. Select a server.
Note: Hovering the mouse over any tab displays the name of the server.
All active tasks on the selected server are displayed.
3. Select a task.
Note: A task may be paused only if the status of the task is running.
4. Click Pause.
A confirmation box appears.
5. Click OK to pause the selected task.
The selected task is paused. For information about restarting a paused task, see Restarting a task.
Restarting a task
Use this procedure to restart a task.
910-6528-001 Revision D, December 2012
41
Alarms and Events, KPIs, and Measurements
Overview
1. Select Status & Manage > Tasks > Active Tasks.
The Active Tasks page appears.
2. Select a server.
Note: Hovering the mouse over any tab displays the name of the server.
All active tasks on the selected server are displayed.
3. Select a paused task.
Note: A task may be restarted only if the status of the task is paused.
4. Click Restart.
A confirmation box appears.
5. Click OK to restart the selected task.
The selected task is restarted.
Active Tasks report elements
The Active Tasks Report page displays report data for selected tasks. This table describes elements
on the Active Tasks Report page.
Table 4: Active Tasks Report Elements
Active Tasks Report Element
Description
ID
Task ID
Name
Task name
Admin State
Confirms task status
Status
Current status of the task. Status values include:
running, paused, completed, exception, and
trapped.
Progress
Current progress of the task
Start Time
Time and date when the task was started
Update Time
Time and date the task's status was last updated
Result
Integer return code of the task. Values other than
0 (zero) indicate abnormal termination of the task.
Each value has a task-specific meaning.
Result Details
Details about the result of the task
PID
Process ID from the operating system
Meta Task ID
ID of the task type
Generating an active task report
Use this procedure to generate an active task report.
910-6528-001 Revision D, December 2012
42
Alarms and Events, KPIs, and Measurements
Overview
1. Select Status & Manage > Tasks > Active Tasks.
The Active Tasks page appears.
2. Select a server.
Note: Hovering the mouse over any tab displays the name of the server.
All active tasks on the selected server are displayed.
3. Select one or more tasks.
Note: If no tasks are selected, all tasks matching the current filter criteria will be included in the
report.
4. Click Report.
The Tasks Report page appears.
5. Click Print to print the report.
6. Click Save to save the report.
Scheduled Tasks
The periodic export of certain data can be scheduled through the GUI. The Scheduled Tasks page
provides you with a location to view, edit, delete and generate reports of these scheduled tasks. For
more information about the types of data that can be exported, see:
•
•
•
•
Exporting active alarms
Exporting alarm and event history
Exporting KPIs
Exporting measurements reports
Viewing scheduled tasks
Use this procedure to view the scheduled tasks.
Select Status & Manage > Tasks > Scheduled Tasks.
The Scheduled Tasks page appears, and all scheduled tasks are displayed.
Scheduled Tasks elements
The Scheduled Tasks page displays information in a tabular format where each tab represents a
unique server. By default, the current server's tab is selected when the page is loaded. This table
describes elements on the Scheduled Tasks page.
Table 5: Scheduled Tasks Elements
Scheduled Tasks Element
Description
Task Name
Name given at the time of task creation
Description
Description of the task
Time of Day
The hour and minute the task is scheduled to run
910-6528-001 Revision D, December 2012
43
Alarms and Events, KPIs, and Measurements
Overview
Scheduled Tasks Element
Description
Day-of-Week
Day of the week the task is scheduled to run
Network Elem
The Network Element associated with the task
Editing a scheduled task
Use this procedure to edit a scheduled task.
1. Select Status & Manage > Tasks > Scheduled Tasks.
The Scheduled Tasks page appears, and all scheduled tasks are displayed.
2. Select a task.
3. Click Edit.
The Data Export page for the selected task appears.
4. Edit the available fields as necessary.
See Scheduled Tasks elements for details about the fields that appear on this page.
5. Click OK or Apply to submit the changes and return to the Scheduled Tasks page.
Deleting a scheduled task
Use this procedure to delete one or more scheduled tasks.
1. Select Status & Manage > Tasks > Scheduled Tasks.
The Scheduled Tasks page appears, and all scheduled tasks are displayed.
2. Select one or more tasks.
3. Click Delete.
A confirmation box appears.
4. Click OK to delete the selected task(s).
The selected task(s) are deleted from the table.
Generating a scheduled task report
Use this procedure to generate a scheduled task report.
1. Select Status & Manage > Tasks > Scheduled Tasks.
The Scheduled Tasks page appears, and all scheduled tasks are displayed.
2. Select one or more tasks.
Note: If no tasks are selected, all tasks matching the current filter criteria will be included in the
report.
3. Click Report.
The Scheduled Tasks Report page appears.
4. Click Print to print the report.
5. Click Save to save the report.
910-6528-001 Revision D, December 2012
44
Chapter
3
Alarms and Events
Topics:
•
•
•
•
•
•
•
•
•
•
•
General alarms information.....46
IP Front End, IPFE (5000-5999).....55
OAM (10000-10999).....60
Session Binding Repository, SBR
(12000-12999).....70
Communication Agent, ComAgent
(19800-19909).....71
Diameter Signaling Router (DSR) Diagnostics
(19910-19999).....94
Diameter Signaling Router, DSR
(22000-22999).....95
Tekelec Virtual Operating Environment, TVOE
(24400-24499).....142
Computer Aided Policy Making, CAPM
(25000-25499).....143
OAM Alarm Management (25500-25899).....145
Platform (31000-32700).....146
910-6528-001 Revision D, December 2012
This section provides general alarm/event
information, and lists the types of alarms and events
that can occur on the system. Alarms and events are
recorded in a database log table. Currently active
alarms can be viewed from the Launch Alarms
Dashboard GUI menu option. The alarms and events
log can be viewed from the View History GUI menu
option.
Note: Some of the alarms in this document are
shared with other applications and may not appear
in this particular product.
45
Alarms and Events
General alarms information
This section provides general information about alarms and events, including an alarms overview,
types of alarms/events, and alarms-related procedures.
Alarms and events overview
Alarms provide information pertaining to a system's operational condition that a network manager
may need to act upon. An alarm might represent a change in an external condition, for example, a
communications link has changed from connected to disconnected state. Alarms can have these
severities:
•
•
•
•
Critical application error
Major application error
Minor application error
Cleared. An alarm is considered inactive once it has been cleared, and cleared alarms are logged
on the Alarms & Events > View History page of the GUI.
Events note the occurrence of an expected condition. Events have a severity of Info and are logged on
the View History page.
The following figure shows how Alarms and Events are organized in the application.
Figure 1: Flow of Alarms
Alarms and events are recorded in a database log table. Application event logging provides an efficient
way to record event instance information in a manageable form, and is used to:
• Record events that represent alarmed conditions
• Record events for later browsing
• Implement an event interface for generating SNMP traps
910-6528-001 Revision D, December 2012
46
Alarms and Events
Alarm indicators, located in the User Interface banner, indicate all critical, major, and minor active
alarms. A number and an alarm indicator combined represent the number of active alarms at a specific
level of severity. For example, if you see the number six in the orange-colored alarm indicator, that
means there are six major active alarms.
Figure 2: Alarm Indicators Legend
Figure 3: Trap Count Indicator Legend
Alarm and event ID ranges
The AlarmID listed for each alarm falls into one of the following process classifications:
Table 6: Alarm/Event ID Ranges
Application/Process Name
Alarm ID Range
IPFE
5000-5099
OAM
10000-10999
SSR
11000-12999
HLR Router
14000-14999
Service Broker
17000-17999
ComAgent
19800-19899
DSR Diagnostics
19900-19999
DSR
22000-22999
CAPM
25000-25899
Platform
31000-32700
910-6528-001 Revision D, December 2012
47
Alarms and Events
Alarm and event types
This table describes the possible alarm/event types that can be displayed.
Note: Not all Tekelec applications use all of the alarm types listed.
Table 7: Alarm and Event Types
Type Name
Type
CAF
Communication Agent (ComAgent)
CAPM
Computer-Aided Policy Making (Diameter
Mediation)
CFG
Configuration
CHG
Charging
CNG
Congestion Control
COLL
Collection
CPA
Charging Proxy Application
DAS
Diameter Application Server (Message Copy)
DB
Database
DIAM
Diameter
DISK
Disk
DNS
Domain Name Service
DPS
Data Processor Server
ERA
Event Responder Application
FABR
Full Address Based Resolution
HA
High Availability
HSS
Home Subscriber Server
IF
Interface
IP
Internet Protocol
IPFE
IP Front End
LOG
Logging
MEAS
Measurements
MEM
Memory
NP
Number Portability
OAM
Operations, Administration & Maintenance
PLAT
Platform
910-6528-001 Revision D, December 2012
48
Alarms and Events
Type Name
Type
PROC
Process
PROV
Provisioning
NAT
Network Address Translation
RBAR
Range-Based Address Resolution
REPL
Replication
SCTP
Stream Control Transmission Protocol
SIGC
Signaling Compression
SIP
Session Initiation Protocol Interface
SL
Selective Logging
SS7
Signaling System 7
SSR
SIP Signaling Router
STK
EXG Stack
SW
Software (generic event type)
TCP
Transmission Control Protocol
Viewing active alarms
Active alarms are displayed in a scrollable, optionally filterable table. By default, the active alarms
are sorted by time stamp with the most recent alarm at the top.
Use this procedure to view active alarms.
Note: The alarms and events that appear in View Active vary depending on whether you are logged
in to an NOAMP or SOAM. Alarm collection is handled solely by NOAMP servers in systems that do
not support SOAMs.
1. Select Alarms & Events > View Active.
The View Active page appears.
2. If necessary, specify filter criteria and click Go.
The active alarms are displayed according to the specified criteria.
The active alarms table updates automatically. When new alarms are generated, the table is
automatically updated, and the view returns to the top row of the table.
3. To suspend automatic updates, click any row in the table.
The following message appears: (Alarm updates are suspended.)
If a new alarm is generated while automatic updates are suspended, a new message appears: (Alarm
updates are suspended. Available updates pending.)
To resume automatic updates, press and hold Ctrl as you click to deselect the selected row.
910-6528-001 Revision D, December 2012
49
Alarms and Events
Active alarms data export elements
This table describes the elements on the View Active Export alarms page.
Table 8: Schedule Active Alarm Data Export Elements
Element
Task Name
Description
Name of the scheduled task
Data Input Notes
Format: Textbox
Range: Maximum length is 24
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Task Name must begin and end
with an alphanumeric character.
Description
Description of the scheduled task
Format: Textbox
Range: Maximum length is 255
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Description must begin with an
alphanumeric character.
Export Frequency
Frequency at which the export
occurs
Format: Radio button
Range: Once, Weekly, or Daily
Default: Once
Time of Day
Time of day the export occurs
Format: Time textbox
Range: 15-minute increments
Default: 12:00 AM
Day of Week
Day of week on which the export
Format: Radio button
occurs
Range: Sunday, Monday,
Tuesday, Wednesday, Thursday,
Friday, or Saturday
Default: Sunday
Exporting active alarms
You can schedule periodic exports of alarm data from the Alarms and Events View Active page.
Active alarm data can be exported immediately, or you can schedule exports to occur daily or weekly.
If filtering has been applied in the View Active page, only filtered data is exported.
During data export, the system automatically creates a CSV file of the filtered data. The file will be
available in the file management area until you manually delete it, or until the file is transfered to an
910-6528-001 Revision D, December 2012
50
Alarms and Events
alternate location using the Export Server feature. For more information about using Export Server,
see Export Server.
Alarm details can be exported to a file by clicking the Export button on the View Active page. The
system automatically creates and writes the exported active alarm details to a CSV file in the file
management area.
If filtering has been applied in the View Active page, only filtered, active alarms are exported.
Use this procedure to export active alarms to a file. Use this procedure to schedule a data export task.
1. Select Alarms & Events > View Active.
The View Active page appears.
2. If necessary, specify filter criteria and click Go.
The active alarms are displayed according to the specified criteria.
3. Click Export.
The Schedule Active Alarm Data Export page appears.
4. Enter the Task Name.
For more information about Task Name, or any field on this page, see Active alarms data export
elements .
5. Select the Export Frequency.
6. Select the Time of Day.
Note: Time of Day is not an option if Export Frequency equals Once.
7. Select the Day of Week.
Note: Day of Week is not an option if Export Frequency equals Once.
8. Click OK or Apply to initiate the active alarms export task.
From the Status & Manage > Files page, you can view a list of files available for download, including
the file you exported during this procedure. For more information, see Displaying the file list.
Scheduled tasks can be viewed, edited, and deleted, and reports of scheduled tasks can be generated
from Status & Manage > Tasks. For more information see:
•
•
•
•
Viewing scheduled tasks
Editing a scheduled task
Deleting a scheduled task
Generating a scheduled task report
9. Click Export.
The file is exported.
10. Click the link in the green message box to go directly to the Status & Manage > Files page.
From the Status & Manage > Files page, you can view a list of files available for download, including
the active alarms file you exported during this procedure.
910-6528-001 Revision D, December 2012
51
Alarms and Events
Generating a report of active alarms
Use this procedure to generate a report.
1. Select Alarms & Events > View Active.
The View Active page appears.
2. Specify filter criteria, if necessary, and click Go.
The active alarms are displayed according to the specified criteria. Alternately, you can select
multiple rows and generate a report using those. To select multiple rows, press and hold Ctrl as
you click to select specific rows.
3. Click Report.
The View Active Report is generated. This report can be printed or saved to a file.
4. Click Print to print the report.
5. Click Save to save the report to a file.
Viewing alarm and event history
All historical alarms and events are displayed in a scrollable, optionally filterable table. The historical
alarms and events are sorted, by default, by time stamp with the most recent one at the top. Use this
procedure to view alarm and event history.
Note: The alarms and events that appear in View History vary depending on whether you are logged
in to an NOAMP or SOAM. Alarm collection is handled solely by NOAMP servers in systems that do
not support SOAMs.
1. Select Alarms & Events > View History .
The View History page appears.
2. If necessary, specify filter criteria and click Go.
Note: Some fields, such as Additional Info, truncate data to a limited number of characters. When
this happens, a More link appears. Click More to view a report that displays all relevant data.
Historical alarms and events are displayed according to the specified criteria.
The historical alarms table updates automatically. When new historial data is available, the table
is automatically updated, and the view returns to the top row of the table.
3. To suspend automatic updates, click any row in the table.
The following message appears: (Alarm updates are suspended.)
If a new alarm is generated while automatic updates are suspended, a new message appears: (Alarm
updates are suspended. Available updates pending.)
To resume automatic updates, press and hold Ctrl as you click to deselect the selected row.
Historical events data export elements
This table describes the elements on the View History Export page.
910-6528-001 Revision D, December 2012
52
Alarms and Events
Table 9: Schedule Event Data Export Elements
Element
Task Name
Description
Name of the scheduled task
Data Input Notes
Format: Textbox
Range: Maximum length is 24
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Task Name must begin and end
with an alphanumeric character.
Description
Description of the scheduled task
Format: Textbox
Range: Maximum length is 255
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Description must begin with an
alphanumeric character.
Export Frequency
Frequency at which the export
occurs
Format: Radio button
Range: Hourly, Once, Weekly,
or Daily
Default: Once
Minute
If hourly is selected for Upload
Format: Scrolling list
Frequency, this is the minute of
each hour when the data will be Range: 0 to 59
written to the export directory.
Time of Day
Time of day the export occurs
Format: Time textbox
Range: 15-minute increments
Default: 12:00 AM
Day of Week
Day of week on which the export
Format: Radio button
occurs
Range: Sunday, Monday,
Tuesday, Wednesday, Thursday,
Friday, or Saturday
Default: Sunday
Exporting alarm and event history
You can schedule periodic exports of historical data from the Alarms and Events View History page.
Historical data can be exported immediately, or you can schedule exports to occur daily or weekly. If
filtering has been applied in the View History page, only filtered data is exported.
910-6528-001 Revision D, December 2012
53
Alarms and Events
During data export, the system automatically creates a CSV file of the filtered data. The file will be
available in the file management area until you manually delete it, or until the file is transfered to an
alternate location using the Export Server feature. For more information about using Export Server,
see Export Server.
The details of historical alarms and events can be exported to a file by clicking the Export button on
the View History page. The system automatically creates and writes the exported historical alarm
details to a CSV file in the file management area.
If filtering has been applied in the View History page, only filtered historical alarms and events are
exported. Use this procedure to export alarm and event history to a file. Use this procedure to schedule
a data export task.
1. Select Alarms & Events > View History.
The View History page appears.
2. If necessary, specify filter criteria and click Go.
The historical alarms and events are displayed according to the specified criteria.
3. Click Export.
The Schedule Event Data Export page appears.
4. Enter the Task Name.
For more information about Task Name, or any field on this page, see Historical events data export
elements .
5. Select the Export Frequency.
6. If you selected Hourly, specify the Minutes.
7. Select the Time of Day.
Note: Time of Day is not an option if Export Frequency equals Once.
8. Select the Day of Week.
Note: Day of Week is not an option if Export Frequency equals Once.
9. Click OK or Apply to initiate the data export task.
The data export task is scheduled. From the Status & Manage > Files page, you can view a list of
files available for download, including the alarm history file you exported during this procedure.
For more information, see Displaying the file list.
Scheduled tasks can be viewed, edited, and deleted, and reports of scheduled tasks can be generated
from Status & Manage > Tasks. For more information see:
•
•
•
•
Viewing scheduled tasks
Editing a scheduled task
Deleting a scheduled task
Generating a scheduled task report
10. Click Export.
The file is exported.
11. Click the link in the green message box to go directly to the Status & Manage > Files page.
910-6528-001 Revision D, December 2012
54
Alarms and Events
From the Status & Manage > Files page, you can view a list of files available for download, including
the alarm history file you exported during this procedure. For more information, see .
Generating a report of historical alarms and events
Use this procedure to generate a report.
1. Select Alarms & Events > View History.
The View History page appears.
2. Specify filter criteria, if necessary, and click Go.
The historical alarms and events are displayed according to the specified criteria.
3. Click Report.
The View History Report is generated. This report can be printed or saved to a file.
4. Click Print to print the report.
5. Click Save to save the report to a file.
IP Front End, IPFE (5000-5999)
This section provides information and recovery procedures for IP Front End (IPFE) alarms, which
range from 5000 to 5999.
5001 - IPFE Backend Unavailable
Alarm Type: IPFE
Description: The IPFE has not received any heartbeats from an application server within the heartbeat
timeout interval.
Severity: Minor
Instance: IP address of the application server
HA Score: Degraded
Auto Clear Seconds: N/A
OID: ipfeBackendUnavailable
Recovery: If a heartbeat is received from the application server, this alarm will clear.
1. Check the status of the application servers by navigating to the Status & Manage > Server page.
2. Consult the application server's documentation for recovery steps.
5002 - IPFE address configuration error
Alarm Type: IPFE
Description: The IPFE is unable to synchronize state data with its peer. This alarm can be issued for
multiple reasons, including missing or invalid configurations, inability to bind a socket to the given
910-6528-001 Revision D, December 2012
55
Alarms and Events
IP address, or incompatible versions of software. The instance column provides more details when
this alarm is raised. This alarm is present when the IPFE is activated but not yet configured.
Severity: Critical
Instance: One of the following strings:
•
•
•
•
•
•
•
•
"ipfe1 and ipfe2 address both empty" - incomplete configuration
"ipfe1 and ipfe2 address identical" - one of the addresses is incorrect
"IPs are both local" - the two addresses correspond to the same interface on the blade
"ipfe1 bad address" - invalid address format
"ipfe2 bad address" - invalid address format
"bind error" - cannot bind a socket to this interface address
"cannot open ipfe device /dev/recent" - xt_recent module in TPD is either missing or incorrect
"peer software version incompatible" - peer IPFE is on a different version
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeStateSyncConfigError
Recovery: If the IPFE is able to successfully synchronize data with its peer, this alarm will clear.
1. To correct configuration errors, select IPFE > Configuration > Options from the left-hand menu.
The Configuration Options pane appears.
2. Ensure that IPFE1 IP Address and IPFE2 IP Address are configured correctly.
3. For issues with modules or versions, contact the Tekelec Customer Care Center for assistance.
5003 - IPFE state sync run error
Alarm Type: IPFE
Description: The IPFE was unable to synchronize state data with its mate.
Severity: Critical
Instance: One of the following strings:
• "connect error" - cannot connect to peer IPFE
• "data read error" - error reading data from peer IPFE
• "data write error" - error writing data to peer IPFE
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeStateSyncRunError
Recovery: If the IPFE is able to synchronize state data with its mate, this alarm will clear.
1. Check the status of the peer IPFE by navigating to the Status & Manage > Server page.
2. Diagnose any network fault between the two IPFEs.
3. For further assistance, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
56
Alarms and Events
5004 - IPFE IP tables configuration error
Alarm Type: IPFE
Description: A target set address is configured with no IP addresses, or with invalid IP addresses. This
alarm can be triggered during configuration of the IPFE when the target set address has been configured,
but application servers have not yet been added to the target set.
Severity: Critical
Instance: "tsa N address misconfiguration" where N is 1-16
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeIpTablesConfigError
Recovery: When the target set address is configured correctly, this alarm will clear.
1. Select IPFE > Configuration > Options from the left-hand menu.
The Configuration Options pane appears.
2. Ensure that the TSA1 IP Address field contains a valid IP address.
3. Select IPFE > Configuration > IP List TSA 1.
The IP List TSA 1 pane appears.
4. Ensure that there is at least one application server IP address configured for the TSA.
5. Repeat for IPFE > Configuration > IP List TSA 1.
5005 - IPFE Backend In Stasis
Alarm Type: IPFE
Description: The IPFE has received a heartbeat packet from the application server that indicates that
the application server is unwilling to accept new connections. However, the application server will
continue to process existing connections.
Severity: Minor
Instance: IP address of the application server in stasis
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeBackendInStasis
Recovery: When the IPFE receives heartbeats from the application server indicating that it is willing
to accept new connections, this alarm will clear.
5006 - Error reading from Ethernet device. Restart IPFE process.
Alarm Type: IPFE
Description: The IPFE was unable to read from an ethernet device.
Severity: Critical
910-6528-001 Revision D, December 2012
57
Alarms and Events
Instance: "pcap <ethernet device name>"
HA Score: Degraded
Auto Clear Seconds: N/A
OID: ipfeEtherDeviceReadError
Recovery: If the IPFE is able to read from the ethernet device, this alarm will clear.
1. Select Status & Manage > Server.
The Server Status page appears.
2. Click to select the IPFE to restart.
3. Click Restart.
A warning message appears:
Are you sure you want to restart application software on the following server(s)? <server name>
4. Click OK to continue.
5007 - Out of Balance: Low
Alarm Type: IPFE
Description: Traffic statistics reveal that an application server is processing higher than average load.
For example, if a TSA has three application servers, but the IPFE has only two connections open, then
one of the application servers will receive no traffic and thus will be considered "underloaded".
Severity: Minor
Instance: IP address of the application server
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeBackendUnderloaded
Recovery: None required. Underloaded application servers do not impact traffic processing. This
alarm will clear when traffic statistics reveal that the application server is no longer underloaded.
5008 - Out of Balance: High
Alarm Type: IPFE
Description: Traffic statistics reveal that an application server is processing higher than average load
and will not receive new connections.
Severity: Minor
Instance: IP address of the overloaded application server
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeBackendOverloaded
910-6528-001 Revision D, December 2012
58
Alarms and Events
Recovery: When traffic statistics indicate that the application server is no longer overloaded, this alarm
will clear.
1. The IPFE will monitor traffic statistics and will not assign connections to the overloaded application
server until statistics indicate that the server is no longer overloaded.
2. Check the status of the application servers by navigating to the Status & Manage > Server page.
3. Consult the application server's documentation for recovery steps.
5009 - No available servers in target set
Alarm Type: IPFE
Description: Through monitoring of the application servers, the IPFE learns that no server in a target
set is available. The associated measurement, TxReject, will also show counts. This alarm can be
triggered during configuration of the IPFE when the target set address has been configured, but
application servers have not yet been added to the target set.
Severity: Critical
Instance: "tsa N has no available servers" where N is 1-16
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeNoAvailableAppServers
Recovery: When at least one application server in a target set becomes available, this alarm will clear.
1. Ensure that application servers have been configured for the target set address by viewing IPFE >
Configuration > IP List TSA N.
2. Check the status of the application servers by navigating to the Status & Manage > Server page.
3. Consult the application server's documentation for recovery steps.
5010 - Unknown Linux iptables command error
Alarm Type: IPFE
Description: The IPFE received an unknown error parsing Linux iptables output. This is an internal
software error.
Severity: Critical
Instance: "error parsing iptables output"
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeErrorParsingIptablesOutput
Recovery:
Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
59
Alarms and Events
5011 - System or platform error prohibiting operation
Alarm Type: IPFE
Description: The IPFE is unable to use its ethernet interfaces.
Severity: Critical
Instance: "error opening ethernet listeners"
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeSystemError
Recovery: If the IPFE is able to use its ethernet interfaces, this alarm will clear.
Contact the Tekelec Customer Care Center for assistance.
5100 - Traffic overload
Alarm Type: IPFE
Description: Total IPFE signaling traffic rate is approaching or exceeding its engineered capacity. The
severity thresholds are the following:
• Minor: set at 1.92 Gb/second, clear at 1.72 Gb/second
• Major: set at 2.56 Gb/second, clear at 2.36 Gb/second
• Criticalset at 3.20 Gb/second, clear at 3.00 Gb/second
Severity: Minor, Major, Critical
Instance: N/A
HA Score: Normal
Auto Clear Seconds: N/A
OID: ipfeTrafficOverload
Recovery: If the signaling traffic declines below the clear threshold, the alarm will clear.
The product is in excess of its design parameters, and may exhibit traffic loss if an additional failure
occurs. Consider expanding system to accommodate additional capacity. Contact the Tekelec
Customer Care Center for assistance.
OAM (10000-10999)
This section provides information and recovery procedures for OAM alarms, ranging from 10000-10999.
Alarms formatting information
This section of the document provides information to help you understand why an alarm occurred
and to provide a recovery procedure to help correct the condition that caused the alarm.
910-6528-001 Revision D, December 2012
60
Alarms and Events
The information provided about each alarm includes:
•
•
•
•
Alarm Type: the type of alarm that has occurred. For a list of alarm types see Alarm and event types.
Description: describes the reason for the alarm
Severity: the severity of the alarm
Instance: where the alarm occurred, for example, GUI, <process name>, IP address, <server name>
Note: The value in the Instance field can vary, depending on the process generating the alarm.
•
•
•
•
HA Score: high availability score; determines if switchover is necessary
Auto Clear Seconds: the number of seconds that have the pass before the alarm will clear itself
OID: alarm identifier that appears in SNMP traps
Recovery: provides any necessary steps for correcting or preventing the alarm
10000 - Incompatible database version
Alarm Type: DB
Description: The database version is incompatible with the installed software database version.
Severity: Critical
Instance: N/A
HA Score: Failed
Auto Clear Seconds: 300
OID: tekelecIncompatibleDatabaseVersionNotify
Recovery: Contact the Tekelec Customer Care Center.
10001 - Database backup started
Alarm Type: DB
Description: The database backup has started.
Severity: Info
Instance: GUI
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecBackupStartNotify
Recovery: No action required.
10002 - Database backup completed
Alarm Type: DB
Description: Backup completed
Severity: Info
Instance: GUI
910-6528-001 Revision D, December 2012
61
Alarms and Events
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecBackupCompleteNotify
Recovery:
No action required.
10003 - Database backup failed
Alarm Type: DB
Description: The database backup has failed.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear
OID: tekelecBackupFailNotify
Recovery:
Contact the Tekelec Customer Care Center.
10004 - Database restoration started
Alarm Type: DB
Description: The database restoration has started.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecRestoreStartNotify
Recovery:
No action required.
10005 - Database restoration completed
Alarm Type: DB
Description: The database restoration is completed.
Severity: Info
Instance: N/A
HA Score: Normal
910-6528-001 Revision D, December 2012
62
Alarms and Events
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecRestoreCompleteNotify
Recovery:
No action required.
10006 - Database restoration failed
Alarm Type: DB
Description: The database restoration has failed.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecRestoreFailNotify
Recovery:
Contact the Tekelec Customer Care Center.
10008 - Database provisioning manually disabled
Alarm Type: DB
Description: Database provisioning has been manually disabled.
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecProvisioningManuallyDisabled
Recovery:
No action required.
10009 - Config and Prov db not yet synchronized
Alarm Type: REPL
Description: The configuration and the provisioning databases are not yet synchronized.
Severity: Critical
Instance: N/A
HA Score: Failed
Auto Clear Seconds: This alarm does not autoclear.
910-6528-001 Revision D, December 2012
63
Alarms and Events
OID: oAGTCfgProvDbNoSync
Recovery:
1. Monitor the replication status using the Status & Manage > Replication GUI page.
2. If alarm persists for more than one hour, contact Tekelec Customer Care Center.
10010 - Stateful db from mate not yet synchronized
Alarm Type: HA
Description: The stateful database is not synchronized with the mate database.
Severity: Minor
Instance: N/A
HA Score: Degraded
Auto Clear Seconds: This alarm does not autoclear.
OID: oAGTStDbNoSync
Recovery:
If alarm persists for more than 30 seconds, contact the Tekelec Customer Care Center.
10011 - Cannot monitor table
Alarm Type: OAM
Description: Monitoring for table cannot be set up.
Severity: Major
Instance: N/A
HA Score: Degraded
Auto Clear Seconds: This alarm does not autoclear.
OID: oAGTCantMonitorTable
Recovery:
Contact the Tekelec Customer Care Center.
10012 - Table change responder failed
Alarm Type: OAM
Description: The responder for a monitored table failed to respond to a table change.
Severity: Major
Instance: N/A
HA Score: Degraded
Auto Clear Seconds: This alarm does not autoclear.
910-6528-001 Revision D, December 2012
64
Alarms and Events
OID: oAGTResponderFailed
Recovery:
Contact the Tekelec Customer Care Center.
10013 - Application restart in progress
Alarm Type: HA
Description: An application restart is in progress.
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: oAGTApplSWDisabled
Recovery:
If duration of alarm is greater than two seconds, contact the Tekelec Customer Care Center.
10020 - Backup failure
Alarm Type: DB
Description: Database backup failed.
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: apwBackupFailure
Recovery:
Alarm will clear if a backup (Automated or Manual) of the same group data is successful. Contact
the Tekelec Customer Care Center if failures persist.
10074 - Standby server degraded while mate server stabilizes
Alarm Type: HA
Description: The standby server has temporarily degraded while the new active server stabilizes
following a switch of activity.
Severity: Minor
Instance: N/A
HA Score: Degraded
910-6528-001 Revision D, December 2012
65
Alarms and Events
Auto Clear Seconds: This alarm does not autoclear.
OID: hASbyRecoveryInProgress
Recovery:
No action required; the alarm clears automatically when standby server is recovered. This is part
of the normal recovery process for the server that transitioned to standby as a result of a failover.
10075 - Application processes have been manually stopped
Alarm Type: HA
Description: The server is no longer providing services because application processes have been
manually stopped.
Severity: Minor
Instance: N/A
HA Score: Failed
Auto Clear Seconds: This alarm does not autoclear.
OID: haMtceStopApplications
Recovery:
If maintenance actions are complete, restart application processes on the server from the Status &
Manage>Servers page by selecting the Restart Applications action for the server that raised the
alarm.
Once successfully restarted the alarm will clear.
10078 - Application not restarted on standby server due to disabled failure cleanup
mode
Alarm Type: HA
Description: The Applications on the Standby server have not been restarted after an active-to- standby
transition since h_FailureCleanupMode is set to 0.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: failureRecoveryWithoutAppRestart
Recovery:
Contact the Tekelec Customer Care Center.
10100 - Log export started
Alarm Type: LOG
910-6528-001 Revision D, December 2012
66
Alarms and Events
Description: Log files export operation has started.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLogExportStart
Recovery:
No action required.
10101 - Log export successful
Alarm Type: LOG
Description: The log files export operation completed successfully.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLogExportSuccess
Recovery:
No action required.
10102 - Log export failed
Alarm Type: LOG
Description: The log files export operation failed.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLogExportFailed
Recovery:
Contact the Tekelec Customer Care Center.
10103 - Log export already in progress
Alarm Type: LOG
Description: The log files export operation was not started because another export is already in progress.
910-6528-001 Revision D, December 2012
67
Alarms and Events
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLogExportNotStarted
Recovery:
Restart export operation after existing export completes.
10151 - Login successful
Alarm Type: LOG
Description: The login operation was successful.
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLoginSuccess
Recovery:
No action required.
10152 - Login failed
Alarm Type: LOG
Description: The login operation failed
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLoginFailed
Recovery:
Verify login information and case is correct, and re-enter.
10153 - Logout successful
Alarm Type: LOG
Description: The logout operation was successful.
Severity: Info
910-6528-001 Revision D, December 2012
68
Alarms and Events
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: tekelecLogoutSuccess
Recovery:
No action required.
10154 - User Account Disabled
Alarm Type: LOG
Description: User account has been disabled
Severity: Info
Instance: N/A
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: userAccountDisabled
Recovery:
The alarm will clear if the account is automatically re-enabled. Otherwise, the administrator must
enable or delete user account.
10200 - Remote database reinitialization in progress
Alarm Type: CFG
Description: The remote database reinitialization is in progress. This alarm is raised on the active
NOAMP server for the server being added to the server group.
Severity: Minor
Instance: <hostname of remote server>
HA Score: Normal
Auto Clear Seconds: This alarm does not autoclear.
OID: apwSgDbReinit
Recovery:
1.
2.
3.
4.
Check to see that the remote server is configured.
Make sure the remote server is responding to network connections.
If this does not clear the alarm, delete this server from the server group.
If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
69
Alarms and Events
Session Binding Repository, SBR (12000-12999)
This section provides information and recovery procedures for SBR alarms, which range from 12000
to 12999.
12003 - SBR Congestion State
Alarm Type: SBRA
Description: The SBR application is in a congested state and is shedding operations. The measurement
Sbr.RxIngressMsgQueueAvg shows the average percentage of queue length utilization, which is used
to determine congestion. The severity thresholds are the following:
Table 10: Congestion Thresholds
Severity
Set Threshold
Clear Threshold
Shed Operations
Associated
Measurements
Minor
60%
50%
Creates
Sbr.TxShedCreates
Major
80%
70%
Creates, Writes
Sbr.TxShedCreates,
Sbr.TxShedWrites
Critical
95%
90%
Creates, Writes,
Reads
Sbr.TxShedCreates,
Sbr.TxShedWrites,
Sbr.TxShedReads
Severity: Minor, Major, Critical
Instance: Sbr.RxIngressMsgQueueMetric[subId], SBR
HA Score: Normal
Auto Clear Seconds: N/A
OID: SbrCongestionState
Recovery: If congestion falls below the clear threshold, this alarm will clear.
The SBR congestion status exceeds the alarm threshold. Additional capacity may be required to
service the traffic load. Contact the Tekelec Customer Care Center for assistance.
12007 - SBR Active Sess Binding Threshold
Alarm Type: SBRA
Description: The SBR application has exceeded its Active Session Binding threshold. The configuration,
Maximum active session bindings, is used to calculate the percentage. The severity thresholds are the
following:
• Minor: set at 70%, clear at 60%
• Major: set at 80%, clear at 70%
• Critical: set at 100%, clear at 90%
910-6528-001 Revision D, December 2012
70
Alarms and Events
Severity: Minor, Major, Critical
Instance: Sbr.EvCurrentSessionMetric, SBR
HA Score: Normal
Auto Clear Seconds: N/A
OID: SbrActiveSessBindThreshold
Recovery: If total active session bindings fall below the clear threshold, this alarm will clear.
1. Select CPA > Configuration > SBR.
The CPA -> Configuration -> SBR page appears.
2. Increase the Maximum active session bindings configuration if it is too low.
3. Click Apply to apply your changes.
Your changes will go into affect immediately.
4. The SBR active session bindings count exceeds the threshold. Additional capacity may be required
to service the traffic load. Contact the Tekelec Customer Care Center for assistance.
12010 - SBR Proc Term
Alarm Type: SBRA
Description: The SBR application has terminated.
Severity: Critical
Instance: sbr
HA Score: Degraded
Auto Clear Seconds: 10
OID: SbrProcTerm
Recovery: When an active SBR is terminated as indicated by this alarm, its standby becomes active.
The Process Manager will automatically attempt to restart the terminated process. If the Process
Manager fails to start the terminated process, it will raise the alarm again. The standby that became
active will remain active until it is placed into standby mode again.
1. Check the status of the terminated SBR by navigating to the Status & Manage > Server page.
2. If the Process Manager cannot restart the process, contact the Tekelec Customer Care Center for
assistance.
Communication Agent, ComAgent (19800-19909)
This section provides information and recovery procedures for Communication Agent (ComAgent)
alarms and events, ranging from 19800 - 19909, and lists the types of alarms and events that can occur
on the system. All events have a severity of Info.
910-6528-001 Revision D, December 2012
71
Alarms and Events
Alarms and events are recorded in a database log table. Currently active alarms can be viewed from
the Launch Alarms Dashboard GUI menu option. The alarms and events log can be viewed from the
Alarms & Events > View History page.
19800 - Communication Agent Connection Down
Alarm Type: CAF
Description: This alarm indicates that a Communication Agent is unable to establish transport
connections with one or more other servers, and this may indicate that applications on the local server
are unable to communicate with all of their peers. Generally this alarm is asserted when a server or
the IP network is undergoing maintenance or when a connection has been manually disabled.
Severity: Major
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFConnectionDownNotify
Recovery:
1. Use Main MenuAlarms & EventsView History to find additional information about the alarm.
The information can be found by locating the row with a sequence number that matches the active
alarm sequence number and viewing the Additional Info column.
2. Check the event history logs at Main MenuAlarms & EventsView History for additional
Communication Agent events or alarms from this MP server.
3. Use Main MenuCommunication AgentMaintenanceConnection Status to determine which
connections on the server have abnormal status.
4. If the connection is manually disabled, then no further action is necessary.
5. Verify that the remote server is not under maintenance.
6. Verify that IP network connectivity exists between the two connection end-points.
7. Verify that the connection’s local IP address and port number are configured on remote Node.
8. Verify that the Application Process using Communication Agent plug-in is running on both ends.
9. Verify that the connection’s remote IP address and port correctly identify remote’s listening port.
10. Contact the Tekelec Customer Care Center for assistance.
19801 - Communication Agent Connection Locally Blocked
Alarm Type: CAF
Description: This alarm indicates that one or more Communication Agent connections have been
administratively blocked at the server asserting the alarm, and this is generally done as part of a
maintenance procedure. A connection that is blocked cannot be used by applications to communicate
with other servers, and so this alarm may indicate that applications are unable to communicate with
their expected set of peers.
Note: It is normal to have this alarm if the connection is in the Blocked administrative state on the
near-side of the connection.
910-6528-001 Revision D, December 2012
72
Alarms and Events
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFConnLocalBlockedNotify
Recovery:
This alarm is cleared when:
• Locally UNBLOCKed: An Admin Action to locally UNBLOCK the service connection and no other
connection is locally blocked.
• Deleted: The MP Server/Connection is deleted.
• Failed: The Connection is terminated, due to Admin Disable action or Heartbeat failure or remote
end initiated disconnection or any other reason.
1. Use Main MenuAlarms & EventsView History to find additional information about the alarm.
The information can be found by locating the row with a sequence number that matches the active
alarm sequence number and viewing the Additional Info column.
2. Check the event history logs at Main MenuAlarms & EventsView History for additional
Communication Agent events or alarms from this MP server.
3. Use Main MenuCommunication AgentMaintenanceConnection Status to determine which
connections on the server have abnormal status.
4. If the expected set of connections is locally blocked, then no further action is necessary.
5. To remove a the local block condition for a connection, use the Main Menu Communication
AgentMaintenanceConnection Status screen and click the 'Enable' action button for the desired
connection.
6. Contact the Tekelec Customer Care Center for assistance.
19802 - Communication Agent Connection Remotely Blocked
Alarm Type: CAF
Description: This alarm indicates that one or more Communication Agent connections have been
administratively blocked at a remote server connected to the server, and this is generally done as part
of a maintenance procedure. A connection that is blocked cannot be used by applications to
communicate with other servers, and so this alarm may indicate that applications are unable to
communicate with their expected set of peers.
Note: It is normal to have this alarm if the connection is in the Blocked administrative state on the
far-side of the connection.
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFConnRemoteBlockedNotify
910-6528-001 Revision D, December 2012
73
Alarms and Events
Recovery:
This alarm is cleared when:
• Locally UNBLOCKed: An Admin Action to locally UNBLOCK the service connection and no other
connection is locally blocked.
• Deleted: The MP Server/Connection is deleted.
• Failed: The Connection is terminated, due to Admin Disable action or Heartbeat failure or remote
end initiated disconnection or any other reason.
1. Use Main MenuAlarms & EventsView History to find additional information about the alarm.
The information can be found by locating the row with a sequence number that matches the active
alarm sequence number and viewing the Additional Info column.
2. Check the event history logs at Main MenuAlarms & EventsView History for additional
Communication Agent events or alarms from this MP server.
3. Use Main MenuCommunication AgentMaintenanceConnection Status to determine which
connections on the server have abnormal status.
4. If the expected set of connections is locally blocked, then no further action is necessary.
5. To remove a the local block condition for a connection, use the Main Menu Communication
AgentMaintenanceConnection Status screen and click the 'Enable' action button for the desired
connection.
6. Contact the Tekelec Customer Care Center for assistance.
19803 - Communication Agent stack event queue utilization
Alarm Type: CAF
Description: The percent utilization of the Communication Agent Task stack queue is approaching
defined threshold capacity. If this problem persists and the queue reaches above the defined threshold
utilization, the new StackEvents (Query/Response/Relay) messages for the Task can be discarded,
based on the StackEvent priority and Application's Global Congestion Threshold Enforcement Mode.
Severity: Minor, Major, Critical
Instance: <ComAgent StackTask Name>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFQueueUtilNotify
Recovery:
1. Use Main MenuAlarms & Events to examine the alarm log.
An IP network or Adjacent node problem may exist preventing from transmitting messages into
the network at the same pace that messages are being received from the network. The Task thread
may be experiencing a problem preventing it from processing events from its event queue. Contact
the Tekelec Customer Care Center for assistance.
2. Use Main MenuStatus & Control KPI Display to monitor the ingress traffic rate of each MP.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
910-6528-001 Revision D, December 2012
74
Alarms and Events
Contact the Tekelec Customer Care Center for assistance.
3. If the MP ingres rate is approximately the same, there may be an insufficient number of MPs
configured to handle the network traffic load.
If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
Contact the Tekelec Customer Care Center for assistance.
19804 - Communication Agent configured connection waiting for remote client to
establish connection
Alarm Type: CAF
Description: Communication Agent configured connection waiting for remote client to establish
connection. This alarm indicates that a Communication Agent is waiting for one or more far-end client
MPs to initiate transport connections. Generally this alarm is asserted when a client MP or the IP
network is undergoing maintenance or when a connection has been manually disabled at a client MP.
Note: It is normal to have this auto-clearing connection alarm for the remote server connections that
configured manually in "Client" mode, but are not yet available for processing traffic.
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 300 (5 min)
OID: CAFClientConnWaitNotify
Recovery:
The alarm is cleared when a "server" connection exits the "forming" state and no other connection
having "server" connect mode is in the "forming" state or the auto-clear time-out occurs.
•
•
•
•
The MP Server/Connection is deleted
When connection is moved to TotallyBlocked/RemotelyBlocked/InService state from Aligning
Auto Clear
Connection is disabled
The alarm is cleared only for remote server connections that are configured manually in “Client”
mode. This mode is used to listen for connection requests from configured remote clients.
•
•
•
•
The MP Server/Connection is deleted
When connection is moved to TotallyBlocked/RemotelyBlocked/InService state from Aligning
Auto Clear
Connection is disabled
1. Find additional information for the alarm in Main MenuAlarms & EventsView History by locating
the row with a sequence number that matches the active alarm sequence number and viewing the
Additional Info column.
2. Check the event history logs at Main MenuAlarms & EventsView History for additional
Communication Agent events or alarms from this MP server.
3. Check Main MenuCommunication AgentMaintenanceConnection Status to determine which
connections on the server have abnormal status.
910-6528-001 Revision D, December 2012
75
Alarms and Events
4. Verify that the remote server is not under maintenance.
5. If the connection is manually disabled at the client MP, and it is expected to be disabled, then no
further action is necessary.
6. If the connection has been manually disabled at the client MP, but it is not supposed to be disabled,
then enable the connection by clicking on the 'Enable' action button on the Connection Status screen.
7. Verify that IP network connectivity exists between the two connection end-points.
8. Verify that the connection's local IP address and port number are configured on remote client MP.
9. Verify that the Application Process using Communication Agent plug-in is running on both ends.
10. Verify that the connection's remote IP address and port correctly identify remote's listening port.
11. Contact the Tekelec Customer Care Center for assistance.
19805 - Communication Agent Failed To Align Connection
Alarm Type: CAF
Description: The Communication Agent failed to align connection. This alarm indicates that
Communication Agent has established one or more transport connections with servers that are running
incompatible versions of software, and so Communication Agent is unable to complete the alignment
of the connection. A connection that fails alignment cannot be used by applications to communicate
with other servers, and so this alarm may indicate that applications are unable to communicate with
their expected set of peers.
Severity: Major
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFConnAlignFailedNotify
Recovery:
1. If the connection administrative action is set to ‘disable’, the alarm is cleared. No further action is
necessary.
2. Check the event history logs at Main MenuAlarms & EventsView History for additional
Communication Agent events or alarms from this MP server.
3. Find additional information for the alarm in Main MenuAlarms & EventsView History by locating
the row with a sequence number that matches the active alarm sequence number and viewing the
Additional Info column.
4. Check the event history logs at Main MenuAlarms & EventsView History for additional
Communication Agent events or alarms from this MP server.
5. Check Main MenuCommunication AgentMaintenanceConnection Status to determine which
connections on the server have abnormal status.
For each connection reporting 'Aligning' connection status, determine the servers that are endpoints,
and verify that the correct software is installed on each server. If incorrect software is present, then
server maintenance may be required.
6. Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
76
Alarms and Events
19806 - Communication Agent CommMessage mempool utilization
Alarm Type: CAF
Description: The percent utilization of the Communication Agent CommMessage mempool is
approaching defined threshold capacity.
The percent utilization of the Communication Agent internal resource pool (CommMessage) is
approaching its defined capacity. If this problem persists and the usage reaches 100% utilization,
ComAgent will allocate the CommMessage objects from the heap. This should not impact the
functionality, but may impact performance and/or latency.
Severity: Critical, Major, Minor
Instance: <ComAgent Process Name>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFPoolResUtilNotify
Recovery:
1. Use Main MenuAlarms & Events to examine the alarm log.
An IP network or Adjacent node problem may exist preventing from transmitting messages into
the network at the same pace that messages are being received from the network. The Task thread
may be experiencing a problem preventing it from processing events from its internal resource
queue. Contact the Tekelec Customer Care Center for assistance.
2. Use Main MenuStatus & Control KPI Display to monitor the ingress traffic rate of each MP.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
Contact the Tekelec Customer Care Center for assistance.
3. If the MP ingres rate is approximately the same, there may be an insufficient number of MPs
configured to handle the network traffic load.
If all MPs are in a congestion state then the ingres rate to the server site is exceeding its capacity.
Contact the Tekelec Customer Care Center for assistance.
19807 - Communication Agent User Data FIFO Queue utilization
Alarm Type: CAF
Description: The percent utilization of the Communication Agent User Data FIFO Queue is approaching
defined threshold capacity. If this problem persists and the queue reaches above the defined threshold
utilization, the new StackEvents (Query/Response/Relay) messages for the Task can be discarded,
based on the StackEvent priority and Application's Global Congestion Threshold Enforcement Mode.
Severity: Minor, Major, Critical
Instance: <ComAgent StackTask Name>
HA Score: Normal
910-6528-001 Revision D, December 2012
77
Alarms and Events
Auto Clear Seconds: 0 (zero)
OID: CAFUserDataFIFOUtilNotify
Recovery:
1. An IP network or Adjacent node problem may exist preventing from transmitting messages into
the network at the same pace that messages are being received from the network.
2. Use Main MenuAlarms & Events to determine if the ComAgent worker thread may be experiencing
a problem preventing it from processing events from User Data FIFO queue.
Contact the Tekelec Customer Care Center for assistance.
3. The mis-configuration of Adjacent Node IP routing may result in too much traffic being distributed
to the MP. The ingress traffic rate of each MP can be monitored from Main MenuStatus & ControlKPI
Display.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
Contact the Tekelec Customer Care Center for assistance.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from Main MenuStatus & ControlKPI Display.
If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
Contact the Tekelec Customer Care Center for assistance.
19808 - Communication Agent Connection FIFO Queue utilization
Alarm Type: CAF
Description: The percent utilization of the Communication Agent Connection FIFO Queue is
approaching defined threshold capacity. If this problem persists and the queue reaches above the
defined threshold utilization, the new ComAgent internal Connection Management StackEvents
messages can be discarded based on Application's Global Congestion Threshold Enforcement Mode.
Severity: Minor, Major, Critical
Instance: <ComAgent StackTask Name>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFConnectionFIFOUtilNotify
Recovery:
1. An IP network or Adjacent node problem may exist preventing from transmitting messages into
the network at the same pace that messages are being received from the network.
2. Use Main MenuAlarms & Events to determine if the ComAgent worker thread may be experiencing
a problem preventing it from processing events from ComAgent Connection FIFO queue.
Contact the Tekelec Customer Care Center for assistance.
3. The mis-configuration of Adjacent Node IP routing may result in too much traffic being distributed
to the MP. The ingress traffic rate of each MP can be monitored from Main MenuStatus & ControlKPI
Display.
910-6528-001 Revision D, December 2012
78
Alarms and Events
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
Contact the Tekelec Customer Care Center for assistance.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from Main MenuStatus & ControlKPI Display.
If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
Contact the Tekelec Customer Care Center for assistance.
19810 - Communication Agent Egress Message Discarded
Event Type: CAF
Description: Communication Agent Egress Message Discarded.
Severity: Info
Instance: < RemoteIp >
Associated Measurement: CATxDscrdConnUnavail, CATxDscrdDestUserIncmpat,
CATxDscrdEncodeFail, CATxDscrdMxSendFail, CATxDscrdInternalErr, CATxDscrdUnkServer,
CAStackQueueFul
Recovery:
1. View the Event AddlInfo column.
Message is being discarded due to one of the reasons specified.
2. If it’s a persistent condition with the status of one of the Communication Agent Configuration
Managed Object then resolve the underlying issue with the Managed Object.
3. If the event is raised due to software condition, It’s an indication that the Communication Agent
Process may be experiencing problems.
4. Use Main MenuAlarms & Events and examine the alarm log.
5. Contact the Tekelec Customer Care Center for assistance.
19811 - Communication Agent Ingress Message Discarded
Event Type: CAF
Description: Communication Agent Ingress Message Discarded.
Severity: Info
Instance: < RemoteIp >
Associated Measurement: CARxDscrdMsgLenErr, CARxMsgUnkown, CARxDscrdDecodeFailed,
CARxDscrdUnkStkLyr, CARxDscrdLayerSendFail, CARxDscrdConnUnavail, CARxDscrdInternalErr,
CARxDscrdUnkServer, CARxDscrdIncompat, CARxDiscUnexpEvent, CATransDscrdInvCorrId,
CATransDscrdStaleErrRsp
Recovery:
1. View the Event AddlInfo column.
910-6528-001 Revision D, December 2012
79
Alarms and Events
Message is being discarded due to one of the reasons specified.
2. If it’s a persistent condition with the status of one of the Communication Agent Configuration
Managed Object then resolve the underlying issue with the Managed Object.
3. If the event is raised due to software condition, it is an indication that the Communication Agent
Process may be experiencing problems.
4. Use Main MenuAlarms & Events and examine the alarm log.
5. Contact the Tekelec Customer Care Center for assistance.
19814 - Communication Agent Peer has not responded to heartbeat
Event Type: CAF
Description: Communication Agent Peer has not responded to heartbeat.
Severity: Info
Instance: < RemoteIp >
Associated Measurement: None
Recovery:
1. Check the configuration of managed objects and resolve any configuration issues with the Managed
Object or hosting nodes.
This message may be due to network condition or latency or due to setup issues.
2. If the event is raised due to software condition, It’s an indication that the Communication Agent
Process may be experiencing problems.
3. Use Main MenuAlarms & Events and examine the alarm log.
4. Contact the Tekelec Customer Care Center for assistance.
19816 - Communication Agent Connection State Changed
Event Type: CAF
Description: Communication Agent Connection State Changed.
Severity: Info
Instance: < RemoteIp >
Associated Measurement: None
Recovery:
1. Use Main MenuAlarms & Events and examine the alarm log.
This Event is a log of connection state change.
2. Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
80
Alarms and Events
19817 - Communication Agent DB Responder detected a change in configurable control
option parameter
Event Type: CAF
Description: Communication Agent DB Responder detected a change in configurable control option
parameter.
Severity: Info
Instance: N/A
Associated Measurement: None
Recovery:
Event is an indication that Communication Agent detected a control parameter change. The change
will be applied to applicable software component. If the change is applied on the GUI, the appropriate
GUI action is logged in security logs. If the action is not performed from GUI and the control parameter
is changed, this event indicates the executed change.
1. Use Main MenuAlarms & Events and examine the alarm log.
2. Use Main MenuSecurity Log and examine the alarm log.
3. If the event shows up in Main MenuAlarms & Events, without the corresponding GUI security-log
in Main MenuSecurity Log. contact the Tekelec Customer Care Center for assistance.
19820 - Communication Agent Routed Service Unavailable
Alarm Type: CAF
Description: This alarm indicates that all connections of all connection groups associated with a Routed
Service are unavailable. This generally occurs when far-end servers have been removed from service
by maintenance actions. This can also occur if all of the Routed Service’s connections have been either
disabled or blocked.
Severity: Major
Instance: <RoutedServiceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFRSUnavailNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceRouted Service Status to view the connection
groups and connections associated with the Routed Service.
2. Use Main MenuCommunication AgentMaintenanceConnection Status to view the the reasons why
connections are unavailable.
3. Use Main MenuStatus & ManageServer to confirm that the far-end servers have an application
state of enabled, and that their subsystems are operating normally.
It is possible that this alarm results from conditions at the far-end servers connected to the server
that asserted this alarm.
910-6528-001 Revision D, December 2012
81
Alarms and Events
4. Contact the Tekelec Customer Care Center for assistance.
19821 - Communication Agent Routed Service Degraded
Alarm Type: CAF
Description: This alarm indicates that some, but not all, connections are unavailable in the connection
group being used by a Communication Agent Routed Service to route messages. The result is that the
server that posted this alarm is not load-balancing traffic across all of the connections configured in
the connection group.
Severity: Major
Instance: <ServiceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFRSDegradedNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceRouted Service Status to view the connection
groups and connections associated with the Routed Service.
2. Use Main MenuCommunication AgentMaintenanceConnection Status to view the the reasons why
connections are unavailable.
3. Use Main MenuStatus & ManageServer to confirm that the far-end servers have an application
state of enabled, and that their subsystems are operating normally.
It is possible that this alarm results from conditions at the far-end servers connected to the server
that asserted this alarm.
4. Contact the Tekelec Customer Care Center for assistance.
19822 - Communication Agent Routed Service Congested
Alarm Type: CAF
Description: This alarm indicates that a routed service is load-balancing traffic across all connections
in a connection group, but all of the connections are experiencing congestion. Messages may be
discarded due to congestion.
Severity: Major
Instance: <ServiceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFRSCongestedNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceRouted Service Status to view the connection
groups and connections associated with the Routed Service.
910-6528-001 Revision D, December 2012
82
Alarms and Events
2. Use Main MenuCommunication AgentMaintenanceConnection Status to view the the are congested
and the degree to which they are congested.
3. Check the far-end of the congested connections in order to further isolate the cause of congestion.
If the far-end servers are overloaded, then it is possible that the system is being presented a load
that exceeds its engineered capacity. If this is the case, then either the load must be reduced, or
additional capacity must be added.
4. Contact the Tekelec Customer Care Center for assistance.
19823 - Communication Agent Routed Service Using Low-Priority Connection Group
Alarm Type: CAF
Description: Communication Agent routed service is routing traffic using a connection group that has
a lower-priority than another connection group.
Severity: Major
Instance: <ServiceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFRSUsingLowPriConnGrpNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceRouted Service Status to view the connection
groups and connections associated with the Routed Service.
2. Use Main MenuCommunication AgentMaintenanceConnection Status to view the the reasons why
connections are unavailable.
3. Use Main MenuStatus & ManageServer to confirm that the far-end servers have an application
state of enabled, and that their subsystems are operating normally.
It is possible that this alarm results from conditions at the far-end servers connected to the server
that asserted this alarm.
4. Contact the Tekelec Customer Care Center for assistance.
19824 - Communication Agent Pending Transaction Utilization
Alarm Type: CAF
Description: The ComAgent Reliable Transfer Function is approaching or exceeding its engineered
reliable transaction handling capacity.
Severity: Minor, Major, Critical
Instance: n/a (ComAgent process)
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID:CAFTransUtilNotify
Recovery:
910-6528-001 Revision D, December 2012
83
Alarms and Events
1. Use Main MenuStatus & Control Server Status to view MP server status.
2. Remote server is slow in responding to outstanding transaction with correlation resource in-use.
The mis-configuration of ComAgent Server/Client routing may result in too much traffic being
distributed to affected connection for MP.
3. There may be an insufficient number of Server Application MPs configured to handle the internal
traffic load. If server application MPs are in a congestion state then the offered load to the server
site is exceeding its capacity.
4. Use Main MenuAlarm & Events and examine the alarm log.
The system may be experiencing network problems.
The Communication Agent Process may be experiencing problems.
5. Contact the Tekelec Customer Care Center for assistance.
19825 - Communication Agent Transaction Failure Rate
Alarm Type: CAF
Description: The number of failed transactions during the sampling period has exceeded configured
thresholds.
Severity: Minor, Major, Critical
Instance: <ServiceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFTransFailRateNotify
Recovery:
1. Use Main MenuStatus & Control Server Status to view MP server status.
2. Remote server is slow in responding to outstanding transaction with correlation resource in-use.
The mis-configuration of ComAgent Server/Client routing may result in too much traffic being
distributed to affected connection for MP.
3. There may be an insufficient number of Server Application MPs configured to handle the internal
traffic load. If server application MPs are in a congestion state then the offered load to the server
site is exceeding its capacity.
4. Use Main MenuAlarm & Events and examine the alarm log.
The system may be experiencing network problems.
The Communication Agent Process may be experiencing problems.
5. Contact the Tekelec Customer Care Center for assistance.
19826 - Communication Agent Connection Congested
Alarm Type: CAF
Description: This alarm indicates that Communication Agent is experiencing congestion in
communication between two servers, and this can be caused by a server becoming overloaded or by
network problems between two servers.
910-6528-001 Revision D, December 2012
84
Alarms and Events
Severity: Major
Instance:N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFConnCongestedNotify
Recovery:
1. Find additional information for the alarm in Main MenuAlarms & Events View History by locating
the row with a sequence number that matches the active alarm sequence number and viewing the
Additional Info column.
2. Check the event history logs at Main MenuAlarms & Events View History for additional
Communication Agent events or alarms from this MP server.
3. Check Main MenuCommunication AgentMaintenanceConnection Status to determine which
connections on the server have abnormal status.
4. If the Remote MP Overload Level (OL) > 0 then determine why the remote server is congested.
a) Verify that the remote server is not under maintenance.
b) Examine the remote's CPU utilization.
c) Examine the remote's current alarms.
5. If the local server's Transport Congestion Level (TCL) > 0 then determine why the connection is
not handling the load.
a) The remote may be overload by traffic from other MPs.
b) The local server may be trying to send too much traffic to the remote.
c) The IP connectivity may be impaired.
6. Contact the Tekelec Customer Care Center for assistance.
19830 - Communication Agent Service Registration State Change
Event Type: CAF
Description: Communication Agent Service Registration State Change.
Severity: Info
Instance: <ServiceName>
Associated Measurement: None
Recovery:
This event is a log of normal application startup and shutdown activity. It may provide aid during
trouble shooting when compared to other events in the log.
19831 - Communication Agent Service Operational State Changed
Event Type: CAF
Description: Communication Agent Service Operational State Changed.
Severity: Info
910-6528-001 Revision D, December 2012
85
Alarms and Events
Instance: <ServiceName>
Associated Measurement: None
Recovery:
1. This event indicates that a Communication Agent service changed operational state, and typically
results from maintenance actions.
A service can also change state due to server overload.
2. If the state change is unexpected, then contact the Tekelec Customer Care Center for assistance.
19832 - Communication Agent Reliable Transaction Failed
Event Type: CAF
Description: Failed transaction between servers result from normal maintenance actions, overload
conditions, software failures, or equipment failures.
Severity: Info
Instance: <ServiceName>, <RemoteIP> |< null>
• If serviceID is InvalidServiceID, then <ServiceName> is “EventTransfer”.
• If <ServiceName> is “EventTransfer”, then include <RemoteIP>.
• If serviceID is unknown, then <ServiceName> is null.
Associated Measurement: CATransEndAbnorm, CATransEndAnsErr, CATransEndErr,
CATransEndNoResponse, CATransEndNoResources, CATransEndUnkwnSvc, CATransEndUnregSvc,
CATransEndAbnormRateAvg, CATransEndAbnormRateMax
Recovery:
1. Use Main MenuCommunication AgentMaintenanceConnection Status to determine if the local
server is unable to communicate with another server or if servers have become overloaded.
2. Check the server’s KPIs and the Main MenuCommunication AgentMaintenanceConnection Status
to trouble-shoot the cause of server overload.
3. Check the Main MenuCommunication AgentMaintenanceHA Status that corresponds to the
ServiceID in the event instance to trouble-shoot the operation of the service.
4. If the event cannot be explained by maintenance actions, then contact the Tekelec Customer Care
Center for assistance.
19833 - Communication Agent Service Egress Message Discarded
Event Type: CAF
Description: Communication Agent Service Egress Message Discarded.
Severity: Info
Instance: <ServiceName>, <RemoteIP> |< null>
• If serviceID is unknown, then <ServiceName> is null.
Associated Measurement: CARSTxDscrdSvcUnavail, CARSTxDscrdCong, CATxDscrdUnknownSvc,
CATxDscrdUnregSvc
910-6528-001 Revision D, December 2012
86
Alarms and Events
Recovery:
1. View the Event AddlInfo column.
Message is being discarded due to one of the reasons specified.
2. If it’s a persistent condition with the status of one of the Communication Agent Configuration
Managed Object then resolve the underlying issue with the Managed Object.
3. If the event is raised due to software condition, It’s an indication that the Communication Agent
Process may be experiencing problems.
4. Use Main MenuAlarms & Events and examine the alarm log.
5. Contact the Tekelec Customer Care Center for assistance.
19842 - Communication Agent Resource-Provider Registered
Event Type: CAF
Description: Communication Agent Resource-Provider Registered.
Severity: Info
Instance: <ResourceName>
Associated Measurement: None
Recovery:
No action required.
19843 - Communication Agent Resource-Provider Resource State Changed
Event Type: CAF
Description: Communication Agent Resource-Provider Resource State Changed.
Severity: Info
Instance: <ProviderServerName>: <ResourceName>
Associated Measurement: None
Recovery:
No action required.
19844 - Communication Agent Resource-Provider Stale Status Received
Event Type: CAF
Description: Communication Agent Resource-Provider Stale Status Received.
Severity: Info
Instance: <ProviderServerName>: <ResourceName>
Associated Measurement: None
Recovery:
910-6528-001 Revision D, December 2012
87
Alarms and Events
If this event is occurring frequently then check the ComAgent maintenance screens for other
anomalies and to troubleshoot further.
19845 - Communication Agent Resource-Provider Deregistered
Event Type: CAF
Description: Communication Agent Resource-Provider Deregistered.
Severity: Info
Instance: <ResourceName>
Associated Measurement: None
Recovery:
No action required.
19846 - Communication Agent Resource Degraded
Alarm Type: CAF
Description: Communication Agent Resource Degraded. A local application is using the resource,
identified in the alarm, and the access to the resource is impaired. Some of the resource providers are
either unavailable and/or congested.
Severity: Major
Instance: <ResourceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFResourceDegradedNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceHA Services Status to determine which
sub-resources are unavailable or degraded for the server that asserted the alarm.
2. Use Main MenuCommunication AgentMaintenanceConnection Status to determine if connections
have failed or have congested.
3. Contact the Tekelec Customer Care Center for assistance.
19847 - Communication Agent Resource Unavailable
Alarm Type: CAF
Description: Communication Agent Resource Unavailable. A local application needs to use a ComAgent
resource, but the resource is unavailable. The resource can be unavailable if the local server has no
ComAgent connections to servers providing the resource or no servers host active instances of the
resource’s sub-resources.
Severity: Major
Instance: <ResourceName>
910-6528-001 Revision D, December 2012
88
Alarms and Events
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFResourceUnavailNotify
Recovery: Check the Communication Agent Connection Status maintenance screen
1. Use Main MenuCommunication AgentMaintenanceConnection Status to verify that the local server
is connected to the expected servers.
If the local server reports unavailable connections, then take actions to troubleshoot the cause of
the connection failures.
2. If the ComAgent connections are InService, use Main MenuCommunication AgentMaintenanceHA
Services Status to determine which servers are providing the resource.
If no servers are providing the resource, then the most likely reason is that maintenance actions
have been taken that have removed from service the application that provides the concerned
resource.
3. Contact the Tekelec Customer Care Center for assistance.
19848 - Communication Agent Resource Error
Alarm Type: CAF
Description: Communication Agent Resource Error. Two sets of servers are using incompatible
configurations for a ComAgent resource.
Severity: Minor
Instance: <ResourceName>
HA Score: Normal
Auto Clear Seconds: 50
OID: CAFResourceErrorNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceHA Services Status to determine which sets of
servers are incompatible.
Check the incompatible servers to verify that they are operating normally and are running the
expected versions of software.
2. Contact the Tekelec Customer Care Center for assistance.
19850 - Communication Agent Resource-User Registered
Event Type: CAF
Description: Communication Agent Resource-User Registered.
Severity: Info
Instance: <ResourceName>
Associated Measurement: None
910-6528-001 Revision D, December 2012
89
Alarms and Events
Recovery:
No action required.
19851 - Communication Agent Resource-User Deregistered
Event Type: CAF
Description: Communication Agent Resource-User Deregistered.
Severity: Info
Instance: <ResourceName>
Associated Measurement: None
Recovery:
No action required.
19852 - Communication Agent Resource Routing State Changed
Event Type: CAF
Description: Communication Agent Resource Routing State Changed.
Severity: Info
Instance: <ResourceName>
Associated Measurement: None
Recovery:
No action required.
19853 - Communication Agent Resource Egress Message Discarded
Event Type: CAF
Description: Communication Agent Resource Egress Message Discarded.
Severity: Info
Instance: <ResourceName>: <SubResourceID>
Note: If the resource is unknown, then <ResourceName> is the ResourceID converted to text. The
<SubResourceID> is an integer converted to text, regardless of whether it is known or unknown.
Associated Measurement: CAHSTxDscrdUnknownSR, CAHSTxDscrdUnavailSR,CAHSTxDscrdCongSR,
CAHSTxDscrdUnkwnRsrc, CAHSTxDscrdIntErrSR
Recovery:
1. Message is being discarded due to one of the reasons specified in Event AddlInfo.
If the condition is persistent with the status of one of the ComAgent Configuration Managed Objects
there is an underlying issue with the Managed Object.
2. Use Main MenuAlarms & Events and examine the alarm log for ComAgent Process problems.
910-6528-001 Revision D, December 2012
90
Alarms and Events
3. Contact the Tekelec Customer Care Center for assistance.
19854 - Communication Agent Resource-Provider Tracking Table Audit Results
Event Type: CAF
Description: Communication Agent Resource-Provider Tracking Table Audit Results. This event is
generated when a Resource Provider Tracking Table (RPTT) entry with Status equal to Auditing is
replaced with a new status (null, Active, Standby, Spare, OOS, etc) and there are no other RPTT entries,
for this specific Resource/SR, with Status equal to Auditing.
Severity: Info
Instance: None
Associated Measurement: None
Recovery:
No action required.
19855 - Communication Agent Resource Has Multiple Actives
Alarm Type: CAF
Description: This alarm indicates a possible IP network disruption that has caused more than one
Resource Provider to become Active. The server that asserted this alarm expects there to be only one
active Resource Provider server for the Resource, but instead it is seeing more than one. During this
condition the server may be sending commands to the wrong Resource Provider. This may affect
applications such as CPA, PDRA.
Severity: Major
Instance: <ResourceName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: CAFResourceMultActiveNotify
Recovery:
1. Use Main MenuCommunication AgentMaintenanceHA Services Status to determine which Resource
Provider servers are announcing ‘Active’ status for the Resource.
2. Investigate possible IP network isolation between these Resource Provider servers.
3. Contact the Tekelec Customer Care Center for assistance.
19900 - Process CPU Utilization
Alarm Type: STK
Description: The Process, which is responsible for handling all Signaling traffic, is approaching or
exceeding its engineered traffic handling capacity.
Severity: Critical, Major, Minor
910-6528-001 Revision D, December 2012
91
Alarms and Events
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: STKprocessCpuUtilizationNotify
Recovery:
1. Use Main MenuStatus & Control KPI Display to monitor the ingress traffic rate of each MP.
• The mis-configuration of Server/Client routing may result in too much traffic being distributed
to the MP. Each MP in the server site should be receiving approximately the same ingress
transaction per second.
• There may be an insufficient number of MPs configured to handle the network traffic load. If
all MPs are in a congestion state then the traffic load to the server site is exceeding its capacity.
2. Use Main MenuAlarms & Events to examine the alarm log.
Contact the Tekelec Customer Care Center for assistance.
19901 - CFG-DB Validation Error
Alarm Type: STK
Description: A minor database validation error was detected on the MP server during an update. MP
internal database is now out of sync with the configuration database. Subsequent database operations
on the MP are ALLOWED.
Severity: Major
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: STKcfgDbValidationErrorNotify
Recovery:
An unexpected condition has occurred while performing a database update, but database updates
are still enabled.
Contact the Tekelec Customer Care Center for assistance.
19902 - CFG-DB Update Failure
Alarm Type: STK
Description: A critical database validation error was detected on the MP server during an update. MP
internal database is now out of sync with the configuration database. Subsequent database operations
on the MP are DISABLED.
Severity: Critical
Instance: N/A
910-6528-001 Revision D, December 2012
92
Alarms and Events
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: STKcfgDbUpdateFailureNotify
Recovery:
An unexpected condition has occurred while performing a database update and database updates
are disabled.
Contact the Tekelec Customer Care Center for assistance.
19903 - CFG-DB post-update Error
Alarm Type: STK
Description: A minor database validation error was detected on the MP server after a database update.
MP internal database is still in sync with the configuration database. Subsequent database operations
on the MP are ALLOWED.
Severity: Major
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: STKcfgDbPostUpdateErrorNotify
Recovery:
An unexpected condition has occurred while performing a database update, but database updates
are still enabled.
Contact the Tekelec Customer Care Center for assistance.
19904 - CFG-DB post-update Failure
Alarm Type: STK
Description: A critical database validation error was detected on the MP server after a database update.
MP internal database is still in sync with the configuration database. Subsequent database operations
on the MP are DISABLED.
Severity: Critical
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: STKcfgDbPostFailureNotify
Recovery:
An unexpected condition has occurred while performing a database update and database updates
are disabled.
910-6528-001 Revision D, December 2012
93
Alarms and Events
Contact the Tekelec Customer Care Center for assistance.
19905 - Measurement Initialization Failure
Alarm Type: STK
Description: A measurement object failed to initialize.
Severity: Critical
Instance: <measTagName>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: STKmeasurementInitializationFailureNotify
Recovery:
Measurement subsystem initialization has failed for the specified measurement.
Contact the Tekelec Customer Care Center for assistance.
Diameter Signaling Router (DSR) Diagnostics (19910-19999)
This section provides information and recovery procedures for DSR alarms and events, ranging from
19910-19999, and lists the types of alarms and events that can occur on the system. All events have a
severity of Info.
Alarms and events are recorded in a database log table. Currently active alarms can be viewed from
the Launch Alarms Dashboard GUI menu option. The alarms and events log can be viewed from the
Alarms & Events > View History page.
19910 - Message Discarded at Test Connection
Event Type: DIAG
Description: Normal traffic is being discarded because it is routed to an egress Test Connection. An
egress Test Connection is given a normal message to be transmitted.
Severity: Major
Instance: <Connection name>
OID:
Recovery:
1. Update routing rules to exclude Test connections from being used for routing.
Normal traffic should be received and sent on non-test connections.
2. Change the hostname of the peer connected to the test connection.
The hostname of the peer connected to the test connection may be the destination host for the
incoming normal traffic.
910-6528-001 Revision D, December 2012
94
Alarms and Events
19911 - Test message discarded
Event Type: DIAG
Description: Test message is given to a non-test connection to be transmitted.
Severity: Info
Instance: <Connection name>
Associated Measurement:
Recovery:
Update routing rules to exclude Test messages from being routed to non-test connection.
Test messages should be received and sent only on test connections.
Diameter Signaling Router, DSR (22000-22999)
This section provides information and recovery procedures for DSR alarms and events, ranging from
22000 - 22999, and lists the types of alarms and events that can occur on the system. All events have
a severity of Info.
Alarms and events are recorded in a database log table. Currently active alarms can be viewed from
the Launch Alarms Dashboard GUI menu option. The alarms and events log can be viewed from the
Alarms & Events > View History page.
22001 - Message Decoding Failure
Event Type: DIAM
Description: A message received from a peer was rejected because of a decoding failure. Decoding
failures can include missing mandatory parameters. A Diameter message was received either without
the mandatory Destination-Realm AVP or, while parsing the message, the message content was
inconsistent with the Message Length in the message header.
Severity: Info
Instance: <TransConnName>
Associated Measurement: RxDecodeFailure
Recovery:
These protocol violations are caused by the originator of the message (identified by the Origin-Host
AVP in the message) or the peer who forwarded the message to this node (identified by the Peer
Name) and cannot be fixed using the application.
22002 - Peer Routing Rules with Same Priority
Event Type: DIAM
910-6528-001 Revision D, December 2012
95
Alarms and Events
Description: A peer routing table search with a received Request message found more than one highest
priority Peer Routing Rule match. The system selected the first rule found but it is not guaranteed that
the same rule will be selected in the future. It is recommended that Peer Routing Rules be unique for
the same type of messages to avoid non-deterministic routing results.
Severity: Info
Instance: <MPName>
Associated Measurement: RxRuleDuplicatePriority
Recovery:
Modify one of the Peer Routing Rule Priorities using the Diameter > Configuration > Peer Routing
Rules GUI page.
22003 - Application ID Mismatch with Peer
Event Type: DIAM
Description: While attempting to route a request message to a peer, a peer's transport connection was
bypassed because the peer did not support the Application ID for that transport connection.
Severity: Info
Instance: <MPName>
Associated Measurement: TxReqMsgApplMismatch
Recovery:
1. The system's peer routing table may be using a Route List containing a peer which does not support
the Application ID or the list of Application IDs supported by the peer on each connection may
not be the same. The list of Application IDs that the peer supports on each connection can be viewed
as follows:
a) Navigate to the GUI page: Diameter > Maintenance > Connections
b) Locate the relevant Peer Node and check the supported Application IDs.
2. If Application IDs are not the same for each connection (but should be) the Application ID for any
connection can be refreshed by:
a) Navigate to the GUI page: Diameter > Maintenance > Connections
b) Locate the relevant Connection
c) Disable the Connection
d) Enable the Connection
3. The Diameter Node which originated the message (identified by the Origin-Host AVP) could be
configured incorrectly and the application is trying to address a node which doesn't support the
Application ID. This cannot be fixed using this application.
4. If the problem persists, contact the Tekelec Customer Care Center.
22004 - Maximum pending transactions allowed exceeded
Event Type: DIAM
910-6528-001 Revision D, December 2012
96
Alarms and Events
Description: Routing attempted to select an egress transport connection to forward a message but the
maximum number of allowed pending transactions queued on the connection has been reached.
Severity: Info
Instance: <TransConnName>
Associated Measurement: TxReqMsgPerConnPtrMax
Recovery:
The maximum number of pending transactions for each connection is set to a system-wide default
value. If this event is occurring frequently enough for a particular connection then the maximum
value may need to be increased. Contact the Tekelec Customer Care Center for assistance.
22005 - No peer routing rule found
Event Type: DIAM
Description: A message not addressed to a peer (either Destination-Host AVP was absent or
Destination-Host AVP was present but was not a peer's FQDN) could not be routed because no Peer
Routing Rules matched the message.
Severity: Info
Instance: <MPName>
Associated Measurement: RxNoRulesFailure
Recovery:
1. Either the message the was incorrectly routed to this node or additional Peer Routing Rules need
to be added. Existing Peer Routing Rules can be viewed and updated using Diameter > Configuration
> Peer Routing Rules page.
2. If the problem persists, contact the Tekelec Customer Care Center.
22006 - Forwarding Loop Detected
Event Type: DIAM
Description:The Ingress Request message received was previously processed by the local node as
determine from the Route-Record AVPs received in the message and an ingress Request message was
rejected because message looping was detected. In general, the forwarding node should not send a
message to a peer which has already processed the message (it should examine the Route-Record
AVPs prior to message forwarding).
Severity: Info
Instance: <PeerName>
Associated Measurement: RxMessageLooping
Recovery:
1. If this type of error is occurring frequently, then the forwarding node is most likely incorrectly
routing the message and the issue cannot be fixed using this application.
2. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
97
Alarms and Events
22007 - Inconsistent Application ID Lists from a Peer
Event Type: DIAM
Description: The list of Application IDs supported by a peer during the Diameter Capabilities Exchange
procedure on a particular transport connection is not identical to one of the list of Application IDs
received from the peer over a different available transport connection to that peer.
Severity: Info
Instance: <PeerName>
Associated Measurement: EvApplIdListInconsistency
Recovery:
1. A peer with multiple transport connections has established a connection and provided a list of
supported Application IDs which does match a previously established connection. This could
prevent Request messages from being routed uniformly over the peer's transport connections
because the decision to route a message containing an Application ID is based upon the list of
Application IDs supported on each transport connection. The list of Application IDs that the peer
supports on each connection can be viewed as follows:
a) Navigate to Diameter > Maintenance > Connections.
b) Locate the relevant Peer Node and check the supported Application IDs.
2. If Application IDs are not the same for each connection (but should be) the Application ID for any
connection can be refreshed by:
a) Navigate to Diameter > Maintenance > Connections.
b) Locate the relevant Connection.
c) Disable the Connection.
d) Enable the Connection.
3. If the problem persists, contact the Tekelec Customer Care Center.
22008 - Orphan Answer Response Received
Event Type: DIAM
Description: An Answer response was received for which no pending request transaction existed,
resulting in the Answer message being discarded. When a Request message is forwarded the system
saves a pending transaction, which contains the routing information for the Answer response. The
pending transaction is abandoned if an Answer response is not received in a timely fashion.
Severity: Info
Instance: <TransConnName>
Associated Measurement: RxAnswerUnexpected
Recovery:
If this event is occurring frequently, the transaction timers may be set too low. The timer values
can be viewed and/or modified using the Diameter > Configuration > System Options page.
910-6528-001 Revision D, December 2012
98
Alarms and Events
22009 - Application Routing Rules with Same Priority
Event Type: DIAM
Description: An application routing table search with a received Request message found more than
one highest priority application routing rule match. At least two application routing rules with the
same priority matched an ingress Request message. The system selected the first application routing
rule found.
Severity: Info
Instance: <MPName>
Associated Measurement: RxApplRuleDuplicatePriority
Recovery:
1. It is recommended that application routing rules be unique for the same type of messages to avoid
unexpected routing results. Peer routing rule priorities can be modified using Diameter >
Configuration > Application Routing Rules page.
2. If the problem persists, contact the Tekelec Customer Care Center.
22011 - Copy message size exceeded the system set limit
Event Type: DIAM
Description: The message created for copying to the DAS exceeded the maximum message size set
system wide.
Severity: Info
Instance: <None>
Associated Measurement: DASCopyFailureSizeExceeded
Recovery:
1. Verify the size of the Request and Answer messages and see it exceeds the system set message size.
Use MainDiameterConfigurationRoute Lists to correct provisioning.
2. Review provisioning and correct provisioning and see whether answers also needed to copy.
Requests and answers may be copied to DAS.
3. If this problem persists, contact the Tekelec Customer Care Center for assistance.
22013 - DAS Peer Number of Retransmits Exceeded for Copy
Event Type: DIAM
Description: The configured number of Message Copy retransmits has been exceeded for the DAS
Peer.
Severity: Info
Instance: <RouteList>
Associated Measurement: DASCopyRetransmitsExceeded
910-6528-001 Revision D, December 2012
99
Alarms and Events
Recovery:
1. Review the configured value of ‘Max Retransmission Attempts’
2. Review local provisioning that connections to intended DAS peer server(s) are in service and that
no network issues exist in the path(s) to intended DAS peer server(s).
3. Review DAS peer provisioning to insure proper configuration.
4. If this problem persists, contact the Tekelec Customer Care Center for assistance.
22015 - Connection Operational Status Inconsistency May Exist
Alarm Type: DIAM
Description: DSR was unable to update the Operational Status and Operation Reason attributes for a
transport connection on the OAM.
Severity: Info
Instance: TransConnName
Associated Measurement: None
Recovery:
1. Use Main MenuDiameterMaintenanceConnections to view the Operational Status and Operation
Reason attributes for a Connection.
The Operational Status and Operation Reason attributes for a Connection on the OAM may be
temporarily out of date with the values on DSR.
This occurs when an internal event queue size has been exceeded. This should rarely occur and
the inconsistency should be cleared when the Connection’s “Remote Busy State” changes again.
2. If the problem persists, contact the Tekelec Customer Care Center.
22016 - Peer Node Alarm Aggregation Threshold
Alarm Type: DIAM
Description: This alarm occurs when there are a ‘Critical’ number of Peer Node alarms for a single
Network Element.
Note: The Alarm Thresholds are configurable using the “Alarm Threshold Options” tab on the Main
MenuDiameterConfigurationSystem Options screen.
Severity: Critical
Instance: <NetworkElement>
OID: eagleXgDiameterPeerNodeUnavailableThresholdReachedNotify
Recovery:
1.
2.
3.
4.
Use Main MenuDiameterMaintenancePeer Nodes to monitor Peer status.
Verify that IP network connectivity exists between the MP server and the adjacent servers.
Check the event history logs for additional DIAM events or alarms from this MP server.
Verify that the peer is not under maintenance.
910-6528-001 Revision D, December 2012
100
Alarms and Events
5. Contact the Tekelec Customer Care Center for assistance.
22017 - Route List Alarm Aggregation Threshold
Alarm Type: DIAM
Description: This alarm occurs when there are a ‘Critical’ number of Route List alarms for the Network
Element.
Note: The Alarm Thresholds are configurable using the “Alarm Threshold Options” tab on the Main
MenuDiameterConfigurationSystem Options screen.
Severity: Critical
Instance: <NetworkElement>
OID: eagleXgDiameterRouteListUnavailableThresholdReachedNotify
Recovery:
1.
2.
3.
4.
5.
Use Main MenuDiameterMaintenanceRoute Lists to monitor Route List status.
Verify that IP network connectivity exists between the MP server and the peers.
Check the event history logs for additional DIAM events or alarms from this MP server.
Verify that the peers in the Route List are not under maintenance.
Contact the Tekelec Customer Care Center for assistance.
22051 - Peer Unavailable
Alarm Type: DIAM
Description: Unable to access the Diameter Peer because all of the transport connections are Down.
Severity: Critical
Instance: <PeerName> (of the Peer which failed)
OID: PeerUnavailableNotify
Recovery:
1. Peer status can be monitored from Diameter > Maintenance > Peer Nodes.
2. Verify that IP network connectivity exists between the MP server and the adjacent servers.
3. Check the event history logs for additional DIAM events or alarms from this MP server.
4. Verify that the peer is not under maintenance.
5. If the problem persists, contact the Tekelec Customer Care Center.
22052 - Peer Degraded
Alarm Type: DIAM
Description: Unable to route Request messages to a Diameter Peer because all of its transport
connections are either Paused or locally congested. You will see this alarm for a peer if the number of
connections provisioned with this peer is less than the value of “Minimum Connection Capacity”
configured for this peer.
910-6528-001 Revision D, December 2012
101
Alarms and Events
Severity: Major
Instance: <PeerName> (of the Peer which is degraded)
OID: PeerDegradedNotify
Recovery:
1. Peer status can be monitored from Diameter > Maintenance > Peer Nodes.
2. Verify that IP network connectivity exists between the MP server and the adjacent servers.
3. Check the event history logs for additional DIAM events or alarms from this MP server.
4. Verify that the peer is not under maintenance.
5. If the problem persists, contact the Tekelec Customer Care Center.
22053 - Route List Unavailable
Alarm Type: DIAM
Description: The Route List is Unavailable. A Route List becomes Unavailable when all of its peers
become Unavailable and a Peer becomes Unavailable when all of its transport connections become
Unavailable.
If a Transport Connection is configured for Initiate mode, the Network Element will periodically
attempt to automatically recover the connection if its Admin State is Enabled. If the Transport
Connection is configured for Responder-Only mode, the peer will be responsible for re-establishing
the transport connection.
Severity: Critical
Instance: <RouteListName> (of the Route List which failed)
OID: RouteListUnavailableNotify
Recovery:
1. Route List status can be monitored from Diameter > Maintenance > Route Lists.
2. Verify that IP network connectivity exists between the MP server and the peers.
3. Check the event history logs for additional DIAM events or alarms from this MP server.
4. Verify that the peers in the Route List not under maintenance.
5. If the problem persists, contact the Tekelec Customer Care Center.
22054 - Route List Degraded
Alarm Type: DIAM
Description: The Route List's Operational Status has changed to Degraded because the capacity of the
Route List's Active Route Group has dropped below the Route List's configured minimum capacity.
There are two potential causes:
1. One or more of the Route List's peers become Unavailable. A Peer becomes Unavailable when all
of its transport connections become Unavailable. If a Transport Connection is configured for Initiate
mode, the Network Element will periodically attempt to automatically recover the connection if
its Admin State is Enabled. If the Transport Connection is configured for Responder-Only mode,
the peer will be responsible for re-establishing the transport connection.
910-6528-001 Revision D, December 2012
102
Alarms and Events
2. The Route Groups within the Route List may not have been configured with sufficient capacity to
meet the Route List's configured minimum capacity.
Severity: Major
Instance: <RouteListName> (of the Route List which is degraded)
OID: RouteListDegradedNotify
Recovery:
1. Route List status and configured minimum capacity can be monitored from Diameter > Maintenance
> Route Lists.
2. Verify that IP network connectivity exists between the MP server and the peers.
3. Check the event history logs for additional DIAM events or alarms from this MP server.
4. Verify that the peers in the Route List not under maintenance.
5. If the problem persists, contact the Tekelec Customer Care Center.
22055 - Non-Preferred Route Group in Use
Alarm Type: DIAM
Description: The application has started to utilize a Route Group other than the highest priority Route
Group to route Request messages for a Route List because the highest priority Route Group specified
for that Route List has either become Unavailable or its capacity has dropped below the minimum
capacity configured for the Route List while a lower priority Route Group has more capacity.
The preferred Route Group (i.e., with highest priority) is demoted from the Active Route Group to a
Standby Route Groupwhen a peer failure occurs causing the Route Group's Operational Status to
change to Unavailable or Degraded. A Route Group becomes Degraded when its capacity has dropped
below Route List's configured minimum capacity. A Route Group becomes Unavailable when all of
its peers have an Operational Status of Unavailable or Degraded.
A Peer becomes Unavailable when all of its transport connections become Unavailable. If a Transport
Connection is configured for Initiate mode, the Network Element will periodically attempt to
automatically recover the connection if its Admin State is Enabled. If the Transport Connection is
configured for Responder-Only mode, the peer will be responsible for re-establishing the transport
connection.
Severity: Minor
Instance: <RouteListName> (of the concerned Route List)
OID: NonpreferredRouteGroupInUseNotify
Recovery:
1. Route List status and configured minimum capacity can be monitored from Diameter > Maintenance
> Route Lists.
2. Verify that IP network connectivity exists between the MP server and the peers.
3. Check the event history logs for additional DIAM events or alarms from this MP server.
4. Verify that the adjacent server is not under maintenance.
5. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
103
Alarms and Events
22056 - Connection Admin State Inconsistency Exists
Alarm Type: DIAM
Description: An operator request to change the Admin State of a transport connection was not
completely processed due to an internal error. The admin state is either disabled from an egress routing
perspective but the connection could not be taken out of service or the admin state is enabled from an
egress routing perspective but the connection is not in service.
Severity: Major
Instance: <TransConnName>
OID: ConnectionDisableFailureNotify
Recovery:
1. If the transport connection's Admin State is Disabled but the transport connection was not taken
out of service due to an internal error do the following actions to correct the failure:
a) Enable the connection via the following GUI menu: Diameter > Maintenance > Connections
b) Wait for this alarm to clear.
c) Disable the connection via the following GUI menu: Diameter > Maintenance > Connections
2. If the transport connection's Admin State is Enabled but the transport connection was not taken
out of service due to an internal error do the following actions to correct the failure:
a) Disable the connection via the following Diameter > Maintenance > Connections
b) Wait for this alarm to clear.
c) Enable the connection via the following GUI menu: Diameter > Maintenance > Connections
3. If the problem persists, contact the Tekelec Customer Care Center.
22101 - Connection Unavailable
Alarm Type: DIAM
Description: Connection is unavailable for Diameter Request/Answer exchange with peer.
Severity: Major
Instance: <TransConnName>
OID: ConnectionUnavailableNotify
Recovery:
1. Identify the most recent Connection Unavailable event in the event log for the connection and use
the Event's recovery steps to resolve the issue.
2. If the problem persists, contact the Tekelec Customer Care Center.
22102 - Connection Degraded
Alarm Type: DIAM
Description: Connection is available for routing only messages with a priority greater than or equal
to the connection's congestion level.
910-6528-001 Revision D, December 2012
104
Alarms and Events
Severity: Major
Instance: <TransConnName>
OID: ConnectionDegradedNotify
Recovery:
1. Identify the most recent Connection Degraded event in the event log for the connection and use
the Event's recovery steps to resolve the issue.
2. If the problem persists, contact the Tekelec Customer Care Center.
22103 - SCTP Connection Impaired
Alarm Type: DIAM
Description: One or more paths of the SCTP connection went down.
Severity: Minor
Instance: <TransConnName>
OID: SCTPConnectionImpairedNotify
Recovery:
1. Identify the most recent SCTP Connection Impaired event in the event log for the connection and
use the Event's recovery steps to resolve the issue.
2. If the problem persists, contact the Tekelec Customer Care Center.
22104 - SCTP peer is operating with a reduced IP address set
Alarm Type: DIAM
Description: The SCTP peer advertised less IP addresses than desired by the connection configuration.
If two IP addresses have been configured for the Local Node of a certain SCTP connection, but following
the SCTP connection establishment the peer node has advertised only one IP address (basically less
than the number of IP addresses configured for the local node).
Severity: Minor
Instance: <TransConnName>
OID: SCTPPeerReducedIPSet
Recovery:
1. The peer is not able to advertise more than one IP address either due to an error in its configuration
or due to being affected by a network interface failure. Check the networking configuration on the
peer node.
2. If the problem persists, contact the Tekelec Customer Care Center.
22200 - Local MP Congestion
Alarm Type: DIAM
Description:The Diameter Process is approaching or exceeding its engineered traffic handling capacity.
910-6528-001 Revision D, December 2012
105
Alarms and Events
Severity: Minor, Major, Critical
Instance: N/A
OID: LocalMpCongestionNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter Process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22201 - Ingress Message Rate
Alarm Type: DIAM
Description: The ingress message rate for the MP is approaching or exceeding its engineered traffic
handling capacity.
Severity: Minor, Major, Critical
Instance: N/A
OID: IngressMessageRateNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If the problem persists, contact the Tekelec Customer Care Center.
22202 - PDU Buffer Pool Utilization
Alarm Type: DIAM
910-6528-001 Revision D, December 2012
106
Alarms and Events
Description: The MP's PDU buffer pool is approaching its maximum capacity. If this problem persists
and the pool reaches 100% utilization all new ingress messages will be discarded. This alarm should
not normally occur when no other congestion alarms are asserted.
Severity: Minor, Major, Critical
Instance: N/A
OID: PDUBufferPoolUtilizationNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. A software defect may exist resulting in PDU buffers not being deallocated to the pool. This alarm
should not normally occur when no other congestion alarms are asserted. The alarm log should
be examined using the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22203 - PTR Buffer Pool Utilization
Alarm Type: DIAM
Description: The MP's PTR buffer pool is approaching its maximum capacity. If this problem persists
and the pool reaches 100% utilization all new ingress messages will be discarded. This alarm should
not normally occur when no other congestion alarms are asserted.
Severity: Minor, Major, Critical
Instance: N/A
OID: PtrBufferPoolUtilizationNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
910-6528-001 Revision D, December 2012
107
Alarms and Events
4. A software defect may exist resulting in PTR buffers not being deallocated to the pool. This alarm
should not normally occur when no other congestion alarms are asserted. The alarm log should
be examined from the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22204 - Request Message Queue Utilization
Alarm Type: DIAM
Description: The MP's Request Message Queue Utilization is approaching its maximum capacity. If
this problem persists and the queue reaches 100% utilization all new ingress Request messages will
be discarded. This alarm should not normally occur when no other congestion alarms are asserted.
Severity: Minor, Major, Critical
Instance: N/A
OID: RequestMessageQueueUtilizationNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the Request Task may be experiencing a problem
preventing it from processing messages from its Request Message Queue. The alarm log should
be examined from the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22205 - Answer Message Queue Utilization
Alarm Type: DIAM
Description: The MP's Answer Message Queue Utilization is approaching its maximum capacity. If
this problem persists and the queue reaches 100% utilization all new ingress Answer messages will
be discarded. This alarm should not normally occur when no other congestion alarms are asserted.
Severity: Minor, Major, Critical
Instance: N/A
OID: AnswerMessageQueueUtilizationNotify
Recovery:
910-6528-001 Revision D, December 2012
108
Alarms and Events
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the Answer Task may be experiencing a problem
preventing it from processing messages from its Answer Message Queue. The alarm log should
be examined from the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22206 - Reroute Queue Utilization
Alarm Type: DIAM
Description: The MP's Reroute Queue is approaching its maximum capacity. If this problem persists
and the queue reaches 100% utilization any transactions requiring rerouting will be rejected. This
alarm should not normally occur when no other congestion alarms are asserted.
Severity: Minor, Major, Critical
Instance: N/A
OID: RerouteQueueUtilizationNotify
Recovery:
1. An excessive amount of Request message rerouting may have been triggered by either connection
failures or Answer time-outs. The status of connections should be examined from the Diameter >
Maintenance > Connections page.
2. If no additional congestion alarms are asserted, the Reroute Task may be experiencing a problem
preventing it from processing messages from its Answer Message Queue. The alarm log should
be examined using the Alarms & Events page.
3. If the problem persists, contact the Tekelec Customer Care Center.
22207 - All-Connections Event Queue Utilization
Alarm Type: DIAM
Description: The MP's All-Connections Event Queue is approaching its maximum capacity. If this
problem persists and the queue reaches 100% utilization all new ingress transactions will be rejected.
This alarm should not normally occur when no other congestion alarms are asserted.
Severity: Minor, Major, Critical
Instance: N/A
OID: AllConnectionsEventQueueUtilizationNotify
Recovery:
910-6528-001 Revision D, December 2012
109
Alarms and Events
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the task may be experiencing a problem preventing
it from processing events from its All-Connections Event Queue. The alarm log should be examined
using the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22209 - Message Copy Disabled
Alarm Type: DIAM
Description: Diameter Message Copy is disabled.
Severity: Minor
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: MessageCopyDisabledNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter Process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22214 - Message Copy Queue Utilization
Alarm Type: DIAM
Description: The MP's Message Copy queue utilization is approaching its maximum capacity.
910-6528-001 Revision D, December 2012
110
Alarms and Events
Severity: Minor, Major, Critical
Instance: N/A
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: MessageCopyQueueUtilNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter Process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
22220 - Connection Congestion Level change
Event Type: DIAM
Description: The egress congestion level associated with the connection has changed. When a
connection's egress queue is congested, the connection's operational status will be Degraded. If this
problem persists and the queue reaches 100% utilization all new egress messages for the Connection
will be discarded. This event should not normally occur when no other congestion alarms are asserted.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvPerConnQueueCongestionChange
Recovery:
1. An IP network or Diameter peer problem may exist thus preventing SCTP/TCP from transmitting
messages into the network at the same pace that messages are being received from the network.
2. The Transport Task associated with the connection may be experiencing a problem preventing it
from processing events from its Connection Event Message Queue. The alarm log should be
examined using the Alarms & Events page.
3. If one or more MPs in a server site have failed, the traffic will be distributed among the remaining
MPs in the server site. MP server status can be monitored using the Status & Manage > Server
page.
4. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP.
The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each
MP in the server site should be receiving approximately the same ingress transaction per second.
910-6528-001 Revision D, December 2012
111
Alarms and Events
5. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
6. If the problem persists, contact the Tekelec Customer Care Center.
22221 - Routing MPS Rate
Alarm Type: DIAM
Description: Message processing rate for this MP is approaching or exceeding its engineered traffic
handling capacity. The routing mps rate (MPS/second) is approaching or exceeding its engineered
traffic handling capacity for the MP.
Severity: Minor, Major, Critical
Instance: N/A
OID:RoutingMPSRateNotify
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed amongst the remaining
MPs in the server site.
MP server status can be monitored from Main MenuStatus & ManageServer Status.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP.
The routing mps rate of each MP can be monitored from Main MenuStatus & ManageKPI Display.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load.
The routing mps rate of each MP can be monitored from Main MenuStatus & ManageKPI Display.
If all MPs are in a congestion state then the ingress message rate to the MP is exceeding its capacity
to process the messages.
4. If the problem persists, contact the Tekelec Customer Care Center.
22300 - Connection Unavailable: Socket configuration failure
Event Type: DIAM
Description: Software failure attempting to configure SCTP or TCP socket.
Severity: Info
Instance: TransConnName
Associated Measurement: EvSockInitFail
Recovery:
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
112
Alarms and Events
22301 - Connection Unavailable: Connection initiation failure
Event Type: DIAM
Description: Failure occurred while attempting to initiate SCTP or TCP connection with the peer.
Severity: Info
Instance: TransConnName
Associated Measurement: EvConnCnxFail
Recovery:
1. Confirm that connection is not administratively Disabled at the peer.
2. Confirm that peer connection configuration (protocol, remote/local IP address, remote/local port)
matches local connection configuration.
3. Confirm IP network connectivity between peer IP and local IP for the connection.
4. Confirm that the connection’s transport protocol and/or port are not being blocked by a network
firewall or other ACL in the network path.
5. If the problem persists, contact the Tekelec Customer Care Center.
22302 - Connection Unavailable: Received malformed message
Event Type: DIAM
Description: Diameter message received from peer with invalid or inconsistent header/AVP length
fields.
Severity: Info
Instance: TransConnName
Associated Measurement: RxConnFailMalfMsg
Recovery:
1. Determine if other nodes/MPs connected to the peer are also experiencing problems with messages
received from the peer. If so, the peer should be diagnosed.
2. Determine if other connections on this same MP are also experiencing problems. If so, the MP
should be removed moved from service, replaced, and the Tekelec Customer Care Center should be
contacted to assist with resolution.
22303 - Connection Unavailable: Peer closed connection
Event Type: DIAM
Description: The SCTP or TCP connection was closed by the peer.
Severity: Info
Instance: TransConnName
Associated Measurement: EvConnFarEndClose
Recovery:
910-6528-001 Revision D, December 2012
113
Alarms and Events
1. If unexpected, use peer node diagnostic/log information to determine why peer closed connection.
2. If the problem persists, contact the Tekelec Customer Care Center.
22304 - Connection Unavailable: Proving Failure
Event Type: DIAM
Description: Connection closed after DWR/DWA based proving algorithm failure.
Severity: Info
Instance: TransConnName
Associated Measurement: EvConnPrvFail
Recovery:
1. Examine the peer to determine why it is not responding to DWRs.
2. If the problem persists, contact the Tekelec Customer Care Center.
22305 - Connection Admin State change
Event Type: DIAM
Description: The Administrative state of the connection has changed.
Severity: Info
Instance: TransConnName
Associated Measurement: EvConnManClose
Recovery:
No action required.
22306 - Connection Unavailable: Timeout waiting for CER/CEA
Event Type: DIAM
Description: Connection closed after Tcex timer expired while waiting on CER or CEA from peer.
Severity: Info
Instance: TransConnName
Associated Measurement: EvConnCexTO
Recovery:
1. For peer initiated connections, confirm that the configured Tcex timer value is not configured to
be less than the expected time for peer to send CER after successfully initiating connection.
2. For locally initiated connections, confirm that the configured Tcex timer value is not less than the
time expected for the peer to respond with CEA after receiving CER.
3. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
114
Alarms and Events
22307 - Connection Unavailable: Timeout waiting for DPA
Event Type: DIAM
Description: Connection closed after Tdpa timer expired while waiting on DPA from peer.
Severity: Info
Instance: TransConnName
Associated Measurement: EvConnDpaTO
Recovery:
No action required.
22308 - Received Unexpected CER/CEA
Event Type: DIAM
Description: CER or CEA message was received from the peer when it was not expected.
Severity: Info
Instance: TransConnName
Associated Measurement: RxConnUnexpCex
Recovery:
1. Diagnose peer for unexpected behavior.
2. If the problem persists, contact the Tekelec Customer Care Center.
22309 - Received Unexpected DWR/DWA
Event Type: DIAM
Description: DWR or DWA message was received from the peer when it was not expected.
Severity: Info
Instance: TransConnName
Associated Measurement: RxConnUnexpDwx
Recovery:
1. Diagnose peer for unexpected behavior.
2. If the problem persists, contact the Tekelec Customer Care Center.
22310 - Received Unexpected DPR/DPA
Event Type: DIAM
Description: DPR or DPA message was received from the peer when it was not expected.
Severity: Info
910-6528-001 Revision D, December 2012
115
Alarms and Events
Instance: TransConnName
Associated Measurement: RxConnUnexpDpx
Recovery:
1. Diagnose peer for unexpected behavior.
2. If the problem persists, contact the Tekelec Customer Care Center.
22311 - Invalid Diameter message received
Event Type: DIAM
Description: Diameter message received from peer which was decodable but contained a semantic
error.
Severity: Info
Instance: <TransConnName>
Associated Measurement: RxConnInvalidMsg
Recovery:
1. Analyze MsgOctets to determine which semantic error occurred and diagnose peer for unexpected
behavior.
2. If the problem persists, contact the Tekelec Customer Care Center.
22312 - Socket send failure
Event Type: DIAM
Description: An unexpected error occurred during the socket send call when attempting to send a
Diameter message to the peer.
Severity: Info
Instance: <TransConnName>
Associated Measurement: TxConnSendFail
Recovery:
1. Analyze error value to determine root cause.
2. If the problem persists, contact the Tekelec Customer Care Center.
22313 - Connection Unavailable: Transport failure
Event Type: DIAM
Description: The connection was closed by the SCTP or TCP transport.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnTransFail
910-6528-001 Revision D, December 2012
116
Alarms and Events
Recovery:
1. Analyze error value to determine root cause.
2. If the problem persists, contact the Tekelec Customer Care Center.
22314 - Connection Unavailable: CEA Realm/Host validation failure
Event Type: DIAM
Description: Origin-Realm and/or Origin-Host in CEA message received from peer on locally initiated
connection does not match the locally configured connection.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnCeaIdValFail
Recovery:
1. Confirm that peer connection configuration (Realm, Host, protocol, remote/local IP address,
remote/local port) matches local connection configuration using the Diameter > Configuration >
Local Nodes page.
2. If the problem persists, contact the Tekelec Customer Care Center.
22315 - Connection Unavailable: Peer IP address validation failure
Event Type: DIAM
Description: Actual peer connection IP address does not match configured peer IP address.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnRejected
Recovery:
1. Confirm that peer connection configuration (Realm, Host, protocol, remote/local IP address,
remote/local port) matches local connection configuration using the Diameter > Configuration >
Local Nodes page.
2. If the problem persists, contact the Tekelec Customer Care Center.
22316 - Connection Unavailable: No common apps
Event Type: DIAM
Description: No common applications were found between local node and peer node during capabilities
exchange.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnNoComnApps
910-6528-001 Revision D, December 2012
117
Alarms and Events
Recovery:
1. Reconcile Application IDs between local and peer nodes. If no common applications exist, the
connection should be deleted or Disabled.
2. If the problem persists, contact the Tekelec Customer Care Center.
22317 - Connection Rejected: Connection already established
Event Type: DIAM
Description: Peer initiated connection was rejected because locally initiated connection has already
completed capabilities exchange.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnRejected
Recovery:
1. If condition persists, diagnose peer to determine reason for the second connection initiation.
2. If the problem persists, contact the Tekelec Customer Care Center.
22318 - Connection Rejected: Connection not Enabled
Event Type: DIAM
Description: Peer initiated connection was rejected because connection was locally Admin Disabled.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnRejected
Recovery:
1. Resolve inconsistency between the local and peer nodes Administrative State.
2. If the problem persists, contact the Tekelec Customer Care Center.
22319 - Connection Unavailable: Diameter Watchdog
Event Type: DIAM
Description: Connection closed due to no traffic from peer within Tw*2 time after sending DWR.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnWdFail
Recovery:
1. Confirm that the connection is not administratively Disabled at the peer.
910-6528-001 Revision D, December 2012
118
Alarms and Events
2. Confirm that the peer connection configuration (protocol, remote/local IP address, remote/local
port) matches local connection configuration.
3. Confirm there is reliable IP network connectivity between the peer IP and the local IP for the
connection (no excess packet loss).
4. Confirm that the connection’s transport protocol and/or port are not being blocked by a network
firewall or other ACL in the network path.
5. If the problem persists, contact the Tekelec Customer Care Center.
22320 - Invalid peer initiated connection
Event Type: DIAM
Description: Origin-Realm and or Origin-Host in CER message received or the peer IP addresses
advertised on peer initiated connection does not match any locally configured connection
Severity: Info
Instance: <MPName>
Associated Measurement:EvMpCerIDValFail
Recovery:
1. Confirm that peer connection configuration (Realm, Host, protocol, remote/local IP address,
remote/local port) matches local connection configuration.
2. If the problem persists, contact the Tekelec Customer Care Center.
22321 - Connection Unavailable: DNS Resolution Failure
Event Type: DIAM
Description: During connection initiation, Transport/Peer FQDN was unable to be resolved to an IP
address via DNS
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnDnsFail
Recovery:
1.
2.
3.
4.
Confirm DNS is available and reachable by MP.
Confirm that DNS configuration contains peer FQDN and appropriate corresponding IP address(es).
Analyze errno value and text from Event Addn’l Info to determine root cause.
If the problem persists, contact the Tekelec Customer Care Center.
22322 - Connection Proving Success
Event Type: DIAM
Description: The connection proving phase completed successfully.
Severity: Info
910-6528-001 Revision D, December 2012
119
Alarms and Events
Instance: <TransConnName>
Associated Measurement:EvConnPrvSuccess
Recovery:
No action required.
22323 - Connection Degraded: Diameter Watchdog
Event Type: DIAM
Description: Connection declared suspect due to no traffic from peer within Tw time after sending
DWR.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnWdSuspect
Recovery:
1. Examine the peer to determine why it is not responding.
2. If the problem persists, contact the Tekelec Customer Care Center.
22324 - Connection Unavailable: CER validation failure
Event Type: DIAM
Description: CER contained invalid or unsupported AVP or AVP value.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnCerValFail
Recovery:
1. Disable peer’s use of inband security.
2. If the problem persists, contact the Tekelec Customer Care Center.
22325 - Host-IP-Address AVP(s) in CER/CEA do not match peer IP address(es)
Event Type: DIAM
Description: The Host-IP-Address AVP(s) received in a CER or CEA message from the peer did not
match the actual peer connection’s IP address(es).
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnCexIpChkFail
Recovery:
1. Diagnose peer to resolve inconsistency.
910-6528-001 Revision D, December 2012
120
Alarms and Events
2. If the problem persists, contact the Tekelec Customer Care Center.
22326 - Connection Established
Event Type: DIAM
Description: The peer connection is available for signaling traffic.
Severity: Info
Instance: <TransConnName>
Associated Measurement:EvConnCnxSuccess
Recovery:
No action required.
22327 - Initiator function disabled
Event Type: DIAM
Description: Peer disconnect reason indicated that we should not attempt to initiate a connection.
Severity: Info
Instance: <TransConnName>
Associated Measurement:N/A
Recovery:
1. No action required. The peer can still initiate a connection. If the peer does not attempt to initiate
a connection within a reasonable amount of time, the connection can be disabled, then re-enabled
to re-activate the initiator function.
2. If the problem persists, contact the Tekelec Customer Care Center.
22329 - SCTP Connection Impaired: A path has become unreachable
Event Type: DIAM
Description: A path of an established SCTP connection has become unreachable.
Severity: Info
Instance: <TransConnName:Peer IP> (peer/remote IP of the failed path)
Associated Measurement:N/A
Recovery:
1. Check whether the routing path between the local IP address and the peer IP address is up. If it is
not, fix it.
2. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
121
Alarms and Events
22330 - SCTP Connection Cfg Mismatch: The peer advertised a different number of IP
addresses than configured
Event Type: DIAM
Description: The peer has advertised in the INIT/INIT_ACK chunk a number of IP addresses different
from the number of IP addresses the peer has been configured with in the respective connection object.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnPeerNumIpFail
Recovery:
Check the peer configuration on the local node and the networking configuration on the peer itself
with regard to which IP addresses the peer shall advertise using the Diameter > Configuration >
System Options page.
22331 - SCTP Connection Partial Matching: SCTP connection accepted but the IP
addresses advertised by the peer match only partially those configured for the peer in
the connection object
Event Type: DIAM
Description: The peer has advertised in the INIT/INIT_ACK chunk a set of IP addresses which overlap
but does not include all the IP addresses configured for the peer in the respective connection object.
Severity: Info
Instance: <TransConnName>
Associated Measurement:
Recovery:
Check the peer configuration on the local node and the networking configuration on the peer itself
with regard to which IP addresses the peer shall advertise using the Diameter > Configuration >
System Options page.
22332 - Connection Rejected: Max Connections Exceeded
Event Type: DIAM
Description: Connection was rejected due to the DA-MP exceeding its maximum number of supported
Diameter Connections.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnRejMaxConnExceeded
Recovery:
910-6528-001 Revision D, December 2012
122
Alarms and Events
1. If the DA-MP is a member of a IPFE TS, verify that the IPFE is configured to fully monitor the
DA-MP’s availability status.
When a IPFE fully monitors application servers in a IPFE TS, it will cease from distributing new
Diameter connections to any/all application servers that report a “Stasis” availability status.
2. If the problem persists, contact the Tekelec Customer Care Center.
22334 - Unexpected Message Priority in ingress Request
Event Type: DIAM
Description: The decoded Message Priority from the ingress Request has an unexpected value.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnUnexpMp
Recovery:
1. Verify that the peer is a DSR
• Product-Name is reported as “Eagle XG DSR”, in the Event Additional Information.
• Vendor-Id is reported as 323 (Tekelec).
2. Verify that the Firmware-Revision reported in the Event Additional Information represents a DSR
software version that supports the Message Priority Feature.
• Call Customer Care Center and obtain the minimum DSR software version that supports Message
Priority and compare with this information.
• If the reported Firmware-Version is greater than or equal to the minimum required DSR software
version, call Customer Care Center.
• If the reported Firmware-Version is less than the minimum required DSR software version, call
Customer Care Center to seek advice on whether the peer DSR needs to be upgraded, or whether
the Message Priority Setting for this Transport Connection or Peer Node needs to be changed
to “None”.
22335 - Peer does not support Message Priority
Event Type: DIAM
Description: Cannot read Message Priority from ingress Requests because Peer does not support
Message Priority.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnPeerUnsuppMp
Recovery:
1. Verify that the peer is a DSR
• Product-Name is reported as “Eagle XG DSR”, in the Event Additional Information.
910-6528-001 Revision D, December 2012
123
Alarms and Events
• Vendor-Id is reported as 323 (Tekelec).
2. Verify that the Firmware-Revision reported in the Event Additional Information represents a DSR
software version that supports the Message Priority Feature.
• Call Customer Care Center and obtain the minimum DSR software version that supports Message
Priority and compare with this information.
• If the reported Firmware-Version is greater than or equal to the minimum required DSR software
version, call Customer Care Center.
• If the reported Firmware-Version is less than the minimum required DSR software version, call
Customer Care Center to seek advice on whether the peer DSR needs to be upgraded, or whether
the Message Priority Setting for this Transport Connection or Peer Node needs to be changed
to “None”.
22336 - Connection Rejected: Multihomed SCTP connection attempt
Event Type: DIAM
Description: Connection was rejected because the peer attempted to initiate an SCTP multihomed
connection to an IPFE connection.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnRejMultiHomedSCTPAtt
Recovery:
1. Update the peer to initiate unihomed IPFE SCTP connections.
2. Contact the Tekelec Customer Care Center for assistance.
22343 - Connection Unavailable: Duplicate Connection Released
Event Type: DIAM
Description: Duplicate connection established, connection terminated.
Severity: Info
Instance: <TransConnName>
Associated Measurement: EvConnRelease
Recovery:
No action necessary.
22344 - Failed to process ingress message: Processor Unavailable or Congested
Event Type: DIAM
Description: The DSR message processor is Unavailable or Congested. This event refers to another
DA-MP, not the one reporting the problem.
Severity: Info
910-6528-001 Revision D, December 2012
124
Alarms and Events
Instance: <SourceMpHost>
Associated Measurement: RxAnsFwdFailed
Recovery:
If this measurement is seen to be incrementing consistently, contact the Tekelec Customer Care
Center.
This measurement should be pegged, only when the DSR process on the destination DA-MP is
Unavailable or the DA-MP is rebooting.
22345 - Connection Priority Level changed
Event Type: DIAM
Description: The Diameter Connection’s CPL has transitioned from its current value to a new CPL
value based on congestion levels reported by various features.
Severity: Info
Instance: <TransConnName>
Associated Measurement: None
Recovery:
1. Find additional information for the alarm in Main MenuAlarms & EventsView History by locating
the row with a sequence number that matches the active alarm sequence number and viewing the
Additional Info column.
2. Identify the most recent “Connection Degraded” event in the event log for the connection and
utilize the Event Detailed information to diagnose the condition.
3. If the problem persists, contact the Tekelec Customer Care Center for assistance.
22346 - MP Reserved Ingress MPS Oversubscribed
Event Type: DIAM
Description: The total connection Reserved Ingress MPS exceeds the Engineered Ingress MPS capacity
of the MP.
Severity: Info
Instance: MPName (Hostname of the DA-MP Server)
Associated Measurement: None
Recovery:
1. Find additional information for the alarm in Main MenuAlarms & EventsView History by locating
the row with a sequence number that matches the active alarm sequence number and viewing the
Additional Info column.
2. Perform one or more of these actions:
• Increase the maximum reserved capacity by increasing the value of IPFE Connection Reserved
Ingress MPS Scaling parameter.
• Reduce the subscribed amount of reserved capacity by reducing the number of connections.
910-6528-001 Revision D, December 2012
125
Alarms and Events
• Reduce the reserved capacity required by connections.
3. If the problem persists, contact the Tekelec Customer Care Center for assistance.
22349 - IPFE Connection Alarm Aggregation Threshold
Alarm Type: DIAM
Description: This alarm occurs when there are a ‘Critical’ number of IPFE Connection alarms for the
Network Element.
Note: The Alarm Thresholds are configurable using the “Alarm Threshold Options” tab on the Main
MenuDiameterConfigurationSystem Options screen.
Severity: Critical, Major
Note: The Critical threshold may be disabled by setting the Critical Threshold to zero using the “Alarm
Threshold Options” tab on the Main MenuDiameterConfigurationSystem Options screen.
Instance: <NetworkElement>
OID: eagleXgDiameterIPFEConnUnavailableThresholdReachedNotify
Recovery:
1. Use Main MenuDiameterMaintenanceConnection to monitor IPFE Connection status.
2. Confirm that peer connection configuration (protocol, remote/local IP address, remote/local port)
matches the local connection configuration.
3. Confirm that the connection’s transport protocol and/or port are not being blocked by a network
firewall or other ACL in the network path.
4. Verify that the peers in the Route List are not under maintenance.
5. Contact the Tekelec Customer Care Center for assistance.
22350 - Fixed Connection Alarm Aggregation Threshold
Alarm Type: DIAM
Description: This alarm occurs when there are a ‘Critical’ number of Fixed Connection alarms for the
DA-MP.
Note: The Alarm Thresholds are configurable using the “Alarm Threshold Options” tab on the Main
MenuDiameterConfigurationSystem Options screen.
Severity: Critical, Major
Note: The Critical threshold may be disabled by setting the Critical Threshold to zero using the “Alarm
Threshold Options” tab on the Main MenuDiameterConfigurationSystem Options screen.
Instance: <DA-MP-Hostname>
OID: eagleXgDiameterFixedConnUnavailableThresholdReachedNotify
Recovery:
1. Use Main MenuDiameterMaintenanceConnection to monitor Fixed Connection status.
2. Confirm that peer connection configuration (protocol, remote/local IP address, remote/local port)
matches the local connection configuration.
910-6528-001 Revision D, December 2012
126
Alarms and Events
3. Confirm that the connection’s transport protocol and/or port are not being blocked by a network
firewall or other ACL in the network path.
4. Verify that the peers in the Route List are not under maintenance.
5. Contact the Tekelec Customer Care Center for assistance.
22400 - Message Decoding Failure
Event Type: RBAR
Description: A message received was rejected because of a decoding failure.
Severity: Info
Instance: <MPName>
Associated Measurement: RxRbarDecodeFailureResol
Recovery:
While parsing the message, the message content was inconsistent with the Message Length in the
message header. These protocol violations can be caused by the originator of the message (identified
by the Origin-Host AVP in the message) or the peer who forwarded the message to this node.
22401 - Unknown Application ID
Event Type: RBAR
Description: A message could not be routed because the Diameter Application ID is not supported.
Severity: Info
Instance: <MPName>
Associated Measurement: RxRbarUnkApplId
Recovery:
The DSR Relay Agent forwarded a Request message to the address resolution application which
contained an unrecognized Diameter Application ID in the header. Either a DSR Relay Agent application
routing rule is mis-provisioned or the Application ID is not provisioned in the RBAR routing
configuration.
View the currently provisioned Diameter Application IDs by selecting RBARConfigurationApplications.
View the currently provisioned Application Routing Rules by selecting DiameterConfiguration
Application Routing Rules.
22402 - Unknown Command Code
Event Type: RBAR
Description: A message could not be routed because the Diameter Command Code in the ingress
Request message is not supported and the Routing Exception was configured to send an Answer
response.
Severity: Info
Instance: <MPName>
910-6528-001 Revision D, December 2012
127
Alarms and Events
Associated Measurement: RxRbarResolFailCmdcode
Recovery:
The order pair (Application ID, Command Code) is not provisioned in the Address Resolutions routing
configuration.
View the currently provisioned Application IDs and Command Codes by selecting
RBARConfigurationAddress Resolutions.
22403 - No Routing Entity Address AVPs
Event Type: RBAR
Description: A message could not be routed because no address AVPs were found in the message and
the Routing Exception was configured to send an Answer response.
Severity: Info
Instance: <AddressResolution>
Associated Measurement: RxRbarResolFailNoAddrAvps
Recovery:
This may be a normal event or an event associated with misprovisioned address resolution
configuration. If this event is considered abnormal, validate which AVPs are configured for routing
with the Application ID and Command Code.
View the currently provisioned Application IDs and Command Codes by selecting
RBARConfigurationAddress Resolutions.
22404 - No valid Routing Entity Addresses found
Event Type: RBAR
Description: A message could not be routed because none of the address AVPs contained a valid
address and the Routing Exception was configured to send an Answer response.
Severity: Info
Instance: <AddressResolution>
Associated Measurement: RxRbarResolFailNoValidAddr
Recovery:
This may be a normal event or an event associated with misprovisioned address resolution
configuration. If this event is considered abnormal, validate which AVPs are configured for routing
with the Application ID and Command Code.
View the currently provisioned Application IDs and Command Codes by selecting
RBARConfigurationAddress Resolutions.
22405 - Valid address received didn’t match a provisioned address or address range
Event Type: RBAR
910-6528-001 Revision D, December 2012
128
Alarms and Events
Description: A message could not be routed because a valid address was found that did not match an
individual address or address range associated with the Application ID, Command Code, and Routing
Entity Type, and the Routing Exception was configured to send an Answer response.
Severity: Info
Instance: <AddressResolution>
Associated Measurement: RxRbarResolFailImsiMatch
RxRbarResolFailMsisdnMatch
RxRbarResolFailImpiMatch
RxRbarResolFailImpuMatch
RxRbarResolFailIpv4Match
RxRbarResolFailIpv6prefixMatch
RxRbarResolFailUnsigned16Match
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
22406 - Routing attempt failed due to internal resource exhaustion
Event Type: RBAR
Description: A message could not be routed because the internal "Request Message Queue" to the DSR
Relay Agent was full. This should not occur unless the MP is experiencing local congestion as indicated
by Alarm-ID 22200 - Local MP Congestion.
Severity: Info
Instance: <MPName>
Associated Measurement: TxRbarFullDRLRequestReject
Recovery:
If this problem occurs, contact the Tekelec Customer Care Center.
22407 - Routing attempt failed due to internal database inconsistency failure
Event Type: RBAR
Description: A message could not be routed because an internal address resolution run-time database
inconsistency was encountered.
Severity: Info
Instance: <MPName>
Associated Measurement: RxRbarResolFailDbFail
Recovery:
910-6528-001 Revision D, December 2012
129
Alarms and Events
If this problem occurs, contact the Tekelec Customer Care Center.
22500 - DSR Application Unavailable
Alarm Type: APPL
Description: DSR Application is unable to process any messages because it is Unavailable
Severity: Critical
Instance: <DSR Application Name>
HA Score: Normal
Auto Clear Seconds: N/A
OID: DSRApplicationUnavailableNotify
Recovery:
1. Display and monitor the DSR Application status by selecting Diameter>Maintenance>Applications.
Verify that the Admin State is set as expected.
A DSR Application becomes Unavailable when either the Admin State is set to Disable with the
Forced Shutdown option, or the Admin State is set to Disable with the Graceful Shutdown option
and the Graceful Shutdown timer expires.
A DSR Application can also become Unavailable when it reaches Congestion Level 3.
2. Check the Event History logs for additional DIAM events or alarms for this MP server.
3. If the problem persists, contact the Tekelec Customer Care Center.
22501 - DSR Application Degraded
Alarm Type: APPL
Description: Unable to forward requests to the DSR Application because it is Degraded
Severity: Critical
Instance: <DSR Application Name>
HA Score: Normal
Auto Clear Seconds: N/A
OID: DSRApplicationDegradedNotify
Recovery:
1. Display and monitor the DSR Application status by selecting Diameter>Maintenance>Applications.
Verify that the Admin State is set as expected.
A DSR Application becomes Degraded when the DSR Application becomes congested or is in the
process of gracefully shutting down.
2. Check the Event History logs for additional DIAM events or alarms for this MP server.
3. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
130
Alarms and Events
22502 - DSR Application Request Message Queue Utilization
Alarm Type: APPL
Description: The DSR Application Request Message Queue Utilization is approaching its maximum
capacity
Severity: Minor, Major, Critical
Instance: <DSR Application Name>
HA Score: Normal
Auto Clear Seconds: N/A
OID: DSRAppRequestMessageQueueUtilizationNotify
Recovery:
1. Display and monitor the DSR Application status by selecting Diameter>Maintenance>Applications.
Verify that the Admin State is set as expected.
The DSR Application's Request Message Queue Utilization is approaching its maximum capacity.
This alarm should not normally occur when no other congestion alarms are asserted.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting Diameter>Configuration >Application Routing Rules.
3. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Request Message Queue. Examine
the Alarm log in Alarms & Events
4. If the problem persists, contact the Tekelec Customer Care Center.
22503 - DSR Application Answer Message Queue Utilization
Alarm Type: APPL
Description: The DSR Application Answer Message Queue Utilization is approaching its maximum
capacity
Severity: Minor, Major, Critical
Instance: <DSR Application Name>
HA Score: Normal
Auto Clear Seconds: N/A
OID: DSRAppAnswerMessageQueueUtilizationNotify
Recovery:
1. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting Diameter>Configuration >Application Routing Rules.
2. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Answer Message Queue. Examine
the Alarm log in Alarms & Events
3. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
131
Alarms and Events
22504 - Ingress Message Rate
Alarm Type: APPL
Description: The ingress message rate for the DSR Application is approaching or exceeding its
engineered traffic handling capacity
Severity: Minor, Major, Critical
Instance: <DSR Application Name>
HA Score: Normal
Auto Clear Seconds: N/A
OID: DSRAppIngressMessageRateNotify
Recovery:
1. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting Diameter>Configuration >Application Routing Rules.
2. There might be an insufficient number on MPs configured to handle the network load. Monitor
the ingress traffic rate of each MP by selecting Status & Manage>KPI Display.
If MPs are in a congestion state, then the offered load to the server site is exceeding its capacity.
3. If the problem persists, contact the Tekelec Customer Care Center.
25510 - Multiple DA-MP Leader Detected Alarm
Alarm Type: DIAM
Description: This alarm occurs when multiple active DA-MP leaders have been detected.
Severity: Critical
Instance: <NetworkElement>
OID: eagleXgDiameterMultipleDaMpLeadersDetectedNotify
Recovery:
If the problem persists, contact the Tekelec Customer Care Center for assistance.
22520 - DSR Application Enabled
Event Type: APPL
Description: DSR Application Admin state was changed to ‘enabled’.
Severity: Info
Instance: <DSR Application Name>
Associated Measurement: N/A
Recovery:
1. No action required.
910-6528-001 Revision D, December 2012
132
Alarms and Events
2. If the problem persists, contact the Tekelec Customer Care Center.
22521 - DSR Application Disabled
Event Type: APPL
Description: DSR Application Admin state was changed to ‘disabled’.
Severity: Info
Instance: <DSR Application Name>
Associated Measurement: N/A
Recovery:
1. No action required.
2. If the problem persists, contact the Tekelec Customer Care Center.
22600 - Message Decoding Failure
Event Type: FABR
Description: Message received was rejected because of a decoding failure. While parsing the message,
the message content was inconsistent with the "Message Length" in the message header. These protocol
violations can be caused by the originator of the message (identified by the Origin-Host AVP in the
message), the peer who forwarded the message to this node, or any intermediate node that modifies
the message.
Severity: Info
Instance: <MPName>
Associated Measurement: RxFabrDecodeFailureResol
Recovery:
Contact the Tekelec Customer Care Center for assistance.
22601 - Unknown Application ID
Event Type: FABR
Description: Message could not be routed because the Diameter Application ID is not supported.
Severity: Info
Instance: <MPName>
Associated Measurement: RxFabrUnkApplId
Recovery:
A Request message was forwarded to the FABR application which contained an unrecognized Diameter
Application ID in the header. Either an application routing rule is mis-provisioned or the Application
ID is not provisioned in the FABR configuration.
910-6528-001 Revision D, December 2012
133
Alarms and Events
1. The currently provisioned Application Routing Rules can be viewed using Main Menu Diameter
Configuration Application Routing Rules.
2. The currently provisioned Diameter Application IDs can be viewed in the
FABRConfigurationApplications Configuration.
3. Contact the Tekelec Customer Care Center for assistance.
22602 - Unknown Command Code
Event Type: FABR
Description: Message could not be routed because the Diameter Command Code in the ingress Request
message is not supported and the Routing Exception was configured to send an Answer response.
Severity: Info
Instance: <MPName>
Associated Measurement: RxFabrResolFailCmdcode
Recovery:
Either an application routing rule is mis-provisioned or the Command Code is not provisioned in the
FABR configuration.
1. The currently provisioned Application Routing Rules can be viewed using Main Menu Diameter
Configuration Application Routing Rules.
2. The currently provisioned Diameter Application IDs can be viewed in the
FABRConfigurationAddress Resolutions.
3. Contact the Tekelec Customer Care Center for assistance.
22603 - No Routing Entity Address AVPs
Event Type: FABR
Description: Message could not be routed because no address AVPs were found in the message and
the Routing Exception was configured to send an Answer response.
Severity: Info
Instance: <AddrResolution>
Associated Measurement: RxFabrResolFailNoAddrAvps
Recovery:
1. If this event is considered abnormal, then validate which AVPs are configured for routing with the
Application ID and Command Code using FABRConfigurationAddress Resolutions.
2. The currently provisioned Application Routing Rules can be viewed using Main Menu Diameter
Configuration Application Routing Rules.
3. Contact the Tekelec Customer Care Center for assistance.
22604 - No valid User Identity Addresses found
Event Type: FABR
910-6528-001 Revision D, December 2012
134
Alarms and Events
Description: No valid User Identity Address is found in the configured AVPs contained in the ingress
message.
Severity: Info
Instance: <AddrResolution>
Associated Measurement: RxFabrResolFailNoValidAddr
Recovery:
1. If this event is considered abnormal, then validate which AVPs are configured for routing with the
Application ID and Command Code using FABRConfigurationAddress Resolutions.
2. The currently provisioned Application Routing Rules can be viewed using Main Menu Diameter
Configuration Application Routing Rules.
3. Contact the Tekelec Customer Care Center for assistance.
22605 - No Destination address is found to match the valid User Identity address
Event Type: FABR
Description: Message could not be routed because the valid user identity address extracted from the
message did not resolve to a destination address. The Routing Exception was configured to send an
Answer response. Please verify the provisioning in the address resolution table and the data provided
in the SDS corresponding to this address/resolution entry.
Severity: Info
Instance: <AddrResolution>
Associated Measurement: RxFabrResolFailImsiMatch, RxFabrResolFailMsisdnMatch,
RxFabrResolFailImpiMatch, RxFabrResolFailImpuMatch
Recovery:
The FABR address resolution table entry may be misconfigured or the destination address associated
with User Identity address from the message and the destination type configured in the address
resolution table may be missing from the address mapping configuration. The destination address
associated with User Identity address derived may be missing from the address mapping configuration
on DP/SDS.
1. Validate the address resolution table entry and verify that a valid destination address is associated
with the user identity address by using DP configuration.
For additional information, see Subscriber Database Server online help.
2. Contact the Tekelec Customer Care Center for assistance.
22606 - Database or DB connection error
Event Type: FABR
Description: FABR application receives service notification indicating Database (DP) or DB connection
(ComAgent) Errors (DP timeout, errors or ComAgent internal errors) for the sent database query.
Severity: Info
Instance: <MPNname>
910-6528-001 Revision D, December 2012
135
Alarms and Events
Associated Measurement: RxFabrSrvNotiDpComAgentErrors
Recovery:
Contact the Tekelec Customer Care Center for assistance.
22607 - Routing attempt failed due to DRL queue exhaustion
Event Type: FABR
Description: Message could not be routed because the internal “Request Message Queue” to the DSR
Relay Agent was full.
Severity: Info
Instance: <MPNname>
Associated Measurement: TxFabrFwdFail
Recovery:
Contact the Tekelec Customer Care Center for assistance.
22608 - Database query could not be sent due to DB congestion
Event Type: FABR
Description: FABR could not send a database query either because the ComAgent reported DP
congestion level of (CL=2 or 3), or an abatement period is in progress.
Severity: Info
Instance: <MPNname>
Associated Measurement: RxFabrSrvNotiDpCongest
Recovery:
Contact the Tekelec Customer Care Center for assistance.
22609 - Database connection exhausted
Event Type: FABR
Description: Database queries could not be sent because the database connection (ComAgent) queue
was full
Severity: Info
Instance: <MPNname>
Associated Measurement: TxFabrDbConFail
Recovery:
Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
136
Alarms and Events
22631 - FABR DP Response Task Message Queue Utilization
Alarm Type: FABR
Description: The FABR Application's DP Response Message Queue Utilization is approaching its
maximum capacity.
Severity: Minor, Major, Critical
Instance: Full Address Based Resolution
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: FabrAppDpResponseMessageQueueUtilizationNotify
Recovery:
This alarm may occur due to persistent overload conditions with respect to database response
processing.
Contact the Tekelec Customer Care Center for assistance.
22632 - COM Agent Registration Failure
Alarm Type: FABR
Description: The Communication Agent routing service registration or service notification registration
failed, FABR can not use the Communication Agent service for database queries.
Severity: Critical
Instance: Full Address Based Resolution
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: ComAgentRegistFailNotify
Recovery:
Contact the Tekelec Customer Care Center for assistance.
22804 - Number of cSBR Unavailable Subresources at Threshold
Alarm Type: CPA
Description: The number of unavailable SBR subresources meets or exceeds the CpaSbrForUnavailable
engineering configurable threshold.
Severity: Critical
Instance: Site Id
HA Score: Normal
Auto Clear Seconds: N/A
910-6528-001 Revision D, December 2012
137
Alarms and Events
OID: cpaUnavailableSubresourcesAtThreshold
Recovery:
1. Check the state of the SBR MPs.
One or more Charging SBR subresources are unavailable. Make sure the SBR MPs are not having
networking trouble.
2. Contact the Tekelec Customer Care Center for assistance.
22805 - Message Decoding Failure
Event Type: CPA
Description: The CPA application could not decode a received Diameter message
Severity: Info
Instance: N/A
Associated Measurement: EvCpaMessageDecodeFail
Recovery:
1. These protocol violations can be caused by the originator of the message (identified by the
Origin-Host AVP in the message) or the peer who forwarded the message to this node.
While parsing the message, the message content was inconsistent with the "Message Length" in
the message header.
2. Contact the Tekelec Customer Care Center for assistance.
22806 - Unknown Diameter Application Id
Event Type: CPA
Description: The CPA application received a Diameter message with an unexpected DSR application
id. The DSR Relay Agent forwarded a Request message to the CPA application which contained an
unrecognized Diameter Application ID in the header. A DSR Relay Agent application routing rule is
mis-provisioned.
Severity: Info
Instance: N/A
Associated Measurement: EvCpaUnkDiameterAppId
Recovery:
1. Examine the DSR Relay Agent application routing rule for provisioning errors.
The currently provisioned Application Routing Rules can be viewed using Main
MenuDiameterConfigurationApplication Routing Rules.
2. Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
138
Alarms and Events
22807 - Unknown Command Code
Event Type: CPA
Description: The CPA application received a Diameter message other than an Accounting message.
The Command Code received in the Diameter message is not an Accounting Message. A DSR Relay
Agent application routing rule is mis-provisioned.
Severity: Info
Instance: N/A
Associated Measurement: RxCpaUnexpected
Recovery:
1. Examine the DSR Relay Agent application routing rule for provisioning errors.
The currently provisioned Application Routing Rules can be viewed using Main
MenuDiameterConfigurationApplication Routing Rules.
2. Contact the Tekelec Customer Care Center for assistance.
22808 - Session Not Found
Event Type: CPA
Description: The CPA queried the SBR and did not get a match for a Session Binding Record based
on the session id. The CPA application expected a Session Binding Record but did not find one. This
condition might indicate that the SBR has timed out the record and deleted it.
Severity: Info
Instance: N/A
Associated Measurement: EvCpaSbrQryNoMatch
Recovery:
Contact the Tekelec Customer Care Center for assistance.
22809 - Undelivered SBR Query
Event Type: CPA
Description: The ComAgent could not deliver the SBR query or no response was received from the
SBR. This event is generated when the ComAgent times out an SBR query because it could not deliver
it or no response was received from the far end.
Severity: Info
Instance: N/A
Associated Measurement: RxCpaUndeliveredMsg
Recovery:
1. Make sure the SBR MPs are not having networking trouble.
910-6528-001 Revision D, December 2012
139
Alarms and Events
2. Contact the Tekelec Customer Care Center for assistance.
22810 - Routing attempt failed due to internal resource exhaustion
Event Type: CPA
Description: An attempt to route a Diameter message through the DRL has failed due to resource
exhaustion.
Severity: Info
Instance: N/A
Associated Measurement: TxCpaRteFailure
Recovery:
1. The MP may be experiencing local congestion.
2. Contact the Tekelec Customer Care Center for assistance.
22811 - CPA Application Event Task Queue Utilization
Event Type: CPA
Description: The CPA Application’s Event Queue Utilization is approaching its maximum capacity.
The DSR Application’s Event Queue (which processes SBR responses that are sent via ComAgent) is
approaching its maximum capacity.
Severity: Minor, Major, Critical
Instance: <DSR Application Name>
HA Score: Normal
Auto Clear Seconds: 0 (zero)
OID: cpaAppEventQueueUtil
Recovery:
1. The alarm log should be examined using Main MenuAlarms & Events.
If no additional congestion alarms are indicated, the CPA Event Task may be experiencing a problem
preventing it from processing messages from its Event Queue.
2. If this problem persists, contact the Tekelec Customer Care Center for assistance.
22812 - Missing AVP
Event Type: CPA
Description: A received Diameter Accounting message does not contain the required Accounting
Record Type or Accounting Record Number AVP.
Severity: Info
Instance: N/A
Associated Measurement: EvCpaMissingAvp
910-6528-001 Revision D, December 2012
140
Alarms and Events
Recovery:
If this problem persists, contact the Tekelec Customer Care Center for assistance.
22813 - Received an error response to an SBR Query
Event Type: CPA
Description: CPA application received an error response in reply to an SBR query. An application
specific error message was received in response to an SBR query.
Severity: Info
Instance: N/A
Associated Measurement: EvCpaSbrQryError
Recovery:
If this problem persists, contact the Tekelec Customer Care Center for assistance.
22814 - HA Sub-Resource Unavailable
Event Type: CPA
Description: An HA Sub-Resource corresponding to a partition of the Session Binding Repository is
unavailable. CPA has received a callback from ComAgent indicating that an HA sub-resource is
unavailable.
Severity: Info
Instance: N/A
Associated Measurement: RxCpaHaSubResourceUnavail
Recovery:
If this problem persists, contact the Tekelec Customer Care Center for assistance.
22815 - Unexpected Session
Event Type: CPA
Description: A Session Binding Record was found when none was expected. CPA received an ACA-Start
and found a Session Binding Record already exists.
Severity: Info
Instance: N/A
Associated Measurement: EvCpaUnexpectedSess
Recovery:
If this problem persists, contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
141
Alarms and Events
22816 - One or more cSBR Subresources Unavailable
Alarm Type: CPA
Description: One or more Charging SBR Subresources are unavailable.
Severity: Based on Subresources unavailable.
• Major - one or more (but not all) cSBR Subresources are unavailable.
• Critical - all cSBR Subresources are unavailable.
Instance: Site Id
HA Score: Normal
Auto Clear Seconds: N/A
OID: cpaSbrSubresourceIsUnavailable
Recovery:
1. Check the state of the SBR MPs.
One or more Charging SBR subresources are unavailable. Make sure the SBR MPs are not having
networking trouble.
2. Contact the Tekelec Customer Care Center for assistance.
22950 - Connection Status Inconsistency Exists
Alarm Type: DIAM
Description: Diameter Connection status inconsistencies exist among the DA-MPs in the DSR signaling
NE.
Severity: Critical
Instance: <MpName> (where inconsistency detected)
OID: eagleXgConnectionStatusInconsistencyNotifv
Recovery:
No action necessary.
Note: DA-MP's SLDB tables are automatically audited and re-synchronized to correct inconsistencies
after a log overrun has occurred.
Tekelec Virtual Operating Environment, TVOE (24400-24499)
This section provides information and recovery procedures for the Tekelec Virtual Operation
Environment (TVOE) alarms, ranging from 24400-24499.
910-6528-001 Revision D, December 2012
142
Alarms and Events
24400 - TVOE libvirtd is down
Alarm Type: TVOE
Description: This alarm indicates that the libvirtd daemon is not running.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.31.1.1.2.1
Recovery:
If the problem persists, contact the Tekelec Customer Care Center.
24401 - TVOE libvirtd is hung
Alarm Type: TVOE
Description: This alarm indicates that we attempted to determine if the libvirtd daemon is not respond
and it didn’t respond.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.31.1.1.2.2
Recovery:
If the problem persists, contact the Tekelec Customer Care Center.
24402 - all TVOE libvirtd connections are in use
Alarm Type: TVOE
Description: This alarm indicates that all twenty connections to libvirtd are in use and more could be
killed.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.31.1.1.2.3
Recovery:
If the problem persists, contact the Tekelec Customer Care Center.
Computer Aided Policy Making, CAPM (25000-25499)
This section provides information and recovery procedures for the Computer-Aided Policy Making
(CAPM) feature (i.e., Diameter Mediation) alarms and events, ranging from 25000 - 25499, and lists
the types of alarms and events that can occur on the system. All events have a severity of Info.
Alarms and events are recorded in a database log table. Currently active alarms can be viewed from
the Launch Alarms Dashboard GUI menu option. The alarms and events log can be viewed from the
Alarms & Events > View History page.
910-6528-001 Revision D, December 2012
143
Alarms and Events
25000 - Rule Template failed to be updated
Event Type: CAPM
Description: The Rule Template failed to update because of syntax errors. The Additional Info of the
Historical alarm includes the name of the Rule Template that failed to be updated.
When the alarm is caused by CAPM Rule Template which contains a syntax error, it may not be raised
immediately after applying the template, but may occur when the first Rule has been provisioned and
committed.
Severity: Minor
Instance: <ruleset> or <ruleset:rule-id>
OID: CAPM_UpdateFailed
Recovery:
1. Check the CAPM Rule Template and verify that the left-hand side term of each condition contains
a valid Linking-AVP or Select expression.
A typical problem can be a non-existing expression, or syntax error of a custom-defined Select
expression. If the CAPM Rule Template contains a syntax error, create a new Rule Template by
copying and modifying the existing one, then deleting the old Rule Template.
2. Verify also that the recently provisioned data of the Rule Template does not contain a syntax error,
i.e., the regular expressions are correct, the fields expecting numbers contain only numbers, etc.
25001 - Action failed within the Rule Template
Event Type: CAPM
Description: When a new Rule Template is created, a failure occurs when performing the action.
Severity: Info
Instance: <ruleset> or <ruleset:rule-id>
OID: CAPM_ActionFailed
Recovery:
Check the reasons the action failed. It may be a lack of system resources to perform an action, or the
action may refer to a part of the message that is not available.
25002 - Stop Rule Template processing after action failure
Event Type: CAPM
Description: When Action Error Handling is set to ‘immediately exit from the rule template’ for the
given Rule Template and a failure occurs when performing the action, processing of the Rule Template
is stopped.
Severity: Info
Instance: <ruleset> or <ruleset:rule-id>
OID: CAPM_Exit_Rule_Template
910-6528-001 Revision D, December 2012
144
Alarms and Events
Recovery:
No action required.
25003 - Exit Trigger point after action failure
Event Type: CAPM
Description: When Action Error Handling is set to ‘immediately exit from the trigger point’ for the
given Rule Template and a failure occurs when performing the action, processing of the Rule Template
is stopped (subsequent templates within the trigger point are also skipped).
Severity: Info
Instance: <ruleset> or <ruleset:rule-id>
OID: CAPM_Exit_Trigger
Recovery:
No action required.
OAM Alarm Management (25500-25899)
This section provides information and recovery procedures related for alarms and events related to
OAM Alarm Management, ranging from 25500 - 25899, that can occur on the system. All events have
a severity of Info.
Alarms and events are recorded in a database log table. Currently active alarms can be viewed from
the Launch Alarms Dashboard GUI menu option. The alarms and events log can be viewed from the
Alarms & Events > View History page.
25500 - No DA-MP Leader Detected Alarm
Alarm Type: DIAM
Description: This alarm occurs when no active DA-MP leaders have been detected.
Severity: Critical
Instance: <NetworkElement>
OID: eagleXgDiameterNoDaMpLeaderDetectedNotify
Recovery:
If the problem persists, contact the Tekelec Customer Care Center for assistance.
25510 - Multiple DA-MP Leader Detected Alarm
Alarm Type: DIAM
Description: This alarm occurs when multiple active DA-MP leaders have been detected.
Severity: Critical
910-6528-001 Revision D, December 2012
145
Alarms and Events
Instance: <NetworkElement>
OID: eagleXgDiameterMultipleDaMpLeadersDetectedNotify
Recovery:
If the problem persists, contact the Tekelec Customer Care Center for assistance.
Platform (31000-32700)
This section provides information and recovery procedures for the Platform alarms, ranging from
31000-32700.
Alarms formatting information
This section of the document provides information to help you understand why an alarm occurred
and to provide a recovery procedure to help correct the condition that caused the alarm.
The information provided about each alarm includes:
•
•
•
•
•
•
Alarm Type: the type of Event that has occurred. For a list of Event types see Alarm and event types.
Description: describes the reason for the Event
Severity: the severity of the alarm
OID: alarm identifier that appears in SNMP traps
Alarm ID: alarm identifier used internally to Tekelec
Recovery: provides any necessary steps for correcting or preventing the alarm
31000 - S/W fault
Alarm Type: SW
Description: Program impaired by s/w fault
Severity: Minor
OID: eagleXgDsrSwFaultNotify
Recovery:
1. Export event history for the given server and the given process.
2. Contact Tekelec Customer Care Center.
31001 - S/W status
Alarm Type: SW
Description: Program status
Severity: Info
OID: eagleXgDsrSWStatusNotify
Recovery:
910-6528-001 Revision D, December 2012
146
Alarms and Events
No action required.
31002 - Process watchdog failure
Alarm Type: SW
Description: Process watchdog timed out
Severity: Minor
OID: eagleXgDsrProcWatchdogFailureNotify
Recovery:
1. Export event history for the given server and the given process.
2. Contact Tekelec Customer Care Center.
31003 - Tab thread watchdog failure
Alarm Type: SW
Description: Tab thread watchdog timed out
Severity: Minor
OID: eagleXgDsrTabThreadWatchdogFailureNotify
Recovery:
1. Export event history for the given server and the given process.
2. Contact Tekelec Customer Care Center.
31100 - Database replication fault
Alarm Type: SW
Description: The Database replication process (inetsync) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbReplicationFaultNotify
Recovery:
1. Export event history for the given server and inetsync task.
2. Contact Tekelec Customer Care Center.
31101 - Database replication to slave failure
Alarm Type: REPL
Description: Database replication to a slave Database has failed
Severity: Critical
OID: eagleXgDsrDbRepToSlaveFailureNotify
910-6528-001 Revision D, December 2012
147
Alarms and Events
Recovery:
1. Check IMI network connectivity between the affected servers.
2. If there are no issues with network connectivity, contact the Tekelec Customer Care Center.
31102 - Database replication from master failure
Alarm Type: REPL
Description: Database replication from a master Database has failed
Severity: Minor
OID: eagleXgDsrDbRepFromMasterFailureNotify
Recovery:
1. Check IMI network connectivity between the affected servers.
2. If there are no issues with network connectivity, contact the Tekelec Customer Care Center.
31103- DB Replication update fault
Alarm Type: REPL
Description: Database replication process cannot apply update to DB
Severity: Minor
OID: eagleXgDsrDbRepUpdateFaultNotify
Recovery:
1. Export event history for the given server and inetsync task.
2. Contact Tekelec Customer Care Center.
31104 - DB Replication latency over threshold
Alarm Type: REPL
Description: Database replication latency has exceeded thresholds
Severity: Minor
OID: eagleXgDsrDbRepLatencyNotify
Recovery:
1. If this alarm is raised occasionally for short time periods (a couple of minutes or less), it may indicate
network congestion or spikes of traffic pushing servers beyond their capacity. Consider
re-engineering network capacity or subscriber provisioning.
2. If this alarm does not clear after a couple of minutes, contact Tekelec Customer Care Center.
31105 - Database merge fault
Alarm Type: SW
910-6528-001 Revision D, December 2012
148
Alarms and Events
Description: The database merge process (inetmerge) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbMergeFaultNotify
Recovery:
1. Export event history for the given server and inetmerge task.
2. Contact Tekelec Customer Care Center.
31106 - Database merge to parent failure
Alarm Type: COLL
Description: Database merging to the parent Merge Node has failed
Severity: Minor
OIL: eagleXgDsrDbMergeToParentFailureNotify
Recovery:
1. Check IMI network connectivity between the affected servers.
2. If there are no issues with network connectivity, contact the Tekelec Customer Care Center.
31107 - Database merge from child failure
Alarm Type: COLL
Description: Database merging from a child Source Node has failed
Severity: Major
OID: eagleXgDsrDbMergeFromChildFailureNotify
Recovery:
1. Check IMI network connectivity between the affected servers.
2. If there are no issues with network connectivity, contact the Tekelec Customer Care Center.
31108 - Database merge latency over threshold
Alarm Type: COLL
Description: Database Merge latency has exceeded thresholds
Severity: Minor
OID: eagleXgDsrDbMergeLatencyNotify
Recovery:
1. If this alarm is raised occasionally for short time periods (a couple of minutes or less), it may indicate
network congestion or spikes of traffic pushing servers beyond their capacity. Consider
re-engineering network capacity or subscriber provisioning.
2. If this alarm does not clear after a couple of minutes, contact Tekelec Customer Care Center
910-6528-001 Revision D, December 2012
149
Alarms and Events
31109 - Topology config error
Alarm Type: DB
Description: Topology is configured incorrectly
Severity: Minor
OID: eagleXgDsrTopErrorNotify
Recovery:
1. This alarm may occur during initial installation and configuration of a server. No action is necessary
at that time.
2. If this alarm occurs after successful initial installation and configuration of a server, contact the
Tekelec Customer Care Center.
31110 - Database audit fault
Alarm Type: SW
Description: The Database service process (idbsvc) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbAuditFaultNotify
Recovery:
1. Export event history for the given server and idbsvc task.
2. Contact Tekelec Customer Care Center.
31111 - Database merge audit in progress
Alarm Type: COLL
Description: Database Merge Audit between mate nodes in progress
Severity: Minor
OID: eagleXgDsrDbMergeAuditNotify
Recovery:
No action required.
31112 - Stateful db synchronization from mate server
Alarm Type: REPL
Description: Stateful database is not yet synchronized with mate database.
Severity: Minor
OID: eagleXgDsrDbRepUpLogTransTimeoutNotify
Recovery:
910-6528-001 Revision D, December 2012
150
Alarms and Events
No action required. Contact Tekelec Customer Care Center if this occurs frequently.
31113 - DB replication manually disabled
Alarm Type: REPL
Description: DB Replication Manually Disabled
Severity: Minor
OID: eagleXgDsrDbReplicationManuallyDisabledNotify
Recovery:
No action required.
31114 - DB replication over SOAP has failed
Alarm Type: REPL
Description: Database replication of configuration data via SOAP has failed
Severity: Minor
OID: eagleXgDsrDbReplicationSoapFaultNotify
Recovery:
1. Check IMI network connectivity between the affected servers.
2. If there are no issues with network connectivity, contact the Tekelec Customer Care Center.
31115 - Database service fault
Alarm Type: SW
Description: The Database service process (idbsvc) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbServiceFaultNotify
Recovery:
1. Export event history for the given server and idbsvc task.
2. Contact Tekelec Customer Care Center.
31116 - Excessive shared memory
Alarm Type: MEM
Description: The amount of shared memory consumed exceeds configured thresholds
Severity: Major
OID: eagleXgDsrExcessiveSharedMemoryConsumptionNotify
Recovery:
910-6528-001 Revision D, December 2012
151
Alarms and Events
Contact Tekelec Customer Care Center.
31117 - Low disk free
Alarm Type: DISK
Description: The amount of free disk is below configured thresholds
Severity: Major
OID: eagleXgDsrLowDiskFreeNotify
Recovery:
1. Remove unnecessary or temporary files from partitions.
2. If there are no files known to be unneeded, contact Tekelec Customer Care Center.
31118 - Database disk store fault
Alarm Type: DISK
Description: Writing the database to disk failed
Severity: Minor
OID: eagleXgDsrDbDiskStoreFaultNotify
Recovery:
1. Remove unnecessary or temporary files from partitions.
2. If there are no files known to be unneeded, contact Tekelec Customer Care Center.
31119 - Database updatelog overrun
Alarm Type: DB
Description: The Database update log was overrun increasing risk of data loss
Severity: Minor
OID: eagleXgDsrDbUpdateLogOverrunNotify
Recovery:
Contact Tekelec Customer Care Center.
31120 - Database updatelog write fault
Alarm Type: DB
Description: A Database change cannot be stored in the updatelog
Severity: Minor
OID: eagleXgDsrDbUpdateLogWriteFaultNotify
Recovery:
910-6528-001 Revision D, December 2012
152
Alarms and Events
Contact Tekelec Customer Care Center.
31121 - Low disk free early warning
Alarm Type: DISK
Description: The amount of free disk is below configured early warning thresholds
Severity: Minor
OID: eagleXgDsrLowDiskFreeEarlyWarningNotify
Recovery:
1. Remove unnecessary or temporary files from partitions that are greater than 80% full.
2. If there are no files known to be unneeded, contact Tekelec Customer Care Center.
31122 - Excessive shared memory early warning
Alarm Type: MEM
Description: The amount of shared memory consumed exceeds configured early warning thresholds
Severity: Minor
OID: eagleXgDsrExcessiveSharedMemoryConsumptionEarlyWarningNotify
Recovery:
Contact Tekelec Customer Care Center.
31123 - Database replication audit command complete
Alarm Type: REPL
Description: A DB replication audit command completed
Severity: Info
OID: eagleXgDsrDbRepAuditCmdCompleteNotify
Recovery:
No action required.
31124 - Database replication audit command error
Alarm Type: REPL
Description: A DB replication audit command detected errors
Severity: Minor
OID: eagleXgDsrDbRepAuditCmdErrorNotify
Recovery:
Contact Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
153
Alarms and Events
31125 - Database durability degraded
Alarm Type: REPL
Description: Database durability has dropped below configured durability level
Severity: Major
OID: eagleXgDsrDbDurabilityDegradedNotify
Recovery:
1. Check configuration of all servers, and check for connectivity problems between server IMI
addresses.
2. If the problem persists, contact Tekelec Customer Care Center.
31126- Audit blocked
Alarm Type: SW
Description: Site Audit Controls blocked an inter-site replication audit due to the number in progress
per configuration.
Severity: Major
OID: eagleXgDsrAuditBlockedNotify
Recovery:
Contact Tekelec Customer Care Center.
31130 - Network health warning
Alarm Type: NET
Description: Network health issue detected
Severity: Minor
OID: eagleXgDsrNetworkHealthWarningNotify
Recovery:
1. Check configuration of all servers, and check for connectivity problems between server IMI
addresses.
2. If the problem persists, contact Tekelec Customer Care Center.
31140 - Database perl fault
Alarm Type: SW
Description: Perl interface to Database is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbPerlFaultNotify
910-6528-001 Revision D, December 2012
154
Alarms and Events
Recovery:
Contact Tekelec Customer Care Center.
31145 - Database SQL fault
Alarm Type: SW
Description: SQL interface to Database is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbSQLFaultNotify
Recovery:
1. Export event history for the given server, and Imysqld task.
2. Contact Tekelec Customer Care Center.
31146- DB mastership fault
Alarm Type: SW
Description: DB replication is impaired due to no mastering process (inetrep/inetrep).
Severity: Major
OID: eagleXgDsrDbMastershipFaultNotify
Recovery:
1. Export event history for the given server.
2. Contact Tekelec Customer Care Center.
31147- DB upsynclog overrun
Alarm Type: SW
Description: UpSyncLog is not big enough for (WAN) replication.
Severity: Minor
OID: eagleXgDsrDbUpSyncLogOverrunNotify
Recovery:
Contact Tekelec Customer Care Center.
31200 - Process management fault
Alarm Type: SW
Description: The process manager (procmgr) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrProcMgmtFaultNotify
910-6528-001 Revision D, December 2012
155
Alarms and Events
Recovery:
1. Export event history for the given server, all processes.
2. Contact Tekelec Customer Care Center.
31201 - Process not running
Alarm Type: PROC
Description: A managed process cannot be started or has unexpectedly terminated
Severity: Major
OID: eagleXgDsrProcNotRunningNotify
Recovery:
Contact Tekelec Customer Care Center.
31202 - Unkillable zombie process
Alarm Type: PROC
Description: A zombie process exists that cannot be killed by procmgr. procmgr will no longer manage
this process.
Severity: Major
OID: eagleXgDsrProcZombieProcess
Recovery:
1. If the process does not exit, it may be necessary to reboot the server to eliminate the zombie process.
2. Contact Tekelec Customer Care Center.
31206 - Process mgmt monitoring fault
Alarm Type: SW
Description: The process manager monitor (pm.watchdog) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrProcMgmtMonFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31207 - Process resource monitoring fault
Alarm Type: SW
Description: The process resource monitor (ProcWatch) is impaired by a s/w fault
Severity: Minor
910-6528-001 Revision D, December 2012
156
Alarms and Events
OID: eagleXgDsrProcResourceMonFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31208 - IP port server fault
Alarm Type: SW
Description: The run environment port mapper (re.portmap) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrPortServerFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31209 - Hostname lookup failed
Alarm Type: SW
Description: Unable to resolve a hostname specified in the NodeInfo table
Severity: Minor
OID: eagleXgDsrHostLookupFailedNotify
Recovery:
1. This typically indicate a DNS Lookup failure. Verify all server hostnames are correct in the GUI
configuration on the server generating the alarm.
2. If the problem persists, contact Tekelec Customer Care Center.
31213 - Process scheduler fault
Alarm Type: SW
Description: The process scheduler (ProcSched/runat) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrProcSchedulerFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31214 - Scheduled process fault
Alarm Type: PROC
Description: A scheduled process cannot be executed or abnormally terminated
Severity: Minor
910-6528-001 Revision D, December 2012
157
Alarms and Events
OID: eagleXgDsrScheduleProcessFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31215 - Process resources exceeded
Alarm Type: SW
Description: A process is consuming excessive system resources
Severity: Minor
OID: eagleXgDsrProcResourcesExceededFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31216 - SysMetric configuration error
Alarm Type: SW
Description: A SysMetric Configuration table contains invalid data
Severity: Minor
OID: eagleXgDsrSysMetricConfigErrorNotify
Recovery:
Contact Tekelec Customer Care Center.
31220 - HA configuration monitor fault
Alarm Type: SW
Description: The HA configuration monitor is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrHaCfgMonitorFaultNotify
Recovery:
Contact Tekelec Customer Care Center.
31221 - HA alarm monitor fault
Alarm Type: SW
Description: The high availability alarm monitor is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrHaAlarmMonitorFaultNotify
910-6528-001 Revision D, December 2012
158
Alarms and Events
Recovery:
Contact Tekelec Customer Care Center.
31222 - HA not configured
Alarm Type: HA
Description: High availability is disabled due to system configuration
Severity: Minor
OID: eagleXgDsrHaNotConfiguredNotify
Recovery:
Contact Tekelec Customer Care Center.
31223 - HA Heartbeat transmit failure
Alarm Type: HA
Description: The high availability monitor failed to send heartbeat
Severity: Major
OID: eagleXgDsrHaHbTransmitFailureNotify
Recovery:
1. This alarm clears automatically when the server successfully registers for HA heartbeating.
2. If this alarm does not clear after a couple minutes, contact Tekelec Customer Care Center.
31224 - HA configuration error
Alarm Type: HA
Description: High availability configuration error
Severity: Major
OID: eagleXgDsrHaCfgErrorNotify
Recovery:
Contact the Tekelec Customer Care Center.
31225 - HA service start failure
Alarm Type: HA
Description: The high availability service failed to start
Severity: Major
OID: eagleXgDsrHaSvcStartFailureNotify
Recovery:
910-6528-001 Revision D, December 2012
159
Alarms and Events
1. This alarm clears automatically when the HA daemon is successfully started.
2. If this alarm does not clear after a couple minutes, contact Tekelec Customer Care Center.
31226 - HA availability status degraded
Alarm Type: HA
Description: The high availability status is degraded due to raised alarms
Severity: Major
OID: eagleXgDsrHaAvailDegradedNotify
Recovery:
1. View alarms dashboard for other active alarms on this server.
2. Follow corrective actions for each individual alarm on the server to clear them.
3. If the problem persists, contact Tekelec Customer Care Center.
31227 - HA availability status failed
Alarm Type: HA
Description: The high availability status is failed due to raised alarms
Severity: Critical
OID: eagleXgDsrHaAvailFailedNotify
Recovery:
1. View alarms dashboard for other active alarms on this server.
2. Follow corrective actions for each individual alarm on the server to clear them.
3. If the problem persists, contact Tekelec Customer Care Center.
31228 - HA standby offline
Alarm Type: HA
Description: High availability standby server is offline
Severity: Major
OID: eagleXgDsrHaStandbyOfflineNotify
Recovery:
1. If loss of communication between the active and standby servers is caused intentionally by
maintenance activity, alarm can be ignored; it clears automatically when communication is restored
between the two servers.
2. If communication fails at any other time, look for network connectivity issues and/or contact
Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
160
Alarms and Events
31229 - HA score changed
Alarm Type: HA
Description: High availability health score changed
Severity: Info
OID: eagleXgDsrHaScoreChangeNotify
Recovery:
Status message - no action required.
31230 - Recent alarm processing fault
Alarm Type: SW
Description: The recent alarm event manager (raclerk) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrRecAlarmEvProcFaultNotify
Recovery:
1. Export event history for the given server and raclerk task.
2. Contact Tekelec Customer Care Center.
31231 - Platform alarm agent fault
Alarm Type: SW
Description: The platform alarm agent impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrPlatAlarmAgentNotify
Recovery:
Contact Tekelec Customer Care Center.
31232- Late heartbeat warning
Alarm Type: SW
Description: No HA heartbeat received from standby server.
Severity: Minor
OID: eagleXgDsrHaLateHeartbeatWarningNotify
Recovery:
No action required; this is a warning and can be due to transient conditions. If there continues to
be no heartbeat from the server, alarm 31228 occurs.
910-6528-001 Revision D, December 2012
161
Alarms and Events
31240 - Measurements collection fault
Alarm Type: SW
Description: The measurments collector (statclerk) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrMeasCollectorFaultNotify
Recovery:
1. Export event history for the given server and statclerk task.
2. Contact Tekelec Customer Care Center.
31250 - RE port mapping fault
Alarm Type: SW
Description: The IP service port mapper (re.portmap) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrRePortMappingFaultNotify
Recovery:
This typically indicate a DNS Lookup failure. Verify all server hostnames are correct in the GUI
configuration on the server generating the alarm.
31260 - Database SNMP Agent
Alarm Type: SW
Description: The Database SNMP agent (snmpIdbAgent) is impaired by a s/w fault
Severity: Minor
OID: eagleXgDsrDbSnmpAgentNotify
Recovery:
1. Export event history for the given server and all processes.
2. Contact Tekelec Customer Care Center.
31270 - Logging output
Alarm Type: SW
Description: Logging output set to Above Normal
Severity: Minor
OID: eagleXgDsrLoggingOutputNotify
Recovery:
910-6528-001 Revision D, December 2012
162
Alarms and Events
Extra diagnostic logs are being collected, potentially degrading system performance. Contact
Tekelec Customer Care Center.
31280 - HA Active to Standby transition
Alarm Type: HA
Description: HA active to standby activity transition
Severity: Info
OID: eagleXgDsrActiveToStandbyTransNotify
Recovery:
1. If this alarm occurs during routine maintenance activity, it may be ignored.
2. Otherwise, contact Tekelec Customer Care Center.
31281 - HA Standby to Active transition
Alarm Type: HA
Description: HA standby to active activity transition
Severity: Info
OID: eagleXgDsrStandbyToActiveTransNotify
Recovery:
1. If this alarm occurs during routine maintenance activity, it may be ignored.
2. Otherwise, contact Tekelec Customer Care Center.
32113 - Uncorrectable ECC memory error
Alarm Type: TPD
Description: This alarm indicates that chipset has detected an uncorrectable (multiple-bit) memory
error that the ECC (Error-Correcting Code) circuitry in the memory is unable to correct.
Severity: Critical
OID: 1.3.6.1.4.1.323.5.3.18.3.1.1.14
Recovery
Contact the Tekelec Customer Care Center to request hardware replacement.
32114 - SNMP get failure
Alarm Type: TPD
Description: The server failed to receive SNMP information from the switch.
Severity: Critical
OID: 1.3.6.1.4.1.323.5.3.18.3.1.1.15
910-6528-001 Revision D, December 2012
163
Alarms and Events
Within this trap is one bind variable, the OID of which is 1.3.6.1.2.1.1.5 <sysname>, where <sysname>
is the name of the switch where the failure occurred.
Recovery
1. Use the following command to verify the switch is active: ping switch1A/B (this requires
command line access).
2. If the problem persists, contact the Tekelec Customer Care Center.
32300 – Server fan failure
Alarm Type: TPD
Description: This alarm indicates that a fan on the application server is either failing or has failed
completely. In either case, there is a danger of component failure due to overheating.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.1
Recovery
Contact the Tekelec Customer Care Center.
32301 - Server internal disk error
Alarm Type: TPD
Description: This alarm indicates the server is experiencing issues replicating data to one or more of
its mirrored disk drives. This could indicate that one of the server’s disks has either failed or is
approaching failure.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.2
Recovery
Contact the Tekelec Customer Care Center.
32302 – Server RAID disk error
Alarm Type: TPD
Description: This alarm indicates that the offboard storage server had a problem with its hardware
disks.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.3
Recovery
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
164
Alarms and Events
32303 - Server Platform error
Alarm Type: TPD
Description: This alarm indicates an error such as a corrupt system configuration or missing files.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.4
Recovery
32304 - Server file system error
Alarm Type: TPD
Description: This alarm indicates unsuccessful writing to at least one of the server’s file systems.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.5
Recovery
Contact the Tekelec Customer Care Center.
32305 - Server Platform process error
Alarm Type: TPD
Description: This alarm indicates that either the minimum number of instances for a required process
are not currently running or too many instances of a required process are running.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.6
Recovery
Contact the Tekelec Customer Care Center.
32307 - Server swap space shortage failure
Alarm Type: TPD
Description: This alarm indicates that the server’s swap space is in danger of being depleted. This is
usually caused by a process that has allocated a very large amount of memory over time.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.8
Recovery
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
165
Alarms and Events
32308 - Server provisioning network error
Alarm Type: TPD
Description: This alarm indicates that the connection between the server’s ethernet interface and the
customer network is not functioning properly.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.9
Recovery
1. Verify that a customer-supplied cable labeled TO CUSTOMER NETWORK is securely connected
to the appropriate server. Follow the cable to its connection point on the local network and verify
this connection is also secure.
2. Test the customer-supplied cable labeled TO CUSTOMER NETWORK with an Ethernet Line Tester.
If the cable does not test positive, replace it.
3. Have your network administrator verify that the network is functioning properly.
4. If no other nodes on the local network are experiencing problems and the fault has been isolated
to the server or the network administrator is unable to determine the exact origin of the problem,
contact the Tekelec Customer Care Center.
32312 - Server disk space shortage error
Alarm Type: TPD
Description: This alarm indicates that one of the following conditions has occurred:
• A filesystem has exceeded a failure threshold, which means that more than 90% of the available
disk storage has been used on the filesystem.
• More than 90% of the total number of available files have been allocated on the filesystem.
• A filesystem has a different number of blocks than it had when installed.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.13
Recovery
Contact the Tekelec Customer Care Center.
32313 - Server default route network error
Alarm Type: TPD
Description: This alarm indicates that the default network route of the server is experiencing a problem.
CAUTION: When changing the network routing configuration of the server, verify that
the modifications will not impact the method of connectivity for the current login session.
The route information must be entered correctly and set to the correct values. Incorrectly
modifying the routing configuration of the server may result in total loss of remote network
access.
910-6528-001 Revision D, December 2012
166
Alarms and Events
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.14
Recovery
Contact the Tekelec Customer Care Center.
32314 - Server temperature error
Alarm Type: TPD
Description: The internal temperature within the server is unacceptably high.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.15
Recovery
1. Ensure that nothing is blocking the fan's intake. Remove any blockage.
2. Verify that the temperature in the room is normal. If it is too hot, lower the temperature in the room
to an acceptable level.
Note: Be prepared to wait the appropriate period of time before continuing with the next step.
Conditions need to be below alarm thresholds consistently for the alarm to clear. It may take about
ten minutes after the room returns to an acceptable temperature before the alarm cleared.
3. If the problem has not been resolved, contact the Tekelec Customer Care Center.
32315 – Server mainboard voltage error
Alarm Type: TPD
Description: This alarm indicates that one or more of the monitored voltages on the server mainboard
have been detected to be out of the normal expected operating range.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.16
Recovery
Contact the Tekelec Customer Care Center.
32316 – Server power feed error
Alarm Type: TPD
Description: This alarm indicates that one of the power feeds to the server has failed. If this alarm
occurs in conjunction with any Breaker Panel alarm, there might be a problem with the breaker panel.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.17
Recovery
910-6528-001 Revision D, December 2012
167
Alarms and Events
1. Verify that all the server power feed cables to the server that is reporting the error are securely
connected.
2. Check to see if the alarm has cleared
• If the alarm has been cleared, the problem is resolved.
• If the alarm has not been cleared, continue with the next step.
3. Follow the power feed to its connection on the power source. Ensure that the power source is ON
and that the power feed is properly secured.
4. Check to see if the alarm has cleared
• If the alarm has been cleared, the problem is resolved.
• If the alarm has not been cleared, continue with the next step.
5. If the power source is functioning properly and the wires are all secure, have an electrician check
the voltage on the power feed.
6. Check to see if the alarm has cleared
• If the alarm has been cleared, the problem is resolved.
• If the alarm has not been cleared, continue with the next step.
7. If the problem has not been resolved, contact the Tekelec Customer Care Center.
32317 - Server disk health test error
Alarm Type: TPD
Description: Either the hard drive has failed or failure is imminent.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.18
Recovery
1. Perform the recovery procedures for the other alarms that accompany this alarm.
2. If the problem has not been resolved, contact the Tekelec Customer Care Center.
32318 - Server disk unavailable error
Alarm Type: TPD
Description: The smartd service is not able to read the disk status because the disk has other problems
that are reported by other alarms. This alarm appears only while a server is booting.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.19
Recovery
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
168
Alarms and Events
32319 – Device error
Alarm Type: TPD
This alarm indicates that the offboard storage server had a problem with its disk volume filling up.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.20
Recovery
Contact the Tekelec Customer Care Center.
32320 – Device interface error
Alarm Type: TPD
Description: This alarm indicates that the IP bond is either not configured or down.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.21
Recovery
Contact the Tekelec Customer Care Center.
32321 – Correctable ECC memory error
Alarm Type: TPD
Description: This alarm indicates that chipset has detected a correctable (single-bit) memory error that
has been corrected by the ECC (Error-Correcting Code) circuitry in the memory.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.22
Recovery
No recovery necessary. If the condition persists, contact the Tekelec Customer Care Center to request
hardware replacement.
32322 – Power Supply A error
Alarm Type: TPD
Description: This alarm indicates that power supply 1 (feed A) has failed.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.23
Recovery
1. Verify that nothing is obstructing the airflow to the fans of the power supply.
910-6528-001 Revision D, December 2012
169
Alarms and Events
2. If the problem persists, contact the Tekelec Customer Care Center.
32323 – Power Supply B error
Alarm Type: TPD
Description: This alarm indicates that power supply 2 (feed B) has failed.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.24
Recovery
1. Verify that nothing is obstructing the airflow to the fans of the power supply.
2. If the problem persists, contact the Tekelec Customer Care Center.
32324 – Breaker panel feed error
Alarm Type: TPD
Description: This alarm indicates that the server is not receiving information from the breaker panel
relays.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.25
Recovery
1. Verify that the same alarm is displayed by multiple servers:
• If this alarm is displayed by only one server, the problem is most likely to be with the cable or
the server itself. Look for other alarms that indicate a problem with the server and perform the
recovery procedures for those alarms first.
• If this alarm is displayed by multiple servers, go to the next step.
2. Verify that the cables that connect the servers to the breaker panel are not damaged and are securely
fastened to both the Alarm Interface ports on the breaker panel and to the serial ports on both
servers.
3. If the problem has not been resolved, call the Tekelec Customer Care Center to request that the
breaker panel be replaced.
32325 – Breaker panel breaker error
Alarm Type: TPD
Description: This alarm indicates that a power fault has been identified by the breaker panel. The
LEDs on the center of the breaker panel (see Figure 4: Breaker Panel LEDs) identify whether the fault
occurred on the input power or the output power, as follows:
• A power fault on input power (power from site source to the breaker panel) is indicated by one of
the LEDs in the PWR BUS A or PWR BUS B group illuminated Red. In general, a fault in the input
power means that power has been lost to the input power circuit.
910-6528-001 Revision D, December 2012
170
Alarms and Events
Note: LEDs in the PWR BUS A or PWR BUS B group that correspond to unused feeds are not
illuminated; LEDs in these groups that are not illuminated do not indicate problems.
• A power fault on output power (power from the breaker panel to other frame equipment) is
indicated by either BRK FAIL BUS A or BRK FAIL BUS B illuminated RED. This type of fault can
be caused by a surge or some sort of power degradation or spike that causes one of the circuit
breakers to trip.
Figure 4: Breaker Panel LEDs
Description: This alarm indicates that a power fault has been identified by the breaker panel.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.26
Recovery
1. Verify that the same alarm is displayed by multiple servers both servers (the single breaker panel
normally sends alarm information to both servers):
• If this alarm is displayed by only one server, the problem is most likely to be with the cable or
the server itself. Look for other alarms that indicate a problem with the server and perform the
recovery procedures for those alarms first.
• If this alarm is displayed by both servers multiple servers, go to the next step.
2. Look at the breaker panel assignments in Figure 5: Breaker Panel Setting. For each breaker assignment,
and verify that the corresponding LED in the PWR BUS A group and the PWR BUS B group is
illuminated Green.
910-6528-001 Revision D, December 2012
171
Alarms and Events
Figure 5: Breaker Panel Setting
If one of the LEDs in the PWR BUS A group or the PWR BUS B group is illuminated Red, a problem
has been detected with the corresponding input power feed. Contact the Tekelec Customer Care
Center
a) Verify that the customer provided source for the affected power feed is operational. If the power
source is properly functioning, have an electrician remove the plastic cover from the rear of the
breaker panel and verify the power source is indeed connected to the input power feed connector
on the rear of the breaker panel. Correct any issues found.
b) Check the LEDs in the PWR BUS A group and the PWR BUS B group again.
• If the LEDs are now illuminated Green, the issue has been resolved.
• Proceed to Substep c to verify that the alarm has been cleared.
• If the LEDs are still illuminated Red, continue to the next sub-step.
c) Have the electrician verify the integrity of the input power feed. The input voltage should
measure nominally -48VDC (that is, between -41VDC and -60VDC). If the supplied voltage is
not within the acceptable range, the input power source must be repaired or replaced.
Note: Be sure the voltmeter is connected properly. The locations of the BAT and RTN connections
are in mirror image on either side of the breaker panel.
If the measured voltage is within the acceptable range, the breaker panel may be malfunctioning.
The breaker panel must be replaced.
d) Check the LEDs in the PWR BUS A group and the PWR BUS B group again after the necessary
actions have been taken to correct any issues found.
• If the LEDs are now illuminated Green, the issue has been resolved. Proceed to Step 3 to
verify that the alarm has been cleared.
• If the LEDs are still illuminated Red, skip to Step 4
3. Check the BRK FAIL LEDs for BUS A and for BUS B.
• If one of the BRK FAIL LEDs is illuminated Red, then one or more of the respective Input
Breakers has tripped. (A tripped breaker is indicated by the toggle located in the center position.)
Perform the following steps to repair this issue:
a) For all tripped breakers, move the breaker down to the open (OFF) position and then back up
to the closed (ON) position.
b) After all the tripped breakers have been reset, check the BRK FAIL LEDs again. If one of the
BRK FAIL LEDs is still illuminated Red, contact the Tekelec Customer Care Center
910-6528-001 Revision D, December 2012
172
Alarms and Events
• If all of the BRK FAIL LEDs and all the LEDs in the PWR BUS A group and the PWR BUS B
group are illuminated Green, continue with the next step.
• If all of the BRK FAIL LEDs and all the LEDs in the PWR BUS A group and the PWR BUS B
group are illuminated Green, there is most likely a problem with the serial connection between
the server and the breaker panel. This connection is used by the system health check to monitor
the breaker panel for failures. Verify that both ends of the labeled serial cables are properly
secured. If any issues are discovered with these cable connections, make the necessary corrections
and continue to the next step to verify that the alarm has been cleared, otherwise contact the
Tekelec Customer Care Center
4. Check to see if the alarm has cleared.
• If the alarm has been cleared, the problem is resolved.
• If the alarm has not been cleared, continue with the next step.
5. If the problem has not been resolved, contact the Tekelec Customer Care Center
32326 – Breaker panel monitoring error
Alarm Type: TPD
Description: This alarm indicates a failure in the hardware and/or software that monitors the breaker
panel. This could mean there is a problem with the file I/O libraries, the serial device drivers, or the
serial hardware itself.
Note: When this alarm occurs, the system is unable to monitor the breaker panel for faults. Thus, if
this alarm is detected, it is imperative that the breaker panel be carefully examined for the existence
of faults. The LEDs on the breaker panel will be the only indication of the occurrence of either alarm
• 32324-Breaker Panel Feed Error or
• 32325-Breaker Panel Breaker Error
until the Breaker Panel Monitoring Error has been corrected.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.27
Recovery
1. Verify that the same alarm is displayed by multiple servers:
• If this alarm is displayed by only one server, the problem is most likely to be with the cable or
the server itself. Look for other alarms that indicate a problem with the server and perform the
recovery procedures for those alarms first.
• If this alarm is displayed by multiple servers, go to the next step.
2. Verify that both ends of the labeled serial cables are secured properly (for locations of serial cables,
see the appropriate hardware manual).
3. If the alarm has not been cleared, contact the Tekelec Customer Care Center.
32327 – Server HA Keepalive error
Alarm Type: TPD
910-6528-001 Revision D, December 2012
173
Alarms and Events
Description: This alarm indicates that heartbeat process has detected that it has failed to receive a
heartbeat packet within the timeout period.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.28
Recovery
1. Determine if the mate server is currently down and bring it up if possible.
2. Determine if the keepalive interface is down.
3. Determine if heartbeart is running (service TKLCha status).
Note: This step may require command line ability.
4. Contact the Tekelec Customer Care Center.
32331 – HP disk problem
Alarm Type: TPD
Description: This major alarm indicates that there is an issue with either a physical or logical disk in
the HP disk subsystem. The message will include the drive type, location, slot and status of the drive
that has the error.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.32
Recovery
Contact the Tekelec Customer Care Center.
32332 – HP Smart Array controller problem
Alarm Type: TPD
Description: This major alarm indicates that there is an issue with an HP disk controller. The message
will include the slot location, the component on the controller that has failed, and status of the controller
that has the error.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.33
Recovery
Contact the Tekelec Customer Care Center.
32333 – HP hpacucliStatus utility problem
Alarm Type: TPD
Description: This major alarm indicates that there is an issue with the process that caches the HP disk
subsystem status. This usually means that the hpacucliStatus daemon is either not running, or hung.
Severity: Major
910-6528-001 Revision D, December 2012
174
Alarms and Events
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.34
Recovery
Contact the Tekelec Customer Care Center.
32334 - Multipath device access link problem
Alarm Type: TPD
Description: One or more "access paths" of a multipath device are failing or are not healthy, or the
multipath device does not exist.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.35
Recovery
Contact the Tekelec Customer Care Center.
32335 - Switch link down error
Alarm Type: TPD
Description: The link is down.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.36
Within this trap are two bind variables, the OIDs of which are:
• 1.3.6.1.2.1.1.5 <sysname>, where <sysname> is the name of the switch where the failure occurred.
• 1.3.6.1.2.1.2.2.1.1 <link index>, where <link index> is the index of the failed link.
Recovery
1. Verify the cabling between the port and the remote side.
2. Verify networking on the remote end.
3. If the problem persists, contact the Tekelec Customer Care Center who should verify port settings
on both the server and the switch.
32336– Half Open TCP Socket Limit
Alarm Type: TPD
This alarm indicates that the number of half open TCP sockets has reached the major threshold. This
problem is caused by a remote system failing to complete the TCP 3-way handshake.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.37
Recovery
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
175
Alarms and Events
32403 – PM&C backup failed
Alarm Type: PM&C
The PM&C application has a failure that needs to be investigated.
Severity: Major
OID: 1.3.6.1.4.1.323.5.3.17.4.2.4
1. Attempt a manual backup using the PM&C GUI.
2. If the problems persists, contact the Tekelec Customer Care Center.
32500 – Server disk space shortage warning
Alarm Type: TPD
Description: This alarm indicates that one of the following conditions has occurred:
• A file system has exceeded a warning threshold, which means that more than 80% (but less than
90%) of the available disk storage has been used on the file system.
• More than 80% (but less than 90%) of the total number of available files have been allocated on the
file system.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.1
Recovery
Contact the Tekelec Customer Care Center.
32501 – Server application process error
Alarm Type: TPD
Description: This alarm indicates that either the minimum number of instances for a required process
are not currently running or too many instances of a required process are running.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.2
Recovery
Contact the Tekelec Customer Care Center.
32502 – Server hardware configuration error
Alarm Type: TPD
Description: This alarm indicates that one or more of the server’s hardware components are not in
compliance with Tekelec specifications (refer to the appropriate hardware manual).
Severity: Minor
910-6528-001 Revision D, December 2012
176
Alarms and Events
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.3
Recovery
Contact the Tekelec Customer Care Center.
32503 – Server RAM shortage warning
Alarm Type: TPD
Description: This alarm is generated by the MPS syscheck software package and is not part of the TPD
distribution.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.4
Recovery
Contact the Tekelec Customer Care Center.
32505 – Server swap space shortage warning
Alarm Type: TPD
Description: This alarm indicates that the swap space available on the server is less than expected.
This is usually caused by a process that has allocated a very large amount of memory over time.
Note: For this alarm to clear, the underlying failure condition must be consistently undetected for a
number of polling intervals. Therefore, the alarm may continue to be reported for several minutes
after corrective actions are completed.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.6
Recovery
Contact the Tekelec Customer Care Center.
32506 – Server default router not defined
Alarm Type: TPD
Description: This alarm indicates that the default network route is either not configured or the current
configuration contains an invalid IP address or hostname.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.7
Recovery
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
177
Alarms and Events
32507 – Server temperature warning
Alarm Type: TPD
Description: This alarm indicates that the internal temperature within the server is outside of the
normal operating range. A server Fan Failure may also exist along with the Server Temperature
Warning.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.8
Recovery
1. Ensure that nothing is blocking the fan's intake. Remove any blockage.
2. Verify that the temperature in the room is normal. If it is too hot, lower the temperature in the room
to an acceptable level.
Note: Be prepared to wait the appropriate period of time before continuing with the next step.
Conditions need to be below alarm thresholds consistently for the alarm to clear. It may take about
ten minutes after the room returns to an acceptable temperature before the alarm cleared.
3. Replace the filter (refer to the appropriate hardware manual).
Note: Be prepared to wait the appropriate period of time before continuing with the next step.
Conditions need to be below alarm thresholds consistently for the alarm to clear. It may take about
ten minutes after the filter is replaced before the alarm cleared.
4. If the problem has not been resolved, contact the Tekelec Customer Care Center.
32508 – Server core file detected
Alarm Type: TPD
Description: This alarm indicates that an application process has failed and debug information is
available.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.9
Recovery
Contact the Tekelec Customer Care Center.
32509 – Server NTP Daemon not synchronized
Alarm Type: TPD
Description: This alarm indicates that the NTP daemon (background process) has been unable to locate
a server to provide an acceptable time reference for synchronization.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.10
Recovery
910-6528-001 Revision D, December 2012
178
Alarms and Events
Contact the Tekelec Customer Care Center.
32510 – CMOS battery voltage low
Alarm Type: TPD
Description: The presence of this alarm indicates that the CMOS battery voltage has been detected to
be below the expected value. This alarm is an early warning indicator of CMOS battery end-of-life
failure which will cause problems in the event the server is powered off.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.11
Recovery
Contact the Tekelec Customer Care Center.
32511 – Server disk self test warning
Alarm Type: TPD
Description: A non-fatal disk issue (such as a sector cannot be read) exists.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.12
Recovery
Contact the Tekelec Customer Care Center.
32512 – Device warning
Alarm Type: TPD
Description: This alarm indicates that either we are unable to perform an snmpget command on the
configured SNMP OID or the value returned failed the specified comparison operation.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.13
Recovery
Contact the Tekelec Customer Care Center.
32513 – Device interface warning
Alarm Type: TPD
Description: This alarm can be generated by either an SNMP trap or an IP bond error.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.14
Recovery
910-6528-001 Revision D, December 2012
179
Alarms and Events
Contact the Tekelec Customer Care Center.
32514 – Server reboot watchdog initiated
Alarm Type: TPD
Description: This alarm indicates that the hardware watchdog was not strobed by the software and
so the server rebooted the server. This applies to only the last reboot and is only supported on a T1100
application server.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.15
Recovery
Contact the Tekelec Customer Care Center.
32515 – Server HA failover inhibited
Alarm Type: TPD
Description: This alarm indicates that the server has been inhibited and therefore HA failover is
prevented from occurring.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.16
Recovery
Contact the Tekelec Customer Care Center.
32516 – Server HA Active to Standby transition
Alarm Type: TPD
Description: This alarm indicates that the server is in the process of transitioning HA state from Active
to Standby.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.17
Recovery
Contact the Tekelec Customer Care Center.
32517 – Server HA Standby to Active transition
Alarm Type: TPD
Description: This alarm indicates that the server is in the process of transitioning HA state from Standby
to Active.
Severity: Minor
910-6528-001 Revision D, December 2012
180
Alarms and Events
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.18
Recovery
Contact the Tekelec Customer Care Center.
32518 – Platform Health Check failure
Alarm Type: TPD
Description: This alarm is used to indicate a configuration error.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.19
Recovery
Contact the Tekelec Customer Care Center.
32519 – NTP Offset Check failure
Alarm Type: TPD
Description: This minor alarm indicates that time on the server is outside the acceptable range (or
offset) from the NTP server. The Alarm message will provide the offset value of the server from the
NTP server and the offset limit that the application has set for the system.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.20
Recovery
Contact the Tekelec Customer Care Center.
32520 – NTP Stratum Check failure
Alarm Type: TPD
Description: This alarm indicates that NTP is syncing to a server, but the stratum level of the NTP
server is outside of the acceptable limit. The Alarm message will provide the stratum value of the NTP
server and the stratum limit that the application has set for the system.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.21
Recovery
Contact the Tekelec Customer Care Center.
32521 – SAS Presence Sensor Missing
Alarm Type: TPD
Description: This alarm indicates that the T1200 server drive sensor is not working.
910-6528-001 Revision D, December 2012
181
Alarms and Events
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.22
Recovery
Contact the Tekelec Customer Care Center to get a replacement server.
32522 – SAS Drive Missing
Alarm Type: TPD
Description: This alarm indicates that the number of drives configured for this server is not being
detected.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.23
Recovery
Contact the Tekelec Customer Care Center to determine whether the issue is with a failed drive or
failed configuration.
32523 – DRBD failover busy
Alarm Type: TPD
Description: This alarm indicates that a DRBD sync is in progress from the peer server to the local
server. The local server is not ready to act as the primary DRBD node, since it’s data is not up to date.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.24
Recovery
A DRBD sync should not take more than 15 minutes to complete. Please wait for approximately
20 minutes, and then check if the DRBD sync has completed. If the alarm persists longer than this
time period, contact the Tekelec Customer Care Center.
32524 – HP disk resync
Alarm Type: TPD
Description: This minor alarm indicates that the HP disk subsystem is currently resynchronizing after
a failed or replaced drive, or some other change in the configuration of the HP disk subsystem. The
output of the message will include the disk that is resynchronizing and the percentage complete. This
alarm should eventually clear once the resync of the disk is completed. The time it takes for this is
dependant on the size of the disk and the amount of activity on the system.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.25
Recovery
Contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
182
Alarms and Events
32525 – Telco Fan Warning
Alarm Type: TPD
Description: This alarm indicates that the Telco switch has detected an issue with an internal fan.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.26
Recovery
1. Contact the Tekelec Customer Care Center to get a replacement switch. Verify the ambient air
temperature around the switch is as low as possible until the switch is replaced.
2. Tekelec Customer Care Center personnel can perform an snmpget command or log into the switch
to get detailed fan status information.
32526 – Telco Temperature Warning
Alarm Type: TPD
Description: This alarm indicates that the Telco switch has detected the internal temperature has
exceeded the threshold.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.27
Recovery
1. Lower the ambient air temperature around the switch as low as possible.
2. If problem persists, contact the Tekelec Customer Care Center.
32527 – Telco Power Supply Warning
Alarm Type: TPD
Description: This alarm indicates that the Telco switch has detected that one of the duplicate power
supplies has failed.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.28
Recovery
1. Verify breaker wasn't tripped.
2. If breaker is still good and problem persists, contact the Tekelec Customer Care Center who can
perform a snmpget command or log into the switch to determine which power supply is failing.
If the power supply is bad, the switch must be replaced.
32528 – Invalid BIOS value
Alarm Type: TPD
910-6528-001 Revision D, December 2012
183
Alarms and Events
Description: This alarm indicates that the HP server has detected that one of the setting for either the
embedded serial port or the virtual serial port is incorrect.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.29
Recovery
Contact the Tekelec Customer Care Center.
32529– Server Kernel Dump File Detected
Alarm Type: TPD
Description: This alarm indicates that the kernel has crashed and debug information is available.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.30
Recovery
Contact the Tekelec Customer Care Center.
32530– TPD Upgrade Failed
Alarm Type: TPD
Description: This alarm indicates that a TPD upgrade has failed.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.31
Recovery
Contact the Tekelec Customer Care Center.
32531– Half Open Socket Warning Limit
Alarm Type: TPD
This alarm indicates that the number of half open TCP sockets has reached the major threshold. This
problem is caused by a remote system failing to complete the TCP 3-way handshake.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.32
Recovery
Contact the Tekelec Customer Care Center.
32532– Server Upgrade Pending Accept/Reject
Alarm Type: TPD
910-6528-001 Revision D, December 2012
184
Alarms and Events
This alarm indicates that an upgrade occurred but has not been accepted or rejected yet.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.18.3.1.3.33
Recovery
Follow the steps in the application's upgrade procedure for accepting or rejecting the upgrade.
32603 – PM&C backup to remote server failed
Alarm Type: PM&C
The PMAC application has a failure that needs to be investigated.
Severity: Minor
OID: 1.3.6.1.4.1.323.5.3.17.4.3.4
1.
2.
3.
4.
Verify that the remote server is operational.
Verify that the primary PMAC can ping the remote server.
Attempt a manual backup to remote server using the PMAC GUI.
If the problems persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
185
Chapter
4
Key Performance Indicators (KPIs)
Topics:
•
•
•
•
•
•
•
•
•
•
•
•
General KPIs information.....187
KPIs server elements .....189
Computer Aided Policy Making (CAPM)
KPIs.....190
Charging Proxy Application (CPA) KPIs.....190
Communication Agent (ComAgent) KPIs.....191
Connection Maintenance KPIs.....191
Diameter (DIAM) KPIs.....191
IP Front End (IPFE) KPIs.....192
Message Processor (MP) KPIs.....192
Full Address Based Resolution (FABR) KPIs...193
Range Based Address Resolution (RBAR)
KPIs.....193
Session Binding Repository (SBR) KPIs.....194
910-6528-001 Revision D, December 2012
This section provides general information about
KPIs, and lists the KPIs that can appear on the Status
& Manage KPIs GUI page.
186
Key Performance Indicators (KPIs)
General KPIs information
This section provides general information about KPIs and the Status and Manage KPI page, and how
to view KPIs.
KPIs overview
Key Performance Indicators (KPIs) allow the user to monitor system performance data, including
CPU, memory, swap space, and uptime per server. This performance data is collected from all servers
within the defined topology.
The KPI display function resides on all OAM servers. Servers that provide a GUI connection rely on
KPI information merged to that server. The Network OAMP servers maintain status information for
all servers in the topology. System OAM servers have reliable information only for servers within the
same network element.
The Status and Manage KPIs page displays performance data for the entire system. KPI data for the
entire system is updated every 60 seconds. If data is not currently being collected for a particular
server, the KPI for that server will be shown as Unk for "Unknown".
KPIs
The Status & Manage > KPIs page displays KPIs for the entire system. KPIs for the server and its
applications are displayed on separate tabs. The application KPIs displayed may vary according to
whether you are logged in to an NOAMP server or an SOAM server.
Viewing KPIs
Use this procedure to view KPI data.
1. Select Status & Manage > KPIs.
The Status & Manage KPIs page appears with the Server tab displayed. For details about the KPIs
displayed on this page, see the application documentation.
2. Click to select an application tab to see KPI data relevant to the application.
Note: The application KPIs displayed may vary according to whether you are logged in to an
NOAMP server or an SOAM server. Collection of KPI data is handled solely by NOAMP servers
in systems that do not support SOAMs.
KPIs data export elements
This table describes the elements on the KPIs Export page.
Table 11: Schedule KPI Data Export Elements
Element
Task Name
Description
Name of the scheduled task
910-6528-001 Revision D, December 2012
Data Input Notes
Format: Textbox
187
Key Performance Indicators (KPIs)
Element
Description
Data Input Notes
Range: Maximum length is 24
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Task Name must begin and end
with an alphanumeric character.
Description
Description of the scheduled task
Format: Textbox
Range: Maximum length is 255
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Description must begin with an
alphanumeric character.
Export Frequency
Frequency at which the export
occurs
Format: Radio button
Range: Hourly, Once, Weekly,
or Daily
Default: Once
Minute
If hourly is selected for Upload
Format: Scrolling list
Frequency, this is the minute of
each hour when the data will be Range: 0 to 59
written to the export directory.
Time of Day
Time of day the export occurs
Format: Time textbox
Range: 15-minute increments
Default: 12:00 AM
Day of Week
Day of week on which the export
Format: Radio button
occurs
Range: Sunday, Monday,
Tuesday, Wednesday, Thursday,
Friday, or Saturday
Default: Sunday
Exporting KPIs
You can schedule periodic exports of security log data from the KPIs page. KPI data can be exported
immediately, or you can schedule exports to occur daily or weekly. If filtering has been applied in the
KPIs page, only filtered data is exported.
During data export, the system automatically creates a CSV file of the filtered data. The file will be
available in the file management area until you manually delete it, or until the file is transfered to an
alternate location using the Export Server feature. For more information about using Export Server,
see Export Server.
Use this procedure to schedule a data export task.
910-6528-001 Revision D, December 2012
188
Key Performance Indicators (KPIs)
1. Select Status & Manage > KPIs.
The KPIs page appears.
2. If necessary, specify filter criteria and click Go.
The KPIs are displayed according to the specified criteria.
3. Click Export.
The Schedule KPI Data Export page appears.
4. Enter the Task Name.
For more information about Task Name, or any field on this page, see KPIs data export elements .
5. Select the Export Frequency.
6. If you selected Hourly, specify the Minutes.
7. Select the Time of Day.
Note: Time of Day is not an option if Export Frequency equals Once.
8. Select the Day of Week.
Note: Day of Week is not an option if Export Frequency equals Once.
9. Click OK or Apply to initiate the KPI export task.
From the Status & Manage > Files page, you can view a list of files available for download, including
the file you exported during this procedure. For more information, see Displaying the file list.
Scheduled tasks can be viewed, edited, and deleted, and reports of scheduled tasks can be generated
from Status & Manage > Tasks. For more information see:
•
•
•
•
Viewing scheduled tasks
Editing a scheduled task
Deleting a scheduled task
Generating a scheduled task report
KPIs server elements
This table describes KPIs that appear regardless of server role.
Table 12: KPIs Server Elements
KPIs Status Element
Description
Network Element
The network element name (set up on the
Configuration > Network Elements page)
associated with each Server Hostname.
Server Hostname
The server hostname set up on the Configuration
> Servers page. All servers in the system are listed
here.
Server Indicators:
910-6528-001 Revision D, December 2012
189
Key Performance Indicators (KPIs)
KPIs Status Element
Description
CPU
Percentage utilization of all processors on the
server by all software as measured by the
operating system.
RAM
Percentage utilization of physical memory on the
server by all software as measured by TPD.
Swap
Percentage utilization of swap space on the server
by all software as measured by TPD.
Uptime
The total amount of time the server has been
running.
Computer Aided Policy Making (CAPM) KPIs
Table 13: CAPM KPIs
Variable
Description
Processing time [ms]
Average processing time of Rule Template on a
per Rule Template basis.
Active Templates
Number of Rule Templates that are in Active state.
Test Templates
Number of Rule Templates that are in Test state.
Development Templates
Number of Rule Templates that are in
Development state.
Charging Proxy Application (CPA) KPIs
The KPI values associated with CPA are visible using Main MenuStatus & ManageKPI Display.
Table 14: Charging Proxy Application (CPA) KPIs
Variable
Description
CPA Answer Message Rate
Track the average number of Answer messages
processed per second by the CPA application.
CPA Ingress Message Rate
Track the average number of Diameter messages
received per second by the CPA application.
CPA Request Message Rate
Track the average number of Request messages
processed per second by the CPA application.
910-6528-001 Revision D, December 2012
190
Key Performance Indicators (KPIs)
Variable
Description
cSBR Query Error Rate
Track the average number of errors received per
second by the CPA application when attempting
to query (read, create, update, delete) SBR.
cSBR Query Rate
Track the average number of SBR Queries sent
per second by the CPA application.
Communication Agent (ComAgent) KPIs
Table 15: Communication Agent KPIs
Variable
User Data Ingress message rate
Description
Average of User Data Ingress Message Rate
(messages per second) utilization on a MP server.
The Ingress Message Rate is the number of User
Data StackEvents (messages) that ComAgent
delivers to Application Layers Queue.
Connection Maintenance KPIs
Table 16: Connection Maintenance KPIs
Variable
RxConnAvgMPS
Description
Exponentially smoothed average rate in MPS on
the connection. Note: This measurement will be
sampled periodically and reported in the
Connections Maintenance GUI as a type of KPI.
Diameter (DIAM) KPIs
Table 17: DIAM KPIs
Variable
Description
Ingress Trans Success Rate
Percentage of ingress peer-to-peer transactions
successfully complete
MsgCopyTxQueueUtilization
Percentage of utilization of the Message Copy Tx
Queue
910-6528-001 Revision D, December 2012
191
Key Performance Indicators (KPIs)
Variable
Description
Avg Rsp Time
Average time from when routing receives a
Request message from a downstream peer to the
time that an Answer response is sent to that
downstream peer
Routing Success Rate
Percentage of transactions successfully routed on
first attempt
IP Front End (IPFE) KPIs
The KPI values associated with IPFE are visible using Main MenuStatus & ManageKPI Display.
Table 18: IPFE KPIs
Variable
Description
CPU %
Total CPU used by the IPFE process
Memory Total
Absolute memory used by the IPFE process
Memory %
Percent memory used by the IPFE process
Mem. Heap
Total heap allocated by the IPFE process
IPFE Packets/Sec
The average number of packets per second the
IPFE receives
IPFE MBytes/Sec
The average number of megabytes per second the
IPFE receives
Message Processor (MP) KPIs
Table 19: MP KPIs
Variable
Description
Avg Diameter Process CPU Util
Average percent Diameter Process CPU utilization
(0-100%) on a MP server.
Avg IMR Offered
Average Ingress Offered message rate (messages
per second) on a MP server . Offered message rate
is number of ingress Diameter messages before
any Ingress controls are applied.
Avg IMR Accepted
Average Ingress Accepted message rate (messages
per second) on a MP server . Accepted message
910-6528-001 Revision D, December 2012
192
Key Performance Indicators (KPIs)
Variable
Description
rate is number of routable messages accepted by
MP after all Ingress controls are applied.
Avg Messsage Processing Load
Average message processing load (messages per
second) on a MP server. The message processing
load is the number of Diameter messages that are
routed , including Reroutes and Msgcop.
Full Address Based Resolution (FABR) KPIs
Table 20: FABR KPIs
Variable
Description
Ingress Message Rate
Ingress Message Rate (messages per second)
utilization on a MP server for the FABR
Application. The Ingress Message Rate is the
number of ingress Diameter messages that were
successfully received by the FABR Application.
Resolved Message Rate
Resolved Message Rate (messages per second)
utilization on a MP server. The Resolved Message
Rate is the number of ingress Diameter messages
that are successfully resolved to a Destination by
the FABR application.
DP Response Time Average
Average DP response time is the average time (in
milliseconds) it takes to receive a DP response
after sending the corresponding DP query.
Range Based Address Resolution (RBAR) KPIs
Table 21: RBAR KPIs
Variable
Description
Avg Resolved Message Rate
Average Resolved Message Rate (messages per
second) utilization on a MP server. The Resolved
Message Rate is the number of ingress Diameter
messages that are successfully resolved to a
Destination by the Range Based Address
Resolution application.
Ingress Message Rate
Average Ingress Message Rate (messages per
second) utilization on a MP server for this DSR
910-6528-001 Revision D, December 2012
193
Key Performance Indicators (KPIs)
Variable
Description
Application. The Ingress Message Rate is the
number of ingress Diameter messages that were
successfully received by the DSR Application.
Session Binding Repository (SBR) KPIs
The KPI values associated with SBR are visible using Main MenuStatus & ManageKPI Display.
Table 22: SBR KPIs
Variable
Description
Current session bindings
Current number of session bindings. Active SBRs
will show a number; standby SBRs will not.
Stale session binds since audit
The expected stale session bindings scheduled for
deletion
Session binding capacity
Percentage of total session bindings
Congestion rate
Percentage of queue length utilization
Service time
Average lifetime of a transaction in microseconds.
The lifetime of a transaction is calculated by taking
the difference between the time a request message
is created by the CPA and the time at which the
SBR sends a response to that message.
Request rate
Number of requests sent to the SBR from the CPA
per second
910-6528-001 Revision D, December 2012
194
Chapter
5
Measurements
Topics:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
General measurements information.....197
Application Routing Rules measurements.....201
Computer Aided Policy Making (CAPM)
measurements.....203
Communication Agent (ComAgent) Performance
measurements.....205
Communication Agent (ComAgent) Exception
measurements.....219
Connection Congestion measurements.....242
Connection Exception measurements.....247
Connection Performance measurements.....252
Diameter Signaling Router (DSR) Application
Exception measurements.....264
Diameter Signaling Router (DSR) Application
Performance measurements.....269
Diameter Egress Transaction measurements....281
Diameter Exception measurements.....285
Diameter Ingress Transaction Exception
measurements.....304
Diameter Ingress Transaction Performance
measurements.....317
Diameter Performance measurements.....322
Diameter Rerouting measurements.....343
Message Priority measurements.....346
Message Processor (MP) Performance
measurements.....350
OAM Alarm measurements.....366
OAM System measurements.....366
Peer Node Performance measurements.....368
Peer Routing Rules measurements.....370
Charging Proxy Application (CPA) Performance
measurements.....373
910-6528-001 Revision D, December 2012
This section provides general information about
measurements (including measurement procedures),
and lists the measurements that display on
measurement reports.
195
Measurements
•
•
•
•
•
•
•
•
•
•
•
•
•
Charging Proxy Application (CPA) Exception
measurements.....379
Charging Proxy Application (CPA) Session DB
measurements.....385
Message Copy measurements.....390
IP Front End (IPFE) Exception
measurements.....397
IP Front End (IPFE) Performance
measurements.....399
Full Address Based Resolution (FABR) Application
Performance measurements.....405
Full Address Based Resolution (FABR) Application
Exception measurements.....413
Range Based Address Resolution (RBAR)
Application Performance measurements.....418
Range Based Address Resolution (RBAR)
Application Exception measurements.....426
Route List measurements.....433
Routing Usage measurements.....436
Session Binding Repository (SBR) Exception
measurements.....438
Session Binding Repository (SBR) Performance
measurements.....441
910-6528-001 Revision D, December 2012
196
Measurements
General measurements information
This section provides general information about measurements, measurement-related GUI elements,
and measurement report procedures.
Measurements
This section provides an overview of the options on the Measurements page. All components of the
system measure the amount and type of messages sent and received. Measurement data collected
from all components of the system can be used for multiple purposes, including discerning traffic
patterns and user behavior, traffic modeling, size traffic sensitive resources, and troubleshooting. This
section provides an overview of measurements, describes how to generate and export a measurements
report, and provides a list of register types.
The measurements framework allows applications to define, update, and produce reports for various
measurements.
• Measurements are ordinary counters that count occurrences of different events within the system,
for example, the number of messages received. Measurement counters are also called pegs.
Additional measurement types provided by the Platform framework are not used in this release.
• Applications simply peg (increment) measurements upon the occurrence of the event that needs
to be measured.
• Measurements are collected and merged at the SOAM and NOAM servers as appropriate.
• The GUI allows reports to be generated from measurements.
Measurements that are being pegged locally are collected from shared memory and stored in a
disk-backed database table every 5 minutes on all servers in the network. Measurements are collected
every 5 minutes on a 5 minute boundary, i.e. at HH:00, HH:05, HH:10, HH:15, and so on. The collection
frequency is set to 5 minutes to minimize the loss of measurement data in case of a server failure, and
also to minimize the impact of measurements collection on system performance.
All servers in the network (NOAMP, SOAM, and MP servers) store a minimum of 8 hours of local
measurements data. More than 5 minutes of local measurements data is retained on each server to
minimize loss of measurements data in case of a network connection failure to the server merging
measurements.
Measurements data older than the required retention period are deleted by the measurements
framework.
Measurements are reported in groups. A measurements report group is a collection of measurement
IDs. Each measurement report contains one measurement group. A measurement can be assigned to
one or more existing or new measurement groups so that it is included in a measurement report.
Assigning a measurement ID to a report group ensures that when you select a report group the same
set of measurements is always included in the measurements report.
Note: Measurements from a server may be missing in a report if the server is down; the server is in
overload; something in the Platform merging framework is not working; or the report is generated
before data is available from the last collection period (there is a 25 to 30 second lag time in availability).
Measurement elements
This table describes the elements on the Measurements Report page.
910-6528-001 Revision D, December 2012
197
Measurements
Table 23: Measurements Elements
Element
Scope
Description
Data Input Notes
Network Elements or Server
Format: Pulldown list
Groups for which the
measurements report can be run. Range: Network Elements in the
topology; Server Groups in the
Note: If the report is generated
topology
from an SOAM network element,
the scope filter will not be
Note: If no selection is made, the
displayed, and the selected scope default scope is Entire Network.
will be that specific SOAM
Default: Entire Network
network element.
Note: Measurements for SOAM
network elements are not
available in systems that do not
support SOAMs.
Report
A selection of reports
Format: Pulldown list
Range: Varies depending on
application
Default: Group
Interval
The increments by which data
can be measured
Format: Pulldown list
Range: Day, Fifteen Minute, Five
Minute, Half Hour, Hour
Default: N/A
Time Range
The interval of time for which
the data is being reported,
beginning or ending on a
specified date.
Format: Pulldown list
Range: Days, Hours, Minutes,
Seconds
Interval Reference Point: Ending,
Beginning
Default: Days
Generating a measurements report
Use this procedure to generate and view a measurements report.
1. Select Measurements > Report .
The Measurements Report page appears.
2. Select the Scope.
For details about this field, or any field on the Measurements Report page, see Measurement elements
.
910-6528-001 Revision D, December 2012
198
Measurements
3.
4.
5.
6.
7.
8.
Select the Report.
Select the Interval.
Select the Time Range.
Select Beginning or Ending as the Time Range interval reference point.
Select the Beginning or Ending date.
Click Go.
The report is generated.
Note: Data for the selected scope is displayed in the primary report page. Data for any available
sub-scopes are displayed in tabs. For example, if the selected scope is Entire Network, report data
for the entire network appears in the primary report page. The individual network entities within
the entire network are considered sub-scopes.
9. To view report data for a specific sub-scope, click on the tab for that sub-scope.
The report data appears.
Measurements data export elements
This table describes the elements on the Measurements Report Export page.
Table 24: Schedule Measurement Data Export Elements
Element
Task Name
Description
Name of the scheduled task
Data Input Notes
Format: Textbox
Range: Maximum length is 24
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Task Name must begin and end
with an alphanumeric character.
Description
Description of the scheduled task
Format: Textbox
Range: Maximum length is 255
characters; alphanumeric (a-z,
A-Z, and 0-9) and minus sign (-).
Description must begin with an
alphanumeric character.
Export Frequency
Frequency at which the export
occurs
Format: Radio button
Range: Once, Weekly, or Daily
Default: Once
Minute
If hourly is selected for Upload
Format: Scrolling list
Frequency, this is the minute of
each hour when the data will be Range: 0 to 59
written to the export directory.
910-6528-001 Revision D, December 2012
199
Measurements
Element
Time of Day
Description
Time of day the export occurs
Data Input Notes
Format: Time textbox
Range: 15-minute increments
Default: 12:00 AM
Day of Week
Day of week on which the export
Format: Radio button
occurs
Range: Sunday, Monday,
Tuesday, Wednesday, Thursday,
Friday, or Saturday
Default: Sunday
Exporting measurements reports
You can schedule periodic exports of data from the Measurements Report page. Measurements data
can be exported immediately, or you can schedule exports to occur daily or weekly. If filtering has
been applied on the Measurements Report page, only filtered data is exported.
During data export, the system automatically creates a CSV file of the filtered data. The file will be
available in the file management area until you manually delete it, or until the file is transfered to an
alternate location using the Export Server feature. For more information about using Export Server,
see Export Server.
Use this procedure to save a measurements report to the file management storage area. Use this
procedure to schedule a data export task.
1. Select Measurements > Report.
The Measurements Report page appears. For a description of each field, see Measurement elements
.
2. Generate a measurements report.
For information about how to generate a measurements report, see Generating a measurements report.
3. Click to select the scope or sub-scope measurement report that you want to export.
4. Click Export.
The measurement report is exported to a CSV file. Click the link at the top of the page to go directly
to the Status & Manage > Files page. From the Status & Manage > Files page, you can view a list
of files available for download, including the measurements report you exported during this
procedure. The Schedule Measurement Log Data Export page appears.
5. Enter the Task Name.
For more information about Task Name, or any field on this page, see Measurements data export
elements .
6. Select the Export Frequency.
7. If you selected Hourly, specify the Minutes.
8. Select the Time of Day.
Note: Time of Day is not an option if Export Frequency equals Once.
910-6528-001 Revision D, December 2012
200
Measurements
9. Select the Day of Week.
Note: Day of Week is not an option if Export Frequency equals Once.
10. Click OK or Apply to initiate the data export task.
The data export task is scheduled. From the Status & Manage > Files page, you can view a list of
files available for download, including the file you exported during this proceduree. For more
information, see Displaying the file list.
Scheduled tasks can be viewed, edited, and deleted, and reports of scheduled tasks can be generated
from Status & Manage > Tasks. For more information see:
•
•
•
•
Viewing scheduled tasks
Editing a scheduled task
Deleting a scheduled task
Generating a scheduled task report
Application Routing Rules measurements
The Application Routing Rules measurement group is a set of measurements associated with the usage
of Application Routing Rules. These measurements will allow the user to determine which Application
Routing Rules are most commonly used and the percentage of times that messages were successfully
(or unsuccessfully) routed.
Table 25: Application Routing Rule Measurements
Measurement Tag
Description
Collection Interval
RxApplRuleSelected
Number of times that an
Application Routing Rule was
selected to route a Request
message
5 min
RxApplRuleFwdFailAll
Number of times that an
Application Routing Rule was
selected to route a Request
message but the message was
not successfully routed (all
reasons)
5 min
RxApplRuleFwdFailUnavail
Number of times that an
5 min
Application Routing Rule was
selected to route a Request
message but the message was
not successfully routed because
the DSR Application’s
Operational Status was
Unavailable
910-6528-001 Revision D, December 2012
201
Measurements
Measurement Tag
Description
Collection Interval
RxApplRuleDuplicatePriority
Number of times that the
5 min
application routing rule was
selected for routing a message
but another application routing
rule had the same priority and
was ignored.
RxApplRuleSelected
Measurement Group:Application Routing Rules
Measurement Type: Simple
Description: Number of times that the application routing rule was selected for routing a Request
message.
Collection Interval: 5 min
Peg Condition: When DRL selects an application routing rule for routing a message.
Measurement Scope: Server Group
Recovery:
No action required.
RxApplRuleFwdFailAll
Measurement Group:Application Routing Rules
Measurement Type: Simple
Description: Number of times that the application routing rule was selected for routing a Request
message and the message was not successfully routed for any reason.
Collection Interval: 5 min
Peg Condition: When DRL selects an application routing rule to route a Request message and one of
the following conditions is met:
• The DSR Application’s Operational Status is “Unavailable”.
• The DSR Application’s Operational Status is not “Unavailable” but the attempt to enqueue the
message to the DSR Application failed.
Measurement Scope: Server Group
Recovery:
No action required.
RxApplRuleFwdFailUnavail
Measurement Group:Application Routing Rules
910-6528-001 Revision D, December 2012
202
Measurements
Measurement Type: Simple
Description: Number of times that the application routing rule was selected for routing a Request
message and the message was not successfully routed because DSR Application’s Operational Status
was “Unavailable”.
Collection Interval: 5 min
Peg Condition: When DRL selects an application routing rule to route a Request message and the DSR
Application’s Operational Status is “Unavailable”.
Measurement Scope: Server Group
Recovery:
No action required.
RxApplRuleDuplicatePriority
Measurement Group: Peer Routing Rules
Measurement Type: Simple
Description: Number of times that the application routing rule was selected for routing a message but
another application routing rule had the same priority and was ignored.
Collection Interval: 5 min
Peg Condition: When DRL searches the ART and finds more than one highest priority application
routing rule with the same priority that matches the search criteria. The measurement is associated
with the application routing rule that is selected for routing.
Measurement Scope: Server Group
Recovery:
Use GUI screen: Main Menu -> Diameter -> Configuration -> Application Routing Rules to
modify peer routing rule priorities.
At least two application routing rules with the same priority matched an ingress Request message.
The system selected the first application routing rule found. Application routing rules must be
unique for the same type of messages to avoid unexpected routing results.
Computer Aided Policy Making (CAPM) measurements
The Computer-Aided Policy Making (CAPM) measurement report contains usage-based measurements
related to the Diameter Mediation feature.
CAPM_Temp_Invoked
Measurement Group: CAPM
Measurement Type: Simple
910-6528-001 Revision D, December 2012
203
Measurements
Description: Indicates the number of times a Rule Template has been invoked. This counter is
incremented on a per Rule Template basis every time the Rule Template is processed.
Collection Interval: 5 min
Peg Condition: A Rule Template is invoked during the message processing.
Measurement Scope: Server Group
Recovery:
1. Verify that the Rule Template was set to Test or Active state; was assigned to the correct Execution
Trigger; the conditions of the Rule Template were properly set; and the provisioned routing or/and
mediation data matches the incoming message.
2. Also verify that alarm 25000 (Rule Template failed to be updated) is not raised.
CAPM_CondSet_True
Measurement Group: CAPM
Measurement Type: Simple
Description: Indicates the number of times a condition set has been evaluated to True. This counter
is incremented on a per Rule Template basis every time all the conditions of the condition set match.
Collection Interval: 5 min
Peg Condition: A Condition Set matches during the message processing.
Measurement Scope: Server Group
Recovery:
1. Verify that the Rule Template was set to Test or Active state; was assigned to the correct Execution
Trigger; the conditions of the Rule Template were properly set; and the provisioned routing or/and
mediation data matches the incoming message.
2. Also verify that the alarm 25000 (Rule Template failed to be updated) is not raised.
CAPM_Action_Set_Fails
Measurement Group: CAPM
Measurement Type: Simple
Description: Indicates the number of times a failure has occurred while executing the action set. This
counter is incremented on a per Rule Template basis every time some of the actions fails.
Note: This counter is incremented only once even if several actions within an action set have failed.
Collection Interval: 5 min
Peg Condition: At least one action within an Action Set has failed.
Measurement Scope: Server Group
Recovery:
Verify that the actions are set correctly; there are enough system resources to perform the actions; and
the actions refer to the part of incoming message that is available.
910-6528-001 Revision D, December 2012
204
Measurements
Communication Agent (ComAgent) Performance measurements
The "Communication Agent Performance" measurement group is a set of measurements that provide
performance information that is specific to the Communication Agent protocol. These measurements
will allow the user to determine how many messages are successfully forwarded and received to and
from each DSR Application.
Table 26: Communication Agent Performance Measurement Report Fields
Measurement Tag
Description
Collection Interval
CAAvgDataFIFOQueueUtil
Average percentage of
ComAgent DataFIFO Queue
Utilization
30 min
CAAvgMxFIFOQueueUtil
Average percentage of
ComAgent MxFIFO Queue
Utilization
30 min
CAAvgRsrcPoolUtil
Average percentage of internal
resource pool utilization
30 min
CAAvgRxStackEvents
Average Number of User Data
ingress events received.
30 min
CAAvgTxStackEvents
Average Number of User Data
egress events received from
stacks to deliver it to remote.
30 min
CAAvgQueueUtil
Average percentage of Queue
Utilization.
30 min
CADSTx
Number of User Data egress
30 min
events specifically for the default
Direct Service.
CAHSTxRsrc
Number of egress stack events
that were routed to a known
Resource.
30 min
CAHSTxRsrcRateAvg
Average rate per second of
egress stack events routed to a
known Resource.
30 min
CAHSTxRsrcRateMax
Maximum rate per second of
egress stack events routed to a
known Resource
30 min
CAPeakDataFIF0QueueUtil
Maximum percentage of
ComAgent DataFIFO Queue
Utilization
30 min
910-6528-001 Revision D, December 2012
205
Measurements
Measurement Tag
Description
Collection Interval
CAPeakMxFIFOQueueUtil
Maximum percentage of
ComAgent MxFIFO Queue
Utilization
30 min
CAPeakQueueUtil
Maximum percentage of Queue 30 min
Utilization.
CAPeakRsrcPoolUtil
Maximum percentage of internal 30min
resource pool utilization
CAPeakRxStackEvents
Maximum Number of User Data 30 min
ingress events received.
CAPeakTxStackEvents
Maximum Number of User Data 30 min
egress events received from
stacks to deliver it to remote.
CARSTx
Number of stack events
submitted to a Routed Service
for routing.
30 min
CARx
Number of User Data ingress
events received from a peer
server.
30 min
CARxSuccess
Number of User Data ingress
events successfully routed to
local layers.
30 min
CATransEndAbnormRateAvg
Average rate per second that
30 min
ComAgent transactions ended
abnormally during the collection
interval.
CATransEndAbnormRateMax
Maximum rate per second that 30 min
ComAgent transactions ended
abnormally during the collection
interval.
CATransEndNorm
Number of reliable transactions 30 min
initiated by local User Layers
that ended normally with a
response from a destination
server.
CATransPendingAvg
Average number of allocated
30 min
pending transaction records over
the collection interval.
CATransPendingMax
Maximum number of allocated
pending transaction records.
30 min
CATransRateAvg
Average rate per second that
ComAgent transactions were
30 min
910-6528-001 Revision D, December 2012
206
Measurements
Measurement Tag
Description
Collection Interval
started during the collection
interval.
CATransRateMax
Maximum rate per second that
ComAgent transactions were
started during the collection
interval.
30 min
CATransEndAbnorm
Number of reliable transactions 30 min
that terminated abnormally.
CATransStarted
Number of reliable transactions 30 min
initiated by local User Layers.
CATransTimeAvg
Average transaction life-time in 30 min
milliseconds.
CATransTimeMax
Maximum transaction life-time
in milliseconds.
30 min
CATx
Number of User Data egress
events received on
Communication Agent task
queue from local stacks to
deliver it to a peer server.
30 min
CATxSuccess
Number of User Data egress
30 min
events successfully delivered to
a peer server.
CAAvgDataFIFOQueueUtil
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average percentage of ComAgent DataFIFO Queue Utilization.
Collection Interval: 30 min
Peg Condition: The average ComAgent connection DataFIFO Queue utilization sample taken during
the collection interval.
Measurement Scope: NE, Server
Recovery:
1. This measurement is primarily intended to assist in evaluating any issues with ComAgent User
Data StackEvent processing and thread scheduling.
If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the queue depth may need to be tuned.
If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
910-6528-001 Revision D, December 2012
207
Measurements
2. Contact the Tekelec Customer Care Center for assistance.
CAAvgMxFIFOQueueUtil
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average percentage of ComAgent MxFIFO Queue Utilization.
Collection Interval: 30 min
Peg Condition: The average ComAgent connection MxFIFO Queue utilization sample taken during
the collection interval.
Measurement Scope: NE, Server
Recovery:
1. This measurement is primarily intended to assist in evaluating any issues with internal StackEvent
processing and thread scheduling.
If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the queue depth may need to be tuned.
If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
2. Contact the Tekelec Customer Care Center for assistance.
CAAvgQueueUtil
Measurement Group: ComAgent Exception
Measurement Type: Average
Description: Average percentage of Queue Utilization.
Collection Interval: 30 min
Peg Condition: The average ComAgent Egress Task Queue utilization sample taken during the collection
interval.
Measurement Scope: NE, Server
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
208
Measurements
CAAvgRsrcPoolUtil
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Average percentage of internal resource pool utilization.
Collection Interval: 30 min
Peg Condition: This is to track the measure of average usage of the internal resource (Ex: CommMessage
Resource pool) for a given interval.
Measurement Scope: NE, Server
Recovery:
This measurement is primarily intended to assist in evaluating the need for additional processing
or performance capacity tuning on a node.
If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of a node over several collection
intervals, then the internal engineering resource pool capacity or other dependent parameters may
need to be tuned, so that it does not result in unaccounted latency.
CAAvgRxStackEvents
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Average Number of User Data ingress events received.
Collection Interval: 30 min
Peg Condition: The average User Data ingress StackEvent sample taken during the collection interval.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of Average Value during the interval, for number of User Data
messages received from remote.
CAAvgTxStackEvents
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average Number of User Data egress events received from stacks to deliver it to remote.
Collection Interval: 30 min
Peg Condition: The average User Data egress StackEvent sample taken during the collection interval.
Measurement Scope: NE, Server
910-6528-001 Revision D, December 2012
209
Measurements
Recovery:
No action required.
This value provides a measure of Average Value during the interval, for number of User Data
messages transmitted to remote.
CADSTx
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of User Data egress events specifically for the default Direct Service.
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent received specifically for the default Direct Service
and processed by ComAgent Stack.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data egress messages are received by ComAgent
to be transmitted from hosting server to destined remote server using default Direct “EventTransfer”
Service.
CAHSTxRsrc
Measurement Group: ComAgent Performance, ComAgent Exception
Measurement Type: Simple
Description: Number of egress stack events that were routed to a known Resource.
Collection Interval: 30 min
Peg Condition: User Layer submits to ComAgent an egress stack event destined to a known Resource.
Measurement Scope: Server
Recovery:
No action required.
CAHSTxRsrcRateAvg
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average rate per second of egress stack events routed to a known Resource.
Collection Interval: 30 min
Peg Condition: Based upon the SysMetric.
910-6528-001 Revision D, December 2012
210
Measurements
Measurement Scope: Server
Recovery:
No action required.
CAHSTxRsrcRateMax
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum rate per second of egress stack events routed to a known Resource.
Collection Interval: 30 min
Peg Condition: Based upon the SysMetric.
Measurement Scope: Server
Recovery:
No action required.
CAPeakDataFIF0QueueUtil
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum percentage of ComAgent DataFIFO Queue Utilization.
Collection Interval: 30 min
Peg Condition: The maximum ComAgent DataFIFO Queue utilization sample taken during the
collection interval.
Measurement Scope: NE, Server
Recovery:
1. This measurement is primarily intended to assist in evaluating any issues with ComAgent User
Data StackEvent processing and thread scheduling.
If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the queue depth may need to be tuned.
If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
2. Contact the Tekelec Customer Care Center for assistance.
CAPeakMxFIFOQueueUtil
Measurement Group: ComAgent Performance
Measurement Type: Max
910-6528-001 Revision D, December 2012
211
Measurements
Description: Maximum percentage of ComAgent MxFIFO Queue Utilization.
Collection Interval: 30 min
Peg Condition: The maximum ComAgent connection MxFIFO Queue utilization sample taken during
the collection interval.
Measurement Scope: NE, Server
Recovery:
1. This measurement is primarily intended to assist in evaluating any issues with internal StackEvent
processing and thread scheduling.
If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the queue depth may need to be tuned.
If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
2. Contact the Tekelec Customer Care Center for assistance.
CAPeakQueueUtil
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Maximum percentage of Queue Utilization.
Collection Interval: 30 min
Peg Condition: The maximum ComAgent Egress Task Queue utilization sample taken during the
collection interval.
Measurement Scope: NE, Server
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance.
CAPeakRsrcPoolUtil
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Maximum percentage of internal resource pool utilization.
Collection Interval: 30 min
Peg Condition: This is to track the measure of maximum usage of the internal resource (Ex:
CommMessage Resource pool) for a given interval.
910-6528-001 Revision D, December 2012
212
Measurements
Measurement Scope: NE, Server
Recovery:
This measurement is primarily intended to assist in evaluating the need for additional processing
or performance capacity tuning on a node.
If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of a node over several collection
intervals, then the internal engineering resource pool capacity or other dependent parameters may
need to be tuned, so that it does not result in unaccounted latency.
CAPeakRxStackEvents
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Maximum Number of User Data ingress events received.
Collection Interval: 30 min
Peg Condition: The maximum User Data ingress StackEvent sample taken during the collection interval.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of Peak Value during the interval, for number of User Data messages
received from remote.
CAPeakTxStackEvents
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum Number of User Data egress events received from stacks to deliver it to remote.
Collection Interval: 30 min
Peg Condition: The maximum User Data egress StackEvent sample taken during the collection interval.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of Peak Value during the interval, for number of User Data messages
transmitted to remote.
CARSTx
Measurement Group: ComAgent Performance
910-6528-001 Revision D, December 2012
213
Measurements
Measurement Type: Simple
Description: Number of stack events submitted to a Routed Service for routing.
Collection Interval: 30 min
Peg Condition: Stack event submitted to ComAgent Routed Service by a local User Layer
Measurement Scope: Server
Recovery:
No action necessary
CARx
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of User Data ingress events received from a peer server.
Collection Interval: 30 min
Peg Condition: For each User Data StackEvent received from one of the configured peer and processed
by Communication Agent Stack.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data ingress messages are received by
Communication Agent to be transmitted to local hosting stack.
This measurement count should be equal to the summation of User Data ingress events success
and all User Data ingress events discards measurement counts
CARxSuccess
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of User Data ingress events successfully routed to local layers.
Collection Interval: 30 min
Peg Condition: For each User Data StackEvent received from a peer server and successfully transmitted
to the local stack.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data ingress messages are received by
Communication Agent and are successfully transmitted to local hosting stack.
910-6528-001 Revision D, December 2012
214
Measurements
CATransEndAbnorm
Measurement Group: ComAgent Exception, ComAgent Performance
Measurement Type: Simple
Description: Number of reliable transactions that terminated abnormally.
Collection Interval: 30 min
Peg Condition:
• Transaction times-out waiting for a response, and the maximum number of transmits has been
reached.
• Transaction time-to-live limit is exceeded.
• Transaction terminated due to lack of resources.
Note: This measurement is NOT pegged for these conditions:
• Transaction involves an unknown service.
• Transaction involves an unregistered Routed Service.
Measurement Scope: Server
Recovery:
1. Check the ComAgent Exception report to further diagnose the reasons why transactions are failing.
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndAbnormRateAvg
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average rate per second that ComAgent transactions ended abnormally during the
collection interval.
Collection Interval: 30 min
Peg Condition: Rate of transaction failures due to final timeouts. Failed Transaction Rate monitoring
is an average rate using an exponential smoothing algorithm. The average transaction failure rate is
a running average, smoothed over approximately 10 seconds.
Measurement Scope: Server
Recovery:
This measurement provides the average rate per second that ComAgent transactions were started.
This measurement is useful during trouble shooting when compared to other measurements.
No action necessary.
CATransEndAbnormRateMax
Measurement Group: ComAgent Performance
910-6528-001 Revision D, December 2012
215
Measurements
Measurement Type: Max
Description: Maximum rate per second that ComAgent transactions ended abnormally during the
collection interval.
Collection Interval: 30 min
Peg Condition: Rate of transaction failures due to final timeouts. Failed Transaction Rate monitoring
is an average rate using an exponential smoothing algorithm. The average transaction failure rate is
a running average, smoothed over approximately 10 seconds.
Measurement Scope: Server
Recovery:
This measurement provides the maximum rate per second that ComAgent transactions were started.
This measurement is useful during trouble shooting when compared to other measurements.
No action necessary.
CATransEndNorm
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended normally with
a response from a destination server.
Collection Interval: 30 min
Peg Condition: When a valid reliable response stack event (G=1, A=1) is received that corresponds to
a pending transaction record.
Measurement Scope: Server
Recovery:
No action necessary.
This measurement has value when compared against other measurements. If no new transactions
are started, then during normal operation, this measurement should match CATransStarted.
CATransPendingAvg
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average number of allocated pending transaction records over the collection interval.
Collection Interval: 30 min
Peg Condition: Average number of allocated pending transaction records during the collection interval.
Measurement Scope: Server
Recovery:
No action necessary.
910-6528-001 Revision D, December 2012
216
Measurements
CATransPendingMax
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum number of allocated pending transaction records.
Collection Interval: 30 min
Peg Condition: When a pending transaction record is allocated, and the total count of allocated pending
transaction records exceeds the current peak.
Measurement Scope: Server
Recovery:
No action necessary.
CATransRateAvg
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average rate per second that ComAgent transactions were started during the collection
interval.
Collection Interval: 30 min
Peg Condition: Transaction rate monitoring is an average rate using an exponential smoothing
algorithm. The average transaction rate is a running average, smoothed over approximately 10 seconds.
Measurement Scope: Server
Recovery:
This measurement provides the average rate per second that ComAgent transactions were started.
This measurement is useful during trouble shooting when compared to other measurements.
No action necessary.
CATransRateMax
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum rate per second that ComAgent transactions were started during the collection
interval.
Collection Interval: 30 min
Peg Condition: Transaction rate monitoring is an average rate using an exponential smoothing
algorithm. The average transaction rate is a running average, smoothed over approximately 10 seconds.
Measurement Scope: Server
Recovery:
910-6528-001 Revision D, December 2012
217
Measurements
This measurement provides the maximum rate per second that ComAgent transactions were started.
This measurement is useful during trouble shooting when compared to other measurements.
No action necessary.
CATransStarted
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers.
Collection Interval: 30 min
Peg Condition: When a valid reliable request stack event (G=1, R=1) is received from a local User
Layer.
Measurement Scope: Server
Recovery:
No action necessary.
CATransTimeAvg
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average transaction life-time in milliseconds.
Collection Interval: 30 min
Peg Condition: Transaction ends either normally or abnormally.
Measurement Scope: Server
Recovery:
No action necessary.
CATransTimeMax
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum transaction life-time in milliseconds.
Collection Interval: 30 min
Peg Condition: Transaction ends either normally or abnormally.
Measurement Scope: Server
Recovery:
No action necessary.
910-6528-001 Revision D, December 2012
218
Measurements
CATx
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of User Data egress events received on Communication Agent task queue from
local stacks to deliver it to a peer server.
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent received and processed by Communication
Agent Stack.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data egress messages are received by
Communication Agent for direct or indirect routing service.
This measurement count should be equal to the summation of User Data egress events success and
all User Data egress events discards measurement counts.
This measurement count should be equal to the summation of User Data egress events received
by Communication Agent for each (Direct, Routed and HA) routing service.
CATxSuccess
Measurement Group: ComAgent Performance
Measurement Type: Simple
Description: Number of User Data egress events successfully delivered to a peer server.
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent transmitted to the peer server.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data messages are successfully transmitted from
hosting server to destined remote server over “event transfer” static connection.
Communication Agent (ComAgent) Exception measurements
The "Communication Agent Exception" measurement group is a set of measurements that provide
information about exceptions and unexpected messages and events that are specific to the
Communication Agent protocol.
910-6528-001 Revision D, December 2012
219
Measurements
Table 27: Communication Agent Exception Measurement Report Fields
Measurement Tag
Description
CADataFIFOQueueFul
StackEvents discarded due to
30 min
ComAgent DataFIFO queue full
condition.
CADSTxDscrdCong
Number of egress stack events 30 min
discarded because the congestion
level of the connection exceeded
the stack events’ priority level.
CAHSRsrcErr
Number of times that ComAgent 30 min
receives in a heartbeat stack
event status concerning a known
Resource but an unknown
Sub-Resource.
CAHSTxDscrdCongSR
Number of stack events
discarded due to HA Service
Sub-Resource congestion.
30 min
CAHSTxDscrdIntErrSR
Number of egress stack events
destined to a known
Sub-Resource that were
discarded due to a ComAgent
internal error.
30 min
CAHSTxDscrdUnavailSR
Number of stack events
discarded because they were
submitted to an Unavailable
Sub-Resource of a given
Resource.
30 min
CAHSTxDscrdUnknownSR
Number of egress stack events 30 min
discarded because they referred
to a known Resource and an
unknown Sub-Resource.
CAHSTxDscrdUnkwnRsrc
Number of egress stack events 30 min
discarded because they referred
to an unknown Resource.
CAHSTxRsrc
Number of egress stack events
that were routed to a known
Resource.
30 min
CAMxFIFOQueueFul
StackEvents discarded due to
ComAgent MxFIFO queue full
condition.
30 min
CARsrcPoolFul
ComAgent internal resource
pool exhaustion condition
910-6528-001 Revision D, December 2012
Collection Interval
220
Measurements
Measurement Tag
Description
CARSTxDscrdCong
Number of stack events
30 min
discarded due to Routed Service
congestion.
CARSTxDscrdSvcUnavail
Number of stack events
discarded because they were
submitted to an Unavailable
Routed Service.
30 min
CARxDiscUnexpEvent
Number of ingress events
discarded because it was
unexpected in the connection
operational state.
30 min
CARxDscrdConnUnavail
Number of User Data ingress
events discarded because
connection was not in-service.
30 min
CARxDscrdDecodeFailed
Number of ingress events
discarded because failed to
deserialize (event not part of
stack service language).
30 min
CARxDscrdIncompat
Number of ingress events
discarded because an
Incompatible header version is
received.
30 min
CARxDscrdInternalErr
Number of ingress events
30 min
discarded because of other
unexpected internal processing
error.
CARxDscrdLayerSendFail
Number of User Data ingress
30 min
events discarded because layer’s
sendTo failed.
CARxDscrdMsgLenErr
Number of ingress events
discarded as it doesn’t contain
enough bytes (less than event
header bytes).
CARxDscrdUnkServer
Number of ingress events
discarded because the
origination server was
unknown/not configured.
30 min
CARxDscrdUnkStkLyr
Number of User Data ingress
events discarded because stack
layer is not known.
30 min
CARxMsgUnknown
Number of ingress events
discarded because stack event
was unknown.
30 min
910-6528-001 Revision D, December 2012
Collection Interval
221
Measurements
Measurement Tag
Description
Collection Interval
CAStackQueueFul
StackEvents discarded due to
ComAgent task queue full
condition.
30 min
CATransDscrdInvCorrId
Number of received stack events 30 min
that were received and discarded
because they did not correlate
with a pending transaction.
CATransDscrdStaleErrRsp
Number of times that an error 30 min
response was discarded because
it contained a valid correlation
ID value but its originating
server was not the last server to
which the request was sent.
CATransEndAbnorm
Number of reliable transactions 30 min
that terminated abnormally.
CATransEndAbnormRateAvg
Average rate per second that
30 min
ComAgent transactions ended
abnormally during the collection
interval.
CATransEndAbnormRateMax
Maximum rate per second that 30 min
ComAgent transactions ended
abnormally during the collection
interval.
CATransEndAnsErr
Number of reliable transactions 30 min
initiated by local User Layers
that ended with an error
response from a destination
server.
CATransEndErr
Number of reliable transactions 30 min
initiated by local User Layers
that ended abnormally with an
error response from a destination
server.
CATransEndNoResources
Number of reliable transactions 30 min
initiated by local User Layers
that ended abnormally due to
lack of resources.
CATransEndNoResponse
Number of reliable transactions 30 min
initiated by local User Layers
that ended abnormally due to a
timeout waiting for a response.
CATransEndUnkwnSvc
Number of reliable transactions 30 min
initiated by local User Layers
910-6528-001 Revision D, December 2012
222
Measurements
Measurement Tag
Description
Collection Interval
that ended abnormally because
they referred to an unknown
service.
CATransEndUnregSvc
Number of reliable transactions 30 min
initiated by local User Layers
that ended abnormally because
they referred to a known service
that lacked a registered User
Layer.
CATransRetx
Number of times stack events
were retransmitted.
30 min
CATransStaleSuccessRsp
Number of times that a success
response was received from an
unexpected server and was
accepted to end a transaction.
30 min
CATxDscrdConnUnAvail
Number of User Data egress
events discarded because
connection was not
in-service(down/blocked/not
aligned).
30 min
CATxDscrdDestUserIncmpat
Number of User Data egress
events discarded because the
remote doesn’t support
requested capabilities (either it
doesn’t support stack or event
library or event library version
is incompatible)
30 min
CATxDscrdEncodeFail
Number of User Data egress
events discarded because of
serialization failures
30 min
CATxDscrdInternalErr
Number of egress events
30 min
discarded because of other
unexpected internal processing
error.
CATxDscrdMxSendFail
Number of User Data egress
30 min
events discarded because of
failure reported by MxEndpoint
CATxDscrdUnknownSvc
Number of non-reliable and
30 min
non-request (G=0 or R=0) egress
stack events discarded because
they refer to an unknown
service.
910-6528-001 Revision D, December 2012
223
Measurements
Measurement Tag
Description
Collection Interval
CATxDscrdUnkServer
Number of egress events
discarded because the
destination server was
unknown/not configured.
30 min
CATxDscrdUnregSvc
Number of egress stack events 30 min
discarded because they reference
a known service that has no
registered User Layer.
CADSTxDscrdCong
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of egress stack events discarded because the congestion level of the connection
exceeded the stack events’ priority level.
Collection Interval: 30 min
Peg Condition: When ComAgent receives a stack event from a local User Layer to be transferred via
the direct service and the selected connection has a congestion level greater than the priority level of
the stack event.
Measurement Scope: Server
Recovery:
When this measurement is increasing, it is an indication that the product is experiencing overload.
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to determine if the offered load is
expected and exceeds the product’s capacity.
If the load is expected and exceeds the product’s capacity, then the capacity should be increased
so that the overload condition does not persist or reoccur.
2. Contact the Tekelec Customer Care Center for assistance.
CAHSTxDscrdCongSR
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of stack events discarded due to HA Service Sub-Resource congestion.D uring
normal operation, this measurement should not be increasing. When this measurement is increasing,
it is an indication that the product is experiencing overload.
Collection Interval: 30 min
Peg Condition: Stack event submitted to ComAgent by a local User Layer, and the stack event references
an HA Service Sub-Resource that has a congestion level greater than the priority level of the stack
event.
910-6528-001 Revision D, December 2012
224
Measurements
Measurement Scope: Server
Recovery:
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to determine if the offered load is
expected and exceeds the product’s capacity.
If the load is expected and exceeds the product’s capacity, then the capacity should be increased
so that the overload condition does not persist or reoccur. If the load does not exceed the product’s
capacity, then check the status of the servers hosting the Resource Providers to trouble-shoot the
cause of the overload.
This measurement may not indicate an error if the discarded stack event was a reliable request,
the Reliable Transfer Function was able to re-attempt, and the subsequent attempt got through.
2. Contact the Tekelec Customer Care Center for assistance.
CAHSRsrcErr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of times that ComAgent receives in a heartbeat stack event status concerning a
known Resource but an unknown Sub-Resource.
Collection Interval: 30 min
Peg Condition: When ComAgent stores an unexpected Sub-Resource entry in the local Resource
Provider Table. An unexpected Sub-Resource involves a known Resource but an unknown Sub-Resource
ID (SRID). This condition is associated with Alarm-ID 19848, and only the first instance of an unexpected
Sub-Resource is counted, not the repeats caused by multiple unknown Sub-Resources and the periodic
heartbeats containing the same information.
Measurement Scope: Server
Recovery:
1. Use Main MenuCommunication AgentMaintenance to determine configuration problems.
2. Contact the Tekelec Customer Care Center for assistance.
CAHSTxDscrdUnavailSR
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of stack events discarded because they were submitted to an Unavailable
Sub-Resource of a given Resource. During normal operation, this measurement should not be increasing.
Each count of this measurement indicates that a local application attempted to send a stack event to
another server using an HA Service Sub-Resource, but the event was discarded due to the Sub-Resource
being unavailable.
Collection Interval: 30 min
910-6528-001 Revision D, December 2012
225
Measurements
Peg Condition: Stack event submitted to ComAgent by a local User Layer, and the stack event references
an Unavailable Sub-Resource.
Measurement Scope: Server
Recovery:
1. Use Main MenuComamunication AgentMaintenanceHA Services Status to diagnose the cause of
routing failures.
If a discarded stack event was a request from a reliable transaction and the routing failure was due
to a temporary condition, then it is possible that the transaction completed successfully using one
or more retransmit attempts.
This measurement may not indicate an error if the discarded stack event was a reliable request,
the Reliable Transfer Function was able to re-attempt, and the subsequent attempt got through.
2. Contact the Tekelec Customer Care Center for assistance.
CAHSTxDscrdUnknownSR
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of egress stack events discarded because they referred to a known Resource and
an unknown Sub-Resource. During normal operation this measurement should be 0. A non-zero value
for this measurement indicates that ComAgent is improperly configured to support a local application.
Collection Interval: 30 min
Peg Condition: User Layer submits to ComAgent an egress stack event that refers to an unknown
Sub-Resource.
Measurement Scope: Server
Recovery:
1. Use Main MenuComamunication AgentMaintenanceHA Services Status to verify that all HA
Service Sub-Resources expected by local applications are present and operating.
2. Contact the Tekelec Customer Care Center for assistance.
CAHSTxDscrdUnkwnRsrc
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of egress stack events discarded because they referred to an unknown Resource.
Collection Interval: 30 min
Peg Condition: User Layer submits to ComAgent an egress stack event that refers to an unknown
Resource.
Measurement Scope: Server
Recovery:
910-6528-001 Revision D, December 2012
226
Measurements
1. Use Main MenuComamunication AgentMaintenanceHA Services Status to verify that all HA
Service Sub-Resources expected by local applications are present and operating.
2. Contact the Tekelec Customer Care Center for assistance.
CAHSTxRsrc
Measurement Group: ComAgent Performance, ComAgent Exception
Measurement Type: Simple
Description: Number of egress stack events that were routed to a known Resource.
Collection Interval: 30 min
Peg Condition: User Layer submits to ComAgent an egress stack event destined to a known Resource.
Measurement Scope: Server
Recovery:
No action required.
CARsrcPoolFul
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: ComAgent internal resource pool exhaustion condition.
Collection Interval: 30 min
Peg Condition: This is to track the measure of the internal resource (Ex: CommMessage Resource pool)
exhaustion condition for a given interval.
For each resource allocation/access attempt that result in resource pool manager returning an indication
that the maximum resources reserved are allocated and are in-use. When this condition occurs
ComAgent tries to allocate a new resource from heap and relists it after its life cycle (Ex: CommMessage
objects required for user data traffic for MxEndpoint interface).
Measurement Scope: NE, Server
Recovery:
This value provides a measure of how many times pre-allocated resources are exhausted in
ComAgent interfaces.
This measurement is primarily intended for performance analysis and to assist in evaluating the
need for any additional engineering processing capacity or tuning.
CARSTxDscrdCong
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of stack events discarded due to Routed Service congestion.
910-6528-001 Revision D, December 2012
227
Measurements
Collection Interval: 30 min
Peg Condition: Stack event submitted to ComAgent by a local User Layer, and the stack event references
a Routed Service that has a congestion level greater than the priority level of the stack event.
Measurement Scope: Server
Recovery:
1. Check the Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status screens to determine if the offered
load is expected and exceeds the product’s capacity.
If the load is expected and exceeds the product’s capacity, then the capacity should be increased
so that the overload condition does not persist or reoccur.
2. Contact the Tekelec Customer Care Center for assistance.
CARSTxDscrdSvcUnavail
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of stack events discarded because they were submitted to an Unavailable Routed
Service.
Collection Interval: 30 min
Peg Condition: Stack event submitted to ComAgent by a local User Layer, and the stack event references
an Unavailable Routed Service.
Measurement Scope: Server
Recovery:
Each count of this measurement indicates that a local application attempted to send a stack event to
another server using a Routed Service, but the event was discarded due to the Routed Service being
unavailable. Routing failures can occur due to:
• Maintenance actions are performed that result in a loss of communication between servers.
• Network problems result in a loss of communication between servers.
• Server overload can result in routes becoming unavailable for some stack events.
1. Check the Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status screens to further diagnose the cause
of routing failures.
If a discarded stack event was a request from a reliable transaction and the routing failure was due
to a temporary condition, then it is possible that the transaction completed successfully using one
or more retransmit attempts.
2. Contact the Tekelec Customer Care Center for assistance.
CARxDiscUnexpEvent
Measurement Group: ComAgent Exception
910-6528-001 Revision D, December 2012
228
Measurements
Measurement Type: Simple
Description: Number of ingress events discarded because it was unexpected in the connection
operational state.
Collection Interval: 30 min
Peg Condition: For each ingress StackEvent that is discarded by ComAgent Stack, due to StackEvent
received in unexpected connection state.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by ComAgent due to
message received in unexpected connection state.
CARxDscrdConnUnavail
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data ingress events discarded because connection was not in-service.
Collection Interval: 30 min
Peg Condition: For each User Data ingress StackEvent received from configured service peer server
with connection status not “in-service”.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data ingress messages are discarded by ComAgent
for the data messages received in connection not in “in-service” state.
CARxDscrdDecodeFailed
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of ingress events discarded because failed to deserialize (event not part of stack
service language).
Collection Interval: 30 min
Peg Condition: For each StackEvent received from a configured peer server that resulted in any decode
failures within ComAgent Stack.
Measurement Scope: NE, Server
Recovery:
No action required.
910-6528-001 Revision D, December 2012
229
Measurements
This value provides a measure of how many ingress messages are discarded by ComAgent due to
internal decode error condition.
CARxDscrdIncompat
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of ingress events discarded because an Incompatible header version is received.
Collection Interval: 30 min
Peg Condition: For each ingress StackEvent that is discarded by ComAgent Stack, due to unsupported
base header version, as indicated in StackEvent.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by ComAgent due to
incompatible base header version of base software event library.
CARxDscrdInternalErr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of ingress events discarded because of other unexpected internal processing
error.
Collection Interval: 30 min
Peg Condition: For each ingress StackEvent that is discarded by ComAgent Stack, due to internal
processing errors for conditions not covered by other meas-pegs.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by ComAgent due to
internal software processing errors for conditions not covered by other measurement pegs.
CARxDscrdLayerSendFail
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data ingress events discarded because layer’s sendTo failed.
Collection Interval: 30 min
910-6528-001 Revision D, December 2012
230
Measurements
Peg Condition: For each User Data StackEvent received from a configured service peer server and
resulted in send failure to the destination stack layer.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data ingress messages are discarded by ComAgent
due to internal send failure to destination stack layer.
CARxDscrdMsgLenErr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of ingress events discarded as it doesn’t contain enough bytes (less than event
header bytes).
Collection Interval: 30 min
Peg Condition: For each StackEvent received from configured peer with message size less than the
minimum required Header.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by Communication
Agent due to message size error.
CARxDscrdUnkServer
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of ingress events discarded because the origination server was unknown/not
configured.
Collection Interval: 30 min
Peg Condition: For each ingress StackEvent that is discarded by ComAgent Stack, due to unknown
origination ip address contents in StackEvent.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by ComAgent due to
unknown origination ip address in StackEvent.
910-6528-001 Revision D, December 2012
231
Measurements
CARxDscrdUnkStkLyr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data ingress events discarded because stack layer is not known.
Collection Interval: 30 min
Peg Condition: For each User Data ingress StackEvent received by Communication Agent Stack, for
an unknown destination stack.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by Communication
Agent , as the destination stack is not registered/known.
CARxMsgUnknown
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of ingress events discarded because stack event was unknown.
Collection Interval: 30 min
Peg Condition: For each undefined StackEvent received from one of the configured peer server.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many ingress messages are discarded by ComAgent as the
message is not defined/known to ComAgent Stack.
CAStackQueueFul
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: StackEvents discarded due to ComAgent task queue full condition.
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent that is discarded by ComAgent Stack, due to
failure in attempting to put the messages in ComAgent Egress Task Queue.
Measurement Scope: NE, Server
Recovery:
910-6528-001 Revision D, December 2012
232
Measurements
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance.
CATransDscrdInvCorrId
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of received stack events that were received and discarded because they did not
correlate with a pending transaction.
Collection Interval: 30 min
Peg Condition: ComAgent receives a response stack event that contains a correlation ID that does not
match a pending transaction record.
Measurement Scope: Server
Recovery:
This measurement indicates that one or more destination servers are either responding to requests
after a transaction has ended or are sending invalid responses. Contact the Tekelec Customer Care
Center for assistance.
CATransDscrdStaleErrRsp
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of times that an error response was discarded because it contained a valid
correlation ID value but its originating server was not the last server to which the request was sent.
Collection Interval: 30 min
Peg Condition: ComAgent receives an error response stack event that has a correlation ID for an
existing pending transaction record but that is originated from a different server than to which the
request was last sent.
Measurement Scope: Server
Recovery:
This measurement indicates that one or more servers are responding with errors to requests after the
local ComAgent has retransmitted the requests to other destination servers. This could occur due to:
• Network problems result in intermittent loss of communication between servers.
• Server overload results in delayed responses
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to check the status of the far-end
servers and look for signs of overload.
910-6528-001 Revision D, December 2012
233
Measurements
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndAbnorm
Measurement Group: ComAgent Exception, ComAgent Performance
Measurement Type: Simple
Description: Number of reliable transactions that terminated abnormally.
Collection Interval: 30 min
Peg Condition:
• Transaction times-out waiting for a response, and the maximum number of transmits has been
reached.
• Transaction time-to-live limit is exceeded.
• Transaction terminated due to lack of resources.
Note: This measurement is NOT pegged for these conditions:
• Transaction involves an unknown service.
• Transaction involves an unregistered Routed Service.
Measurement Scope: Server
Recovery:
1. Check the ComAgent Exception report to further diagnose the reasons why transactions are failing.
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndAbnormRateAvg
Measurement Group: ComAgent Performance
Measurement Type: Average
Description: Average rate per second that ComAgent transactions ended abnormally during the
collection interval.
Collection Interval: 30 min
Peg Condition: Rate of transaction failures due to final timeouts. Failed Transaction Rate monitoring
is an average rate using an exponential smoothing algorithm. The average transaction failure rate is
a running average, smoothed over approximately 10 seconds.
Measurement Scope: Server
Recovery:
This measurement provides the average rate per second that ComAgent transactions were started.
This measurement is useful during trouble shooting when compared to other measurements.
No action necessary.
910-6528-001 Revision D, December 2012
234
Measurements
CATransEndAbnormRateMax
Measurement Group: ComAgent Performance
Measurement Type: Max
Description: Maximum rate per second that ComAgent transactions ended abnormally during the
collection interval.
Collection Interval: 30 min
Peg Condition: Rate of transaction failures due to final timeouts. Failed Transaction Rate monitoring
is an average rate using an exponential smoothing algorithm. The average transaction failure rate is
a running average, smoothed over approximately 10 seconds.
Measurement Scope: Server
Recovery:
This measurement provides the maximum rate per second that ComAgent transactions were started.
This measurement is useful during trouble shooting when compared to other measurements.
No action necessary.
CATransEndAnsErr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended with an error
response from a destination server.
Collection Interval: 30 min
Peg Condition: When a reliable response stack event (G=1, A=1, E=1) is received from a server to
which a request was sent, and the response corresponds to a pending transaction record.
Measurement Scope: Server
Recovery:
No action necessary.
This measurement has value when compared against other measurements. Server applications
may respond with errors as part of normal operations, as seen by ComAgent.
CATransEndErr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended abnormally
with an error response from a destination server.
Collection Interval: 30 min
910-6528-001 Revision D, December 2012
235
Measurements
Peg Condition: When a valid reliable response stack event (G=1, A=0, E=1) is received from a server
to which a request was sent, and the response corresponds to a pending transaction record.
Measurement Scope: Server
Recovery:
This measurement indicates that one or more destination servers are unable to process reliable requests
received from the local server. This can be caused due to maintenance actions, server overload, and
unexpected conditions in software.
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to determine network and server
communications.
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndNoResources
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended abnormally due
to lack of resources.
Collection Interval: 30 min
Peg Condition: ComAgent receives a reliable request (G=1, R=1) from a local User Layer and ComAgent
is unable to allocate resources to process the transaction.
Measurement Scope: Server
Recovery:
This measurement indicates that the local server is exhausting its resources for processing reliable
transactions. This can result when the combination of transaction rate and response delays exceeds
engineered limits. High transaction rates can result from local server overload. Excess response delays
can result from overloaded destination servers and problems in the network between servers.
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to determine network and server
communications.
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndNoResponse
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended abnormally due
to a timeout waiting for a response.
Collection Interval: 30 min
Peg Condition: Limit on the number of retransmits is reached with no response and limit on the
transaction time-to-live is exceeded.
910-6528-001 Revision D, December 2012
236
Measurements
Measurement Scope: Server
Recovery:
This measurement indicates that one or more destination servers are unable to process reliable requests
received from the local server. This can be caused due to maintenance actions, server overload, and
unexpected conditions in software.
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to determine network and server
communications.
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndUnkwnSvc
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended abnormally
because they referred to an unknown service.
Collection Interval: 30 min
Peg Condition: ComAgent receives a reliable request (G=1, R=1) from a local User Layer that refers
to an unknown service.
Measurement Scope: Server
Recovery:
This measurement indicates improper configuration of ComAgent and/or a User Layer application.
1. Use Main MenuCommunication AgentConfigurationRouted Services to confirm that all services
expected by local applications are present.
2. Contact the Tekelec Customer Care Center for assistance.
CATransEndUnregSvc
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of reliable transactions initiated by local User Layers that ended abnormally
because they referred to a known service that lacked a registered User Layer.
Collection Interval: 30 min
Peg Condition: ComAgent receives a reliable request (G=1, R=1) from a local User Layer that refers
to a known service that has no registered User Layer.
Measurement Scope: Server
Recovery:
A non-zero value in this measurement indicates a software malfunction.
Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
237
Measurements
CATransRetx
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of times stack events were retransmitted.
Collection Interval: 30 min
Peg Condition: ComAgent reliable transaction retransmit timer expires and the limit on the number
of retransmits has not been reached.
Measurement Scope: Server
Recovery:
When this measurement is increasing, it indicates that communication between servers is experiencing
unexpectedly high latency and/or packet loss. Retransmissions can occur due to:
• Maintenance actions are performed that result in a loss of communication between servers.
• Network problems result in a loss of communication between servers.
• Server overload can result in delayed responses.
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to determine network and server
communications.
2. Contact the Tekelec Customer Care Center for assistance.
CATransStaleSuccessRsp
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of times that a success response was received from an unexpected server and
was accepted to end a transaction.
Collection Interval: 30 min
Peg Condition: ComAgent receives a success response stack event (G=1, A=1, E=1) that has a correlation
ID for an existing pending transaction record but that is originated from a different server than to
which the request was last sent.
Measurement Scope: Server
Recovery:
This measurement indicates that a Routed Service received a success response from an unexpected
server. This most commonly occurs if a server is slow to respond, ComAgent retransmits a request to
another server, and then the original server finally responds to the request.
1. Use Main MenuCommunication AgentMaintenanceRouted Services Status and Main
MenuCommunication AgentMaintenanceConnection Status to diagnose stale responses.
2. Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
238
Measurements
CATxDscrdConnUnAvail
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data egress events discarded because connection was not
in-service(down/blocked/not aligned).
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent that is discarded by ComAgent Stack, due to
connection status not being in-service.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data egress messages are discarded by ComAgent
due to connection unavailability reasons.
CATxDscrdDestUserIncmpat
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data egress events discarded because the remote doesn’t support
requested capabilities (either it doesn’t support stack or event library or event library version is
incompatible).
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent that is discarded by Communication Agent
Stack, due to incompatibility in requested library id/version and the one known by Communication
Agent.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data egress messages are discarded by
Communication Agent due to remote not supporting requested capabilities.
CATxDscrdEncodeFail
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data egress events discarded because of serialization failures.
Collection Interval: 30 min
910-6528-001 Revision D, December 2012
239
Measurements
Peg Condition: For each User Data egress StackEvent that is discarded by Communication Agent
Stack, due to any local encode failures.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data egress messages are discarded by
Communication Agent due to local encode failure.
CATxDscrdInternalErr
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of egress events discarded because of other unexpected internal processing error.
Collection Interval: 30 min
Peg Condition: For each egress StackEvent that is discarded by ComAgent Stack, due to internal
processing errors for conditions not covered by other meas-pegs.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many egress messages are discarded by ComAgent due to
internal software processing errors for conditions not covered by other measurement pegs.
CATxDscrdMxSendFail
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of User Data egress events discarded because of failure reported by MxEndpoint.
Collection Interval: 30 min
Peg Condition: For each User Data egress StackEvent that is discarded by Communication Agent
Stack, due to send failure as indicated by underlying transport.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many User Data egress messages are discarded by
Communication Agent due to transport reported error condition.
910-6528-001 Revision D, December 2012
240
Measurements
CATxDscrdUnknownSvc
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of non-reliable and non-request (G=0 or R=0) egress stack events discarded
because they refer to an unknown service.This measurement indicates that ComAgent is improperly
configured to support a local application.
Collection Interval: 30 min
Peg Condition: User Layer submits to ComAgent a non-reliable or non-request (G=0 or R=0) egress
stack event that refers to an unknown service.
Measurement Scope: Server
Recovery:
1. Use Main MenuCommunication AgentConfigurationRouted Services screen to verify that all Routed
Services expected by local applications are properly configured.
2. Contact the Tekelec Customer Care Center for assistance.
CATxDscrdUnkServer
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of egress events discarded because the destination server was unknown/not
configured.
Collection Interval: 30 min
Peg Condition: For each egress StackEvent that is discarded by ComAgent Stack, due to unknown
destination ip address contents in StackEvent.
Measurement Scope: NE, Server
Recovery:
No action required.
This value provides a measure of how many egress messages are discarded by ComAgent due to
unknown destination ip address in StackEvent.
CATxDscrdUnregSvc
Measurement Group: ComAgent Exception
Measurement Type: Simple
Description: Number of egress stack events discarded because they reference a known service that
has no registered User Layer.
Collection Interval: 30 min
910-6528-001 Revision D, December 2012
241
Measurements
Peg Condition: User Layer submits to ComAgent an egress stack event that refers to a known service
that lacks a registered User Layer.
Measurement Scope: Server
Recovery:
A non-zero measurement indicates that a local application is malfunctioning and is attempting to
use a service for which it has not registered. Contact the Tekelec Customer Care Center for assistance.
Connection Congestion measurements
The Connection Congestion measurement report contains per-connection measurements related to
Diameter Connection congestion states. Measurements in this group include:
• Congestion Level-X time duration
• Number of times entered Congestion Level-X
• Number of times Remote Busy Congestion occurred
Table 28: Connection Congestion Measurement Report Fields
Measurement Tag
Description
ConnOnsetCL1
The number of times the
5 min
connection experienced the onset
of CL1.
ConnOnsetCL2
The number of times the
5 min
connection experienced the onset
of CL2.
ConnOnsetCL3
The number of times the
5 min
connection experienced the onset
of CL3.
ConnOnsetCL4
The number of times the
5 min
connection experienced the onset
of CL4.
EvSmoothedEmrPeak
Smoothed EMR Peak.
5 min
EvSmoothedEmrAvg
Smoothed EMR Average.
5 min
EvRemoteBusyCongested
Number of times Remote Busy
Congestion occurred.
5 min
RxRejectedConnCongestion
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node because of
Diameter Connection
Congestion.
910-6528-001 Revision D, December 2012
Collection Interval
242
Measurements
Measurement Tag
Description
Collection Interval
TmConnInCL1
Total amount of time (in
seconds) the connection
experienced CL1.
5 min
TmConnInCL2
Total amount of time (in
seconds) the connection
experienced CL2.
5 min
TmConnInCL3
Total amount of time (in
seconds) the connection
experienced CL3.
5 min
TmConnInCL4
Total amount of time (in
seconds) the connection
experienced CL4.
5 min
ConnOnsetCL1
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: The number of times the connection experienced the onset of CL1.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
ConnOnsetCL2
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: The number of times the connection experienced the onset of CL2.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
ConnOnsetCL3
Measurement Group: Connection Congestion
Measurement Type: Simple
910-6528-001 Revision D, December 2012
243
Measurements
Description: The number of times the connection experienced the onset of CL3.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
ConnOnsetCL4
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: The number of times the connection experienced the onset of CL4.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
EvRemoteBusyCongested
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: Number of times Remote Busy Congestion occurred.
Collection Interval: 5 min
Peg Condition: Each time the Remote Busy Congestion Level changed from CL0 to either CL1, CL2
or CL3.
Measurement Scope: Site
Recovery:
No action necessary.
EvSmoothedEmrAvg
Measurement Group: Connection Congestion
Measurement Type: Average
Description: Average of the “Smoothed EMR” calculations made during the collection interval.
Collection Interval: 5 min
Peg Condition: A “Smoothed EMR” calculation St is periodically calculated (every 90ms). Each time
St is calculated, then the “Average Smoothed EMR” measurement shall be updated. For example, if
910-6528-001 Revision D, December 2012
244
Measurements
3 Smoothed EMR values were calculated during the collection interval – 10, 14 and 9 respectively,
then the “Average Smoothed EMR” would be: 11 ((10+14+ 9)/3)
Measurement Scope: Site
Recovery:
No action necessary.
EvSmoothedEmrPeak
Measurement Group: Connection Congestion
Measurement Type: Max
Description: Peak “Smoothed EMR” calculation made during the collection interval.
Collection Interval: 5 min
Peg Condition: A “Smoothed EMR” calculation St is periodically calculated (every 90ms). If the new
St exceeds any previous St-k value for the collection interval, then this measurement will be updated
with the new St value. For example, if 3 Smoothed EMR values were calculated during the collection
interval – 10, 14 and 9 respectively, then the “Peak Smoothed EMR” would be: 14=Max(10, 14, 9)
Measurement Scope: Site
Recovery:
No action necessary.
RxRejectedConnCongestion
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: Number of Request messages from a downstream peer rejected by a Local Node because
of Diameter Connection Congestion.
Collection Interval: 5 min
Peg Condition: Each time an ingress transaction is abandoned and the Routing Option Set “Connection
Congestion” action is invoked.
Measurement Scope: Site
Recovery:
No action required.
TmConnInCL1
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: Total amount of time (in seconds) the connection experienced CL1.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
245
Measurements
Peg Condition:
Measurement Scope: Server Group
Recovery:
TmConnInCL2
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: Total amount of time (in seconds) the connection experienced CL2.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
TmConnInCL3
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: Total amount of time (in seconds) the connection experienced CL3.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
TmConnInCL4
Measurement Group: Connection Congestion
Measurement Type: Simple
Description: Total amount of time (in seconds) the connection experienced CL4.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
246
Measurements
Connection Exception measurements
The Connection Exception measurement report contains measurements that provide information
about exceptions and unexpected messages and events for individual SCTP/TCP connections that
are not specific to the Diameter protocol.
Table 29: Connection Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
EvConnCerValFail
The number of times a CER
5 min
contained invalid or
unsupported AVP or AVP value.
EvConnCexIpChkFail
The Host-IP-Address AVP(s)
received in a CER or CEA
message from the peer did not
match the actual peer
connection’s IP address(es).
EvConnCnxFail
Number of times the transport 5 min
connection attempt failed. This
includes only unsuccessful
attempts to connect to the peer;
it does not include failure of
established connections.
EvConnDnsFail
Number of times an attempt to
resolve a peer’s FQDN to an IP
address via DNS failed.
5 min
EvConnFarEndClose
Number of times the far end
closed the connection.
5 min
EvConnManClose
Number of times the connection 5 min
was manually closed via
administratively Disabling the
connection locally.
EvConnPeerNumIpFail
The peer has advertised in the 5 min
INIT/INIT_ACK chunk a
number of IP addresses different
from the number of IP addresses
the peer has been configured
with in the respective connection
object.
5 min
EvConnRejMultiHomedSCTPAtt The number of times a
5 min
connection attempt was rejected
because the peer attempted to
initiate an SCTP multi-homed
IPFE connection.
910-6528-001 Revision D, December 2012
247
Measurements
Measurement Tag
Description
Collection Interval
EvConnRelease
The number of times the
5 min
connection was terminated based
on a connection release request
from DRL
EvConnSockInitFail
Number of times the socket
initialization failed.
5 min
EvConnTransFail
The number of times the
connection was closed due to
SCTP/TCP transport failure.
5 min
TxConnSendFail
Number of times the transport 5 min
send failed for any message on
an established connection. When
this occurs, the transport
connection will NOT be
disconnected.
EvConnCerValFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: CER contained invalid or unsupported AVP or AVP value.
Collection Interval: 5 min
Peg Condition: Inband-Security AVP value in CER was other than 0 (NO_INBAND_SECURITY).
Measurement Scope: Server Group
Recovery:
1. Disable peer’s use of inband security.
2. If the problem persists, contact the Tekelec Customer Care Center.
EvConnCexIpChkFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The Host-IP-Address AVP(s) received in a CER or CEA message from the peer did not
match the actual peer connection’s IP address(es).
Collection Interval: 5 min
Peg Condition: On receipt of CER/CEA message from the peer for which the Host-IP-Address AVP(s)
received in a CER or CEA message from the peer did not match the actual peer connection’s IP
address(es).
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
248
Measurements
Recovery:
1. Diagnose peer to resolve inconsistency.
2. If the problem persists, contact the Tekelec Customer Care Center.
EvConnCnxFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the transport connection attempt failed. This includes only
unsuccessful attempts to connect to the peer; it does not include failure of established connections.
Collection Interval: 5 min
Peg Condition: Pegged when the DSR attempts to initiate a connection to a peer and fails.
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive number of failed connection attempts, check that the
peer is operational, and that it is accepting connections on the SCTP/TCP listen port configured
for the Peer Node.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnDnsFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times an attempt to resolve a peer’s FQDN to an IP address via DNS failed.
Collection Interval: 5 min
Peg Condition: Pegged when a connection is closed without the peer sending a DPR.
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive number of DNS resolution failures, examine the DNS
configuration values to determine if the correct DNS servers are being queried.
2. Examine the DNS configuration of the configured DNS servers.
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnFarEndClose
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the far end closed the connection.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
249
Measurements
Peg Condition: Pegged when the peer closes the connection.
Measurement Scope: Server Group
Recovery:
If this measurement indicates an excessive number of peer disconnects, the Alarm History and
measurements RxConnDpr, RxConnDwr, and TxConnDwa should be examined to determine the
reason for the peer disconnects.
EvConnManClose
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the connection was manually closed via administratively disabling
the connection locally.
Collection Interval: 5 min
Peg Condition: Pegged when a user disables a connection from the GUI.
Measurement Scope: Server Group
Recovery:
No action required.
EvConnPeerNumIpFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The peer has advertised in the INIT/INIT_ACK chunk a number of IP addresses different
from the number of IP addresses the peer has been configured with in the respective connection object.
Collection Interval: 5 min
Peg Condition: The peer advertised a different number of IP addresses than configured.
Measurement Scope: Server Group
Recovery:
Check the peer configuration on the local node and the networking configuration on the peer itself
with regard to which IP addresses the peer shall advertise using the Diameter > Configuration >
System Options page.
EvConnRejMultiHomedSCTPAtt
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times a connection attempt was rejected because the peer attempted to
initiate an SCTP multi-homed IPFE connection.
910-6528-001 Revision D, December 2012
250
Measurements
Collection Interval: 5 min
Peg Condition: This measurement is incremented when a DSR detects a multihomed SCTP IPFE
connection attempt by the peer, based on the CER received from the peer.
Measurement Scope: Server Group
Recovery:
1. Update the peer to initiate unihomed IPFE SCTP connections.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnRelease
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the connection was terminated based on a connection release request
from DRL.
Collection Interval: 5 min
Peg Condition: Pegged when a connection terminated successfully on request from DRL.
Measurement Scope: Server Group
Recovery:
No action necessary.
EvConnSockInitFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the socket initialization failed.
Collection Interval: 5 min
Peg Condition: Pegged when the DSR attempts to apply the SCTP/TCP socket options to a peer
connection and fails.
Measurement Scope: Server Group
Recovery:
Check the SCTP/TCP options in the Connection Configuration Set for the connection and correct
them.
EvConnTransFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the transport connection was closed due to SCTP/TCP transport
failure.
910-6528-001 Revision D, December 2012
251
Measurements
Collection Interval: 5 min
Peg Condition: Pegged when a connection is closed without the peer sending a DPR.
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive number of ungraceful peer disconnects the Alarm
History should be examined to determine the reason for the peer disconnects.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxConnSendFail
Measurement Group: Connection Exception
Measurement Type: Simple
Description: The number of times the transport send failed for any message on an established
connection. When this occurs, the transport connection will NOT be disconnected.
Collection Interval: 5 min
Peg Condition: Pegged when the DSR is unable to send a message on the connection
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive number of send failures, examine the
TxConnSendBufPeak and TxConnSendBufAvg measurements.
2. Contact the Tekelec Customer Care Center for assistance if needed.
Connection Performance measurements
The Connection Performance measurement report contains measurements that provide performance
information for individual SCTP/TCP connections that are not specific to the Diameter protocol.
Table 30: Connection Performance Measurement Report Fields
Measurement Tag
Description
EvConnCnxSuccess
Number of times the transport 5 min
connection was successfully
established. In instances where
two connections are established
and one is disconnected after an
election, both connection
establishments are counted.
EvPerConnQueueCongestionChange Number of times that the
congestion level changed for a
Connection.
910-6528-001 Revision D, December 2012
Collection Interval
5 min
252
Measurements
Measurement Tag
Description
RxConnAvgMPS
Exponentially smoothed average 5 min
rate in MPS on the connection.
Note: This measurement will be
sampled periodically and
reported in the Connections
Maintenance GUI as a type of
KPI.
RxConnPeakMPS
Peak rate of the exponentially
smoothed average rate in MPS
on the connection
RxConnMsgs
Number of messages received 5 min
on the connection. This includes
all Diameter messages, both
routable and non-routable.
RxConnOctets
Number of octets received on the 5 min
connection. This includes
Diameter payload octets for all
Diameter messages, both
routable and non-routable.
RxConnRecvBufAvg
Average number of bytes in the 5 min
SCTP/TCP receive buffer. The
bytes in the receive buffer are
those received from the peer but
not yet read by the peer state
machine.
RxConnRecvBufPeak
Peak number of bytes in the
5 min
SCTP/TCP receive buffer. The
bytes in the receive buffer are
those received from the peer but
not yet read by the peer state
machine.
RxMsgRateAvg
Average Connection Ingress
Message Rate.
5 min
RxMsgRatePeak
Peak Connection Ingress
Message Rate.
5 min
RxSctpChunkMp
Number of SCTP data chunks
received by the MP (excluding
duplicates).
5 min
RxSctpPacketMp
Number of SCTP packets
received by the MP (excluding
duplicates).
5 min
TmRxMPSDelay_MaxCapacity
Total amount of time during the 5 min
measurement reporting interval
910-6528-001 Revision D, December 2012
Collection Interval
5 min
253
Measurements
Measurement Tag
Description
Collection Interval
that the connection experienced
delay in ingress message
processing because the ingress
message rate on the connection
exceeded the connection’s
configured Maximum Ingress
MPS
TmRxMPSDelay_SharedCapacity Total amount of time during the 5 min
measurement reporting interval
that the connection experienced
delay in ingress message
processing due to no capacity
available in the MP server’s
shared ingress MPS pool
TxConnMsgs
Number of messages sent on the 5 min
connection. This includes all
Diameter messages, both
routable and non-routable.
TxConnOctets
Number of octets sent on the
connection. This includes
Diameter payload octets for all
Diameter messages, both
routable and non-routable.
TxConnSendBufAvg
Average number of bytes in the 5 min
SCTP/TCP send buffer. The
SCTP/TCP send buffer contains
all bytes sent to the SCTP/TCP
socket by the peer state machine
which have not yet been sent to
the peer or have been sent to the
peer and have not been
unacknowledged.
TxConnSendBufPeak
Peak number of bytes in the
5 min
SCTP/TCP send buffer. The
SCTP/TCP send buffer contains
all bytes sent to the SCTP/TCP
socket by the peer state machine
which have not yet been sent to
the peer or have been sent to the
peer and have not been
unacknowledged.
TxPerConnQueueAvg
Per Connection Egress Message 5 min
Queue Average Utilization.
TxPerConnQueuePeak
Per Connection Egress Message 5 min
Queue Peak Utilization.
910-6528-001 Revision D, December 2012
5 min
254
Measurements
Measurement Tag
Description
Collection Interval
TxSctpChunkMp
The number of SCTP data
chunks sent by the MP
(excluding duplicates).
5 min
TxSctpPacketMp
The number of SCTP packets
sent by the MP (excluding
duplicates).
5 min
TxSctpRTOExpMp
The number of SCTP
5 min
retransmission timer expirations
on the MP.
EvConnCnxSuccess
Measurement Group: Connection Performance
Measurement Type: Simple
Description: The number of times the transport connection was successfully established. In instances
where two connections are established and one is disconnected after an election, both connection
establishments are counted.
Collection Interval: 5 min
Peg Condition: Pegged when a socket connection is made, regardless of which side initiates the
connection.
Measurement Scope: Server Group
Recovery:
No action required.
EvPerConnQueueCongestionChange
Measurement Group: Connection Performance
Measurement Type: Simple
Description: The number of times that the congestion level changed for a Per Connection Egress Queue.
Collection Interval: 5 min
Peg Condition: Each time the congestion level for a Per Connection Egress Queue was changed.
Measurement Scope: Server Group
Recovery:
1. An IP network, or Diameter peer, problem may exist thus preventing SCTP/TCP from transmitting
messages into the network at the same pace that messages are being received from the network.
2. The transport task associated with the connection may be experiencing a problem, preventing it
from processing events from its Connection Event Message Queue. The alarm log should be
examined using the Alarms & Events page.
910-6528-001 Revision D, December 2012
255
Measurements
3. If one or more MPs in a server site have failed, the traffic will be distributed among the remaining
MPs in the server site. MP server status can be monitored using the Status & Manage > Server
page.
4. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP.
The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each
MP in the server site should be receiving approximately the same ingress transaction per second.
5. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
6. If the problem persists, contact the Tekelec Customer Care Center.
RxConnAvgMPS
Measurement Group: Connection Performance
Measurement Type: Average
Description: Exponentially smoothed average rate in MPS on the connection.
Note: This measurement will be sampled periodically and reported in the Connections Maintenance
GUI as a KPI.
Collection Interval: 5 min
Peg Condition: This measurement is driven by the SysMetric.
Measurement Scope: Per network, per NE, per MP server
Recovery:
This measurement indicates the exponentially smoothed 30-second average of the ingress messages
per second over the measurement reporting interval. The average rate is exponentially smoothed over
a 30 second interval to help eliminate variance caused by bursts in the ingress message rate. This
measurement, if reported periodically, provides a history of the ingress messaging rate for each
connection.
This measurement can also be seen in near real-time by viewing the connection status screen
(DiameterMaintenanceConnections).
No action required.
RxConnMsgs
Measurement Group: Connection Performance
Measurement Type: Simple
Description: The number of messages received on the connection. This includes all Diameter messages,
both routable and non-routable.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is received from the peer on the connection. This
measurement is pegged for all messages accepted for processing, as well as those rejected due to local
congestion, MPS limitation, etc.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
256
Measurements
Recovery:
No action required.
RxConnOctets
Measurement Group: Connection Performance
Measurement Type: Simple
Description: The number of octets received on the connection. This includes Diameter payload octets
for all Diameter messages, both routable and non-routable.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is received from the peer on the connection. This
measurement is pegged for all messages accepted for processing, as well as those rejected due to local
congestion, MPS limitation, etc.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnPeakMPS
Measurement Group: Connection Performance
Measurement Type: Max
Description: Peak rate of the exponentially smoothed average rate in MPS on the connection.
Collection Interval: 5 min
Peg Condition: This measurement is driven by the SysMetric.
Measurement Scope: Per network, per NE, per MP server
Recovery:
This measurement indicates the highest average rate in ingress messages per second that was processed
by the Diameter connection. In other words, this measurement shows the highest value of measurement
ConnIngressAvgMPS during the measurement reporting interval.
No action required.
RxConnRecvBufAvg
Measurement Group: Connection Performance
Measurement Type: Average
Description: The average number of bytes in the SCTP/TCP receive buffer. The bytes in the receive
buffer are those received from the peer but not yet read by the peer state machine.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
257
Measurements
Peg Condition: Periodically (currently once a second) the depth of the socket receive buffer is measured
and the value used to update this measurement.
Measurement Scope: Server Group
Recovery:
1. If this measurement is at or above 80%, this may be an indication that the SCTP/TCP socket receive
buffer size is too small, or that the Local Node is unable to handle the load it is presented. Increase
the SCTP/TCP Socket Receive Buffer Size from the Connection Configuration Set for this connection.
2. If this does not improve the situation, consider load-sharing with other DSRs.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxConnRecvBufPeak
Measurement Group: Connection Performance
Measurement Type: Max
Description: The peak number of bytes in the SCTP/TCP receive buffer. The bytes in the receive buffer
are those received from the peer but not yet read by the peer state machine.
Collection Interval: 5 min
Peg Condition: Periodically (currently once a second) the depth of the socket receive buffer is measured
and the value used to update this measurement.
Measurement Scope: Server Group
Recovery:
1. If this measurement exceeds the SCTP/TCP socket receive buffer size, this may be an indication
that the SCTP/TCP socket receive buffer size is too small, or that the Local Node is unable to handle
the load it is presented. Increase the SCTP/TCP Socket Receive Buffer Size from the Connection
Configuration Set for this connection.
2. If this does not improve the situation, consider load-sharing with other DSRs.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxMsgRateAvg
Measurement Group: Connection Performance
Measurement Type: Average
Description: The average connection ingress message rate (in messages per second) measured during
the collection interval. The ingress message rate is the number of ingress Diameter messages that are
targeted for Relay Agent routing (non-zero Application ID).
Collection Interval: 5 min
Peg Condition:The average of all connection ingress message rate samples taken during the collection
interval.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
258
Measurements
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxMsgRatePeak
Measurement Group: Connection Performance
Measurement Type: Max
Description: The peak connection ingress message rate (in messages per second) measured during the
collection interval. The ingress message rate is the number of ingress Diameter messages that are
targeted for Relay Agent routing (non-zero Application ID).
Collection Interval: 5 min
Peg Condition: The maximum connection ingress message rate (messages per second) sample taken
during the collection interval.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
259
Measurements
TmRxMPSDelay_MaxCapacity
Measurement Group: Connection Performance
Measurement Type: Simple
Description: Total amount of time in milliseconds that the connection experienced delay in ingress
message processing because the ingress message rate on the connection exceeded the connection’s
configured Maximum Ingress MPS.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by the denial read delay in milliseconds each time
a capacity refresh request results in no additional capacity due to the connection’s maximum ingress
MPS budget being exhausted.
Measurement Scope: Per network, per NE, per MP server
Recovery:
Consistently high values in this measurement indicate that the ingress message rate on the Diameter
connection may be higher than the maximum ingress MPS value the connection was configured with.
When this measurement is incremented, it indicates that the per connection ingress MPS control feature
is throttling its rate of reading messages from the connection.
This measurement is not intended to measure how much delay is being introduced into the connection’s
ingress message processing; rather it is intended to give a general idea of how often per connection
ingress MPS control throttling is occurring due to exhaustion of the connection’s maximum ingress
MPS capacity.
Note: This measurement may also be incremented due to normal spikes in the ingress MPS rate.
Therefore occasional non-zero values or low values should not cause concern. If the ingress MPS rate
is truly too high, alarm-id 22328 should also be present for the connection.
No action required.
TmRxMPSDelay_SharedCapacity
Measurement Group: Connection Performance
Measurement Type: Simple
Description: Total amount of time in milliseconds that the connection experienced delay in ingress
message processing due to no capacity available in the DA MP’s Shared Pool.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by the denial read delay in milliseconds each time
a capacity refresh request results in no additional capacity due to lack of shared ingress MPS capacity
on the MP server that hosts the connection.
Measurement Scope: Per network, per NE, per MP server
Recovery:
Consistent non-zero values in this measurement indicate that the connection was delayed in reading
a message because there was no available shared ingress MPS capacity remaining on the MP server.
Connections use shared ingress MPS capacity when their maximum ingress MPS is configure higher
910-6528-001 Revision D, December 2012
260
Measurements
than their reserved ingress MPS and the actual rage of ingress traffic is higher than the reserved ingress
MPS value. When connections competing for shared ingress MPS capacity exhaust the MP server’s
licensed capacity, the per connection ingress MPS control feature delays the connection trying to read
an ingress message. When this occurs, this measurement is incremented.
When this measurement is non-zero for connections using shared capacity, it indicates that the MP
server is processing ingress messaging rates near or exceeding its licensed capacity. If this measurement
is only rarely non-zero, the delays are in response to spikes in the ingress messaging rate. This latter
condition can generally be ignored.
This measurement is not intended to measure how much delay is being introduced into the connection’s
ingress message processing; rather it is intended to give a general idea of how often per connection
ingress MPS control throttling is occurring due to exhaustion of the MP server’s shared ingress MPS
capacity.
Please look for alarm-id 22328 to determine if any one connection is using capacity well above its
configured maximum ingress MPS rate. Note, however, that it is possible for all connections to be
operating within their configured maximum ingress MPS rates, but the sum of those rates exceeds the
MP servers licensed MPS capacity.
No action required.
TXConnMsgs
Measurement Group: Connection Performance
Measurement Type: Simple
Description: The number of messages sent on the connection. This includes all Diameter messages,
both routable and non-routable.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is sent to the peer on the connection
Measurement Scope: Server Group
Recovery:
No action required.
TxConnOctets
Measurement Group: Connection Performance
Measurement Type: Simple
Description: The number of octets sent on the connection. This includes all Diameter messages, both
routable and non-routable.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is sent to the peer on the connection.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
261
Measurements
No action required.
TxConnSendBufAvg
Measurement Group: Connection Performance
Measurement Type: Average
Description: The average number of bytes in the SCTP/TCP send buffer. The SCTP/TCP send buffer
contains all bytes sent to the SCTP/TCP socket by the peer state machine which have not yet been
sent to the peer or have been sent to the peer and have not been unacknowledged.
Collection Interval: 5 min
Peg Condition: Periodically (currently once a second) the depth of the socket send buffer is measured
and the value used to update this measurement.
Measurement Scope: Server Group
Recovery:
1. If this measurement is at or above 80%, this may be an indication that the peer is unable to handle
the load it is presented with. Consider load-sharing with other Peer Nodes.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxConnSendBufPeak
Measurement Group: Connection Performance
Measurement Type: Max
Description: The peak number of bytes in the SCTP/TCP send buffer. The SCTP/TCP send buffer
contains all bytes sent to the SCTP/TCP socket by the peer state machine which have not yet been
sent to the peer or have been sent to the peer and have not been unacknowledged.
Collection Interval: 5 min
Peg Condition: Periodically (currently once a second) the depth of the socket send buffer is measured
and the value used to update this measurement.
Measurement Scope: Server Group
Recovery:
No action required.
TxPerConnQueueAvg
Measurement Group: Connection Performance
Measurement Type: Average
Description: The average Per Connection Egress Message Queue utilization (0-100%) measured during
the collection interval.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
262
Measurements
Peg Condition: The average of all Per Connection Egress Message Queue utilization samples taken
during the collection interval.
Measurement Scope: Server Group
Recovery:
1. An IP network or Diameter peer problem may exist that is preventing SCTP/TCP from transmitting
messages into the network at the same pace that messages are being received from the network.
2. The transport task associated with the connection may be experiencing a problem preventing it
from processing events from its Connection Event Message Queue. The alarm log should be
examined using the Alarms & Events page.
3. If one or more MPs in a server site have failed, the traffic will be distributed among the remaining
MPs in the server site. MP server status can be monitored using the Status & Manage > Server
page.
4. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP.
The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each
MP in the server site should be receiving approximately the same ingress transaction per second.
5. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
6. If the problem persists, contact the Tekelec Customer Care Center.
TxPerConnQueuePeak
Measurement Group: Connection Performance
Measurement Type: Max
Description: The peak Per Connection Egress Message Queue utilization (0-100%) measured during
the collection interval.
Collection Interval: 5 min
Peg Condition: The maximum Per Connection Egress Message Queue utilization sample taken during
the collection interval.
Measurement Scope: Server Group
Recovery:
1. An IP network or Diameter peer problem may exist that is preventing SCTP/TCP from transmitting
messages into the network at the same pace that messages are being received from the network.
2. The transport task associated with the connection may be experiencing a problem preventing it
from processing events from its Connection Event Message Queue. The alarm log should be
examined using the Alarms & Events page.
3. If one or more MPs in a server site have failed, the traffic will be distributed among the remaining
MPs in the server site. MP server status can be monitored using the Status & Manage > Server
page.
4. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP.
The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each
MP in the server site should be receiving approximately the same ingress transaction per second.
910-6528-001 Revision D, December 2012
263
Measurements
5. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
6. If the problem persists, contact the Tekelec Customer Care Center.
Diameter Signaling Router (DSR) Application Exception measurements
The "DSR Application Exception" measurement group is a set of measurements that provide information
about exceptions and unexpected messages and events that are specific to the DSR protocol.
Table 31: DSR Application Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxApplRequestNoRoutes
Number of Request messages
5 min
received from a DSR Application
that could not be routed.
RxApplUnavailable
Number of Request messages
5 min
received for a DSR Application
that could not be routed to the
DSR Application because it was
Unavailable.
RxApplUnavailableForRequest Number of Request messages
5 min
received for a DSR Application
which could not be routed to
DSR Application because it was
not available.
RxApplUnavailableForAnswer Number of Answer messages
5 min
received for a DSR Application
which could not be routed to
DSR Application because it was
not available.
TxFabrFullDRLRequestReject
The average Request Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
TxFabrFullDRLAnswerDiscard The number of egress Diameter 5 min
Answer messages that were
discarded because the DRL’s
Answer Queue was full.
TxRbarFullDRLRequestReject
Egress Request Messages
Rejected - DRL Request Queue
Full.
910-6528-001 Revision D, December 2012
5 min
264
Measurements
Measurement Tag
Description
Collection Interval
TxRbarFullDRLAnswerDiscard Egress Answer Messages
5 min
Discarded - DRL Answer Queue
Full.
RxApplRequestNoRoutes
Measurement Group: DSR Application Exception
Measurement Type: Simple
Description: Number of Request messages received from a DSR Application that could not be routed.
Collection Interval: 5 min
Peg Condition: When DRL successfully receives a Request message from s DSR Application that is
rejected with an Answer response because either a Peer Routing Rule was not found or implicit routing
could not be invoked.
Measurement Scope: Server Group
Recovery:
The DSR Application is forwarding Request messages that cannot be routed to a peer. The following
problems could exist:
• A Peer Routing Rule could be missing of incorrectly configured.
• The DSR Application could be incorrectly configured.
• The Request message from a downstream peer was mis-routed to the DSR.
1. Verify the Peer Routing Rules on the following GUI screen, and make any needed corrections.
Diameter>Configuration>Peer Routing Rules
2. Verify the DSR Application Id configuration on the following GUI screen, and make any needed
corrections.
Diameter>Configuration>Application Ids
RxApplUnavailable
Measurement Group: DSR Application Exception
Measurement Type: Simple
Description: Number of Request messages received for a DSR Application that could not be routed
to the DSR Application because the DSR Application was Unavailable.
Collection Interval: 5 min
Peg Condition: When DRL receives a Request message from s peer that matches an Application Routing
Rule, but cannot be routed to the DSR Application because its Operational Status is "Unavailable".
Measurement Scope: Server Group
Recovery:
The DSR Application Operational Status is "Unavailable" when one of the following conditions occurs:
910-6528-001 Revision D, December 2012
265
Measurements
• The operator has removed the DSR Application from service (Admin State is "Disabled".)
• The DSR Application was congested when an attempt to route a Request message to the SR
Application occurred.
When a DSR Application is "Unavailable", the message will be handled as defined by the "unavailability
Action" attribute for the DSR Application (see the GUI screen for the DSR Application).
1. Verify the DSR Application Admin State on the following GUI screen:
Diameter>Maintenance>Applications
2. Verify the DSR Application "Unavailability Action" attribute configuration on the following GUI
screen..
Diameter>Configuration>Application Ids
RxApplUnavailableForAnswer
Measurement Group: DSR Application Exception
Measurement Type: Simple
Description: Number of Answer messages received for a DSR Application which could not be routed
to DSR Application because it was not available.
Collection Interval: 5 min
Peg Condition: When DRL receives an Answer message from a peer associated with a PTR indicating
that the Answer response must be routed back to the DSR Application but cannot be routed to the
DSR Application because its Operational Status is “Unavailable.”
Measurement Scope: Server Group
Recovery:
A DSR Application’s Operational Status is “Unavailable” when one of the following conditions occur:
• The operator has removed the DSR Application from service (Admin State is “Disabled”)
• The DSR Application was congested when an attempt to route a Request message to the DSR
Application occurred.
When a DSR Application is "Unavailable", the message will be handled as defined by the "unavailability
Action" attribute for the DSR Application (see the GUI screen for the DSR Application).
1. Verify the DSR Application Admin State on the following GUI screen:
Diameter>Maintenance>Applications
2. Verify the DSR Application "Unavailability Action" attribute configuration on the following GUI
screen..
Diameter>Configuration>Application Ids
RxApplUnavailableForRequest
Measurement Group: DSR Application Exception
Measurement Type: Simple
910-6528-001 Revision D, December 2012
266
Measurements
Description: Number of Request messages received for a DSR Application which could not be routed
to DSR Application because it was not available.
Collection Interval: 5 min
Peg Condition: When DRL receives a Request message from a peer which matches a ART rule but
cannot be routed to the DSR Application because its Operational Status was not “Available”.
Measurement Scope: Server Group
Recovery:
A DSR Application’s Operational Status is “Unavailable” when one of the following conditions occur:
• The operator has removed the DSR Application from service (Admin State is “Disabled”)
• The DSR Application was congested when an attempt to route a Request message to the DSR
Application occurred.
When a DSR Application is "Unavailable", the message will be handled as defined by the "unavailability
Action" attribute for the DSR Application (see the GUI screen for the DSR Application).
1. Verify the DSR Application Admin State on the following GUI screen:
Diameter>Maintenance>Applications
2. Verify the DSR Application "Unavailability Action" attribute configuration on the following GUI
screen..
Diameter>Configuration>Application Ids
TxFabrFullDRLRequestReject
Measurement Group: DSR Application Exception
Measurement Type: Average
Description: The average Request Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Request Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. Display and monitor the DSR Application status by selecting Diameter>Maintenance>Applications.
Verify that the Admin State is set as expected.
The DSR Application's Request Message Queue Utilization is approaching its maximum capacity.
This alarm should not normally occur when no other congestion alarms are asserted.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting Diameter>Configuration >Application Routing Rules.
3. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Request Message Queue. Examine
the Alarm log in Alarms & Events
4. If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
267
Measurements
TxFabrFullDRLAnswerDiscard
Measurement Group: DSR Application Exception
Measurement Type: Simple
Description: The number of egress Diameter Answer messages that were discarded because the DRL’s
Answer Queue was full.
Collection Interval: 5 min
Peg Condition: For each Answer message discarded because the “All-Connections Event Queue” was
full.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the MPs may be unable to handle the network load.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. If the problem persists, contact the Tekelec Customer Care Center.
TxRbarFullDRLRequestReject
Measurement Group: DSR Application Exception
Measurement Type: Simple
Description: Number of egress Diameter Request messages that were rejected because the DRL's
Request Queue was full.
Collection Interval: 5 min
Peg Condition: When a Request message is discarded because the DRL's Request Queue is full.
Measurement Scope: Server Group
Recovery:
This measurement is primarily intended to assist in evaluating the need for additional Message
Processor (MP) processing capacity at a Network Element and indicates overall MP congestion is
occurring.
• If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
• If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element, then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
• If the problem persists, contact the Tekelec Customer Care Center.
910-6528-001 Revision D, December 2012
268
Measurements
TxRbarFullDRLAnswerDiscard
Measurement Group: DSR Application Exception
Measurement Type: Simple
Description: Number of egress Diameter Answer messages that were discarded because the DRL's
Answer Queue was full.
Collection Interval: 5 min
Peg Condition: When an Answer message is discarded because the All-Connections Event Queue is
full.
Measurement Scope: Server Group
Recovery:
This measurement is primarily intended to assist in evaluating the need for additional Message
Processor (MP) processing capacity at a Network Element and indicates overall MP congestion is
occurring.
• If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
• If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element, then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
• If the problem persists, contact the Tekelec Customer Care Center.
Diameter Signaling Router (DSR) Application Performance measurements
The "DSR Application Performance" measurement group is a set of measurements that provide
performance information that is specific to the DSR protocol. These measurements will allow the user
to determine how many messages are successfully forwarded and received to and from each DSR
Application.
Table 32: DSR Application Performance Measurement Report Fields
Measurement Tag
Description
RxApplAnswerFwdSuccess
Number of Answer messages
5 min
successfully forwarded to a DSR
Application
RxApplAnswerReceived
Number of Answer messages
5 min
received from a DSR Application
RxApplRequestFwdSuccess
Number of Request messages
5 min
successfully forwarded to a DSR
Application
910-6528-001 Revision D, December 2012
Collection Interval
269
Measurements
Measurement Tag
Description
RxApplRequestReceived
Number of Request messages
5 min
received from a DSR Application
RxCpaAnswerMsgQueueAvg
The average Answer Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxCpaAnswerMsgQueuePeak
The peak Answer Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxCpaAnswerProcessed
The total number of Answers
processed by DSR Application.
RxCpaEventMsgQueueAvg
The average CPA Application
5 min
Event Message Queue utilization
measured during the collection
interval.
RxCpaEventMsgQueuePeak
The peak CPA Application Event 5 min
Message Queue utilization
measured during the collection
interval.
RxCpaMsgRateAvg
The average DSR Application’s 5 min
Message Processing rate
measured during the collection
interval.
RxCpaMsgRatePeak
The peak DSR Application’s
5 min
Message Processing rate
measured during the collection
interval.
RxCpaRequestMsgQueueAvg
The average Request Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxCpaRequestMsgQueuePeak
The peak DSR Application’s
Request Message Queue
utilization (0-100%) measured
during the collection interval.
5 min
RxCpaRequestProcessed
The total number of Requests
processed by DSR Application.
5 min
RxFabrMsgRateAvg
The average DSR Application’s 5 min
Ingress Message Rate measured
during the collection interval.
910-6528-001 Revision D, December 2012
Collection Interval
5 min
270
Measurements
Measurement Tag
Description
Collection Interval
RxFabrMsgRatePeak
The peak DSR Application’s
5 min
Ingress Message Rate measured
during the collection interval.
RxFabrRequestMsgQueueAvg
The average Request Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxFabrRequestMsgQueuePeak
The peak DSR Application’s
Request Message Queue
utilization (0-100%) measured
during the collection interval.
RxFabrRequestProcessed
The number of Requests
5 min
processed by a DSR Application
during the collection interval.
RxRbarMsgRateAvg
DSR Application Message
Processing Rate
5 min
RxRbarMsgRatePeak
DSR Application Message
Processing Rate Peak
5 min
RxRbarRequestMsgQueueAvg
DSR Application Request
Message Queue Average
Utilization
5 min
5 min
RxRbarRequestMsgQueuePeak DSR Application Request
5 min
Message Queue Peak Utilization
RxRbarRequestProcessed
Total number of Requests
processed by DSR Application
5 min
TxApplTransSuccess
Number of Transactions initiated 5 min
by DSR Application that
successfully completed
TxCpaFullDRLAnswerReject
The number of egress Diameter 5 min
Answer messages that were
discarded because the DRL’s
Answer Queue was full.
TxCpaFullDRLRequestReject
The number of egress Diameter 5 min
Request messages that were
rejected because the DRL’s
Request Queue was full.
RxApplRequestFwdSuccess
Measurement Group: DSR Application Performance
Measurement Type: Simple
910-6528-001 Revision D, December 2012
271
Measurements
Description: Number of Request messages successfully forwarded to a DSR Application.
Collection Interval: 5 min
Peg Condition: When DRL successfully enqueues a Request message on the DSR Application’s internal
Message Queue.
Measurement Scope: Server Group
Recovery:
No action required.
RxApplAnswerFwdSuccess
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: Number of Answer messages successfully forwarded to a DSR Application.
Collection Interval: 5 min
Peg Condition: When DRL successfully enqueues an Answer message on the DSR Application’s
internal Message Queue.
Measurement Scope: Server Group
Recovery:
No action required.
RxApplRequestReceived
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: Number of Request messages received from a DSR Application.
Collection Interval: 5 min
Peg Condition: When DRL successfully receives a Request message from a DSR Application.
Measurement Scope: Server Group
Recovery:
No action required.
RxApplAnswerReceived
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: Number of Request messages received from a DSR Application.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
272
Measurements
Peg Condition: When DRL successfully receives a Request message from a DSR Application.
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaAnswerMsgQueueAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The average Answer Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Answer Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaAnswerMsgQueuePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
Description: The peak Answer Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The maximum Answer Message Queue utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaAnswerProcessed
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: The total number of Answers processed by DSR Application.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when a Diameter Answer is received.
910-6528-001 Revision D, December 2012
273
Measurements
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaEventMsgQueueAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The average CPA Application Event Message Queue utilization measured during the
collection interval.
Collection Interval: 5 min
Peg Condition: The average Event Message Queue utilization sample taken during the collection
interval.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaEventMsgQueuePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
Description: The peak CPA Application Event Message Queue utilization measured during the
collection interval.
Collection Interval: 5 min
Peg Condition: The maximum Event Message Queue utilization sample taken during the collection
interval.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaMsgRateAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The average DSR Application’s Message Processing rate measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all message processing rate samples taken during the collection interval.
Used for congestion control by DSR.
910-6528-001 Revision D, December 2012
274
Measurements
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaMsgRatePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
Description: The peak DSR Application’s Message Processing rate measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The maximum message processing rate sample taken during the collection interval.
Used for congestion control by DSR.
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaRequestMsgQueueAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The average Request Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Request Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaRequestMsgQueuePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
Description: The peak DSR Application’s Request Message Queue utilization (0-100%) measured
during the collection interval.
Collection Interval: 5 min
Peg Condition: The maximum Request Message Queue utilization sample taken during the collection
interval.
910-6528-001 Revision D, December 2012
275
Measurements
Measurement Scope: Server Group
Recovery:
No action required.
RxCpaRequestProcessed
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: The total number of Requests processed by DSR Application.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when a Diameter Request is received.
Measurement Scope: Server Group
Recovery:
No action required.
RxFabrMsgRateAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The average DSR Application’s Ingress Message Rate measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all DSR Application Ingress Message Rate samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. Verify the configuration using DiameterConfigurationApplication Routing Rules.
The Application Routing Table may be mis-configured and sending too much traffic to the DSR
Application.
2. Use Main MenuStatus & ManageKPI Display to monitor the ingress traffic rate of each MP.
The MPs may be unable to handle the network load. MPs are in a congestion state when the ingress
message rate to the MP is exceeding its capacity to process the messages.
3. If the problem persists, contact the Tekelec Customer Care Center.
RxFabrMsgRatePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
910-6528-001 Revision D, December 2012
276
Measurements
Description: The peak DSR Application’s Ingress Message Rate measured during the collection interval.
Collection Interval: 5 min
Peg Condition: The maximum DSR Application Ingress Message Rate sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. Verify the configuration using DiameterConfigurationApplication Routing Rules.
The Application Routing Table may be mis-configured and sending too much traffic to the DSR
Application.
2. Use Main MenuStatus & ManageKPI Display to monitor the ingress traffic rate of each MP.
The MPs may be unable to handle the network load. MPs are in a congestion state when the ingress
message rate to the MP is exceeding its capacity to process the messages.
3. If the problem persists, contact the Tekelec Customer Care Center.
RxFabrRequestMsgQueueAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The average Request Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Request Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. Display and monitor the DSR Application status by selecting Diameter>Maintenance>Applications.
Verify that the Admin State is set as expected.
The DSR Application's Request Message Queue Utilization is approaching its maximum capacity.
This alarm should not normally occur when no other congestion alarms are asserted.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting Diameter>Configuration >Application Routing Rules.
3. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Request Message Queue. Examine
the Alarm log in Alarms & Events
4. If the problem persists, contact the Tekelec Customer Care Center.
RxFabrRequestMsgQueuePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
910-6528-001 Revision D, December 2012
277
Measurements
Description: The peak DSR Application’s Request Message Queue utilization (0-100%) measured
during the collection interval.
Collection Interval: 5 min
Peg Condition: The maximum Request Message Queue utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. Display and monitor the DSR Application status by selecting Diameter>Maintenance>Applications.
Verify that the Admin State is set as expected.
The DSR Application's Request Message Queue Utilization is approaching its maximum capacity.
This alarm should not normally occur when no other congestion alarms are asserted.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting Diameter>Configuration >Application Routing Rules.
3. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Request Message Queue. Examine
the Alarm log in Alarms & Events
4. If the problem persists, contact the Tekelec Customer Care Center.
RxFabrRequestProcessed
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: The number of Requests processed by a DSR Application during the collection interval.
Collection Interval: 5 min
Peg Condition: For each Request message successfully de-queued from the DSR Application’s Request
Message queue.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarMsgRateAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: Average DSR Application's Ingress Message Rate measured during the collection interval
Collection Interval: 5 min
Peg Condition: When the average of all DSR Application Ingress Message Rate samples is taken during
the collection interval.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
278
Measurements
Recovery:
1. Display and monitor the DSR Application message rate by selecting
DiameterMaintenanceApplications. Verify that the message rate is set as expected.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting DiameterConfigurationApplication Routing Rules.
3. There might be an insufficient number of MPs configured to handle the network load. Monitor the
traffic rate of each MP by selecting DiameterStatus & ManageKPI Display.
If MPs are in a congestion state, then the offered load to the server site is exceeding its capacity.
4. If the problem persists, contact the Tekelec Customer Care Center.
RxRbarMsgRatePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
Description: Peak DSR Application's Ingress Message Rate measured during the collection interval
Collection Interval: 5 min
Peg Condition: When the maximum DSR Application Ingress Message Rate sample is taken during
the collection interval.
Measurement Scope: Server Group
Recovery:
1. Display and monitor the DSR Application message rate by selecting
DiameterMaintenanceApplications. Verify that the message rate is set as expected.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting DiameterConfigurationApplication Routing Rules.
3. There might be an insufficient number of MPs configured to handle the network load. Monitor the
traffic rate of each MP by selecting DiameterStatus & ManageKPI Display.
If MPs are in a congestion state, then the offered load to the server site is exceeding its capacity.
4. If the problem persists, contact the Tekelec Customer Care Center.
RxRbarRequestMsgQueueAvg
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: Average Request Message Queue utilization (0-100%) measured during the collection
interval
Collection Interval: 5 min
Peg Condition: When the average of all Request Message Queue utilization samples is taken during
the collection interval.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
279
Measurements
1. Display and monitor the DSR Application status by selecting DiameterMaintenanceApplications.
Verify that the Operational Reason, which indicates congestion level, is set as expected.
The DSR Application's Request Message Queue Utilization is approaching its maximum capacity.
This alarm should not normally occur when no other congestion alarms are asserted.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting DiameterConfigurationApplication Routing Rules.
3. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Request Message Queue. Examine
the Alarm log in Alarms & Events
4. If the problem persists, contact the Tekelec Customer Care Center.
RxRbarRequestMsgQueuePeak
Measurement Group: DSR Application Performance
Measurement Type: Max
Description: Peak DSR Application's Request Message Queue utilization (0-100%) measured during
the collection interval
Collection Interval: 5 min
Peg Condition: When the maximum Request Message Queue utilization sample is taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. Display and monitor the DSR Application status by selecting DiameterMaintenanceApplications.
Verify that the Operational Reason, which indicates congestion level, is set as expected.
The DSR Application's Request Message Queue Utilization is approaching its maximum capacity.
This alarm should not normally occur when no other congestion alarms are asserted.
2. Application Routing might be mis-configured and is sending too much traffic to the DSR Application.
Verify the configuration by selecting DiameterConfigurationApplication Routing Rules.
3. If no additional congestion alarms are asserted, the DSR Application Task might be experiencing
a problem that is preventing it from processing message from its Request Message Queue. Examine
the Alarm log in Alarms & Events
4. If the problem persists, contact the Tekelec Customer Care Center.
RxRbarRequestProcessed
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: Number of Requests processed by a DSR Application during the collection interval
Collection Interval: 5 min
Peg Condition: When a Request message is successfully de-queued from the DSR Application's Request
Message queue.
910-6528-001 Revision D, December 2012
280
Measurements
Measurement Scope: Server Group
Recovery:
No action required.
TxApplTransSuccess
Measurement Group: DSR Application Performance
Measurement Type: Simple
Description: Number of Request messages received from a DSR Application.
Collection Interval: 5 min
Peg Condition: When DRL successfully receives a Request message from a DSR Application.
Measurement Scope: Server Group
Recovery:
No action required.
Diameter Egress Transaction measurements
The Diameter Egress Transaction measurement report contains measurements providing information
about Diameter peer-to-peer transactions forwarded to upstream peers.
Table 33: Diameter Egress Transaction Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxAnswerExpectedAll
Number of valid Answer
messages received from an
upstream peer that were
associated with a pending
transaction.
5 min
RxAnswerMsgQueueFullDiscard The number of ingress Diameter 5 min
Answer messages that were
discarded because the Answer
Message Queue was full.
TxAnswerTimeout
Number of times that an Answer 5 min
response was not received from
a peer before the maximum
allowed time
PENDING_ANSWER_TIMER.
TxConnAnswerMsgs
Number of routable Answer
messages successfully sent on
the connection.
910-6528-001 Revision D, December 2012
5 min
281
Measurements
Measurement Tag
Description
Collection Interval
TxConnectionFailed
Egress peer-to-peer transactions 5 min
aborted by a Local Node connection failure.
TxConnRequestMsgs
Number of routable Request
messages successfully sent on
the connection.
5 min
TxRequestSuccessAllConn
Number of Request messages
successfully routed to a peer.
5 min
RxAnswerExpectedAll
Measurement Group: Diameter Egress Transaction, Diameter Performance
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were associated
with a pending transaction.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer message event with a valid transport connection
ID for which a pending transaction is found.
The connection measurement is associated with the connection from which the Answer message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxAnswerMsgQueueFullDiscard
Measurement Group: Diameter Egress Transaction, Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter Answer messages that were discarded because the
Answer Message Queue was full.
Collection Interval: 5 min
Peg Condition: For each Answer message discarded because the Answer Message Queue was full.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
910-6528-001 Revision D, December 2012
282
Measurements
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TxAnswerTimeout
Measurement Group: Diameter Egress Transaction
Measurement Type: Simple
Description: The number of times that an Answer response was not received from a peer before the
maximum allowed time PENDING-ANSWER-TIMER.
Answer timeouts can be caused by a variety of reasons:
• The peer associated with this connection may be experiencing congestion, causing delays in sending
the Answer response.
• IP Network congestion.
• If the peer associated with this connection is a Diameter Relay Agent, then an upstream node from
the peer may be experiencing congestion, causing delays in sending the Answer response.
Collection Interval: 5 min
Peg Condition: When timer PENDING-ANSWER-TIMER expires.
The connection measurement is associated with the connection from which the corresponding Request
message was sent.
Measurement Scope: Server Group
Recovery:
1. If the user-configurable answer response timer is set too low it can cause the timer to expire before
a Answer response is received. The user-configurable value is set using the page Diameter >
Configuration > System Options.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxConnAnswerMsgs
Measurement Group: Diameter Egress Transaction, Diameter Performance
Measurement Type: Simple
Description: The number of routable Answer messages successfully sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter Answer message is sent to the peer.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
283
Measurements
TxConnectionFailed
Measurement Group: Diameter Egress Transaction
Measurement Type: Simple
Description: The number of times that a pending peer-to-peer transaction was abandoned due to a
transport connection failure.
Collection Interval: 5 min
Peg Condition: When a pending transaction is rerouted due to a transport connection failure.
This connection measurement is associated with the connection to which the corresponding Request
message was sent.
Measurement Scope: Server Group
Recovery:
1. Connection status can be monitored using the Diameter > Maintenance > Connections page.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxConnRequestMsgs
Measurement Group: Diameter Egress Transaction, Diameter Performance
Measurement Type: Simple
Description: The number of routable Request messages successfully sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter request message is sent to the peer.
Measurement Scope: Server Group
Recovery:
No action required.
TxRequestSuccessAllConn
Measurement Group: Diameter Egress Transaction
Measurement Type: Simple
Description: The number of Request messages successfully routed to a peer.
Collection Interval: 5 min
Peg Condition: When the DSR successfully queues a Request message to the DCL.
The connection measurement is associated with the connection to which the Request message was
sent.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
284
Measurements
No action required.
Diameter Exception measurements
The Diameter Exception measurement report contains measurements that provide information about
exceptions and unexpected messages and events that are specific to the Diameter protocol.
Table 34: Diameter Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
EvApplIdListInconsistency
Number of times that the
supported Application IDs
received from the Peer were
Inconsistent with another
Transport Connection
5 min
EvConnCeaIdValFail
The number of times the
5 min
connection was closed due to
CEA Realm/Host validation for
locally initiated connections.
Note: CER Realm/Host
validation failures are tracked
via the EvConnCerIdValFail
measurement and are NOT
included in this measurement.
EvConnCexTO
Number of times the connection 5 min
timed out waiting for the peer to
send a CER or CEA.
EvConnDpaTO
The number of times the
5 min
connection timed out waiting for
the peer to send a DPA.
EvConnNoComnApps
Number of times the connection 5 min
was closed due to there being no
common application IDs existing
between the local and peer
nodes.
EvConnPrvFail
Number of times the connection 5 min
was closed after failing to
successfully complete the
proving phase.
EvConnRejected
Number of times the connection 5 min
was rejected. Reasons include IP
addresss validation failure, the
connection already established,
910-6528-001 Revision D, December 2012
285
Measurements
Measurement Tag
Description
Collection Interval
and connection Administratively
Disabled.
EvConnRejInsufficientIngressMps The number of times DA-MP
5 min
rejected a Diameter connection
due to insufficient Ingress MPS
on the DA-MP to support the
Reserved Ingress MPS
configured for the connection.
EvConnRejMaxConnExceeded
The number of times DA-MP
5 min
rejected a Diameter connection
due to the DA-MP exceeding its
maximum number of supported
Diameter connections.
EvConnWdFail
Number of times the Diameter 5 min
Watchdog algorithm closed the
connection due to no traffic
received from the peer within
Tw*2 time after a DWR was sent.
EvConnWdSuspect
Number of times the Diameter 5 min
Watchdog algorithm declared
the connection suspect due to no
traffic received from the peer
within Tw time after a DWR was
sent.
EvMpCerIdValFail
The number of times the
5 min
connection was closed due to
CER Realm/Host validation for
peer initiated connections.
EvTransLifetimeExceededMp
Number of transaction failures 5 min
because “Transaction Lifetime”
exceeded.
RxAnswerMsgQueueFullDiscard The number of ingress Diameter 5 min
Answer messages that were
discarded because the Answer
Message Queue was full.
RxAnswerUnexpected
Number of valid Answer
5 min
messages received from an
upstream peer that could not be
associated with a pending
transaction
RxConnCeaError
Number of CEA error messages 5 min
received on the connection.
910-6528-001 Revision D, December 2012
286
Measurements
Measurement Tag
Description
Collection Interval
RxConnFailMalfMsg
Number of messages received
on the connection which were
malformed. Malformed
messages cause the connection
to be closed.
5 min
RxConnInvalidMsg
Number of messages received
on the connection which had a
semantic error. Messages with
semantic errors are discarded.
5 min
RxConnUnexpCex
Number of unexpected
5 min
CER/CEA messages received on
the connection.
RxConnUnexpDpx
Number of unexpected
5 min
DPR/DPA messages received on
the connection.
RxConnUnexpDwx
Number of unexpected
5 min
DWR/DWA messages received
on the connection.
RxMaxMpsRejectConn
The number of ingress Diameter 5 min
messages that were rejected
because of the MP Maximum
MPS limitation and an Answer
response was sent.
RxMaxMpsRejectMp
The number of ingress Diameter 5 min
messages that were rejected
because of MP Maximum MPS
limitation and an Answer
response was sent.
RxMpCongestionDiscardMp
The number of ingress Diameter 5 min
Request messages received that
were discarded or rejected
because of local MP congestion.
RxMpCongestionRejectConn
The number of ingress Diameter 5 min
messages that were discarded
because of local MP congestion
and an Answer response was
sent.
RxMpCongestionRejectMp
The number of ingress Diameter 5 min
messages that were discarded
because of Local MP Congestion
and an Answer response was
sent.
910-6528-001 Revision D, December 2012
287
Measurements
Measurement Tag
Description
Collection Interval
RxPduPoolEmptyDiscard
The number of Diameter
messages that were discarded
because no PDU Buffers were
available.
5 min
RxRoutableRejectMsgsMp
The number of ingress Diameter 5 min
Request messages received that
are rejected by MP with Error
Answer due to MP Overload
Control or Maximum IMR
Limitation.
TmConnDegraded
Total time (in seconds) during
the reporting period that the
connection state was in the
Degraded state.
5 min
TmConnEnabledNotAvail
Total time (in seconds) during
the reporting period that the
connection state was
Administratively Enabled and
the connection state was not
Available.
5 min
TxAllConnQueueFullAnswerDiscard The number of egress Diameter 5 min
Answer messages that were
discarded because the
All-Connections Event Queue
was full and an Answer response
was sent.
TxConnCeaError
Number of CEA error messages 5 min
sent on the connection.
TxReqMsgApplMismatch
Number of times message
routing detected application
mismatch
TxReqMsgPerConnPtrMax
Number of times message
5 min
routing bypassed the connection
because the maximum allowed
pending transactions was
exceeded
TxRequestEgressLoop
Outgoing message loops
detected
5 min
5 min
EvApplIdListInconsistency
Measurement Group: Diameter Exception
Measurement Type: Simple
910-6528-001 Revision D, December 2012
288
Measurements
Description: Number of times that the supported Application IDs received from the peer were
inconsistent with another transport connection.
Collection Interval: 5 min
Peg Condition: If the Application ID list received from the DSR for a peer's transport connection is
not identical to the Application ID list for at least one of the transport connections for a peer that has
an Operation Status state of Available.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the DSR may be experiencing a problem preventing
it from processing events from its All-Connections Event Queue. The alarm log should be examined
using the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
EvConnCeaIdValFail
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection was closed due to CEA Realm/Host validation for
locally initiated connections.
Collection Interval: 5 min
Peg Condition: Pegged when a CEA message is received on the connection that has an Origin-Host
AVP value that does not match the FQDN configured for the peer, or an Origin-Realm AVP value
that does not match the realm configured for the peer.
Measurement Scope: Server Group
Recovery:
1. Examine the Origin-Host and Origin-Realm AVP values in the CEA sent by the peer.
2. Either change the FQDN/Realm configured for the peer to match this value, or change the peer so
that it sends Origin-Host/Origin-Realm AVP values that match the peer FQDN/Realm
configuration.
3. Contact the Tekelec Customer Care Center for assistance if needed.
910-6528-001 Revision D, December 2012
289
Measurements
EvConnCexTO
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection timed out waiting for the peer to send a CEx.
Collection Interval: 5 min
Peg Condition: Pegged when a peer initiated a connection and fails to send a CER within Tcex (from
the Connection Configuration Set) seconds of the socket connection being established, or when the
DSR initiates a connection and the peer fails to send a CEA within Tcex (from the Connection
Configuration Set) seconds of the DSR sending a CER.
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it did not send the appropriate CEx message.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnDpaTO
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection timed out waiting for the peer to send a DPA.
Collection Interval: 5 min
Peg Condition: Pegged when a peer fails to send a DPA within Tdpx (from the Connection
Configuration Set) seconds of the DSR sending a DPR.
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it did not respond to the DPR message that the DSR sent to it.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnNoComnApps
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection was closed due to there being no common Application
IDs existing between the Local and Peer Nodes.
Collection Interval: 5 min
Peg Condition: Pegged when a CEx message is received on the connection that has
1. No Application IDs specified (when in Relay mode), or
2. No Application IDs in common with those configured for the local node or
910-6528-001 Revision D, December 2012
290
Measurements
3. If any of the Application IDs marked as ‘MUST exist in Peer CEx’, in the CEx Cfg Set of that
connection object, is not present in the CEx message
Measurement Scope: Server Group
Recovery:
Verify that either the Auth-Application-ID, the Acct-Application-ID, or the
Vendor-Specific-Application-ID AVPs are present in the CEx message sent by the peer.
EvConnPrvFail
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection was closed after failing to successfully complete the
proving phase.
Collection Interval: 5 min
Peg Condition: Pegged when a peer fails a proving period.
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it did not respond in a timely fashion to the DWRs sent during
the proving period.
2. Consider increasing the Proving Timer in the Connection Configuration Set for the connection to
allow more time for the peer to respond to DWRs.
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnRejected
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection was rejected. Reasons include IP address validation
failure, the connection already established, and connection administratively disabled.
Collection Interval: 5 min
Peg Condition: Pegged when a connection is rejected for any reason.
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History to determine the specific reason(s) for the connection being rejected.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnRejInsufficientIngressMps
Measurement Group: Diameter Exception
910-6528-001 Revision D, December 2012
291
Measurements
Measurement Type: Simple
Description: The sum of the Reserved Ingress MPS for the added connection and MP Reserved Ingress
MPS has exceeded the MP Maximum Reserved Ingress MPS. The number of times DA-MP rejected a
Diameter connection due to insufficient Ingress MPS on the DA-MP to support the Reserved Ingress
MPS configured for the connection.
Collection Interval: 5 min
Peg Condition: This measurement is incremented for each Diameter connection that was rejected.
Measurement Scope: Server Group
Recovery:
1. The value for Reserved Ingress MPS for the added connection needs to be examined to determine
if its value should be decreased.
2. Contact the Tekelec Customer Care Center for assistance.
EvConnRejMaxConnExceeded
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The maximum number of active Diameter connections supported by a DA-MP has been
exceeded. The number of times DA-MP rejected a Diameter connection due to the DA-MP exceeding
its maximum number of supported Diameter connections.
Collection Interval: 5 min
Peg Condition: This measurement is incremented for each Diameter connection that is rejected by a
DA-MP.
Measurement Scope: Server Group
Recovery:
1. If the DA-MP is a member of a IPFE TS, verify that the IPFE is configured to fully monitor the
DA-MP’s availability status.
When a IPFE fully monitors application servers in a IPFE TS, it will cease from distributing new
Diameter connections to any/all application servers that report a “Stasis” availability status.
2. If the problem persists, contact the Tekelec Customer Care Center.
EvConnWdFail
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the Diameter watchdog algorithm closed the connection due to no
traffic received from the peer within Tw*2 seconds after a DWR was sent.
Collection Interval: 5 min
Peg Condition: Pegged when no messages were received from the peer within Tw*2 seconds of sending
a DWR to the peer.
910-6528-001 Revision D, December 2012
292
Measurements
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it is not responding to requests.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvConnWdSuspect
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the Diameter watchdog algorithm declared the connection suspect
due to no traffic received from the peer within Tw seconds after a DWR was sent.
Collection Interval: 5 min
Peg Condition: Pegged when no Diameter messages are received on the connection for Tw seconds
after a DWR was sent to the peer.
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it is not responding to requests.
2. Contact the Tekelec Customer Care Center for assistance if needed.
EvMpCerIDValFail
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times the connection was closed due to CER Realm/Host validation for
peer initiated connections.
Collection Interval: 5 min
Peg Condition: Pegged when the value Origin-Host and/or Origin-Realm AVPs sent by the peer in
its CER message do not match the values provisioned for the connection.
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History to determine the Origin Host and Realm sent by the peer.
2. Compare these values to those configured in the Peer Node object for this connection. These values
must match in order for the peer connection to be validated.
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvTransLifetimeExceededMp
Measurement Group: DSR Application Exception
Measurement Type: Simple
910-6528-001 Revision D, December 2012
293
Measurements
Description: Number of transaction failures because “Transaction Lifetime” exceeded.
Collection Interval: 5 min
Peg Condition: When the DRL was prevented from rerouting a Request message because the
“Transaction Lifetime” was exceeded.
Measurement Scope: Site
Recovery:
No action required.
RxAnswerMsgQueueFullDiscard
Measurement Group: Diameter Egress Transaction, Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter Answer messages that were discarded because the
Answer Message Queue was full.
Collection Interval: 5 min
Peg Condition: For each Answer message discarded because the Answer Message Queue was full.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxAnswerUnexpected
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were associated
with a pending transaction.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer message event with a valid transport connection
ID for which a pending transaction is found.
The connection measurement is associated with the connection from which the Answer message was
received.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
294
Measurements
Recovery:
No action required.
RxConnCeaError
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of CEA error messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a CEA message with a non-success response code is received on the
connection.
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History to determine why the connection is being rejected.
2. Contact the Tekelec Customer Care Center for assistance if needed.
RxConnFailMalfMsg
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of messages received on the connection which were malformed. Malformed
messages cause the connection to be closed.
Collection Interval: 5 min
Peg Condition: Pegged when a message is received on the connection that cannot be decoded.
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History and find event 22302 for this connection.
2. Examine the displayed message bytes for errors. Monitor the connection for invalid Diameter
messages.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxConnInvalidMsg
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of messages received on the connection which had a semantic error. Messages
with semantic errors are discarded.
Collection Interval: 5 min
Peg Condition: Pegged when a message is received on the connection that cannot be decoded.
910-6528-001 Revision D, December 2012
295
Measurements
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History and find event 22311 for this connection.
2. Examine the displayed message bytes for errors.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxMaxMpsRejectConn
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter messages that were rejected because of the MP Maximum
MPS limitation and an Answer response was sent.
Collection Interval: 5 min
Peg Condition: For each ingress Diameter message discarded because of the MP Maximum MPS
limitation and an Answer response was sent.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. The MP is approaching or exceeding its maximum configured MPS limitation. If this value is not
set to the MP's engineered traffic handling capacity, then the maximum MPS capacity allowed may
need to be changed. Contact Tekelec Customer Care Center for assistance.
2. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
3. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
5. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
6. If the problem persists, contact the Tekelec Customer Care Center.
RxMpCongestionDiscardMp
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter Request messages received that were discarded or
rejected because of local MP congestion.
910-6528-001 Revision D, December 2012
296
Measurements
Collection Interval: 5 min
Peg Condition: For each ingress Diameter Request message discarded because of local MP congestion.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxMpCongestionRejectConn
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter messages that were discarded because of local MP
congestion and an Answer response was sent.
Collection Interval: 5 min
Peg Condition: For each ingress Diameter message that was discarded because of local MP congestion
and an Answer response was sent.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
910-6528-001 Revision D, December 2012
297
Measurements
5. If the problem persists, contact the Tekelec Customer Care Center.
RxMpCongestionRejectMp
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter messages that were discarded because of Local MP
Congestion and an Answer response was sent.
Collection Interval: 5 min
Peg Condition: Pegged for each message discarded with "Drop Message & Send Response".
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter Process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxConnUnexpCex
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of unexpected CER/CEA messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a CER/CEA message is received on the connection after the capabilities
exchange has been completed. Pegged when a CER is expected from the peer and a CEA received, or
vice versa.
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History and find event 22308 for this connection to determine the reason that
the CEx was unexpected.
2. Contact the Tekelec Customer Care Center for assistance if needed.
910-6528-001 Revision D, December 2012
298
Measurements
RxConnUnexpDpx
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of unexpected DPR/DPA messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DPx message is received on the connection before the capabilities
exchange has been completed, or when a DPA is received without a DPR being sent to it.
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it is sending non-CEx messages before the capabilities exchange
is complete, or why it is sending a DPA without receiving a DPR.
2. Contact the Tekelec Customer Care Center for assistance if needed.
RxConnUnexpDwx
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of unexpected DWR/DWA messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DWx message is received on the connection before the capabilities
exchange has been completed.
Measurement Scope: Server Group
Recovery:
1. Examine the peer to determine why it is sending non-CEx messages before the capabilities exchange
is complete.
2. Contact the Tekelec Customer Care Center for assistance if needed.
RxMaxMpsRejectMp
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter messages that were rejected because of MP Maximum
MPS limitation and an Answer response was sent.
Collection Interval: 5 min
Peg Condition: Pegged for each message discarded with "Drop Message & Send Response".
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
299
Measurements
1. The MP is approaching or exceeding its maximum configured MPS limitation. If this value is not
set to the MP's engineered traffic handling capacity, then the maximum MPS capacity allowed may
need to be changed. Contact Tekelec Customer Care Center for assistance.
2. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
3. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
5. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
6. If the problem persists, contact the Tekelec Customer Care Center.
RxPduPoolEmptyDiscard
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of Diameter messages that were discarded because no PDU buffers were
available.
Collection Interval: 5 min
Peg Condition: For each Diameter message discarded.
The connection measurement is associated with the connection the message was received from.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurements for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP when the Ingress
Message Rate and/or Diameter Process CPU Utilization measurements are below the recommended
maximum engineered capacity of an MP, then a network (IP or Diameter) problem may exist.
Looking at these measurements on a time of day basis may provide additional insight into potential
network problems.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific software problem may exist (e.g., a buffer pool leak).
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxRoutableRejectMsgsMp
Measurement Group: Diameter Exception
Measurement Type: Simple
910-6528-001 Revision D, December 2012
300
Measurements
Description: The number of ingress Diameter Request messages received that are rejected by MP with
Error Answer due to MP Overload Control or Maximum IMR Limitation.
Collection Interval: 5 min
Peg Condition: Pegged for each Request message that is rejected.
Measurement Scope: Server Group
Recovery:
1. The MP is approaching or exceeding its maximum configured MPS limitation. If this value is not
set to the MP's engineered traffic handling capacity, then the maximum MPS capacity allowed may
need to be changed. Contact Tekelec Customer Care Center for assistance.
2. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
3. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
5. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
6. If the problem persists, contact the Tekelec Customer Care Center.
TmConnDegraded
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: Total time (in seconds) during the reporting period that the connection state was in the
Degraded state.
Collection Interval: 5 min
Peg Condition: Pegging started when a peer enters the Degraded state. Pegging stopped when the
peer enters the Available or Unavailable state.
A peer may be degraded for short periods of time (< 30 seconds) due to being in a proving period or
during a graceful disconnect; degraded conditions lasting longer periods of time are most likely due
to local congestion.
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive amount of time spent in the degraded state, examine
the Alarm History to determine the cause of the degraded condition.
2. Contact the Tekelec Customer Care Center for assistance if needed.
910-6528-001 Revision D, December 2012
301
Measurements
TmConnEnabledNotAvail
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: Total time (in seconds) during the reporting period that the connection state was
administratively enabled and the connection state was not Available.
Collection Interval: 5 min
Peg Condition: Pegging is started when a peer is enabled or when a peer disconnects. Pegging is
stopped when the peer connects and completes capabilities exchange, or when the connection is
disabled.
Measurement Scope: Server Group
Recovery:
1. Examine the Alarm History to determine if the connection is being rejected by either end, and for
notification of local congestion.
2. Make sure the peer is running.
3. If the connection is configured as a Responder connection, make sure that the peer is attempting
to initiate a connection.
4. If the connection is an Initiator connection, make sure that the peer is listening on the configured
port.
5. Contact the Tekelec Customer Care Center for assistance if needed.
TxAllConnQueueFullAnswerDiscard
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of egress Diameter Answer messages that were discarded because the
All-Connections Event Queue was full.
Collection Interval: 5 min
Peg Condition: For each Answer message discarded because the All-Connections Event Queue was
full.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
910-6528-001 Revision D, December 2012
302
Measurements
TxConnCeaError
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of CEA error messages sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a CEA message with a non-success response code is sent on the connection.
Measurement Scope: Server Group
Recovery:
1. Examine the alarm history to determine why the connection is being rejected.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxReqMsgApplMismatch
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times a selected egress peer was not selected because it does not support
the target Application ID in the message header.
Collection Interval: 5 min
Peg Condition: Each time the DSR bypasses a transport connection during route selection because the
Application ID in the Request message does not match one of the Application IDs received from the
peer on the transport connection during the Diameter Capabilities Exchange procedure.
The connection measurement is associated with the egress connection to which an Application ID was
not supported for routing the message.
Measurement Scope: Server Group
Recovery:
Contact the Tekelec Customer Care Center for assistance if needed.
TxReqMsgPerConnPtrMax
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times message routing bypassed the connection because the maximum
allowed pending transactions was exceeded.
Collection Interval: 5 min
Peg Condition: Each time the DSR bypasses a transport connection during route selection because the
maximum number of pending transactions allowed for the connection was exceeded.
The connection measurement is pegged against the egress connection with the maximum number of
pending transactions condition which prevented message routing.
910-6528-001 Revision D, December 2012
303
Measurements
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the DSR may be experiencing a problem preventing
it from processing messages from its Request Message Queue. The alarm log should be examined
from the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
TxRequestEgressLoop
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of times that a selected route associated with an egress peer was not selected
because a forwarding loop would occur (i.e., the upstream peer has already processed the Request
message as determined by the Route-Record AVPs).
Collection Interval: 5 min
Peg Condition: Each time the DSR bypasses a peer during route selection because the peer's FQDN
matches one of the FQDNs in the message's Route-Record AVPs.
The connection measurement is associated with the first connection assigned to the peer.
Note: This failure is associated with the peer, not any particular connection. The measurement should
always be pegged against the same peer connection, i.e., the first one assigned to the peer.
Measurement Scope: Server Group
Recovery:
Contact the Tekelec Customer Care Center for assistance if needed.
Diameter Ingress Transaction Exception measurements
The Diameter Ingress Transaction Exception report group contains measurements providing information
about exceptions associated with the routing of Diameter transactions received from downstream
peers.
910-6528-001 Revision D, December 2012
304
Measurements
Table 35: Diameter Ingress Transaction Exception Measurement Report Fields
Measurement Tag
Description
RxAnsFwdFailed
The number of times an ingress 5 min
Diameter Answer message could
not be forwarded to the
appropriate DA-MP, because the
DA-MP was unavailable or
congested.
RxDecodeFailure
Number of Request messages
5 min
rejected from a downstream peer
because the message could not
be decoded.
RxMaxMpsDiscardConn
Number of ingress Diameter
5 min
Request messages received on a
connection that were discarded
because of MP Maximum MPS
limitation.
RxMaxMpsDiscardMp
The number of ingress Diameter 5 min
Request messages received on a
connection that were discarded
because of Local MP Congestion
without Error Answer.
RxMessageLooping
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node because
message looping was detected
(FQDN of the Local Node
associated with the ingress
transport connection matched a
FQDN in the messages'
Route-Record AVPs).
RxMpCongestionDiscard
Number of ingress Diameter
5 min
Request messages received on a
connection that were discarded
because of local MP congestion.
RxNoRoutesFound
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node because no
routes were available for routing
the message.
RxNoRulesFailure
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node because no Peer
Routing Rule was found.
910-6528-001 Revision D, December 2012
Collection Interval
305
Measurements
Measurement Tag
Description
RxPrtRuleRejection
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node because a peer
routing rule ACTION is set to
"Send Answer".
RxRejectedAll
Number of Request messages
5 min
rejected from a downstream peer
by a Local Node (all reasons).
RxRejectedOther
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node for any reason
other than those identified by
other measurements.
RxRequestMsgQueueFullDiscard Number of ingress Diameter
Request messages that were
discarded because the Request
Message Queue was full.
Collection Interval
5 min
RxRoutableDiscardedMsgsMp
The number of ingress Diameter 5 min
Request messages received that
are discarded by MP without
Error Answer due to MP
Overload Control or Maximum
IMR Limitation.
RxTransactionTimeout
Number of Request messages
5 min
from a downstream peer rejected
by a Local Node because
maximum message reroutes
exceeded.
TxAllConnQueueFullRequestReject Number of egress Diameter
Request messages that were
rejected because the
All-Connections Event Queue
was full.
5 min
TxPerConnQueueFullAnswerDiscard Number of egress Answer
5 min
messages that were discarded
because the Per Connection
Egress Message Queue was full.
TxPerConnQueueFullRequestDiscard Number of egress Request
5 min
messages that were discarded
because the Per Connection
Egress Message Queue was full.
TxPtrPoolEmpty
Number of ingress Diameter
Request messages that were
910-6528-001 Revision D, December 2012
5 min
306
Measurements
Measurement Tag
Description
Collection Interval
discarded because no PTR
Buffers were available.
TxRerouteQueueFullReject
Number of egress Diameter
Request messages that were
rejected because the Reroute
Queue was full.
5 min
RxAnsFwdFailed
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of times an ingress Diameter Answer message could not be forwarded to
the appropriate DA-MP, because the DA-MP was unavailable or congested.
Collection Interval: 5 min
Peg Condition: This peg is incremented when a DA-MP receives a Diameter Answer message, identifies
the DA-MP that holds the pending transaction, however finds that the DA-MP is unavailable or
congested.
Measurement Scope: Server Group
Recovery:
If this measurement is seen to be incrementing consistently, contact the Tekelec Customer Care
Center.
This measurement should be pegged, only when the DSR process on the destination DA-MP is
Unavailable or the DA-MP is rebooting.
RxDecodeFailure
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: Number of Request messages rejected from a downstream peer because the message
could not be decoded.
Collection Interval: 5 min
Peg Condition:Request message from a downstream peer is rejected by a Local Node because it could
not be decoded.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
307
Measurements
1. These protocol violations are caused by the originator of the message (identified by the Origin-Host
AVP in the message) or the peer that forwarded the message to this node (identified by the peer
name) and cannot be fixed using the application.
2. Contact the Tekelec Customer Care Center for assistance if needed.
RxMaxMpsDiscardConn
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of ingress Diameter Request messages received on a connection that were
discarded because of MP Maximum MPS limitation without Error Answer.
Collection Interval: 5 min
Peg Condition: For each message discarded.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. The MP is approaching or exceeding its maximum configured MPS limitation. If this value is not
set to the MP's engineered traffic handling capacity, then the maximum MPS capacity allowed may
need to be changed. Contact Tekelec Customer Care Center for assistance.
2. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
3. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
5. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
6. If the problem persists, contact the Tekelec Customer Care Center.
RxMaxMpsDiscardMp
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of ingress Diameter Request messages received on a connection that were
discarded because of Local MP Congestion without Error Answer.
Collection Interval: 5 min
Peg Condition: Pegged for each message discarded with "Discard Message".
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
308
Measurements
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter Process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxMessageLooping
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of Request messages from a downstream peer rejected by a Local Node
because message looping was detected (FQDN of the Local Node associated with the ingress transport
connection matched a FQDN in the messages' Route-Record AVPs).
Collection Interval: 5 min
Peg Condition: Request message from a downstream peer is rejected by a Local Node with Result-Code
3005 (DIAMETER_LOOP_DETECTED).
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
1. An excessive amount of Request message rerouting may have been triggered by either connection
failures or Answer timeouts. The status of connections should be examined from the Diameter >
Maintenance > Connections page.
2. If no additional congestion alarms are asserted, the routing Answer task may be experiencing a
problem preventing it from processing messages from its Answer Message Queue. The alarm log
should be examined using the Alarms & Events page.
3. If the problem persists, contact the Tekelec Customer Care Center.
RxMpCongestionDiscardConn
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of ingress Diameter Request messages received on a connection that were
discarded because of local MP congestion without Error Answer.
910-6528-001 Revision D, December 2012
309
Measurements
Collection Interval: 5 min
Peg Condition: For each ingress Diameter Request message discarded because of local MP congestion.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxNoRoutesFound
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: Number of Request messages from a downstream peer rejected by a Local Node because
no routes were available for routing the message.
Collection Interval: 5 min
Peg Condition:Request message from a downstream peer is rejected by a Local Node because no routes
were available for routing the message. A No Routes Available condition occurs when:
• A Route List was selected via a Peer Routing Rule or implicit routing but its Operational Status
was Unavailable
• Implicit routing was invoked and the peer's Operational Status was not Available and an alternate
implicit route was not provisioned for the peer
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
1. If the message matched a Peer Routing Rule but none of the peers in the Route List were eligible
for routing the message because either their operation state was Unavailable, the Application ID
in the Request message did not match an application ID supported by the peer, or the peer had
previously processed the message as defined by the Route-Record AVPs in the message:
a) Verify that IP network connectivity exists between the MP server and the peers.
b) Check the event history logs for additional DIAM events or alarms from this MP server.
910-6528-001 Revision D, December 2012
310
Measurements
c) Verify that the peers in the Route List are not under maintenance. Contact Tekelec Customer
Care Center for assistance if needed.
2. If the message was addressed to a peer directly connected to the Local Node via the Destination-Host
AVP but the peer's operational status was Unavailable or the alternate path to the peer, designated
by the peer's alternate implicit route was either not provisioned or was Unavailable:
a) Verify that IP network connectivity exists between the MP server and the adjacent servers.
b) Check the event history logs for additional DIAM events or alarms from this MP server.
c) Verify that the peer is not under maintenance.
3. If the message was addressed to a peer directly connected to the Local Node via the Destination-Host
AVP but the application ID in the Request message did not match an Application ID supported
by the peer:
a) The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs
page. Each MP in the server site should be receiving approximately the same ingress transaction
per second.
b) There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
c) A software defect may exist resulting in PTR buffers not being deallocated to the pool. This
alarm should not normally occur when no other congestion alarms are asserted. The alarm log
should be examined from the Alarms & Events page.
4. Contact the Tekelec Customer Care Center for assistance if needed.
RxNoRulesFailure
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of Request messages from a downstream peer rejected by a Local Node
because no Peer Routing Rule was found.
Collection Interval: 5 min
Peg Condition: Request message from a downstream peer is rejected by a Local Node because no Peer
Routing Rules were found in the peer routing table and the message was not addressed to a peer
(either Destination-Host AVP was absent or Destination-Host AVP was present but was not a peer's
FQDN).
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
910-6528-001 Revision D, December 2012
311
Measurements
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the Routing Answer Task may be experiencing a
problem preventing it from processing messages from its Answer Message Queue. The alarm log
should be examined from the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxPrtRuleRejection
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of Request messages from a downstream peer rejected by a Local Node
because a Peer Routing Rule action is set to Send Answer.
Collection Interval: 5 min
Peg Condition: Request message from a downstream peer rejected by a Local Node because a Peer
Routing Rule action is set to Send Answer.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRejectedAll
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of Request messages rejected from a downstream peer by a Local Node (all
reasons).
Collection Interval: 5 min
Peg Condition: When measurement ID RxDecodeFailure, RxMessageLooping, RxConnInvalidMsg,
RxNoRulesFailure, RxNoRoutesFound, RxTransactionTimeout, RxPrtRuleRejection or RxRejectedOther
is pegged.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
312
Measurements
RxRejectedOther
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of Request messages from a downstream peer rejected by a Local Node for
any reason other than those identified by measurements RxDecodeFailure, RxMessageLooping,
RxConnInvalidMsg, RxNoRulesFailure, RxNoRoutesFound, RxTransactionTimeout, or
RxPrtRuleRejection.
Collection Interval: 5 min
Peg Condition: Request message from a downstream peer rejected by a Local Node for any reason
other than those identified by measurements RxDecodeFailure, RxMessageLooping, RxConnInvalidMsg,
RxNoRulesFailure, RxNoRoutesFound, RxTransactionTimeout, or RxPrtRuleRejection.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRequestMsgQueueFullDiscard
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of ingress Diameter Request messages that were discarded because the
Request Message Queue was full.
Collection Interval: 5 min
Peg Condition: For each Request message discarded because the Request Message Queue was full.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxRoutableDiscardedMsgsMp
Measurement Group: Diameter Ingress Transaction Exception
910-6528-001 Revision D, December 2012
313
Measurements
Measurement Type: Simple
Description: The number of ingress Diameter Request messages received that are discarded by MP
without Error Answer due to MP Overload Control or Maximum IMR Limitation.
Collection Interval: 5 min
Peg Condition: Pegged when Diameter Request message is discarded.
Measurement Scope: Server Group
Recovery:
1. The MP is approaching or exceeding its maximum configured MPS limitation. If this value is not
set to the MP's engineered traffic handling capacity, then the maximum MPS capacity allowed may
need to be changed. Contact Tekelec Customer Care Center for assistance.
2. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
3. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
4. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
5. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
6. If the problem persists, contact the Tekelec Customer Care Center.
RxTransactionTimeout
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of Request messages from a downstream peer rejected by a Local Node
because maximum message reroutes are exceeded.
Collection Interval: 5 min
Peg Condition: Request message from a downstream peer is rejected by a Local Node because maximum
number of message reroutes was exceeded.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
1. If the maximum number of message reroutes is set too low (e.g., zero) then any failure trigger
message reroute will fail. The user-configurable value is set using the Diameter > Configuration
> System Options page.
910-6528-001 Revision D, December 2012
314
Measurements
2. If the user-configurable answer response timer is set too low the timer expires before an Answer
response is received. The user-configurable value is set using the Diameter > Configuration >
System Options page.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TxAllConnQueueFullRequestReject
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of egress Diameter Request messages that were rejected because the
All-Connections Event Queue was full.
Collection Interval: 5 min
Peg Condition: For each Request message discarded because the All-Connections Event Queue was
full.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TxPerConnQueueFullAnswerDiscard
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of egress Answer messages that were discarded because the Per Connection
Egress Message Queue was full.
Collection Interval: 5 min
Peg Condition: For each Per Connection Egress Message Queue Answer message discarded.
Measurement Scope: Server Group
Recovery:
1. An IP network or Diameter peer problem may exist that is preventing SCTP/TCP from transmitting
messages into the network at the same pace that messages are being received from the network.
2. The transport task associated with the connection may be experiencing a problem preventing it
from processing events from its Connection Event Message Queue. The alarm log should be
examined using the Alarms & Events page.
910-6528-001 Revision D, December 2012
315
Measurements
3. If one or more MPs in a server site have failed, the traffic will be distributed among the remaining
MPs in the server site. MP server status can be monitored using the Status & Manage > Server
page.
4. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP.
The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each
MP in the server site should be receiving approximately the same ingress transaction per second.
5. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
6. If the problem persists, contact the Tekelec Customer Care Center.
TxPerConnQueueFullRequestDiscard
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of egress Request messages that were discarded because the Per Connection
Egress Message Queue was full.
Collection Interval: 5 min
Peg Condition: For each Per Connection Egress Message Queue Request message discarded.
Measurement Scope: Server Group
Recovery:
1. An IP network or Diameter peer problem may exist that is preventing SCTP/TCP from transmitting
messages into the network at the same pace that messages are being received from the network.
2. The transport task associated with the connection may be experiencing a problem preventing it
from processing events from its Connection Event Message Queue. The alarm log should be
examined using the Alarms & Events page.
3. If one or more MPs in a server site have failed, the traffic will be distributed among the remaining
MPs in the server site. MP server status can be monitored using the Status & Manage > Server
page.
4. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP.
The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each
MP in the server site should be receiving approximately the same ingress transaction per second.
5. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all
MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
6. If the problem persists, contact the Tekelec Customer Care Center.
TxPtrListEmpty
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of ingress Diameter Request messages that were discarded because no PTR
Buffers were available.
910-6528-001 Revision D, December 2012
316
Measurements
Collection Interval: 5 min
Peg Condition: For each ingress Diameter Request message discarded because no PTR Buffers were
available.
The connection measurement is associated with the connection from which the message was received.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurements for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP when the Ingress
Message Rate and/or Diameter Process CPU Utilization measurements are below the recommended
maximum engineered capacity of an MP, then a network (IP or Diameter) problem may exist.
Looking at these measurements on a time of day basis may provide additional insight into potential
network problems.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific software problem may exist (e.g., a buffer pool leak).
3. Contact the Tekelec Customer Care Center for assistance if needed.
TxRerouteQueueFullReject
Measurement Group: Diameter Ingress Transaction Exception
Measurement Type: Simple
Description: The number of egress Diameter Request messages that were rejected because the Reroute
Queue was full.
Collection Interval: 5 min
Peg Condition: For each Request message rejected because the Reroute Queue was full.
The connection measurement is associated with the connection the Request message was received
from.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
Diameter Ingress Transaction Performance measurements
The Diameter Ingress Transaction Performance measurement report contains measurements providing
information about the outcome of Diameter transactions received from downstream peers.
910-6528-001 Revision D, December 2012
317
Measurements
Table 36: Diameter Ingress Transaction Performance Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxConnRequestMsgs
Number of routable Request
messages received on the
connection
5 min
TxAnswer1xxx
Ingress Answer messages from
peers successfully routed Result-Code value 1xxx
(Informational)
5 min
TxAnswer2xxx
Answer messages from
5 min
upstream peers successfully
routed to downstream peers Result-Code value 2xxx (Success)
TxAnswer3xxx
Answer messages from
5 min
upstream peers successfully
routed to downstream peers Result-Code value 3xxx (Protocol
Error)
TxAnswer4xxx
Answer messages from
upstream peers successfully
routed to downstream peers Result-Code value 4xxx
(Transient Failure)
5 min
TxAnswer5xxx
Answer messages from
upstream peers successfully
routed to downstream peers Result-Code value 5xxx
(Permanent Failure)
5 min
TxAnswerFailure
Expected Answer responses
5 min
from a peer or Answer responses
created by a Local Node which
were not successfully routed to
a downstream peer (for any
reason).
TxAnswerLocalNode
Answer messages created by
5 min
Local Node successfully routed
to downstream peers (all
Result-Code values)
TxAnswerOther
Answer messages from
5 min
upstream peers successfully
routed to downstream peers Result-Code value not 1000-5999
910-6528-001 Revision D, December 2012
318
Measurements
RxConnRequestMsgs
Measurement Group: Diameter Ingress Transaction Performance, Diameter Performance
Measurement Type: Simple
Description: The number of routable Request messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter request message is received from the peer.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswer1xxx
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of Answer responses from peers that were successfully routed to a downstream
peer with a Result-Code value 1xxx.
Collection Interval: 5 min
Peg Condition: Answer message received from a peer that was successfully sent to the DSR with a
Result-Code value in the range of 1000 - 1999.
The connection measurement is associated with the connection to which the message was routed.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswer2xxx
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of Answer responses from peers that were successfully routed to a downstream
peer with a Result-Code value 2xxx.
Collection Interval: 5 min
Peg Condition: Answer message received from a peer that was successfully sent to the DSR with a
Result-Code value in the range of 2000 - 2999.
The connection measurement is associated with the connection to which the message was routed.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
319
Measurements
No action required.
TxAnswer3xxx
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of Answer responses from peers that were successfully routed to a downstream
peer with a Result-Code value 3xxx (Protocol Error).
Collection Interval: 5 min
Peg Condition: Answer message received from a peer that was successfully sent to the DSR with a
Result-Code value in the range of 3000 - 3999.
The connection measurement is associated with the connection to which the message was routed.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswer4xxx
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of Answer responses from peers that were successfully routed to a downstream
peer with a Result-Code value 4xxx (Transient Failure).
Collection Interval: 5 min
Peg Condition: Answer message received from a peer that was successfully sent to the DSR with a
Result-Code value in the range of 4000 - 4999.
The connection measurement is associated with the connection to which the message was routed.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswer5xxx
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of Answer responses from peers that were successfully routed to a downstream
peer with a Result-Code value 5xxx (Permanent Failure).
Collection Interval: 5 min
Peg Condition: Answer message received from a peer that was successfully sent to the DSR with a
Result-Code value in the range of 5000 - 5999.
910-6528-001 Revision D, December 2012
320
Measurements
The connection measurement is associated with the connection to which the message was routed.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswerFailure
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of (expected) Answer responses from a peer and Answer responses created
by a Local Node which were not successfully routed to a downstream peer (for any reason).
Note: An expected Answer response from a peer is an Answer response for which a pending transaction
existed.
Collection Interval: 5 min
Peg Condition: Any time the DSR fails to queue an Answer response.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswerLocalNode
Measurement Group: Diameter Ingress Transaction Performance
Measurement Type: Simple
Description: The number of Answer responses from a Local Node that were successfully routed to a
downstream peer (all Result-Code values).
Collection Interval: 5 min
Peg Condition: Any time the DSR successfully creates and queues an Answer response to DCL in
response to a Request message received from a downstream peer.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
TxAnswerOther
Measurement Group: Diameter Ingress Transaction Performance
910-6528-001 Revision D, December 2012
321
Measurements
Measurement Type: Simple
Description: The number of Answer responses from peers that were successfully routed to a downstream
peer with a Result-Code value not in the range of 1000-5999.
Collection Interval: 5 min
Peg Condition: Answer message received from a peer which was successfully sent to the DSR with
either a Result-Code value not in the range of 1000 - 5999 or without a Result-Code AVP.
The connection measurement is associated with the connection to which the message was routed.
Measurement Scope: Server Group
Recovery:
No action required.
Diameter Performance measurements
The Diameter Performance measurement report contains measurements that provide performance
information that is specific to the Diameter protocol.
Table 37: DiameterPerformance Measurement Report Fields
Measurement Tag
Description
EvConnPrvSuccess
Number of times the connection 5 min
successfully completed the
proving phase.
EvPerConnPtrQueueAvg
The average length of the PTR
queue for a connection during
the collection interval.
EvPerConnPtrQueuePeak
The maximum length of the PTR 5 min
queue for a connection during
the collection interval
RoutingMsgs
The number of messages
processed by DRL , including
Rerouting and Message Copy.
RxAcceptedRequestsMp
The number of ingress Diameter 5 min
Request messages that are
accepted by MP to be routed
after all Overload Controls are
applied.
RxAnswerExpectedAll
Number of valid Answer
messages received from an
upstream peer that were
associated with a pending
transaction.
910-6528-001 Revision D, December 2012
Collection Interval
5 min
5 min
5 min
322
Measurements
Measurement Tag
Description
Collection Interval
RxAnswerExpectedAllMp
Number of valid Answer
messages received from an
upstream peer that were
associated with a pending
transaction.
5 min
RxAnswerExpectedRoutedMP
Number of valid Answer
messages received from an
upstream peer that were
successfully routed to a
downstream peer.
5 min
RxAnswerMsgsMp
Number of Answer messages
received.
5 min
RxConnAnswerMsgs
Number of routable Answer
messages received on the
connection.
5 min
RxConnCea
Number of CEA messages
received on the connection.
5 min
RxConnCer
Number of CER messages
received on the connection.
5 min
RxConnDpa
Number of DPA messages
received on the connection.
5 min
RxConnDpr
Number of DPR messages
received on the connection
5 min
RxConnDwa
Number of DWA messages
received on the connection.
5 min
RxConnDwr
Number of DWR messages
received on the connection.
5 min
RxConnOtherNonRoutable
Number of non-routable
5 min
messages received on the
connection that were not CEx,
DWx, or DPx messages. Includes
messages where the header
P(roxy) bit is not set and
messages where the application
ID is 0.
RxConnRequestMsgs
Number of routable Request
messages received on the
connection.
5 min
RxConnRoutableMsgs
Number of routable messages
received on the connection.
5 min
RxMaxMpsAcceptedMp
The number of ingress Diameter 5 min
messages received that are
910-6528-001 Revision D, December 2012
323
Measurements
Measurement Tag
Description
Collection Interval
accepted by Maximum IMR
Controls of MP.
RxMaxMpsAcceptedRequestsMp The number of ingress Diameter 5 min
Request messages that are
accepted by MP to be routed
after Maximum IMR Controls
are applied by MP.
RxMsgSize
Ingress message size statistics.
5 min
RxMsgSizeAvg
Average ingress message size in 5 min
Diameter payload octets.
RxMsgSizePeak
Peak ingress message size in
Diameter payload octets.
5 min
RxRequestMsgsMp
Number of Request messages
received.
5 min
RxRequestNoErrors
Transactions successfully
processed on one routing
attempt.
5 min
RxRequestNoErrorsMp
Number of transactions
successfully processed on one
routing attempt.
5 min
RxRoutableAcceptedMsgsMpmn The number of ingress Diameter 5 min
messages received that are
accepted by MP for processing
after all overload controls are
applied.
RxRoutableMsgsMp
Number of routable messages
received.
5 min
TmConnAvail
Total time in seconds that the
connection state was
AVAILABLE during the
measurement period.
5 min
TmConnPrvRspAvg
Average time (in microseconds) 5 min
between sending a DWR and
receiving a DWA during any
proving phase(s) for the
measurement period. If proving
fails, no sample is recorded.
TmResponseTimeDownstream
Average downstream transaction 5 min
response time.
TmResponseTimeDownstreamMp Average time (in milliseconds)
from when routing receives a
Request message from a
910-6528-001 Revision D, December 2012
5 min
324
Measurements
Measurement Tag
Description
Collection Interval
downstream peer to the time that
an Answer response is sent to
that downstream peer.
TmResponseTimeUpstream
Average upstream transaction
response time.
5 min
TxAnswerMsgsMp
Number of routable Answer
messages transmitted.
5 min
TxConnAnswerMsgs
Number of routable Answer
messages successfully sent on
the connection.
5 min
TxConnCea
Number of CEA messages sent
on the connection.
5 min
TxConnCer
Number of CER messages
received on the connection.
5 min
TxConnDpa
Number of DPA messages sent
on the connection.
5 min
TxConnDpr
Number of DPR messages sent
on the connection.
5 min
TxConnDwa
Number of DWA messages sent 5 min
on the connection.
TxConnDwr
Number of DWR messages
received on the connection.
5 min
TxConnRequestMsgs
Number of routable Request
messages successfully sent on
the connection.
5 min
TxMsgSize
Average egress message size in 5 min
Diameter payload octets.
TxMsgSizeAvg
Average egress message size in 5 min
Diameter payload octets.
TxMsgSizePeak
Peak egress message size in
Diameter payload octets.
5 min
TxRequestMsgsMp
Number of routable Request
messages transmitted.
5 min
TxRequestSuccessAllMp
Number of Request messages
successfully routed to a peer.
5 min.
EvConnPrvSuccess
Measurement Group: Diameter Performance
910-6528-001 Revision D, December 2012
325
Measurements
Measurement Type: Simple
Description: The number of times the connection successfully completed the proving phase.
Collection Interval: 5 min
Peg Condition: Pegged when a proving period is successfully completed.
Measurement Scope: Server Group
Recovery:
1. If the proving mode in the Connection Configuration Set is set to On Error, and this measurement
indicates an excessive number of proving periods being performed, examine measurements
TxConnDpr, RxConnDpa, RxConnDpr, and TxConnDpa.
2. Also examine the Alarm History for events 22303, 22319 and 22345.
The presence of these measurements/events may indicate that the peer is not responding to DWRs
or not handling the DPx exchange on disconnect properly, after which the DSR will require a
proving period.
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvPerConnPtrQueueAvg
Measurement Group: Diameter Performance
Measurement Type: Average
Description: The average length of the PTR queue for a connection during the collection interval.
Collection Interval: 5 min
Peg Condition: Each time a PTR is dequeued or enqueued on the connection's PTR queue, the average
queue length is calculated using the COMCOL average measurement type method.
Measurement Scope: Server Group
Recovery:
No action required.
EvPerConnPtrQueuePeak
Measurement Group: Diameter Performance
Measurement Type: Max
Description: The maximum length of the PTR queue for a connection during the collection interval.
Collection Interval: 5 min
Peg Condition: Each time a PTR is dequeued or enqueued on the connection's PTR queue, the maximum
queue length is calculated using the COMCOL maximum measurement type method.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
326
Measurements
RoutingMsgs
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of messages processed by DRL, including Rerouting and Message Copy.
Collection Interval: 5 min
Peg Condition: This peg should be incremented per any of these conditions.
• Ingress Request processing resulting in the Request being routed upstream (with or without local
DSR application processing of the Request)
• Ingress Answer processing resulting in forwarding of Answer downstream (with or without local
DSR application processing of the Answer)
• Ingress Request processing resulting in Answer message sent by DSR to originator (with or without
local DSR application processing of the Request)
• Ingress Request discarded due to validation error or overload
• Ingress Answer discarded due to validation error
• Initial copy and transmit of a Request to a DAS
• Ingress Answer triggering reroute of the pending Request message (including Answers from DAS
for copied Requests)
• Request reroute due to connection failure or Answer response timeout (including reroute of copied
Requests to DAS for same reasons)
• Ingress Answer from a DAS terminated by DSR due to Request copy completion or termination
Measurement Scope: Server Group
Recovery:
No action necessary.
RxAcceptedRequestsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of ingress Diameter Request messages that are accepted by MP to be routed
after all Overload Controls are applied.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
No action required.
RxAnswerExpectedAll
Measurement Group: Diameter Egress Transaction, Diameter Performance
910-6528-001 Revision D, December 2012
327
Measurements
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were associated
with a pending transaction.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer message event with a valid transport connection
ID for which a pending transaction is found.
The connection measurement is associated with the connection from which the Answer message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxAnswerExpectedAllMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were associated
with a pending transaction.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer message event with a valid transport connection
ID for which a pending transaction is found.
The connection measurement is associated with the connection from which the Answer message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxAnswerExpectedRoutedMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were
successfully routed to a downstream peer.
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
328
Measurements
RxAnswerMsgsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of Answer messages received.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is received from the peer on the connection. This
measurement is pegged for all messages accepted for processing, as well as those rejected due to local
congestion, MPS limitation, etc.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnAnswerMsgs
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of routable Answer messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter answer message is received from the peer.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnCea
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of CEA messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a CEA message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
329
Measurements
RxConnCer
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of CER messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a CER message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnDpa
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of DPA messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DPA message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnDpr
Measurement Group: Diameter Performance
Measurement Type:Simple
Description: The number of DPR messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DPR message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnDwa
Measurement Group: Diameter Performance
Measurement Type: Simple
910-6528-001 Revision D, December 2012
330
Measurements
Description: The number of DWA messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DWA message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnDwr
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of DWR messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DWR message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnOtherNonRoutable
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of non-routable messages received on the connection that were not CEx,
DWx, or DPx messages. Includes messages where the header Proxy bit is not set and messages where
the application ID is 0.
Collection Interval: 5 min
Peg Condition: Pegged when a message is received with the Proxy bit not set and the Application ID
is 0, and the command code is not CEx, DWx, or DPx.
Note: If this measurement is non-zero, the peer is sending commands to be processed by the Local
Node that the Local Node does not understand. These messages will be discarded.
Measurement Scope: Server Group
Recovery:
1. Monitor the connection to determine which messages are being addressed to the Local Node.
2. Contact the Tekelec Customer Care Center for assistance if needed.
RxConnRequestMsgs
Measurement Group: Diameter Ingress Transaction Performance, Diameter Performance
910-6528-001 Revision D, December 2012
331
Measurements
Measurement Type: Simple
Description: The number of routable Request messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter request message is received from the peer.
Measurement Scope: Server Group
Recovery:
No action required.
RxConnRoutableMsgs
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of routable messages received on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a message with the Proxy bit set is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
RxMaxMpsAcceptedMp
Measurement Group: Diameter Exception
Measurement Type: Simple
Description: The number of ingress Diameter messages received that are accepted by Maximum IMR
Controls of MP.
Collection Interval: 5 min
Peg Condition: Pegged for each message message not discarded or rejected with "Discard Message"
or "Drop Message & Send Response".
Measurement Scope: Server Group
Recovery:
No action required.
RxMaxMpsAcceptedRequestsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of ingress Diameter Request messages that are accepted by MP to be routed
after Maximum IMR Controls are applied by MP.
910-6528-001 Revision D, December 2012
332
Measurements
Collection Interval: 5 min
Peg Condition:
Measurement Scope: Server Group
Recovery:
No action required.
RxMsgSize
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: Ingress message size statistics.
Note: Each bucket in the array contains the number of PDUs with Diameter payload octets that fell
within the bucket's range during the measurement period.
•
•
•
•
•
•
•
•
•
[0] = less than 512 octets
[1] = 512 to 1023 octets
[2] = 1024 to1535 octets
[3] = 1536 to 2047 octets
[4] = 2048 to 2559 octets
[5] = 2560 to 3071 octets
[6] = 3072 to 3583 octets
[7] = 3584 to 4095 octets
[8] = 4096 or more octets
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is received from the peer on the connection. This
measurement is pegged for all messages accepted for processing, as well as those rejected due to local
congestion, MPS limitation, etc.
Measurement Scope: Server Group
Recovery:
No action required.
RxMsgSizeAvg
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The average ingress message size in Diameter payload octets.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is received from the peer on the connection. This
measurement is pegged for all messages accepted for processing, as well as those rejected due to local
congestion, MPS limitation, etc.
910-6528-001 Revision D, December 2012
333
Measurements
Measurement Scope: Server Group
Recovery:
No action required.
RxMsgSizePeak
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The peak ingress message size in Diameter payload octets.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is received from the peer on the connection. This
measurement is pegged for all messages accepted for processing, as well as those rejected due to local
congestion, MPS limitation, etc.
Measurement Scope: Server Group
Recovery:
1. If this measurement exceeds the configured maximum Diameter message size, examine the
RxConnFailMalfMsg measurement to determine how many messages were discarded because of
this condition.
2. Examine the Alarm History and find event 22302 for this connection.
3. Examine the displayed message bytes for errors and monitor the connection for invalid Diameter
messages.
4. Contact the Tekelec Customer Care Center for assistance if needed.
RxRequestMsgsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of Request messages received.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter request message received is from the peer. This measurement
is pegged for all requests accepted for processing, as well as those rejected due to local congestion,
MPS limitation, etc.
Measurement Scope: Server Group
Recovery:
No action required.
RxRequestNoErrors
Measurement Group: Diameter Performance
Measurement Type: Simple
910-6528-001 Revision D, December 2012
334
Measurements
Description: The number of transactions successfully processed on one routing attempt.
Collection Interval: 5 min
Peg Condition: When an Answer response from a peer is successfully queued to the DSR for a
transaction and the total number of times that the corresponding Request message has been forwarded
to a peer equals "1".
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRequestNoErrorsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of transactions successfully processed on one routing attempt.
Collection Interval: 5 min
Peg Condition: When an Answer response from a peer is successfully queued to the DSR for a
transaction and the total number of times that the corresponding Request message has been forwarded
to a peer equals "1".
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRoutableAcceptedMsgsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of ingress Diameter messages received that are accepted by MP for processing
after all overload controls are applied.
Collection Interval: 5 min
Peg Condition: Pegged when Diameter message is sent to DRL for routing.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
335
Measurements
RxRoutableMsgsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of routable messages received.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message, with the Proxy bit set, is received from the peer.
This measurement is pegged for all messages accepted for processing, as well as those rejected due to
local congestion, MPS limitation, etc.
Measurement Scope: Server Group
Recovery:
No action required.
TmConnAvail
Measurement Group: Diameter Performance
Measurement Type:Simple
Description: Total time in seconds that the connection state was available during the measurement
period.
Collection Interval: 5 min
Peg Condition: Pegging started when the connection state is Available. Pegging stopped when the
connection state is Unavailable or Degraded.
Measurement Scope: Server Group
Recovery:
1. If this measurement varies significantly from the total time in the collection period, examine the
Alarm History to determine the reason(s) that the connection was Unavailable or Degraded.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TmConnPrvRspAvg
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The average time (in microseconds) between sending a DWR and receiving a DWA during
any proving phase(s) for the measurement period. If proving fails, no sample is recorded.
Collection Interval: 5 min
Peg Condition: Pegged after a proving period completes successfully.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
336
Measurements
No action required.
TmResponseTimeDownstream
Measurement Group: Diameter Performance
Measurement Type: Average
Description: Average time (in milliseconds) from when routing receives a Request message from a
downstream peer to the time that an Answer response is sent to that downstream peer.
Collection Interval: 5 min
Peg Condition: Time interval for each transaction starts when the DSR successfully decodes an ingress
Request message from a downstream peer. Time interval for each transaction stops when the DSR
attempts to send an Answer response. This includes Answer messages received from upstream peers
and those generated by the DSR.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
1. If the average is significantly larger than what is considered normal, then additional measurements,
such as measurement TmResponseTimeUpstream, should be consulted to assist in determining
the source of the delay.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TmResponseTimeDownstreamMp
Measurement Group: Diameter Performance
Measurement Type: Average
Description: Average time (in milliseconds) from when routing receives a Request message from a
downstream peer to the time that an Answer response is sent to that downstream peer.
Collection Interval: 5 min
Peg Condition: Time interval for each transaction starts when the DSR successfully decodes an ingress
Request message from a downstream peer. Time interval for each transaction stops when the DSR
attempts to send an Answer response. This includes Answer messages received from upstream peers
and those generated by the DSR.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
337
Measurements
TmResponseTimeUpstream
Measurement Group: Diameter Performance
Measurement Type: Average
Description: Average time (in milliseconds) from when routing forwards a Request message to an
upstream peer to the time that an Answer response is received.
Collection Interval: 5 min
Peg Condition: Time interval for each transaction starts when the DSR successfully queues a Request
message. Time interval for each transaction stops when the DSR receives an Answer response for the
pending transaction associated with the forwarded Request message.
The connection measurement is associated with the connection the Request message is sent to.
Note: This measurement excludes transactions which are aborted due to a failure (E.g., timer
PENDING-ANSWER-TIMER or PENDING-TRANSACTION-TIMER expiration or transport connection
failure).
Measurement Scope: Server Group
Recovery:
Contact the Tekelec Customer Care Center for assistance if needed.
TxAnswerMsgsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of routable Answer messages transmitted.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter Answer message is sent to the peer on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxConnAnswerMsgs
Measurement Group: Diameter Egress Transaction, Diameter Performance
Measurement Type: Simple
Description: The number of routable Answer messages successfully sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter Answer message is sent to the peer.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
338
Measurements
No action required.
TxConnCea
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of CEA messages sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a CEA message is sent on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxConnCer
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of CER messages sent on the connection.
Collection Interval: 5 min
Peg Condition: When a CER message is sent to the peer on the connection. This measurement is pegged
for CER messages indicating success as well as those indicating an error. A separate measurement
(TxConnCerErr) is also pegged if the CER indicates an error.
Measurement Scope: Server Group
Recovery:
No action required.
TxConnDpa
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of DPA messages sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DPA message is sent on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
339
Measurements
TxConnDpr
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of DPR messages sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DPR message is sent on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxConnDwa
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of DWA messages sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DWA message is sent on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxConnDwr
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of DWR messages sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a DWR message is received on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxConnRequestMsgs
Measurement Group: Diameter Egress Transaction, Diameter Performance
Measurement Type: Simple
910-6528-001 Revision D, December 2012
340
Measurements
Description: The number of routable Request messages successfully sent on the connection.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter request message is sent to the peer.
Measurement Scope: Server Group
Recovery:
No action required.
TxMsgSize
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: Egress message size statistics.
Note: Each bucket in the array contains the number of PDUs with Diameter payload octets that fell
within the bucket's range during the measurement period.
•
•
•
•
•
•
•
•
•
[0] = less than 512 octets
[1] = 512 to 1023 octets
[2] = 1024 to1535 octets
[3] = 1536 to 2047 octets
[4] = 2048 to 2559 octets
[5] = 2560 to 3071 octets
[6] = 3072 to 3583 octets
[7] = 3584 to 4095 octets
[8] = 4096 or more octets
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is sent to the peer on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxMsgSizeAvg
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The average egress message size in Diameter payload octets.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter message is sent to the peer on the connection.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
341
Measurements
No action required.
TxMsgSizePeak
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The peak egress message size in Diameter payload octets.
Collection Interval: 5 min
Peg Condition: Pegged when the size of the Diameter message sent to the peer is larger than any other
message sent to the peer during the reporting interval.
Measurement Scope: Server Group
Recovery:
No action rerquired.
TxRequestMsgsMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of routable Request messages transmitted.
Collection Interval: 5 min
Peg Condition: Pegged when a Diameter Request message is sent to the peer on the connection.
Measurement Scope: Server Group
Recovery:
No action required.
TxRequestSuccessAllMp
Measurement Group: Diameter Performance
Measurement Type: Simple
Description: The number of Request messages successfully routed to a peer.
Collection Interval: 5 min
Peg Condition: When the DSR successfully queues a Request message.
The connection measurement is associated with the connection to which the Request message was
sent.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
342
Measurements
Diameter Rerouting measurements
The Diameter Rerouting measurement report is a set of measurements which allows the user to evaluate
the amount of message rerouting attempts which are occurring, the reasons for why message rerouting
is occurring, and the success rate of message rerouting attempts.
Table 38: Diameter Rerouting Measurement Report Fields
Measurement Tag
Description
Collection Interval
TxRerouteAnswerRsp
Answer messages received
5 min
associated with rerouted Request
messages
RxRerouteAnswerRspMp
Number of valid Answer
messages received from an
upstream peer that were
associated with a pending
rerouted transaction.
TxRerouteAnswerResponse
Number of message rerouting 5 min
attempts triggered by the receipt
of an Answer response
Result-Code value which is a
candidate for message rerouting.
TxRerouteAnswerTimeout
Rerouting attempts triggered by 5 min
a timeout on the Answer
response.
TxRerouteAttempts
Total number of message
rerouting attempts.
TxRerouteConnFailure
Rerouting attempts triggered by 5 min
a connection failure.
TxRerouteSuccessSent
Message rerouting attempts that 5 min
were successfully rerouted.
5 min
5 min
RxRerouteAnswerRsp
Measurement Group: Diameter Rerouting
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were associated
with a pending rerouted transaction.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer message event with a valid transport connection
ID for which a pending transaction associated with a rerouted message is found.
910-6528-001 Revision D, December 2012
343
Measurements
The connection measurement is associated with the connection from which the Answer message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRerouteAnswerRspMp
Measurement Group: Diameter Rerouting
Measurement Type: Simple
Description: The number of valid Answer messages received from an upstream peer that were associated
with a pending rerouted transaction.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer message event with a valid Transport Connection
ID for which a pending transaction associated with a rerouted message is found.
The connection measurement is associated with the connection from which the Answer message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
TxRerouteAnswerResponse
Measurement Group: Diameter Rerouting
Measurement Type: Simple
Description: The number of message rerouting attempts triggered by the receipt of an Answer response
Result-Code value that is a candidate for message rerouting.
Collection Interval: 5 min
Peg Condition: When the DSR receives an Answer response with a Result-Code value that is a candidate
for message rerouting.
The connection measurement is associated with the upstream connection from which the Answer
response was received.
Measurement Scope: Server Group
Recovery:
No action required.
TxRerouteAnswerTimeout
Measurement Group: Diameter Rerouting
910-6528-001 Revision D, December 2012
344
Measurements
Measurement Type: Simple
Description: The number of message rerouting attempts triggered by a timeout
(PENDING-ANSWER-TIMER) on the Answer response.
Collection Interval: 5 min
Peg Condition: When timer PENDING-ANSWER-TIMER expires and the DSR attempts to reroute a
Request message.
Measurement Scope: Server Group
Recovery:
1. If the user-configurable answer response timer is set too low it can cause the timer to expire before
a Answer response is received. The user-configurable value is set from the Diameter > Configuration
> System Options page.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxRerouteAttempts
Measurement Group: Diameter Rerouting
Measurement Type: Simple
Description: Total number of message rerouting attempts.
Collection Interval: 5 min
Peg Condition: When the DSR attempts to reroute a Request message routed via a Route List for one
of the following reasons:
• Transport connection fails
• PENDING-ANSWER-TIMER expires
• Answer response Result-Code plus application ID matches user-defined values for message rerouting
This measurement will be pegged when any of the following measurement IDs are pegged:
TxRerouteConnFailure, TxRerouteAnswerTimeout, TxRerouteAnswerResponse.
The connection measurement is associated with the upstream connection from which rerouting was
triggered.
Measurement Scope: Server Group
Recovery:
1. If the user-configurable answer response timer is set too low it can cause the timer to expire before
an Answer response is received. The user-configurable value is set from the Diameter >
Configuration > System Options page.
2. Connection status can be monitored from the Diameter > Maintenance > Connections page.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TxRerouteConnFailure
Measurement Group: Diameter Rerouting
Measurement Type: Simple
910-6528-001 Revision D, December 2012
345
Measurements
Description: The number of message rerouting attempts triggered by a connection failure.
Collection Interval: 5 min
Peg Condition: For each Request message rerouting attempt invoked by the receipt of a valid Connection
Down event notification from the DSR.
Measurement Scope: Server Group
Recovery:
1. Connection status can be monitored from the Diameter > Maintenance > Connections page.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TxRerouteSuccessSent
Measurement Group: Diameter Rerouting
Measurement Type: Simple
Description: The number of message rerouting attempts that were successfully rerouted.
Collection Interval: 5 min
Peg Condition: When the DSR successfully reroutes a Request message.
The connection measurement is associated with the upstream connection from which rerouting was
triggered.
Measurement Scope: Server Group
Recovery:
No action required.
Message Priority measurements
The Message Priority measurement group contains measurements that provide information on message
priority assigned to ingress Diameter messages. Measurements such as these are included in this
group.
• Totals for the number of Request messages set to priority “X” when received from a peer.
• Totals for the number of Request messages set to priority “X” as a result of PRT processing.
Table 39: Message Priority Measurement Report Fields
Measurement Tag
EvConnPeerUnsuppMp
Description
The number of times an ingress
Request was received on a
connection configured to read
message priority from the
ingress message, and the peer
910-6528-001 Revision D, December 2012
Collection Interval
5 min
346
Measurements
Measurement Tag
Description
Collection Interval
did not support the UCMP
feature.
Note: In this case, DSR assigns
the default priority of 0 to all
such requests.
EvConnUnexpMp
The number of times an ingress 5 min
Request message was received
with a priority of “3”, when the
peer supports UCMP feature.
RxMsgPri0Ingress
Total number of ingress
messages assigned message
priority 0.
RxMsgPri0PeerRule
Number of Request messages set 5 min
to priority “0” as a result of PRT
processing.
RxMsgPri1Ingress
Total number of ingress
messages assigned message
priority 1.
RxMsgPri1PeerRule
Number of Request messages set 5 min
to priority “1” as a result of PRT
processing.
RxMsgPri2Ingress
Total number of ingress
messages assigned message
priority 2.
RxMsgPri2PeerRule
Number of Request messages set 5 min
to priority “2” as a result of PRT
processing.
5 min
5 min
5 min
ExConnPeerUnsuppMp
Measurement Group: Message Priority
Measurement Type: Simple
Description: The number of times an ingress Request was received on a connection configured to read
message priority from the ingress message, and the peer did not support the UCMP feature.
Note: In this case, DSR assigns the default priority of 0 to all such requests.
Collection Interval: 5 min
Peg Condition: Pegged when a connection is configured to read message priority from ingress message
and the peer does not support UCMP feature.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
347
Measurements
1. Verify that the peer is a DSR
• Product-Name is reported as “Eagle XG DSR”, in the Event Additional Information.
• Vendor-Id is reported as 323 (Tekelec).
2. Verify that the Firmware-Revision reported in the Event Additional Information represents a DSR
software version that supports the Message Priority Feature.
• Call Customer Care Center and obtain the minimum DSR software version that supports Message
Priority and compare with this information.
• If the reported Firmware-Version is greater than or equal to the minimum required DSR software
version, call Customer Care Center.
• If the reported Firmware-Version is less than the minimum required DSR software version, call
Customer Care Center to seek advice on whether the peer DSR needs to be upgraded, or whether
the Message Priority Setting for this Transport Connection or Peer Node needs to be changed
to “None”.
ExConnUnexpMp
Measurement Group: Message Priority
Measurement Type: Simple
Description: The number of times an ingress Request message was received with a priority of “3”,
when the peer supports UCMP feature.
Collection Interval: 5 min
Peg Condition: Pegged when a peer supports UCMP feature and an ingress Request message was
received with a priority of “3”.
Measurement Scope: Server Group
Recovery:
1. Verify that the peer is a DSR
• Product-Name is reported as “Eagle XG DSR”, in the Event Additional Information.
• Vendor-Id is reported as 323 (Tekelec).
2. Verify that the Firmware-Revision reported in the Event Additional Information represents a DSR
software version that supports the Message Priority Feature.
• Call Customer Care Center and obtain the minimum DSR software version that supports Message
Priority and compare with this information.
• If the reported Firmware-Version is greater than or equal to the minimum required DSR software
version, call Customer Care Center.
• If the reported Firmware-Version is less than the minimum required DSR software version, call
Customer Care Center to seek advice on whether the peer DSR needs to be upgraded, or whether
the Message Priority Setting for this Transport Connection or Peer Node needs to be changed
to “None”.
910-6528-001 Revision D, December 2012
348
Measurements
RxMsgPri0Ingress
Measurement Group: Message Priority
Measurement Type: Simple
Description: Total number of ingress messages assigned message priority 0.
Collection Interval: 5 min
Peg Condition: Pegged when an ingress message is assigned a priority of 0.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxMsgPri0PeerRule
Measurement Group: Message Priority
Measurement Type: Simple
Description: Number of Request messages set to priority “0” as a result of PRT processing.
Collection Interval: 5 min
Peg Condition: Each time DRL selects a peer routing rule for routing a Request message, the rule action
is set to “Route to Peer”, and a Message Priority of “0” is assigned to the peer routing rule.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxMsgPri1Ingress
Measurement Group: Message Priority
Measurement Type: Simple
Description: Total number of ingress messages assigned message priority 1.
Collection Interval: 5 min
Peg Condition: Pegged when an ingress message is assigned a priority of 1.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxMsgPri1PeerRule
Measurement Group: Message Priority
910-6528-001 Revision D, December 2012
349
Measurements
Measurement Type: Simple
Description: Number of Request messages set to priority “1” as a result of PRT processing.
Collection Interval: 5 min
Peg Condition: Each time DRL selects a peer routing rule for routing a Request message, the rule action
is set to “Route to Peer”, and a Message Priority of “1” is assigned to the peer routing rule.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxMsgPri2Ingress
Measurement Group: Message Priority
Measurement Type: Simple
Description: Total number of ingress messages assigned message priority 2.
Collection Interval: 5 min
Peg Condition: Pegged when an ingress message is assigned a priority of 2.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxMsgPri2PeerRule
Measurement Group: Message Priority
Measurement Type: Simple
Description: Number of Request messages set to priority “2” as a result of PRT processing.
Collection Interval: 5 min
Peg Condition: Each time DRL selects a peer routing rule for routing a Request message, the rule action
is set to “Route to Peer”, and a Message Priority of “2” is assigned to the peer routing rule.
Measurement Scope: Server Group
Recovery:
No action necessary.
Message Processor (MP) Performance measurements
The MP Performance measurement report contains measurements that provide performance information
for an MP server.
910-6528-001 Revision D, December 2012
350
Measurements
Table 40: MP Performance Measurement Report Fields
Measurement Tag
Description
EvDiameterProcessAvg
The average Diameter process 5 min
CPU utilization (0-100%)
measured during the collection
interval. The Diameter process
is responsible for all
Diameter-related processing.
EvDiameterProcessPeak
The peak Diameter process CPU 5 min
utilization (0-100%) measured
during the collection interval.
The Diameter process is
responsible for all
Diameter-related processing.
EvMpCongestionEntered
Number of times that the MP
5 min
became congested (regardless of
severity level).
EvPduPoolAvg
The average Diameter PDU
5 min
Buffer Pool utilization (0-100%)
measured during the collection
interval.
EvPduPoolPeak
The peak Diameter PDU Buffer 5 min
Pool utilization (0-100%)
measured during the collection
interval.
EvPtrPoolAvg
The average Diameter PTR
5 min
Buffer Pool utilization (0-100%)
measured during the collection
interval.
EvPtrPoolPeak
The peak Diameter PTR Buffer 5 min
Pool utilization (0-100%)
measured during the collection
interval.
EvStasisModeMaxConnections
The number of times DA-MP
requested IPFE to cease
distributing Diameter
connections to the DA-MP due
to the maximum number of
connections on the DA-MP.
5 min
EvStasisModeMpCongestion
The number of times DA-MP
requested IPFE to cease
distributing Diameter
connections to the DA-MP due
to MP Congestion.
5 min
910-6528-001 Revision D, December 2012
Collection Interval
351
Measurements
Measurement Tag
Description
RxAnswerMsgQueueAvg
The average Answer Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxAnswerMsgQueuePeak
The peak Answer Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxMsgRateAvgMp
The average MP ingress message 5 min
rate (in messages per second)
measured during the collection
interval. The ingress message
rate is the number of ingress
Diameter messages that are
targeted for Relay Agent routing
(non-zero application ID).
RxMsgRatePeakMp
The peak Ingress message rate 5 min
(in messages per second)
measured during the collection
interval. The ingress message
rate is the number of ingress
Diameter messages that are
targeted for Relay Agent routing
(non-zero application ID).
RxRequestMsgQueueAvg
The average Request Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
RxRequestMsgQueuePeak
The peak Request Message
5 min
Queue utilization (0-100%)
measured during the collection
interval.
TmAnswerTimeAvg
Average time (in microseconds) 5 min
to process an Answer message.
This is the time from when a
Diameter Answer message is
read from the ingress peer’s
SCTP/TCP socket until it is sent
to the egress peer’s SCTP/TCP
socket.
TmAnswerTimePeak
Peak time (in microseconds) to
process an Answer message.
This is the time from when a
Diameter Answer message is
read from the ingress peer’s
910-6528-001 Revision D, December 2012
Collection Interval
5 min
352
Measurements
Measurement Tag
Description
Collection Interval
SCTP/TCP socket until it is sent
to the egress peer’s SCTP/TCP
socket.
TmMpCongestion
Total time (in milliseconds) spent 5 min
in local MP congestion state.
TmRequestTimeAvg
Average time (in microseconds) 5 min
to process a Request message.
This is the time from when a
Diameter Request message is
read from the ingress peer’s
SCTP/TCP socket until it is sent
to the egress peer’s SCTP/TCP
socket.
TMRequestTimePeak
Peak time (in microseconds) to 5 min
process a Request message. This
is the time from when a
Diameter Request message is
read from the ingress peer’s
SCTP/TCP socket until it is sent
to the egress peer’s SCTP/TCP
socket.
TxAllConnQueueAvg
The average All-Connections
5 min
Event Queue utilization (0-100%)
measured during the collection
interval.
TxAllConnQueuePeak
The peak All-Connections Event 5 min
Queue utilization (0-100%)
measured during the collection
interval.
TxRerouteQueueAvg
The average Reroute Queue
utilization (0-100%) measured
during the collection interval.
5 min
TxRerouteQueuePeak
The peak Reroute Queue
utilization (0-100%) measured
during the collection interval.
5 min
EvDiameterProcessAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average Diameter Process CPU utilization (0-100%) measured during the collection
interval. The Diameter process is responsible for all Diameter-related processing.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
353
Measurements
Peg Condition: The average of all Diameter process CPU utilization samples taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvDiameterProcessPeak
Measurement Group: MP Performance
Measurement Type: Max
Description: The peak Diameter process CPU utilization (0-100%) measured during the collection
interval. The Diameter process is responsible for all Diameter-related processing.
Collection Interval: 5 min
Peg Condition: The maximum Diameter process CPU utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvMpCongestionEntered
Measurement Group: MP Performance
Measurement Type: Simple
Description: The number of times that the MP became congested (regardless of severity level).
Collection Interval: 5 min
Peg Condition: Each time Alarm ID 22200 transitions from cleared to asserted with severity CL1.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
354
Measurements
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. The Diameter process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
EvPduPoolAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average Diameter PDU Buffer Pool utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Diameter PDU Buffer Pool utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurements for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP when the ingress
message rate and/or Diameter process CPU utilization measurements are below the recommended
maximum engineered capacity of an MP, then a network (IP or Diameter) problem may exist.
Looking at these measurements on a time of day basis may provide additional insight into potential
network problems.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific software problem may exist (e.g., a buffer pool leak).
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvPduPoolPeak
Measurement Group: MP Performance
Measurement Type: Max
Description: The peak Diameter PDU Buffer Pool utilization (0-100%) measured during the collection
interval.
A PDU is allocated to each message that arrives at an MP and is de-allocated when message processing
completes. This measurement is useful for evaluating whether persistent network problems exist. In
910-6528-001 Revision D, December 2012
355
Measurements
general, PDU buffers are engineered to match the processing capacity of the MP. If network problems
exist, delaying the off-loading of egress messages from the MP, then PDUs/messages will sit in internal
Diameter queues.
Collection Interval: 5 min
Peg Condition: The maximum Diameter PDU Buffer Pool utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurements for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP when the ingress
message rate and/or Diameter process CPU utilization measurements are below the recommended
maximum engineered capacity of an MP, then a network (IP or Diameter) problem may exist.
Looking at these measurements on a time of day basis may provide additional insight into potential
network problems.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific software problem may exist (e.g., a buffer pool leak).
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvPtrListAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average Diameter PTR Buffer Pool utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Diameter PTR Buffer Pool utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurements for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP when the ingress
message rate and/or Diameter process CPU utilization measurements are below the recommended
maximum engineered capacity of an MP, then a network (IP or Diameter) problem may exist.
Looking at these measurements on a time of day basis may provide additional insight into potential
network problems.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific software problem may exist (e.g., a buffer pool leak).
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvPtrListPeak
Measurement Group: MP Performance
910-6528-001 Revision D, December 2012
356
Measurements
Measurement Type: Max
Description: The peak Diameter PTR Buffer Pool utilization (0-100%) measured during the collection
interval.
A PTR is allocated for each Request message that is forwarded to an upstream peer and is de-allocated
when an Answer response is received and routed to a downstream peer. This measurement is useful
for evaluating whether persistent network or upstream server problems exist. In general, PTR buffers
are engineered to match the processing capacity of the MP. If network or upstream server problems
exist, delaying pending transactions in the MP, then PTRs (and associated messages/PDUs) will sit
in internal Diameter queues.
Collection Interval: 5 min
Peg Condition: The maximum Diameter PTR Buffer Pool utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurements for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP when the ingress
message rate and/or Diameter process CPU utilization measurements are below the recommended
maximum engineered capacity of an MP, then a network (IP or Diameter) problem may exist.
Looking at these measurements on a time of day basis may provide additional insight into potential
network problems.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific software problem may exist (e.g., a buffer pool leak).
3. Contact the Tekelec Customer Care Center for assistance if needed.
EvStasisModeMaxConnections
Measurement Group: MP Performance
Measurement Type: Simple
Description: The maximum number of active Diameter connections supported by a DA-MP has been
exceeded. The number of times DA-MP requested IPFE to cease distributing Diameter connections to
the DA-MP due to the maximum number of connections on the DA-MP.
Collection Interval: 5 min
Peg Condition: This measurement is incremented when the A DA-MP is sending IPFE a “heartbeat”
message and it has determined that the number of Diameter connections established has reached the
maximum number supported by the DA-MP since the last “heartbeat” message was sent. A DA-MP
will send a “heartbeat” message indicating a STASIS availability status when it has reached its maximum
number of active Diameter connections.
Measurement Scope: Server Group
Recovery:
1. If the DA-MP is a member of a IPFE TS, verify that the IPFE is configured to fully monitor the
DA-MP’s availability status.
910-6528-001 Revision D, December 2012
357
Measurements
When a IPFE fully monitors application servers in a IPFE TS, it will cease from distributing new
Diameter connections to any/all application servers that report a “Stasis” availability status.
2. If the problem persists, contact the Tekelec Customer Care Center.
EvStasisModeMpCongestion
Measurement Group: MP Performance
Measurement Type: Simple
Description: The DA-MP is in MP Congestion due to high traffic rates. The number of times DA-MP
requested IPFE to cease distributing Diameter connections to the DA-MP due to MP Congestion.
Collection Interval: 5 min
Peg Condition: This measurement is incremented when the A DA-MP is sending IPFE a “heartbeat”
message and it has been determined that its Congestion Level has transitions from CL0 (No Congestion)
since the last heartbeat message sent. A DA-MP will send a “heartbeat” message indicating STASIS
availability status when it’s Congestion Level is greater than CL0.
Measurement Scope: Server Group
Recovery:
1. The traffic rate needs to be decreased.
2. Contact the Tekelec Customer Care Center for assistance.
RxAnswerMsgQueueAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average Answer Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Answer Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
910-6528-001 Revision D, December 2012
358
Measurements
RxAnswerMsgQueuePeak
Measurement Group: MP Performance
Measurement Type: Max
Description: The peak Answer Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The maximum Answer Message Queue utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxMsgRateAvgMp
Measurement Group: MP Performance
Measurement Type: Average
Description: The average MP ingress message rate (in messages per second) measured during the
collection interval. The ingress message rate is the number of ingress Diameter messages that are
targeted for Relay Agent routing (non-zero Application ID).
Collection Interval: 5 min
Peg Condition: The average of all MP ingress message rate samples taken during the collection interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxMsgRatePeakMp
Measurement Group: MP Performance
910-6528-001 Revision D, December 2012
359
Measurements
Measurement Type: Max
Description: The peak ingress message rate (in messages per second) measured during the collection
interval. The ingress message rate is the number of ingress Diameter messages that are targeted for
Relay Agent routing (non-zero Application ID).
Collection Interval: 5 min
Peg Condition: The maximum ingress message rate (messages per second) sample taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxRequestMsgQueueAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average Request Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The average of all Request Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
RxRequestMsgQueuePeak
Measurement Group: MP Performance
Measurement Type: Max
910-6528-001 Revision D, December 2012
360
Measurements
Description: The peak Request Message Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The maximum Request Message Queue utilization sample taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. If both the peak and average measurement for multiple MPs within a Network Element are
consistently near the recommended maximum engineered capacity of an MP over several collection
intervals, then the number of MPs in the Network Element may need to be increased.
2. If the peak and average for an individual MP is significantly different than other MPs in the same
Network Element then an MP-specific hardware, software, or configuration problem may exist or
a Diameter peer and/or DNS routing mis-configuration problem may exist.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TmAnswerTimeAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: Average time (in milliseconds) to process an Answer message. This is the time from when
a Diameter Answer message is read from the ingress peer's SCTP/TCP socket until it is sent to the
egress peer’s SCTP/TCP socket.
Note: This is the average cross-MP delay for answers during the measurement period excluding
ethernet/IP stack ingress and egress processing time.
Collection Interval: 5 min
Peg Condition: Timing started when an ingress Answer message is read from the connection socket.
Timing stopped when the matching egress Answer message is written to the connection socket. The
difference between the two times is used to update the average.
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive average cross-MP delay, examine the DIAM KPIs to
determine if the system is under excessive load.
2. Examine the Peer Routing Rules to determine if there are an excessive number of rules.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TmAnswerTimePeak
Measurement Group: MP Performance
Measurement Type: Max
910-6528-001 Revision D, December 2012
361
Measurements
Description: Peak time (in milliseconds) to process an Answer message. This is the time from when a
Diameter Answer message is read from the ingress peer’s SCTP/TCP socket until it is sent to the egress
peer’s SCTP/TCP socket.
Note: This is the peak cross-MP delay for answers during the measurement period excluding
ethernet/IP stack ingress and egress processing time.
Collection Interval: 5 min
Peg Condition: Timing started when an ingress Answer message is read from the connection socket.
Timing stopped when the matching egress Answer message is written to the connection socket. This
measurement is pegged if the difference is larger than the current value of the measurement.
Measurement Scope: Server Group
Recovery:
No action required.
TmMpCongestion
Measurement Group: MP Performance
Measurement Type: Simple
Description: Total time (in seconds) spent in local MP congestion state.
Collection Interval: 5 min
Peg Condition:The time duration interval starts when one of the following conditions occurs:
1. A new collection interval for the measurement begins and alarm ID 22200 is asserted (regardless
of severity level).
2. Alarm ID 22200 is asserted with severity Minor (local MP congestion level CL0 to CL1 transition).
The time duration interval stops when one of the following conditions occurs:
1. The collection interval for the measurement ends and alarm ID 22200 is asserted (regardless of
severity level).
2. Alarm ID 22200 is cleared (local MP congestion level CL1 to CL0 transition).
When a time duration interval completes, the time measured is added to the total measurement value.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
910-6528-001 Revision D, December 2012
362
Measurements
4. The Diameter Process may be experiencing problems. The alarm log should be examined using
the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
TmRequestTimeAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: Average time (in milliseconds) to process a Request message. This is the time from when
a Diameter Request message is read from the ingress peer’s SCTP/TCP socket until it is sent to the
egress peer’s SCTP/TCP socket.
Note: This is the average cross-MP delay for Requests during the measurement period excluding
ethernet/IP stack ingress and egress processing time.
Collection Interval: 5 min
Peg Condition: Timing started when an ingress message is read from the connection socket. Timing
stopped when the matching egress message is written to the connection socket. The difference between
the two times is used to update the average.
Measurement Scope: Server Group
Recovery:
1. If this measurement indicates an excessive average cross-MP delay, examine the DIAM KPIs to
determine if the system is under excessive load.
2. Examine the Peer Routing Rules to determine if there are an excessive number of rules.
3. Contact the Tekelec Customer Care Center for assistance if needed.
TMRequestTimePeak
Measurement Group: MP Performance
Measurement Type: Max
Description: Peak time (in milliseconds) to process a Request message. This is the time from when a
Diameter Request message is read from the ingress peer’s SCTP/TCP socket until it is sent to the
egress peer’s SCTP/TCP socket.
Note: This is the peak cross-MP delay for Requests during the measurement period excluding
ethernet/IP stack ingress and egress processing time.
Collection Interval: 5 min
Peg Condition: Timing started when an ingress request message is read from the connection socket.
Timing stopped when the matching egress request message is written to the connection socket. This
measurement is pegged if the difference is larger than the current value of the measurement.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
363
Measurements
TxAllConnQueueAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average All-Connections Event Queue utilization (0-100%) measured during the
collection interval.
Collection Interval: 5 min
Peg Condition: The average of all All-Connections Event Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the DSR may be experiencing a problem preventing
it from processing events from its All-Connections Event Queue. The alarm log should be examined
using the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
TxAllConnQueuePeak
Measurement Group: MP Performance
Measurement Type: Max
Description: The peak All-Connections Event Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: The maximum of all All-Connections Event Queue utilization samples taken during
the collection interval.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
910-6528-001 Revision D, December 2012
364
Measurements
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. If no additional congestion alarms are asserted, the DSR may be experiencing a problem preventing
it from processing events from its All-Connections Event Queue. The alarm log should be examined
using the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
TxRerouteQueueAvg
Measurement Group: MP Performance
Measurement Type: Average
Description: The average Reroute Queue utilization (0-100%) measured during the collection interval.
Collection Interval: 5 min
Peg Condition: The average of all Reroute Queue utilization samples taken during the collection
interval.
Measurement Scope: Server Group
Recovery:
1. An excessive amount of Request message rerouting may have been triggered by either connection
failures or Answer timeouts. The status of connections should be examined from the Diameter >
Maintenance > Connections page.
2. If no additional congestion alarms are asserted, the routing answer task may be experiencing a
problem, preventing it from processing messages from its Reroute Queue. The alarm log should
be examined using the Alarms & Events page.
3. If the problem persists, contact the Tekelec Customer Care Center.
TxRerouteQueuePeak
Measurement Group: MP Performance
Measurement Type: Max
Description: The peak Reroute Queue utilization (0-100%) measured during the collection interval.
Collection Interval: 5 min
Peg Condition: The maximum Reroute Queue utilization sample taken during the collection interval.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
365
Measurements
1. An excessive amount of Request message rerouting may have been triggered by either connection
failures or Answer timeouts. The status of connections should be examined from the Diameter >
Maintenance > Connections page.
2. If no additional congestion alarms are asserted, the routing answer task may be experiencing a
problem, preventing it from processing messages from its Reroute Queue. The alarm log should
be examined using the Alarms & Events page.
3. If the problem persists, contact the Tekelec Customer Care Center.
OAM Alarm measurements
Table 41: OAM Alarm measurements
Measurement Tag
Description
Collection Interval
Alarm Crit
The number of critical alarms.
5 minutes
Alarm Major
The number of major alarms.
5 minutes
Alarm Minor
The number of minor alarms
5 minutes
Alarm State
The alarm state.
5 minutes
OAM System measurements
Table 42: OAM System measurements
Measurement Tag
Description
System CPU UtilPct Average
The average CPU usage from 0 5 minutes
to 100% (100% indicates that all
cores are completely busy).
System CPU UtilPct Peak
The peak CPU usage from 0 to
100% (100% indicates that all
cores are completely busy).
System Disk UtilPct Average
The average disk usage for the 5 minutes
partition on which the COMCOL
database resides.
System Disk UtilPct Peak
The peak disk usage for the
5 minutes
partition on which the COMCOL
database resides.
System RAM UtilPct Average
The average committed RAM
5 minutes
usage as a percentage of the total
physcial RAM. This
measurement is based on the
910-6528-001 Revision D, December 2012
Collection Interval
5 minutes
366
Measurements
Measurement Tag
Description
Collection Interval
Committed_AS measurement
from Linux/proc/meminfo. This
measurement can exceed 100%
if the kernal has committed more
resources than provided by
physical RAM, in which case,
swapping will occur.
System RAM UtilPct Peak
The peak committed RAM usage 5 minutes
as a percentage of the total
physcial RAM. This
measurement is based on the
Committed_AS measurement
from Linux/proc/meminfo. This
measurement can exceed 100%
if the kernal has committed more
resources than provided by
physical RAM, in which case,
swapping will occur.
System ShMem UtilPct Average The average shared memory
5 minutes
usage as a percentage of the limit
configured by shl.set.
System ShMem UtilPct Peak
The peak shared memory usage 5 minutes
as a percentage of the limit
configured by shl.set.
System SwapIn Rate Average
The average number of memory 5 minutes
pages swapped in to memory
from disk per second.
System SwapIn Rate Peak
The peak number of memory
pages swapped in to memory
from disk per second.
5 minutes
System SwapOut Rate Average The average number of memory 5 minutes
pages swapped out of memory
from disk per second.
System SwapOut Rate Peak
The peak number of memory
pages swapped out of memory
from disk per second.
System Swap UtilPct Average
The average usage of swap space 5 minutes
as a percentage of the total
configured swap space.
System Swap UtilPct Peak
The peak usage of swap space as 5 minutes
a percentage of the total
configured swap space.
910-6528-001 Revision D, December 2012
5 minutes
367
Measurements
Measurement Tag
Description
Collection Interval
System CPU CoreUtilPct
Average
The average CPU usage for each 5 minutes
core. On an eight-core system,
there will be eight sub-metrics
showing the utilization of each
core.
System CPU CoreUtilPct Peak
The peak CPU usage for each
core. On an eight-core system,
there will be eight sub-metrics
showing the utilization of each
core.
5 minutes
Peer Node Performance measurements
The "Peer Node” measurement group is a set of measurements that provide performance information
that is specific to a Peer Node. These measurements will allow you to determine how many messages
are successfully forwarded and received to/from each Peer Node. Measurements such as the following
are included in this group.
Table 43: Peer Routing Rules Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxPeerAnswers
Number of routable Answer
5 min
messages received from Peer-X
RxPeerRequests
Number of routable Request
5 min
messages received from Peer-X
TxPeerAnswers
Number of routable Answer
messages sent to Peer-X
5 min
TxPeerRequests
Number of routable Request
messages sent to Peer-X
5 min
RxPeerAnswers
Measurement Group: Peer Node Performance
Measurement Type: Simple
Description: Number of routable Answer messages received from Peer-X.
Collection Interval: 5 min
Peg Condition: When DRL receives an Answer message event from DCL with a valid Transport
Connection ID owned by Peer-X.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
368
Measurements
No action required.
RxPeerRequests
Measurement Group: Peer Node Performance
Measurement Type: Simple
Description: Number of routable Request messages received from Peer-X.
Collection Interval: 5 min
Peg Condition: When DRL receives an Request message event from DCL with a valid Transport
Connection ID owned by Peer-X.
Measurement Scope: Server Group
Recovery:
No action required.
TxPeerAnswers
Measurement Group: Peer Node Performance
Measurement Type: Simple
Description: Number of routable Answer messages sent to Peer-X.
Collection Interval: 5 min
Peg Condition: When DRL successfully queues a Request message for Peer-X to DCL.
Measurement Scope: Server Group
Recovery:
No action required.
TxPeerRequests
Measurement Group: Peer Node Performance
Measurement Type: Simple
Description: Number of routable Request messages sent to Peer-X.
Collection Interval: 5 min
Peg Condition: When DRL successfully queues a Request message for Peer-X to DCL.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
369
Measurements
Peer Routing Rules measurements
The Peer Routing Rules measurement report is a set of measurements associated with the usage of
Peer Routing Rules. These measurements allow you to determine which Peer Routing Rules are most
commonly used and the percentage of times that messages were successfully (or unsuccessfully) routed
using the Route List.
Table 44: Peer Routing Rules Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxPrtSelected
Number of times that a peer
routing rule from PRT-X was
selected for routing a Request
message.
5 min
RxRuleDuplicatePriority
Number of times that the Peer 5 min
Routing Rule was selected for
routing a message but another
Peer Routing Rule had the same
priority and was ignored.
RxRuleFwdFailActionSendAns Number of times that the Peer 5 min
Routing Rule was selected for
routing a Request message and
the message was not successfully
routed because the Peer Routing
Rule's Action is "Send Answer".
RxRuleFwdFailAll
Number of times that the Peer 5 min
Routing Rule was selected for
routing a Request message and
the message was not successfully
routed for any reason.
RxRuleSelected
Number of times that the Peer
Routing Rule was selected for
routing a Request message.
5 min
RxPrtSelected
Measurement Group: Peer Routing Rules
Measurement Type: Simple
Description: Number of times that a peer routing rule from PRT-X was selected for routing a Request
message.
Collection Interval: 5 min
Peg Condition: When the DRL selects a peer routing rule from PRT-X for routing a message.
Measurement Scope: Site
910-6528-001 Revision D, December 2012
370
Measurements
Recovery:
No action required.
RxRuleDuplicatePriority
Measurement Group: Peer Routing Rules
Measurement Type: Simple
Description: The number of times that the Peer Routing Rule was selected for routing a message but
another Peer Routing Rule had the same priority and was ignored.
Collection Interval: 5 min
Peg Condition: When the DSR searches the Peer Routing Rules and finds more than one highest priority
Peer Routing Rule with the same priority that matches the search criteria.
The measurement is associated with the Peer Routing Rule that is selected for routing.
Measurement Scope: Server Group
Recovery:
1. If one or more MPs in a server site have failed, the traffic will be distributed between the remaining
MPs in the server site. MP server status can be monitored from the Status & Manage > Server
page.
2. The mis-configuration of Diameter peers may result in too much traffic being distributed to the
MP. The ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page.
Each MP in the server site should be receiving approximately the same ingress transaction per
second.
3. There may be an insufficient number of MPs configured to handle the network traffic load. The
ingress traffic rate of each MP can be monitored from the Status & Manage > KPIs page. If all MPs
are in a congestion state then the offered load to the server site is exceeding its capacity.
4. A software defect may exist resulting in PDU buffers not being deallocated to the pool. This alarm
should not normally occur when no other congestion alarms are asserted. The alarm log should
be examined using the Alarms & Events page.
5. If the problem persists, contact the Tekelec Customer Care Center.
RxRuleFwdFailActionSendAns
Measurement Group: Peer Routing Rules
Measurement Type: Simple
Description: The number of times that the Peer Routing Rule was selected for routing a Request
message and the message was not successfully routed because the Peer Routing Rule's action is Send
Answer.
Collection Interval: 5 min
Peg Condition: When the DSR selects a Peer Routing Rule to route a Request message and the Peer
Routing Rule's action is Send Answer.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
371
Measurements
Recovery:
No action required.
RxRuleFwdFailAll
Measurement Group: Peer Routing Rules
Measurement Type: Simple
Description: The number of times that the Peer Routing Rule was selected for routing a Request
message and the message was not successfully routed for any reason.
Collection Interval: 5 min
Peg Condition: When the DSR selects a Peer Routing Rule to route a Request message and one of the
following conditions are met:
1. The Peer Routing Rule's action is Send Answer.
2. The Route List associated with the Peer Routing Rule has an Operational Status of Unavailable.
3. The DSR attempts to route the call but exhausts all routes associated with the Route List and sends
an Answer response 3002 (DIAMETER_UNABLE_TO_DELIVER) .
The Route List measurement is associated with the Route List selected for routing.
Measurement Scope: Server Group
Recovery:
1. If a Peer Routing Rule has been configured with the action Send Answer, then every time this Peer
Routing Rule is selected for routing a message, this measurement will be incremented. A Peer
Routing Rule's action can be viewed using the Diameter > Configuration > Peer Routing Rules
page.
2. If a Peer Routing Rule has been configured with the action Route to Peer, then every time this Peer
Routing Rule is selected for routing a message, the Route List associated with this Peer Routing
Rule will be used for routing the message. The Peer Routing Rule's Route List can be viewed using
the Diameter > Configuration > Peer Routing Rules page.
RxRuleSelected
Measurement Group: Peer Routing Rules
Measurement Type: Simple
Description: The number of times that the Peer Routing Rule was selected for routing a Request
message.
Collection Interval: 5 min
Peg Condition: When the DSR selects a Peer Routing Rule for routing a message.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
372
Measurements
Charging Proxy Application (CPA) Performance measurements
The CPA Performance measurement group contains measurements that provide performance
information that is specific to the CPA application. Measurements in this group include:
• Totals for various expected/normal messages and events
• Totals for various expected/normal routing procedures invoked
Table 45: CPA Performance Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxCpaAcaEvent
The number of Accounting
Answer-Event messages
received during the collection
interval.
5 min
RxCpaAcaInterim
The number of Accounting
Answer-Interim messages
received during the collection
interval.
5 min
RxCpaAcaStart
The number of Accounting
5 min
Answer-Start messages received
during the collection interval.
RxCpaAcaStop
The number of Accounting
5 min
Answer-Stop messages received
during the collection interval.
RxCpaAccounting
The number of Diameter
Accounting messages received
during the reporting interval.
5 min
RxCpaAcrEvent
The number of Accounting
Request-Event messages
received during the collection
interval.
5 min
RxCpaAcrInterim
The number of Accounting
Request-Interim messages
received during the collection
interval.
5 min
RxCpaAcrStart
The number of Accounting
5 min
Request-Start messages received
during the collection interval.
RxCpaAcrStop
The number of Accounting
5 min
Request-Stop messages received
during the collection interval.
910-6528-001 Revision D, December 2012
373
Measurements
Measurement Tag
Description
Collection Interval
RxCpaMsgProcessed
The total number of Diameter
messages (Request or Answer)
received during the reporting
interval.
5 min
TxCpaAnswerMsgToDrl
The number of Answers sent to 5 min
DRL layer by CPA during the
collection interval.
TxCpaMsgCopyInd
The number of messages sent by 5 min
the CPA to the routing layer
with message copy indication
set.
TxCpaRequestMsgToDrl
The number of Requests sent to 5 min
DRL layer by CPA during the
collection interval.
TxCpaTraceInd
The number of messages sent by 5 min
the CPA to the routing layer
with trace indication set.
RxCpaAcaEvent
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Answer-Event messages received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Answer-Event message
is received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaAcaInterim
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Answer-Interim messages received during the collection
interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Answer-Interim message
is received by the CPA application.
910-6528-001 Revision D, December 2012
374
Measurements
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaAcaStart
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Answer-Start messages received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Answer-Start message
is received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaAcaStop
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Answer-Stop messages received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Answer-Stop message is
received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaAccounting
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Diameter Accounting messages received during the reporting interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when a Diameter Accounting message is
received.
Measurement Scope: Network, NE, Server Group
Recovery:
910-6528-001 Revision D, December 2012
375
Measurements
No action required.
RxCpaAcrEvent
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Request-Event messages received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Request-Event message
is received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaAcrInterim
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Request-Interim messages received during the collection
interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Request-Interim message
is received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaAcrStart
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Request-Start messages received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Request-Start message
is received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
376
Measurements
RxCpaAcrStop
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Accounting Request-Stop messages received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an Accounting Request-Stop message is
received by the CPA application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaMsgProcessed
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The total number of Diameter messages (Request or Answer) received during the reporting
interval.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever a Diameter message (Request or Answer)
is received.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
TxCpaAnswerMsgToDrl
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Answers sent to DRL layer by CPA during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever CPA sends an Answer to DRL during
the collection interval.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
377
Measurements
TxCpaMsgCopyInd
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of messages sent by the CPA to the routing layer with message copy indication
set.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA sends a message to the routing
layer with the message copy indication set.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
TxCpaRequestMsgToDrl
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of Requests sent to DRL layer by CPA during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever CPA sends a Request to DRL during the
collection interval.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
TxCpaTraceInd
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of messages sent by the CPA to the routing layer with trace indication set.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA sends a message to the routing
layer with the trace indication set.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
378
Measurements
Charging Proxy Application (CPA) Exception measurements
The CPA Exception measurement group contains measurements that provide information about
exceptions and unexpected messages and events that are specific to the CPA application. Measurements
in this group include:
• Totals for unexpected/errors associated with message content
• Totals for unexpected/errors associated with message routing
Table 46: CPA Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
EvCpaMessageDecodeFail
The total number of diameter
message decode failures.
5 min
EvCpaMissingAvp
The total number of diameter
messages received without an
AVP required for this
application.
5 min
EvCpaOOS
The number of times the CPA
was taken Out Of Service.
5 min
EvCpaSubResourceCongested
The total number of
5 min
Sub-Resources that are
determined to be in congestion.
EvCpaUnexpectedSess
The CPA has received an
ACA-Start that already has a
Session Binding Record.
5 min
EvCpaUnkDiameterAppId
The total number of diameter
messages received with an
unknown application ID.
5 min
RxCpaHaSubResourceUnavail
The number of times a Diameter 5 min
message is received whose
Session-Id hashes to a database
partition that is unavailable.
RxCpaNon2xxAnswer
The number of Diameter Answer 5 min
messages received with a
non-2xx response code.
RxCpaOpStatusUnavail
The number of times a message 5 min
is received and the CPA has an
operational status of unavailable.
RxCpaUnexpected
The number of Unexpected
5 min
Diameter message types received
during the reporting interval.
910-6528-001 Revision D, December 2012
379
Measurements
Measurement Tag
Description
Collection Interval
TxCpaAnswerByCpa
The number of times an Answer 5 min
is generated (not relayed) by the
CPA.
TxCpaRteFailure
The number of messages sent by 5 min
the CPA to the routing layer
which failed to route
successfully.
EvCpaMessageDecodeFail
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The total number of diameter message decode failures.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever a Diameter message decode failure is
detected.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaMissingAvp
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The total number of diameter messages received without an AVP required for this
application.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever a Diameter message is received without
an AVP required for this application.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaOOS
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The number of times the CPA was taken Out Of Service.
910-6528-001 Revision D, December 2012
380
Measurements
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA is taken Out Of Service either
manually or automatically.
Measurement Scope: Network, NE, Server Group
Recovery:
1. This measurement indicates problems with the CPA. Logs and Alarms should be checked to
determine the cause of the problem.
2. Contact the Tekelec Customer Care Center for assistance.
EvCpaSubResourceCongested
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The total number of Sub-Resources that are determined to be in congestion.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever SBR reports a congestion level either
through a response or a polled query.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaUnexpectedSess
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The CPA has received an ACA-Start that already has a Session Binding Record.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an ACA-Start is received and a Session
Binding Record already exists.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaUnkDiameterAppId
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The total number of diameter messages received with an unknown application ID.
910-6528-001 Revision D, December 2012
381
Measurements
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever a Diameter message is received with an
unknown application ID.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaHaSubResourceUnavail
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The number of times a Diameter message is received whose Session-Id hashes to a database
partition that is unavailable.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when a Diameter request hashes to a database
partition that is unavailable.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaNon2xxAnswer
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The number of Diameter Answer messages received with a non-2xx response code.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an unexpected Diameter answer with a
non-2xx response code is received.
Measurement Scope: Network, NE, Server Group
Recovery:
1. If this count is non-zero it could indicate a mis-configuration of Application Routing.
2. Contact the Tekelec Customer Care Center for assistance.
RxCpaOpStatusUnavail
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The number of times a message is received and the CPA has an operational status of
unavailable.
910-6528-001 Revision D, December 2012
382
Measurements
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when a Diameter Request is received when
the operational status of the CPA is Unavailable.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaUnexpected
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The number of Unexpected Diameter message types received during the reporting interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an unexpected Diameter (ie; not an
Accounting) message is received.
Measurement Scope: Network, NE, Server Group
Recovery:
1. If this count is non-zero it could indicate a mis-configuration of Application Routing.
2. Contact the Tekelec Customer Care Center for assistance.
TxCpaAnswerByCpa
Measurement Group: CPA Exception
Measurement Type: Simple
Description: The number of times an Answer is generated (not relayed) by the CPA.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when an error condition occurs that causes the
CPA to generat an Answer and not relay one.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
TxCpaFullDRLAnswerDiscard
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The number of egress Diameter Answer messages that were discarded because the DRL’s
Answer Queue was full.
910-6528-001 Revision D, December 2012
383
Measurements
Collection Interval: 5 min
Peg Condition: For each Answer message discarded because the “All-Connections Event Queue” was
full. Used for congestion control by DSR.
Measurement Scope: Server Group
Recovery:
1. The MP may be experiencing local congestion.
2. Contact the Tekelec Customer Care Center for assistance.
TxCpaFullDRLRequestReject
Measurement Group: DSR Application Performance
Measurement Type: Average
Description: The number of egress Diameter Request messages that were rejected because the DRL’s
Request Queue was full.
Collection Interval: 5 min
Peg Condition: For each Request message discarded because the “DRL’s Request Queue” was full.
Used for congestion control by DSR.
Measurement Scope: Server Group
Recovery:
1. The MP may be experiencing local congestion.
2. Contact the Tekelec Customer Care Center for assistance.
TxCpaRteFailure
Measurement Group: CPA Performance
Measurement Type: Simple
Description: The number of messages sent by the CPA to the routing layer which failed to route
successfully.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA sends a message to the routing
layer which fails to route successfully.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
384
Measurements
Charging Proxy Application (CPA) Session DB measurements
The CPA Session DB measurement group contains measurements that provide information about
events that occur when the CPA queries the Session Binding Repository:
• Performance related measurements for SBR queries
• Exceptions and unexpected events related to SBR query processing
Table 47: CPA Session DB Measurement Report Fields
Measurement Tag
Description
Collection Interval
EvCpaNoSbrAccess
The number of queries by the
CPA to the SBR where the SBR
is inaccessible.
5 min
EvCpaSbrAvgRespTime
The average response time for a 5 min
stateful SBR transaction.
EvCpaSbrCreateSess
The number of sessions created 5 min
by the CPA on the SBR during
the collection interval.
EvCpaSbrDeleteSess
The number of sessions deleted 5 min
by the CPA on the SBR during
the collection interval.
EvCpaSbrPeakRespTime
The peak response time for SBR 5 min
queries during the reporting
interval.
EvCpaSbrQryError
The number of queries initiated 5 min
by the CPA to the SBR that
resulted in an error condition
during the collection interval.
EvCpaSbrQryMatch
The number of queries initiated 5 min
by the CPA to the SBR that
resulted in a matching condition
during the collection interval.
EvCpaSbrQryNoMatch
The number of queries initiated 5 min
by the CPA to the SBR that
resulted in a no match condition
during the collection interval.
EvCpaSbrRespTime
This measurement groups
5 min
responses to SBR queries by the
amount of round trip time they
took to process. Each bucket will
represent the number of
responses processed within that
time interval.
910-6528-001 Revision D, December 2012
385
Measurements
Measurement Tag
Description
Collection Interval
EvCpaSbrUpdateSess
The number of update session 5 min
requests sent by the CPA to the
SBR during the collection
interval. The value does not
include created sessions.
RxCpaUndeliveredMsg
The total number of messages
5 min
that ComAgent could not send
or for which it did not receive a
response.
TxCpaSbrQueryTot
The total number of queries
5 min
(reads / creates / updates /
deletes) sent from the CPA to the
SBR during the reporting
interval.
EvCpaNoSbrAccess
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of queries by the CPA to the SBR where the SBR is inaccessible.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA attempts a query when the SBR
is inaccessible.
Measurement Scope: Network, NE, Server Group
Recovery:
1. The SBR could be Out Of Service or temporarily down.
2. Contact the Tekelec Customer Care Center for assistance.
EvCpaSbrAvgRespTime
Measurement Group: CPA Session DB
Measurement Type: Average
Description: The average response time for a stateful SBR transaction.
Collection Interval: 5 min
Peg Condition: This measurement is the average response time for SBR transactions.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
386
Measurements
EvCpaSbrCreateSess
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of sessions created by the CPA on the SBR during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA creates a new session based on
the session identifier.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaSbrDeleteSess
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of sessions deleted by the CPA on the SBR during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever CPA deletes a session on the SBR during
the collection interval.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaSbrPeakRespTime
Measurement Group: CPA Session DB
Measurement Type: Max
Description: The peak response time for SBR queries during the reporting interval.
Collection Interval: 5 min
Peg Condition: This measurement tracks the maximum response time for an SBR query in milliseconds
for the reporting interval.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
387
Measurements
EvCpaSbrQryError
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of queries initiated by the CPA to the SBR that resulted in an error condition
during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA initiates a query to the SBR and
receives an error response.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaSbrQryMatch
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of queries initiated by the CPA to the SBR that resulted in a matching condition
during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA initiates a query to the SBR and
finds a match based on the session identifier.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaSbrQryNoMatch
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of queries initiated by the CPA to the SBR that resulted in a no match condition
during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the initiates a query (read, create, update,
delete) to the and finds no match based on the session identifier.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
388
Measurements
EvCpaSbrRespTime
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: This measurement groups responses to SBR queries by the amount of round trip time
they took to process. Each bucket will represent the number of responses processed within that time
interval.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged for every SBR response received.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
EvCpaSbrUpdateSess
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The number of update session requests sent by the CPA to the SBR during the collection
interval. The value does not include created sessions.
Collection Interval: 5 min
Peg Condition: This measurement will be incremented when the CPA sends an update request to the
SBR.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
RxCpaUndeliveredMsg
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The total number of messages that ComAgent could not send or for which it did not
receive a response.
Collection Interval: 5 min
Peg Condition: This measurement will be pegged whenever a ComAgent invokes the Undelivered
Message callback.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
389
Measurements
TxCpaSbrQueryTot
Measurement Group: CPA Session DB
Measurement Type: Simple
Description: The total number of queries (reads / creates / updates / deletes) sent from the CPA to
the SBR during the reporting interval.
Collection Interval: 5 min
Peg Condition: This measurement is the total number of queries sent by the CPA to the SBR.
Measurement Scope: Network, NE, Server Group
Recovery:
No action required.
Message Copy measurements
The Diameter Application Server (DAS) measurements reflect the Message Copy performance. These
measurements allow the user to monitor the amount of traffic being copied and the percentage of
times that messages were successfully (or unsuccessfully) copied. Measurements such as the following
are included in this group:
•
•
•
•
Number of messages being copied
Number of errors in transmitting those copies (i.e., retransmits)
Number of times a copy transaction failed
Tx and Message Copy queue utilization
Table 48: Message Copy Measurement Report Fields
Measurement Tag
Description
DASCopyAnswerRx
The total number of DAS Copy 5 min
Answers received.
DASCopyDiscarded
Total number of Message Copy 5 min
failures because of any error (no
Answer received, the result code
in the Answer didn’t match
provisioning).
DASCopyFailureMPCong
Total number of DAS Copy
Failures because the MP was
congested.
DASCopyFailureNoRLProv
Total amount of DAS Copy
5 min
failures because no route list was
provisioned in the System
Options.
910-6528-001 Revision D, December 2012
Collection Interval
5 min
390
Measurements
Measurement Tag
Description
Collection Interval
DASCopyFailurePeerApplIdUnsup Total amount of DAS Copy
5 min
Failures because the Diameter
Application Layer has specified
a route list with no peer for the
application ID in the message.
DASCopyFailureRLNotProv
Total number of DAS Copy
5 min
Failures because the route list is
not provisioned.
DASCopyRetransmits
Total number of DAS Copy
retransmits.
5 min
DASCopyRetransmitsExceeded Total number of times the DAS 5 min
Copy retransmits exceeded the
configured max number of
retransmits.
DASCopyTx
The total number of DAS Copies 5 min
forwarded.
DASCopyValidAnswer
The total number of DAS Copy 5 min
transactions completed (a Copy
Pending Transaction has been
paired with a qualified Answer
from the DAS peer).
TxMsgCopyQueueAve
The average Message Copy
5 min
Queue utilization (0-100%)
measured during the collection
interval.
TxMsgCopyQueueFullDiscard
Total number of DAS Request
5 min
messages discarded because the
Message Copy queue was full.
TxMsgCopyQueuePeak
The peak Message Copy Queue 5 min
utilization (0-100%) measured
during the collection interval.
DASCopyAnswerRx
Measurement Group: DAS
Measurement Type: Simple
Description: The total number of DAS Copy Answers received.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time an Answer response is received from a
DAS peer.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
391
Measurements
Recovery:
No action required.
This measurement is an indication of the Message Copy response traffic load being processed by
the MP.
DASCopyDiscarded
Measurement Group: DAS
Measurement Type: Simple
Description: Total number of Message Copy failures because of any error (no Answer received, the
result code in the Answer didn’t match provisioning).
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time a DAS Copy fails for any reason. Some
failure reasons include (but are not limited to): no answer from peer, Application ID not supported
at the peer, result code in the Answer incorrect/doesn’t match provisioning.
Measurement Scope: Server Group
Recovery:
1. Verify proper routing to the intended DAS peer is configured and in service (route list is properly
configured), Diameter application is selecting intended route list.
2. Verify intended DAS peer is properly configured to receive the intended traffic and traffic load.
3. Verify no network issues exist between the MP and intended DAS peer.
4. Contact the Tekelec Customer Care Center for assistance.
DASCopyFailureMPCong
Measurement Group: DAS
Measurement Type: Simple
Description: Total number of DAS Copy Failures because the MP was congested.
Collection Interval: 5 min
Peg Condition: When the MP declares congestion (declared CL1-CL3), the Message Copy function is
disabled. Original messages marked for copy and held as a Pending Transactions are not copied and
increment this measurement. If the Copy has been sent to the DAS peer, the Copy transaction will be
allowed to complete. If the Copy transaction fails, another measurement will be incremented.
Either the MP is receiving traffic in excess of its rated capacity or the intended DAS peer is not
responding in a timely fashion.
Measurement Scope: Server Group
Recovery:
1. Reduce traffic being received by the MP.
2. Verify there are no network issues between the MP and the intended DAS peer.
910-6528-001 Revision D, December 2012
392
Measurements
3. Ensure the intended DAS peer has sufficient capacity to process the traffic being directed to it by
the MP
4. Contact the Tekelec Customer Care Center for assistance.
DASCopyFailureSizeExceeded
Measurement Group: DAS
Measurement Type: Simple
Description: Total amount of DAS Copy failures due to the copied message size exceeding the maximum
message size configured for the system.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time the Copy Pending Transaction is discarded
because a the message being copied to the DAS exceeded the system set meaximum message size,
thus causing the copy action to fail.
Measurement Scope: Server Group
Recovery:
1. Verify the maximum message size set system wide is sufficient for handling the messages being
processed.
2. Contact the Tekelec Customer Care Center for assistance.
DASCopyFailurePeerApplIdUnsup
Measurement Group: DAS
Measurement Type: Simple
Description: Total amount of DAS Copy Failures because the Diameter Application Layer has specified
a route list with no peer for the application ID in the message.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time the Copy Pending Transaction is discarded
because a Diameter Request has been marked for copy by the application, but no connection in the
provided Route List supports the Application ID in the request, causing the copy action to fail.
Measurement Scope: Server Group
Recovery:
1. Verify the route list provisioning points to the intended DAS peer, and the intended DAS peer is
responding with the desired Application ID.
2. Contact the Tekelec Customer Care Center for assistance.
DASCopyFailureRLNotProv
Measurement Group: DAS
Measurement Type: Simple
910-6528-001 Revision D, December 2012
393
Measurements
Description: Total number of DAS Copy Failures because the route list is not provisioned.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time the Copy Pending Transaction fails because
the indicated route list contained in the Diameter request does not match what has been provisioned
as a system option or other provisioned route lists.
Measurement Scope: Server Group
Recovery:
1. Review local provisioning that connections to intended DAS peer server(s) are in service and that
no network issues exist in the path(s) to intended DAS peer server(s).
2. Review DAS peer provisioning to insure proper configuration.
3. Contact the Tekelec Customer Care Center for assistance.
DASCopyRetransmits
Measurement Group: DAS
Measurement Type: Simple
Description: Total number of DAS Copy retransmits.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time any Copied Message is retransmitted to
a DAS peer because a qualified Diameter Answer response has not been received within the Pending
Answer Timer’s timeout value to complete the pending transaction.
Measurement Scope: Server Group
Recovery:
1. Verify proper routing to the intended DAS peer is configured and in service (route list is properly
configured), Diameter application is selecting intended route list.
2. Verify intended DAS peer is properly configured to receive the intended traffic and traffic load.
3. Verify no network issues exist between the MP and intended DAS peer.
4. Contact the Tekelec Customer Care Center for assistance.
DASCopyRetransmitsExceeded
Measurement Group: DAS
Measurement Type: Simple
Description: Total number of times the DAS Copy retransmits exceeded the configured max number
of retransmits.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time a Copy Pending Transaction is discarded
because the Copied Request has been retransmitted the configured number of times without receiving
an Answer response from the DAS peer.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
394
Measurements
Recovery:
1. Verify proper routing to the intended DAS peer is configured and in service (route list is properly
configured), Diameter application is selecting intended route list.
2. Verify intended DAS peer is properly configured to receive the intended traffic and traffic load.
3. Verify no network issues exist between the MP and intended DAS peer.
4. Contact the Tekelec Customer Care Center for assistance.
DASCopyTx
Measurement Group: DAS
Measurement Type: Simple
Description: The total number of DAS Copies forwarded.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time a Message Copy is transmitted to a DAS
peer.
Measurement Scope: Server Group
Recovery:
No action required.
This measurement is an indication of the Message Copy traffic load being processed by the MP.
DASCopyValidAnswer
Measurement Group: DAS
Measurement Type: Simple
Description: The total number of DAS Copy transactions completed (a Copy Pending Transaction has
been paired with a qualified Answer from the DAS peer).
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time a Copy Pending Transaction is completed
because a Diameter Copy Pending Transaction has been paired with a qualified Answer received from
a DAS peer, completing the transaction.
Measurement Scope: Server Group
Recovery:
1. Verify proper routing to the intended DAS peer is selected and in service.
2. desired answer result code is provisioned in the DiameterSystem Options.
3. desired DAS peer is configured to return the answer result code provisioned in the DiameterSystem
Options.
4. Contact the Tekelec Customer Care Center for assistance.
910-6528-001 Revision D, December 2012
395
Measurements
TxMsgCopyQueueAve
Measurement Group: DAS
Measurement Type: Average
Description: The average Message Copy Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
Peg Condition: This measurement is pegged when a new Message Copy SysMetric sample is collected,
then divided by the number of samples collected in the collection period.
Measurement Scope: Server Group
Recovery:
No action required.
This is an diagnostic indicator of the amount of traffic load being processed by the Message Copy
feature.
TxMsgCopyQueueFullDiscard
Measurement Group: DAS
Measurement Type: Simple
Description: Total number of DAS Request messages discarded because the Message Copy queue was
full.
Collection Interval: 5 min
Peg Condition: This measurement is incremented each time a DAS Request is discarded because the
Message Copy Tx queue was full, thus preventing a new DAS Request from being queued for transmit.
Measurement Scope: Server Group
Recovery:
No action required.
This is an diagnostic indicator of the amount of traffic load being processed by the Message Copy
feature.
TxMsgCopyQueuePeak
Measurement Group: DAS
Measurement Type: Max
Description: The peak Message Copy Queue utilization (0-100%) measured during the collection
interval.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
396
Measurements
Peg Condition: This measurement is pegged when a new Message Copy SysMetric sample is collected
and the sample exceeds the previously saved peak for the collection period. When a new collection
period is begun, the peak is reset to 0.
Measurement Scope: Server Group
Recovery:
No action required.
This is an diagnostic indicator of the amount of traffic load being processed by the Message Copy
feature.
IP Front End (IPFE) Exception measurements
The "IPFE Exception" measurement group is a set of measurements that provide information about
exceptions and unexpected messages and events specific to the IPFE application. Measurements such
as the following are included in this group.
Table 49: IPFE Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
PcapDroppedPackets
Number of ARP/ICMP/ICMPv6 5 min
control packets dropped
TsaUnexpctedSctp
Number of SCTP packets sent to 5 min
a TSA configured as “TCP
Only”.
TsaUnexpctedTcp
Number of TCP packets sent to 5 min
a TSA configured as “SCTP
Only”.
TxReject
Number of new associations
rejected
5 min
TxRejectSctp
Number of new SCTP
associations rejected
5 min
PcapDroppedPackets
Measurement Group: IPFE Exception
Measurement Type: Simple
Description: ARP/ICMP/ICMPv6 control packets dropped. The pcap library listens for packets on
the network interfaces on behalf of the IPFE. If the network interface receives more packets than it can
handle, the library will drop packets and increase a dropped packet counter.
Collection Interval: 5 minutes
910-6528-001 Revision D, December 2012
397
Measurements
Peg Condition: This measurement is incremented by one each time the IPFE drops an
ARP/ICMP/ICMPv6 control packet.
Measurement Scope: Network, NE, Server Group
Recovery:
1. In the unlikely event that counts should appear for this measurement, network diagnostics should
be performed.
2. For further assistance, contact the Tekelec Customer Care Center.
TsaUnexpctedSctp
Measurement Group: IPFE Exception
Measurement Type: Simple
Description: Number of SCTP packets sent to a TSA configured as “TCP Only”.
Collection Interval: 5 minutes
Peg Condition: Incremented when an SCTP packet is received for a TSA configured as “TCP Only”.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed
Recovery:
Check client configuration for clients attempting SCTP associations with a TCP-only TSA.
TsaUnexpctedTcp
Measurement Group: IPFE Exception
Measurement Type: Simple
Description: Number of TCP packets sent to a TSA configured as “SCTP Only”.
Collection Interval: 5 minutes
Peg Condition: Incremented when a TCP packet is received for a TSA configured as “SCTP Only”.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed
Recovery:
Check client configuration for clients attempting TCP connections on an SCTP-only TSA.
TxReject
Measurement Group: IPFE Exception
Measurement Type: Simple
910-6528-001 Revision D, December 2012
398
Measurements
Description: Number of new associations rejected. The IPFE rejects new associations when there are
no available applications servers for the target set address. The associated alarm, 5009 - No available
servers in target set, will also be issued.
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time the IPFE rejects a new association
for a target set address.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by target set address
Recovery:
Check the status of the application servers by navigating to the Status & Manage > Server page.
TxRejectSctp
Measurement Group: IPFE Exception
Measurement Type: Simple
Description: New SCTP associations rejected.
Collection Interval: 5 minutes
Peg Condition: Incremented when an SCTP association is rejected.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
IP Front End (IPFE) Performance measurements
The "IPFE Performance" measurement group contains measurements that provide performance
information that is specific to the IPFE application. Counts for various expected/normal messages
and events are included in this group. Measurements such as the following are included.
Table 50: IPFE Performance Measurement Report Fields
Measurement Tag
Description
AsNewAssociations
Number of new associations for 5 min
each server
AsNewAssociationsSctp
Number of new SCTP
associations for each server
IpfeNewAssociations
Number of new associations for 5 min
the IPFE
IpfeNewAssociationsSctp
Number of new SCTP
associations for the IPFE
910-6528-001 Revision D, December 2012
Collection Interval
5 min
5 min
399
Measurements
Measurement Tag
Description
Collection Interval
RxIpfeBytes
Number of bytes received by the 5 min
IPFE
RxIpfeBytesSctp
Number of SCTP bytes received 5 min
by the IPFE
RxIpfePackets
Number of packets received by
the IPFE
5 min
RxTsaBytes
Number of bytes received for
each TSA
5 min
RxTsaBytesSctp
Number of SCTP bytes received 5 min
for each TSA
RxTsaPackets
Number of packets received for 5 min
each TSA
RxTsaPacketsSctp
Number of SCTP packets
received for each TSA
TsaNewAssociations
Number of new associations for 5 min
each TSA
TsaNewAssociationsSctp
Number of new SCTP
associations for each TSA
5 min
TxAsBytes
Number of bytes sent for each
server
5 min
TxAsBytesSctp
Number of SCTP bytes sent for
each server
5 min
TxAsPackets
Number of packets sent for each 5 min
server
TxAsPacketsSctp
Number of SCTP packets sent for 5 min
each server
5 min
AsNewAssociations
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: New associations for each server
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time the IPFE associates a client packet
with an application server.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
910-6528-001 Revision D, December 2012
400
Measurements
AsNewAssociationsSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: New SCTP associations for each server,
Collection Interval: 5 minutes
Peg Condition: Incremented when a new SCTP association is established for an application server.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
IpfeNewAssociations
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: New associations for the IPFE
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time the IPFE associates a client packet
with an application server.
Measurement Scope: Network, NE, Server Group
Recovery: None required
IpfeNewAssociationsSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: New SCTP associations for the IPFE ,
Collection Interval: 5 minutes
Peg Condition: Incremented when a new SCTP association is established through an IPFE.
Measurement Scope: Network, NE, Server Group
Recovery: None required
RxIpfeBytes
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: The number of bytes received by the IPFE.
Collection Interval: 5 minutes, 30 minutes, 60 minutes
Peg Condition: The measurement is incremented by one for each byte the IPFE receives.
910-6528-001 Revision D, December 2012
401
Measurements
Measurement Scope: Network, NE, Server Group
Recovery: None required
RxIpfeBytesSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: The number of SCTP bytes received by the IPFE.
Collection Interval: 5 minutes, 30 minutes, 60 minutes
Peg Condition: Incremented by the packet payload size when an SCTP packet is received by the IPFE.
Measurement Scope: Network, NE, Server Group
Recovery: None required
RxIpfePackets
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: Packets received by the IPFE
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one for each packet the IPFE receives.
Measurement Scope: Network, NE, Server Group
Recovery: None required
RxTsaBytes
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: Bytes received for each TSA.
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time a byte is received for a particular
target set address.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by target set address
Recovery: None required
RxTsaBytesSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: SCTP bytes received for each TSA.
910-6528-001 Revision D, December 2012
402
Measurements
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time an SCTP byte is received for a
particular target set address.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by target set address
Recovery: None required
RxTsaPackets
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: Packets received for each TSA
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time a packet is received for a particular
TSA.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by TSA
Recovery: None required
RxTsaPacketsSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: SCTP packets received for each TSA.
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time an SCTP packet is received for a
particular TSA.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by TSA
Recovery: None required
TsaNewAssociations
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: New associations for each target set address
Collection Interval:
Peg Condition: This measurement is incremented by one each time the IPFE associates a client packet
with a target set address.
Measurement Scope: Network, NE, Server Group
910-6528-001 Revision D, December 2012
403
Measurements
Measurement Dimension: Arrayed by target set address
Recovery: None required
TsaNewAssociationsSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: New SCTP associations for each TSA.
Collection Interval: 5 minutes
Peg Condition: Incremented when a new SCTP association is established for a TSA.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by target set address
Recovery: None required
TxAsBytes
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: Bytes sent for each server
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time a byte is sent to a particular
application server.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
TxAsBytesSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: SCTP bytes sent for each server
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time an SCTP byte is sent to a particular
application server.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
910-6528-001 Revision D, December 2012
404
Measurements
TxAsPackets
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: Packets sent for each server.
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time a packet is sent to a particular
application server.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
TxAsPacketsSctp
Measurement Group: IPFE Performance
Measurement Type: Simple
Description: SCTP packets sent for each server.
Collection Interval: 5 minutes
Peg Condition: This measurement is incremented by one each time an SCTP packet is sent to a particular
application server.
Measurement Scope: Network, NE, Server Group
Measurement Dimension: Arrayed by application server
Recovery: None required
Full Address Based Resolution (FABR) Application Performance
measurements
The "FABR Application Performance" measurement group is a set of measurements that provide
performance information that is specific to the FABR feature. These measurements will allow you to
determine how many messages are successfully forwarded and received to and from the FABR
Application.
Table 51: DSR Application Performance Measurement Report Fields
Measurement Tag
Description
RxDpResponseTimeAvg
Average time (in milliseconds) 5 min
it takes to receive a DP response
after sending the correlated
database query.
910-6528-001 Revision D, December 2012
Collection Interval
405
Measurements
Measurement Tag
Description
RxFabrAvgMsgSize
Average size of Request message 5 min
received.
RxFabrDpResponseMsgQueueAvg The average DP Response
Message Queue utilization
(0-100%) measured during the
collection interval.
Collection Interval
5 min
RxFabrDpResponseMsgQueuePeak The peak DSR Application's DP 5 min
Response Message Queue
utilization (0-100%) measured
during the collection interval.
RxFabrMsgs
Number of Request messages
received by FABR application.
5 min
RxFabrResolAll
Number of Addresses
Successfully Resolved to a
Destination
5 min
RxFabrResolAllMp
Number of Addresses
Successfully Resolved to a
Destination by the MP.
5 min
RxFabrResolImpi
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IMPI.
RxFabrResolImpu
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IMPU.
RxFabrResolImsi
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IMSI.
RxFabrResolMsisdn
Number of Addresses Successful 5 min
Resolved with Routing Entity
type MSISDN.
RxFabrResolRateAvg
Average Addresses Successfully 5 min
Resolved per second
RxFabrResolRatePeak
Peak Addresses Successfully
Resolved per second.
TxFabrAbandonRequest
Number of Request message that 5 min
are abandoned.
TxFabrFwdDefaultDest
Number of Request message
forwarding attempts using a
Default Destination.
910-6528-001 Revision D, December 2012
5 min
5 min
406
Measurements
Measurement Tag
Description
Collection Interval
TxFabrFwdNochange
Number of Request message
forwarding attempts without
changing the message.
5 min
TxFabrFwdSuccess
Number of Request messages
successfully forwarded (all
reasons).
5 min
TxFabrMsgAttempt
Number of Request message
forwarding attempts (all
reasons).
5 min
RxDpResponseTimeAvg
Measurement Group: Full Address Resolution Performance
Measurement Type: Average
Description: Average time (in milliseconds) it takes to receive a DP response after sending the correlated
database query.
Collection Interval: 5 min
Peg Condition: It is calculated based on the total number of sampled database queries during the
collection interval.
Measurement Scope: MP
Recovery:
No action necessary.
RxFabrAvgMsgSize
Measurement Group: Full Address Resolution Performance
Measurement Type: Average
Description: Average size of Request message received.
Collection Interval: 5 min
Peg Condition: Average calculated for each Request message received.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrDpResponseMsgQueueAvg
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
910-6528-001 Revision D, December 2012
407
Measurements
Description: The average DP Response Message Queue utilization (0-100%) measured during the
collection interval.
Collection Interval: 5 min
Peg Condition: The average of all Request Message Queue utilization samples taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
This alarm may occur due to persistent overload conditions with respect to database response
processing.
Contact the Tekelec Customer Care Center for assistance.
RxFabrDpResponseMsgQueuePeak
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: The peak DSR Application's DP Response Message Queue utilization (0-100%) measured
during the collection interval.
Collection Interval: 5 min
Peg Condition: The maximum DP Response Message Queue utilization sample taken during the
collection interval.
Measurement Scope: Server Group
Recovery:
This alarm may occur due to persistent overload conditions with respect to database response
processing.
Contact the Tekelec Customer Care Center for assistance.
RxFabrMsgs
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request messages received by FABR application.
Collection Interval: 5 min
Peg Condition: For each message successfully de-queued from the application’s internal “Message
Event” queue.
Measurement Scope: Server Group
Recovery:
No action necessary.
910-6528-001 Revision D, December 2012
408
Measurements
RxFabrResolAll
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successfully Resolved to a Destination.
Collection Interval: 5 min
Peg Condition: For each message successfully resolved to a Destination.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrResolAllMp
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successfully Resolved to a Destination by the MP.
Collection Interval: 5 min
Peg Condition: For each message successfully resolved to a Destination by the MP.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrResolImpi
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IMPI.
Collection Interval: 5 min
Peg Condition: For each message successfully resolved to a Destination using a Routing Entity Type
of IMPI.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrResolImpu
Measurement Group: Full Address Resolution Performance
910-6528-001 Revision D, December 2012
409
Measurements
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IMPU.
Collection Interval: 5 min
Peg Condition: For each message successfully resolved to a Destination using a Routing Entity Type
of IMPU.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrResolImsi
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IMSI.
Collection Interval: 5 min
Peg Condition: For each message successfully resolved to a Destination using a Routing Entity Type
of IMSI.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrResolMsisdn
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type MSISDN.
Collection Interval: 5 min
Peg Condition: For each message successfully resolved to a Destination using a Routing Entity Type
of MSISDN.
Measurement Scope: Server Group
Recovery:
No action necessary.
RxFabrResolRateAvg
Measurement Group: Full Address Resolution Performance
Measurement Type: Average
Description: Average Addresses Successfully Resolved per second.
910-6528-001 Revision D, December 2012
410
Measurements
Collection Interval: 5 min
Peg Condition: The “average per second” is periodically calculated based on the total number of
addresses successfully resolved.
Measurement Scope: Server Group
Recovery:
No action required.
RxFabrResolRatePeak
Measurement Group: Full Address Resolution Performance
Measurement Type: Max
Description: Peak Addresses Successfully Resolved per second.
Collection Interval: 5 min
Peg Condition: At the end of each sample period associated with average successfully resolved message
rate, as defined by measurement RxFabrResolRateAvg, if the value exceeds the current value for this
measurement, then the measurement will be updated with the current sample periods value.
Measurement Scope: Server Group
Recovery:
No action required.
TxFabrAbandonRequest
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message that are abandoned.
Collection Interval: 5 min
Peg Condition: Each time the Routing Exception “Abandon Request” is invoked.
Measurement Scope: Server Group
Recovery:
No action necessary.
TxFabrFwdDefaultDest
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message forwarding attempts using a Default Destination.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
411
Measurements
Peg Condition: Each time the Routing Exception “Forward route the message with a user-configurable
Default Destination” is invoked.
Measurement Scope: Server Group
Recovery:
No action necessary.
TxFabrFwdNochange
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message forwarding attempts without changing the message.
Collection Interval: 5 min
Peg Condition: Each time the Routing Exception “Forward route the message unchanged” is invoked.
Measurement Scope: Server Group
Recovery:
No action necessary.
TxFabrFwdSuccess
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request messages successfully forwarded (all reasons).
Collection Interval: 5 min
Peg Condition: Each time the application successfully enqueues a Request message on the DSR Relay
Agent’s Request Message Queue.
Measurement Scope: Server Group
Recovery:
If this value is less than TxFabrMsgAttempt, then an internal resource error is occurring.
Contact the Tekelec Customer Care Center for assistance.
TxFabrMsgAttempt
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message forwarding attempts (all reasons).
Collection Interval: 5 min
Peg Condition: Each time the application attempts to enqueue a Request message on the DSR Relay
Agent’s “Request Message Queue”.
910-6528-001 Revision D, December 2012
412
Measurements
Measurement Scope: Server Group
Recovery:
No action necessary.
Full Address Based Resolution (FABR) Application Exception measurements
The "FABR Application Exception" measurement group is a set of measurements that provide
information about exceptions and unexpected messages and events that are specific to the FABR
feature.
Table 52: FABR Application Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxFabrDecodeFailureResol
Number of Request messages
rejected due to a message
decoding error.
5 min
RxFabrResolFailAll
Total number of Request
5 min
messages received which did not
resolve a Destination address.
RxFabrResolFailCmdcode
Number of Request messages
received with an unknown
Command Code.
5 min
RxFabrResolFailImpiMatch
Number of Request messages
received for which IMPI was
used for Destination address
resolution, but no Destination
address was found.
5 min
RxFabrResolFailImpuMatch
Number of Request messages
received for which IMPU was
used for Destination address
resolution, but no Destination
address was found.
5 min
RxFabrResolFailImsiMatch
Number of Request messages
received for which IMSI was
used for Destination address
resolution, but no Destination
address was found.
5 min
RxFabrResolFailMsisdnMatch
Number of Request messages
5 min
received for which MSISDN was
used for Destination address
resolution, but no Destination
address was found.
910-6528-001 Revision D, December 2012
413
Measurements
Measurement Tag
Description
Collection Interval
RxFabrResolFailNoAddrAvps
Number of Request messages
received without a Routing
Entity Address AVP.
5 min
RxFabrResolFailNoValidAddr
Number of Request messages
5 min
received with at least Routing
Entity Address AVP but no valid
Routing Entity Addresses were
found.
RxFabrUnkApplId
Number of Request messages
rejected due to an unknown
Application ID.
TxFabrDbConFail
Number of database queries
5 min
failed due to the Communication
Agent queue exhaustion.
TxFabrFwdFail
Number of routing attempt
5 min
failures due to internal resource
exhaustion.
5 min
RxFabrDecodeFailureResol
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request messages rejected due to a message decoding error.
Collection Interval: 5 min
Peg Condition: For each routing exception when the Application ID is not valid or the AVP extends
beyond the length of the message indicated by the Message Length parameter in the message header.
Measurement Scope: Server Group
Recovery:
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailAll
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Total number of Request messages received which did not resolve a Destination address.
Collection Interval: 5 min
Peg Condition: For each Request message which did not resolve to a Destination address.
Measurement Scope: Server Group
Recovery:
910-6528-001 Revision D, December 2012
414
Measurements
Validate which destination address is associated with the user identity address by using DP GUI.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailCmdcode
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with an unknown Command Code.
Collection Interval: 5 min
Peg Condition: For each routing exception where the (Application ID, Command Code) pair in the
incoming Request message is not configured.
Measurement Scope: Server Group
Recovery:
The currently provisioned Diameter Application IDs can be viewed in the FABR Configuration &
Maintenance GUI.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailImpiMatch
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received for which IMPI was used for Destination address
resolution, but no Destination address was found.
Collection Interval: 5 min
Peg Condition: For each message which did not successfully resolve to a Destination using a Routing
Entity Type of IMPI.
Measurement Scope: Server Group
Recovery:
Validate which destination address is associated with the user identity address by using DP GUI.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailImpuMatch
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received for which IMPU was used for Destination address
resolution, but no Destination address was found.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
415
Measurements
Peg Condition: For each message which did not successfully resolve to a Destination using a Routing
Entity Type of IMPU.
Measurement Scope: Server Group
Recovery:
Validate which destination address is associated with the user identity address by using DP GUI.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailImsiMatch
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received for which IMSI was used for Destination address
resolution, but no Destination address was found.
Collection Interval: 5 min
Peg Condition: For each message which did not successfully resolve to a Destination using a Routing
Entity Type of IMSI.
Measurement Scope: Server Group
Recovery:
Validate which destination address is associated with the user identity address by using DP GUI.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailMsisdnMatch
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received for which MSISDN was used for Destination
address resolution, but no Destination address was found.
Collection Interval: 5 min
Peg Condition: For each message which did not successfully resolve to a Destination using a Routing
Entity Type of MSISDN.
Measurement Scope: Server Group
Recovery:
Validate which destination address is associated with the user identity address by using DP GUI.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailNoAddrAvps
Measurement Group: Full Address Resolution Exception
910-6528-001 Revision D, December 2012
416
Measurements
Measurement Type: Simple
Description: Number of Request messages received without a Routing Entity Address AVP.
Collection Interval: 5 min
Peg Condition: For each routing exception with no valid User Identity address found and the number
of AVPs searched for the message was 0.
Measurement Scope: Server Group
Recovery:
If this event is considered abnormal, then use validate which AVPs are configured for routing with
the Application ID and Command Code using the FABR GUI screen.
Contact the Tekelec Customer Care Center for assistance.
RxFabrResolFailNoValidAddr
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with at least Routing Entity Address AVP but no
valid Routing Entity Addresses were found.
Collection Interval: 5 min
Peg Condition: For each routing exception with no valid User Identity address found and the number
of AVPs searched for the message was greater than 0.
Measurement Scope: Server Group
Recovery:
If this event is considered abnormal, then use validate which AVPs are configured for routing with
the Application ID and Command Code using the FABR GUI screen.
Contact the Tekelec Customer Care Center for assistance.
RxFabrUnkApplId
Measurement Group: Full Address Resolution Performance
Measurement Type: Simple
Description: Number of Request messages rejected due to an unknown Application ID.
Collection Interval: 5 min
Peg Condition: For each routing exception when the Application ID is not valid.
Measurement Scope: Server Group
Recovery:
1. The currently provisioned Diameter Application IDs can be viewed in the FABR Configuration &
Maintenance GUI.
910-6528-001 Revision D, December 2012
417
Measurements
2. The currently provisioned Application Routing Rules can be viewed using Main Menu Diameter
Configuration Application Routing Rules.
3. Contact the Tekelec Customer Care Center for assistance.
TxFabrDbConFail
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of database queries failed due to the Communication Agent queue exhaustion.
Collection Interval: 5 min
Peg Condition: Each time the application attempts to send DP queries and fails due to Communication
Agent queue exhaustion.
Measurement Scope: Server Group
Recovery:
Contact the Tekelec Customer Care Center for assistance.
TxFabrFwdFail
Measurement Group: Full Address Resolution Exception
Measurement Type: Simple
Description: Number of routing attempt failures due to internal resource exhaustion.
Collection Interval: 5 min
Peg Condition: Each time the application attempts to enqueue a Request message on the DSR Relay
Agent’s “Request Message Queue” or enqueue a Answer message on “DRL Answer Queue” and it
fails (e.g., queue full).
Measurement Scope: Server Group
Recovery:
Contact the Tekelec Customer Care Center for assistance.
Range Based Address Resolution (RBAR) Application Performance
measurements
The RBAR Application Performance measurement group is a set of measurements that provide
performance information that is specific to a RBAR Application. These measurements allow you to
determine how many messages are successfully forwarded and received to/from each RBAR
Application.
910-6528-001 Revision D, December 2012
418
Measurements
Table 53: RBAR Performance Measurement Report Fields
Measurement Tag
Description
RxRbarAvgMsgSize
Average size of Request message 5 min
received.
RxRbarMsgs
Number of Diameter messages 5 min
received by Range Based
Address Resolution application.
RxRbarResolAll
Number of Addresses Successful 5 min
Resolved to a Destination.
RxRbarResolAllMp
Number of Addresses Successful 5 min
Resolved to a Destination by the
MP.
RxRbarResolImpi
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IMPI.
RxRbarResolImpu
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IMPU.
RxRbarResolImsi
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IMSI.
RxRbarResolIpv4
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IPv4 Address.
RxRbarResolIpv6prefix
Number of Addresses Successful 5 min
Resolved with Routing Entity
type IPv6-Prefix Address.
RxRbarResolMsisdn
Number of Addresses Successful 5 min
Resolved with Routing Entity
type MSISDN.
RxRbarResolRateAvg
Average Addresses Successfully 5 min
Resolved per second.
RxRbarResolRatePeak
Peak Addresses Successfully
Resolved per second.
RxRbarResolSingleAddr
Number of Addresses Successful 5 min
Resolved with an Individual
Address.
RxRbarResolUnsigned16
Number of Addresses Successful 5 min
Resolved with Routing Entity
type UNSIGNED16.
910-6528-001 Revision D, December 2012
Collection Interval
5 min
419
Measurements
Measurement Tag
Description
Collection Interval
TxRbarFwdDefaultDest
Number of Request message
forwarding attempts using a
Default Destination.
5 min
TxRbarFwdNochange
Number of Request message
forwarding attempts without
changing the message.
5 min
TxRbarFwdSuccess
Number of Request messages
successfully forwarded (all
reasons).
5 min
TxRbarMsgAttempt
Number of Request message
forwarding attempts (all
reasons).
5 min
RxRbarAvgMsgSize
Measurement Group: Address Resolution Performance
Measurement Type: Average
Description: Average size of Request message received.
Collection Interval: 5 min
Peg Condition: Average calculated for each Request message received as defined by measurement
.RxRbarMsgs.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarMsgs
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Request messages received by RBAR.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and determines that the Application ID in
the message header is defined in the routing configuration and valid.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
420
Measurements
RxRbarResolAll
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved to a Destination.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and successfully resolves its Application ID,
Command Code and Routing Entity to a Destination and forwards the message to the DSR Relay
Agent.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolAllMp
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved to a Destination by the MP.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and successfully resolves its Application ID,
Command Code and Routing Entity to a Destination.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolImpi
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IMPI.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IMPI and
successfully resolves its Application ID, Command Code and Routing Entity to a Destination and
forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
421
Measurements
RxRbarResolImpu
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IMPU.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IMPU and
successfully resolves its Application ID, Command Code and Routing Entity to a Destination and
forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolImsi
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IMSI.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IMSI and
successfully resolves its Application ID, Command Code and Routing Entity to a Destination and
forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolIpv4
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IPv4 Address.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IPv4 Address
and successfully resolves its Application ID, Command Code and Routing Entity to a Destination and
forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
422
Measurements
RxRbarResolIpv6prefix
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type IPv6-Prefix Address.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IPv6-Prefix
Address and successfully resolves its Application ID, Command Code and Routing Entity to a
Destination and forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolMsisdn
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type MSISDN.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of MSISDN and
successfully resolves its Application ID, Command Code and Routing Entity to a Destination and
forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolRateAvg
Measurement Group: Address Resolution Performance
Measurement Type: Average
Description: Average Addresses Successfully Resolved per second.
Collection Interval: 5 min
Peg Condition: The average per second is periodically calculated based on the total number of addresses
successfully resolved as defined by measurement RxRbarResolAllMp.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
423
Measurements
RxRbarResolRatePeak
Measurement Group: Address Resolution Performance
Measurement Type: Max
Description: Peak Addresses Successfully Resolved per second
Collection Interval: 5 min
Peg Condition: At the end of each sample period associated with average successfully resolved message
rate, as defined by measurement RxRbarResolRateAvg, if the value exceeds the current value for this
measurement, then the measurement will be updated with the current sample periods value.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolSingleAddr
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with an Individual Address.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and uses the Address Exceptions to successfully
resolve its Application ID, Command Code and Routing Entity to a Destination and forwards the
message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
RxRbarResolUnsigned16
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Addresses Successful Resolved with Routing Entity type UNSIGNED16.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of UNSIGNED16
and successfully resolves its Application ID, Command Code and Routing Entity to a Destination and
forwards the message to the DSR Relay Agent.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
424
Measurements
TxRbarFwdDefaultDest
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message forwarding attempts using a Default Destination.
Collection Interval: 5 min
Peg Condition: Each time the Routing Exception Forward route the message with a user-configurable
Default Destination is invoked.
Measurement Scope: Server Group
Recovery:
No action required.
TxRbarFwdNoChange
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message forwarding attempts without changing the message.
Collection Interval: 5 min
Peg Condition: Each time the Routing Exception Forward route the message unchanged is invoked.
Measurement Scope: Server Group
Recovery:
No action required.
TxRbarFwdSuccess
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Request messages successfully forwarded (all reasons).
Collection Interval: 5 min
Peg Condition: Each time the application successfully enqueues a Request message on the DSR Relay
Agent's Request Message Queue.
Measurement Scope: Server Group
Recovery:
If this value is less than measurement TxRbarMsgAttempt, then an internal resource error is
occurring. Contact the Tekelec Customer Care Center. if needed.
910-6528-001 Revision D, December 2012
425
Measurements
TxRbarMsgAttempt
Measurement Group: Address Resolution Performance
Measurement Type: Simple
Description: Number of Request message forwarding attempts (all reasons).
Collection Interval: 5 min
Peg Condition: Each time the application attempts to enqueue a Request message on the DSR Relay
Agent's Request Message Queue.
Measurement Scope: Server Group
Recovery:
No action required.
Range Based Address Resolution (RBAR) Application Exception
measurements
The RBAR Application Exception measurement group is a set of measurements that provide
performance information that is specific to a RBAR Application. These measurements allow you to
determine how many messages are successfully forwarded and received to/from each RBAR
Application.
Table 54: RBAR Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxRbarDecodeFailureResol
Number of Request messages
rejected due to a message
decoding error.
5 min
RxRbarResolFailAll
Number of Request messages
received which did not resolve
to a provisioned address or
address range.
5 min
RxRbarResolFailCmdcode
Number of Request messages
received with an unknown
Command Code.
5 min
RxRbarResolFailDbFail
Number of routing attempt
5 min
failures due to internal database
inconsistency failure.
RxRbarResolFailImpiMatch
Number of Request messages
received with a valid IMPI that
did not match a provisioned
address or address range.
910-6528-001 Revision D, December 2012
5 min
426
Measurements
Measurement Tag
Description
Collection Interval
RxRbarResolFailImpuMatch
Number of Request messages
5 min
received with a valid IMPU that
did not match a provisioned
address or address range.
RxRbarResolFailImsiMatch
Number of Request messages
received with a valid IMSI that
did not match a provisioned
address or address range.
RxRbarResolFailIpv4Match
Number of Request messages
5 min
received with an IPv4 Address
that did not match a provisioned
address or address range.
5 min
RxRbarResolFailIpv6prefixMatch Number of Request messages
5 min
received with an IPv6-Prefix
Address that did not match a
provisioned address or address
range.
RxRbarResolFailMsisdnMatch
Number of Request messages
5 min
received with a valid MSISDN
that did not match a provisioned
address or address range.
RxRbarResolFailNoAddrAvps
Number of Request messages
received without a Routing
Entity Address AVP.
RxRbarResolFailNoValidAddr
Number of Request messages
5 min
received with at least Routing
Entity Address AVP but no valid
Routing Entity Addresses were
found.
5 min
RxRbarResolFailUnsigned16Match Number of Request messages
5 min
received with an UNSIGNED16
value that did not match a
provisioned address or address
range.
RxRbarUnkApplId
Number of Request messages
rejected due to an unknown
Application ID.
5 min
RxRbarDecodeFailureResol
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages rejected due to a message decoding error.
910-6528-001 Revision D, December 2012
427
Measurements
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and does not decode an AVP which extends
beyond the length of the message indicated by the Message Length parameter in the message header.
Measurement Scope: Server Group
Recovery:
While parsing the message, the message content was inconsistent with the Message Length in the
message header. These protocol violations can be caused by the originator of the message (identified
by the Origin-Host AVP in the message) or the peer who forwarded the message to this node.
RxRbarResolFailAll
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received which did not resolve to a provisioned address
or address range.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and, using the provisioned individual addresses
or address ranges, does not successfully resolve to a Destination.
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarResolFailCmdcode
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with an unknown Command Code.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and, after attempting to validate the ordered
pair (Application ID and Command Code), the Command Code is unknown. RBAR invokes the routing
exception handling procedure assigned to this Application ID and Routing Exception Type.
Measurement Scope: Server Group
Recovery:
The order pair (Application ID and Command Code) is not provisioned in the Address Resolutions
routing configuration.
View the currently provisioned Application IDs and Command Codes by selecting
RBARConfigurationAddress Resolutions.
910-6528-001 Revision D, December 2012
428
Measurements
RxRbarResolFailDbFail
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of routing attempt failures due to internal database inconsistency failure.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message and encounters a run-time database
inconsistency.
Measurement Scope: Server Group
Recovery:
If this problem occurs, contact the Tekelec Customer Care Center.
RxRbarResolFailImpiMatch
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with a valid IMPI that did not match a provisioned
address or address range.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IMPI and, using
the provisioned individual addresses or address ranges, does not successfully resolve to a Destination.
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarResolFailImpuMatch
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with a valid IMPU that did not match a provisioned
address or address range.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IMPU and,
using the provisioned individual addresses or address ranges, does not successfully resolve to a
Destination.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
429
Measurements
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarResolFailImsiMatch
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with a valid IMSI that did not match a provisioned
address or address range.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IMSI and, using
the provisioned individual addresses or address ranges, does not successfully resolve to a Destination.
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarResolFailIpv4Match
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with an IPv4 Address that did not match a
provisioned address or address range
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IPv4 Address
and, using the provisioned individual addresses or address ranges, does not successfully resolve to
a Destination.
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
910-6528-001 Revision D, December 2012
430
Measurements
RxRbarResolFailIpv6prefixMatch
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with an IPv6-Prefix Address that did not match
a provisioned address or address range
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of IPv6-Prefix
Address and, using the provisioned individual addresses or address ranges, does not successfully
resolve to a Destination.
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarResolFailMsisdnMatch
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with a valid MSISDN that did not match a
provisioned address or address range
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of MSISDN and,
using the provisioned individual addresses or address ranges, does not successfully resolve to a
Destination.
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarResolFailNoAddrAvps
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received without a Routing Entity Address AVP.
910-6528-001 Revision D, December 2012
431
Measurements
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message, with the number of AVPs searched–as defined
by measurement RxRbarAvgAddrAvps for the message–as 0 and hence, a valid Routing Entity address
cannot be found using any of the Routing Entity Types assigned to the ordered pair (Application ID
and Command Code).
Measurement Scope: Server Group
Recovery:
This may be a normal event or an event associated with misprovisioned address resolution
configuration. If this event is considered abnormal, validate which AVPs are configured for routing
with the Application ID and Command Code.
View the currently provisioned Application IDs and Command Codes by selecting
RBARConfigurationAddress Resolutions.
RxRbarResolFailNoValidAddr
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with at least Routing Entity Address AVP but no
valid Routing Entity Addresses were found.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message, with the number of AVPs searched–as defined
by measurement RxRbarAvgAddrAvps for the message–as > 0 but, a valid Routing Entity address
cannot be found using any of the Routing Entity Types assigned to the ordered pair (Application ID
and Command Code).
Measurement Scope: Server Group
Recovery:
This may be a normal event or an event associated with misprovisioned address resolution
configuration. If this event is considered abnormal, validate which AVPs are configured for routing
with the Application ID and Command Code.
View the currently provisioned Application IDs and Command Codes by selecting
RBARConfigurationAddress Resolutions.
RxRbarResolFailUnsigned16Match
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages received with an UNSIGNED16 value that did not match
a provisioned address or address range.
Collection Interval: 5 min
Peg Condition: When RBAR receives a Request message with a Routing Entity type of UNSIGNED16
and, using the provisioned individual addresses or address ranges, does not successfully resolve to
a Destination.
910-6528-001 Revision D, December 2012
432
Measurements
Measurement Scope: Server Group
Recovery:
An individual address or address range associated with the Application ID, Command Code and
Routing Entity Type may be missing from the RBAR configuration. Validate which address and address
range tables are associated with the Application ID, Command Code and Routing Entity Type.
View the currently provisioned Application IDs, Command Codes, and Routing Entity Types by
selecting RBARConfigurationAddress Resolutions.
RxRbarUnkApplId
Measurement Group: Address Resolution Exception
Measurement Type: Simple
Description: Number of Request messages rejected due to an unknown Application ID.
Collection Interval: 5 min
Peg Condition: When a Request message received and the Application ID is not present in the RBAR
configuration.
Measurement Scope: Server Group
Recovery:
The DSR Relay Agent forwarded a Request message to the address resolution application which
contained an unrecognized Diameter Application ID in the header. Either a DSR Relay Agent application
routing rule is misprovisioned or the Application ID is not provisioned in the RBAR routing
configuration.
1. View the currently provisioned Diameter Application IDs by selecting
RBARConfigurationApplications.
2. View the currently provisioned Application Routing Rules by selecting DiameterConfiguration
Application Routing Rules.
Route List measurements
The Route List measurement report is a set of measurements associated with the usage of Route Lists.
These measurements will allow the user to determine which Route Lists are most commonly used
and the percentage of times that messages were successfully (or unsuccessfully) routed using the
Route List.
Table 55: Route List Measurement Report Fields
Measurement Tag
Description
RxRouteListFailure
Number of times that a Route
5 min
List was selected for routing a
Request message and the DSR
was unable to successfully route
the message.
910-6528-001 Revision D, December 2012
Collection Interval
433
Measurements
Measurement Tag
Description
Collection Interval
RxRouteListSelected
Number of times the Route List 5 min
was selected for routing a
Request message.
RxRouteListUnavailable
Number of Request messages
from a downstream peer that
were rejected by a Local Node
because the Route List selected
had an "Operational Status" of
"Unavailable".
TmRouteListOutage
Time duration that the Route List 5 min
was unavailable during the
measurement interval.
5 min
RxRouteListFailure
Measurement Group: Route List
Measurement Type: Simple
Description: The number of times that a Route List was selected for routing a Request message and
the DSR was unable to successfully route the message. There are several reasons why a message cannot
be routed using a Route List:
•
•
•
•
The Operational Status of the Route List is Unavailable
The peers in the active Route Group do not support the Application ID in the Request message
The Answer response timer is expiring for messages routed through the active Route Group
Message loop detection is being detected for the peers in the active Route Group
Collection Interval: 5 min
Peg Condition: When the DSR selects a Route List to route a Request message and either the Route
List's Operational Status is Unavailable or the DSR attempts to route the call but exhausts all routes
associated with the Route List and sends an Answer response 3002
(DIAMETER_UNABLE_TO_DELIVER).
The Route List measurement is associated with the Route List selected for routing.
Measurement Scope: Server Group
Recovery:
1. Check the Route List settings using the Diameter > Configuration > Route Lists page.
2. Contact the Tekelec Customer Care Center for assistance if needed.
RxRouteListSelected
Measurement Group: Route List
Measurement Type: Simple
Description: Number of times that Route List was selected for routing a Request message.
910-6528-001 Revision D, December 2012
434
Measurements
Collection Interval: 5 min
Peg Condition: When the DSR selects a Route List for routing a message.
The Route List measurement is associated with the Route List selected for routing.
Measurement Scope: Server Group
Recovery:
No action required.
RxRouteListUnavailable
Measurement Group: Route List
Measurement Type: Simple
Description: The number of Request messages from a downstream peer that were rejected by a Local
Node because the selected Route List had an Operational Status of Unavailable.
Collection Interval: 5 min
Peg Condition: Request message from a downstream peer is rejected by a Local Node because the
selected Route List had an Operational Status of Unavailable. This occurs when the Route List was
selected via a Peer Routing Rule or implicit routing but its Operational Status was Unavailable.
The Route List measurement is associated with the Route List selected for routing.
Measurement Scope: Server Group
Recovery:
1. The operation status of the Route List should be verified using the Diameter > Maintenance >
Route Lists page.
2. Contact the Tekelec Customer Care Center for assistance if needed.
TmRouteListOutage
Measurement Group: Route List
Measurement Type: Simple
Description: Time duration that a Route List was unavailable during the measurement interval. This
will appear as an aggregate value retrieved from all DA-MPs in a Network Element.
Collection Interval: 5 min
Peg Condition: The time duration interval starts when one of the following conditions occurs:
1. A new collection interval for the measurement begins and Alarm 22053 is asserted.
2. Alarm 22053 is asserted.
The time duration interval stops when one of the following conditions occurs:
1. The current collection interval for the measurement ends and Alarm 22053 is asserted.
2. Alarm 22053 is cleared.
When a time duration interval completes, the time measured is added to the total measurement value.
910-6528-001 Revision D, December 2012
435
Measurements
Measurement Scope: Server Group
Recovery:
1. The operation status of the Route List should be verified using the Diameter > Maintenance >
Route Lists page.
2. Contact the Tekelec Customer Care Center for assistance if needed.
Routing Usage measurements
The Routing Usage measurement report allows you to evaluate how ingress Request messages are
being routed internally within the Relay Agent.
Table 56: Routing Usage Measurement Report Fields
Measurement Tag
Description
Collection Interval
RxRoutedIntraMPAttempt
Number of attempts to route an 5 min
ingress request message via
intra-MP routing.
RxRoutedPeerDirect
Number of Request messages
implicitly routed directly to a
peer.
RxRoutedPeerRouteList
Number of Request messages
5 min
implicitly routed to a peer via its
alternate implicit route.
RxRoutedPrt
Number of Request messages
5 min
routed using Peer Routing Rules.
5 min
RxRoutedIntraMPAttempt
Measurement Group: Routing Usage
Measurement Type: Simple
Description: The number of attempts to route an ingress request message via intra-MP routing.
Collection Interval: 5 min
Peg Condition: When the DSR selects a transport connection controlled by the local MP and successfully
queues the Request message on the local message queue.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
910-6528-001 Revision D, December 2012
436
Measurements
RxRoutedPeerDirect
Measurement Group: Routing Usage
Measurement Type: Simple
Description: The number of Request messages implicitly routed directly to a peer.
Collection Interval: 5 min
Peg Condition: When the DSR does not find a Peer Routing Rule that matches message content, the
Destination-Host AVP is present and its value matches a FQDN of a peer, and the peer is available
for egress routing.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRoutedPeerRouteList
Measurement Group: Routing Usage
Measurement Type: Simple
Description: The number of Request messages implicitly routed to a peer via its alternate implicit
route.
Collection Interval: 5 min
Peg Condition: When the DSR does not find a Peer Routing Rule that matches message content, the
Destination-Host AVP is present and its value matches a FQDN of a peer, the peer is Unavailable for
egress routing, and the user-defined alternate implicit route for the peer contains a valid Route List.
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
RxRoutedPrt
Measurement Group: Routing Usage
Measurement Type: Simple
Description: The number of Request messages routed using Peer Routing Rules.
Collection Interval: 5 min
Peg Condition:When the DSR selects the highest priority Peer Routing Rule which matches message
content.
910-6528-001 Revision D, December 2012
437
Measurements
The connection measurement is associated with the connection from which the Request message was
received.
Measurement Scope: Server Group
Recovery:
No action required.
Session Binding Repository (SBR) Exception measurements
The "SBR Exception" measurement group is a set of measurements that provide information about
exceptions and unexpected messages and events specific to the SBR application. Measurements such
as the following are included in this group.
Table 57: SBR Exception Measurement Report Fields
Measurement Tag
Description
Collection Interval
Sbr.TxError
Number of error responses sent 5 min
during the collection interval
Sbr.TxShedCreates
Number of load shed error
5 min
responses per task indicating
load shed create sent during the
collection interval
Sbr.TxShedWrites
Number of load shed error
5 min
responses per task indicating
load shed write sent during the
collection interval
Sbr.TxShedReads
Number of load shed error
responses per task indicating
load shed read sent during the
collection interval
5 min
Sbr.TxShedAll
Number of load shed error
responses per task indicating
load shed all sent during the
collection interval
5 min
Sbr.StackQueueFull
Number of StackEvents
5 min
discarded due to SBR task queue
full condition
Sbr.TxError
Measurement Group: SBR Exception
Measurement Type: Simple
Description: The number of error responses sent during the collection interval.
910-6528-001 Revision D, December 2012
438
Measurements
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application sends an error
response.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by return code:
•
•
•
•
•
•
0 = Unknown message type
1 = SBDB is full
2 = SBDB returned an error
3 = Session record not found
4 = Required parameter was missing
5 = Request shed due to load
Recovery:
1. Any counts for this measurement should be investigated.
2. For counts of unknown message type (return code 0), SBDB errors (return code 2) or missing
parameters (return code 4), contact the Tekelec Customer Care Center for assistance.
3. For counts of SBDB is full messages (return code 1), additional capacity may be required. Contact
the Tekelec Customer Care Center for assistance.
4. Counts of missing records (return code 3) occur if a session was removed during audit and then
another request was received. To prevent this, increase the Stale SBDB session binding age setting
found on the CPA -> Configuration -> SBR pane.
5. Any counts of requests shed due to load (return code 5) indicate that the SBR may be congested.
Inspect the alarms for the SBR for more information regarding the severity of the congestion. Also
check the Sbr.TxShed measurements to see which requests are being shed.
Sbr.TxShedCreates
Measurement Group: SBR Exception
Measurement Type: Simple
Description: The number of load shed error responses sent that indicate creation operations shed
during the collection interval. Creation operations are shed during minor congestion.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR transmits a load shed error
response.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: Any counts for this measurement should be investigated. Counts for this measurement
indicate that the SBR may be congested. Inspect the alarms for the SBR for more information regarding
the severity of the congestion. The Sbr.TxError measurement will also show counts when this
measurement shows counts. Another associated measurement, Sbr.RxIngressMsgQueueAvg, shows
the average percentage of queue length utilization, which is used to determine congestion.
910-6528-001 Revision D, December 2012
439
Measurements
Sbr.TxShedWrites
Measurement Group: SBR Exception
Measurement Type: Simple
Description: The number of load shed error responses sent that indicate update operations shed during
the collection interval. Update operations are shed during major congestion.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR transmits a load shed error
response.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: Any counts for this measurement should be investigated. Counts for this measurement
indicate that the SBR may be congested. Inspect the alarms for the SBR for more information regarding
the severity of the congestion. The Sbr.TxError measurement will also show counts when this
measurement shows counts. Another associated measurement, Sbr.RxIngressMsgQueueAvg, shows
the average percentage of queue length utilization, which is used to determine congestion.
Sbr.TxShedReads
Measurement Group: SBR Exception
Measurement Type: Simple
Description: The number of load shed error responses sent that indicate read operations shed during
the collection interval. Read operations are shed during critical congestion.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR transmits a load shed error
response.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: Any counts for this measurement should be investigated. Counts for this measurement
indicate that the SBR may be congested. Inspect the alarms for the SBR for more information regarding
the severity of the congestion. The Sbr.TxError measurement will also show counts when this
measurement shows counts. Another associated measurement, Sbr.RxIngressMsgQueueAvg, shows
the average percentage of queue length utilization, which is used to determine congestion.
Sbr.TxShedAll
Measurement Group: SBR Exception
Measurement Type: Simple
Description: The number of load shed error responses indicating load shed sent during the collection
interval.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
440
Measurements
Peg Condition: This measurement is incremented by one each time the SBR transmits a load shed error
response.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: Any counts for this measurement should be investigated. Counts for this measurement
indicate that the SBR may be congested. Inspect the alarms for the SBR for more information regarding
the severity of the congestion. The Sbr.TxError measurement will also show counts when this
measurement shows counts.
Sbr.StackQueueFull
Measurement Group: SBR Exception
Measurement Type: Simple
Description: StackEvents discarded due to the SBR's task queue being full.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR discards a StackEvent due
to its task queue being full.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: Any counts for this measurement should be investigated. Counts for this measurement
indicate that the SBR may be congested. Inspect the alarms for the SBR for more information regarding
the severity of the congestion. The Sbr.TxError measurement will also show counts when this
measurement shows counts.
Session Binding Repository (SBR) Performance measurements
The "SBR Performance" measurement group contains measurements that provide performance
information that is specific to the SBR application. Counts for various expected/normal messages and
events are included in this group. Measurements such as the following are included.
Table 58: SBR Performance Measurement Report Fields
Measurement Tag
Description
Collection Interval
Sbr.RxCreate
Number of create requests
received during the collection
interval
5 min
Sbr.RxUpdate
Number of update requests
received during the collection
interval
5 min
Sbr.RxRead
Number of read requests
received during the collection
interval
5 min
910-6528-001 Revision D, December 2012
441
Measurements
Measurement Tag
Description
Collection Interval
Sbr.RxDelete
Number of delete requests
received during the collection
interval
5 min
Sbr.RxStatus
Number of status requests
received during the collection
interval
5 min
Sbr.TxSuccess
Number of success responses
sent during the collection
interval
5 min
Sbr.TxError
Number of error responses sent 5 min
during the collection interval
Sbr.RxReqRatePeak
Maximum number of
5 min
transactions/second processed
by the SBR during the reporting
interval
Sbr.RxServTimeAvg
Average transaction service time 5 min
in microseconds during the
reporting interval
Sbr.RxServTimePeak
Peak transaction service time in 5 min
microseconds during the
reporting interval
Sbr.EvStaleRecRemoved
Number of stale session binding 5 min
records cleaned by the audit
procedure during the reporting
interval
Sbr.EvCreateUpdateMod
Number of create operations
turned into update operations
during the reporting interval
5 min
Sbr.EvAvgSessionAge
Average age of all current
session bindings
5 min
Sbr.RxReqRateAvg
Average of all message
processing rate samples taken
during the collection interval
5 min
Sbr.EvSchdStaleRec
Expected number of stale session 5 min
bindings scheduled for deletion
Sbr.EvStaleRecRevived
Number of session bindings
5 min
older than the mostly age that
have their timestamps refreshed
to the current time
Sbr.EvMostlyStaleSessPartition Number of session bindings
older than the mostly stale age
in each partition
910-6528-001 Revision D, December 2012
5 min
442
Measurements
Measurement Tag
Description
Collection Interval
Sbr.EvAvgSessionAgePartition
Average age of session binding 5 min
of a partition
Sbr.RxIngressMsgQueuePeak
Peak SBR Ingress Message
Queue utilization measured
during the collection interval
5 min
Sbr.RxIngressMsgQueueAvg
Average SBR Ingress Message
Queue utilization measured
during the collection interval
5 min
Sbr.RxCreate
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of create requests received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application receives a
create request.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxUpdate
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of update requests received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application receives an
update request.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxRead
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of read requests received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application receives a read
request.
910-6528-001 Revision D, December 2012
443
Measurements
Measurement Scope: Server Group
Recovery: None required
Sbr.RxDelete
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of delete requests received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application receives a
delete request.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxStatus
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of status requests received during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application receives a
status request.
Measurement Scope: Server Group
Recovery: None required
Sbr.TxSuccess
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of success responses sent during the collection interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application sends a success
response.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxReqRatePeak
Measurement Group: SBR Performance
Measurement Type: Max
910-6528-001 Revision D, December 2012
444
Measurements
Description: The maximum number of transactions/second processed by the SBR during the reporting
interval.
Collection Interval: 5 min
Peg Condition: This measurement is maximum number of transactions/second processed by the SBR
application during the collection interval.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxServTimeAvg
Measurement Group: SBR Performance
Measurement Type: Average
Description: The average transaction service time in microseconds during the reporting interval
Collection Interval: 5 min
Peg Condition: This measurement is the average transaction service time in microseconds processed
by the SBR application.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxServTimePeak
Measurement Group: SBR Performance
Measurement Type: Max
Description: The peak transaction service time in microseconds during the reporting interval.
Collection Interval: 5 min
Peg Condition: This measurement is the peak transaction service time in microseconds processed by
the SBR application.
Measurement Scope: Server Group
Recovery: None required
Sbr.EvStaleRecRemoved
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of stale session binding records cleaned by the audit procedure during the
reporting interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application removes a
stale session binding record during the audit procedure. This measurement only shows counts in the
collection interval that occurs immediately after the audit has run.
Measurement Scope: Server Group
910-6528-001 Revision D, December 2012
445
Measurements
Recovery: None required
Sbr.EvCreateUpdateMod
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of create operations turned into update operations during the reporting
interval.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time the SBR application turns a create
operation into an update operation. That is, it finds a pre-existing sessionId.
Measurement Scope: Server Group
Recovery: None required
Sbr.EvAvgSessionAge
Measurement Group: SBR Performance
Measurement Type: Average
Description: The average age in seconds of all current session bindings.
Collection Interval: 5 min
Peg Condition: This measurement is the average age of all current session bindings processed by the
SBR application. This measurement only shows counts in the collection interval that occurs immediately
after the audit has run.
Measurement Scope: Server Group
Recovery: None required
Sbr.RxReqRateAvg
Measurement Group: SBR Performance
Measurement Type: Average
Description: The average message processing rate per second.
Collection Interval: 5 min
Peg Condition: The average of all message processing rate samples per second taken during the
collection interval.
Measurement Scope: Server Group
Recovery: None required
Sbr.EvSchdStaleRec
Measurement Group: SBR Performance
Measurement Type: Simple
910-6528-001 Revision D, December 2012
446
Measurements
Description: The expected number of stale session bindings scheduled for deletion.
Collection Interval: 5 min
Peg Condition: This measurement is the expected number of stale session bindings to be deleted during
the next stale session binding record audit. This measurement only shows counts in the collection
interval that occurs immediately after the audit has run.
Measurement Scope: Server Group
Recovery: None required
Sbr.EvStaleRecRevived
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of session bindings older than the "mostly age" that have their timestamps
refreshed to the current time.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time a session binding that is older than
the "mostly stale" age has its timestamp refreshed to the current time.
Measurement Scope: Server Group
Recovery: None required
Sbr.EvMostlyStaleSessPartition
Measurement Group: SBR Performance
Measurement Type: Simple
Description: The number of session bindings older than the "mostly stale" age in each partition.
Collection Interval: 5 min
Peg Condition: This measurement is incremented by one each time a session binding becomes older
than the "mostly stale" age. This measurement only shows counts in the collection interval that occurs
immediately after the audit has run.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by partition
Recovery: None required
Sbr.EvAvgSessionAgePartition
Measurement Group: SBR Performance
Measurement Type: Average
Description: The average age in seconds of session binding of a partition.
Collection Interval: 5 min
910-6528-001 Revision D, December 2012
447
Measurements
Peg Condition: This measurement will be computed during each partition’s audit process and updated
appropriately. This measurement only shows counts in the collection interval that occurs immediately
after the audit has run.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by partition
Recovery: None required
Sbr.RxIngressMsgQueuePeak
Measurement Group: SBR Performance
Measurement Type: Max
Description: The peak SBR Ingress Message Queue utilization measured during the collection interval
Collection Interval: 5 min
Peg Condition: This measurement is the peak ingress message queue utilization by the SBR application.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: None required
Sbr.RxIngressMsgQueueAvg
Measurement Group: SBR Performance
Measurement Type: Average
Description: The average SBR Ingress Message Queue utilization in percent measured during the
collection interval. This measurement, if it goes above 85% percent, will trigger a congestion alarm.
Collection Interval: 5 min
Peg Condition: This measurement is the average ingress message queue utilization in percent by the
SBR application.
Measurement Scope: Server Group
Measurement Dimension: Arrayed by subresource
Recovery: None required
910-6528-001 Revision D, December 2012
448
Chapter
6
Copyright, notice, trademarks, and patents
Topics:
•
EAGLE XG Diameter Signaling Router (DSR) Copyright, Notice, Trademarks, and Patents....450
910-6528-001 Revision D, December 2012
This section provides important information about
copyrights, notices, trademarks, and patents
associated with this product.
449
Copyright, notice, trademarks, and patents
EAGLE XG Diameter Signaling Router (DSR) - Copyright, Notice,
Trademarks, and Patents
©
2012 Tekelec
All Rights Reserved
Printed in U.S.A.
Notice
Information in this documentation is subject to change without notice. Unauthorized use, copying, or
translation of this documentation can result in civil or criminal penalties.
Any export of Tekelec products is subject to the export controls of the United States and the other
countries where Tekelec has operations.
No part of this documentation may be reproduced, translated, or transmitted in any form or by any
means, electronic or mechanical, including photocopying or recording, for any purpose without the
express written permission of an authorized representative of Tekelec.
Other product names used herein are for identification purposes only, and may be trademarks of their
respective companies.
RoHS 5/6 - As of July 1, 2006, all products that comprise new installations shipped to European Union
member countries will comply with the EU Directive 2002/95/EC "RoHS" (Restriction of Hazardous
Substances). The exemption for lead-based solder described in the Annex will be exercised. RoHS 5/6
compliant components will have unique part numbers as reflected in the associated hardware and
installation manuals.
WEEE - All products shipped to European Union member countries comply with the EU Directive
2002/96/EC, Waste Electronic and Electrical Equipment. All components that are WEEE compliant
will be appropriately marked. For more information regarding Tekelec's WEEE program, contact your
sales representative.
Trademarks
TEKELEC, EAGLE, G-Flex, G-Port, and CAMIANT are registered trademarks of Tekelec. The Tekelec
logo, A-Port, EAGLE 5, EAGLE 5 ISS, IP7, IP7 Secure Gateway, V-Flex, ngHLR, BLUESLICE, and
Subscriber Data Server (SDS) are trademarks of Tekelec. All other trademarks are the property of their
respective owners.
Patents
This product may be covered by one or more of the following U.S. and foreign patents:
U.S. Patent Numbers:
6,795,546; 6,901,262; 6,967,956; 7,043,000; 7,190,959; 7,286,516; 7,318,091; 7,383,298; 7,403,537; 7,406,159;
7,466,807; 7,633,872; 7,633,969; 7,650,367; 7,706,343; 7,743,131; 7,804,789; 7,860,799; 7,916,685; 8,179,885;
8,224,928;
Foreign Patent Numbers:
EP 1314324; EP 1568203; EP 1846832; EP 1847076; ZL 200780017383.1;
910-6528-001 Revision D, December 2012
450
Glossary
B
BIOS
Basic Input-Output System
C
CAPM
Computer-aided policy making
CEA
Capability-Exchange-Answer
The Diameter response that the
prepaid rating engine sends to the
Mobile Originated application
during capability exchanges.
CER
Capabilities-Exchange-Request
A Diameter message that the
Mobile Originated application
sends to a prepaid rating engine to
perform a capability exchange. The
CER (indicated by the
Command-Code set to 257 and the
Command Flags' 'R' bit set) is sent
to exchange local capabilities.The
prepaid rating engine responds
with a
Capability-Exchange-Answer
(CEA) message.
Charging Proxy Application
A DSR Application that is
responsible for sending and
receiving Diameter accounting
messages.
CMOS
Complementary Metal Oxide
Semiconductor
CMOS semiconductors use both
NMOS (negative polarity) and
PMOS (positive polarity) circuits.
Since only one of the circuit types is
on at any given time, CMOS chips
910-6528-001 Revision D, December 2012
451
Glossary
C
require less power than chips using
just one type of transistor.
ComAgent
Communication Agent
A common infrastructure component
delivered as part of a common
plug-in, which provides services to
enable communication of message
between application processes on
different servers.
COMCOL
Communications Core Object
Library
A suite of re-usable C++ libraries, as
well as processes and procedures
available for use in Tekelec products.
Many of its features are focused
toward the communications area of
software developments, although it
purpose is not intended to restrict
its functionality to any particular
area
Communication Agent
See ComAgent.
CPA
Charging Proxy Application
A local application running on the
DSR.
CSV
Comma-separated values
The comma-separated value file
format is a delimited data format
that has fields separated by the
comma character and records
separated by newlines (a newline
is a special character or sequence
of characters signifying the end of
a line of text).
D
910-6528-001 Revision D, December 2012
452
Glossary
D
DB
Database
Daughter Board
Documentation Bulletin
Diameter
Protocol that provides an
Authentication, Authorization, and
Accounting (AAA) framework for
applications such as network access
or IP mobility. Diameter works in
both local and roaming AAA
situations.
Diameter can also be used as a
signaling protocol for mobility
management which is typically
associated with an IMS or wireless
type of environment. Diameter is the
successor to the RADIUS protocol.
The MPE device supports a range of
Diameter interfaces, including Rx,
Gx, Gy, and Ty.
DNS
Domain Name System
A system for converting Internet
host and domain names into IP
addresses.
DP
Data Processor
The repository of subscriber data on
the individual DSR node elements.
The DP hosts the full address
resolution database.
DPA
Disconnect-Peer-Answer
A message used by a Diameter
node to answer the
Disconnect-Peer-Request (DPR).
DPR
Disconnect-Peer-Request
A message used by a Diameter
node to inform its peer of its intent
910-6528-001 Revision D, December 2012
453
Glossary
D
to disconnect the transport layer.
Upon receipt of a DPR, the
Disconnect-Peer-Answer (DPA) is
returned.
DRL
Diameter Routing Layer
The software layer of the Eagle XG
Diameter stack that implements
Diameter routing.
DSR
Diameter Signaling Router
A set of co-located Message
Processors which share common
Diameter routing tables and are
supported by a pair of OAM servers.
A DSR Network Element may
consist of one or more Diameter
nodes.
DWA
Device-Watchdog-Answer
A Diameter message used with the
Device-Watchdog-Request (DWR)
message to proactively detect
connection failures. If no traffic is
detected on a connection between
the Mobile Originated application
and the prepaid rating engine
within the configured timeout
period, a DWR message is sent to
the prepaid rating engine. If the
prepaid rating engine fails to
respond with a DWA within the
required time, the connection is
closed with the prepaid rating
engine and initiates failover
procedures. All new and pending
requests are then sent to the
secondary server.
DWR
Device-Watchdog-Request
A Diameter message used with the
Device-Watchdog-Answer (DWA)
910-6528-001 Revision D, December 2012
454
Glossary
D
message to proactively detect
connection failures. If no traffic is
detected on a connection between
the Mobile Originated application
and the Diameter server within the
configured timeout period, a DWR
message is sent to the Diameter
Server. If the Diameter server fails
to respond within the required
time, the connection is closed with
the Diameter server and initiates
failover procedures. All new and
pending requests are then sent to
the secondary Diameter server.
F
FABR
Full Address Based Resolution
Provides an enhanced DSR routing
capability to enable network
operators to resolve the designated
Diameter server addresses based on
individual user identity addresses
in the incoming Diameter request
messages.
Full Address Based Resolution
See FABR.
G
GUI
Graphical User Interface
The term given to that set of items
and facilities which provide the
user with a graphic means for
manipulating screen data rather
than being limited to character
based commands.
H
HA
High Availability
High Availability refers to a system
or component that operates on a
continuous basis by utilizing
910-6528-001 Revision D, December 2012
455
Glossary
H
redundant connectivity, thereby
circumventing unplanned outages.
HP
Hewlett-Packard
I
IPFE
IP Front End
A traffic distributor that routes TCP
traffic sent to a target set address by
application clients across a set of
application servers. The IPFE
minimizes the number of externally
routable IP addresses required for
application clients to contact
application servers.
K
KPI
Key Performance Indicators
M
Message Processor
See MP
MP
Message Processor
The role of the Message Processor
is to provide the application
messaging protocol interfaces and
processing. However, these servers
also have OAM&P components.
All Message Processors replicate
from their Signaling OAM's
database and generate faults to a
Fault Management System.
N
NTP
Network Time Protocol
O
OAM
910-6528-001 Revision D, December 2012
Operations, Administration, and
Maintenance
456
Glossary
O
The application that operates the
Maintenance and Administration
Subsystem which controls the
operation of many Tekelec products.
OID
Object Identifier
An identifier for a managed object
in a Management Information Base
(MIB) hierarchy. This can be
depicted as a tree, the levels of which
are assigned by different
organizations. Top level MIB OIDs
belong to different standard
organizations. Vendors define
private branches that include
managed objects for their own
products.
P
PDU
Protocol Data Unit
Peer
A Diameter node to which a given
Diameter node has a direct
transport connection.
PM&C
Platform Management and
Configuration
Server with hardware management
software that manages the
remaining servers (System OAMs
and MPs) in a network element.
The terms PM&C and system
manager are used synonymously
in the online help documentation.
PM&C functions include hardware
monitoring and control, switch
configuration, and software
installation and upgrade.
Provides hardware and platform
management capabilities at the site
level for Tekelec platforms. The
PMAC application manages and
monitors the platform and installs
910-6528-001 Revision D, December 2012
457
Glossary
P
the TPD operating system from a
single interface.
R
Range Based Address Resolution
See RBAR.
RBAR
Range Based Address Resolution
A DSR enhanced routing application
which allows the user to route
Diameter end-to-end transactions
based on Application ID, Command
Code, “Routing Entity” Type, and
Routing Entity address ranges.
Relay Agent
Diameter agent that forwards
requests and responses to other
Diameter nodes based on
routing-related AVPs (such as
Destination-Realm) and routing
configuration. Because relays do
not make policy decisions, they do
not examine or alter non-routing
AVPs. As a result, relays never
originate messages, do not need to
understand the semantics of
messages or non-routing AVPs,
and are capable of handling any
Diameter application or message
type.
S
SBR
Session Binding Repository
A highly available, distributed
database for storing Diameter
session binding data.
SCTP
Stream Control Transmission
Protocol
An IETF transport layer protocol,
similar to TCP that sends a message
in one operation.
910-6528-001 Revision D, December 2012
458
Glossary
S
The transport layer for all standard
IETF-SIGTRAN protocols.
SCTP is a reliable transport protocol
that operates on top of a
connectionless packet network such
as IP and is functionally equivalent
to TCP. It establishes a connection
between two endpoints (called an
association; in TCP, these are
sockets) for transmission of user
messages.
Service Broker
Provides service aggregation and
orchestration in both wireless and
wireline networks using the
Customized Application of Mobile
network Enhanced Logic (CAMEL)
protocol.
Session Binding Repository
See SBR.
SNMP
Simple Network Management
Protocol.
An industry-wide standard protocol
used for network management. The
SNMP agent maintains data
variables that represent aspects of
the network. These variables are
called managed objects and are
stored in a management information
base (MIB). The SNMP protocol
arranges managed objects into
groups.
SOAM
System Operations,
Administration, and Maintenance
SOAP
Simple Object Access Protocol
SSR
SIP Signaling Router
910-6528-001 Revision D, December 2012
459
Glossary
S
Function responsible for querying
a redirection server and proxying
requests to other SSR servers,
redirect servers, SSR Service Points,
and Gateways. It helps in evolving
a Flat NGN network into a
hierarchical network.
SW
Software
Switch
910-6528-001 Revision D, December 2012
460
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement