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-1498UDS1-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.
FAIL UDS1 Interface circuit pack failed the CSU Equipment Loopback Test.
1. Retry the
test ds1-loop PCSS ds1/csu-loopback-tests
command.
2. If the ELB test continues to fail, then either the TN464F board, the CSU
Module, or the I/O cable between the backplane and the CSU module
(or any combination thereof) has failed. Attempt to isolate the problem
to one of these areas. Begin by replacing the CSU Module and
running the
test ds1-loop PCSS ds1/csu-loopback-tests
command
again.
3. If the ELB test continues to fail, then replace the TN464F board and
run the
test ds1-loop PCSS ds1/csu-loopback-tests
command again.
4. If the ELB test continues to fail, the problem could be in the I/O cable
between the backplane and the CSU module.
Table 10-504. TEST #1210 CSU Equipment Loopback Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page