Cause

This gives the reason for the system reset as follows:

• Craft Request — The reset was manually initiated using reset system.

• Initialized — A power-up. Always the first entry in the log unless more than 15 restarts have occurred since the last power up.

• Interchange — A State of Health change caused the arbiter process to initiate the restart.

• Interchange-Craft — An administrative session (session -i command, on-demand interchange) caused the arbiter process to initiate the restart.

• Internal Request — Software requested the restart, usually in response to a server interchange. Internal request restarts are not initiated in direct response to an error and are non-escalating.

• Software Request — Software requested the system restart.

Action

The level of recovery performed by the system.

1. Reset system 1 (Warm) — Communication Manager software is restarted, and active calls remain up.

2. Reset system 2 (Cold) — Communication Manager software is restarted, translations are preserved, and all calls are dropped.

3. Reset system 4 (Reload) — Communication Manager software is completely reloaded, and the hardware is reinitialized.

Escalated

y/n

y — The restart was escalated to a higher level than originally attempted. The system’s software escalation strategy can perform a higher level restart than the one initiated if problems prevent or conditions interfere with normal execution.

Mode

State of the server immediately after the interchange, at the time of the restart.

Look for a change of mode to help determine when an interchange occurred.

• Active — Mode of a simplex server and for a duplex server that is the active server.

• Standby — Mode of a standby server in a duplex configuration.

• Busyout — Mode of a standby server that has been placed out-of-service with a busyout command.

Time

The month, day, and time of the restart.