Troubleshooting
Troubleshooting ATM
Maintenance Procedures
177
December 2003
Diagnostics
Has the A500 been installed and configured correctly?
•
Is the A500 powered up?
•
If you are administering the A500 through a locally attached console, is there a local console
terminal connected to the console port on the A500 switch processor board with the correctly
pinned RS232 serial cable?
•
If you are administering the A500 through Telnet over the Ethernet, is there an 10BaseT Ethernet
drop plugged into the Ethernet port on the A500 switch processor board? (Note that a few A500
commands are only permitted over the local console terminal.)
•
Has the A500 been booted using either the recessed reset button or by turning the power off, then
on again?
•
Did the A500 go through a normal power-up sequence, including testing every LED?
•
Are any A500 amber fault LEDs lit?
•
Are the remaining A500 LEDs in a normal state (
Table 61, A500 LED Quick Reference,
175)?
•
Can you log into the A500 console using the diagnostic account root from the local console
terminal or through Telnet? (See
Figure 27: A500 login screen
8
Enter status at the
A500:
Figure 28, A500 screen output for status command,
178 shows the output from the status command.
A500 System Console
(c) 1997 Avaya Inc.
login: root
password: XXXXXX
********** New System Alarms **********
[1] Failed to fetch configuration files
******* Hit any key to continue *******
A500:
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 ...