| Asset ID: |
1-72-2404292.1 |
| Update Date: | 2018-05-29 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2404292.1
:
Diameter Signaling Router (DSR): Showing Wrong/Duplicate IPs For Connections Under SCTP Statistics
| Related Items |
- Oracle Communications Diameter Signaling Router (DSR)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
|
In this Document
Created from <SR 3-17457962561>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.2.0 and later
Tekelec
Symptoms
Connections showing Invalid IP address under Main Menu: Diameter -> Maintenance -> Connections -> SCTP statistics
Changes
Cause
When the connection goes down (go to Operstatus_Unavailable), the DCL module should remove the association record from PeerStatus.0 table; subsequently, the corresponding record is removed from PeerStatus.1 too.
But due to the Bug# 26615731, records in PeerStatus.x tables are not removed. It is found that the PeerStatus.0 table still contains the SCTP association data even if the association is released from Linux (i.e. connection already down).
Typically for the IFPE responder type connection, when there are more than 1 MPs in the TSA, after bouncing the connection several times, we can find each MP's PeerStatus.0 table still contains the SCTP association information. This will cause the PeerStatus.x table to populate "dirty" data thereby causing the SCTP statistic to show many IP entries.
Stale entries could be for same IPs (when same connection deleted and added again) or different IPs (when a connection deleted and new connection added).
Solution
Issue is fixed in DSR 8.2 release.
Attachments
This solution has no attachment
