Go to primary content
Oracle® Communications Diameter Signaling Router Measurements
Release 8.3
E93201
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

EvEtlRateCongestionOnset

Measurement ID
14054
Measurement Group
Egress Throttle List Performance
Measurement Type
Simple
Measurement Dimension
Arrayed (by ETL ID)
Description
Number of times an ETL-RCL was advanced.
Collection Interval
5 min
Peg Condition
Each time the EMR Congestion Level is advanced
Measurement Scope
Network

Recovery

  1. Verify that the "Maximum EMR" for the ETL is set sufficiently high.
  2. Adjust the EMR onset/abatement thresholds if necessary. Setting an abatement threshold too close to its onset threshold may trigger oscillation between higher and lower congestion levels.
  3. Adjust the "Rate Convergence Time" parameter for the ETL if necessary. Increasing the "Rate Convergence Time" value allows the user to control the sensitivity of the request traffic bursts to ETG rate.
  4. Verify the "EMR Abatement Timeout" for the ETL is set sufficiently high. Short abatement time periods may result in triggering EMR throttling too rapidly.
  5. Determine if other connections (not part of this ETL) to the adjacent Diameter Node are out of service thus causing more traffic to be sent on connections/peers of this ETL than what the adjacent Diameter Node can support on a per-connection basis.
  6. Determine if the ETL is over-subscribed from a routing perspective. Any recent changes to DSR routing configurable may have inadvertently diverted more message traffic to connections/peers in this ETL.
  7. If the problem persists, it is recommended to contact My Oracle Support (MOS).