| Description |
This article discusses the behavior where IP address information may not immediately update in the UI when host is in isolation.
It is possible IP address information can take longer than expected to populate while testing with hosts in isolation. Passive and active methods are used for determining IP address information for a host. In isolation, IP address information is updated via the DHCP leases log.
The DHCP leases log is parsed when a change is detected. The host entry is updated only when there is a change between the current cached address and a newly parsed address.
If a host is deleted and is leased the same address, it can take multiple minutes until another active method for IP address population will update the host record. |
| Scope | Versions: 8.x and 9.x. |
| Solution |
This does not reflect real world use, and does not indicate any underlying issue. |
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.