DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-1183UDS1-BD (UDS1 Interface Circuit Pack)
3
v. LAN Critical Error. A critical failure has b een detected in the Pack et Bus
interface of the circuit p ack. This failure may be due to an on-board fault or
a Packet Bus fault. If the Packet Bus is alarmed, refer to the PKT-BUS
Maintenance documentatio n for recommended repair p rocedures.
This error will isolate the board from the Packet Bus and rais e an alarm. If
the Packet Bus is not alarmed, enter the following commands: busyout
board UUCSS, reset board UUCSS, test board UUCSS, release board
UUCSS. This should clear the alarm and restore the b oard to the Packet
Bus.
If the problem persists, and there are no PKT-BUS alarms, then replace the
circuit pack.
w. For later releases of G3V4 and beyond, only error 3585 will sh ow that this
board is receiving misframes and the AUX data shows the last misframe
count that was reported.
x. These errors are not service-affecting. No ac tion is required. These errors
are reported by the c ircuit pack when it rec eives a bad control c hannel
message from the switch. The auxiliary data identifies the following error
events:
y. The UDS1 Interface circuit pac k has detected a transient hard ware logic
error (for example, program log ic inconsistency). This error will disap pear
when no faults are detected for 100 minutes. The value in Aux Data field
indicates the type of hard ware problem.
z. Bad Translation RAM Location Found Error. This error is not
service-affecting. No ac tion is required. A Bad Translation RAM is
detected, b ut the call continues by using another translation location.
aa. LAN Receive Parity Error. This error occurs when the circuit pac k detects
an error in a received frame from the Packet Bus. These errors are most
likely caused by a Pac ket Bus problem, but may b e due to a circuit p ack
fault.
Refer to the PKT-BUS Maintenance documentation to determine if the
problem is isolated to this c ircuit pack or if the p roblem is caused b y
Packet Bus faults.
4096 Bad major heading
4097 Bad port number
4098 Bad data
4099 Bad sub-qualifier
4100 State inconsistency
4101 Bad logical link