09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

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

● faulty data received on one of the circuit pack’s external ports. If any of the ports on this<br />

circuit pack are alarmed, refer to the repair procedures for those MOs.<br />

If the error occurs 3 times within 10 minutes, the system raises the board alarm and isolates<br />

it from the packet bus.<br />

1. Clear the alarm and restore the board to the packet bus:<br />

a. busyout board location<br />

b. reset board location<br />

c. test board location long clear<br />

d. release board location<br />

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

circuit pack. See Shutting Down NT on the TN802 before removing the circuit pack.<br />

m. Error Type 1538: Hyperactive circuit pack is out-of-service and may exhibit one or more of<br />

the following symptoms:<br />

● The common circuit pack tests (for example, Test #50 and/or Test #52) abort with Error<br />

Code 2000.<br />

● Port tests on this circuit pack return NO-BOARD.<br />

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

● A list configuration shows that the circuit pack and ports are properly installed.<br />

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

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

20 – 30 minutes. When no faults are detected for 20 – 30 minutes, the MAPD Interface<br />

circuit pack is restored to normal operation, and every trunk or port on the MAPD Interface<br />

circuit pack returns to the in-service state.<br />

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

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

n. Error Types 3073 – 3160: Board is reporting slip errors. Aux Data shows the last reported<br />

slip count.<br />

o. Error Type 3330: LAN Critical error; critical failure in the packet bus interface to the circuit<br />

pack. This failure may be due to an on-board or a packet bus fault.<br />

1. If the packet bus is alarmed, see PKT-BUS (Packet Bus) or PKT-INT (Packet Interface)<br />

for repair procedures.<br />

If the packet bus is not alarmed, clear the alarm and restore the board to the packet bus<br />

using:<br />

a. busyout board location<br />

b. reset board location<br />

c. test board location long clear<br />

d. release board location<br />

Communication Manager Release 5.0 Issue 4 January 2008 973

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

Saved successfully!

Ooh no, something went wrong!