Troubleshooting Tip: Unused IP Pools can blackhole and disrupt traffic
| Description | This article describes the possible reason for service disruption after adding an IP Pools object, even though the object is not applied to any firewall policy. |
| Scope | FortiGate. |
| Solution | Consider the Network topology:
Internet <---> [WAN] FortiGate [LAN] 14.14.14.17 <---> Client 14.14.14.100
FortiGate IP Pools configuration:
config firewall ippool edit "test" set startip 14.14.14.100 set endip 14.14.14.100 next end
Scenario:
Analysis:
diagnose sniffer packet any 'icmp and host 14.14.14.100' 4 0 l interfaces=[any] filters=[icmp and host 14.14.14.100] 2025-11-19 14:39:58.714801 LAN in 14.14.14.100 -> 14.14.14.17: icmp: echo request 2025-11-19 14:39:58.714853 root out 14.14.14.17 -> 14.14.14.100: icmp: echo reply 2025-11-19 14:39:58.714861 root in 14.14.14.17 -> 14.14.14.100: icmp: echo reply
config firewall ippool
diagnose system cmdb refcnt show firewall.ippool
If the IP pool has a reference count of 0, it should be removed/deleted or have arp-reply disabled. Failure to do so may cause unexpected traffic interruption, VPN failure, or routing blackholes.
Fortinet strongly recommends auditing and removing unused IP pools & VIPs before upgrading.
Related articles: |
