Avaya Communication Manager controlled maintenance
MG-DS1 (DS1 Interface Media Module)
Maintenance of the Avaya G350 Media Gateway
197
June 2004
Yellow Alarm Inquiry Test (#141)
Receiving a Yellow alarm from a remote DS1 endpoint indicates that the remote DS1 endpoint has an
out-of-frame condition. The Yellow Alarm Inquiry Test is used to determine whether the remote DS1
endpoint is transmitting a Yellow alarm. The MG-DS1 Interface Media Module takes 500 msec to
recognize and report a Yellow alarm and 500 msec to recognize and report that a Yellow alarm condition
is cleared.
When the MM-DS1 Interface Media Module detects a Yellow alarm from the remote DS1 endpoint, it
sends a YELLOW-ALARM uplink message to the maintenance software. After the maintenance
software receives the YELLOW-ALARM message, the Yellow Alarm Inquiry Test is run to confirm the
Yellow alarm. Once the Yellow alarm is confirmed, the maintenance software places all trunks or ports on
the Media Module into the out-of-service state. The Inquiry Test runs every 10 minutes until the Yellow
alarm is cleared.
When the Yellow alarm is cleared, the maintenance software restores all trunks or ports on the MG-DS1
Interface Media Module back to their previous service state before the Yellow alarm was raised.
This Yellow alarm corresponds to the yellow F2 state documented in CCITT Recommendation I.431.
Remote Multiframe Alarm
Remote Multiframe Alarm (RMA) indicates that the remote DS1 endpoint is in a Loss of Multiframe
Alarm condition while the MG-DS1 Interface Media Module is administered using the DMI-BOS
common channel signaling. The RMA is handled as a Yellow alarm.
PASS
No Red alarm is detected on the MG-DS1 Interface Media Module.
Any
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
Ensure that the board translations are correct. Execute the
add ds1
GGGVS
command to administer the MG-DS1 interface if it is not already
administered.
If the board was already administered correctly, check the error log to
determine whether the board is hyperactive. If this is the case, the board is
shut down. Reseating the board will re-initialize the board.
If the board was found to be correctly inserted in step 1, then use the
busyout board
command.
Use the
reset board
command.
Use the
release busy board
command.
Use the
test board long
command.
This should re-establish the linkage between the internal ID and the port.
Table 111: TEST #140 Red Alarm Inquiry Test 4 of 4
Error
Code
Test
Result
Description/ Recommendation
4 of 4
Summary of Contents for Media Gateway G350
Page 1: ...Maintenance of the Avaya G350 Media Gateway 555 245 105 Issue 3 June 2004 ...
Page 16: ...About this book Sending us comments 16 Maintenance of the Avaya G350 Media Gateway June 2004 ...
Page 284: ...Monitoring Extended keepalive 284 Maintenance of the Avaya G350 Media Gateway June 2004 ...