CMDB/Discovery: Dell iDRAC CI Missing Host Reference Field

[Vaishnavi20]

Hello Community,
We are experiencing a critical data gap in our CMDB where many discovered Dell iDRAC CIs are missing the Host field value, which is a reference field pointing to the cmdb_ci_computer table). This is severely impacting our xyz team's ability to map vulnerabilities to physical servers.
Example: The iDRAC CI IDRAC-7XXXX04 (10.XX1.XX8.201) has no value in its Host reference field.
We rely on ServiceNow Discovery for these devices, likely using SNMP for the iDRACs. We need assistance identifying where the Discovery Pattern finds the host's identifier, how it sets the reference field, and why this process might be failing.
Key Questions for Troubleshooting the Missing Host Reference
1. Discovery Pattern & Logic (Where is the Host Identifier Found?)

• What is the name of the Out-of-the-Box (OOTB) Discovery Pattern responsible for Dell iDRACs?
• Which step within this iDRAC pattern is responsible for obtaining the identifier of the parent host server? Is it:
• Reading the host's Serial Number via a specific SNMP OID on the iDRAC?
• How does the pattern then use this identifier to look up the corresponding Host CI (cmdb_ci_computer)?
• Crucially, which Pattern Variable (or Pattern Command) is responsible for setting the host reference field on the iDRAC CI record?

2. Analyzing Payloads and Missing Data (Why is the Data Missing?)

• For a failing iDRAC (like IDRAC-7XXXX04), how can we check the latest Input ECC Queue payload to confirm if the iDRAC device returned the necessary identifier (e.g., the Host Server's Serial Number)?
• If the data is missing from the payload, it's a device/network issue.
• If the data is present in the payload, it's a Pattern or IRE issue.
• If the data is present in the payload, which Probe or Pattern step should be reviewed to see if it correctly parses and maps this host identifier into the pattern's temporary variables?

3. Identification & Reconciliation Engine (IRE) Rules

• Since the host field is a reference, the IRE must be used to set it. Are there any known issues where the iDRAC Pattern's payload fails to match the host to an existing cmdb_ci_computer record, even if the identifier (like Serial Number) is correct?
• How can we check the IRE payload/transaction log for the failed discovery to see A) if the host's sys_id was successfully retrieved by the pattern, and B) if the IRE attempted to set the host field and was blocked (e.g., by an IRE rule or data mismatch)?
• Is it possible the Host CI is being discovered after the iDRAC CI, causing a temporary data lag, or are the host CIs themselves missing or not fully identified?

Any insight into the specific OOTB code/logic that creates this essential link between the iDRAC and the host server would be immensely helpful!

@AJ-TechTrek please provide the suggestion. 

Thank you!

[Shashank_Jain]

@AJ-TechTrek , Can you please look into this matter, that would be helpful!