Avaya Definity SI Maintenance Manual page 353

display initcauses
Action
Escalated
Carrier
Time
555-233-123
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).
Dupint Unknown: This initcause occurs when the LMM receives
an UNKNOWN initcause from the Dupint. This could occur in a
High or Critical Reliability System where the MTP thinks a PEI
has occurred but the dupint disagrees. 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).
S-vintage Mismatch: This initcause occurs when a mismatch in
the duplication super vintage is detected by the LMM. Level of
Restart: Reboot (no escalation).
Monitor Reset: (For Development Environment Only) This
initcause occurs when "ini 1" is executed from the Flash Monitor.
This initcause can occur only in systems with SBB. Level of
Restart: Reboot (no escalation).
Bad GDT: (For Development Environment Only) This initcause
occurs when the LMM fails to transfer control to Oryx/Pecos
because of absence of entry in GDT to point at O/P. This usually
occurs in a system with no data. Again, this should only occur in
systems with SBB.
The level of recovery performed by the system. The recovery levels
are:
Reset system 1 (Warm)
Reset system 2 (Cold-2)
Reset system 3 (Cold-1)
Reset system 4 (Reboot)
Reset system 5 (Extended Reboot)
Reset system interchange (High or Critical Reliability
System only - hot restart interchange)
Whether the restart was escalated to a higher level to clear the
problem. There is a software escalation strategy that can cause a
higher level of restart than the one previously performed to be
executed if the need arises.
The "carrier" statement indicates the carrier on which the recovery
was performed (possible values are 1A and 1B). In most cases, this
"carrier" is the Active SPE carrier when the restart occurs. However, it
is possible in a High or Critical Reliability System that this carrier was
the Standby carrier. See the preceding description of
initcauses'' for a complete explanation.
The date (month and day) and time of the restart.
''display
Issue 4 May 2002 8-103