TmConnInCL2

Measurement Group: Connection Congestion

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: Total amount of time (in seconds) the connection experienced CL2.

Collection Interval: 5 min

Peg Condition: A "time duration interval" is determined as follows:

The "time duration interval" starts when one of the following occurs:
  • New "collection interval" for the measurement begins and the connection congestion level is CL2.
  • Connection congestion level changes to CL2.
The "time duration interval" stops when one of the following occurs:
  • The collection interval for the measurement ends.
  • The connection congestion level changes from CL2 to another congestion level.

Measurement Scope: Server Group

Recovery:

  1. If EMR Throttling is enabled for the connection, either the maximum EMR may be set too high or the onset/abatement thresholds need adjustment.
  2. The "Remote Bust Abatement Timeout" may be too small.
  3. This problem can be caused if other connections to the adjacent Diameter Node are out of service, thus causing more traffic to be sent on this connection than what the adjacent Diameter Node can support on a per-connection basis.
  4. The connection may be over-subscribed from a routing perspective. Any recent changes to DSR routing configurable may have inadvertently diverted more message traffic to this connection.
  5. Contact My Oracle Support (MOS) for further assistance.
Parent topic: Connection Congestion measurements