DDIENGINEER.COM / FOLLOW THE EVIDENCEFICTIONAL NETWORKS. REAL TROUBLESHOOTING.
⌕ PACKET DETECTIVE
THE FIELD GUIDE / IPAM

IPAM troubleshooting labs

Learn to reconcile address inventory with routing context, ownership and actual allocation history. A matching prefix alone is rarely the whole story.

What you can practise

Keep routing domain, tenant, prefix and lifecycle state together before deciding that an allocation is redundant.

Choose an investigation

10 playable cases. Each includes simulated evidence, interactive checks and a guided verdict.

  1. CASE 001 / Foundation

    IPAM subnet reconciliation: complete coverage

    Reconcile routed prefixes with address inventory.

  2. CASE 002 / Foundation

    IPAM subnet reconciliation: partial coverage

    Reconcile routed prefixes with address inventory.

  3. CASE 007 / Foundation

    Reconcile overlapping IPAM prefixes across VRFs

    Same prefix. Different routing worlds.

  4. CASE 008 / Foundation

    Review inactive and reserved IPAM subnets

    Silence is not permission to delete.

  5. CASE 013 / Advanced

    Detect an unauthorised DHCP server

    Two offers. Only one belongs here.

  6. CASE 018 / Advanced

    Reconcile Infoblox network-view allocations

    An export flags the same prefix twice and proposes deleting one allocation.

  7. CASE 023 / Advanced

    Prevent duplicate IPAM allocations after API timeouts

    One timeout. Two allocations. A very confident green tick.

  8. CASE 029 / Advanced

    DDI consolidation: competing DNS automation writers

    Two reconcilers. One record. No ownership agreement.

  9. CASE 031 / Advanced

    IPAM API pagination: incomplete inventory results

    HTTP 200. One page. Two hundred false alarms.

  10. CASE 032 / Advanced

    IPAM API automation: concurrent address allocation race

    Both jobs checked. Neither claimed atomically.

Explore another trail