Problem Statement
Avaya Communication Manager (Core) generated a Major MG-SYNC alarm from the CommunicaMgr process. The alarm appeared with maintenance object avCmAlmMgSyncMajor, notification identifier avCmAlmNotifications 5280, alarm code ACT, and an affected equipment number. A related Minor NR-REG alarm may also be present on another media gateway or equipment number.
Impact
A Major MG-SYNC alarm can indicate a media gateway synchronization or registration-related condition that may affect gateway health monitoring. In the observed case, service impact was not confirmed because all media gateways were registered and all H.248 links were up during validation.
Alarm
avCmAlmMgSyncMajor
Troubleshooting Steps
- Log in to Avaya Communication Manager using an authorized administration interface.
- Run the command: status media-gateways
- Review the ALARM SUMMARY section and confirm whether Major alarms are still present.
- Review the H.248 LINK SUMMARY section and confirm Links Down is 0 and expected links are up.
- Review the GATEWAY STATUS table for the affected media gateway or equipment number. Confirm the Lk field shows up.
- Check whether the affected media gateway has active Major or Minor alarm counts in the Mj and Mn columns.
- If a related NR-REG alarm is present, verify that the relevant media gateway is registered and that its link status is up.
- If all media gateways are registered, all expected links are up, and Major alarm count is 0, treat the MG-SYNC Major condition as cleared and continue monitoring.
- If the affected gateway link is down, registration is missing, or Major alarms remain active, continue normal Avaya media gateway troubleshooting for network reachability, H.248 connectivity, gateway health, and Communication Manager alarm details.
Resolution
Validation with status media-gateways showed Major: 0, Links Down: 0, all listed media gateway links in up state, and all media gateways registered. No active MG-SYNC Major condition remained. Any remaining minor or warning alarms should be reviewed separately according to their maintenance object and affected gateway.