---
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


---

# IP address inventory management data model

# IP address inventory management data model {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The IP address inventory management data model shows how the tables for IP Address Blocks, IP Subnetworks, allocated IP addresses, and IP addresses relate to each other.
The
data model supports both IPv4 and IPv6, and supports nesting subnetworks to any depth within a parent.

## Data model {#ip-address-inventory-management-data-model__data-model}

The data model defines four record types in a parent-child hierarchy:

* IP Address Block (class: Managed IP Pool) --- top-level record representing a routable address range.
* IP Subnetwork (class: Managed IP Network Subnet) --- operational subdivision of an IP Address Block. An IP Subnetwork can contain further nested IP Subnetworks recursively.
* Allocated IP Address --- one record per address slot within an IP Subnetwork's CIDR.
* IP Address --- the active CMDB Configuration Item for an address. Created from an allocated IP slot or from a subnetwork as a whole.

## How IP addresses are allocated {#ip-address-inventory-management-data-model__how-ip-addresses-are-allocated}

The allocation flow depends on whether individual host addresses are tracked or the subnetwork is bound as a single entity.

Per-host tracking (from allocated IPs):

1. Define the IP Address Block representing the routable range.
2. Create one or more IP Subnetworks within the block.
3. Generate allocated IP records for a subnetwork (one per address in its CIDR).
4. Create IP Address records from selected allocated IPs as individual hosts are assigned.

Subnetwork-level binding (at subnet level):

1. Define the IP Address Block representing the routable range.
2. Create one or more IP Subnetworks within the block.
3. Create a single IP Address record representing the subnetwork as a whole. The IP Address record's value is the subnetwork's CIDR.

The two methods are mutually exclusive within a subnetwork. For more information about the methods and the relationships they create, see [CMDB relationships for IP address records](https://servicenow-prod.fluidtopics.net/ExKgutGNOGsd2TKE2iy2mA "When an IP Address record is created, the system writes one or two relationship records to the CMDB relationship table (cmdb_rel_ci). The relationships created depend on which allocation method was used to create the IP Address record. The relationships are visible on the IP Address record's Related Items panel and in the Dependency View.").
**Related concepts**   

* [CMDB relationships for IP address records](https://servicenow-prod.fluidtopics.net/ExKgutGNOGsd2TKE2iy2mA "When an IP Address record is created, the system writes one or two relationship records to the CMDB relationship table (cmdb_rel_ci). The relationships created depend on which allocation method was used to create the IP Address record. The relationships are visible on the IP Address record's Related Items panel and in the Dependency View.")  
**Related tasks**   

* [Create an IP Address Block record](https://servicenow-prod.fluidtopics.net/S7~AWj2an5aZ90dtgd~GTw "Create an IP Address Block record to define a top-level IP address range, expressed in Classless Inter-Domain Routing (CIDR) notation. The block becomes the parent for one or more IP Subnetworks. Supports both IPv4 and IPv6.")
* [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.")