Server initialization, recovery, and resets
S8100 Initialization
Maintenance Procedures
129
December 2003
SPE-down mode
In the S8100 system, SPE-Down mode refers to the condition in which:
•
Windows 2000 failed
•
System firmware still running
The firmware will issue an INADS alarm call at 7 minute intervals. If the problem has not been corrected
after the first three messages have been issued, the alarm call interval is increased to 45 minutes.
Recovery from fatal errors
In general, if there is a fatal error, the system will not be operating at a level that can be investigated in the
field.
If the S8100 has a fatal error:
1
Reboot the system. If you cannot access the system using any of the software methods, you can
reboot the system by pressing the reset button on the TN2314 processor circuit pack.
2
Verify that you have no alarm leads on the TN2314 that could be shorted together to cause an SPE
download.
a
Check to see if UPS is being used.
b
If yes, proceed to the next step.
c
Check to see whether pins 26 and 1 are being used as other alarm inputs. Pins 26 and 1 on
the AUX connector are dedicated to the UPS alarm input.
d
If yes, disconnect from the other connections.
3
If the problem persists after reboot, you may have to replace the processor circuit pack.
Resolving alarms
An alarm is generated when a non-fatal error is detected by the S8100 system. This section describes
methods to determine the source of alarms.
Recovery procedures
The first step is to determine the location of the problem. It is possible for two or more circuit packs to
have failed. It is also possible for a fatal problem with one circuit pack to affect another circuit pack,
especially the Processor circuit pack. To determine where the fatal fault lies, employ all three of the
following methods:
•
Using the bash shell in a telnet session
•
Obtaining information from Communication Manager alarms
•
Summary of Contents for CMC1
Page 1: ...Maintenance Procedures 555 245 103 Issue 1 1 December 2003 ...
Page 14: ...Contents 14 Maintenance Procedures December 2003 ...
Page 416: ...Additional maintenance procedures IP Telephones 416 Maintenance Procedures December 2003 ...
Page 426: ...Index X 426 Maintenance Procedures December 2003 ...