Maintenance-Object Repair Procedures
555-233-143
8-646 Issue 1 May 2002
Table 8-258. Test #1213 Far CSU Loop-Back Test
Error
Code
Tes t
Result Description / Recommendation
ABORT Internal system error
1. Retry test ds1-loop UUCSS far-csu-loopback-test-begin at 1-minute
intervals up to 5 times.
1005 ABORT Far CSU Loopback test cannot be executed in the current configuration. To
run this, the TN767E (or higher-suffixed) DS1 must be administered for
24-channel operation. The
Bit Rate field on the DS1 circuit pack
administration form must be set to “1.544” for 24-channel operation.
1015 ABORT Ports on the DS1 Interface circuit pack have not been busied out to
out-of-service.
1. Enter the busyout board UUCSS command to put all trunks or ports of the
DS1 Interface circuit pack into the out-of-service state.
2. Retry the command.
1039 ABORT The DS1 Interface circuit pack is providing timing for the system. Executing
this test could cause major system disruption.
If the DS1 Interface circuit pack needs to be tested, set the synchronization
reference to another DS1 Interface circuit pack or to the Tone-Clock circuit via
the following command sequence:
1. Issue the disable synchronization-switch command.
2. Next, issue the set synchronization UUCSS command.
3. Lastly, issue the enable synchronization-switch command.
1950 ABORT Another loop-back/span test is already executing on the DS1 board or the
board is in a network requested loop-back mode (Line loop back or Payload
loop back). The hardware error log will indicate whether a Customer Loopback
Jack test, Far CSU Loopback test, or the One-Way Span test is executing or if
the board is in line loop-back or payload loop-back mode. Only one
long-duration loop-back/span test can be active at a given time. Thus, if a
loop-back/span test is already active, that test must be deactivated via the test
ds1-loop UUCSS end-loopback/span-test command in order to execute this
test.
ABORT Internal system error
2100 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
Continued on next page