DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1509STBY-SPE (Standby SPE Maintenance)
9
Standby SPE Status Query Test (#855)
This test
does not require handshake communication.
It reads the active SPE’s
duplication interface circuit pack hardware register to determine standby SOH,
status of the lock switches, and whether shadowing is currently turned on. It
updates all internal status data kept about the standby SPE (which can be read
via the "status spe" command). This test is considered to pass if standby SOH is
functional
, memory shadowing is turned on and the standby memory is fully
refreshed. It returns different failure codes depending of which of these
conditions is not met. Abort codes reflect that the status data could not be read.
Table 9-570. TEST #855 Standby SPE Status Query Test
Error
Code
Tes t
Result Description/ Recommendation
1330 ABORT Test cannot run due to duplication-interface hardware failure.
1. busyout spe-standby
2. test duplication-interface long
3. Proceed according to the DUPINT and DUP-CHL service documentation in
this chapter.
4. If all DUPINT tests pass, rerun command.
1338 ABORT Test cannot run because a planned SPE interchange is in progress
1. Wait for the planned SPE interchange to complete (this might have been
stimulated by a craft request or by scheduled maintenance).
1321 FAIL Test failed because the SPEs are in locked mode.
1. Check that the SPE-SELECT switches on the two DUPINT packs agree with
this. This failure will clear once the SPEs are unlocked.
Continued on next page
