Description | This article describes the DHCP demon causing High Memory utilization due to frequent DHCPDiscover request coming from the client. |
Scope | FortiOS |
Solution |
FortiGate memory utilization goes high due to Clients frequent 'DHCPDiscover' message.
Once the FortiGate receives a client's 'DHCPDiscover' message, it makes a 'DHCPOffer'. When the 'DHCPDiscover' message is received too frequently from multiple hosts, it may cause memory to spike for a while, depending on the model's available memory. Running the command 'diag debug crashlog read' will show 'Kernel exits extreme low memory mode' and 'Kernel enters extreme low memory mode'.
2025-05-20 04:23:59 msg="Kernel exits extreme low memory mode"
DHCP Debug:
diag debug application dhcps -1 diag debug console timestamp en diag debug enable
[note]DHCPDISCOVER from 00:45:6e:xx:xx:xx via port3 (found) [debug]deled ip 192.168.10.10 mac 00:45:6e:xx:xx:xx in vd root
diag sniffer packet port3 'port 67 or port 68' 4 0 l
1 0.000000 192.168.10.10 192.168.10.1 DHCP 342 DHCP Release - Transaction ID 0x829f183e
Here, note that the client is continuously requesting a DHCP IP. Once the FortiGate makes an offer, it Releases the IP and makes another DHCP Discover request.
This continuous request pushes the DHCP process to consume more memory than usual.
When the DHCP daemon is terminated with the 'fnsysctl killall dhcpd' command, the memory consumption goes down, but will go up again after an extended period of the client sending continuous requests.
In order to resolve this issue permanently, the client needs to be isolated.
Related article: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.