Filter
Top Products
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Object Repair Procedures
Page 10-1082PKT-BUS (Packet Bus)
10
ASAI-ADJ). These interactions are discussed in the "Circuit Packs That Use the
Packet Bus" section of Chapter 9, ‘‘
Packet Bus Fault Isolation and Correction’’.
The following list summarizes some of the important points to consider when
working with the Packet Bus.
■ The Maintenance/Test circuit pack (TN771) is a critical tool for isolating
Packet Bus faults. This circuit pack is present in each port network of a
high or critical reliability system that is using the Packet Bus. In a standard
system, the circuit pack may be included as a customer option. If a TN771
is not present, one must be taken to the customer site to allow for
proper fault isolation. (A determination as to whether a TN771 circuit pack
is in the system is made by entering the list configuration command.)
Use of the Maintenance/Test Packet Bus port facilities is described under
"The Maintenance/Test Circuit Pack (TN771)" in Chapter 9, ‘‘
Packet Bus
Fault Isolation and Correction’’. Also, in the same chapter, the section
entitled "Special Precaution Concerning the TN771" describes other
circumstances when a TN771 must be taken to the customer site.
■ Certain catastrophic Packet Bus failures have an effect on Packet circuit
pack, port, and endpoint maintenance. The following list summarizes the
impact of such failures in this regard.
■ 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 errors
are neither placed into the error log nor acted upon.
■ Circuit pack and port in-line errors that are not relevant to the
Packet Bus or that indicated 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.
The actions in the previous list serve to reduce the system load, which
could become excessive if too many maintenance objects are affected by
a Packet Bus failure. However, such an excessive load should in no way
impede the isolation and the correction of the faults.
When the actions in the list are implemented, Error Type 3329 is logged
against PKT-BUS, and a Warning alarm is raised (although other Packet
Bus errors in many cases raise more severe alarms, thereby overriding the
Warning alarm).