Installation guide

26-3
Messages 900 – 999
Local -912- [protocol] Load failure, timeout
Explanation: A downline load sequence was interrupted because a load message was not
received. The load sequence is restarted.
Action: For information on software installation failure, refer to Chapter 1 .
Local -913- Fatal Bugcheck, PC = n SP = n SR = n M = n C = n
Explanation: The access server hardware detected an internal fatal error, called a fatal
bugcheck error. This error can be caused by either the software or the hardware:
• If the fatal error is a software problem, it is likely to cause only intermittent fatal
bugcheck errors. Your unit might operate again for a period of time, then fail again. If
there is more than one access server on the Ethernet, the problem could affect all the
units.
• If the fatal error is a hardware problem, it is probably isolated to one access server. The
hardware problem may be intermittent and only affect the unit occasionally. There is
no corrective procedure for this problem. Refer to Chapter 29 for service information.
When a fatal bugcheck error occurs, the access server attempts an upline dump of its
memory to a load host on the Ethernet. If several load hosts are defined, the address of the
one that accepted the upline dump can be determined using the SHOW SERVER STATUS
command. The Ethernet address of the dump host is displayed along with the crash
information from the fatal bugcheck error message.
Action: Record the values of the five parameters in message 913, and forward this
information and the access server upline dump file to supplier. Refer to Chapter 29 for
service information.