DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1510STBY-SPE (Standby SPE Maintenance)
9
1322 FAIL Test failed because memor y shadowing is off (b ut not inhibited). When not
inhibited by the standby SPE, memory shadowing can be off for the following
reasons:
1. Shadowing has not been turned on yet (temporary condition). To allow for
this, the test again (or status spe) after 5 minutes to see if shadowing is
then on.
2. There is a failure in the d uplication-inte rface hardware: to a llow for this, look
for errors or alarms against the duplication-interface hardware (DUPINT
and DUP-CHL): address these according to duplication-interfac e
documentation. Then re-run the test.
3. Ha ndsh ake ha s not b een es tabl ished betw een th e two SPEs: use "st atus
spe" to see if handshake is up. If it is not, address that problem according
to the section
Resolving Handshake Failure
.
4. There is a hardware configuration mismatch between components of the
two SPEs. Look for error 1537 in the hardware error log and use "list config
control" to identify the hardwa re discrepanc y between SPEs. Fix this.
5. There is a major alarm against the memory (MEM-BD), packet-interface
(PKT-INT) or switch-control (SW-CTL) circuit packs of the standby SPE.
Look for alarms against these and correct the problem.
1324 FAIL Test failed because stan dby SPE has
partially function al
SOH;
1. Use "display alarms" to see alarms against standby SPE components.
2. If a MINO R alarm is ac tive ag ains t the c urren t car rier o f STBY-SPE,
associated with an error 103, then clear this condition with "test
spe-standby lo n g". If a WARNING alarm exists against STBY-SPE, use
"status spe" to see if the standby is busied out. If so, "release spe-standby"
will clear the health problem.
3. Use "status spe" to see if handshake is up. If it is not, deal with that problem
according to the section
Resolving Handshake Failure
.
4. Otherwise look for a MAJOR, ON-BOARD alarm against the processor
(PROCR), memory (MEM-BD), switch-control (SW-CTL), packet-interface
(PKT-INT) , or SYSAM circ uit p acks of the s tand by SPE. Us ing t he
lock-and-power-down approach, rep lace the offending circuit pack on the
standby SPE. Consult the documentation for that component to clear its
alarms. Once the alarm against the offending component clears, the SOH
of the standby SPE will automatically improve from the
partially functional
level. If error 1324 persists and either none of the above c ases is true or
you have fixed all of these particular problems, escalate the problem.
Table 9-570. TEST #855 Standby SPE Status Query Test — Continued
Error
Code Test
Result Description/ Recommendation
Continued on next page