Filter
Top Products
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-128display initcauses
8
Output
Cause The cause field indicates the reason for the restart.
■ Active Down: (high or critical reliability system only) The Active SPE
went into SPE Down mode. The Duplication Interface initiated an
SPE-interchange to the Standby SPE. If this initcause triggers an SPE
interchange when the Standby is NOT in Maintenance mode, the
previous entry in the log may actually represent a restart that
occurred on the Standby SPE. See the preceding description of
display initcauses for a complete explanation. If a high or critical
reliability system does a PEI with a warm start, the system software
often requests a Cold 2 restart to recover properly only minutes after
the warm start has occurred.
■ Bad Handshake: (High or Critical Reliability system only) The
Duplication Interface received inconsistent handshakes from the
Active SPE. Thus, the Duplication Interface initiated an
SPE-interchange to the Standby SPE. If this initcause triggers an SPE
interchange when the Standby is NOT in Maintenance mode, the
previous entry in the log may actually represent a restart that
occurred on the Standby SPE. See the preceding description of
display initcauses for a complete explanation. If a High or Critical
Reliability System does a PEI with a warm start, the system software
often requests a COLD 2 restart to recover properly only minutes after
the warm start has occurred.
■ Bad Memory: A defective memory circuit pack generating too many
errors caused a restart.
■ System Technician Request: The restart was performed because of
system technician demand. A system technician-requested reset
system 4 command entry should always precede an upgrade
software command entry.
■ Failed Interchange: A "hot-start" interchange (system
technician-demanded, scheduled, or software-requested) failed
because shadowing was disabled.
■ From Monitor (mon): (For Development Environment only)
■ Initialized: This is always the first entry in the history and is present
until more than 15 restarts have been performed. It indicates
power-up and also occurs if the Maintenance/Tape Processor is reset
during initialization.