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.

Circuit Pack LEDs<br />

After a circuit pack has been initialized, a red LED should be accompanied by an alarm in the<br />

alarm log. A single fault can sometimes light alarm LEDs on several circuit packs, as in the<br />

following examples.<br />

● A TDM bus problem may cause several port circuit packs to display red LEDs.<br />

● A Maintenance circuit pack can prevent an Expansion Interface (EI) circuit pack from<br />

initializing.<br />

● Extensive interactions in the Center Stage Switch (CSS) can cause multiple alarms from<br />

single faults in DS1C, SNI and SNC circuit packs and fiber links.<br />

● Tone-Clock or ipserver-interface problems may cause other circuit packs to report alarms.<br />

● Optical fiber cables which are not connected correctly may cause several circuit packs to<br />

alarm.<br />

● Packet bus faults can cause several port circuit packs to display red LEDs.<br />

If a circuit pack has had at least five minutes to be initialized and the red LED is lit without an<br />

associated alarm in the alarm log, the circuit pack may not be in communication with the<br />

system. This may also be the case when a circuit pack is properly administered and present in<br />

its slot, but there is an Error Type 1 logged against it. To determine whether this is so, proceed<br />

as follows:<br />

1. Enter the list configuration board location command. If the system does not<br />

detect the circuit pack, this command will return one of the following:<br />

identifier not assigned<br />

no board<br />

If the documentation for the associated maintenance object gives no special instructions for<br />

this situation, go to the next step.<br />

2. Check the hardware error log for TONE-BD or TDM-BUS errors with the display errors<br />

command. If the board has a “P” suffix, execute the reset board location command.<br />

Otherwise, execute the test tdm, test tone-clock, test ipserver-interface<br />

command. Use the appropriate maintenance procedures to resolve any identified faults. If<br />

this does not resolve the problem, go to the next step.<br />

3. Reseat the suspect circuit pack.<br />

CAUTION: This<br />

! CAUTION:<br />

procedure can cause a partial or total service outage. Consult the<br />

documentation for the associated maintenance object before proceeding.<br />

Observe any precautions and procedures described above.<br />

4. Inspect the backplane connectors for bent pins.<br />

5. If the system seems to be functioning correctly, but the circuit pack in question will not<br />

communicate with the system, replace the circuit pack.<br />

Communication Manager Release 5.0 Issue 4 January 2008 293

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

Saved successfully!

Ooh no, something went wrong!