Creating a Discovery Task

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 of devices via SNMP first, and then log into devices by using Telnet to retrieve live data.

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

▪SNMP and Telnet/SSH — retrieve vendor and model information of devices via SNMP first, and then log into 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 of devices via SNMP first, and then log into 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:

▪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 option Use CLI routing table to discover next-hops 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.

▪Use NDP to discover neighbor devices — discover neighbor devices by looking up 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.

It takes 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 Discover all live network for more details.

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 of devices via SNMP first, and then log into devices by using Telnet to retrieve live data.

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

▪SNMP and Telnet/SSH — retrieve vendor and model information of devices via SNMP first, and then log into 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 of devices via SNMP first, and then log into 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.

▪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.