---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# IPAM Discovery integration

# IPAM Discovery integration {#ariaid-title1}

Release version: Australia  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 IPAM Discovery integration

The IP Address Management (IPAM) to Discovery integration in ServiceNow automates the creation and management of Discovery schedules using IPv6 network data stored in IPAM.
It synchronizes Discovery processes with changes in your IPv6 and IPv4 network infrastructure, ensuring an accurate and current view of your network environment.
Show full answer Show less  

## How it works

* Identifies operational resources from IPAM tables
* Processes only the latest changes since the last sync
* Creates Discovery schedules grouped by a specified tag key
* Disables schedules that no longer have valid network targets

## Benefits

* **Automated schedule management:** Removes the need for manual Discovery schedule creation and maintenance for both IPv4 and IPv6 networks.
* **Synchronization with network changes:** Automatically updates Discovery schedules based on network, subnet, or IP address changes.
* **Incremental updates:** Improves performance by processing only changed resources.
* **IPv4 and IPv6 support:** Supports both IP versions with dedicated capacity limits and mapping.
* **Audit capability:** Maintains history of synchronization activities and changes via execution records for monitoring and troubleshooting.

## Requirements

* Service Graph Connector Central v2.4.0 (sgcadmin access)
* Service Graph Connector for Infoblox v1.5.0 (sgcadmin access)
* CMDB Workspace v9.0.0
* Discovery Admin Workspace v1.13.0 (discoveryadmin access)
* ServiceNow AI Platform Australia, ZP8 or later, or YP13 or later
* IPAM data must include operational managed networks, IP subnets, and allocated IP addresses with valid CIDR notation for IPv4 subnets and established relationships between these entities

## Configuration

Key system properties control integration behavior:

* **Debug logging:** Enable detailed logs for troubleshooting.
* **Schedule grouping:** Define a tag or attribute (e.g., "location") to group Discovery schedules.
* **IPv4/IPv6 limits:** Set maximum IP addresses per auto-generated Discovery schedule (default 65,536 for IPv4, 20,000 for IPv6; lower limits apply to older platform versions).

## Generated Discovery schedules

* Maintenance source marked as Discovery-IPAM Integration
* Initially inactive for review before activation
* MID Server selection set to MID Cluster
* Description includes managed network details, grouping criteria, and navigation links

## Execution tracking and monitoring

* Each synchronization generates an execution record capturing metrics, configuration, and errors
* Prevents simultaneous runs to avoid conflicts
* Execution records should be reviewed regularly to monitor integration health

## Best practices

* Assign subnets to groups in your IPAM product to enable meaningful schedule grouping
* Regularly review generated schedules and update configurations as needed
* Use debug logging during initial deployment to understand integration behavior
* Ensure IPAM data quality before synchronization
* Monitor execution records frequently to detect and resolve issues early  
The IP Address Management (IPAM) to Discovery integration automatically creates and manages Discovery schedules based on your IPv6 network infrastructure data stored in IPAM. The integration keeps discovery processes synchronized with IPv6 network changes, providing an up-to-date view of your network environment.

## How it works {#ipv6-ipam-disco-integration__section_hrn_ryp_23c}

The IPAM to Discovery integration automates schedule management through the following process:

* Identifying resources marked as operational in your IPAM tables
* Processing only the latest changes from your IPAM system
* Creating Discovery schedules, organized by a tag key you specify
* Disabling schedules that no longer have valid network targets
{#ipv6-ipam-disco-integration__ul_fhf_h1q_23c}

## Benefits {#ipv6-ipam-disco-integration__section_pvf_fyp_23c}

The following examples highlight the primary advantages of integrating IPAM with Discovery:

* Automated schedule management: Eliminates the need to manually create and maintain Discovery schedules for IPv4 and IPv6 networks.
* Synchronization with network changes: Automatically adjusts Discovery schedules when networks, subnets, or IP addresses change.
* Incremental updates: Processes only resources that changed since the last synchronization, improving performance.
* IPv4 and IPv6 support: Handles both IPv4 and IPv6 networks with separate capacity limits and mapping approaches.
* Audit capability: Maintains history of synchronization activities and changes through execution records.
{#ipv6-ipam-disco-integration__ul_xfc_gyp_23c}

## Requirements {#ipv6-ipam-disco-integration__section_xdw_lyp_23c}

This feature requires the following:

* Service Graph Connector Central (SGC Central) v2.4.0 with sgc_admin access.
* Service Graph Connector for Infoblox v1.5.0 with sgc_admin access.
* CMDB Workspace v9.0.0.
* Discovery Admin Workspace v1.13.0 with discovery_admin access.
* Australia, ZP8 or later, or YP13 or later version of the ServiceNow AI Platform.
{#ipv6-ipam-disco-integration__ul_ys2_nyp_23c}  
Before using the integration, ensure that your IPAM tables contain the following data:

* Managed networks in the Managed Network \[cmdb_ci_managed_network\] table with operational status set to operational.
* IP subnets in the IP Network Subnet \[cmdb_ci_ip_network_subnet\] table with operational status set to operational.
* IP addresses in the Allocated IP Address \[cmdb_ci_allocated_ip_address\] table with operational status set to operational.
* IPv4 subnets should have valid Classless Inter-Domain Routing (CIDR) notation for address calculation.
* Relationships between managed networks, subnets, and IP addresses must be established.
{#ipv6-ipam-disco-integration__ul_r2h_wts_m3c}

## Configuration {#ipv6-ipam-disco-integration__section_mtz_jzp_23c}

The following system properties control the behavior of the integration:  
{#ipv6-ipam-disco-integration__table_nff_rzp_23c__entry__3}

| Property name | Description | Default |
|-|-|-|
| glide.discovery.schedule.autogenerate.debug | Enables detailed logging for troubleshooting. | false |
| glide.discovery.schedule.autogenerate.group | Groups auto-generated IPAM Discovery schedules by a specific tag or attribute. The value of this property represents a key that IPAM retrieves and stores in the Key Values \[cmdb_key_value\] table. For example, entering "location" as the value would group the schedules by their associated locations. | empty |
| glide.discovery.schedule_ipv4_limit | Defines the maximum number of IPv4 addresses that can be included in a single auto‑generated IPv4 Discovery schedule. | 65,536 |
| glide.discovery.schedule_ipv6_limit | Defines the maximum number of IPv6 addresses that can be included in a single auto‑generated IPv6 Discovery schedule. | 20,000 Note: On instances below ZP3 and YP9, the maximum number of IPv6 addresses per schedule must not exceed 5,000, which is also the default value in Yokohama and earlier releases. |
[Table 1. System properties]

{#ipv6-ipam-disco-integration__table_nff_rzp_23c}

## Generated schedules {#ipv6-ipam-disco-integration__section_qjw_g5s_m3c}

The integration creates Discovery schedules with the following characteristics:

* Maintenance source: The maintenance source is set to Discovery-IPAM Integration.
* Initial state: The initial state is set to inactive for review before activation.
* MID Server selection: The MID Server selection is set to MID Cluster.
* Description: Includes managed network, grouping criteria, and navigation links.
{#ipv6-ipam-disco-integration__ul_v5b_35s_m3c}

## Execution tracking {#ipv6-ipam-disco-integration__section_vkx_jdt_m3c}

Each synchronization creates an execution record that captures performance metrics, configuration settings, and any errors. The integration helps prevent multiple simultaneous executions to avoid conflicts. Review these
execution records to monitor integration health.

## Optimization {#ipv6-ipam-disco-integration__section_j51_jfq_23c}

Follow these guidelines to get the most out of the IPAM Discovery integration:  
* Assign subnets to groups: In your IPAM product, assign subnets to groups so the integration can organize schedules based on those groupings.
* Regular maintenance: Periodically review generated schedules and adjust configuration as needed.
* Test with debug logging: Enable debug logging during initial implementation to understand behavior.
* Verify data quality: Verify IPAM data quality before running synchronization.
* Monitor execution records: Review execution records regularly to catch issues early.
{#ipv6-ipam-disco-integration__ul_atk_jfq_23c}