Isolating and Repairing Packet-Bus Faults
Issue 1 May 2002
4-99555-233-143
Packet Bus Fault Isolation Flowchart
Figure 4-45 on page 4-100 shows the steps to be taken for isolating and resolving
a packet-bus problem. The order of examining maintenance objects (MOs) can
be determined by assessing how wide-spread the failure is. For example, since
every ISDN-BRI device communicates with the TN2312 IPSI circuit pack’s Packet
Interface circuit, its MO should be examined early in the sequence On the other
hand, a failure of an EPN’s TN570 circuit pack may cause an ISDN-BRI failure in
one EPN, but not in another.
Whenever the flowchart refers to an MO’s repair procedure, remember that the
repair procedure for that MO may, in turn, refer to another MO’s procedure. The
flowchart tries to coordinate these procedures so that (if a packet-bus problem is
not resolved by the first set of repair procedures) a logical flow is maintained.
However, some packet-bus faults can lead to a somewhat haphazard referencing
of the various MO procedures — resulting in either repetitive or unnecessary
steps. Should this occur, return to the flowchart at the step that follows the
reference to Chapter 8, ‘‘Maintenance-Object Repair Procedures’’, and continue
from there. The following status commands can also help diagnose packet-bus
problems, especially when logged in remote:
status port-network P status ipserver-interface
status pnc status packet-interface
status station status bri-port
status link status data-module
status sp-link status pms-link
status journal-link status cdr-link
To Next Page
Loading...
