Filter
Top Products
DS1-BD (DS1 Interface Circuit Pack)
Issue 1 June 2005 1007
When the Red alarm is cleared, the DS1 Interface circuit pack will stop transmitting the Yellow
alarm to the remote DS1 endpoint. The maintenance software restores all trunks of the DS1
Interface circuit pack to the service state before the Red alarm occurs.
Loss of Multiframe Alarm: If the DS1 Interface circuit pack is administered using DMI-BOS
signaling, the DS1 Interface circuit pack raises a Loss of Multiframe Alarm (LMA) when it cannot
interpret the incoming signaling bits to synchronize to the multiframe pattern received in the 24
th
channel. Once DS1 Interface circuit pack detects an LMA, the circuit pack will transmit a
Remote Multiframe Alarm (RMA) to the remote DS1 endpoint. Maintenance software handles
both Red alarm and LMA alarm(s) using the same mechanism.
Table 346: Test #140 Red Alarm Inquiry Test
Error
Code
Test
Result
Description / Recommendation
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 has no affect on the test results.
● 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 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 3