Skip to main content

Avaya CM MG-ANA ACT Alarm

Jeremy Boilard

Problem Statement

Avaya Communication Manager reports a Minor MG-ANA alarm with alarm code ACT against an analog media module or virtual analog media module slot. Running a long board test may show MG-ANA test 52 passing while other MG-ANA or AN-LN-PT tests abort, and some ports may return NO BOARD.

Impact

Analog line or trunk ports associated with the affected media module may be unavailable, incorrectly administered, or inconsistent with the physical or virtual module inventory. The impact can be limited to ports on the affected slot, but should be validated before clearing the alarm.

Alarm

Minor MG-ANA ACT

Troubleshooting Steps

  1. Confirm the active alarm details in Avaya Communication Manager and note the affected board or slot identifier without using customer-specific identifiers in documentation.
  2. Run `test board <slot> long` for the affected analog media module slot.
  3. Review the TEST RESULTS for MG-ANA and AN-LN-PT entries. In the referenced case, MG-ANA test 52 passed, while other MG-ANA and AN-LN-PT tests returned ABORT with error codes 1412, 1392, or 2000, and some ports returned NO BOARD.
  4. Check whether the issue appeared after a recent equipment move, gateway move, media module replacement, or administration change.
  5. Compare the administered media module type with the expected physical or virtual hardware. MG-ANA supports analog modules such as MM711, MM714, MM716, TIM508, TIM514, TIM516, TIM518, VMM_ANA, and VMM_42ANA. Investigate any conflict between the administered analog media module and another module type shown for the same slot.
  6. Review the port administration for the affected range. If ports are marked as assigned or administered but the board test reports NO BOARD, verify whether those ports should remain administered on that slot.
  7. If administration does not match the installed or intended module, correct the board or port administration according to the site design and change-control process.
  8. After corrections or hardware verification, rerun `test board <slot> long` and confirm whether the MG-ANA alarm clears from the alarm dashboard.
  9. If the alarm remains and the administered module matches the physical hardware, escalate to Avaya support or dispatch field support to inspect the media gateway slot, module seating, cabling, and hardware state.

Resolution

A confirmed final fix was not documented in the source ticket. The investigation indicated a likely media module administration conflict after a recent move, with ports assigned on the affected analog slot and test results showing ABORT or NO BOARD. The reusable resolution path is to reconcile the administered media module and port assignments with the actual hardware or intended design, then retest the board and verify alarm clearance.