Skip to tutorial content
Rate module Not yet rated

Verifying the Linux CI and Relationships in the CMDB

4 min read
On this page

In this lesson, you will learn:

  • What to check on a discovered CI
  • Where related records appear
  • How to confirm IRE matched correctly

🔁 Quick look back: Last time: Following the Discovery: Status, Logs and ECC Queue. You learned how to follow a scan through status, log and ECC queue.

1 The Problem: A Completed Scan Can Still Leave Bad Data

The scan completed. But completion doesn’t prove the CI is right. It could be:

  • A new duplicate instead of an update.
  • Missing fields because of a rights gap.
  • Without relationships.

🎯 The problem: A completed scan can still leave bad data.

👉 The fix: Check the CI itself: class, fields, related records and relationships.

Table of checks on snwr-mail-01.
Figure 1. Checking snwr-mail-01 after the scan.

2 What to check

  • The class is right.
  • Required fields are filled.
  • Related lists show disks, network adapters, IP addresses and software.
  • Relationships make sense.
  • The Discovery source shows Discovery.
  • There’s no second CI with the same name.

3 Confirming the match

Check the CI’s sys_id is the same as before, and its incidents are still linked. That proves IRE updated the existing CI.

💡 Good to know: Need a refresher? See Fundamentals › CMDB Essentials › CI Classes & Relationships for relationship basics.

4 Project Clear View: How We Implemented It

📍 Situation: The first scan completed. Hana wanted proof the data is right.

🧭 Decision: Check snwr-mail-01 against a short list with Hana.

🛠️ Steps we took:

  1. Opened the CI and checked class and fields.
  2. Checked related lists and relationships.
  3. Confirmed the sys_id and incidents were unchanged.
  4. Searched for any duplicate.

✅ What we verified:

  • Every check passed.
  • Hana signed the first-device check.

📁 Evidence: The first-device checklist, reused for each technology.

5 Quick recap

  • Completed doesn’t mean correct.
  • Check class, fields, related records and relationships.
  • Same sys_id and linked incidents prove IRE matched.
  • Search for duplicates.

6 Check yourself

Think of your answer first. Then tap to check.

1 Why check the CI after a completed scan? Show answer

Completion doesn’t prove the data is right.

2 How do you prove IRE updated the existing CI? Show answer

The sys_id is unchanged and incidents are still linked.

3 What does the Discovery source show? Show answer

That Discovery (ServiceNow) reported the CI.

Nice work! SNWR’s first discovered CI is proven right. 🎉
Next up: Discovering One Windows Server

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.