DHCP Pool Exhausted
Intermediate TroubleshootQuestion
A subnet 192.168.1.0/27 has its DHCP pool configured for the full usable range. Three addresses are statically reserved (gateway, DNS server, printer). The network administrator reports that 30 devices need DHCP addresses but some are receiving 169.254.x.x (APIPA) addresses. Identify the problem and recommend a fix.
Given
{
"subnet": "192.168.1.0/27",
"reserved": 3,
"devices": 30
}
Answer
{
"usable_hosts": 30,
"subnet_range": "192.168.1.1 - 192.168.1.30",
"available_after_reserved": 27,
"devices_needing_dhcp": 30,
"problem": "30 devices exceed 27 available DHCP addresses (30 usable minus 3 static reservations = 27 available)",
"devices_without_ip": 3,
"fix_option_a": "Expand to /26 (62 usable hosts, 59 after reservations)",
"fix_option_b": "Add a second /27 subnet and configure DHCP relay"
}
Try to solve it first, then click Reveal Answer
Step-by-Step Explanation
Step 1: Calculate the subnet capacity
192.168.1.0/27: - /27 = 32 total addresses (2^5) - Network address: 192.168.1.0 - Broadcast address: 192.168.1.31 - Usable range: 192.168.1.1 – 192.168.1.30 = 30 usable host addresses
Step 2: Account for static reservations
3 addresses are statically assigned: - 192.168.1.1 → Gateway (router) - 192.168.1.2 → DNS server - 192.168.1.3 → Printer
Remaining for DHCP: 30 - 3 = 27 addresses DHCP pool should be: 192.168.1.4 – 192.168.1.30 (27 addresses)
Step 3: Identify the shortage
DHCP pool capacity: 27 addresses Devices needing DHCP: 30 devices Shortage: 30 - 27 = 3 devices cannot get an IP address
These 3 devices will time out waiting for a DHCP offer and fall back to APIPA (169.254.x.x), which is not routable and explains why they have no network access.
Step 4: Diagnose on the DHCP server
# Linux (isc-dhcp-server)
cat /var/lib/dhcp/dhcpd.leases | grep -c "binding state active"
# If = 27, pool is exhausted
# Windows Server
netsh dhcp server scope 192.168.1.0 show clients
# Count active leases vs. pool size
# Check for 169.254.x.x devices (APIPA indicates DHCP failure)
arp -a | grep "169.254"
Step 5: Fix options
Option A — Expand to /26 (recommended if growing):
New subnet: 192.168.1.0/26
Usable hosts: 62
After 3 static reservations: 59 available for DHCP
Covers 30 devices with room for ~29 more
Update the router interface and DHCP scope.
Option B — Add a second /27 + DHCP relay (if /26 not available):
Existing: 192.168.1.0/27 (30 usable, 27 DHCP)
New: 192.168.1.32/27 (30 usable, 30 DHCP)
Configure: ip helper-address on the router
Step 6: DHCP lease time tuning
If devices are mostly dynamic (laptops, phones), shorten lease time: - Default: 24 hours - Recommended for high-churn: 4 hours - Short leases return addresses faster, effectively increasing pool availability
Key takeaway
A /27 subnet provides exactly 30 usable hosts — a tight fit. Network planning should account for: - Static reservations (gateway, DNS, printers, servers) - Growth headroom (at least 20% free) - DHCP lease overlap (not all leases expire simultaneously)