Avaya DEFINITY Server CSI Maintenance Manual page 1085

DS1-BD (DS1 Interface Circuit Pack)
Table 226. TEST #135 Internal Looparound Test — Continued
Error Test
Code Result
1015 ABORT Ports on DS1 Interface circuit pack have not been busied out.
1039 ABORT The DS1 Interface circuit pack is providing timing for the system. Therefore,
it cannot be reset without major system disruption.
2000 ABORT The test was aborted. 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.
2100 ABORT Could not allocate the necessary system resources to run this test.
555-233-119
Description/ Recommendation
1. Enter the busy-out board UUCSS command to put all trunks of the DS1
Interface circuit pack into out-of-service state.
2. Retry the command.
1. 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 pack via the following command sequence:
Issue the disable synchronization-switch command.
Next, issue the set synchronization UUCSS command.
Lastly, issue the enable synchronization-switch command.
1. The DS1-BD tests (such as Test 139 and Test 140) 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.
NOTE:
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 DS1
interface circuit pack is restored to normal operation. All of the trunks
for the DS1 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, escalate this problem.
1. Retry the command at 1-minute intervals for a maximum of 5 times.
Continued on next page
Issue 5 October 2002
1085