Diameter Signaling Router (DSR) - "Message Priority" Measurement Report is Not Generated

Asset ID:	1-72-2259857.1
Update Date:	2017-11-02
Keywords:

Solution Type Problem Resolution Sure

Solution 2259857.1 : Diameter Signaling Router (DSR) - "Message Priority" Measurement Report is Not Generated

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.3.0 to DSR 7.4.0 [Release DSR 7.0]
Information in this document applies to any platform.

Symptoms

"Message Priority" Measurement reports are not generated. The related task fails with "Exception" status (under "Main Menu -> Status & Manage -> Tasks -> Active Tasks" System Operation, Administration & Maintenance (SOAM) GUI menu). Moreover, the "Active Tasks" screen may show "Data export failed: No measurements selected" in the "Result Details" column. And perhaps a statement indicating any Task that includes Message Priority among the selected Reports may fail in this manner.

Cause

This issue is due to Bug 25451488. The content of "MeasRptGroup" & "MeasDef" tables shows discrepancies. In fact, "measid=10127" entry is included in "MeasRptGroup" table, but is undefined in "MeasDef" one:

"MeasRptGroup" table

[admusr@dsrno-a ~]$ iqt -E MeasRptGroup | egrep '(Message Priority)'
repgrp=Message Priority measid=10028 subgrp=
repgrp=Message Priority measid=10029 subgrp=
repgrp=Message Priority measid=10033 subgrp=
repgrp=Message Priority measid=10127 subgrp=

"MeasDef" table

[admusr@dsrno-a ~]$ iqt -E MeasDef | egrep '(10028|10029|10033|10127)'
id=10028 tag=RxMsgPri0PeerRule clerk=StatClerk scope=B dim=Single type=Simple itvl=5min flags=SE scale=0 stoTopCnt=0 stoThresh=0 subMeasNameTab= birthTime=01/01/1970 01:00:00 descr=Number of Request messages set to priority "0" as a result of PRT processing
id=10029 tag=RxMsgPri1PeerRule clerk=StatClerk scope=B dim=Single type=Simple itvl=5min flags=SE scale=0 stoTopCnt=0 stoThresh=0 subMeasNameTab= birthTime=01/01/1970 01:00:00 descr=Number of Request messages set to priority "1" as a result of PRT processing
id=10033 tag=RxMsgPri2PeerRule clerk=StatClerk scope=B dim=Single type=Simple itvl=5min flags=SE scale=0 stoTopCnt=0 stoThresh=0 subMeasNameTab= birthTime=01/01/1970 01:00:00 descr=Number of Request messages set to priority "2" as a result of PRT processing

Solution

Bug 25451488 is resolved in DSR 8.0 release. However a workaround can be applied on DSR 7.3 & DSR 7.4 releases to avoid this issue. It consists on deleting the extra entry from "MeasRptGroup" table. Since "MeasRptGroup" table is not replicated, the below command needs to be ran on all Active and Standby Network, Operation, Administration & Maintenance (NOAM) and SOAM servers. As admusr:

$ irem MeasRptGroup where "repgrp = 'Message Priority' and measid = 10127"

References

<BUG:25451488> - [MSGPRI:MEALS] INEXISTENT MESSAGE PRIORITY MEASUREMENT CAUSES EXPORT FAILURES

Attachments

This solution has no attachment