---
title: "Debugging Issues in Discovery and Data Collection"
canonical: "https://docs.infoblox.com/space/netmri754/105941570/Debugging%20Issues%20in%20Discovery%20and%20Data%20Collection"
format: markdown
---
> ⚠️ **Note**
> ⚠️ 
> ⚠️ The Juniper devise discovery polling intervals occur hourly because such devices do not support the ccmHistory SNMP MIB object, which is limited to Cisco devices.

The CC column in the **Network** **Explorer** > **Discovery** table reveals important debugging information for configuration collection issues. The most important discovery and Config Collection issues are listed in this topic, along with where in NetMRI to fix them.

|  |  |
| --- | --- |
| **Config** **Collection** | > Macro (inline-media-image)

Warning icons in the **CC** column indicate possible configuration data collection problems. Other locations that report related messages include** Device** **Viewer** > **Settings** **&** **Status **>** Management** **Status** and **Settings** icon > **Setup** > **Discovery** **Settings** > **Seed** **Router**. Specific messages are described below. |
| **Config** **Not** **Changed** | The configuration for the device has not changed since the previous polling of the device. No problem is indicated here unless you have pushed a changed configuration to the device. Even in those cases, allow some more time for the device to synchronize with NetMRI. If you expect changes to be reflected in device polling. go to **Device** **Viewer **> **Configuration** **Management **> **Config** **Explorer** and check the **Running** **Config Saved?** status line. If the answer is No, ensure the changes in the device's running-config are saved according to the device's configuration data saving requirements. |
| **CLI** **Credentials** **Unknown** | NetMRI cannot obtain the device configuration due to not having the correct CLI username/password tuple, and credential guessing did not work for the device. Go to the **Device** **Viewer** > **Settings** **&** **Status** > **CLI** **Credentials** page for that device. Click **Edit** and enter the necessary values for the SSH and/or Telnet login tuple and the **Enable** **Password** if necessary. Each attempt at connection and collection is listed in the table. Note that the **C** column, for CLI Credentials Status, may show an Error, usually listed as **Failed** **to** **authenticate:** **Invalid** **Username** **and/or** **password**. |
| **Configuration** **Collection** **Disabled** **Globally** | This message appears for devices that support configuration collection, but the collection was skipped because Config Collection is globally disabled in NetMRI. The same message appears in the **Device** **Viewer **> **Settings** **&** **Status** > **Management** **Status** page. Go to the **Settings** icon > **Setup** > **Collection** **and** **Groups** > **Groups** > **Config** **Management** side tab, and enable the **Config** **Collection** checkbox. Also, ensure the proper protocols (SSH, Telnet, HTTP) are enabled for config collection. |
| **Configuration** **Collection** **Enabled** **Globally,** **All** **Protocol** **Options** **Disabled** | This message appears for devices that support configuration collection, but the collection was skipped because Config Collection is globally enabled in NetMRI but no data collection protocols were enabled. The same message appears in the **Device** **Viewer **> **Settings** **&** **Status** > **Management** **Status** page. Go to the **Settings** icon > **Setup**  > **Collection** **and** **Groups** > **Groups** > **Config** **Management** side tab, and enable the **Config** **Collection** checkbox. Ensure the proper protocols (SSH, Telnet, and/or HTTP) are enabled for config collection. |
| **Configuration** **Collection** **Disabled** **at** **Device** **Group** **level** | The device showing this message currently has config collection disabled for the Device Group to which the device belongs. Go to the **Settings** icon > **Setup** > **Collection** **and** **Groups** > **Groups**, click the **Action** icon, and choose **Edit** for the selected Device Group. In the **Group** **Settings** tab, enable the **Config** **Collection** checkbox. |
| **Not** **Included** **by** **Discovery** **Settings** | The message indicates that although the device has been detected by NetMRI, it is not included in any IP **Ranges** or as a **Static** **IP** with the **Exclude** **from** **Discovery** **Settings** option, is not reachable through **Device** **Hints**, or is not detectable as a **Seed** **Router**.   
  
The device in question may also be explicitly excluded from management by previously clicking the **Unmanage** button in **Device** **Viewer** > **Settings** **&** **Status** > **Management** **Status** page. Go to **Settings** icon > **Setup** > **Discovery** **Settings** and change the appropriate settings in any of the four categories. This message appears only during a manual **Get** **Config** operation. |
| **Not** **LIcensed** | The message indicates that the device has not been added automatically to the full NetMRI license for the appliance reporting the Issue. Go to the **Device Viewer **> **Settings** **&** **Status** > **Management** **Status** page and click the **License** button. In the License Status dialog, choose the settings necessary to change the licensing status for the device. This message appears only during a manual **Get** **Config** operation. |