Blue Alarm Inquiry Test (#139) - Avaya G350 Maintenance Manual

Avaya Communication Manager controlled maintenance
MG-DS1 (DS1 Interface Media Module)
Table 109: TEST #138 Loss of Signal Alarm Inquiry Test 3 of 3
Error Test
Code Result
Any NO
BOARD

Blue Alarm Inquiry Test (#139)

The Blue Alarm is a signal sent by the remote DS1 endpoint when it is out-of-service. The Blue Alarm
Inquiry Test checks the blue alarm status of the remote DS1 endpoint.
When the MG-DS1 Interface Media Module detects a Blue Alarm signal from the remote DS1 endpoint,
the Media Module transmits a Yellow alarm to the remote DS1 endpoint and sends a BLUE ALARM
message to the maintenance software. When the Blue alarm is confirmed, the maintenance software
places all trunks or ports of the MG-DS1 Interface Media Module into the out-of-service state. The
inquiry test runs every 10 minutes until the Blue alarm is cleared.
The MG-DS1 Interface Media Module takes one second to recognize and report a Blue alarm and 16
seconds to recognize and report the resolution of a Blue alarm. When the Blue alarm is cleared, the MG-
DS1 Interface Media Module stops transmitting the Yellow alarm and places the trunks or ports back into
the service state before the Blue alarm occurs.
Line Loopback Alarm
The Line Loopback (LLB) is used by the remote DS1 endpoint to put the DS1 board into a loopback
mode. When the DS1 board is in the LLB mode, the arriving bit pattern is regenerated and sent back. The
Line Loopback (LLB) Alarm activates when the in-band activate LLB bit pattern arrives continuously for
5 seconds on the DS1 line. The LLB deactivates when the in-band deactivate LLB bit pattern arrives
continuously for 5 seconds on the DS1 line.
Since LLB is a maintenance condition rendering all DS0 channels unavailable for signaling or bearer
traffic, maintenance software treats this the same as a Blue Alarm.
190
Description/ Recommendation
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.
Maintenance of the Avaya G350 Media Gateway
3 of 3
June 2004