09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Communication Manager Maintenance Object Repair Procedures<br />

Table 221: Aux Data for Error Type 258 5 of 5<br />

Aux Data Description of Failure<br />

17 Could not retrieve the file from the file server<br />

1. Verify that the file image is present on the file server and in the<br />

directory that was specified on the change firmware<br />

download screen<br />

2. Verify that the source board is able to reach the file server.<br />

3. Verify that the login and password work on the file server.<br />

4. Verify that the file server is configured correctly.<br />

5. Retry the download command.<br />

6. If the error recurs, escalate the problem.<br />

18 Invalid header information - No flash time for download.<br />

19 IP address message was not acknowledged by the source board<br />

20 Login/password messages not acknowledged by the source board<br />

21 Failed to send login and password messages to the source board<br />

22 Failed to send image name message to the source board<br />

23 No response to image name message from the source board<br />

24 Downlink for file retrieval failed to the source board<br />

25 Source board did not respond to file retrieval message<br />

26 Downlink for IP address failed<br />

1. Retry the download command.<br />

2. If the error recurs, escalate the problem.<br />

27 Attempt to store download data failed. This is a system error.<br />

1. Check for system-wide errors.<br />

2. Retry the download command.<br />

3. If the error recurs, escalate the problem.<br />

846 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s<br />

5 of 5

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

Saved successfully!

Ooh no, something went wrong!