Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

Discovery creating duplicate Hardware Models instead of matching existing

scotts3003
Tera Contributor

We are encountering an issue with Discovery where it is creating a brand-new Hardware Model (cmdb_hardware_product_model) record for almost every newly discovered CI, rather than linking the CI to our existing Hardware Model record.

This behavior is occurring primarily with storage and infrastructure CIs, specifically Hitachi and NetApp items/BMCs.


Expected Behavior:

During the Discovery payload processing and Identification and Reconciliation Engine (IRE) execution, the system should match the discovered Model Name and Manufacturer against existing records in cmdb_hardware_product_model and populate the model_id reference on the CI with the existing model.


Actual Behavior:

Instead of referencing the pre-existing Hardware Model, Discovery inserts a new model record into the Hardware Model table for each CI run, leading to significant model duplication across our CMDB.


Environment Details:

  • Primary Affected CIs: Hitachi & NetApp storage devices / BMCs / Controllers

  • Target Table: Hardware Model (cmdb_hardware_product_model)

  • Normalization is running

Questions for the Community:

  1. Has anyone seen this specific model-duplication behavior with Hitachi or NetApp Discovery patterns/probes?

  2. Are there known issues with how the Model Name string is normalized or extracted from these specific storage patterns that bypasses standard Model Normalization / IRE matching?

  3. What is the recommended approach to troubleshoot where the payload is failing to match—checking the Model Normalization rules, pattern script outputs, or pre-bind scripts?

Any guidance, PRBs, or troubleshooting steps you could share would be greatly appreciated!


Thanks in advance for your help!

0 REPLIES 0