Oracle Communications EAGLE (Software)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
 

In this Document

Goal

Solution

References

Created from <SR 3-9207288081>

Applies to:

Goal

On : EAGLE 43.x version, Eagle 5 - STP (Production)

IDPR feature related counters are changed in measurement reports // INC000000074155

Solution

We had PR 209888 in R 44.0.X which is fixed in R 45.0.X

The details of the PR 209888 are as below,

Problem Description:- IDPRMSERR is getting pegged if no matching NPP Rule is found.

It is quiet normal not to see a matching NPP rule for CdPN/CgPN if the MSU is not supposed to be proceed further as per the NPP configuration. So pegging IDPRMSERR if no matching NPP Rule is found may cause Eagle to raise false SCCP Service Error Threshold Exceeded alarms.

Currently (R 44.0.X) the IDPRMSERR is pegged in lot of cases which include:

1. CONNECT/CONTINUE/RELEASE response couldn'’t be encoded properly or couldn’'t be routed properly.
2. No matching NPP Rule was found.
3. Encoding error occurred while encoding CDPN/CGPN in the relayed message.

Point 1 and point 3 seem valid conditions for pegging an error. However, it is quiet normal that matching NPP rule was not found. So point 2 should not increment the IDPRMSERR counter. Instead only IDPRMSRCV should be pegged in such scenario. Also it should increment the reroute/warning counter under corresponding SCCP service.

This is resulting in the difference in the IDPR counters after the upgrading to Software Release 45.0.1-64.70.35
 

In R 44.0.X:-

Pegs IDPRMSERR for “No matching NPP Rule found for incoming IDPR MSU” scenario.

System raises alarm if the error pegs due to “No matching NPP Rule found for incoming IDPR MSU” scenario is crossing the service error alarm threshold.

IDPRMSRCV= IDPRMSERR+IDPRMSFAIL+IDPRMSSUCC

SUCCESS RATIO = IDPRMSSUCC/(IDPRMSERR+IDPRMSFAIL+IDPRMSSUCC)
OR
SUCCESS RATIO = IDPRMSSUCC/IDPRMSRCV

In R 45.0.X

Pegs IDPRMSFAIL for “No matching NPP Rule found for incoming IDPR MSU” scenario

System will not raise alarm if the warning pegs due to “No matching NPP Rule found for incoming IDPR MSU” scenario is crossing the service error alarm threshold.

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

SUCCESS RATIO = IDPRMSSUCC/(IDPRMSERR+IDPRMSFAIL+IDPRMSSUCC)

Fall-Through Cases: All MSUs that have failed IDPR pre-processing and fall through to GTT.
Currently there is no MEAS register for Fall-through case. However Fall-through case can be calculated as: Fall-through case = IDPRMSRCV – (IDPRMSERR+IDPRMSFAIL+IDPRMSSUCC)

References

This solution has no attachment