Scheduled network discovery can discover new devices from your network, add them to your domain automatically, and enable you to check the latest status of your network devices regularly. With the scheduled discovery task, you can get to know any newly added devices, decommissioned devices and more.

1.Log in to the Domain Management page.

2.In the Domain Management page, click Schedule Task on the Start Page or select Operations > Schedule Task from the quick access toolbar.

3.On the Schedule Task tab, click Add Discovery Task.

4.Enter the task name and description.

5.Follow the tabs in the wizard to configure the settings for the task.

▪Frequency — specify the execution frequency for the task. By default, it is Once.

▪Network Setting — select the proxies and credentials to be used in the discovery.

▪Discovery Seed — select a discovery method and then configure the related options.

Discover all live network

It takes all devices in the domain as seeds to discover new devices by neighbor spreading until the discovery depth is reached.

➢Access Mode:

▪SNMP and Telnet — retrieve vendor and model information via SNMP first, and then log in to devices by using Telnet to retrieve live data.

▪SNMP and SSH — retrieve vendor and model information via SNMP first, and then log in to devices by using SSH to retrieve live data.

▪SNMP and Telnet/SSH — retrieve vendor and model information via SNMP first, and then log in to devices by using Telnet to retrieve live data; if Telnet doesn't work, then use SSH.

▪SNMP and SSH/Telnet — retrieve vendor and model information via SNMP first, and then log in to devices by using SSH to retrieve live data; if SSH doesn't work, then use Telnet.

▪SNMP Only — retrieve live data via SNMP only.

Note: The data retrieved via SNMP only might be incomplete.

➢Discovery Depth — set the discovery depth by entering a value between 0 and 255.
It refers to how deep you want the discovery to go. That is, how many levels of neighbors that will be explored from the seed router. For example, depth 0 indicates only the seed router can be discovered; depth 1 indicates the neighbors of the seed router can be discovered (including NDP neighbors or next hop in the route table).

➢Advanced Options:

▪Run additional operations after discovery — choose to whether to build Site right after the Discover task. It is recommended to keep this option checked, otherwise the discovered devices will not be ready until the benchmark task finishes.

▪Retrieve device/module/interface information — choose to whether to retrieve the device/module/interface information for certain discovery (for example, AWS discovery to merge the multi-source devices and Juniper discovery for complete MIB information).

▪CLI Forced Timeout — the time limit of each CLI command to retrieve live data from a device. The default value is 600 seconds.

▪Use NDP to discover neighbor devices — discover neighbor devices by looking up an NDP table.

▪Find routing protocol neighbor via SNMP — retrieve routing protocol (such as BGP, EIGRP, and OSPF) neighbors via SNMP.

▪Use CLI routing table to discover next-hops — discover neighbor devices from route tables retrieved by CLI commands.

▪Scan destination subnets — continue to scan all destination subnets in the route tables of the devices that are discovered in the last depth.

Note: The option is only available when the Use CLI routing table to discover next-hops option is selected.

▪Scan all connected subnets — continue to scan all directly connected subnets of the devices that are discovered in the last depth.

oMinimum mask bits — scan subnets with mask exceeding the threshold. The default value is 24 and can be configured between 22 and 32.

▪The maximum percentage over node license limit to discover devices: This ratio represents the max percentage of devices that the domain will discover once the node license limit is exceeded. 0 means the system will stop discovering when the discovered devices number equals the license limit.

Discover Selected Live Network

It offers the option to scan the IP range or discover via seed routers by taking the IP addresses you input as seeds to discover new devices by neighbor spreading until the discovery depth is reached. To configure the settings, see Discovering Network Devices for more details.
API Triggered Discovery

It only scans the IP addresses you added to the scanning table.

 

1)Select an access mode according to the configuration on your devices.

▪SNMP and Telnet — retrieve vendor and model information via SNMP first, and then log in to devices by using Telnet to retrieve live data.

▪SNMP and SSH — retrieve vendor and model information via SNMP first, and then log in to devices by using SSH to retrieve live data.

▪SNMP and Telnet/SSH — retrieve vendor and model information via SNMP first, and then log in to devices by using Telnet to retrieve live data; if Telnet doesn't work, then use SSH.

▪SNMP and SSH/Telnet — retrieve vendor and model information via SNMP first, and then log in to devices by using SSH to retrieve live data; if SSH doesn't work, then use Telnet.

▪SNMP Only — retrieve live data via SNMP only.

Note: The data retrieved via SNMP only might be incomplete.

2)Click Add to input the IP address and live access credentials. For details about advanced settings, refer to Advanced Options.

▪Use designated credentials to discover only — if selected, the system will only use the input credentials to access devices; if not selected, the system will try the access credentials in the Network Settings after failed through the input access credentials.

▪Email Alerts — enable the email alert function when the task execution fails or succeeds with warning.

▪Summary — check your configurations.

6.Click Submit. The newly added task is enabled by default.

Tip: After the Discovery task is executed, the system will automatically rebuild IPv4 Layer 3 topology and synchronize with sites.

 

See also:

▪Scheduling Discovery Tasks