DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-31ATM Tips
5
NOTE:
The following examples show DEFINITY port networks connected to A500
ports A1.1 and A1.2.
Has the A500 been installed and configured correctly?
Diagnostics
■ 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
all of the LEDs?
■ Are any A500 yellow fault LEDs lit?
■ Are the remaining A500 LEDs in a normal state (Table 5-6 above)?
■ Can you log into the A500 console using the diagnostic account
root
from
the local console terminal or through telnet? (See Figure 5-7
below.)
Figure 5-7. A500 login screen
8. Enter status at the A500: prompt. Figure 5-8
shows the output from the
status command.
A500 System Console
(c) 1997 Lucent Technologies
login: root
password: XXXXXX
********** New System Alarms **********
[1] Failed to fetch configuration files
******* Hit any key to continue *******
A500:
