Avaya Media Processing Server 1000 Hardware Installation And Maintenance page 153

You do not need a detailed understanding of each task in the sequence to diagnose system
problems. If the LEDs indicate that multiple corrective actions are needed, perform the tasks in the
order listed and retest after each task until the system boots normally. To reboot the NIC press the
reset button on the edge of the NIC (see preceding illustration) or do a soft reset. See
NIC on page 147.
Table 9: Boot Sequence Diagnostics for NIC
Hex Duration (approx.)
Code
02/03 (See description)
82/83 --
04/05 (See description)
84/85 --
86 --
06/07 <<1 sec.
08/09 ~3-5 sec.
0A/0B (See description
0C/0D <1 sec.
October 2014
Description of Task or Error
DRAM write and immediate readback
and verify test. This LED only tests
onboard SIMM ability to retain data.
Activity LED switches on or off for each
MB of memory tested (that is, 1 MB on
and 1 MB off).
DRAM write/read test failed.
DRAM readback and verify test. Reads
back the pattern written in the previous
test, then writes all 0s. Also tests address
bus and memory size. Activity LED
switches on or off for each MB of memory
tested (that is, 1 MB on and 1 MB off).
DRAM readback test failed.
DRAM test failed. Looping and watchdog
timer that times out forcing a reset
(independent of the state of the watchdog
timer in boot ROM dialog).
Copy ROM to RAM and start PSSINIT
Initializes hub chip (ETH-1000 board
Waits for time-out as specified under
STARTUP DELAY in boot ROM dialog.
Default is 5 seconds. (See
Modifying Boot ROM Settings
page 139.
NIC waiting for console input from boot
ROM dialog. See
Boot ROM Settings
Avaya Media Processing Server 1000 Hardware Installation and Maintenance
Comments? infodev@avaya.com
1
.
2
).
Verifying and
on
Verifying and Modifying
on page 139.
NIC Startup LED Sequence
Resetting the
Corrective Action(s) for
Error(s)
• Remove and replace the
memory SIMM on board
NIC.
• If the error persists, remove
and replace the NIC.
(Reinstall the original SIMM
on the failed NIC and tag for
logistics disposition.)
• If the system remains in this
state, check the NIC for
proper grounding. Check
that the NIC card is seated
in the connector and the
mounting brackets make
good contact with the
chassis.
• A key is inadvertently struck
during the STARTUP
DELAY. Check the boot
ROM. See Verifying and
153