IPAM API pagination: incomplete inventory results
A reconciliation report marks 200 networks missing. The API call returned HTTP 200, and the export contains exactly 100 objects. A remarkably tidy coincidence.
What you’ll practise
Trace the supplied evidence, challenge alternative explanations, and choose a safe next action. Use the topology and private notebook to document your reasoning.
Lab scope: Vendor-neutral paginated lab API. Contract uses an opaque next cursor. Read-only collection: no records are deleted during this investigation.
Validation: Original synthetic operational lab; not a reproduced vendor defect
DHCP says yes.
DNS says yesterday.
A laptop moved networks. Its name didn’t. Find out who’s telling the truth — and what you should check next.
Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.
New lease.
Old address.
Same confused user.
10.62.4.27 ✓↓ six minutes and three cache flushes later09:36 / DNS ANSWER10.61.4.27 ?“Have you tried flushing it again?”
The fourth time is not a strategy.
Troubleshooting guide
Recognise the symptoms
A reconciliation report marks 200 networks missing. The API call returned HTTP 200, and the export contains exactly 100 objects. A remarkably tidy coincidence.
Checks to compare
- Inspect response and connector trace. Compare what this check establishes with the other devices in the path.
- Follow documented pagination. Compare what this check establishes with the other devices in the path.
- Reconcile complete collection. Compare what this check establishes with the other devices in the path.
Scope matters. Vendor-neutral paginated lab API. Contract uses an opaque next cursor. Read-only collection: no records are deleted during this investigation.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
HTTP success refers to the requested page. The explicit next cursor and repeated requests establish that the first result was incomplete.
Common mistakes to avoid in this scenario
- The missing objects have been deleted: Recreate everything absent from the first response page.
- The API request failed completely: Treat HTTP 200 as a transport failure and retry the identical first-page request.
A proportionate next action
Follow the documented cursor to completion, validate uniqueness/snapshot consistency and gate publication on collection completeness.
Limits of the conclusion
Pagination syntax and snapshot guarantees vary by API. This lab defines them explicitly; do not assume generic limit/offset behaviour.