Demand test descriptions and error codes - Avaya Support

Table 454: Far-End Internal Loopback Test (#797) 3 of 3
Error
Code
Test
Result
Description / Recommendation
Far-End Internal Loopback Test (#797)
FAIL Far-End Internal loopback failed. A problem exists between DS1
converter A and DS1 converter B’s internal interface for the DS1 facility
See Figure 109: Far-End Internal Loopback Test Configuration.
1. Enter display errors and follow the associated repair
procedures for any on-board DS1C-BD (DS1 Converter Circuit
Pack) errors on this DS1 converter circuit pack and the DS1
converter circuit pack at the other end of the DS1 converter
complex.
2. If the network is used instead of private T1 lines, verify that the DS1
facility and the network are using the same Line Coding. For TN574
boards and TN1654 boards in T1 mode, also verify that the
Framing Mode used is the same. Enter list fiber-link and
display fiber-link to check the values for this DS1 facility.
Contact T1 Network Service to check the modes used by the
network. See Line Coding and Framing Mode for details on how
these options apply to the TN574 and TN1654 DS1 converter
boards.
3. Isolate the problem by running the Near-End External Loopback
test (#799) with test ds1-facility location
external-loopback, first at this end and then at the other end of
the DS1 converter complex. Set up loopbacks at different points as
shown in the description diagram for Test #799, and follow repair
procedures described for Near-End External Loopback Test (#799).
4. If the problem could not be found by near-end external loopback
tests, the fault should be between the CSU A and the CSU B.
Contact T1 Network Service to resolve the problem. Also see the
repair procedures for Error Type 1025 (loss of frame alignment) for
DS1C-BD (DS1 Converter Circuit Pack).
Any PASS Transmission through the path of the loopback is successful. TN1654 DS1
facilities will display the round trip delay time in milliseconds in the Error
Code field. The round trip delay time is defined as the length of time in
milliseconds it takes for the firmware to receive the test pattern after it has
been sent.
3 of 3
Issue 5 May 2009 1515