Initialization and Recovery
4-1
4
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
4
Initialization and Recovery
When the system is powered up, or when it exp eriences a catastrophic fault that
interrupts its basic func tions, it undergoes a reboot. In ad dition to reboot, there
are several less severe resets available for the system to rec over from less
disrupting errors. The technic ian can also initiate these resets with a c ommand.
!CAUTION:

System resets can have wide-ranging disruptive effects. Unless you are

familiar with resetting the system, follow normal escal ation procedures

before attempting a d emand reset.

If a reset fails to recover normal system operation, the fir mware that controls reset
will escalate to the next higher level, up to reb oot if necessary. A failure to reboot
results in SPE-down mode, which is descr ibed in later in this chap ter.
This chapter describ es the causes, effects, and duration of each reset level. In a
syste m with dup lica ted SPE, t he sta ndb y SPE can unde rgo a reset w ithou t
disrupting servic e since the active SPE remains in control. These resets can also
be requested with the corresponding reset standby-spe

level

commands. All
stand by re sets t urn of f memo ry sha dowi ng, l eaving the s tand by SPE te mpor arily
unavailable for service. Refresh of the standby typically takes several minutes.
When resets occur, including interchanges, an error is logg ed against the
maint enanc e obj ect “ SYSTEM.” The erro r cod e gi ves in forma tion a bout t he ca use
of the reset. Information about the reset is also logg ed in the initcauses log . See
display initcauses in Chapter 8, ‘‘Maintenance Commands’’.
The EPNs can also undergo individual resets. These are desc ribed in ‘‘EXP-INTF
(Expansion Interface Circuit Pack)’’ and ‘‘EXP- PN (Expansion Port Network)’’ in
Chapter 9, ‘‘Maintenance Object Repair Procedures’’. PNC interchanges are