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
- Verify that the "Maximum EMR" for the ETL is set sufficiently high.
- 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.
- 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.
- Verify the "EMR Abatement Timeout" for the ETL is set sufficiently high. Short abatement time periods may result in triggering EMR throttling too rapidly.
- 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.
- 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.
- If the problem persists, it is recommended to contact My Oracle Support (MOS).