09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 228: Reason Codes for status firmware station-download 2 of 2<br />

Reason<br />

Code<br />

FW-STDL (Firmware Station Download)<br />

3 ABRT The terminal was not downloaded before the scheduled stop time<br />

occurred. Schedule a new download with adequate time for the<br />

downloads to complete, or select the continue daily option to allow the<br />

schedule to resume the following day.<br />

4 ABRT The terminal could not be downloaded because the schedule aborted<br />

for an unknown reason.<br />

5 ABRT The terminal did not respond to the download request.<br />

6 ABRT The terminal that was added to the download list at the scheduled start<br />

time no longer exists. This can occur when a station is removed during<br />

an active download schedule. Download to this terminal was aborted.<br />

18 ABRT The terminal was busied out by craft and could not be downloaded.<br />

32 ABRT Download to the terminal timed out due to an internal error in the station<br />

firmware download process.<br />

1000 ABRT Terminal was in use at the time that it was to be downloaded. Download<br />

to this terminal was aborted.<br />

1012 ABRT An internal error occurred while preparing to download to this station.<br />

3841 ABRT or<br />

FAIL<br />

Status Description<br />

The system restarted during an active download. As a result, all<br />

terminals that were not downloaded are marked with a status of ABORT<br />

with this reason code. All terminals that were actively downloading<br />

when the reset occurred are marked with a status of FAIL with this<br />

reason code.<br />

128 FAIL The terminal rejected the firmware because the firmware image failed<br />

the checksum test.<br />

129 FAIL The terminal rejected the firmware because the firmware image failed<br />

the image validity test. The firmware image may not be the right image<br />

for the hardware being downloaded to.<br />

130 FAIL The terminal being downloaded could not write its flash memory.<br />

131 FAIL A terminal in the range was translated to be a valid terminal for this<br />

download schedule. However, the terminal is not a valid receiver of the<br />

download.<br />

513 FAIL The terminal was not in service at the time that it was to be downloaded.<br />

Download to this terminal failed.<br />

3584 FAIL The terminal rejected the firmware image.<br />

2 of 2<br />

Communication Manager Release 5.0 Issue 4 January 2008 859

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!