4849 views

Troubleshooting a failed Discovery


Description

This article guides you through the process of troubleshooting a failed Discovery with probes and sensors (not patterns). It provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking and device is correct.

 

Video Tutorial: Troubleshooting a failed Discovery: Introduction


 

 

Symptoms
Symptoms may include the following:
  • No device found
  • Too many devices found
  • The wrong device is matched
  • The CMDB is not populated
  • Device lacks the necessary information
  • Duplicate records appear
  • Not enough records are present
  • Discovery stops

 

Resolution

First, determine whether any of the troubleshooting steps below are true for your environment. Each step provides a link to an article that will help you eliminate possible causes and take corrective action as necessary. 

  1. Determine if Discovery failed during the Are you there phase. For more information, please review the article, KB0535234: Troubleshooting the Shazzam Phase in Discovery
  2. Determine if Discovery failed during the What are you phase. For more information, please review the article, KB0535236: Troubleshooting the Classification Phase in Discovery
  3. Determine if Discovery failed during the Have I seen you before phase. For more information, please review the article, KB0535238: Troubleshooting the Identification Phase in Discovery
  4. Determine if Discovery failed during the What else can you tell me about yourself phase. For more information, please review the article, KB0535240: Troubleshooting the Exploration Phase in Discovery.  
Note: If your problem still exists after trying the steps in this article: Submit an incident to Customer Support and note this Knowledge Base article ID (KB0535181) in the problem description. For more information, see Submitting an Incident.

 

Article Information

Last Updated:2017-10-31 08:30:44
Published:2014-03-10