Maintenance-Object Repair Procedures
555-233-143
8-680
Issue 1 May 2002
To isolate a problem, set the loop back first at the loop-back point LB 1, and then
at the loop-back point LB 2, see
. Place the loop
backs at as many points as your CSU capabilities will allow. Hard-wired loop
backs at the far end are not desirable, because the equalization-level adjustments
may cause problems.
Every part of this test is executed under firmware control and the result is sent
back to the maintenance software. The test is executed by sending digital data
through every DS1 channel on this DS1 facility.
This test is executed via the test ds1-facility UUCSSf external-loopback
command. It is not part of the long test sequence because it requires
modifications to the physical connectivity of the DS1 facility.
If there is only one DS1 facility available, system will not allow the last facility to be
busied out. In that case, the DS1 CONV circuit pack must be busied out before
executing this test.
For a standard-, duplex-, or high-reliability system (no PNC duplication), if there is
only one DS1 facility available, then this test can only be executed at the endpoint
that is closer to the media server relative to the neighbor DS1 CONV circuit pack
because of its impacts on the system control links. For a critical-reliability system
(PNC duplication) or for a system with multiple DS1 facilities, the test can be
executed at any DS1 CONV circuit pack.
If the test passes on a TN1654 DS1 facility, the round trip delay time will be
displayed 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. This measurement is taken on the last DS1
channel tested.
Figure 8-28.
Loopback Points for Test #799
LB 2
LB 1
DS1 Facility
DS1CONV
A
CSU A
Test starts here
CSU B
DS1CONV
B
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...