Lucent Technologies Release 7 Manuel D’Utilisation
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Commands
8-99
display initcauses
8
The following display shows a typical result when dis init is entered.
Cause
mon: A restart was initiated from the system monitor (not available to craft
login).
login).
Sanity Timer Reset: The sanity timer on the processor timed out and reset
the system. This usually indicates corrupted software.
the system. This usually indicates corrupted software.
Scheduled Interchange: An interchange was performed as part of
scheduled daily maintenance.
scheduled daily maintenance.
Software Request: System software detected problems and executed a
restart to recover.
restart to recover.
SPE-Select Lead Change: On systems with duplicated SPEs, the SPE
select lead changed and reset the processor.
select lead changed and reset the processor.
SPE-Select Switch: The SPE select switches on the DUPINT circuit packs
were manually set to lock the standby SPE active, causing a spontaneous
interchange. This is not a recommended procedure.
were manually set to lock the standby SPE active, causing a spontaneous
interchange. This is not a recommended procedure.
Unknown: The restart could not be classified. The Error Log may contain
more information about the restart.
more information about the restart.
Upgrade Software: The indicated SPE was reset as part of the execution of
the upgrade software command. If this precedes a Software Requested
level 2 reset, both are probably associated and indicate a non-call
preserving upgrade took place.
the upgrade software command. If this precedes a Software Requested
level 2 reset, both are probably associated and indicate a non-call
preserving upgrade took place.
Action
The level of recovery performed by the system.
1
Reset system 1 (Warm)
2
Reset system 2 (Cold-2)
3
Reset system 3 (Cold-1)
4
Reset system 4 (Reboot)
5
Reset system 5 (Extended Reboot)
Planned SPE Interchange (requested by reset system command or
scheduled maintenance)
scheduled maintenance)
Escalated
Whether the restart was escalated to a higher level than originally
attempted. The system’s software escalation strategy can perform a higher
level restart than the one initiated if problems prevent or conditions interfere
with normal execution.
attempted. The system’s software escalation strategy can perform a higher
level restart than the one initiated if problems prevent or conditions interfere
with normal execution.
Carrier
The carrier (always A in a simplex system) on which the restart took place. If
an interchange took place, this indicates the carrier of the newly active SPE
that was switched into.
an interchange took place, this indicates the carrier of the newly active SPE
that was switched into.
Time
The month, day and time of the restart.