Sites, networks, and addresses

Model from broad context toward individual allocations: create the site, attach its networks, divide address space into useful pools, then associate addresses with the resources that use them.

Network records

Use the real IPv4 or IPv6 CIDR as the network boundary. Add a gateway and VLAN ID/name where those values help operators understand or automate the environment. If two locations use overlapping private ranges, keep each network attached to the correct site.

Address pools

Pools communicate intent within a network. Common examples include dynamic DHCP, static infrastructure, client reservations, or space held for future expansion. Use names that describe policy rather than only numeric ranges.

Pool and network summaries show usable, in-use, and available capacity. From a pool, MiniPAM can suggest an available address; the site allocation context also supports allocation forms without making the operator calculate ranges manually.

IP addresses

Add assignment type, usage state, provisioning state, and ownership context when allocating an address. Associate the address with its interface or other supported resource so search results are actionable.

Use a network's Allocation view to inspect contiguous ranges and distinguish reserved, occupied, available, and out-of-pool space. Use Observed activity to review when known IP or MAC identities appeared on the network, and address association history to understand ownership changes.

A simple operating habit

Review unknown and conflicting observations before importing them, reserve stable infrastructure addresses intentionally, and retire old associations when equipment moves. That keeps utilization meaningful over time.