IP Management is comprised of four basic functions: adding aggregates into ProVision, managing those aggregate blocks, assigning them to a resource, and deleting the aggregates.
ProVision provides multiple ways for you to achieve each step, depending on your needs. For example, if your organization currently uses spreadsheet data to track aggregates, ProVision provides tools that can import your existing spreadsheets for bulk updates, saving you time. Need to just quickly assign a single IP? Direct Assign will allow you to do so with just a few clicks.
Adding new aggregate may be done manually, automatically from a RIR import, or imported from a .csv file.
Edit, Split, Merge, and connect with RIRs to architect the aggregates as needed and update WHOIS information, if applicable.
Aggregates may be assigned to a Resource at their creation/import, or assigned later manually or via Smart / Direct Assign.
Delete an aggregate from the aggregate box in the IPAM Tab. See: Working with IP Aggregates.
In ProVision, the IP assignment lifecycle starts with an available block which is free to be assigned to any IPAM-enabled resource holder. There are multiple methods that may be used to assign a block to a resource holder: Smart Assign, Direct Assign, or Manual Assign (Smart Browse). See Working with IP Blocks for details on assigning blocks.
Once an IP block is assigned, blocks can be further subassigned via the same methods, if desired, by using the "allow subassignments" toggle when editing an assigned block. If a block has subassignments enabled, but has not yet been subassigned, it is listed as "Allocated" - essentially held by the parent resource, but not fully assigned.
When an assigned block is un-assigned it proceeds into the Holding Tank: a special resource where blocks are held until either a set time has elapsed or until they are manually reclaimed to 'available' status. If a subassigned block is unassigned, it too proceeds to the Holding Tank if not overridden, and then reverts back to allocated to the original parent resource.
For more information on performing tasks in this IP Assignment Lifecycle, see the following documentation sections: