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.

BRI-PORT (ISDN-BRI Port)<br />

● 40988 – This indicates that the BRI-LINE circuit pack has detected an overcurrent<br />

condition and has turned the EPF off.<br />

Execute the short test sequence, and see the repair procedures for Test #622.<br />

e. Error Type 513: the circuit pack is having problems transmitting data to the packet bus,<br />

thus affecting the conveyance of signaling information over the D-Channel. With Aux Data<br />

46222, this error occurs when the packet bus transmit buffers overflow. This condition<br />

probably indicates a hardware problem. The BRI-PORT Alarm Level for the error with Aux<br />

Data 46222 is “MINOR/WARNING,” and the ABRI-PORT/ATT-PORT/LGATE-PT/ATTE-PT<br />

Alarm Level is “MAJOR/MINOR/WARNING.” With Aux Data 0, this error occurs whenever<br />

the packet bus transmit FIFO buffers overflow. This condition can be caused by an on-board<br />

hardware problem as well as by problems on the packet bus that disrupt the BRI circuit<br />

pack’s ability to transmit data onto the packet bus. Use troubleshooting procedures for both<br />

on-board hardware problems and potential off-board packet bus problems. See PKT-BUS<br />

(Packet Bus) as well as Isolating and repairing packet-bus faults in Maintenance<br />

Procedures (03-300432) for more information about troubleshooting the packet bus. The<br />

BRI-PORT Alarm Level for the error with Aux Data 0 is “MINOR,” and the ABRI-PORT/<br />

ATT-PORT/LGATE-PT/ATTE-PT Alarm Level is “MAJOR.”<br />

f. Error Type 769: the BRI NPE Crosstalk Test (#617) fails. Run the long test sequence, and<br />

note the results of Test #617.<br />

g. Error Type 1281: a port’s associated broadcast-signaling links have too much traffic related<br />

to link establishment. This could occur if an endpoint on this port is sending link<br />

establishment traffic on a port level broadcast link or if there are Level 1 problems on the<br />

port. Check the error logs for Level 1 errors. If Level 1 problems exist, follow the repair<br />

procedures listed for Test #621. Software will suspend activity to this port for 75 minutes<br />

when the port is alarmed due to this error (note that service suspension does not occur if<br />

the port is an ABRI-PORT/LGATE-PT/ATTE-PT/ATT-PORT). If this problem persists,<br />

replace the endpoint or endpoints associated with this port. If replacing the endpoints does<br />

not fix the problem, follow normal escalation procedures.<br />

h. Error Type 1537: the port receives an invalid frame over the D-Channel. When CRC errors<br />

exceed five within 15 minutes, the port is taken out of service for five seconds. If five more<br />

CRC errors are received within 15 minutes of the first set of five errors, the port is taken out<br />

of service for one minute. If five more CRC errors are received within 15 minutes of the last<br />

five, the port is taken out of service for 15 minutes.<br />

This error is most likely due to a problem with the wiring to the set or adjunct, interference<br />

on the wiring due to a noise source, or no termination (an open circuit). It usually does not<br />

indicate a problem with the circuit pack.<br />

● Check the wiring to the endpoints or the adjunct.<br />

● If the problem persists, replace the endpoints or adjuncts, or escalate the problem.<br />

i. Error Type 1793: the BRI Port Local TDM Looparound Test (#619) fails. Run the long test<br />

sequence, and note the results of Test #619.<br />

There are no recommended actions for the following Error Types. The Error Types are<br />

simply provided as additional data that may prove useful while troubleshooting.<br />

Communication Manager Release 5.0 Issue 4 January 2008 595

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

Saved successfully!

Ooh no, something went wrong!