Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1040 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
1950 ABRT 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 test ds1-loop location end-loopback/span-test in order to
execute this test.
ABRT Internal system error
2100 ABRT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2000 ABRT 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.
● The DS1-BD tests (such as test 138 and test 139) are aborting with
error code 2000.
● The tests run on the ports of this circuit pack are returning a no board
result.
● A busyout or a release command has no affect on the test results.
● 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 its trunks 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 DS1 interface circuit pack is restored to normal operation. Every
DS1 interface trunk is 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, escalate this
problem.
2 FAIL The far CSU Loopback test was not set up properly. The DS1 Interface
circuit pack could not put the far-end CSU into loop-back mode.
Table 357: Test #1213 Far CSU Loop-Back Test (continued)
Error
Code
Test
Result
Description / Recommendation
2 of 3