A SERVICE OF

logo

DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-15Executing a Planned SPE Interchange
5
Executing a Planned SPE Interchange
Planned SPE interchanges are initiated on demand by the
reset system
interchange
command, or automatically by scheduled daily maintenance. The
latter is administered with the system-parameters maintenance screen. A
planned interchange normally has no perceivable effect on service. All active
calls, transient calls, system links and stimuli, and data transmission are
preserved. The SYSAM-RMT port (also called the Remote Access Port) is
dropped, necessitating a re-login. The duration of the interchange is
approximately one minute.
!
CAUTION:
Switching the SPE-select switches to the standby carrier causes a
spontaneous interchange, not a planned one. This can disrupt service and
is not a recommended procedure.
Prerequisites
Several conditions must be met to guarantee a non-disruptive interchange. If
these are not met the system will not execute the interchange. All of these
conditions, listed below, are expected to be met during normal operation.
The SPE must not be locked by the SPE-SELECT switches.
The standby SPE must be fully in service.
That is, handshake is up, shadowing is on, memory is refreshed, and
standby SPE state-of-health is “functional”. ‘‘STBY-SPE (Standby SPE
Maintenance)’’ describes how to correct a failure of any of these.
There can be no minor alarms against the standby’s PKT-INT or SYSAM
circuit packs.
There can be no ongoing disk or tape operations on either active or
standby MSS components.
Wait until all such operations, such as translation saves or backup
restores, are complete before requesting an interchange.
SPE Interchange Failures
If the above conditions are not met, or if any intermediate steps taken by the
system in executing the interchange fail, the interchange is prevented. Usually,
failure of a planned interchange has no effect on service.
If the interchange fails after the packet interface links have migrated, the system
will require a reset level 1 (warm restart) to restore the links. In such a case, no
calls are dropped, and new call service resumes within 5 seconds. However, it is
probable that there is a severe system problem which predates the attempted
interchange.