Discovery creating duplicates for IP Switches and IP Routers and is often not identifying existing CIs correctly. Issue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Symptoms Duplicate switch and router records being created when discovery schedule is running. Release Any release Cause The reclassification of the CI (CI class is getting toggled between a router and a switch)This causes a situation where the Identification Reconciliation Engine receives two payloads from discovery at the same time with same name for IP Switch and IP Router. During reclassification, it first deletes the existing record and inserts a new one with the same sys id.If there is a second payload that comes between the delete and insert it won't able to match on name, resulting in creating a duplicate. Resolution Usually there is mis-classification between router and switch CI's when the sys object OID is not received in the SNMP - Classify probe payload.Based on the other OIDs that are received, the CI could be wrongly classified.To stop the mis-classification, add the following classification criteria under "Standard Network Switch" and "Standard Network Router" classification: "sysoid" does not equal empty value