EvPerConnQueueCongestionChange

Measurement Group: Connection Performance

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: The number of times that the congestion level changed for a Per Connection Egress Queue.

Collection Interval: 5 min

Peg Condition: Each time the congestion level for a Per Connection Egress Queue was changed.

Measurement Scope: Server Group

Recovery:

An IP network, or Diameter peer, problem may exist thus preventing SCTP/TCP from transmitting messages into the network at the same pace that messages are being received from the network.
The transport task associated with the connection may be experiencing a problem, preventing it from processing events from its Connection Event Message Queue. The alarm log should be examined using the Alarms & Events page.
If one or more MPs in a server site have failed, the traffic will be distributed among the remaining MPs in the server site. MP server status can be monitored using the Status & Manage > Server page.
The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP. The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. Each MP in the server site should be receiving approximately the same ingress transaction per second.
There may be an insufficient number of MPs configured to handle the network traffic load. The ingress traffic rate of each MP can be monitored using the Status & Manage > KPIs page. If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
If the problem persists, contact My Oracle Support (MOS).