
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1501STBY-SPE (Standby SPE Maintenance)
9
To restore handshake, proceed through the following steps.
1. Make sure that the SPE is not locked, and that it has power. Resolve any
CARR-POW alarms on the standby SPE carrier. (If the standby SOH is
partially functional or better, you can assume that the standby SPE has
power.)
2. Busyout the standby SPE and run
test dup long
. Some DUP-CHL tests
may abort due to the absence of handshake. If any tests
fail
, follow
procedures in DUPINT and then DUP-CHL to resolve the problem. If you
replace any DUPINT hardware, wait to see if the standby SPE can be fully
restored to service.
3. If the above tests did not fail, lock the SPEs with the SPE-select switches
and use the SPE-down interface to test the standby components as
described in Chapter 4. If all tests pass, proceed to the next step. Replace
any component that fails testing. (Use the lock-and-power-down
technique.) Bring the SPE back up as described in Chapter 4.
4. With the standby still busied out, issue the command
r
to reboot the
standby SPE and immediately unplug the STANDBY terminal connector.
The standby should still be busied out. Wait for the yellow LED on the
standby Processor to begin flashing, unlock the SPEs, and monitor the
standby with
status spe
.
5. If handshake is established, release the standby SPE from busyout and
monitor its recovery with
status spe
. If the onset of memory shadowing or
refresh causes handshake to fail, then suspicion is cast on these standby
circuit packs:
■ DUPINT
■ PKT-INT
■ MEMORY
■ MSSNET
Replace each of these in the standby in the above order, using
lock-and-power-down. For each one, bring up the standby SPE and wait
to see if handshake and memory refresh succeed.
Resolving Shadowing Failure
This section addresses the situation in which handshake communication is up,
but memory shadowing is not on after reasonable initialization time, or is
repeatedly turning on and off. If the onset of memory shadowing is causing
handshake failure, see the preceding section.
The following conditions prevent memory shadowing:
■ Busyout of the standby SPE
■ Locking of the SPEs by means of the SPE-select switches