Skip to main content

Avaya IX Messaging RAM Critical Alarm

Jeremy Boilard

Problem Statement

Avaya IX Messaging IXM (Consolidated) reports a Major avIXAlmServRAMCritical alarm with alarm code ACT and description indicating memory usage became critical at 90%.

Impact

High memory utilization can indicate resource pressure on the Avaya IX Messaging server. If sustained, it may affect messaging service performance or stability and should be investigated promptly.

Alarm

avIXAlmServRAMCritical

Troubleshooting Steps

  1. Confirm the active alarm details in the monitoring dashboard, including device type, alarm severity, maintenance object, alarm code, and reported memory percentage.
  2. Check whether the alarm is still active or has cleared. If it has downgraded to avIXAlmServRAMWarning, continue monitoring until memory utilization returns to normal thresholds.
  3. Review current system memory utilization on the Avaya IX Messaging server using the supported operating system or platform monitoring tools.
  4. Identify any processes consuming unusually high memory and confirm whether they are expected Avaya IX Messaging services or unrelated system processes.
  5. Check for recent changes, scheduled jobs, backups, reporting tasks, or maintenance activity that could temporarily increase memory usage.
  6. If memory remains at or above the critical threshold, follow the approved operational procedure for the environment, such as restarting affected services or performing a controlled server reboot during an approved maintenance window.
  7. After any corrective action, verify that avIXAlmServRAMCritical is cleared from monitoring and that memory utilization remains below critical levels.
  8. If the alarm recurs or memory continues to rise, escalate to the Avaya application support team with the alarm details, current memory usage, process utilization, and recent-change information.

Resolution

In the reported occurrence, the Major avIXAlmServRAMCritical alarm cleared. Monitoring later showed avIXAlmServRAMWarning at 89%, indicating memory usage had dropped below the critical threshold but still required observation until fully normalized.