User Guide
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-131display initcauses 
8
■ 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 Idata. Again, this should only occur in systems with 
SBB.
Action The level of recovery performed by the system. The recovery levels 
follow:
■ 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)
Escalated Whether the restart was escalated to a higher level to clear the problem. 
There is a software escalation strategy which can cause a higher level of 
restart than the one previously performed to be executed if the need 
arises.










