Asm Health Checker Found 1 New Failures Updated Access

The ASM Health Checker can trigger this alert for a variety of reasons. Below are the most frequent root causes encountered in production environments.

ls -la /dev/oracleasm/disks/
# or
ls -la /dev/mapper/

The ASM health checker does not just detect failures — it maintains a persistent failure record.

The phrase "1 new failures updated" is precise. It communicates three key pieces of information:

It is crucial to understand that this is not an immediate fatal error. ASM is reporting that it found something abnormal, but the disk group may still be mounted and operational (often in a degraded state). asm health checker found 1 new failures updated

Prepared by: [Your Name/Role] Status: Awaiting resolution

ASM Health Checker alert "found 1 new failures updated" typically indicates that the BIG-IP system's internal monitoring has detected a specific resource or service failure within the Application Security Manager (ASM)

. This is often triggered when a monitored resource crosses a predefined threshold or a critical daemon stops responding. Immediate Review Checklist To review and resolve this failure, follow these steps: Identify the Failure Source : Navigate to Security > Reporting > Settings > ASM Alerts The ASM Health Checker can trigger this alert

in the Configuration utility. This screen displays which specific health alert was triggered (e.g., CPU usage, memory limits, or database connectivity). Check Daemon Health : Verify if critical ASM processes like asm_config_server are running. You can check this via the command line using tmsh show /sys service Investigate Recent Changes

: Review the audit logs for recent maintenance activities, such as software upgrades, re-licensing, or configuration loads, which are common triggers for ASM health failures. Examine MySQL Database Status

: ASM relies heavily on an internal MySQL database. Check for database corruption or space issues by running tmsh load sys config verify or reviewing /var/log/asm for SQL-related errors. Utilize iHealth Diagnostics : Generate a file and upload it to the F5 iHealth portal The ASM health checker does not just detect

. This will automatically compare your system state against known bugs and best practices to pinpoint the exact failure. Common Root Causes

Configuring BIG-IP ASM system resource alerts using ... - My F5

SELECT group_number, name, path, state, failgroup, mode_status 
FROM v$asm_disk 
WHERE state != 'NORMAL';