Problem Statement
A Major alarm is generated on Avaya Communication Manager for maintenance object cmgRegistrationFault with alarm code ACT. The alarm indicates that a Media Gateway cannot register with any controllers in its controller list.
Impact
The affected Media Gateway may be unable to register to Avaya Communication Manager controllers. This can impact call processing or media gateway services for endpoints and trunks dependent on that gateway until registration is restored.
Alarm
cmgRegistrationFault, Alarm Code ACT, Major
Troubleshooting Steps
- From the Media Gateway Processor (MGP) CLI, verify the configured controller list with: show mgc list
- Confirm that the listed controller IP addresses match the expected Avaya S8700-series Server C-LAN or S8300 Server IP addresses for the environment.
- If the controller list is incorrect, enter configure mode on the MGP CLI and clear the existing list with: clear mgc list
- Reconfigure the correct controller list with: set mgc list <controller-ip-addresses>
- If the controller list is correct, investigate network connectivity between the Media Gateway and the configured controllers, including routing, VLAN, firewall, interface, and reachability issues.
- Verify that the primary controller is up and reachable.
- If the controller list is correct, network connectivity is confirmed, and the controller is available but the Media Gateway still does not register, reboot the Media Gateway during an approved maintenance window or following operational procedures.
- After corrective action, confirm that the alarm clears and that the Media Gateway is registered.
Resolution
In the referenced scenario, the cmgRegistrationFault alarm cleared shortly after being raised, indicating a transient registration issue. If the alarm persists or recurs, validate the MGP controller list, controller availability, and network connectivity, then reboot the Media Gateway if required.