Filter
Top Products
DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Commands
2-71display initcauses
2
Field descriptions
Cause
■ 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.
■ LMM Request
: A sanity time-out was requested by the LMM
firmware. The three processor circuit pack LEDs blink until the sanity
timer goes off. The LMM requests a restart like this when it gets into
trouble, usually with memory.
■ Maintenance Reset
: This refers to resets of the SPE by
maintenance in SPE Down mode in which maintenance periodically
tries to awaken the SPE.
■ Oryx Request
: A sanity time-out was requested by the Oryx
operating system. The three processor circuit pack LEDs blink until
the sanity timer goes off. Oryx requests a restart like this when it gets
into trouble, usually with software.
■ Sanity Timer Reset
: The sanity timer on the processor timed out
and reset the system. This event usually indicates a software fault.
■ Software Request
: Software requested the system restart.
■ Unknown
: A restart that could not be classified. The Software Error
Log may contain more information about the restart.
■ LMM Put Fail
: This initcause occurs when the LMM has failed to
place the request for initcause message in the DPR. This could occur
if the MTP does not respond to the DPR handshake. Level of Restart:
Warm (escalation turned on).
■ LMM Get Fail
: This initcause occurs when the LMM does not
receive a response to the request for initcause message from the
MTP. This could occur if the MTP is not taking messages out of the
DPR. Level of Restart: Warm (escalation turned on).
■ MTP Reset Unknown
: This initcause occurs when the LMM has
reset the MTP during the process of trying to get initcause from the
MTP. Level of Restart: Warm (escalation turned on).