Back to All Scenarios
PASSEDnetwork / ipam_exhaustion
IPAM Exhaustion — No Addresses to Allocate
The IP Address Management system shows all subnets in the production VLAN are fully allocated. DHCP scopes have no available leases, and new devices cannot obtain IP addresses. Server provisioning and workstation deployment are both blocked.
Pattern
DHCP_EXHAUSTION
Severity
CRITICAL
Confidence
90%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | DHCP_EXHAUSTION | DHCP_EXHAUSTION | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 4 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Production VLAN with /22 subnet (1022 usable IPs). All IPs allocated between static and DHCP. 200 stale DHCP leases from decommissioned devices. New server deployment blocked. New employee workstation setup failing. DHCP scope at 100%.
Injected Error Messages (1)
DHCP scope exhaustion — no leases available in production scope 10.10.0.0/22, all 1022 addresses allocated, 200 stale leases from decommissioned devices, new devices receiving APIPA addresses (169.254.x.x), no leases available for server provisioning or workstation deployment, DHCP server event ID 1063: no leases available in scope
Neural Engine Root Cause Analysis
The DHCP server has exhausted all available IP addresses in the 10.10.0.0/22 scope, with all 1022 addresses allocated. The issue is compounded by 200 stale leases from decommissioned devices that are still consuming IP addresses unnecessarily. New devices are falling back to APIPA addresses (169.254.x.x), indicating they cannot obtain valid network configuration, which will severely impact network connectivity and service provisioning.
Remediation Plan
1. Immediately clean up stale DHCP leases from decommissioned devices to free ~200 IP addresses. 2. Reduce lease duration temporarily to accelerate turnover of unused addresses. 3. Monitor scope utilization and consider expanding the DHCP scope or implementing additional scopes if the cleaned addresses are insufficient. 4. Implement automated lease cleanup policies to prevent future exhaustion. 5. Set up proactive monitoring for DHCP scope utilization thresholds.
Tested: 2026-03-30Monitors: 1 | Incidents: 1Test ID: cmnck2k6p06a5obqeq2pwxtt4