
Maintenance Object Repair Procedures
555-233-123
10-1658
Issue 4 May 2002
i. The circuit pack is has problems transmitting/receiving data to/from the
Packet Bus.
j. Error Type (2305, 3330): A critical failure in the Circuit Pack’s Packet Bus
interface. Possible causes include either a Packet Bus fault or an on-board
fault, for example, the board received a bad CRC or invalid DLCI. If the
Packet Bus is alarmed, refer to the “Maintenance Manual” section for
Packet Bus fault location and recommended repair procedures. The
number of ISDN circuit packs displaying this error increases the probability
of errors due to Packet Bus problems.
If there are no Packet Bus alarms, reset the circuit pack with the busyout
board PCSS and reset board PCSS commands. If the Circuit Pack
Restart Test (#594) passes, then the on-board circuitry is healthy. Retire
the alarm with the test board PCSS long clear command. If the Circuit
Pack Restart Test (#594) fails, replace the circuit pack.
k. The SPE software detects an excessive number of up-link messages from
the TN2185 board within a certain time period. To prevent the faulty board
from flooding the switch with data, the switch software takes the board out
of service and alarms it. The switch software also tells the Archangel to
ignore up-link messages from the board.
When the board is alarmed due to this error, the switch software
periodically puts the board back in service and tells the Archangel to
process up-link messages from the board. If the problem still exists, the
software takes the circuit pack out of service again. If the circuit pack does
not exhibit the problem for a certain time period, then maintenance
software resolves the alarm and the circuit pack is left in service.
l. The circuit pack received an inconsistent down-link message (a bad
header, port number, data, subqualifier, or logical link) over the Control
Channel.
1793
Parity errors are detected when transmitting data to the Packet Bus.
1794
Packet Bus transmit buffers overflow.
1795
Circuit pack cannot find end of frame when transmitting to Packet
Bus. Clear the alarm with: busyout board PCSS, reset board
PCSS, test board PCSS long clear, release board PCSS. If the
error recurs within 10 minutes, replace the circuit pack.
2306
Error in a received frame from the Packet Bus, most likely caused by
a packet bus problem, but may be due to a circuit pack fault. An
invalid Link Access Procedure Data (LAPD) frame error occurs if the
frame contains a bad Cyclical Redundancy Check (CRC). If bus
parity errors occur, run the LAN Receive Parity Error Counter Test
(#595) to determine if the condition has cleared. Refer to the
maintenance documentation to determine if the problem is isolated
to this circuit pack or is caused by Packet Bus faults.
Содержание Definity SI
Страница 1: ...0DLQWHQDQFH IRU YD D 1 7 6HUYHU 6 Volumes 1 2 and 3 555 233 123 Issue 4 May 2002...
Страница 62: ...Maintenance Architecture 555 233 123 1 26 Issue 4 May 2002...
Страница 92: ...Management Terminals 555 233 123 3 26 Issue 4 May 2002...
Страница 204: ...Routine Maintenance Procedures 555 233 123 5 100 Issue 4 May 2002...
Страница 250: ...LED Interpretation 555 233 123 7 10 Issue 4 May 2002...
Страница 2763: ...VC DSPPT Issue 4 May 2002 10 1977 555 233 123 Figure 10 107 VC Circuit Pack DSP Port Local TDM Loopback Test...
Страница 2776: ...Maintenance Object Repair Procedures 555 233 123 10 1990 Issue 4 May 2002 Figure 10 109 VC Circuit Pack Summer Port Loopback Test...
Страница 2804: ...Maintenance Object Repair Procedures 555 233 123 10 2018 Issue 4 May 2002...
Страница 2968: ...Index 555 233 123 IN 10 Issue 4 May 2002...