DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Commands
8-188reset system interchange
8
conditions may prevent a requested reset. If the reset fails and the message
displayed is not self-explanatory, use
status spe
to determine what caused the
failure.
reset system interchange
reset system interchange [health-override][contention-override]
!
CAUTION:
Although this command is normally not disruptive, certain conditions may
escalate the interchange to a higher reset level.
This command is used to switch control from the currently active SPE to the
standby. This type of interchange is called a planned, soft, demand or requested
interchange. Interchanges caused by hardware faults or the SPE-Select
hardware switches are called spontaneous or hard interchanges. Planned
interchanges are discussed under:
— SPE Duplication in Chapter 1, ‘‘Maintenance Architecture’’
— Executing a Planned Interchange in Chapter 5, ‘‘Alarms, Errors, and
Troubleshooting’’
— STBY-SPE in Chapter 9
This operation is not disruptive if the state of health of the standby SPE is
“functional.” If this condition is not met, system software will normally abort a
requested interchange. When this is the case, the
health-override
option can be
specified to try to force a
spontaneous
(hard) interchange.
!
CAUTION:
Use of health-override may cause serious service disruption.
Once a planned interchange has been initiated, it cannot be aborted with the
CANCEL key. A
reset system interchange
command will abort for the following
reasons:
■ If the standby SPE is down
■ If the SPEs are locked by means of the SPE-Select switches
■ If communication to the standby SPE is not possible (handshake is down)
■ If shadowing to the standby SPE is not turned on
■ If the standby SPE is not fully refreshed
■ If the State-of-Health of the standby is not “functional”
■ There is an SCD dual-port RAM failure
■ If there is any Mass Storage System activity
