TxDmiwfMtoDRoutingFail

Measurement Group: DM-IWF Exception

Measurement Dimension: Single

Measurement Type: Simple

Description: Number of MAP-to-Diameter transactions which could not be routed to the Diameter network due to a failure.

Collection Interval: 5 min

Peg Condition:
  • Whenever DM-IWF is unable to successfully forward a Request message received from a SS7-MP due to a failure.
  • Whenever the Request message is not routed to a Diameter Peer Node due to a routing error (either DRL or another DSR Application initiates an Answer response).
  • Whenever DM-IWF receives an Answer response from DRL and the Application-Data stack event parameter "Message Source ID" is set to "DRL" or "APP".

Recovery:

  1. Examine the Admin State of the DM-IWF DSR application. Verify that the DM-IWF DSR application is Enabled via the Diameter > Maintenance > Applications screen.
  2. If the DM-IWF DSR application is enabled, this measurement is pegged when either DM-IWF internal resources are exhausted or DSR's internal request processing queue is highly congested. Examine the following additional information to determine which resources are exhausted and/or whether the DSR internal queue is congested:

    • Alarms and Events from the Alarms & Events screen (Alarm 33005 - DM-IWF PTR Pool Utilization. Refer to the DSR Alarms and KPIs Reference for details about this alarm)
    • Measurement EvDmiwfPtrPoolExceeded
    • Measurement EvDmIwfTxFwdFail

  3. Evaluate the cause of resource exhaustion or internal queue congestion and take corrective action. Examine the following additional information to assist with determination of the cause of resource exhaustion:

    • Alarms and Events from the Alarms & Events screen
    • The rate of messages being processed by DM-IWF from the Status & Manage > KPIs page

  4. If the problem persists, contact My Oracle Support (MOS).
Parent topic: DM-IWF Exception measurements