disco.config table

The config table configures the general operation of the discovery process.

Table 1. disco.config database table schema
Column name	Constraints	Data type	Description
m_AllowVirtual	Default = 1	Integer	Flag indicating whether to allow virtual IP addresses as part of the discovery. 0: Do not perform any discovery for virtual IP addresses. 1: Perform discovery for virtual IP addresses. This is the default setting. 2: Perform discovery for virtual IP addresses only if the address is defined in the scope.special table. This table defines management IP addresses.
m_BuildLogicalCollections		Boolean Integer	Specifies whether to build logical collection entities to group together items such as VTP domains, OSPF areas, and MPLS VPNs: 0: Do not build logical collection entities. 1: Build logical collection entities.
m_CheckFileFinderReturns	Externally defined Boolean data type default = 0	Boolean Integer	Flag indicating whether to use the Ping finder to check the devices specified in the flat file supplied to the File finder. 1: This setting tells the Ping finder to check the devices specified in the flat file supplied to the File finder. This setting is recommended if you have reason to doubt that some of the devices specified in the flat file are still connected to the network. 0: This setting indicates that you do not want to perform any checking of the devices specified in the flat file supplied to the File finder.
m_CycleLimit		Integer	The number of discovery cycles to complete before instigating a full rediscovery (used by the FinalPhase stitcher).
m_CreateStchrEvents	Externally defined Boolean data type default = 1	Boolean Integer	Specifies whether to create discovery events to be sent to the ObjectServer. This field takes the following values: 0: Do not generate discovery events. 1: Generate discovery events.
m_DirScanIntvl		Integer	The time period between scans for modifications to the stitcher and agent files. If changes are found, the stitcher and agent definitions are loaded and the appropriate changes are made to the stitchers and agents.
m_DiscoProfiling		Boolean Integer	Flag indicating whether to profile the discovery. 1: Profile the discovery. 0: Do not profile the discovery.
m_DiscoOnStartup		Boolean Integer	Specifies whether a discovery should automatically start when the Discovery engine, ncp_disco, is started: 0: Do not automatically start a discovery. 1: Automatically start a discovery.
m_FeedbackCtrl	Default = 0	Integer	Flag indicating whether to use the feedback mechanism during the discovery. The feedback mechanism allows any new IP addresses to be fed back into the discovery and thus increases the size of the discovered network. Devices that are fed back are pinged by the Ping finder. Note: For feedback to work the ping finder must be activated. 0: Feedback is off for all discoveries and rediscoveries. This option provides speed but discovers only those devices specified to the finders, and hence provides an incomplete topology. However, this setting ensures that discoveries and rediscoveries complete in the quickest possible time. 1: Feedback is on for full discoveries, full rediscoveries, and partial rediscoveries. All IP addresses are pinged. This option provides a complete topology in all situations but takes the longest. 2: Feedback is on for full discoveries and full rediscoveries, this ensuring a complete topology in these cases. In the case of partial rediscoveries there is no feedback. This ensures that the partial rediscovery runs in the quickest time possible. This is the default setting.
m_FindersOnStartup		Boolean Integer	Specifies whether the finders should automatically start when the Discovery engine, ncp_disco, is started : 0: Do not automatically start finders. 1: Automatically start finders.
m_EnableCrossDomainProcessing		Boolean Integer	Set to 1 to enable cross-domain processing. If you are performing a cross-domain discovery, you must perform other configuration steps in addition.
m_ManagedWaitTimeOut		Integer	Applicable when the value of the field `m_WaitForManagedProcs` is set to 1. Maximum time to wait for all collectors to complete retrieving data from their EMSs. Effectively a fail-safe mechanism to cover the siutation where one of the collectors never completes processing. By default, this value is set to 0, which means wait indefinitely.
m_MinResidentSize		Integer	The minimum initial size of DISCO in kilobytes (KB). The maximum value that you can specify is 500 MB (512 000 KB). Specifying an initial value speeds up the discovery by allocating the memory of DISCO in one block.
m_ModelVlans	Externally defined Boolean data type	Boolean Integer	Flag indicating whether to switch off VLAN modelling. 1: This setting switches on VLAN modelling. When you make this setting, the AddGlobalVlans, CreateTrunkConnections and AddVlanContainers stitchers are called. 0: This setting switches off VLAN modelling. When you make this setting, the AddGlobalVlans, CreateTrunkConnections and AddVlanContainers stitchers are not called.
m_NothngFndPeriod		Float	The maximum time lapse, in seconds, between the discovery of one device and the discovery of the next device in the device discovery phase.
m_PendingPerCent		Integer	The maximum allowed ratio of pending devices to processing devices. A breach of this threshold condition instigates a full discovery (rather than a partial rediscovery).
m_PingVerification	Default = 2	Integer	Option to check whether an interface is able to be pinged. If the device is not pingable, then Network Manager does not poll the device for alerts 0: Do not check pingability: Network Manager performs no pingability check on any of the interfaces discovered. Interfaces will be polled regardless of whether they are pingable at discovery time. 1: Check pingability: perform a pingability check, following discovery, for every interface discovered. 2: Determine best method: sets the pollability flag for an interface based on whether feedback was active during the discovery..
m_RebuildLayers	Externally defined Boolean data type	Boolean Integer	Flag indicating whether to rebuild topology layers after partial rediscovery. 1: Rebuild the layers. After partial rediscovery, topology layers stitchers are run. Partial rediscovery takes longer but results in a complete topology. 0: Do not rebuild the layers. After partial rediscovery, topology layers stitchers are not run. The result is a much quicker partial discovery; however, connectivity associated with the newly discovered device is not fully seen in the topology.
m_RediscoverRelatedDevices		Boolean Integer	In a partial rediscovery when a device has changed, specifies whether to rediscover the related devices if the connection appears to have changed: 0: Do not rediscover the related devices if the connection appears to have changed. 1: Rediscover the related devices if the connection appears to have changed.
m_RefreshDiscovery	Default = 1	Boolean Integer	Specifies whether the FullDiscovery stitcher restarts the discovery when called after an initial full discovery has completed. The default value is 1: restart the discovery process. Set the value to 0 to not restart the discovery process using the RestartDiscoProcess.stch stitcher. Enabling this option by default is useful for the following reasons: If the discovery is loading custom data into the DiscoContrib.cfg file then this option facilitates the process by having the new discovery process read the file again. The option also helps if the discovery process is accumulating memory because the newly started process resets the process to the initial state Note: The FullDiscovery stitcher only stops and starts the discovery process if there is no discovery in progress at the time it is called.
m_RestartAgents		Integer	A flag that determines whether DISCO attempts to restart discovery agents that fail during their operation.
m_RestartFinders		Integer	Flag to determine whether to restart a failed finder.
m_UseContext		Boolean Integer	Flag indicating whether this is a context-sensitive discovery. 1: Specifies a context-sensitive discovery. 0: Specifies that this is not a context-sensitive discovery.
m_VerifyCDPUsingDeviceId		Boolean Integer	Specifies whether to verify the CDP links using the CDP device ID. Occasionally the CDP device ID has been found to be unreliable. Switching on `m_VerifyCDPUsingDeviceId` will improve CDP connectivity if the Device ID is accurate but might degrade connectivity if the Device ID is inaccurate. 0: Do not verify the CDP links using the CDP device ID. 1: Verify the CDP links using the CDP device ID.
m_WaitForManagedProcs		Boolean Integer	Flag indicating whether to tell the discovery engine ncp_disco wait until the Collector finder status is complete before moving to the next phase of discovery. 1: Wait until the Collector finder status is complete before moving to the next phase of discovery. Setting m_WaitForManagedProcs = 1 when running a multiple collector discovery forces the discovery process to remain in phase 1 until all the collectors have completed data processing on their respective EMSs. 0: Do not wait until the Collector finder status is complete before moving to the next phase of discovery. When this field is set to 1, then the parameter `m_ManagedWaitTimeOut` defines the maximum time to wait for all collectors to complete retrieving data from their EMSs.
m_WriteTablesToCache	Externally defined Boolean data type	Boolean Integer	Flag indicating whether to write a cache of the Discovery engine, ncp_disco, tables to disk. Note: Setting this flag results in discoveries that are slower than a standard discovery. 1: Write cache of ncp_disco tables to disk. The tables that are defined in the failover database are cached and ncp_disco can be restarted at any point. 0: Do not write cache of ncp_disco tables to disk. No tables are cached during the discovery and ncp_disco ignores any existing cache files if it is restarted.
m_UnmanagedSubInts		Boolean Integer	Flag indicating whether to automatically set sub-interfaces to unmanaged when the parent interface is marked as unmanaged by the PopulateDNCIM_ManagedStatus.stch stitcher. 1: Automatically set sub-interfaces to unmanaged if the parent interface is set to unmanaged by the stitcher. 0: Do not automatically set sub-interfaces to unmanaged.