DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-1232UDS1-BD (UDS1 Interface Circuit Pack)
3
1950 ABORT Another loopback/span test is already executing on the DS1 board or the board
is in a network requested loopback mode (Line loopback or Payload loopback).
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 loopback or payload loopback mod e. Only one long-duration
loopback/span test can be active at a g iven time. Thus, if a loopback/span test
is already active, that test must be terminated via the
test ds1-loop UUCSS
end-loopback/span-test
command in order to execute this test.
1951 ABORT The CSU E quipment Loopback Test could not be executed because the 120A1
CSU Module or the 401A T1 Sync Splitter was not physically installed.
Physically connect the 120A1 CSU Module or the 401A T1 Sync Splitter to the
TN464F board on the back of the port carrier.
2000 ABORT Response to the test was not received within the allowable time period. This
may be due to hyperactivity. Error type 1538 in the error log indicates
hyperactivity. The hyperactive circuit pack is out of service and one or more of
the following symptoms may be exhibited.
1. The UDS1-BD tests (such as test 138 and test 139) are aborting with error
code 2000.
2. The tests run on the ports of this circuit pack are returning a no board
result.
3. A busyout or a release command has no affect on the test results.
4. A list config command shows that the circuit pack and the p orts are
properly installed.
NOTE:
When hyperactivity occurs, the circuit pack is isolated from the system,
and all of the trunks for this circuit pack are placed into the out of service
state. The system will try to restore the circuit pack within 15 minutes.
When no faults are detected for 15 minutes, the UDS1 interface circuit
pack is restored to normal operation. All of the trunks for the UDS1
interface circuit pack are then returned to the in service state.
Hyperactivity is often caused by the associated facility. In such a case,
faults (such as slips, misframes, or blue alarms) would be entered in the
error log. In addition, many hardware errors would be logged against the
associated trunk circuits. If the facility is OK and the error occurs again
after 15 minutes, replace the circuit pack.
2100 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals for a maximum of 5 times.
Table 3-529. TEST #1210 CSU Equipment Loopback Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page