1. Alarms and KPIs
  2. Alarms and Events
  3. Diameter Alarms and Events (8000-8299, 22000-22350, 22900-22999, 25600-25899)
  4. 22222 - Long Timeout PTR Buffer Pool Utilization

3.9.97 22222 - Long Timeout PTR Buffer Pool Utilization

Alarm Group:
DIAM
Description:
The MP's Long Timeout PTR buffer pool is approaching its maximum capacity.
Severity:
Minor, Major, Critical
Instance:
N/A
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDiameterLongTimeoutPtrBufferPoolUtilNotify

Recovery:

  1. If one or more MPs in a server site have failed, the traffic will be distributed amongst the remaining MPs in the server site. Monitor the MP server status from Status & Manage, and then Server Status.
  2. The misconfiguration of Pending Answer Timer assignment may result in excessive traffic being assigned to the Long Timeout PTR buffer Pool. View the Pending Answer Timer values via Diameter, and then Configuration, and then Pending Answer Timers. Examine the Pending Answer Timers assignment via the Diameter, and then Configuration, and then Application Ids and Diameter, and then Configuration, and then Peer Nodes.
  3. The misconfiguration of Diameter peers may result in too much traffic being distributed to the MP. Monitor the ingress traffic rate of each MP from Status & Manage, and then KPIs. Each MP in the server site should be receiving approximately the same ingress transaction per second
  4. There may be an insufficient number of MPs configured to handle the network traffic load. Monitor the ingress traffic rate of each MP from Status & Manage, and then KPIs. If all MPs are in a congestion state then the offered load to the server site is exceeding its capacity.
  5. A software defect may exist resulting in Long Timeout PTR buffers not being de-allocated to the pool. This alarm should not normally occur when no other congestion alarms are asserted. Examine the alarm log from Alarms & Events.
  6. If the problem persists, it is recommended to contact My Oracle Support.