Oracle Communications Diameter Signaling Router (DSR)
 

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

In this Document

Goal

Solution

Created from <SR 3-16480172691>

Applies to:

Goal

What is the reasons for the below alarms and how to solve it:

Are these telling us that all diameter messages are failing?

At 2017-12-22 16:00:00 UTC LabSOAM PDRA exceed thrshld 0.9% for TxAns5xxx in TSA7_sy at 98.8%. RawFail=254, Attmpt: 257

At 2017-12-22 16:05:00 UTC LabSOAM PDRA exceed thrshld 0.9% for TxAns5xxx in TSA7_sy at 100.%. RawFail=277, Attmpt: 277

At 2017-12-22 16:10:00 UTC LabSOAM PDRA exceed thrshld 0.9% for TxAns5xxx in TSA7_sy at 99.2%. RawFail=259, Attmpt: 261

Solution

Reference to the Page 338 of Oracle DSR Measurements Reference: https://docs.oracle.com/cd/E80134_01/docs.74/E73291_rev_01.pdf

TxAnswer5xxx in the Diameter Ingress Transaction Performance measurements refers to the Answer message received from a peer that was successfully sent to the Diameter Connection Layer (DCL) with a Result-Code value in the range of 5000 - 5999. The connection measurement is associated with the connection to which the message was routed.

This is not necessarily and issue at the DSR. Usually DSR is just pegging the answer codes into different categories here. The exact answer code can provide more details about what is content of the answer message.

The exact Answer Code can be identified from a PCAP trace. For example,  PCAP can show 5030 (DIAMETER_USER_UNKNOWN) messages:

This error is used by the OCS to indicate to the PCRF that the end user specified in the request is unknown to the OCS and that the Sy session cannot be created.

This solution has no attachment