Skip to main content

Avaya IXM CPU Critical Alarm

Jeremy Boilard

Problem Statement

Avaya IX Messaging IXM (Consolidated) reports a Major alarm with maintenance object avIXAlmServCPUCritical. The alarm indicates CPU usage became critical, reported at 100%, with a description that the amount of traffic generated does not match CPU specifications.

Impact

The IX Messaging server may experience degraded performance while CPU utilization remains critical. Messaging functions can become slow or unstable if the condition persists.

Alarm

avIXAlmServCPUCritical

Troubleshooting Steps

  1. Confirm the alarm details in the monitoring dashboard, including device type, alarm severity, maintenance object, and reported CPU utilization.
  2. Verify whether CPU utilization is still at or near 100% or whether the alarm was transient.
  3. Check the Avaya IX Messaging server health and look for any related service, application, or system resource alarms.
  4. Review current system load and identify processes consuming excessive CPU.
  5. Check for abnormal or unexpected traffic patterns toward the IX Messaging server that could explain the alarm description.
  6. Confirm whether recent configuration changes, maintenance activity, software updates, integrations, or traffic increases occurred before the alarm opened.
  7. If CPU utilization has returned to normal, continue monitoring to confirm the alarm clears and does not recur.
  8. If CPU utilization remains critical, reduce or isolate the source of excessive traffic or CPU load where possible.
  9. If the cause cannot be isolated or the alarm persists, collect system logs, alarm details, CPU/process utilization data, and recent change history, then escalate to the Avaya support path or appropriate engineering team.

Resolution

No ticket-specific resolution was provided. The alarm should be treated as an active CPU saturation condition until CPU utilization returns to normal and the avIXAlmServCPUCritical alarm clears. Persistent occurrences require investigation of high-CPU processes, abnormal traffic, recent changes, and possible capacity or application issues.