Troubleshooting an unusually long discovery

A discovery might be taking a long time to complete because an agent is unable to complete processing on a specific device. Use the Agents Status section to determine which agent is taking a long time to complete and which device it is working on.

1. Click the Discovery icon and select Network Discovery Status.
2. Within Network Discovery Status, click the Agents Status tab.
3. Set the Phases drop-down list above the upper Agents table to Interrogating Devices.
   The upper Agents table now displays only agents that are scheduled to complete in the first discovery phase, Interrogating Devices.

   Note: This problem usually occurs during the first discovery phase, Interrogating Devices.
4. Ensure that the State column is sorted in descending order.
   The agents appear by default in descending order of agent state, as listed in the following table.

   Table 1. Agent states

   State	Value	Icon	Description
   Died	5		The agent has terminated unexpectedly. This is a potential discovery problem.
   Finished	4		The agent is still running but has finished processing of all the entities in its queue. The agent is still available to process any further agents placed in the queue.
   Running	3		The agent is currently processing entities.
   Starting	2		The agent is starting up.
   Not running	1		The Agent is not running.

5. Scroll down the table to find the agents that have the status Running .
   These are the agents that are still processing devices. If the discovery has been running for an unusually long time, then there might be just one agent that still has Running status . This is the blocked agent.
6. Select one of the agents with Running status .
   By default, the lower table now displays all the entities that are still queued for this agent.
7. Click the All radio button above the lower table.
   The lower table now shows all entities that have been processed by this agent, that are still being processed by this agents, or that are in the agent queue.
8. Ensure that the State column is sorted in descending order.
   The entities appear by default in descending order of agent state, as listed in the following table.

   Table 2. Entity states

   State	Value	Icon	Description
   Died	5		Processing of the entity terminated unexpectedly. Either the agent was stopped manually, or there is a discovery problem.
   Finished	4		An agent has completed processing this entity.
   Running	3		An agent is currently processing this entity.
   Starting	2		An agent is beginning to process this entity.
   Not running	1		This entity is not currently being processed.

9. Scroll down the table to find the entities that have the status Running .
   These entities are still being processed by this agent. If the agent is stuck on a single device, then there will only be one entity with Running status .
10. Look at the other information in the table to find out more about this entity.
    The Elapsed Time column indicates how long the agent has been processing this device. The SNMP Access column indicates whether the agent was able to gain SNMP access to this device. If the agent was unable to gain SNMP access to the device, there might be a problem with SNMP community string settings. Further investigation of this device is required.
11. If the device has a large number of interfaces, the discovery might appear to be stuck on this device because it takes a long time to download all the information. Configure an interface filter for this device to filter out information that you are not interested in. When you run discovery again, the SNMP helper retrieves less information from the device, and this might solve the problem.