Troubleshooting data mismatch in the scanner and consolidator

Identify the problem and its scope

Is the data mismatch between the Consolidator and the Scanner, or between the CMDB and the Consolidator? Thus, is the data on the CMDB and Consolidator the same as each other but different from the Scanner, or the data on the Consolidator and Scanner are the same but different from the CMDB? This is important so you know how to investigate. This section helps you investigate differences between the Consolidator and the Scanner.

If your issue involves the data mismatch between the Consolidator and the CMDB, check your CMDB Sync patterns and research other KAs or troubleshooting articles. Ensure that your CMDB Sync connection is working and that Continuous Sync is enabled.

Identify how many Hosts, Network Devices, Software Instances, and so on are different between the Consolidator and the Scanner appliances?

When did the problem start?

Investigate the start of the problem. Do you have reports from the Consolidator or from CMDB (such as, Smart Reporting) that can assist you with determining this?

What changes occurred around the time that the problem started? For example:

• Did you deploy a new TKU or new custom patterns?
• Did you upgrade to a newer version of Discovery?
• Did you encounter any issues with the Consolidator appliance around the time that the problem started occurring?

• Verify that the Scanner is currently linked to the Consolidator.
  (To do this, go to Administration > Discovery Consolidation in the UI, on both the Consolidator and Scanner appliances).
• Ensure that you are running the same Discovery version and TKU level on both, the Consolidator and the Scanner.
  (To do this, go to Manage > Knowledge in the UI and check the version in the top-right corner, and the TKUs under the Knowledge Summary section).
• Ensure that all the core patterns are activated on both, the Consolidator and the Scanner appliances, for the TKU you are running (unless you have deliberately deactivated some patterns for some reason, such as advised by Customer Support).
  (To do this, go to Manage > Knowledge in the UI. Normally all the patterns for each TKU should be active. The important thing is that they are the same on both Scanner and the Consolidator).
• Ensure that any applicable custom patterns are activated on both, the Consolidator and the Scanner appliances.
  (To do this, go to Manage > Knowledge > Knowledge Summary > Custom Modules in the UI).
• Have you uploaded any beta patterns on the Scanner or Consolidator? If so, upload them on both, unless you were advised otherwise by Customer Support.
• Are your model maintenance settings the same on the Scanner and the Consolidator? If you have different ageing parameters, this could explain why some nodes are visible on one appliance but not on the other.
• If you spotted discrepancies in the above, remediate them and try rescanning the devices, and check to see if the data mismatch still occurs. For discovery of clusters, it is sometimes necessary to scan multiple times before the correct model is achieved.

If all the prerequisites are correct and the above KA has not helped to resolve the discrepancy, try manually destroying the Host/Device on both, the Scanner and Consolidator appliances. Then try scanning it afresh and compare the data on the Consolidator and Scanner after the consolidation is complete. 

1. Find the device on the appliance (Scanner and Consolidator appliances in turn) and select Actions > Destroy.
2. Scan the device on its own, from the Scanner.
3. Verify that the scan is consolidated to the Consolidator.
4. Verify the data on the Consolidator and check if it is still different to that of the Scanner.
5. If it is different, check the Discovery Access (DA) page on the Consolidator and compare it with the Scanner. Are there permission errors on the DA page of the Consolidator that do not exist on the Scanner? If so, try searching the BMC Knowledge base for these errors.