DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Alarms, Errors, and Troubleshooting
5-102Packet Bus Fault Isolation and Repair
5
Troubleshooting Procedures
Packet bus faults are usually caused b y a defective circ uit pack connected to the
backplane, b y bent pins on the backp lane, or by defective cab les or terminators
that make up the packet b us. The first two faults cause shorts, while the third fault
causes either shorts or opens.
There are four procedures for correcti ng packet bus faults. Whic h are used
depends on the nature of the fault . For example:
■If the Maintenance/Test packet bus port is activated, and if there is an
indication of open leads on the packet bus from status port-network or
Test #572, go directly to Procedure 4. Procedures 1 through 3 try to loc ate
faulty circuit pac ks or bent pins and these d o not cause open faults.
■If there are both shorts and opens, s tart with Procedure 4, and return to
Procedure 1 if shorts persist after the op en leads are fixed.
!CAUTION:
Packet bus fault isolation proc edures involve removing circuit p acks and
possibly disc onnecting entire carriers These p rocedures are destructi ve.
Whenever possible, implement these p rocedures during ho urs of minimum
system use.
!CAUTION:
To replace the following circuit pac ks, follow instructions in the app ropriate
sections: Tone-Clock (
‘‘TONE-BD (Tone-Clock Circuit Pack)’’
), Expansion
Interface (
‘‘EXP-INTF (Expansion Interface Circuit Pack)’’
), Packet Interface
(
‘‘Replacing SPE Circuit Packs’’
).
When the procedure asks whether the pa cket bus problem has b een resolved,
the following conditio ns should all be met:
■All faulty leads reported by the TN771D standalone mode should no
longer be reported .
■All alarms against the pac ket bus and pack et circuit packs have b een
resolved.
■All ISDN-BRI stations and data modules and al l relevant ASAI, System
Port, and Packet Gateway supporte d adjuncts are in service.