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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

UDS1-BD (UDS1 Interface Circuit Pack)<br />

Echo Cancellation is no longer being supplied by the board. Clear the alarm using the<br />

following comm<strong>and</strong>s: busyout board location, <strong>test</strong> board location long, <strong>and</strong><br />

release board location. If Test #1420 (Echo Canceller <strong>test</strong>) fails, replace the circuit<br />

pack.<br />

t. Error Type 1537: LAN Bus Timeout Error. This <strong>error</strong> occurs when the circuit pack transmits<br />

too many bytes on the LAN bus for a single frame. This condition may be caused by an<br />

on-board fault or by faulty data received on one of the circuit pack’s external ports. If any of<br />

the ports on this circuit pack are alarmed, refer to the repair procedures for those<br />

Maintenance Objects.<br />

If the <strong>error</strong> occurs three times within 10 minutes, the board is isolated from the Packet bus<br />

<strong>and</strong> the board is alarmed. To clear the alarm <strong>and</strong> restore the board to the Packet bus, use<br />

busyout board location, reset board location, <strong>test</strong> board location<br />

long, <strong>and</strong> release board location.<br />

If the problem persists, <strong>and</strong> there are no PKT-BUS alarms or port alarms, then replace the<br />

circuit pack.<br />

u. Error Type 1538: the hyperactive circuit pack is out-of-service <strong>and</strong> may exhibit one or more<br />

of the following symptoms:<br />

● The common circuit pack level <strong>test</strong>s such as Test #50 <strong>and</strong>/or Test #52 abort with Error<br />

Code 2000.<br />

● The <strong>test</strong>s run on the ports of this circuit pack return a NO-BOARD result.<br />

● A busyout/release of the circuit pack has no effect on <strong>test</strong> results.<br />

● A list configuration comm<strong>and</strong> shows that the circuit pack <strong>and</strong> ports are<br />

properly installed.<br />

The circuit pack is isolated from the system <strong>and</strong> every trunk or port on this circuit pack is<br />

placed into the out-of-service state. The system will try to restore the circuit pack within<br />

20-30 minutes. When no faults are detected for 20-30 minutes, the UDS1 Interface circuit<br />

pack is restored to normal operation. Every trunk or port of the UDS1 Interface circuit pack<br />

is then returned to the in-service state.<br />

If the board is not restored to normal operation or the <strong>error</strong> recurs after the board was<br />

restored to normal operation, escalate the problem.<br />

v. Error Types 3073 to 3160: for releases of G3V4 <strong>and</strong> higher, Error Type 3073 shows that<br />

this board is receiving slips. The Aux Data contains the last slip count reported.<br />

w. Error Type 3330: LAN critical <strong>error</strong>. A critical failure has been detected in the Packet bus<br />

interface of the circuit pack. This failure may be due to an on-board fault or a Packet bus<br />

fault. If the Packet bus is alarmed, see PKT-INT (Packet Interface) for recommended repair<br />

procedures.<br />

This <strong>error</strong> isolates the board from the Packet bus <strong>and</strong> raises an alarm. If the Packet bus is<br />

not alarmed, enter busyout board location, reset board location, <strong>test</strong><br />

board location, <strong>and</strong> release board location. This should clear the alarm <strong>and</strong><br />

restore the board to the Packet bus.<br />

If the problem persists, <strong>and</strong> there are no PKT-BUS alarms, then replace the circuit pack.<br />

Issue 5 May 2009 1037

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

Saved successfully!

Ooh no, something went wrong!