Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Multiple discovery payloads with different class types sent at the same time for the same CI cause duplicates in CMDB - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Multiple discovery payloads with different class types sent at the same time for the same CI cause duplicates in CMDB
KB0715237

Multiple discovery payloads with different class types sent at the same time for the same CI cause duplicates in CMDB


396 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

During a Discovery scan for IP Switch/IP Router, there can be more than one payload being sent to the Identification and Reconciliation Engine (IRE) at the same time, for the same CI, but with different class types. This can lead to the creation of duplicates in the CMDB. For example, if two payloads are sent to IRE for the same IP Switch/IP Router, one with class type cmdb_ci_ip_switch, and the other with cmdb_ci_ip_router, it can create duplicates for that CI.

Steps to Reproduce

Perform a Discovery scan for IP Switch or IP Router.

Workaround

This problem has been mitigated in Madrid by the resolution of PRB1301835/KB0723645, reducing the number of payloads sent for the same device via multiple IPs.

As further workaround, add system OIDs to the [discovery_snmp_oid] table, to force a specific class during Classification phase. This prevents the class from flipping between IP Switch/IP Router based on inconsistent SNMP OID responses used to dynamically determine the class.


Related Problem: PRB1296612

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.