IPAM
Pools, Auto-Assign, the editable Interfaces table, and the rules that check the plan against the device.
Define IP pools — supernets for loopbacks, point-to-points, user VLANs and the rest — and let the platform allocate from them. Every address it hands out is tracked back to its pool, and the drawer is also where you read and edit the plan the design already has.
Pool types#
The type does two things: it decides how big a slice each allocation takes, and it tells Auto-Assign which links and interfaces it is allowed to serve.
| Management (/32) | One host address per device for the management plane. |
| User (VLAN) (/24) | Access subnets behind SVIs — the VLANs users and servers actually sit on. |
| WAN Interconnect (/31) | Router-to-router and router-to-firewall links inside your own network. |
| ISP / Public (/30) | Provider-issued space on an internet-facing handoff. Entered, not invented. |
| MPLS (/30) | Carrier-issued space per MPLS circuit. Reported and consumed here; the carrier owns the numbering. |
| Loopback (/32) | Stable per-device addresses for routing protocols, management and source-interface bindings. |
| Server (/32) | Host addresses for attached servers and appliances. |
/31 (RFC 3021 — two hosts, no waste), while ISP / Public and MPLS links carve a /30, because a provider handoff is normally delivered that way. A pool can override its own prefix per pool.The five views#
| Auto-Assign | Pick the categories present in this design and let the platform fill them in. It plans first and shows you the counts before anything is written. |
| Interfaces | Every addressable interface in the design as one editable table — management ports, SVIs, loopbacks and routed links together, whatever tab or panel they normally live behind. |
| By Device | The same addresses grouped per device, for reading a single box. |
| By Subnet | Grouped by subnet, which is where a carrier-issued MPLS or public prefix gets entered by hand. |
| Advanced | Pool and allocation records directly, including VLAN pinning, loopback pinning by role, and Cisco secondary subnets. |
Any view exports to CSV, so the plan can leave with you.
Auto-Assign#
The wizard offers only the categories this topology actually has — a design with no internet-facing link is never asked for a public prefix. By default it fills empty interfaces only, so re-running it after adding a site leaves every existing address alone; reassigning everything is a deliberate, separate choice.
- Loopbacks are written into the device's own configuration, not just the ledger, so they reach the generated config and anything that sources from them.
- A management interface is named the way its platform names it —
mgmt0,Management1,GigabitEthernet0orMGT— rather than one invented name for all of them. - Attached endpoints (servers, load balancers, end-user networks) get no management row. They have no NOS to manage, so an address there would render nowhere.
- An internet-facing link is never addressed out of private space. If no ISP / Public pool exists it is left unaddressed and reported, rather than quietly given a transit /31.
What validation checks#
The IP plan and the interfaces are checked together, so a pool that disagrees with what is configured on the device is itself a finding:
| alloc-address-invalid | IPAM addresses that aren’t usable hosts |
| duplicate-ip-extended | Addresses used twice (incl. loopbacks & IPAM) |
| ipam-config-drift | IP plan disagrees with the interface |
| subnet-overlap | Overlapping subnets |
| gateway-off-subnet | Gateways on no connected subnet |
| nexthop-off-subnet | Next-hops on no connected subnet |
| vlan-subnet-conflict | VLANs addressed as two subnets |
| vlan-undefined | VLANs referenced but never defined |
| prefix-unusable | Prefixes the interface can’t carry |
| mtu-mismatch | Mismatched MTU across a link |
| interface-no-ip | Interfaces with no IP address |