Skip to main content

Avaya IX Messaging CPU Critical Alarm

Jeremy Boilard

Problem Statement

Avaya IX Messaging IXM (Consolidated) reports a Major CPU utilization alarm. The maintenance object is avIXAlmServCPUCritical and the equipment status indicates CPU usage became Critical, reported at 100%.

Impact

High CPU utilization can affect messaging platform responsiveness and may cause delays or intermittent service impact if utilization remains sustained. In the referenced event, CPU utilization later returned to a normal state and the alarm cleared.

Alarm

avIXAlmServCPUCritical

Troubleshooting Steps

  1. Confirm the active alarm details in the monitoring dashboard, including severity, maintenance object, alarm code, and current CPU percentage.
  2. Check whether the alarm has already cleared. Look for the resolved maintenance object avIXAlmServCPUResolved or a status indicating CPU usage became Normal.
  3. If the alarm is still active, verify current CPU utilization directly from the Avaya IX Messaging IXM management interface or operating system monitoring tools available for the deployment.
  4. Review recent traffic or message volume changes, because the alarm description indicates the amount of traffic generated may not match the available CPU specifications.
  5. Check for processes or services consuming abnormal CPU and verify whether utilization is sustained or only a short spike.
  6. Review recent configuration changes, maintenance activity, backups, scans, upgrades, or integrations that could temporarily increase CPU load.
  7. Check system logs and Avaya IX Messaging application logs for errors occurring at the same time as the CPU spike.
  8. If CPU usage remains critical, reduce nonessential load where operationally safe, restart only impacted services according to approved procedures, or escalate to the Avaya/application support path for deeper analysis.
  9. Continue monitoring after the CPU returns to normal to confirm that the alarm does not recur.

Resolution

The alarm cleared when CPU utilization returned to a normal state. The clearing event was reported as avIXAlmServCPUResolved with CPU usage became Normal at 89%. No further corrective action was documented for the event beyond monitoring after recovery.