--- title: "Troubleshooting IP Address with Discovery Diagnostics" canonical: "https://docs.infoblox.com/space/UniversalAssetInsights/1592197224/Troubleshooting%20IP%20Address%20with%20Discovery%20Diagnostics" format: markdown --- Discovery Diagnostics is a troubleshooting feature available as part of Universal Asset Insights to analyze the health, performance, and status of network discovery processes. It provides detailed visibility into how the system scans, identifies, and collects information from network devices, enabling administrators to detect problems, verify configurations, and ensure accurate and timely data collection. When network discovery is enabled, the system periodically polls configured network ranges or cloud environments to detect active devices, gather metadata (such as IP addresses, MAC addresses, operating systems, and services). Discovery Diagnostics allows administrators to review these operations in real time or retrospectively by presenting results from completed polling cycles. Key functions of Discovery Diagnostics include tracking the status of polling operations, identifying errors (such as timeouts, unreachable devices, or credential failures), and validating the configuration of discovery protocols like SNMP. It also displays metrics such as the number of discovered devices, the duration of each polling step, and success/failure indicators for each phase of the process. Discovery Diagnostics is an essential tool for ensuring that network discovery is functioning correctly, efficiently, and securely. It helps administrators troubleshoot issues quickly, optimize discovery settings, and maintain accurate and comprehensive network visibility. # Before You Begin Discovery Diagnostics only returns results when diagnostic telemetry exists for the IP address. Depending on how an IP address was discovered, Discovery Diagnostics may return limited information or no results. This behavior is expected and does not necessarily indicate a configuration or product issue. Discovery Diagnostics may return no data when: - The IP address was discovered through passive discovery, which does not perform live polling. - The IP address originated from a cloud discovery source that imports data through APIs. - The IP address came from a third-party or imported discovery source that does not support IP-level diagnostics. - The associated discovery job has not run recently, or polling is disabled. - The required diagnostic data is not collected based on license entitlements. If no results are displayed, this often means that the discovery method used to identify the IP address does not generate diagnostic telemetry. # Troubleshooting an IP Address Complete the following steps to troubleshoot an IP address: 1. Go to **Integrations > Discovery**. 2. Click **Discovery Diagnostics**. 3. In the Discovery Diagnostics dialog, configure the following: - **Diagnostic Mode**: Choose one of the following options: - **Recent Polls**: Recent Polls displays information from the most recently completed discovery polling cycles. This view is historical in nature, showing finalized results from prior discovery operations. It includes details such as the polling status, duration, any errors encountered, and the number of devices or networks discovered. Administrators typically use this view to review and troubleshoot issues based on completed discovery runs. Since it only includes finished polling cycles, it does not provide insight into ongoing or active processes. - **Recent & Live Polling**: Recent and Live Polling combines both completed polling results and information from polling tasks that are currently in progress. This view is particularly useful for real-time diagnostics, allowing administrators to observe the live status of discovery operations as they happen. It shows which polling steps are currently running, pending, or have encountered issues such as timeouts or authentication failures. This live view helps in proactively identifying and resolving issues before the discovery cycle completes. - **IP Address:** Specify an IPv4 or IPv6 IP address. If this IP address is already discovered, it will be shown in the drop-down. If not, you must enter the IP address manually. This field is mandatory. - **Discovery Service**: Choose the discovery service from the drop-down. This field is mandatory. - **SNMP Credentials**: Choose the SNMP credentials from the drop-down. This option is only available when you choose **Recent & Live Polling**,** **specify the **IP Address**, and select the **Discovery Service** from the drop-down. This field is optional. - **CLI Credentials**: Choose the CLI credentials from the drop-down. This option is only available when you choose **Recent & Live Polling**, specify the **IP Address**, and select the **Discovery Service** from the drop-down. This field is optional. - **Enable SNMP debug**: Choose this option if you want to perform an SNMP debug. SNMP debug refers to the diagnostic process of capturing and analyzing Simple Network Management Protocol (SNMP) communication between a network management system and SNMP-enabled devices (such as routers, switches, firewalls, and servers). It is commonly used by administrators to troubleshoot SNMP-related issues during network discovery, monitoring, or device configuration. When SNMP debug is enabled, the system logs detailed information about the SNMP requests being sent (such as `GET`, `GET-NEXT`, or `WALK`) and the responses received from the target devices. This includes timestamps, OIDs (Object Identifiers), MIB data, community strings (for SNMPv1/v2c), or authentication parameters (for SNMPv3), and error messages if any. This check box is optional. SNMP debug is especially useful in the following scenarios: - **Verifying credentials**: Ensures that the correct SNMP version, community string, or SNMPv3 credentials are being used. - **Diagnosing timeouts or failures**: Helps identify why a device is not responding to SNMP queries, such as misconfigured SNMP agents, blocked ports (typically UDP 161), or access control restrictions. - **Confirming OID responses**: Allows admins to see whether expected values are being returned from the device, which is useful when verifying MIB support or custom monitoring configurations. - **Troubleshooting discovery issues**: SNMP debug helps explain why a device may not be detected or classified correctly during network discovery. 4. Click **Run**. # Viewing Diagnostic Results You can perform the following actions once the diagnostics are completed: - Click Show **Results**. The diagnostic data is shown on the screen. - Click **Download** to download the diagnostic details. The file is saved as `discovery_diagnostics_[DATE].log`. If Discovery Diagnostics does not display any data and continues loading for more than a minute or two, this may indicate that the IP address cannot be diagnosed using this tool based on the discovery method or available data.