| Asset ID: |
1-71-2210765.1 |
| Update Date: | 2016-12-06 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2210765.1
:
Diameter Signaling Router (DSR) - Why TmConnEnabledNotAvail Counter Shows Wrong Values
| 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-13545121791>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 3.0 and later
Information in this document applies to any platform.
Goal
Why is TmConnEnabledNotAvail counter (Measuremments->Reports->Diameter Exceptions report) returning incorrect values for some given connections included in a Target Set Address (TSA)?
Solution
Due to a Bug, on DA-MPs (Message Processor Servers) that are already in a TSA, but end up not hosting an IPFE connection, incorrect data for the TmConnEnabledNotAvail counter (Enabled but Unavailable) will be reported. This will affect rolled up numbers for the connection (for example, if viewed at the SOAM level). This only affects IPFE connections.
In order to get the correct TmConnEnabledNotAvail counter values, use one of the following workarounds:
- Find the DA-MP that hosts the connection (if any) and use the value from that DA-MP,
OR
- Determine the number of DA-MPs in the TSA for the IPFE connection (N), and subtract (300 * (N-1)) from the result, to remove the incorrect peg values.
References
<BUG:19115574> - [238524]INCORRECT MEASUREMENT VALUE "TMCONNENABLEDNOTAVAIL" IN DSR 60.7.0
Attachments
This solution has no attachment
