3.26.3 RxDOCDiscardMp
- Measurement ID
- 10252
- Measurement Group
- Diameter Ingress Transaction Exception
- Measurement Type
- Simple
- Measurement Dimension
- Single
- Description
- The number of ingress messages that were discarded due to local DA-MP danger of CPU congestion.
- Collection Interval
- 5 min
- Peg Condition
- Pegged for each message discarded due to DA-MP danger of CPU congestion.
- 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. DA-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 DA-MP can be monitored from the page. Each DA-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 DA-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.
- The Diameter Process may be experiencing problems. The alarm log should be examined using the Alarms & Events page.
- If the problem persists, it is recommended to contact unresolvable-reference.html#GUID-F069C6FD-5BA3-4F31-AE9E-A187D5B5F729.