Skip to tutorial content
Rate module Not yet rated

Reading Errors and Discovery Logs

4 min read
On this page

In this lesson, you will learn:

  • Where Discovery errors appear
  • How to read a log line
  • How to sort failures

🔁 Quick look back: Last time: A Troubleshooting Method. You learned a four-question method for any Discovery failure.

1 The Problem: Errors Are Spread Across Many Records

After the pilot, errors appear in several places:

  • The status record shows counts.
  • Device history shows each IP.
  • The log holds the details.

🎯 The problem: Discovery errors are spread across many records.

👉 The fix: Start from the status record, drill into each device, and read its log lines.

Table of error types.
Figure 1. Sorting the pilot failures.

2 Where to look

  1. Open the Discovery status record.
  2. Open the Devices list and find failed IPs.
  3. Open the device history for one IP.
  4. Read its log lines in order.

💡 Good to know: Need a refresher? See Fundamentals › System Maintenance › System Logs for system logs in general.

3 Reading a log line

  • When it happened.
  • Which step: scanning, classification, pattern, IRE.
  • The message: what failed.
  • Which MID Server ran it.

💡 Good to know: Search the log for the IP address to see only that device’s lines.

4 Project Clear View: How We Implemented It

📍 Situation: Three pilot devices failed.

🧭 Decision: Read each device’s history and log, and sort the failures.

🛠️ Steps we took:

  1. Opened the pilot status record.
  2. Found the three failed IPs in the Devices list.
  3. Read each log: two ‘no response’ on WMI, one ‘permission denied’ on a command.
  4. Sorted them as access and exploration problems.

✅ What we verified:

  • Each failure has a type and a log line as evidence.
  • Hana could see why each failed.

📁 Evidence: Log evidence added to the troubleshooting log.

5 Quick recap

  • Start from the status record, then device history, then the log.
  • Read time, step, message and MID Server.
  • Sort into access, credential, exploration and identification.
  • Search the log by IP.

6 Check yourself

Think of your answer first. Then tap to check.

1 Where do you start when a scan has failures? Show answer

The Discovery status record.

2 What type is ‘permission denied’ on a command? Show answer

An exploration problem: the account lacks rights for that command.

3 How can you see only one device’s lines? Show answer

Search the log for its IP address.

Nice work! You can read Discovery errors. 🎉
Next up: Fixing Access and Port Failures

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.