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

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

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

Reset Board Test (#787)<br />

The reset sequence will take about one minute to complete <strong>and</strong> runs on the DS1C-BD (DS1<br />

Converter Circuit Pack).<br />

Table 449: Reset Board Test (#787)<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

2100 ABORT Could not allocate the necessary system resources to run this <strong>test</strong>.<br />

1. Retry the comm<strong>and</strong> at 1-minute intervals up to 3 times.<br />

2300 ABORT The downlink message necessary to run this <strong>test</strong> could not be sent.<br />

1. Retry the comm<strong>and</strong> at 1-minute intervals up to 3 times.<br />

2301 ABORT The timer could not be set before sending the downlink message.<br />

1. Retry the comm<strong>and</strong> at 1-minute intervals up to 3 times.<br />

2316 ABORT Fiber link is not administered.<br />

1. Enter add fiber-link to administer the DS1 converter fiber link.<br />

2321 ABORT DS1 converter circuit pack is not busied out.<br />

1. Enter busyout board to busyout the DS1 converter circuit pack.<br />

2500 ABORT Internal system <strong>error</strong><br />

1. Retry the comm<strong>and</strong> at 1-minute intervals up to 3 times.<br />

PASS The reset sequence was executed successfully. However, this <strong>test</strong> result<br />

does not indicate whether the firmware diagnostic <strong>test</strong>s passed.<br />

1. Enter display <strong>error</strong>s <strong>and</strong> check the <strong>error</strong> log for Error Type 1<br />

for this circuit pack’s location. This indicates a failed diagnostic<br />

firmware <strong>test</strong>.<br />

2. Enter display alarms to check the alarm log for any<br />

ON-BOARD MAJOR alarms.<br />

0 NO<br />

BOARD<br />

See NO BOARD for the repair procedures.<br />

Issue 5 May 2009 1501

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

Saved successfully!

Ooh no, something went wrong!