IPAM
IP pools, allocation, and conflict detection.
Relevant for:Enterprise / NetOpsProfessional Services
Where to find itCanvas toolbar→IPAM
Define IP pools (supernets for loopbacks, point-to-points, user VLANs…) and let the platform allocate from them: SVIs, routed links, and FHRP virtual addresses can be auto-assigned consistently, with every allocation tracked back to its pool.
Conflict detection#
Validation continuously checks for duplicate addresses and overlapping subnets across the whole design — including addresses typed manually outside any pool.
Why
Address conflicts are the most expensive “simple” mistake in networking — they pass every syntax check and then take down two segments at once. Pool-based allocation makes conflicts structurally impossible for managed ranges, and the overlap checker catches the hand-typed stragglers.
Tip
Use per-site pools sized for growth (a /20 per site for user VLANs, a /24 of /31s for point-to-points) — the auto-assign helpers number FHRP groups and pair addresses consistently across a distribution pair.