TmRemoteBusy

Measurement ID

10042

Measurement Group

Diameter Performance

Measurement Type

Simple

Measurement Dimension

Arrayed

Description

Total time (in milliseconds) that a connection’s Remote Busy State was Busy.

Collection Interval

5 min

Peg Condition

Each time that DRL changes the connection’s Remote Busy State to Busy. Each time interval stops when DRL changes the connection’s Remote Busy State to Not Busy

Measurement Scope

Server Group

Recovery

1. The ingress message rate to the connection is excessive.
   Under normal circumstances, TmRemoteBusy should be very small. If it is large, then the ingress message traffic to the connection may be exceeding the ability of the peer to process the traffic from this connection. The following measurements may be useful in evaluating the ingress traffic for this connection:

   • TxAll - measures the total routable and non-routable measurements which were sent on the connection.
   • TxRequestSuccessAllConn - measures the total number of Request messages forwarded to the connection.
   1. An excessive number of messages may have been rerouted to this connection. Examine TxRerouteAttempts, TxRerouteConnFailure, TxRerouteAnswerTimeout, TxRerouteSuccessSent, and RxRerouteAnswerRsp.
   2. Route Group configurable options can be viewed and modified using Main Menu > Diameter > Configuration > Route Groups.

      The connection may be a member of one or more Route Groups whose peer or connection weight may be mis-configured or need modification.

   3. Use Main Menu > Diameter > Configuration > Route Groups to examine Connection status.

      The connection may be a member of one or more Route Groups containing failed connections. When this occurs, the traffic will be routed to the remaining connections in those route groups.

   4. The peer node or this particular connection to the peer node may be under-engineered for the ingress traffic load.
   5. The total offered load to this connection may have peaked during a short time duration due to larger than normal network usage patterns. This measurement should be view over multiple measurement intervals to look for trends.
2. Use Main Menu > Diameter > Configuration > Connections to examine and modify the Remote Busy Abatement Timeout attribute setting for the connection.
   If the total duration that the connection is congested is small (as defined by TmRemoteBusy), then the user-configurable Remote Busy Abatement Timeout attribute for the connection may be set too small.
3. It is recommended to contact My Oracle Support for assistance if needed.