Go to primary content
User Data Repository Alarms, KPIs, and Measurements
Release 12.4
E82598-01
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

8002 - 207 - MpEvRxException_ReqDuplicate

Event Type
DIAM
Description
Connection ingress message processing exception.
Severity
Info
Instance
<Connection Name>:207
HA Score
Normal
Throttle Seconds
10
OID
eagleXgDiameterMpEvRxException

Recovery:

  1. It is possible to observe this event occasionally, due to the unreliable nature of the UDP transport protocol. However, if the occurrence of this event is frequent, investigate the issue further.

    This event is expected when a retransmission is received from the client before a server has responded to the request, possibly a result of the client retransmitting too quickly before allowing sufficient time for a server to respond in time. Another possible cause is if one or more servers configured to handle the request are non-responsive.

  2. Investigate the routing configuration to narrow down the list of servers (Peer Nodes) which are expected to handle requests from the reported server connection.
  3. Evaluate whether an Egress Transaction Failure Rate alarm has been raised for any of the corresponding client connections. If so, investigate the cause of the server becoming non-responsive and address the condition.

    Note:

    Depending on the operator's choice, the client connection may need to be Admin Disabled until the evaluation is complete, which will allow requests to be routed to other servers, depending on the routing configuration. If this is not the case, tune the client's retransmit timers to be greater than the typical turnaround time for the request to be processed by the server and for the response to be sent back to the client.
  4. If the problem persists, it is recommended to contact unresolvable-reference.htm#GUID-DD0927BD-FD0B-4CEB-86E9-98A33C12D4E0.