Discovery Profile Timeout

MartynLawson

Hi,

 

I've recently our Solarwinds installation to an new application server and the database to a dedicated SQL server. During our test and development stages both the application and the database were stored on the same server and the network discovery worked without any problems, but with our new setup it seems to run for a while and then freezes and times out. Does anyone have any idea why this might be happening? 

 

Cheers in advance 

wbrown

It may or may not resolve your issue, but disabling the topology discovery will GREATLY decrease the time required to discover.  I was having issues where the discovery would appear to hang, but really the backend was still busy crunching the info to build the topology.

Support provided me the below steps to disable topology discovery.  This allowed me to complete discovery in less than an hour with networks that previously couldn't finish in the 10 hour max.

Per support run the following SQL statement:
    DELETE FROM [dbo].[DiscoveryProfileOptions]
    WHERE OptionID IN (15, 16) AND ProfileID = %ProfileID%
               
%ProfileID% should be replaced with correct profile ids from DiscoveryProfiles table.

If we would like to turn it off for all profiles - then just:
    DELETE FROM [dbo].[DiscoveryProfileOptions]
    WHERE OptionID IN (15, 16)