Files for Troubleshooting Understanding and Responding to SNMP Traps

8-14 Oracle WebLogic Communications Server Administration Guide

8.5.2.1 connectionLostToPeer

This trap is generated by an engine tier server instance when it loses its connection to a replica in the SIP data tier. It may indicate a network connection problem between the engine and SIP data tiers, or may be generated with additional traps if a SIP data tier server fails.

8.5.2.1.1 Recovery Procedure If this trap occurs in isolation from other traps indicating

a server failure, it generally indicates a network failure. Verify or repair the network connection between the affected engine tier server and the SIP data tier server. If the trap is accompanied by additional traps indicating a SIP data tier server failure for example, dataTierServerStopped, follow the recovery procedures for the associated traps.

8.5.2.2 connectionReestablishedToPeer

This trap is generated by an engine tier server instance when it successfully reconnects to a SIP data tier server after a prior failure after a connectionLostToPeer trap was generated. Repeated instances of this trap may indicate an intermittent network failure between the engine and SIP data tiers.

8.5.2.2.1 Recovery Procedure See

Section 8.5.2.1, connectionLostToPeer .

8.5.2.3 dataTierServerStopped

Oracle WebLogic Communication Services SIP data tier nodes generate this alarm when an unrecoverable error occurs in a WebLogic Server instance that is part of the SIP data tier. Note that this trap may be generated by the server that is shutting down, by another replica in the same partition, or in some cases by both servers network outages can sometimes trigger both servers to generate the same trap.

8.5.2.3.1 Recovery Procedure See the Recovery Procedure for

Section 8.5.2.8, serverStopped .

8.5.2.4 overloadControlActivated, overloadControlDeactivated

Oracle WebLogic Communication Services engine tier nodes use a configurable throttling mechanism that helps you control the number of new SIP requests that are processed. After a configured overload condition is observed, Oracle WebLogic Communication Services destroys new SIP requests by responding with 503 Service Unavailable to the caller. The servers continues to destroy new requests until the overload condition is resolved according to a configured threshold control value. This alarm is generated when the throttling mechanism is activated. The throttling behavior should eventually return the server to a non-overloaded state, and further action may be unnecessary.

8.5.2.4.1 Recovery Procedure Follow this recovery procedure:

1. Check other servers to see if they are nearly overloaded. Section 8.5.2.5, replicaAddedToPartition Section 8.5.2.6, replicaRemovedEnginesRegistration Section 8.5.2.7, replicaRemovedFromPartition Table 8–3 Cont. Oracle WebLogic Communication Services SNMP Traps Server Node in which Trap is Generated Trap Name