BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack)
Issue 1 May 2002
8-325
555-233-143
i. These error types are reported when the following errors are detected:
j. These errors indicate that the circuit pack is having problems transmitting
data to the packet bus.
1537
Frame overrun at packet-bus interface. This condition may be
caused by an on-board fault or by faulty data received on one of the
circuit pack’s external ports. If any of the ports on this circuit pack
are alarmed, refer to the repair procedures for those MOs.
1538
Circuit packet is hyperactive; that is, it is flooding the switch with
messages sent over the control channel. The circuit pack is taken
out-of-service when a threshold number of these errors is reported
to the switch. Clear the alarm via the following commands:
busyout board UUCSS, reset board UUCSS, test board UUCSS
long clear, release board UUCSS. If the error recurs within 10
minutes, then replace the circuit pack.
1793
Parity errors are detected when transmitting data to the packet bus.
1794
Overflow of packet-bus transmit buffers has occurred.
1795
Circuit pack cannot find end of frame when transmitting to packet
bus. Clear the alarm via the following commands: busyout board
UUCSS, reset board UUCSS, test board UUCSS long clear,
release board UUCSS. If the error recurs within 10 minutes, then
replace the circuit pack.
2306
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. An invalid Link Access Procedure Data (LAP-D) frame error
occurs if the frame contains a bad cyclical redundancy check
(CRC), is greater than the maximum length, or violates the link level
protocol. When bus parity errors are reported, the LANBIC Receive
Parity Error Counter test (#595) should be performed to determine
whether the condition had cleared. See
to determine whether the problem is
isolated to this circuit pack or is caused by packet-bus faults.
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...