Troubleshooting a failed DiscoveryIssue 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 foundToo many devices foundThe wrong device is matchedThe CMDB is not populatedDevice lacks the necessary informationDuplicate records appearNot enough records are presentDiscovery stopsResolutionFirst, 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. Determine if Discovery failed during the Are you there phase. More information in KB0535234: Troubleshooting the Shazzam Phase in Discovery. Determine if Discovery failed during the What are you phase. More information in KB0535236: Troubleshooting the Classification Phase in Discovery. Determine if Discovery failed during the Have I seen you before phase. More information in KB0535238: Troubleshooting the Identification Phase in Discovery. Determine if Discovery failed during the What else can you tell me about yourself phase. More information in 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