Skip to tutorial content
Rate module Not yet rated

Fixing Classification Failures

4 min read
On this page

In this lesson, you will learn:

  • What classification failures look like
  • Common causes
  • How SNWR found the missing archiver

🔁 Quick look back: Last time: Fixing Credential Failures. You learned how credential and sudo failures were fixed.

1 The Problem: The Mail Archiver Disappeared

After Priya restarted snwr-mail-02, the SNWR Mail Archiver disappeared from Discovery results. The server was still found, but:

  • The archiver’s application CI wasn’t updated.

🎯 The problem: The Mail Archiver disappeared from the results.

👉 The fix: Check what the classifier expects, and what the server now shows.

Table of classification failure causes.
Figure 1. Why devices or apps go unclassified.

2 Finding the cause

  1. Check device history: which classifier ran?
  2. Compare what the device reported with what the classifier expects.
  3. For apps, check the process list from the scan.

3 Fixing it

  • New model: add an OID classification.
  • App process renamed: update the process classifier.
  • App not running: it’s not a Discovery problem. Tell the owner.

4 Project Clear View: How We Implemented It

📍 Situation: The Mail Archiver vanished after a restart.

🧭 Decision: Check the process list and the classifier.

🛠️ Steps we took:

  1. Read the process list from the latest scan of snwr-mail-02.
  2. Found the process now ran as snwr-archiver-svc after an update.
  3. Updated the process classifier to match both names.
  4. Reran Quick Discovery.

✅ What we verified:

  • The archiver is found again.
  • Arjun was told the process name changed.

📁 Evidence: The classifier fix, recorded in the migration matrix.

5 Quick recap

  • Classification decides the device or app type.
  • Unknown models, no credential or renamed processes cause failures.
  • Compare what the device reports with what the classifier expects.
  • Some ‘failures’ are real changes on the server.

6 Check yourself

Think of your answer first. Then tap to check.

1 A device is saved as generic network gear. Likely cause? Show answer

An unknown model or OID.

2 Why did the archiver disappear? Show answer

Its process name changed to snwr-archiver-svc after an update.

3 What if an app just isn’t running? Show answer

It’s not a Discovery problem. Tell the owner.

Nice work! You can fix classification failures. 🎉
Next up: Fixing MID Server Problems

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.