DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-10Troubleshooting a Duplicated SPE
5
Troubleshooting a Duplicated SPE
The section on maintenance object
‘‘STBY-SPE (Standby SPE Maintenance)’’
contains procedures for troubleshooting specific problems such as handshake
failure, memory shadowing failure, and poor state of health. The following
procedures describe a method for determining the cause of a spontaneous SPE
interchange and resolving any related problems.
If a spontaneous SPE interchange has occurred, assume that a serious fault has
occurred on the SPE that is currently the standby. The following symptoms
indicate that a spontaneous SPE interchange has taken place:
■ A MINOR alarm with error type 103 is logged against STBY-SPE.
■ An interchange entry is recorded in the initcauses log.
■ The system is put into
recent interchange mode
, which prevents further
SPE interchanges from taking place.
The presence of recent interchange mode is displayed on the
status spe
screen.
The system is released from this mode, and the minor alarm is cleared, after 1
hour, or upon the execution of
test spe-standby long
, regardless of whether all
tests pass.
There are three possible causes of a spontaneous interchange:
■ Major hardware failure
■ Failed recovery that has been software escalated
■ Switching both SPE-SELECT switches to the standby carrier (not a
recommended procedure)
In the last case, the interchange is not fault-driven, and no specific repair action
is required. To determine whether this is the case, enter
display initcauses
. If
the interchange was initiated by the SPE-SELECT switches, the
Cause
field will
appear as in the following example.
If the interchange was fault-driven, there are two ways of finding the cause.
1. Using alarm and error logs in conjunction with the timestamp described
above. After a spontaneous SPE interchange has occurred, the Alarm Log
retains a record of any MAJOR ON-BOARD alarm against an SPE
component that took place before the interchange. This record is retained
for three hours and may indicate the cause of the interchange when
testing is not possible or conclusive. Other information in the Error Log
may also be helpful.
2. Testing the standby SPE when the logs do not identify the problem.
Cause Action Escalated Carrier Time
SPE-SELECT switch 1 no 1B 11/27 14:53
