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 by a defective circuit pack connected to the
backplane, by bent pins on the backplane, or by defective cables or terminators
that make up the packet bus. The first two faults cause shorts, while the third fault
causes either shorts or opens.
There are four procedures for correcting packet bus faults. Which 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 locate
faulty circuit packs or bent pins and these do not cause open faults.
■ If there are both shorts and opens, start with Procedure 4, and return to
Procedure 1 if shorts persist after the open leads are fixed.
!
CAUTION:
Packet bus fault isolation procedures involve removing circuit packs and
possibly disconnecting entire carriers These procedures are destructive.
Whenever possible, implement these procedures during hours of minimum
system use.
!
CAUTION:
To replace the following circuit packs, follow instructions in the appropriate
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 packet bus problem has been resolved,
the following conditions should all be met:
■ All faulty leads reported by the TN771D standalone mode should no
longer be reported.
■ All alarms against the packet bus and packet circuit packs have been
resolved.
■ All ISDN-BRI stations and data modules and all relevant ASAI, System
Port, and Packet Gateway supported adjuncts are in service.
