Review the formats and descriptions of SafeLinx Server traps.
The tables in this section describe each trap.
- The origin of the trap is denoted by the first two letters of the first variable. Traps sent by the SafeLinx Server use AG.
- The 120390 and 120391 traps are for completeness and not necessarily used in the current implementations of trap-generating components.
|Code / Severity||Variables||Description|
||SafeLinx Server software is starting.|
|120266 MAJOR||SafeLinx Server software is terminating.|
|120267 CLEARED||Transition CLOSED->OPEN The mobile device can now establish a connection.|
|120268 INDETERMINATE||Transition OPEN/(SHORT)HOLD->CONNECTED The mobile device is now logged on.|
|120269 INDETERMINATE||Transition CONNECTED/(SHORT)HOLD->OPEN The mobile device is now logged off.|
|120270 MINOR||Transition OPEN / CONNECTED / (SHORT)HOLD-> CLOSED|
|120271 WARNING||Transition CONNECTED->HOLD|
||Transition CONNECTED-> SHORT_HOLD.|
|120273 INDETERMINATE||A connection was removed from the SafeLinx Server.|
||A new connection was added to the SafeLinx Server.|
|120275 MINOR||An authentication error was made during the logon procedure.|
||An error occurred in the PPP protocol.|
|120277 MINOR||A client login session refused a data management option set by the SafeLinx Server.|
||An MNC cannot make a connection to the network carrier or message center.|
|120289 INDETERMINATE||The mobile session roamed to a new device.|
|120320 MAJOR||The messaging services failed to connect to backend application server.|
|120321 WARNING||The messaging client device failed authentication with the messaging services.|
|120322 CRITICAL||When messaging services detects that the Connection Manager is deadlocked, it saves queued messages to the database. Then, messaging services generates a core file for debugging, restarts the SafeLinx Server, and resumes sending the queued messages.|
|120390 MINOR||Other errors|
|120391 WARNING||Other warnings|