A ServiceNow administrator notices that a CI record in the CMDB is not being updated by a scheduled discovery job. The CI is a Linux server that is reachable on the network. Which is the most likely cause?
Trap 1: The discovery source is not configured for this IP range.
This is a possible cause but not the most likely if the CI exists and discovery is running.
Trap 2: The Identification and Reconciliation Engine (IRE) is disabled.
IRE is not required for discovery to update existing CIs.
Trap 3: The cmdb_ci table ACL is set to private.
ACLs do not prevent discovery from updating CIs.
- A
The discovery source is not configured for this IP range.
Why wrong: This is a possible cause but not the most likely if the CI exists and discovery is running.
- B
The Identification and Reconciliation Engine (IRE) is disabled.
Why wrong: IRE is not required for discovery to update existing CIs.
- C
The cmdb_ci table ACL is set to private.
Why wrong: ACLs do not prevent discovery from updating CIs.
- D
The CI is classified under a different CI class in the CMDB.
If the CI is misclassified, discovery may update a different record or create a duplicate.