19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - 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 125: Aux Data for Error Type 258 3 of 6<br />

Aux Data Description of Failure<br />

6 This is one of two different <strong>error</strong>s. On the SAT, enter<br />

status firmware download location to determine the<br />

reason code.<br />

Reason Code 6208: The suffix on the change firmware<br />

download screen does not match the suffix of image on the source<br />

board.<br />

1. Verify that the suffix is correct, <strong>and</strong> make sure the correct image is<br />

being used.<br />

2. Retry the download comm<strong>and</strong>.<br />

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

Reason Code 6265: The Certificate Chain of Trust is invalid.<br />

Possible corrupt firmware file.<br />

1. Re-copy the firmware file from the <strong>Avaya</strong> support website.<br />

2. Retry the download.<br />

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

7 This is one of three different <strong>error</strong>s. On the SAT, enter<br />

status firmware download location to determine the<br />

reason code.<br />

Reason Code 6201: The source board is not inserted.<br />

1. Compare the board’s entered location on the change firmware<br />

download screen with its actual location.<br />

2. Verify that the source board is inserted.<br />

3. Retry the download.<br />

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

Reason Code 6263: No source board available for download.<br />

1. Wait until a source board is available<br />

2. Retry the download.<br />

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

Reason Code 6266: An <strong>error</strong> occurred attempting to unpack the<br />

verification information in the firmware image. Possible corrupt<br />

firmware file.<br />

1. Re-copy the firmware file from the <strong>Avaya</strong> support website.<br />

2. Retry the download.<br />

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

472 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

3 of 6

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

Saved successfully!

Ooh no, something went wrong!