Справочник Пользователя для Lucent Technologies R5SI
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Packet Bus Fault Isolation and Correction
Page 9-8
Maintenance of the Packet Bus
9
with a large number of Digital/Analog/Hybrid sets and a small number of
ISDN-BRI sets would probably not consider the Packet Bus failure a catastrophic
problem.) The only way a Packet Bus failure can affect TDM traffic is via possible
impact on system response time in a large switch due to ISDN-BRI endpoint
maintenance running. This should rarely happen because the Packet Bus
maintenance software is able to prevent this impact for most Packet Bus faults
(see the next section).
ISDN-BRI sets would probably not consider the Packet Bus failure a catastrophic
problem.) The only way a Packet Bus failure can affect TDM traffic is via possible
impact on system response time in a large switch due to ISDN-BRI endpoint
maintenance running. This should rarely happen because the Packet Bus
maintenance software is able to prevent this impact for most Packet Bus faults
(see the next section).
!
CAUTION:
Since the correction procedures and some of the fault isolation procedures
for the Packet Bus are highly destructive to service throughout the system
(inasmuch as the procedures primarily involve removing circuit packs),
particular attention must be paid to nondestructive fault isolation. Also, for
the same reason, the time taken with destructive procedures must be
minimized. This is the major reason that maintenance of the Packet Bus and
of the Packet maintenance objects is described in such detail.
for the Packet Bus are highly destructive to service throughout the system
(inasmuch as the procedures primarily involve removing circuit packs),
particular attention must be paid to nondestructive fault isolation. Also, for
the same reason, the time taken with destructive procedures must be
minimized. This is the major reason that maintenance of the Packet Bus and
of the Packet maintenance objects is described in such detail.
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 the
PKT-BUS section in
tests, and alarms relevant to Packet Bus faults. These are described in the
PKT-BUS section in
, and
they are similar in design to the maintenance strategy for most maintenance
objects.
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:
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.
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
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.
or that indicate a circuit pack failure, are acted upon in the normal fashion.
■
Normal background maintenance (periodic and scheduled) is not
affected.
affected.
■
Foreground maintenance (for example, commands executed on the
Manager I terminal) are not affected.
Manager I terminal) are not affected.