There are several reasons why your discoveries could be taking so long to run. Here is a list of potential reasons and Hyperview recommendations to help resolve the issue.

The Hyperview data collector is not close enough to your assets.

• Hyperview recommends that the data collector assigned for discoveries be located near or within the same network range as the discovered devices. This ensures that network latency is not the cause of discoveries taking a long time to complete.

One or many of your assets may be communicating slowly.

• If one or some devices that are being discovered by Hyperview are taking a very long time to report information to the data collector, then the discovery could last a very long time. Hyperview implements timeouts for the discoveries to try to circumvent this from occurring, but sometimes the timeouts are not strict enough for certain devices.

Some device types contain a lot of information.

• Certain device types like network switches or other network gear may contain vast amounts of information that is being communicated to the data collector. The sheer amount of data being collected may be a cause for the discovery taking a long time to complete.

The number of credentials in the discovery are too high.

• Especially for first time discoveries, the number of credentials setup for the discovery could be a factor in the discovery taking a long time to complete. For each new device that is discovered, each set of credentials will be attempted in the discovery process until a working set is identified. On subsequent discoveries this is not much of an issue because the data collector has identified what credentials have worked in the past. Try to limit the number of credentials being used in your discoveries.

The number of IP addresses being scanned is too large.

• If a very large range or list of IP addresses have been configured in the discovery settings, it could slow down the discovery process. Each IP address included in a discovery without a device located there will consume additional time for the data collector to timeout and move onto the next IP address. Try to limit your IP addresses for discoveries to include smaller ranges or ranges of primarily active devices.