Oracle Communications Subscriber Data Management (SDM)
 

PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec SDM
 

In this Document

Goal

Solution

References

Created from <SR 3-12407742121>

Applies to:

Goal

Diameter too busy and DIAMETER_ERROR_TRANSPARENT_DATA_OUT_OF_SYNC reported in SPR.

Solution

Analysis on Diameter too busy error :-

On analyzing the blue logs it is found that diameter too busy failures are reported due to high TPS than dimensioned license capacity of 200 TPS in SPR . Same was validated by PM Counter reports and following error logs reported in SPR.

OCDiameter[INFO]: Entering traffic limitation mode due to licensing. Current traffic rate is limited to 200 TPS.
OCDiameter[INFO]: Exiting traffic limitation mode. Current traffic rate is 200 TPS.
OCDiameter[INFO]: The peer has been authorized.
OCDiameter[INFO]: No route to this peer will be added automatically. It will be used only for replies, or requests that have a Destination-Host AVP.
OCDiameter[INFO]: Entering traffic limitation mode due to licensing. Current traffic rate is limited to 200 TPS.
OCDiameter[INFO]: Exiting traffic limitation mode. Current traffic rate is 200 TPS.
OCDiameter[INFO]: Entering traffic limitation mode due to licensing. Current traffic rate is limited to 200 TPS.
OCDiameter[INFO]: Exiting traffic limitation mode. Current traffic rate is 200 TPS.
OCDiameter[INFO]: Entering traffic limitation mode due to licensing. Current traffic rate is limited to 200 TPS.

+++++++++++++PM COUNTERS of 24 hours+++++++++++++

Total TPS : [250]
TPS UAR : [0]
TPS MAR : [0]
TPS SAR : [0]
TPS LIR : [0]
TPS RTR : [0]
TPS PPR : [0]
TPS UDR : [21]
TPS SNR : [114]
TPS PUR : [113]
TPS PNR : [0]

---------------------------------

Issue was resolved after customer bought additional license in SPR.

Analysis on DIAMETER_ERROR_TRANSPARENT_DATA_OUT_OF_SYNC :-

Diameter Transparent data out of sync is a known issue in older versions of MPE. It can be caused by several factors such as the same subscribers being updated by two different MPE's on the same SPR, CCRu's sent to the MPE at a fast rate for the same subscriber (within msec.) CCRi and CCRt's sent to the MPE for the same subscriber with in msec, all have had a part in causing this type of error.

There have been several fixes on the MPE and SPR to resolve this issue. It is recommended to upgrade SPR as well as
policy servers CMP/MRA/MPE to the latest available software release and patch level.

References

This solution has no attachment