Unmanaged IPs
The page lists all IP addresses discovered during network scans that do not belong to any configured container, subcontainer, block, or subnet in IPAM. These IPs were detected as active on the network but are not mapped to your IP address hierarchy.
Unmanaged IPs typically indicate:
Devices operating outside defined subnets
Incorrect or inconsistent IP allocation
Newly connected devices that have not yet been added to the IPAM structure
Potential rogue, shadow, or unmanaged assets on the network
Misconfigured network segments or DHCP pools
What You See on the Screen
The page displays the following columns:
Unmanaged IPs | Basic Details
Subnet
The subnet from which the unmanaged IP was detected. This is based on the responding source IP.
Source IP
The scanner IP or data collector IP that detected the unmanaged address.
IP Address
The unmanaged IP was discovered during an Availability or Inventory scan.
How IPs Become “Unmanaged”
An IP appears in the Unmanaged IPs list when:
A scan detects a reachable IP address
The IP does not fall under any configured container → subcontainer → block → subnet
The IP’s address range is not part of your existing IPAM hierarchy
Example scenarios:
A device with an address outside configured subnet ranges
An external or guest device connected temporarily
Incorrectly assigned static IPs
Devices on overlapping or shadow networks
Exporting
The page includes an Export button to download all unmanaged IPs in CSV format.
Last updated