EvEmrCongestionOnset

Measurement Group: Connection Congestion

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: Number of times an EMR Congestion Level was advanced

Collection Interval: 5 min

Peg Condition Each time the EMR Congestion Level is advanced

Measurement Scope:

Recovery: Site

  1. Verify the "Maximum EMR" for the connection is set sufficiently high.
  2. Verify the EMR onset/abatement thresholds are properly adjusted. Setting an abatement threshold too close to its onset threshold may trigger oscillation between higher and lower congestion levels.
  3. Verify the "Smoothing Factor" parameter for the connection is properly adjusted. Increasing the "Smoothing Factor" value places more weight towards the current EMR over the smoothed EMR. Decreasing the "Smoothing Factor" value places more weight towards the smoothed EMR over the current EMR.
  4. Verify the "EMR Abatement Timeout" for the connection is set sufficiently high. Short abatement time periods may result in triggering EMR throttling too rapidly.
  5. Check to see if other connections to the adjacent Diameter Node are out of service. Adjacent Diameter nodes being out of service can cause more traffic to be sent on this connection than what the adjacent Diameter Node can support on a per-connection basis.
  6. Check to see if the connection is over-subscribed from a routing perspective. Any recent changes to DSR routing configurable may have inadvertently diverted more message traffic to this connection.
  7. If the problem persists, contact My Oracle Support (MOS).

Parent topic: Connection Congestion measurements