Avaya 03-300430 Benutzerhandbuch
MG-DS1 (DS1 Interface Media Module)
Issue 1 June 2005
1615
Loss of Multiframe Alarm
If the MM710 Interface Media Module is administered using DMI-BOS signaling, the MM710
Interface Media Module raises a Loss of Multiframe Alarm (LMA) when it cannot interpret the
incoming signaling bits to synchronize to the multiframe pattern received in the 24th channel.
Once the MM710 Interface Media Module detects an LMA, the Media Module transmits a
Remote Multiframe Alarm (RMA) to the remote DS1 endpoint. Maintenance software handles
both Red alarm and LMA alarm(s) using the same mechanism.
Interface Media Module raises a Loss of Multiframe Alarm (LMA) when it cannot interpret the
incoming signaling bits to synchronize to the multiframe pattern received in the 24th channel.
Once the MM710 Interface Media Module detects an LMA, the Media Module transmits 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 594: TEST #140 Red Alarm Inquiry Test
Error
Code
Code
Test
Result
Result
Description/ Recommendation
ABRT
Internal system error
1. Retry the command at 1-minute intervals a maximum of 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 Media Module is out of service
and one or more of the following symptoms may be exhibited:
●
The MG-DS1 tests (such as Test #138 and Test #139) are aborting
with Error Code 2000.
with Error Code 2000.
●
The tests run on the ports of this Media Module are returning a no
board result.
board result.
●
A busyout or a release command has no affect on the test
results.
●
A list config command shows that the Media Module and the
ports are properly installed.
When hyperactivity occurs, the Media Module is isolated from the
system, and all of the trunks for this Media Module are placed into the
out of service state. The system will try to restore the Media Module
within 15 minutes. When no faults are detected for 15 minutes, the
MM710 interface Media Module is restored to normal operation. All of
the trunks for the MM710 interface Media Module 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.
system, and all of the trunks for this Media Module are placed into the
out of service state. The system will try to restore the Media Module
within 15 minutes. When no faults are detected for 15 minutes, the
MM710 interface Media Module is restored to normal operation. All of
the trunks for the MM710 interface Media Module 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.
1. If the facility is OK and the error occurs again after 15 minutes,
replace the Media Module.
1 of 4