8202 - RclItrPoolCongested
- Alarm Group
- DIAM
- Description
- RCL ITR pool utilization threshold crossed.
- Severity
- Minor, Major, Critical
- Instance
- RclItrPool, DIAM
- HA Score
- Normal
- Auto Clear Seconds
- 0 (zero)
- OID
- eagleXgDiameterRclItrPoolCongested
Recovery:
-
Adjust the RADIUS
Cached Response Duration option
of the associated Connection configuration sets to reduce the lifetime of
cached transactions, if needed.
-
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
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
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
page.
If all MPs are in a congestion state then the offered load to the server site
is exceeding its capacity.
-
A software defect may exist resulting in PTR buffers
not being deallocated to the pool. This alarm should not normally occur when no
other congestion alarms are asserted. The alarm log should be examined from the
Alarms & Events page.
-
If the problem persists, it is recommended to
contact
unresolvable-reference.htm#GUID-DD0927BD-FD0B-4CEB-86E9-98A33C12D4E0.