Avaya S8700 Maintenance Manual page 165

Isolating and Repairing Packet-Bus Faults
The analog trunk testing functions are discussed in the following sections in
Chapter 8, ''Maintenance-Object Repair
''TIE-TRK (Analog Tie Trunk)'' on page 8-1638
''DID-TRK (Direct Inward Dial Trunk)'' on page 8-515
''AUX-TRK (Auxiliary Trunk)'' on page 8-310
NOTE:
Every Maintenance/Test circuit pack must be of TN771D vintage or later.
TN771D Packet Functions
The Maintenance/Test packet-bus port (M/T-PKT) provides the packet-bus testing
and reconfiguration capabilities. When the port is in service, it continuously
monitors the packet bus for faults and fault recoveries, and reports results to
PKT-BUS maintenance.
The amber LED on the TN771D Maintenance/Test circuit pack provides a visual
indication of the state of the packet bus:
Flashing
On steady
Off
NOTE:
It takes 5 to 10 seconds for the LED to respond to a change in the state of
the packet bus.
During normal switch operation, the Maintenance/Test circuit pack provides visual
feedback of the packet-bus state. When in stand-alone mode (see next section),
these visual indications are still present, but the packet bus is never reconfigured.
The amber LED either blinks, or is off.
555-233-143
Flashing of the amber LED once per second indicates that there are too
many faults for the Maintenance/Test packet-bus port to recover by
swapping leads. The packet bus may be unusable. If the failures
detected are open lead failures, the packet bus may still be operating.
The Maintenance/Test packet-bus port has swapped leads on the packet
bus to correct a fault. The packet bus is still operating. Or, one of the
other ports on the Maintenance/Test circuit pack is in use.
NOTE:
First busy out the Maintenance/Test circuit pack's ports not
used for packet-bus testing before using this circuit pack to
help resolve packet-bus faults. This is done by entering
busyout port UUCSS01, busyout portUUCSSl02, and
busyout port UUCSS03. Be sure to release these ports
when the process is completed.
There is no packet-bus fault present.
Procedures'':
Issue 1 May 2002 4-91