Allocate IP address slots in a subnetwork
Allocate IP address slots in bulk from an IP Subnetwork. The system creates one allocated IP record for each address in the subnetwork’s CIDR. Reserved addresses (the first and last for IPv4, or the first for IPv6) are flagged automatically and cannot be promoted to IP Address records.
Before you begin
Before you begin:
- Install all required Telecommunications Network Inventory plugins.
- Role required:
core.dc_ops_agent, sn_ni_core.inventory_agent - The IP Subnetwork must be in an active state (Life Cycle Stage = Operational and Life Cycle Stage Status = In Use).
- The subnetwork must not already have allocated IP records. To re-allocate, delete the existing allocated IP records first.
- The subnetwork’s CIDR must contain at most 64 addresses. This means the prefix length must be /26 or longer for IPv4, or /122 or longer for IPv6. To learn more, see Bulk allocation limits for allocated IP addresses.
About this task
Allocating IP address slots creates one Allocated IP Address record for every address in the subnetwork's CIDR. Each record carries an Is Reserved flag, set automatically for protocol-reserved addresses. It also carries an Is Managed flag, set automatically once an IP Address record is created from the slot. The slot records form the inventory you draw from when creating individual IP Address records using the from allocated IPs method.
This task is the first step of the per-host allocation method. If you instead want to create a single IP Address record representing the subnetwork as a whole (the at-subnet-level method), do not run this task. See Create an IP Address record at subnet level.
Procedure
What to do next
Create IP Address records from one or more of the allocated IP slots. See Create IP Address records from allocated IPs.