Skip to main content

Avaya CMS DISKFULLWRN Alarm

Jeremy Boilard

Problem Statement

A Minor alarm is generated on Avaya Call Management System (CMS) with maintenance object avCmsUnknown, description Unknown CMS Alarm(Minor), alarm code ACT, and equipment number DISKFULLWRN. The alarm indicates a disk-full warning condition reported by CMS monitoring.

Impact

If disk usage continues to increase, CMS logging, reporting, data collection, or normal application operations may be affected. The alarm should be reviewed before the disk reaches a critical/full state.

Alarm

avCmsUnknown / DISKFULLWRN / Unknown CMS Alarm(Minor) / ACT

Troubleshooting Steps

  1. Confirm the active alarm details in the monitoring dashboard and verify the device is an Avaya Call Management System (CMS).
  2. Access the CMS server using the approved administrative method for the environment.
  3. Check filesystem utilization with standard operating system commands such as df -h or the platform-approved equivalent.
  4. Identify any filesystem at or near the configured warning threshold.
  5. Review large files or directories in the affected filesystem using approved commands such as du -sh * from the relevant mount point or log/archive directory.
  6. Check CMS and system log/archive locations for accumulated files, old reports, backups, core files, or temporary files that can be safely removed or archived according to the site retention policy.
  7. Do not delete active CMS application files, database files, or system files unless confirmed safe by the CMS administrator or vendor documentation.
  8. If disk usage is caused by expected growth and cleanup is not sufficient, plan capacity remediation such as increasing filesystem capacity or moving archived data to approved storage.
  9. After cleanup or capacity remediation, recheck disk utilization and confirm it is below the warning threshold.
  10. Verify that the DISKFULLWRN alarm clears in the monitoring dashboard. If it remains active after disk utilization is normalized, refresh/recheck CMS alarm status and escalate to the CMS support team or vendor support.

Resolution

No final remediation details were documented in the source ticket. The standard resolution is to identify the filesystem triggering DISKFULLWRN, safely reduce disk usage or increase capacity, then verify the Minor CMS alarm clears from monitoring.