Avaya Definity SI, Maintenance Manual, Page: 2325 / 2968

STBY-SPE (Standby SPE)
Issue 4 May 2002 10-1539 555-233-123
Test Result Error Codes and Text Strings
The text string messages and error codes documented in the Error Codes tables
at the end of this section may result from any of the system technician commands
described earlier in this section.
In general, these error codes result from an inability of the Active SPE to
successfully conduct a maintenance activity request on the Standby SPE and not
from a problem detected by the test itself. In fact, all error codes except for 2015,
2021, 2047, 2048, 2049, and 2050 indicate that the test was not actually run.
If an error code returned from a test does not appear in the Error Code table, the
Active SPE successfully conducted the maintenance activity request on the
Standby SPE, and the test was actually run (in most cases). For details on this
error code, refer to the documentation describing the specific object you now
suspect as possibly being defective. In the Short and Long Test Sequences listed
earlier in this section, the name of the object tested appears directly after each
test number and name.
Several of the conditions corresponding to the error codes documented here may
be detected as soon as the test <component> [[0]1] a | b [short | long]
command is issued. The net result is that none of the tests in the sequence for the
component will be attempted and a message will appear on the terminal message
line describing why the command was rejected.
The following is a list of these text strings.
■
Cannot interrupt Standby SPE while entering maintenance mode;
please try later
This message line error is displayed when a refresh spe-standby
command is issued while maintenance software is in the process of putting
the Standby SPE into Maintenance mode when any of the Error Types
listed in “Hardware Error Log Entries and Test to Clear Value” have
occurred and have not been resolved. It is also displayed when a system
technician-demanded test has been issued and subsequently canceled
because maintenance software is performing the Memory Functional Test,
Shadow Link Test, or M-BUS Time-out Query. Another cause may be that
maintenance software is in the process of putting the Standby SPE into
Maintenance Mode to run any other system technician-demanded test that
must be conducted on the Standby SPE in Maintenance Mode. Allow up to
10 minutes for the maintenance software to complete its attempt to put the
Standby SPE into Maintenance Mode before issuing the refresh
spe-standby command.
■
Cannot perform SPE interchange; for information use status system
This message is displayed in response to the reset system interchange
command and because there are outstanding STBY-SPE errors. Display
the error log using the “dup-spe” category, and following the procedures for
all STBY-SPE errors.