Skip to main content

Avaya IXM CPU or RAM Warning Alarm

Jeremy Boilard

Problem Statement

Avaya IX Messaging IXM reports a Minor resource-utilization alarm such as avIXAlmServCPUWarning. The alarm description may indicate that traffic or workload does not match available CPU capacity. A related warning, avIXAlmServRAMWarning, may also be reported when memory utilization is high.

Impact

High CPU or memory utilization can reduce IX Messaging performance and may cause delayed message processing, slow administration response, or degraded voicemail/application behavior if the condition persists.

Alarm

avIXAlmServCPUWarning; related alarm: avIXAlmServRAMWarning

Troubleshooting Steps

  1. Confirm the active alarm in the monitoring dashboard and identify whether the current condition is CPU, RAM, or both.
  2. Check whether the alarm is still active or was transient by reviewing recent CPU and memory utilization trends.
  3. Review current system workload, including message traffic, user activity, scheduled maintenance tasks, backups, reporting, or other jobs running during the alarm window.
  4. If authorized, use system or appliance administration tools to identify high-resource processes. Generic operating-system tools may include top, ps, free, vmstat, or equivalent vendor-supported commands.
  5. Check for recent changes that could increase resource demand, such as software updates, configuration changes, user growth, traffic increases, integrations, or new scheduled tasks.
  6. Verify that the server or virtual machine has sufficient allocated CPU and memory for the current IX Messaging workload and that the underlying host is not resource-constrained.
  7. If one process or service is consuming abnormal resources, follow vendor-supported procedures to restart or remediate that component during an approved maintenance window.
  8. If utilization remains high without an obvious process fault, reduce workload where possible, reschedule noncritical jobs, or plan a capacity increase or platform scaling action.
  9. Continue monitoring until CPU and memory return to normal operating levels and the alarm clears from the dashboard.

Resolution

The alarm is cleared by reducing sustained CPU or memory utilization below the warning threshold. If the condition is workload-related, adjust traffic, scheduling, or capacity. If the condition is caused by an abnormal process or service, remediate it using vendor-supported procedures and verify that the alarm clears afterward.