Discovery Configuration

Based on the Discovery configuration, the Servers, Networks, Links, Printers, and Laptop devices in the organization can be identified. The discovered devices are saved in their respective modules. You can configure multiple subnets for a job and configure protocols, such as WMI, SNMP, SSH and Telnet to discover devices in the given subnet range. You can configure the order of execution of the protocols. After the devices are discovered, you can view the listed devices in the Scanned Result section and the devices that are not listed can be viewed in the Errors Result section.

Prerequisites

Requirements for Network Connectivity

Purpose	Source	Destination	Outbound
E-mail Communications	Summit Web	Exchange	POP [110] / 465
Database Communications	Summit Web	Summit DB	SQL [1433]
AD Authentication	Summit Proxy	Active Directory	LDAPS[636] or LDAP[389]
Domain Name Service	Summit Proxy	Domain Name Server	DNS[53]
Availability Management	Summit Proxy	Network Device	SNMP Polling [161]
Availability Management	Summit Proxy	Windows Server	WMI [135-139]
Availability Management	Summit Proxy	Linux/Unix/Mac	SSH [22]
Discovery Common	Summit Proxy	All	PING [ICMP]
Discovery Common	Summit Proxy	Network Device	SNMP Polling [161]
Discovery Common	Summit Proxy	Windows Server	WMI [135-139]
Discovery Common	Summit Proxy	Linux/Unix/Mac	SSH [22]

Windows Servers

Requirement	Description
Common requirements	An administrative service account: Member of local Administrators group (either domain or local) Stored in monitoring accounts (customer can manage the password) Bidirectional Ping [ICMP]: Used for the latency graph up/down alerts
Agent Based (Preferred Option)	Simple low footprint agent Only requires http/s from target to proxy Supports other functions - Asset/Proxy
Windows Management Instrumentation (Alternative Option)	WMI requires Ports 135-139 from Proxy to Target It depends on the port mapper configuration. Fixed or dynamic ports for return communications. Dynamic ports will cause more effort in secure networks.

Linux Servers

Requirement	Description
Common requirements	An administrative service account: Read only but able to run privileged commands. Bidirectional Ping [ICMP] Used for the latency graph up/down alerts.
Agent Based (Preferred Option)	Agent requires http/s from target to proxy.
Secure Shell (SSH) (Alternative Option)	SSH requires Ports 22from Proxy to Target server.

Network and Other Requirements

Requirement	Description
Account requirements	Domain Administrator credential ID is required for the Auto Discovery functionality of the Asset Management. SSH credentials with port number shall be made available for Linux/Unix device discovery. SNMP V2c community read only string or V3 account, password, authorization and privacy information. Account Names and Passwords shall be stored in the Monitoring Account UI, where the passwords can be managed independent of the implementation staff.
Ports that are to be opened	All devices that require Ping: ICMP is required from the Proxy to all the targeted systems ICMP is required from the Summit server to the Proxy Proxy to Summit server (in Azure cloud) Proxy to Web server, port HTTPS [443] is required for traversing the internet. Windows servers to proxy (with agents installed) Port 443 https agent to proxy only If required, port 80 can be configured. Linux servers to Proxy (no agent is installed) SSH port 22 linux server to proxy Linux servers to Proxy with agents installed) Port 443 https agent to proxy Network devices SNMPV2c or v3 port 161 proxy to network device. Note: SummitAI supports only 128-bit encryption.
Recommended browser	Internet Explorer 10x and above

To configure Discovery:

Select Admin > Advanced > Discovery & Monitoring > Discovery.
On the DISCOVERY page, click ADD NEW on the ACTIONS panel.
Select the Tenant and fill in the required details. For more information about the fields and icons on the DISCOVERY page, see Field Description.
Click SUBMIT. The Discovery details are configured.

Figure: DISCOVERY page

Field Description

The following table describes the fields on the DISCOVERY page:

Field	Description
DETAILS
Discovery From (Proxy)	If you select Proxy Server in the Monitoring Source field, the Discovery From (Proxy) field is displayed. Select the Proxy device from the list to discover devices from the selected proxy server.
Job Name	Type in the job name that will perform the Common Discovery.
Type	Select the Type as Subnet. Subnet From: Type in the subnet numbers. Subnet To: Type in the subnet numbers. Select the Type as Subnet Mask. Subnet From: Type in the subnet numbers and select a CIDR value from the CIDR drop-down list. For more information on CIDR, see CIDR Notation table. Note: CIDR field is used for advanced (NMAP based) discovery configurations only to determine the Broadcast address internally. Select the Type as Active Directory. LDAP Path: Select the LDAP path from drop-down list. Enable Consider all IP Addresses till the last octet of the Subnet To check box to consider all IP Addresses specified in the range between Subnet From and Subnet To while discovering devices.
Extended Discovery	The following protocols are available to select: None: Select the None check box if there is no protocol is required. SNMP: Select the SNMP check box and the SNMP version from drop-down list. Specify the SNMP strings and the timeout (in seconds). The Simple Network Management Protocol (SNMP) is a set of protocols for managing and monitoring complex networks. if SNMP check box is selected, then SNMP Version has to be specified. Select the SNMP version from the list: SNMPV1 SNMPV2c SNMPV3 Note: SNMP V3 requires an authentication and login credentials for managing a device on the network. SNMP V3 provides important security features such as confidentiality to prevent snooping by an unauthorized source, message integrity to avoid data tampering, and authentication to validate the source. If SNMPV3 is selected, the AuthType field is displayed. Select the Authentication Type from the list: AuthNoPriv: If selected you have to specify the authentication details. You have to select the SNMP user and authentication mode( SHA or MD5) AuthPriv: If selected you have to specify the SNMP user, authentication mode, privilege password, and privilege protocol. NoAuthNoPriv: If selected authentication and privilege is not applicable. You have to select the SNMP user from the list. You can provide ping time out for each protocol. Select any one monitoring protocol option. Type in the respective protocol details, as required. WMI: Select the WMI check box, the WMI user from the drop-down list, and specify the timeout in seconds. The Windows Management Interface (WMI) is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification. Note: (a) The WMI protocol is used to mainly monitor the event status that is configured in the server. (b) New fields Software Discovery, Advanced Software Discovery, and Additional Discovery check boxes are populated when you select WMI protocol. SSH: Select the SSH check box and the SSH user from the drop-down list, Specify the SSH Port No. and the timeout (in seconds). Select the SSH check box and SNMP version SSH is used in case of other than windows OS. The Secure Shell (SSH) is a Unix Shell program for logging into, and executing commands on, a remote computer. The protocol provides secure encrypted communications between two untrusted hosts over an insecure network. Telnet: Select the Telnet check box and the Telnet user from the drop-down list, Specify the Telnet Port and the timeout (in seconds). Telnet offers users the capability of running programs remotely and facilitates remote administration. Telnet is available for all operating systems and eases integration in varied networking environments. Set Time For: In this section, you can specify the ping retry and ping timeout (in micro seconds). Thread Timeout: It is required when the multi-threaded Discovery is performed. If a thread is not discovered in one attempt, the SummitAI application retries the Discovery attempt until the time (in seconds) specified in this field. If the respective thread is not discovered within the specified time, a thread timeout error message is displayed. By default, the Thread Timeout value is 300 seconds.
Ping Protocol	The Ping Protocols are used for diagnostics (like Ping), error messages, moving data between applications, and so on. Select the Ping Protocol from the drop-down list. Note: Port 7 (TCP/UDP Ping) is used for 'echo service'. If there is any environment restriction on using ICMP based ping, TCP Ping can be leveraged.
Enable Nmap Discovery	Enable this check box to discover the devices based on the reachability of the Nmap exe followed by the selected protocol.
Nmap Exe Path	If there is no path defined for the Nmap Exe, the application considers the Root path.
Discovery Scripts	Lists the configured scripts. Select the script from the list to monitor the parameters defined in the scripts through discovery and click the ADD TO LIST button to add the selected script for execution. Select the script from the list and click the DELETE button to remove the script from the ADD TO LIST section.
Discovery SNMP	Lists the configured SNMP. Select the SNMP from the list to monitor the parameters through discovery and click the ADD TO LIST button to add the selected SNMP for execution. Select the SNMP from the list and click the DELETE button to remove the SNMP from the ADD TO LIST section.
Note: The Discovery Scripts and Discovery SNMP fields are displayed based on the selected Protocols. If a Script or an SNMP MIB is configured for the selected protocol then Discovery Script or Discovery SNMP fields are displayed respectively.
Protocol Execution Order	Allows to specify the order of protocols if more than one protocols are selected. You can move the protocol up and down to specify the order.
Add For Monitoring	If selected, you can assign a default template to the discovered servers.
Default Configuration Template	Select a default configuration template from the drop-down list.
Software Discovery	If this check box is selected, only the basic Software details are discovered. It is a WMI-based Discovery that gives data of only added and removed Software, which in turn contributes in enhancing the system performance. If this check box is not selected, the SummitAI application ignores the added and removed Software for discovery. Note: On the DISCOVERY page (Type: Subnet/Active Directory/Subnet Mask), the Software Discovery check box is displayed only after selecting the WMI check box in the Protocol field.
Advanced Software Discovery	If this check box is selected, the Application fetches the registry and provides extensive Software Discovery details. Note: On the DISCOVERY page (Type: Subnet/Active Directory/Subnet Mask), the Advanced Software Discovery check box is displayed only after selecting the WMI check box in the Protocol field.
Additional Discovery	In the traditional Hardware Discovery only the basic parameters, such as CPU, model number, memory size, serial number, and so on, are discovered. If this check box is enabled, more details of the Hardware, such as local users, services, and so on, are discovered. If this check box is not selected, the Application does not perform additional Discovery and the Hardware is discovered in a traditional way. Note: On the DISCOVERY page (Type: Subnet/Active Directory/Subnet Mask), the Additional Discovery check box is displayed only after selecting the WMI check box in the Protocol field.
ADD TO LIST	Click the ADD TO LIST button to execute the protocols. All the selected protocols are added in the table below the button.
Delete	Allows you to delete the protocol from the table. Select the check box for the protocol you want to delete and click the DELETE button.
Notify Once Complete	If selected, after completing the discovery task an e-mail notification is sent to the Administrator.
Execute Job	Select Now to execute the job now. If you select Later to run the job later. Specify the values for the following fields: Run As User: Type in the user name. Password: Type in the password to run the job. Re-enter Password: Re-type the password. Start Date: Specify the date when the job should be started. End Date: Specify the date when the job should end. Repeat Job: If you select Repeat, you need to specify the frequency of repeating the job. Note: These fields will vary based on the selected option.

CIDR Notation table

CIDR Notation	Subnet	IPs in Range	Example Input	CIDR IP Range
24	1	256	192.168.50.0/24	192.168.50.0 - 192.168.50.255
23	2	512	192.168.50.0/23	192.168.50.0 - 192.168.51.255
22	4	1,024	192.168.50.0/22	192.168.48.0 - 192.168.51.255
21	8	2,048	192.168.50.0/21	192.168.48.0 - 192.168.55.255
20	16	4,096	192.168.50.0/20	192.168.48.0 - 192.168.63.255
19	32	8,192	192.168.50.0/19	192.168.32.0 - 192.168.63.255
18	64	16,384	192.168.50.0/18	192.168.0.0 - 192.168.63.255
17	128	32,768	192.168.50.0/17	192.168.0.0 - 192.168.127.255
16	256	65,536	192.168.50.0/16	192.168.0.0 - 192.168.255.255

Note:

You can configure CIDR notations other than default available CIDR notation by inserting the following key in the SummitAI Proxy Server.Config.exe: <add key="isCIDRConfigurable" value="True" />.

ACTIONS

This section explains all the icons displayed on the ACTIONS panel of DISCOVERY page.

SHOW LIST

Click SHOW LIST to display the LIST table showing all the configured discovery values for the selected Tenant.

DISCOVERY page: List of Common Discovery configurations
Figure: DISCOVERY page: List of Common Discovery configurations

Click the View Jobs icon to view the job details. The Job Name column displays the name of the job. The Status column indicates that the job is either Not Started or Error or Completed.
Click the Delete icon to delete the job from the list.
Click the Re-run icon to re-run the job.
Click the Edit icon to edit an existing job configuration.
Click ADD NEW on the ACTIONS panel to configure a new Common Discovery value.

On the Job Details pop-up, you can view the subnet details, device details discovered in the specified sub net range, and error details. If the devices present within the given sub-net range are not discovered, the reason for the error is displayed.

Click the Scanned hyperlink to view the device details.
Click the IP ADDRESS hyperlink to view the device details such as hardware, software, error, and other details.

JOB DETAILS pop-up page
Figure: JOB DETAILS pop-up page

You can also view Hardware, Software, Error, and Other Details of the selected IP Address or Job Name.

JOB DETAILS: Additional parameters
Figure: JOB DETAILS: Additional parameters

On the Device Details pop-up, you can view the list of parameters and value of the corresponding parameter. You can also view the parameter values for the selected discovery script and discovery SNMP. Based on the selected script, you can view the parameter values under the SCRIPT BASED DISCOVERY VALUE section. Similarly, you can view the parameter values of the selected SNMPs under the SNMP BASED DISCOVERY VALUE section. The parameter values are categorized into single value output, multi-value output and free form text. Based on the parameter value type, the discovered device details are categorized and displayed in each section.

Filters

Click the Filters icon to specify a particular filter criteria to display Common Discovery values. The FILTERS pop-up page is displayed. Select the filter criteria and click SUBMIT.

Figure: FILTERS pop-up page

Elbrus