Lucent Technologies R5SI 用户手册
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-1276
STBY-SPE (Standby SPE)
10
described in Items 6, 7, and 8) is executed within three minutes, the one to
20-minute delay prior to the first test will
20-minute delay prior to the first test will
not
be observed. Each test in the
sequence, including the first test, takes from 10 to 60 seconds to run.
Furthermore, the Active SPE leaves the Standby SPE in Maintenance
Mode for three minutes after the completion of the additional command.
This is true for each additional test command issued on a Standby SPE
component.
Mode for three minutes after the completion of the additional command.
This is true for each additional test command issued on a Standby SPE
component.
6. The
test memory [[0]1] a | b long
command is an exception to Item 5.
Because of the nature of the Memory Functional Test (#332) the same
delays as described in Item 2 are always observed for
delays as described in Item 2 are always observed for
test memory [[0]1]
a | b long
.
7. The
test duplication-interface [[0]1] a | b long
command is also an
exception to Item 5. Because of the nature of the MBUS Time-out Query
(#285) the same delays as described in Item 3 are always observed for
(#285) the same delays as described in Item 3 are always observed for
test duplication-interface [[0]1] a | b long
.
8. The
test spe-standby long
command is also an exception to Item 5.
Because of the nature of the Memory Functional Test (#285), the Shadow
Link Test (#318), and the MBUS Time-out Query (#285) the same delays
as described in Item 4 are always observed for
Link Test (#318), and the MBUS Time-out Query (#285) the same delays
as described in Item 4 are always observed for
test spe-standby long
.
9. For test commands whose sequence spans multiple terminal screens (for
example,
test spe-standby [short | long]
) the same 3-minute window that
was described in Item 4 applies to pressing the "page" key to proceed to
the next screen of test results. If the "page" key is not pressed within three
minutes of the completion of the last test on the current screen, the one to
20 minute delay is observed before the first test on the next screen is run
and its test results are displayed on the terminal. Each subsequent test on
that screen takes from 10 to 60 seconds to run. If the "page" key is
pressed within three minutes of the completion of the last test on the
current screen, the one to 20 minute delay will
the next screen of test results. If the "page" key is not pressed within three
minutes of the completion of the last test on the current screen, the one to
20 minute delay is observed before the first test on the next screen is run
and its test results are displayed on the terminal. Each subsequent test on
that screen takes from 10 to 60 seconds to run. If the "page" key is
pressed within three minutes of the completion of the last test on the
current screen, the one to 20 minute delay will
not
be observed.
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.
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.
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
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