EvApplIdListInconsistency

Measurement Group: Diameter Exception

Measurement Type: Simple

Measurement Dimension: Arrayed (by Connection ID)

Description: Number of times that the supported Application IDs received from the peer were inconsistent with another transport connection.

Collection Interval: 5 min

Peg Condition: If the Application ID list received from the DSR for a peer's transport connection is not identical to the Application ID list for at least one of the transport connections for a peer that has an Operation Status state of Available.

Measurement Scope: Server Group

Recovery:

If one or more MPs in a server site have failed, the traffic will be distributed between the remaining MPs in the server site. MP server status can be monitored from the Status & Manage > Server page.
The mis-configuration of Diameter peers may result in too much traffic being distributed to the MP. The ingress traffic rate of each MP can be monitored from 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 from 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 no additional congestion alarms are asserted, the DSR may be experiencing a problem preventing it from processing events from its All-Connections Event Queue. The alarm log should be examined using the Alarms & Events page.
If the problem persists, contact My Oracle Support (MOS).