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 472: Expansion Interface Lightwave Transceiver Looparound Test (#242) 5 of 5<br />

Error<br />

Code<br />

Test<br />

Result<br />

PASS When this test (#242) and the EI Local Looparound test (#240) pass, this<br />

indicates that the EI board is functioning properly, but it does not verify<br />

that the optical portion of the lightwave transceiver is functioning.<br />

1. Enter test board location on the EI board on both ends of<br />

fiber. If this test passes from both sides, but other tests fail, such as<br />

#241, this condition indicates either a faulty lightwave transceiver or<br />

the fiber itself has failed. To determine whether a lightwave<br />

transceiver or the fiber itself has failed, run the Expansion Interface<br />

Manual Loopback Procedure.<br />

Test #242 can only be run from both EIs if they are the standby pair<br />

and the active pair is working properly.<br />

2. If this EI board is failing other tests, run the Expansion Interface<br />

Manual Loopback Procedure<br />

0 NO<br />

BOARD<br />

Description / Recommendation<br />

Circuit Pack Restart Test (#252)<br />

3. If problems still exist after the EI Manual Loopback Procedure<br />

indicates both EI boards and both lightwave transceivers are healthy,<br />

manually check out the building fiber. Verify that each optical fiber<br />

connects to a transmitter at one end and a receiver at the other.<br />

4. If the tests pass, enter release board location.<br />

No board was detected by the test.<br />

1. Check the error log for wrong board (Error 125) or no board (Error<br />

131). Resolve either of these issues, if applicable.<br />

2. Check that the board is properly translated and inserted. If so, check<br />

for hyperactivity (Error 1538). If hyperactive, enter<br />

reset board location.<br />

3. Run the test again. If it fails, the ID chip on board may be bad.<br />

Replace the board and retest.<br />

This test is destructive.<br />

This test is not part of either the short or long demand test sequence.<br />

1682 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!