---
sourceDocument: Australia Telecommunications Network Inventory
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/telecom-network-inventory

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecommunications Network Inventory

ft:clusterId :

    - telninv

bundleId :

    - telninv

workflow :

    - Customer and Industry


---

# Allocate IP address slots in a subnetwork

# Allocate IP address slots in a subnetwork {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Allocate IP address slots to create one Allocated IP Address record for each address in a subnetwork CIDR. Reserved addresses (the first and last for IPv4, or the first for IPv6) are flagged automatically and
can't be promoted to IP Address records.

## Before you begin

Install all required Telecommunications Network Inventory plugins.

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. For more information, see [Bulk allocation limits for allocated IP addresses](https://servicenow-prod.fluidtopics.net/WIEG_uemZKRzR9R8Tu7diA "When you trigger bulk creation of allocated IP records from an IP Subnetwork, the system applies size limits and reserved-address rules before generating the records. This topic describes those limits and the messages displayed when they apply.").

Role required: `core.dc_ops_agent, sn_ni_core.inventory_agent`

## 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 that 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](https://servicenow-prod.fluidtopics.net/q3YlFrpcnUl5o5EeYJXmVA "Create a single IP Address record that represents an entire IP Subnetwork as one Configuration Item. The IP Address record uses the subnetwork'ss CIDR as its value, rather than a single host address. This method is used when the subnetwork is bound to a service, port, customer, or interface as a single entity.").

## Procedure

1. Navigate to WorkspacesNetwork Inventory Workspace or Service Operations Workspace.
2. Open the IP Subnetwork record.
   1. Go to Inventory Number AllocationIP Network Subnets.
   2. Select the subnetwork.
3. Select the Allocated IP Address tab.
4. Open the three-dot menu and select Create Allocated IP Address Record.
5. In the confirmation dialog, review the number of addresses that will be created.
6. Select OK to confirm.  
   The allocated IP records are created and a confirmation banner appears.
7. Review the allocated IP records on the Allocated IP Address tab.  
   The tab count updates to reflect the number of records created. Each record displays the following fields:
   {#allocate-ip-address-slots-in-a-subnetwork__allocated-ip-address-fields__entry__2}

   | Field | Description |
   |-|-|
   | Name | Address value. |
   | IP Address | Address value. |
   | Is Reserved | Option to prevent promotion of this address to IP Address records (first and last for IPv4; first only for IPv6). |
   | Is Managed | Cleared until an IP Address record is created from this slot. Not user-editable. |
   | Managed Network | Parent subnetwork. |
   [ ]

   {#allocate-ip-address-slots-in-a-subnetwork__allocated-ip-address-fields}

## What to do next

Create IP Address records from one or more of the allocated IP slots. See [Create an IP Address record from allocated IPs](https://servicenow-prod.fluidtopics.net/hRNDS4NQVx0~F9JurffE9g "Create one or more IP Address records by selecting allocated IP slots and promoting them to active CMDB Configuration Items.").
**Related tasks**   

* [Create an IP Address record from allocated IPs](https://servicenow-prod.fluidtopics.net/hRNDS4NQVx0~F9JurffE9g "Create one or more IP Address records by selecting allocated IP slots and promoting them to active CMDB Configuration Items.")
* [Create an IP Subnetwork record](https://servicenow-prod.fluidtopics.net/9uvIJPRcTs8lUhUZ167X8A "Create an IP Subnetwork record to subdivide an IP Address Block or to nest a subnetwork within an existing IP Subnetwork. The subnetwork's CIDR must fall within its parent's range. This task supports both IPv4 and IPv6.")  
**Related reference**   

* [Bulk allocation limits for allocated IP addresses](https://servicenow-prod.fluidtopics.net/WIEG_uemZKRzR9R8Tu7diA "When you trigger bulk creation of allocated IP records from an IP Subnetwork, the system applies size limits and reserved-address rules before generating the records. This topic describes those limits and the messages displayed when they apply.")
* [Allocated IP Address form](https://servicenow-prod.fluidtopics.net/449ooShmk06nuxpkYNhflw "The Allocated IP Address form represents a single address slot within an IP Subnetwork. The fields on this form are listed below.")

*[\>]: and then