Allocate IP prefixes and individual addresses on supported IPAM platforms.
Allocates network/subnet space and individual IP addresses on whichever IPAM platform the caller is targeting, following that platform's own documented procedure and call mechanism exactly.
dns-record-management
for that (a separate concept from address-space allocation, even on platforms like Infoblox that offer
both).There is no RFC grounding IPAM allocation the way RFC 1035 grounds DNS — every platform's allocation model is its own product design. What is genuinely shared:
Invoke-SwisVerb), not HTTP methods — confirm the mechanism in references/INDEX.md before assuming
GET/POST semantics apply.See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
platform argument. Check
references/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet.references/<platform>/procedure.md and follow it exactly — it contains that platform's
full operational procedure, error handling, patterns, known limitations, tools, and verification
checklist.dns-record-management for those), SolarWinds IPAM, Nautobot, Micetro (address space only), and
phpIPAM. A platform not listed in references/INDEX.md needs a new reference file before this skill
can be used for it.dhcp-scope-management), network discovery, or
DNS record creation on any platform — those are adjacent capabilities, not address-space
allocation.SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed call mechanism detail — belong in that platform's own
references/<platform>/procedure.md, never here.
Each platform assumes its own authenticated client and call mechanism (REST, WAPI, or SOAP/SWIS verb
invocation) — see references/INDEX.md for which, and that platform's procedure.md for the specific
operations.
references/INDEX.md before proceeding, including its call
mechanism (REST vs. non-REST)procedure.md was followed, including its own confirmation/reservation
semantics — not a generic/improvised sequence