Avaya MCC1 Maintenance Procedures page 177

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
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
A500 System Console
login: root
password:
********** New System Alarms **********
[1] Failed to fetch configuration files
******* Hit any key to continue *******
A500:
8 Enter status at the A500:
178 shows the output from the status command.
Maintenance Procedures
December 2003
Figure 27, A500 login screen,
(c) 1997 Avaya Inc.
XXXXXX
prompt.
(Table 61, A500 LED Quick Reference,
on page 177.)
Figure 28, A500 screen output for status command,
Troubleshooting
Troubleshooting ATM
on page
on page
177