Note the exact timestamp to correlate the failure with AWS CloudTrail audit logs. 2. Verify IAM and Resource Policies
The "ASM Health Checker found 1 new failures" notification is a critical alert in the F5 BIG-IP Application Security Manager ecosystem. This error indicates that a background diagnostic script has detected a discrepancy or a component failure within the Web Application Firewall (WAF) module. If ignored, these failures can lead to configuration sync issues, traffic processing latency, or complete service outages. Immediate Impact of ASM Health Check Failures
The ASM Health Checker is part of the broader . It runs periodic checks—and can be triggered manually—to assess the integrity of: asm health checker found 1 new failures
Operations teams are advised to follow this runbook:
. This message indicates that a failure has been logged in the Automatic Storage Management (ASM) health check framework, often related to disk group dismounts, header corruption, or voting file issues. Oracle ASM Health Check Failure Report Report Field Description / Details Alert Message ASM Health Checker found 1 new failures System Component Oracle Automatic Storage Management (ASM) Detection Source ASM Alert Log (typically located at diag/asm/+asm/ /trace/alert_+asm.log Incident Status Note the exact timestamp to correlate the failure
In a Real Application Clusters (RAC) environment, a rolling upgrade or manual DBA change left an initialization parameter (like ASM_DISKSTRING or ASM_POWER_LIMIT ) inconsistent across nodes. How to Fix:
Before troubleshooting the error, understanding the tool is crucial. The ASM Health Checker is an automatic, background diagnostic framework introduced in Oracle Grid Infrastructure 11gR2 (enhanced in 12c and 19c). It runs periodically (typically every hour or on specific triggers) to validate: This error indicates that a background diagnostic script
If your disk group uses (requiring 2 or 3 failure groups) or High Redundancy (requiring 5) and an entire array goes offline, ASM will flag the failure. It does this because your storage is now running exposed without proper protection. Step-by-Step Diagnostic and Resolution Workflow
