DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1499STBY-SPE (Standby SPE Maintenance)
9
There are two ways in which the standby SPE can exit recent interc hange mode.
a. You can run test spe-standby long clear and wait until all the tests of
STBY-SPE hav e com ple ted. (thi s runs test s of
all
components of the
standby SPE in addition to those for STBY-SPE). The first test of the
sequence (#855) fails, b ecause the standby SOH is at level

partially

functional
. The execution of this sequence c lears the minor alarm against
STBY-SPE and allo ws nor mal t reatm ent of the s tand by SPE. I f the s tand by
is refreshed and has no major alarms ag ainst critical co mponents, its SOH
will be allowed to improve to
functional
.
b. Alternately, when one hour has passed since the last spontaneous
interchange, system software automatical ly transitions the standby SPE
out of recent interchange mod e. The minor alarm clears and the stand by
SPE’s SOH level is allowed to go to its appropriate value (typically
functional
if there are no major component alarms and it is refreshed).
Resolving Error Conditions on the Standby SPE
Divergence of the standb y SPE from the state of full availability involves one of
the following events:
■Handshake communication i s down
■Memory shadowing is off
■The standby SPE is not refreshed
■The standby SOH is not
functional
A hierarchical app roach is recommended in the above order. Follow the steps
presented in the following d iagram.