reset system

Last Updated : Aug 07, 2023 |
Use reset system to reload Communication Manager software. All system resets are disruptive and terminate the SAT login.
Caution:
All system resets are service affecting, with higher levels being increasingly destructive. Some resets may take up to one-half hour to complete. Certain conditions may result in a higher reset level than the one requested. Unless you are experienced with resetting a system, follow normal escalation procedures.
Prolog information
Metadata
Keywords:

Syntax

reset system level# 
level#
(1–5) Restart Level

Description

If you set the value of the Display Warning Prior to System Reset? field to y on the system-parameters maintenance screen and then use the reset system command, a warning message is displayed. 
WARNING: All system resets are service affecting, with higher levels being increasingly destructive.
Press the SUBMIT or ENTER function key to continue or CANCEL to abort the command.
Note:
Connections are preserved on H.248 branch gateways on reset system 2 and reset system 4 conditions. To reset gateways from the SAT, use reset media-gateway.
reset system resets the system in the following manner:
  • A mini-coredump is generated for non-interchange related restarts and placed in the directory:/var/log/defty/dumps.
  • A change in translation administration is in progress.
System software does not escalate a demand system reset to a higher level. There are certain conditions that result in a higher level reset than that requested. These include:
  • the restart is performed

Approximate Recovery Time for System Resets (min:sec)

System reset times differ between different configurations
Level
Recovery
2,400 lines
5,000 lines
15,000 lines
1
Warm Restart
:10
:10
:10
2
Cold-2
1:00
2:00
4:00
4
Reload
4:00
6:30
11:00

reset system feature interactions

reset system invokes system initialization like low-level maintenance. Software never escalates requested reset levels; technicians determine the levels.
Reset system cannot be canceled. The screen shows the results of various initialization tests. If reset system is successful, the user is logged off. Several conditions may prevent a requested reset.

Reset Level 1

Reset Level 1 (warm restart) duration, causes, and effects
Duration
Up to 10 seconds, typically 4 seconds
Causes
reset system 1 command from Communication Manager (SAT) command line
Spontaneous server interchange (those caused by hardware faults) Software faults that are not service affecting
Demand server interchange
Software escalation
Effects
Stable calls are preserved; queued ACD calls, H.323 calls, and H.320 (multimedia) calls stay up.
System links such as ISDN-PRI D-channel signaling links, CMS, AUDIX, DCS links over Procor are preserved. The CMS, DCS, and AUDIX links could lose buffered messages.
Error and alarm logs are preserved, but every alarm is resolved except busyouts.
Stable features are preserved.
Transient calls (not yet connected) and some user stimuli are dropped.
New calls are not processed during the reset.
Encrypted system links may be dropped and reestablished.
If the reset resulted from a spontaneous server interchange, memory shadowing is turned off, and the standby server will not be available for service until memory is refreshed (several minutes).
Application links such as those to AUDIX and CDR are dropped and re-established in under 2½ minutes.
Translation data is preserved in memory. If save translation is in progress, an SAT-requested warm restart would be aborted. A software-requested warm restart would result in an unsuccessful save translation and possibly corrupt translations.

Reset Level 2

Reset Level 2 (cold restart) duration, causes, and effects
Duration
Up to 3.75 minutes
Causes
reset system 2 command from Communication Manager (SAT) command line
Escalation from SAT’s reset level 1
An attempted SAT’s reset level 1
Spontaneous interchange into an unrefreshed standby server
Effects
Every system and application link is dropped.
Gateways are not reset.
Every call is dropped.
Every administrative session is dropped.
Every system link is dropped and re-established.
Every application link is dropped and re-established.
Non-translation feature data, such as Automatic Wakeup calls, are lost and must be re-entered.
Translation data is preserved in memory. If save translation is in progress, a SAT-requested cold-2 restart would be aborted. A software-requested cold-2 restart would result in an unsuccessful save translation and possibly corrupt translations.
Every login, including remote access and system port logins, is dropped.
Initialization firmware runs diagnostics and displays results on the screen.
Server memory shadowing is turned off, leaving the standby server unavailable for service for up to several minutes.
Every hardware component is reset except:
  • DS1 clocks.
Every busied-out MO is released and can be rebusied.
Error and alarm logs are preserved, and every Communication Manager alarm is resolved.

Reset Level 4

Reset Level 4 (reload) duration, causes, and effects
Duration
Typically 11 to 14 minutes
Causes
reset system 4 command from Communication Manager (SAT) command line
Escalation from SAT’s reset level 2
Power up
Recovery attempt from server-down mode
Effects
System software (boot image) is reloaded and every process is re-initialized.
Communication Manager administration (translations) are reloaded from the hard disk.
Before reboot, the system attempts to save the alarm and error logs.
After reboot, error and alarm logs are restored. Some error and alarm information may be lost if the last save before the reboot save does not succeed.
Other effects are the same as those in reset level 2, except that more extensive diagnostics are performed.
A core dump is automatically enabled for this reset level and is saved to the /var/ log/defty/dumps/ directory. The reboot is delayed until the core dump is finished.