DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Initialization and Recovery
4-14SPE-Down Command Interface
4
Duplicated SPE’’ and
‘‘Testing the Standby SPE’’
sections in
Chapter 5, ‘‘Alarms,
Errors, and Troubleshooting’’. Note that the test memory command performs
exhaustive tests and can be very time-consuming.
When testing is complete, the system readies itself for another command and the
prompt appears. If testing does not complete within 20 minutes, the following
message is displayed:
LMM did not finish test in time.
This is a serious error indicating that the processor, bus, and/or LMM are not
working properly. Normally you will see initial test result output within a few
seconds. If not, you can abort the test request by pressing
ESC 3 times, and the
command prompt will be returned.
If the SPE-down mode is entered or re-entered as a result of the test request, the
screen displays:
Can’t continue - test aborted.
Again, this is a serious error, but at least the processor is able to handle
SPE-down reporting. Likely fault locations are memory board number 1,
processor board, or processor/memory bus.
Display Alarms Command
The display alarms command asks for the alarms that caused the SPE to go
down. It is valid only in the SPE-down or down-and-locked-standby mode. If
d
is
entered while the SPE is in one of the down modes, the following header is
displayed:
DISPLAY ALARMS:
Physical
Name
Logical
Name
On
Board?
Alternate
Name
Alarm
Type
Date
Alarmed
Date
Resolved
