Demand test descriptions and error codes - Avaya Support

Table 487: One-Way Span Test (#1214) 2 of 3
Error
Code
Test
Result
Description / Recommendation
One-Way Span Test (#1214)
1005 ABORT One-Way Span test cot be executed in the current configuration. To run
this, the DS1 must be administered for 24-chel operation. The Bit Rate
field on the DS1 circuit pack administration screen must be set to 1.544 for
24-chel operation.
1015 ABORT Ports on the DS1 Interface circuit pack have not been busied out.
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.
1039 ABORT The DS1 Interface circuit pack is providing timing for the system. Executing
this test could cause major system disruption.
If the DS1 Interface circuit pack needs to be tested, set the
synchronization reference to another DS1 Interface circuit pack or to the
Tone-Clock circuit with the following command sequence:
1. disable synchronization-switch
2. set synchronization location
3. enable synchronization-switch
1950 ABORT Another loopback/span test is already running on the DS1 board, or the
board is in a network requested loopback mode (Line loopback or Payload
loopback). The error log will indicate whether a Customer Loopback Jack
test, Far CSU Loopback test, or the One-Way Span test is running or if the
board is in line loopback or payload loopback mode. Only one
long-duration loopback/span test can be active at a given time
If a loopback/span test is already active, that test must be deactivated with
test ds1-loop location end-loopback/span-test in order to
run this test.
2000 ABORT Response to the test was not received within the allowed time.
1. Check for board hyperactivity. See Hyperactive DS1/UDS1 Interface
Circuit Pack/Media Module.
2100 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL The test was run between a DS1 circuit pack and a DS1 media module,
which generates incompatible patterns.
2 of 3
Issue 5 May 2009 1593