Avaya 03-300430 User Manual

The list measurements ds1 summary command shows the number of bit errors detected 

(Loopback/Span Test Bit-Error Count field). Injecting this single bit error should increment the 
bit error count of the loopback/span test by one.

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 UDS1 Interface circuit pack have not been busied out.

1. Enter busyout board location to put each trunk or port of the 

UDS1 Interface circuit pack into the out-of-service state.

2. Retry the command.

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.

1. The UDS1-BD tests (such as Tests #138 and #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 effect on the test results.
4. A list config 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 UDS1 interface circuit pack is restored to 

normal operation. Every trunk for the UDS1 interface circuit pack 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, replace the circuit pack.

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.

 1 of 2