Isolating and Repairing Packet-Bus Faults
Issue 1 May 2002
4-89
555-233-143
Packet Bus maintenance software
Packet Bus maintenance software involves the usual set of MO error conditions,
tests, and alarms. These are described in
‘‘PKT-BUS (Packet Bus)’’ on page
. Since an EPN’s packet-bus fault can cause every BRI/ASAI endpoint and
its associated port and circuit pack to report faults, be careful to prevent a flood of
error messages overloading the system and interfering with traffic on the TDM
bus. When such a failure occurs, circuit-pack maintenance is affected in the
following manner:
■
In-line errors for the following MOs that indicate possible packet-bus faults
are logged but not acted upon: BRI-BD, PGATE-BD, PDATA-BD,
UDS1-BD.
■
In-line errors for the following MOs that indicate possible packet-bus faults
are neither logged nor acted upon: BRI-PORT, ABRI-PORT, PGATE-PT,
PDATA-PT, ISDN-LNK.
■
All in-line errors for the following MOs are neither logged nor acted upon:
BRI-SET, BRI-DAT, ASAI-ADJ.
■
Circuit pack and port in-line errors that are not related to the packet bus, or
that indicate a circuit pack failure, are acted upon in the normal fashion.
■
Periodic and scheduled background maintenance is not affected.
■
Foreground maintenance (for example, commands executed from the
terminal) is not affected.
These interactions allow normal non-packet system traffic to continue unaffected,
and they reduce the number of entries into the error/alarm logs. If the packet bus
failure is caused by a failed circuit pack, errors against the circuit pack should
appear in the error/alarm logs as an aid for fault isolation. The above strategy is
implemented when:
■
In-line errors indicate a possible packet bus failure reported by two or more
packet circuit packs.
■
A packet-bus uncorrectable report is sent from the Maintenance/Test
packet-bus port (M/T-PKT).
When such a failure occurs, a PKT-BUS error is logged. See
for more detailed information.
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 ...
