Avaya MCC1 Maintenance Procedures page 251

Packet bus maintenance software
Packet Bus maintenance software involves the traditional set of error conditions, tests, and alarms
relevant to Packet Bus faults. These are described in
Alarms Reference (555-245-102) and they are similar in design to the maintenance strategy for most
maintenance objects.
In addition, because a Packet Bus failure can cause all BRI/ASAI endpoints in the affected Port Network
(and their associated ports and circuit packs) to report failures, special care must be taken to ensure that
the flood of error messages from the affected maintenance objects does not overload the system and
interfere with TDM Bus traffic. When such a failure occurs, maintenance of Packet circuit packs is
affected in the following manner:
• ISDN-BRI circuit pack (BRI-BD) in-line errors indicating possible Packet Bus failures are placed
into the error log, but are not acted upon.
• ISDN-BRI port (BRI-PORT, ABRI-PORT) in-line errors indicating possible Packet Bus failures
are neither placed into the error log nor acted upon.
• ISDN-BRI endpoint (BRI-SET, BRI-DAT, ASAI-ADJ) in-line error are neither placed into the
error log nor acted upon.
• 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.
• Normal background maintenance (periodic and scheduled) is not affected.
• Foreground maintenance (for example, commands executed on the Manager I terminal) are not
affected.
These interactions allow normal, non-Packet, system traffic to continue unaffected, and they reduce the
number of extraneous entries into the Error/Alarm Logs. If the Packet Bus failure is caused by a failed
circuit pack, the circuit pack should appear in the Error/Alarm Logs, which aids in fault isolation.
The following events indicate a Packet Bus failure that requires the actions in the previous paragraph to
occur:
• In-line errors that indicate a possible Packet Bus failure reported by two or more Packet circuit
packs
• Packet Bus Uncorrectable report from the Maintenance/Test Packet Bus port (M/T-PKT)
• Packet Bus Interface Failure from the Packet Control (PKT-INT)
If such a failure occurs, this information is available in the Error Log entry for PKT-BUS. Refer to
BUS (Packet Bus - S8100)
information.
Fault correction procedure overview
This section gives an overview of the procedures used to (1) isolate the cause of Packet Bus faults and to
(2) correct the Packet Bus faults. These procedures are applicable to High and Critical Reliability
systems, and they are detailed fully later in this chapter:
1 The first procedure attempts to determine if a circuit pack that interfaces to the Packet Bus is the
cause of the Packet Bus problem. The error and alarm logs are examined for entries for these
circuit packs, and the normal maintenance procedures for those circuit packs are attempted.
Maintenance Procedures
December 2003
PKT-BUS (Packet Bus - S8100)
section in Maintenance Alarms Reference (555-245-102) for more detailed
Packet and serial bus maintenance
S8100 packet bus fault isolation and repair
in Maintenance
PKT-
251