CMDB Coverage scheduled jobs

  • Release version: Australia
  • Updated March 12, 2026
  • 2 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 CMDB Coverage Scheduled Jobs

    CMDB Coverage utilizes scheduled jobs to identify stale and missing data within the Configuration Management Database (CMDB). Customers can access the list of these scheduled jobs by enteringsysautoscript.listin the navigation filter.

    Show full answer Show less

    Key Features

    • PopulateBinaryTable: A one-time initialization job that converts historical IPv4 addresses into binary format for efficient matching, storing them in the Binary IP Address table.
    • InitializeAllocatedIPTable: This one-time job processes historical records from the Allocated IP Address table, updates the cimatchstatus for these records, and establishes relationships between discovered Configuration Items (CIs) and allocated IP addresses.
    • ProcessStagingTable: This job monitors real-time changes in IP address information via the DB Listener, updating the Allocated IP Address table with new and modified records from the IP Address Staging table.
    • SubnetUsageCount: A daily job that tracks subnet usage by counting free, allocated, and reserved IP addresses based on the cimatchstatus in the Allocated IP Address table.
    • Find Missing IPAM IPs in Discovery: This job compares IPAM data with configured discovery ranges to identify gaps in IP address coverage, recording findings in the Discovery Schedule Gap table for operational review.

    Key Outcomes

    By implementing these scheduled jobs, ServiceNow customers can ensure accurate and up-to-date IP address management, minimize discovery gaps, and enhance the reliability of their CMDB data. This leads to improved operational efficiency and better decision-making regarding asset management and network planning.

    CMDB Coverage uses scheduled jobs to identify stale and missing data.

    To view the list of scheduled jobs, enter sysauto_script.list in the navigation filter.

    PopulateBinaryTable

    The PopulateBinaryTable scheduled job is a one-time initialization job that processes the historical records that existed before the CMDB Coverage was configured. All historical IP addresses (IPv4 addresses) are converted into binary format for fast matching. The records are added to the Binary IP Address [sn_cmdb_ip_cov_binary_ip_address] table. IPv6 addresses are processed as is.

    InitializeAllocatedIPTable

    The InitializeAllocatedIPTable scheduled job is another one-time initialization job that runs after the PopulateBinaryTable job. This scheduled job performs the following tasks and populates records in the CMDB Coverage Initialization Tracker [sn_cmdb_ip_cov_init_tracker] table:
    • Processes the historical records in the Allocated IP Address [cmdb_ci_allocated_ip_address] table.
    • Updates the value of the ci_match_status attribute for the records in the Allocated IP Address [cmdb_ci_allocated_ip_address] table.
    • Creates relationships between the discovered CIs and the records in the Allocated IP Address [cmdb_ci_allocated_ip_address] table. That is, corresponding records are created in the CMDB [cmdb_ci_rel] table.
    The possible values of the ci_match_status attribute are:
    • none: No CI matches the IP​ address, which indicates a discovery gap.
    • single: Exactly one CI matches​ the IP address.
    • multiple: Multiple CIs match​ the IP address.
    • not_evaluated: The record isn’t processed yet.

    ProcessStagingTable

    The ProcessStagingTable scheduled job processes the records that are created by the DB Listener after the CMDB Coverage application is configured.

    You can configure the list of tables that the DB Listener should monitor in the IP Coverage CI Table Configuration [sn_cmdb_ip_cov_ci_config] table. The Validate IP Coverage CI Config business rule validates the records that are created in the IP Coverage CI Table Configuration [sn_cmdb_ip_cov_ci_config] table to verify that only the IP address field is updated.

    The DB Listener performs the following tasks:
    • Detects real-time changes in IP address information.
    • Monitors the tables that are configured in the IP Coverage CI Table Configuration [sn_cmdb_ip_cov_ci_config] table.
    • Identifies new and updated IP addresses and creates corresponding records in the IP Address Staging [sn_cmdb_ip_cov_ip_staging] table.
    • Pushes changes to the Allocated IP Address [cmdb_ci_allocated_ip_address] table.
    The Platform DB Listener doesn’t rely on polling. Therefore, all updates to IP addresses are identified.

    The ProcessStagingTable scheduled job identifies the new records that were added by the DB Listener to the IP Address Staging [sn_cmdb_ip_cov_ip_staging] table. Subsequently, the ci_match_status attribute in the Allocated IP Address [cmdb_ci_allocated_ip_address] table is updated for all new records.

    SubnetUsageCount

    This daily scheduled job tracks subnet usage. Based on the value of the ci_match_status attribute in the Allocated IP Address [cmdb_ci_allocated_ip_address] table, the SubnetUsageCount scheduled job counts the number of free IP addresses, allocated IP addresses, and reserved IP addresses for each subnet.​

    Find missing IPAM ips in discovery

    IPAM-managed networks, subnets, and allocated IP addresses are managed separately from the configured discovery ranges and schedules of organizations. This often leads to stale and missing data (such as IP address ranges that are never scanned) in the CMDB.

    The Find missing IPAM ips in discovery scheduled job compares the IPAM data (networks, subnets, and allocated IP addresses) and the configured discovery ranges and schedules (IPv4 and IPv6 addresses) to identify gaps in IP address coverage, such as missing IPv4 address ranges and the number of IPAM IP addresses that don't have a discovery schedule. The data about gaps in IP address coverage is added to the Discovery schedule gap [sn_cmdb_ip_cov_discovery_schedule_gap]​ table, and is then available for operational review.