IP addresses allocation

  • Release version: Australia
  • Updated June 16, 2026
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of IP addresses allocation

    The IP address allocation feature in ServiceNow enables you to create, review, and manage IP Address Blocks, IP Subnetworks, and allocated IP addresses using Classless Inter-Domain Routing (CIDR) notation. This functionality supports both IPv4 and IPv6 protocols and integrates with the Configuration Management Database (CMDB) to maintain accurate network asset records.

    Show full answer Show less

    Key Concepts

    • IP Address Block: A top-level CIDR range representing a Managed IP Pool that contains IP Subnetworks.
    • IP Subnetwork: A subdivision of an IP Address Block that can be nested to any depth for detailed address space segmentation.
    • Allocated IP Address: Individual address slots within a subnetwork’s CIDR, flagged automatically if reserved or managed.
    • IP Address Record: Active CMDB records representing either single host addresses or entire subnetworks.
    • Managed Network: Defines a network scope ensuring CIDR uniqueness within that scope, allowing identical CIDRs in separate managed networks.

    IP Allocation Methods

    Two exclusive methods are available for creating IP address records in a subnetwork:

    • From Allocated IPs: Select individual allocated IP slots to create corresponding IP address records. Suitable for assigning IPs to specific devices or services.
    • At Subnet Level: Create a single IP address record for the entire subnetwork using its CIDR. Suitable for binding the subnet to a service or customer.

    Once an IP address record is created by one method, the other method is locked until deletion of existing IP address records, preserving allocated IP slots.

    Operational Requirements and Reserved Addresses

    • Records must be in an active state (Life Cycle Stage: Operational and Status: In Use) before creating child subnetworks or allocating IP addresses.
    • Reserved addresses are automatically flagged during allocation and differ by protocol:
      • IPv4: Network and broadcast addresses reserved, except for /31 and /32 subnets.
      • IPv6: Only the first address (Subnet Router Anycast) is reserved; no broadcast addresses exist.

    CMDB Relationships

    IP Address records maintain standard ServiceNow CMDB relationships:

    • When created from allocated IPs, each IP address record links to its allocated slot and containing subnetwork.
    • When created at subnet level, the IP address record links only to the containing subnetwork.
    • These relationships are visible in the Related Items panel and Dependency View, supporting network asset tracking and impact analysis.

    Practical Application

    ServiceNow customers can use this feature to systematically manage IP address spaces with clear hierarchical structures and enforced uniqueness scopes. The ability to allocate addresses individually or at a subnet level provides flexibility for diverse operational needs. Active record requirements and reservation rules ensure accuracy and compliance in IP address management. Integration with CMDB relationships supports comprehensive configuration and dependency management.

    Using the IP address allocation feature, you can create, review, and update IP Address Blocks and IP Subnetworks. You can also manage allocated IP addresses and IP addresses expressed in Classless Inter-Domain Routing (CIDR) notation. Both IPv4 and IPv6 are supported.

    IP address tables

    • IP Address Block: An IP Address Block is a top-level range of IP addresses expressed as a CIDR. The user interface label IP Address Block refers to the underlying Managed IP Pool class.
    • IP Subnetwork: An IP Subnetwork is an operational subdivision of an IP Address Block. An IP Subnetwork can itself contain further nested IP Subnetworks, allowing IP address space to be subdivided to any depth.
    • Allocated IP address: An allocated IP address represents a single address slot within an IP Subnetwork's CIDR. Allocated IP address records carry two flags. Is Reserved is set automatically for structurally unassignable addresses. Is Managed is set automatically when an IP Address record is created from this slot.
    • IP address: An IP address record is the active CMDB record for an address. It can represent a single host address within a subnetwork, created from an allocated IP. Alternatively, it can represent the entire subnetwork by using the subnetwork's CIDR as its value.
    • Managed Network: A Managed Network defines a network scope within which an IP Address Block's CIDR must be unique. The same CIDR may exist in different Managed Networks without conflict. The Managed Network assigned to an IP Address Block propagates down to its IP Subnetworks and cannot be changed at a lower level. To learn more, see Create Managed Network.

    IP allocation methods

    An IP Subnetwork uses one of two methods to create IP address records. The two methods are mutually exclusive: A subnetwork may use one or the other, but never both at the same time.

    • From allocated IPs: The user selects one or more allocated IP records on a subnetwork and creates a corresponding IP address record for each selected slot. Each new IP address record uses the host address as its value. This method is appropriate when individual addresses are being assigned to devices, interfaces, or services.
    • At subnet level: A single IP address record is created for the subnetwork as a whole. The IP address record uses the subnetwork's CIDR as its value, rather than a single host address. This method is appropriate when the subnetwork is bound to a service, port, customer, or interface.

    Once the first IP address record is created on a subnetwork by either method, the other method is locked for that subnetwork. To switch methods, delete the existing IP address records. The underlying allocated IP slots are preserved across deletion.

    Active state required for operations

    A record must be in an active state before child records or IP allocations can be created against it. A record is active when the Life Cycle Stage is Operational and the Life Cycle Stage Status is In Use. Any other combination of values prevents the creation of subnetworks beneath the record or the allocation of addresses from it.

    Reserved addresses

    When allocated IP records are generated for a subnetwork, addresses that are structurally unassignable are flagged automatically with Is Reserved = True. The rule differs by protocol. For IPv4, the first address (the network address) and the last address (the broadcast address) are reserved. A /31 IPv4 subnet reserves no addresses (RFC 3021); a /32 IPv4 subnet reserves no addresses. For IPv6, only the first address — the Subnet Router Anycast address (RFC 4291) — is reserved. IPv6 has no broadcast address. A /128 IPv6 subnet reserves no addresses.

    CMDB relationships

    Every IP Address record participates in standard ServiceNow CMDB relationships. The relationships created depend on the method used. When IP Address records are created from selected Allocated IPs, the system writes two relationships per record. The first is an IP Address Manages Allocated IP relationship, linking the new record to its source slot. The second is an IP Subnetwork Contains IP Address relationship, linking it to the subnetwork. When a single IP Address record is created at the subnetwork level, only the IP Subnetwork Contains IP Address relationship is created.

    Both relationship types are visible on each IP Address record’s Related Items panel and in the Dependency View.