Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-1510UDS1-BD (UDS1 Interface Circuit Pack)
10
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 ports are
properly installed.
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.
2. If the test continues to abort, escalate the problem.
2 FAIL The test failed because it was not set up properly. The UDS1 pack could
not successfully put the far-end CSU into loopback mode.
1. Rerun the test ds1-loop PCSS far-csu-loopback-test-begin
command.
2. If the test continues to fail, the problem could be with the TN464F
board, the CPE loopback jack equipment, or somewhere between.
Run the test ds1-loop PCSS cpe-loopback-jack-test-begin
command to determine if the CPE loopback jack loopback test is
successful. If a CPE loopback jack device is not being used, issue the
test ds1-loop PCSS ds1/csu-loopback-tests command instead. If
the closer loopback test fails, follow the maintenance strategy that is
associated with that test; otherwise, escalate the problem.
Table 10-507. TEST #1213 Far CSU Loopback Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page