DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Commands
8-189reset system interchange
8
■ If Packet Interface link migration fails
■ If a minor or major alarm is logged against the standby SPE’s SYSAM or
Packet Interface circuit packs
■ If the standby SPE is busied out
The destructiveness of an interchange that fails depends on how far the
interchange proceeds before it fails. A non-destructive recovery should occur if
an interchange is aborted before link migration has started. If the interchange
fails after link migration has started, the system will perform a WARM restart to
recover.
The SPE-Select switches located on the Duplication Interface circuit packs
override any demand maintenance activities. If the SPEs are locked by means of
these hardware switches, an interchange cannot take place until the switches are
unlocked.
If a planned interchange aborts or fails, an error will be logged against SYSTEM,
signaling that the expected interchange has not occurred. In this case, the reset
may be escalated by software. This condition is described in Failure of Planned
Interchange in Chapter 5, ‘‘Alarms, Errors, and Troubleshooting’’
.
If
reset system interchange override
is specified while a PNC interchange is
occurring, a spontaneous (hard) SPE interchange will occur which results in a
Cold restart. After the restart, the active PNC will be the one that was being
switched into before the restart.
If a requested SPE interchange fails, an error conveying additional information
about the failure will be logged against the SYSTEM maintenance object.
