EasyManua.ls Logo

Avaya Definity SI - Page 2316

Avaya Definity SI
2968 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Maintenance Object Repair Procedures
555-233-123
10-1530 Issue 4 May 2002
w. Error Type 809 is logged when the upgrade software command failed due
to the failure to perform an SPE-Interchange immediately after the
successful upgrade of the Standby SPE. This implies possible problems
with the Dupint circuit packs.
Issue the test duplication-interface a and test duplication-interface b
commands. If the tests pass, re-execute the upgrade software command.
x. Error Type 810 is logged when the upgrade software command failed due
to a bad checksum on the software card-mem during the upgrade of the
new Standby SPE following the successful upgrade of the old Standby
SPE and of SPE-Interchange.
The software card-mem should be replaced by one that has a good
checksum. The upgrade software command should be re-executed.
y. Whenever an SPE interchange is forced by using the health-override
option as part of the reset system interchange command, a WARNING
OFF circuit pack STBY-SPE alarm is raised, and the Fault Severity Level
(FSL) of the new standby SPE is raised to its highest possible value to
prevent an SPE interchange back to the original active SPE. This artificial
FSL lasts one hour or until a busyout spe-standby command is executed,
followed by a release spe-standby command. After this time, the FSL of
the two SPEs are recomputed, and the healthiest SPE becomes or
remains active.
z. The system interchanged from the active SPE to the standby SPE with a
restart that is more disruptive to service than the normal system hot start.
The switches were not used to force this interchange. The level of restart
can be observed by using the display initcauses command. Look for
other alarms on the standby SPE that possibly caused this interchange.
Also see Reset System Interchange (High or Critical Reliability Systems
Only) in Chapter 4, ‘‘Initialization and Recovery’’.
aa. The software vintage in the Standby SPE does not match the software
vintage in the active SPE.
The upgrade software command should be executed for the standby SPE
as described in Chapter 5, ‘‘Routine Maintenance Procedures’’.

Table of Contents

Related product manuals