Avaya S8700 Maintenance Manual page 537

UDS1-BD (UDS1 Interface Circuit Pack)
w. Error Type 3330 — LAN Critical Error. A critical failure has been detected
in the Packet bus interface of the circuit pack. This failure may be due to
an on-board fault or a Packet bus fault. If the Packet bus is alarmed, see
''PKT-BUS (Packet Bus)'' on page 8-918
procedures.
This error isolates the board from the Packet bus and raises an alarm. If
the Packet bus is not alarmed, enter the commands busyout board
UUCSS, reset board UUCSS, test board UUCSS, release board
UUCSS. This should clear the alarm and restore the board to the Packet
bus.
If the problem persists, and there are no PKT-BUS alarms, then replace the
circuit pack.
x. Error Types 3585 to 3601 — For later releases of G3V4 and beyond, only
Error Type 3585 shows that this board is receiving misframes, and the AUX
Data shows the last misframe count reported.
y. Error Type 3840 — Not service-affecting. No action is required. These
errors are reported by the circuit pack when it receives a bad control
channel message from the switch. The auxiliary data identifies the
following error events:
Aux Data
4096
4097
4098
4099
4100
4101
z. Error Type 3841 — The UDS1 Interface circuit pack has detected a
transient hardware logic error (for example, program logic inconsistency).
This error will disappear when no faults are detected for 100 minutes. The
value in Aux Data indicates the type of hardware problem.
aa. Error Type 3842 — Bad Translation RAM Location Found Error. This error
is not service-affecting. No action is required. A Bad Translation RAM is
detected, but the call continues by using another translation location.
ab. Error Type 3843 — LAN Receive Parity Error. This error occurs when the
circuit pack detects 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.
See ''PKT-BUS (Packet Bus)'' on page 8-918
problem is isolated to this circuit pack or is caused by Packet bus faults.
555-233-142
Event
Bad major heading
Bad port number
Bad data
Bad sub-qualifier
State inconsistency
Bad logical link
for recommended repair
to determine whether the
Issue 1 May 2002 8-1233