Here's an explanation of settings in the Common tab.
|Number of threads|
Set the number of parallel running scan threads.
The default number is 4. We recommend setting a maximum of 2 thread per core (e.g. if you're using an 8 Core CPU, the best performance is by 16 threads).
|Instance prefix||A user-defined string that allows to identify different Discovery-Instance after importing Discovery-Settings to Insight.|
|Max scan thread time (m)||The number of minutes after which a scan thread will be canceled.|
With the "Normal"-Setting, the log file will only contain basic information like the ICMP-Result and the Discovery Statistic. With the "Debug"-Setting, the log file will contain more information that can be helpful when getting support for an issue.
|Split log per thread|
If this option is set, the Discovery-Tool will create multiple log files and create a subfolder for each scan.
Each logical thread will result in a log file. The file name will end with the internal number of threads. The main thread will always be the file ending with 0000 and contain information of started threads. It can be used as index for searching a specific scan file.
|Delete logs after (days)|
Log files and folders will be deleted after the configured time.
The default number is 7 days.
|Delete unknown hosts*|
If you select this option, the Discovery tool will remove all Unknown hosts from the result.
Unknown hosts respond to ICMP requests but the credentials to receive details are missing so Discovery doesn’t get basic information (see Basic hosts).
In this case, a new object is created with only a Name attribute and is categorized as an Unknown host.
Configures the timeout for ICMP (Ping) requests in milliseconds.
The default number is 300 milliseconds.
Configures the amount of retries of ICMP Requests when the request wasn't successful.
The default number is 0.
|Delete basic hosts|
If this option is set, Discovery will remove all "Basic Hosts" from the result.
"Basic Hosts" are hosts that responding to ICMP Requests, but the credentials to get full details are missing.
The Discovery-Tool can only try to get a hostname via DNS-Reverse-LookUp and optional a MAC-Address via arp-cache.
|SNMP timeout (ms)|
Configures the timeout for SNMP connections in milliseconds.
The default number is 500 milliseconds.
|Delete VM guests|
With Docker, ESXi, or Virtual Box, there are virtual guests on the system running. The information retrieved from the host itself will describe the VMs—the information stored in the host concerning the VMs.
If you unselect this option, the Discovery scan result will contain this information and the host will be mapped to the Virtual guests object type. These objects won't get any of the information contained in the VMs themselves.
|SSH timeout (s)|
Configures the timeout for SSH connections in seconds.
The default number is 40 seconds.
|Delete duplicate device|
There are network SNMP devices like routers and IP cameras responding on the SNMP protocol. Discovery will create an object from it.
It's possible that the Cisco router has a native operating system that is running on Linux, and you can connect to it via SSH, so you end up with two identical devices. The first time you connected to it via SNMP protocol, and the second time via SSH.
|WMI timeout (s)|
Configures the timeout for WMI connections in seconds.
The default number is 25 seconds.
If that option is set, Discovery try to establish a PowerShell connection to the remote server.
If that was successful the alternative PowerShell-Pattern will be used instead of the WMI-Pattern.
Also it is possible to use Custom PowerShell-Pattern.
|vSphere timeout (s)|
Configures the timeout for vSphere connections in seconds.
The default number is 25 seconds.
|Auto add sudo|
If this option is checked, "sudo" will be added to all SSH-Commands
Please just enable PowerShell if:
If the the described points aren't available, the performance of Discovery will drop dramatically.
|Try VM guest scan|
When you select ESXi, Virtual Box, or HyperV patterns, Discovery will attempt to scan the host which may be hosting many virtual machines. When you’ve installed Guest Additions on guests, the Hypervisor knows the IP address of the guest system. There is no need to configure the IP address of the Guest system in the scan settings as Discovery gets that information from the Hypervisor.
Selecting this option will treat VMs as if they were physical hosts. All related patterns (e.g. Windows, Linux) will be attempted while scanning them.
Note: This option works only on ESXi machines.
If you’re using Discovery 3.1.x, you don’t get the network information for Windows Hypervisor and their respective IPs addresses must be included in the Scan Setting IP Ranges.
Here, you can change your settings password.
*Only available by using the Discovery Tool on a Windows Environment.