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 objec t ‘‘STBY-SPE (Standby SPE Maintenance)’’
contains proced ures for troubleshooting specific problems such as hand shake
failure, memory shadowing failure, and poor state of health. The following
proc edur es de scrib e a me thod for de termi ning the c ause of a spo ntane ous SPE
interchange and resolving any related problems.
If a sp ontan eous SPE i nterc hange has occurred , assume that a serious fault has
occ urred on the SPE that is curr ently the sta ndb y. The fol lowin g symp toms
indi cate t hat a s pont aneou s SPE inter chan ge has taken plac e:
■A MINO R alarm with e rror ty pe 10 3 is lo gge d aga inst STB Y-SPE.
■An interchange entry is rec orded in the initcauses log .
■The system is put into

recent interchange mod e

, which prevents further
SPE interchanges from taking place.
The presence of recent interchange mod e is displayed on the status spe sc reen.
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 spontane ous interchange:
■Major hardware failure
■Failed recovery that has been software esc alated
■Switc hing both SPE- SELECT swi tches to the stand by c arrie r (not a
recommended proc edure)
In the last case, the interchang e is not fault-driven, and no spec ific repair action
is required. To determine whether this is the case, enter display initcauses. If
the interchange was initiated b y the SPE-SELECT s witch es, th e Cause field will
appear as in the following ex ample.
If the interchange was fault-drive n, 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 occ urred, the Alarm Log
retains a record of any MAJOR ON-BOARD alarm against an SPE
component that took plac e before the interchange. This record is retained
for three hours and may indicate the cause of the interchange when
testing is not possible or c onclusive. Other information in the Error Log
may also be helpful.
2. Testing the standby SPE when the logs do not identify the p roblem.
Cause Action Escalated Carrier Time
SPE-SELECT switch 1 no 1B 11/27 14:53