EAGLE: Rept-stat-sccp Reporting High Fail Ratio For IDPR Service.

Asset ID:	1-72-2392105.1
Update Date:	2018-04-27
Keywords:

Solution Type Problem Resolution Sure

Solution 2392105.1 : EAGLE: Rept-stat-sccp Reporting High Fail Ratio For IDPR Service.

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.0 and later
Tekelec

Symptoms

Rept-stat-sccp reporting high fail ratio for IDPR service.

Changes

Cause

From the IDPR-SYSTOT report we see huge count for IDPRMSFAIL counter.

TYPE OF REPORT: STP SYSTEM TOTAL MEASUREMENTS ON IDPR
REPORT PERIOD: LAST
REPORT INTERVAL: 18-03-19, 11:00:00 THROUGH 11:29:59

IDPR-SYSTOT MEASUREMENTS

These measurements are from 18-03-19, 11:00:00 through 11:29:59.
Measurement data represents an incomplete interval.
IDPRMSRCV = 5250950, IDPRMSSUCC = 214808, IDPRMSFAIL = 779888,
IDPRMSERR = 152, IDPAPTYRTD = 0, IDPAPTYSKR = 0,
IDPAPTYGTT = 0, IDPSKRTD = 0, IDPSKGTT = 0,
IDPBKLCONN = 0, IDPBKLCONT = 0, IDPINPCONN = 0,
IDPINPCONN2= 0, IDPINPCONN3= 0, IDPINPCONN4= 0,
IDPINPCONT = 0, IDPINPCONT2= 0, IDPINPCONT3= 0,
IDPINPCONT4= 0, IDPINPRLC = 0, IDPINPRLC2 = 0,
IDPINPRLC3 = 0, IDPINPRLC4 = 0, IDPINPRTG = 0,
IDPINPRTG2 = 0, IDPINPRTG3 = 0, IDPINPRTG4 = 0,
IDPSKGTART = 0, IDPSKGTART2= 0, IDPSKGTART3= 0,
IDPSKGTART4= 0, IDPRCDPN = 994848, IDPRCDPN2 = 0,
IDPRCDPN3 = 0, IDPRCDPN4 = 0

IDPRMSRCV = IDPRMSSUCC+IDPRMSFAIL+IDPRMSERR+Fall-Through Case

In Rept-stat-sccp output, for service IDPR,

Success = IDPRMSSUCC
Errors = IDPRMSFAIL+IDPRMSERR

Fail ratio = Errors/(Errors + Success)

From the ent-trace we captured for IDPR service, following are the details,

1) 117 Messages triggered IDPR service.

Info: SCCP: idpr service selected

2) Only 28 messages of 117 messages completed IDPR preprocessing successfully and was processed by IDPRCDPN NPP service.

Info: IDPR Preprocessing successful
Info: IDP msg processing by IDPRCDPN NPP service

3) Out of 28 messages only for 8 messages the RTDB lookup was successful. This will peg IDPRMSSUCC. Please note it may peg IDPRMSERR if encoding fails post successful RTDB lookup.

Info: idpr_rtdb_lookup_and_match=Yes

4) For 20 messages out of 28 messages the RTDB lookup was unsuccessful. This will peg IDPRMSFAIL

Info: idpr_rtdb_lookup_and_match=No

5) 36 out of 117 messages, SCCP CdPA GT was not found in the GTA CSL table. This will peg Fall-through case.

Info: SCCP CdPA GT not found in GTA CSL Table.

6) 51 out of 117 messages TCAP decoding failed due to Missing component portion. This will peg Fall-through Case.

Info: Missing component portion. 5=e_dcd_qry_err

Info: Error detected during TCAP decoding.

Calculation using the above formulas:-

Based on the traces we have,

Success = 8
Errors= 20

Fail ratio = 20/28 = 71.42 %

Please note out of 8 messages which had successful RTDB lookup may peg IDPRMSERR if encoding fails.

Based on the observation it expected that fail ratio of IDPR service will be high.

Solution

High IDPR fail ratio reported in rept-stat-sccp depends on the traffic triggering the IDPR service, configuration and the provisioning data in the RTDB. Customer has to audit the traffic triggering the IDPR feature verify the configuration and provisioning data in the RTDB. Audit can be done with help of Oracle consulting services.

Attachments

This solution has no attachment