Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1046 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Use release board to restore the trunks or ports on the TN767E DS1 Interface circuit pact to
the inservice state.
Table 359: Test #1215 Inject Single Bit Error Test
Error
Code
Test
Result
Description / Recommendation
ABRT Internal system error
1. Retry test ds1-loop location inject-single-bit-error at
1-minute intervals up to 5 times.
1015 ABRT Ports on the DS1 Interface circuit pack have not been busied out to
out-of-service.
1. Enter busyout board location to put all trunks or ports of the DS1
Interface circuit pack into the out-of-service state.
2. Retry the command.
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.
1 of 2