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.

4. Enter busyout board location<br />

5. Enter reset board location<br />

This test runs on EXP-INTF (Expansion Interface Circuit Pack).<br />

Table 489: Expansion Interface Reset Test (#336) 1 of 3<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

Expansion Interface Reset Test (#336)<br />

4 ABORT The neighbor EI circuit pack or SNI circuit pack is not recognized by the<br />

system. The circuit pack is not inserted.<br />

1. Insert neighbor EI circuit pack or SNI circuit pack and perform the<br />

reset again.<br />

1015 ABORT The EI circuit pack has not been busied out.<br />

1. Busyout the EI circuit pack with busyout board location.<br />

2. Enter reset board location.<br />

3. Retry the command.<br />

2000 ABORT Response to the test was not received within the allowed time.<br />

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

2500 Internal system error<br />

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

1 FAIL The EI did not successfully reset.<br />

1. If the EI circuit pack is in the PN, the PN’s Maintenance board may<br />

be holding the EI circuit pack reset. Attempt to rectify this condition<br />

by executing test maint P long on the Maintenance board in<br />

the same PN.<br />

2. If step 1 was not successful in releasing the EI circuit pack,<br />

temporarily remove the PN’s Maintenance circuit pack.<br />

3. Repeat reset board location.<br />

4. If reset continues to fail, replace circuit pack.<br />

5. Insert PN’s Maintenance circuit pack if it was removed.<br />

1 of 3<br />

Communication Manager Release 5.0 Issue 4 January 2008 1713

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

Saved successfully!

Ooh no, something went wrong!