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


---

# Create an IP Address record at subnet level

# Create an IP Address record at subnet level {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
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.

## 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 IP Subnetwork must not have any existing IP Address records created from allocated IPs. If it does, delete those records first, or use this method on a different subnetwork.

Role required: core.dc_ops_agent, sn_ni_core.inventory_agent

## About this task

This task is the at-subnet-level allocation method. The system creates one IP Address record whose value is the subnetwork's CIDR (for example,
`10.10.1.0/26`). The record represents the subnetwork as a single CMDB Configuration Item and is linked
to the subnetwork through a Contains relationship.

The two IP allocation methods (from allocated IPs and at subnet level) are mutually exclusive on a given subnetwork. After the first IP Address record is created by either method, the other method is locked for that subnetwork
until all IP Address records are deleted. For more information, 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.").

This method does not require the subnetwork's allocated IP records to be created first. The IP Address record is bound directly to the subnetwork, not to any individual address slot.

## 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.
   {#create-an-ip-address-record-at-subnet-level__substeps_sqj_vcd_xjc}
3. Open the three-dot menu on the record.
4. Select Create IP Address Record.  
   Note:  
   This menu item is separate from the Create IP Address Records button on the Allocated IP Address tab.
5. In the confirmation dialog, review the subnetwork details.
6. Select OK to confirm.  
   The system creates the IP Address record and displays a confirmation banner:

       IP Address record created: {Name} ( {CIDR} )

7. Review the new IP Address record on the IP Address tab.  
   The tab count updates to 1. The IP Address record displays the following fields.
   {#create-an-ip-address-record-at-subnet-level__ip-address-fields-subnet-level__entry__2}

   | Field | Description |
   |-|-|
   | Name | The subnetwork's CIDR. Ffor example, 10.10.1.0/26. |
   | IP Address | The subnetwork's CIDR. |
   | IP version | IP version, such as IPv4 or IPv6. This matches the subnetwork's protocol. |
   [Table 1. IP Address record fields]

   {#create-an-ip-address-record-at-subnet-level__ip-address-fields-subnet-level}

## Result

The system writes one CMDB relationship:
IP
Subnetwork → Contains → IP Address. This links the IP Address record to the parent subnetwork. The system does not write a Manages relationship because the IP Address record is not bound
to a specific allocated IP slot. For more information, 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.").

## What to do next

Bind the IP Address record to the service, port, customer, or interface it represents by populating the Owned By Configuration Item field on the record.
**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 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**   

* [IP Address form](https://servicenow-prod.fluidtopics.net/Ntxn7c7tTK_NvKGeDIiZNw "The IP Address form is the active CMDB record for an IP address, created from an allocated IP slot or at the subnetwork level.")

*[\>]: and then