Avaya Media Processing Server 1000 Hardware Installation And Maintenance page 150

Configuration
LED Duration (approx.)
3, 14, --
15
4, 14, --
15
4 <1 sec.
5 (See description)
6 <1 sec.
7 ~1-2 sec.
8 <<1 sec.
9 <<1 sec.
9, 14, --
15
10 (See description)
Avaya Media Processing Server 1000 Hardware Installation and Maintenance
150
Description of Task or Error
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. Code is looping and
watchdog timer times out forcing a reset
(independent of state of watchdog timer
in boot ROM dialog).
Copy ROM to RAM and start PSSINIT
Waiting for time-out as specified under
STARTUP DELAY in boot ROM dialog.
Default is 5 seconds. See
Modifying Boot ROM Settings
page 139.
Waiting for console input from boot ROM
dialog. See Verifying and Modifying Boot
ROM Settings on page 139.
Set values specified in the boot ROM
2
dialog, perform RARP and BOOTP
required. Activity LEDs cycle when
RARP and BOOTP packets are sent.
End system initialization and initialize
pSOS1 on page 154. System remains in
this state if one of the pROBE+ options
is selected as the boot mode from the
boot ROM dialog. See Verifying and
Modifying Boot ROM Settings
page 139.
4
Start of TFTP . (pSOS is now fully
loaded and running.)
Error in TFTP startup.
TFTP download of application image.
Activity switches with each 32 KB
downloaded. Duration depends on the
size of the download.
Comments? infodev@avaya.com
Corrective Actions for Errors
1
.
Verifying and
on
• If the system remains in this
state, check the TMS for proper
grounding. Check that the card
is seated in the connector and
the front panel makes good
contact with the chassis.
• Key is inadvertently struck
during the STARTUP DELAY.
Check boot ROM. See
and Modifying Boot ROM
Settings
Host not responding.
3
, if
• Check physical network
connections.
• Misconfigured IP address.
Check the boot ROM. See
Verifying and Modifying Boot
ROM Settings
on
• Most likely TFTP open failed,
typically from bus traffic, packet
errors, or the application
processor is not on the network.
Retry when the system
resources stabilize.
• Incorrect image definition file
(.idf) specified. See
Verifying
on page 139.
on page 139.
Verifying
October 2014