Maintenance Commands and Trouble-Clearing Aids
555-233-123
8-100 Issue 4 May 2002
Field descriptions
Cause
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.
■ 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.
To Next Page
Loading...
