When discovering load balancers, previously found related data that is not found by the most recent discovery is deleted, along with any relationships with that data.

Related data consists of load balancer services (sometimes referred to as 'VIPs'), pools, pool members, VLANs, and interfaces. They are represented in the following tables, respectively:

Discovery should mark any data in the CMDB that is not found again with Status set to Absent rather than summarily deleting it.

Steps to Reproduce


  1. Discover a load balancer that is configured with some number of services, pools, pool members, VLANs, or interfaces.

    For more information, see the documentation topic Data collected by Discovery on load balancers.

  2. Perform either of these operations to modify the data:

    • Update the load balancer itself and then rediscover it.
    • Remove data from the applicable exploration probe's previous payload (for example, 'SNMP - F5 BIG-IP - System') and then rerun the appropriate sensor.

    Instead of marking the missing data as Absent and retaining its relationships, note that the previously discovered load balancer services not in the current payload have been deleted from the CMDB, along with all of its relationships (for example, to the parent load balancer).


This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In field to determine whether any versions have a permanent fix.

Related Problem: PRB832300

Seen In

There is no data to report.

Fixed In

Istanbul Patch 11
Istanbul Patch 9

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:34:11