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

STBY-SPE (Standby SPE)
Issue 4 May 2002 10-1545 555-233-123
2015 ABORT The Standby SPE Maintenance/Tape Processor did not reply to an
Active SPE request to hold the Standby SPE Processor reset. The
communication path between the Active SPE and the Standby SPE
Maintenance/Tape Processor may have failed, or the Standby SPE
Maintenance/Tape Processor may have failed. Follow the
procedures described for Error Code 2024 in the STBY-SPE
section.
2016
2017 ABORT The Active SPE attempted to put the Standby SPE into Maintenance
Mode, but did not receive notification from the Standby SPE
Maintenance software that it successfully entered Maintenance
Mode OR, once in Maintenance Mode, the Standby SPE sent a
request to the Active SPE to have the Active SPE conduct a portion
of a test in the Standby SPE’s behalf, but the Standby SPE did not
receive a response to its request. In either case, the communication
path between the Active SPE and the Standby SPE may have
failed. Follow the procedures described for Error Code 2024 in the
STBY-SPE section.
2018 ABORT The test requires that a maintenance activity request be made to the
Standby SPE; however, the request cannot be made because the
Standby SPE is busy processing a previous maintenance activity
request.
1. Issue refresh spe-standby to force the Standby SPE to
Standby Mode. This command may have to be issued multiple
times. If refresh spe-standby successfully completes 5 times
without the Standby SPE becoming labeled “standby” on the
status system form, wait 30 minutes. This does not include
cases where the command completes with the terminal
message line errors “Refresh not successful; use ‘display
errors’ to check for STBY-SPE errors” or “Cannot interrupt
Standby SPE while entering maintenance mode; please try
later.” Issue refresh spe-standby once more.
2. Repeat the test.
3. Issue test spe-standby long to thoroughly test all Standby
SPE components.
2019 ABORT A translation save on the Standby SPE was not carried out because
the Shadow Link Test failed. (The Shadow Link Test was done to
verify the integrity of the translation data on the Standby SPE.)
1. Check for Memory Shadowing Link errors and alarms. Refer to
SHDW-LNK (Memory Shadowing Link) Maintenance
documentation and follow the prescribed procedures.
Table 10-578. Test Result Error Codes Associated with the Standby SPE — Continued
Error
Code Test
Result Description/Recommendation
Continued on next page