# PROGRAMMED REBOOT

CAUTION: System reboots take a significant amount of time during which the system will be non-operational. To prevent service outage, Mitel recommends that a Universal ASU with emergency phones be provided (the System Fail Transfer feature allows emergency calls from these phones).

## Qualifiers:

COURTESY ON

COURTESY OFF

DISPLAY

RESOURCE RECOVERY ON

RESOURCE RECOVERY OFF

RESOURCE RECOVERY <hh:mm:ss>

SCHEDULE ON

SCHEDULE OFF

SCHEDULE DAILY <hh:mm:ss>

SCHEDULE <day-of-week> <hh:mm:ss>

SCHEDULE MONTHLY <week # [1-4]> <day-of-week> <hh:mm:ss>

SCHEDULE INTERVAL <interval in weeks [1-52]> <MMM> <day-of-month> <hh:mm:ss>

NOTE: The default values are:
PROGRAMMED REBOOT SCHEDULE IS OFF
PROGRAMMED REBOOT SCHEDULED: DAILY 02:15:00
PROGRAMMED REBOOT RESOURCE RECOVERY IS ON
PROGRAMMED REBOOT RESOURCE: RECOVERY 02:15:00
PROGRAMMED REBOOT COURTESY IS OFF

## Purpose:

Enables or disables a programmed system reboot, schedules a system reboot, or displays the programmed reboot settings and status.

COURTESY ON/OFF enables or disables the call courtesy option for resource recovery and scheduled reboots.

CAUTION

- The Programmed Reboot Resource Recovery function (default: 02:15 A.M. daily) will reboot the system at the specified time ONLY if the available memory threshold is reached, or a non-critical resource failure occurs. Use the Resource Recovery option to reduce the occurrence of programmed reboots.

- Do not enable courtesy if you routinely leave lines or links open for long periods of time. With courtesy enabled, scheduled reboots will only occur when there are no active calls. Open lines from off-hook phones, long duration calls including "nailed up" calls, or active ISDN signalling links (ISDN Network Inactivity Timer set to more than 10 minutes) can significantly reduce the likelihood of a successful programmed reboot.

## Details:

The Programmed Reboot command automates the management of routine maintenance and resolves minor memory faults (for example, memory fragmentation) which often have no apparent immediate effect. However, the effects of minor faults can accumulate and create symptoms that may eventually affect call processing if dynamic memory is no longer available. The system automatically detects a fault if the threshold of available memory is reached and a Maintenance Log entry and alarm (Memory Avail) are generated. The alarm is also presented on any installed consoles.

Programmed Reboot Courtesy ON/OFF - Turns the "courtesy down" option on or off. When courtesy is enabled, the system waits for all calls to clear before rebooting. If there are still calls in progress after an hour, the system either reschedules the reboot for the next scheduled interval (scheduled reboot) or proceeds (resource recovery reboot). In the event the system initiates a resource recovery reboot in response to a critical resource shortage, the courtesy option is ignored and the reboot proceeds even if calls are in progress. If the system cannot reboot as scheduled, it generates a maintenance log to this effect. If both a scheduled reboot and resource recovery reboot are enabled and pending, the recovery reboot takes precedence and the reboot will proceed.

Programmed Reboot Display - Displays the programmed reboot settings and status, including the day and time that the action will occur.

Programmed Reboot Resource Recovery ON/OFF - Turns the programmed reboot on and off. If enabled, a software-controlled reboot will occur at the next occurrence of the specified time ONLY if the available memory threshold has been reached or if a non-critical resource failure occurs. Alarms are raised (Memory Consumption, Stale Tasks or Memory Avail) and Maintenance Logs generated. See Resource Monitoring for threshold details. Critical system resources may deteriorate to the point where the system performs a software-controlled reboot on its own, before the scheduled reboot time. If this occurs, the reason for the reboot is saved in the "panic" area of the Maintenance Log for the Memory Avail alarm. System Memory Consumption and Stale System Tasks generate alarms and maintenance logs at the time of the resource failure.

Programmed Reboot Resource Recovery <hh:mm:ss> - Sets the time for a resource recovery reboot.

Programmed Reboot Schedule ON/OFF - Turns the programmed reboot on and off.

Programmed Reboot Schedule - A software-controlled reboot occurs at the next occurrence of the specified day and time on a daily, weekly, monthly or yearly basis. This setting is useful for customers who prefer to schedule this activity as part of routine maintenance.

NOTES

- Enter the month in 3-letter format (Jan, Feb, etc.).

- When setting a scheduled reboot or a resource recovery, make sure that there is at least 10 minutes between the programmed time and the current system time.

- MONTHLY SCHEDULED reboots are limited to four per month. Thus, if the day-of-week specified occurs five times in a month, there is no reboot on the fifth occurrence.

### Reboot Behavior

With courtesy reboots enabled, the system may wait up to one hour from the scheduled time for the reboot before rebooting. During this time, the system periodically checks for active calls. This section describes system behavior if programmed reboot settings are modified during this "auditing" period.

Condition | User Action | System Behavior
Scheduled reboot sequence has started | Scheduled reboot is turned OFF | If no resource recovery reboot is in progress, the scheduled programmed reboot will abort. A maintenance log will be generated indicating the scheduled programmed reboot sequence aborted. The system will reschedule the programmed reboot for the next programmed interval. NOTE: Turning the scheduled programmed reboot back ON will start a reboot sequence at the next programmed interval otherwise the schedule reboot remains OFF. If a resource recovery reboot is in progress, the reboot sequence will continue.
Resource recovery programmed reboot sequence has already started | Resource recovery reboot is turned OFF | If no scheduled reboot is in progress, the resource recovery programmed reboot will abort. A maintenance log will be generated indicating the scheduled programmed reboot sequence aborted. The system will reschedule the programmed reboot for 24 hours later. NOTE: Turning the resource recovery programmed reboot back ON will start a reboot sequence 24 hours later otherwise the resource recovery reboot remains OFF. If a scheduled reboot is in progress, the reboot sequence will continue.
Resource recovery is ON and pending Schedule is OFF but the date and time lines up with the upcoming programmed reboot The programmed reboot sequence has started | Schedule is turned ON Resource Recovery is turned OFF (in that order) | If calls are up for the duration of the reboot sequence, the scheduled programmed reboot will abort at the end of the reboot sequence. A maintenance log will be generated indicating the scheduled programmed reboot sequence aborted. The system will reschedule the programmed reboot for the next programmed interval.
Resource recovery is OFF Schedule is ON and the date and time lines up with the upcoming programmed reboot The programmed reboot sequence has started | Resource Recovery is turned ON Schedule is turned OFF (in that order) | If calls are up for the duration of the reboot sequence, the resource recovery programmed reboot will proceed at the end of the reboot sequence.
The resource recovery or scheduled reboot sequence has already started | Courtesy is turned OFF | Courtesy call checking will abort and the programmed reboot will proceed immediately.
Resource recovery or schedule programmed reboot sequence has already started | Programmed reboot date/time OR the system date/time is changed | The reboot sequence will proceed as if the date/time wasn't changed.

## Example:

To set Programmed Reboot Schedule every Thursday at 3 A.M.:

1. Choose Maintenance and Diagnostics from the Selection menu.

2. Click Maintenance Commands and then click All.

3. In the Command field, enter PROGRAMMED REBOOT SCHEDULE ON then click Submit.

4. Enter PROGRAMMED REBOOT SCHEDULE THURSDAY 03:00 then click Submit.

5. Enter PROGRAMMED REBOOT DISPLAY then click Submit.

6. Ensure that the reboot schedule is displayed correctly.

### Entry: PROGRAMMED REBOOT DISPLAY

System Response:

PROGRAMMED REBOOT SCHEDULE IS ON
PROGRAMMED REBOOT SCHEDULED: THURSDAY 03:00:00
PROGRAMMED REBOOT RESOURCE RECOVERY IS ON
PROGRAMMED REBOOT RESOURCE: RECOVERY 03:00:00
PROGRAMMED REBOOT COURTESY IS OFF