Avaya S8700 Maintenance Manual page 37

MAPD-BD (MAPD Interface Circuit Pack TN802)
n. Error Type 3330—LAN Critical error; critical failure in the packet-bus
interface to the circuit pack. This failure may be due to an on-board or a
packet-bus fault.
1. If the packet bus is alarmed, see
2. If the problem persists, and there are no PKT-BUS alarms, then
o. Error Type 3585 - 3601—The board received misframe errors; the Aux
Data shows the last reported misframe count.
p. Error Type 3840—The circuit pack received a bad control channel
message from the switch. This error is not service-affecting, and requires
no action. The Aux Data describes the following error events:
4096
4097
4098
4099
4100
4101
q. Error Type 3841—The circuit pack detected a transient hardware logic
error (for example, program logic inconsistency). This error resolves when
no faults are detected for 100 minutes. The value in Aux Data field (4358)
indicates the type of hardware problem.
r. Error Type 3842—Bad Translation RAM Location Found error; the call
continues by using another translation location. This error is not
service-affecting and requires no action.
s. Error Type 3843—LAN Receive Parity error; the circuit pack detected an
error in a received frame from the packet bus. These errors are most likely
caused by a packet-bus problem, but may be due to a circuit-pack fault.
1. Determine whether the problem is isolated to this circuit pack or the
555-233-142
recommended repair procedures.
If not, clear the alarm and restore the board to the packet bus using
the following command sequence:
a. busyout board UUCSS
b. reset board UUCSS
c. test board UUCSS clear
d. release board UUCSS
replace the circuit pack. See
before removing the circuit pack.
Bad major heading
Bad port number
Bad data
Bad sub-qualifier
State inconsistency
Bad logical link
problem is caused by packet-bus faults (see the PKT-BUS MO).
''PKT-BUS (Packet Bus)''
''Shutting Down NT on the TN802''
Issue 1 May 2002
for
8-733