PKT-BUS (Packet Bus)
Issue 4 May 2002
10-1263555-233-123
e. In-line errors indicating possible Packet Bus failures are placed into
the error log, but are not acted upon. Circuit pack maintenance
objects thus affected include:
■ BRI-BD
■ LGATE-BD
■ ASAI-BD
■ TBRI-BD
■ PGATE-BD
■ CLAN-BD
■ UDS1-BD
■ MAPD-BD
■ MEDPRO
f. In-line errors indicating possible Packet Bus failures are neither
placed into the error log nor acted upon. Circuit pack port and
endpoint maintenance objects thus affected include:
■ BRI-PORT, ABRI-PORT, BRI-SET, TBRI-PT
■ ASAI-ADJ, ASAI-PT, ASAI-EPT
■ ATT-PORT, ATT-ADJ, ATTE-PT, ATTE-AJ
■ LGATE-PT, LGATE-AJ
■ PGATE-PT
■ ETH-PT
■ PPP-PT
■ MEDPRO-RES
g. Circuit pack and port in-line errors that are not relevant to the Packet
Bus or that indicate a circuit pack failure are acted upon in the
normal fashion.
h. Normal background maintenance (periodic and scheduled) is not
affected.
i. Foreground maintenance (for example, commands executed on the
Manager I terminal) is 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).