I will share what I thought had resolved my problem first. And then go through a general troubleshooting process.
WHAT RESOLVED MY PROBLEM:
I realized my problem was because I had more than one "RouterOS" device - despite the Dude being disabled on the other one. So, while adding a "Discovery," I defined the "Agent" (the actual RouterOS). Choosing the "Default" agent was causing the process to remain at "Finishing 100%" for a long time and sometimes never finished.
GENERAL TROUBLESHOOTING:
There are several reasons why The Dude discovery process may remain in a "finishing" status at 100% progress and not complete. Here are a few possible causes and solutions:
- Large network: If you are scanning a large network, it may take a long time for The Dude to complete the discovery process. In this case, you may need to increase the timeout value or split the network into smaller segments.
- Network connectivity issues: If there are connectivity issues on your network, such as intermittent packet loss or high latency, The Dude may have difficulty discovering devices. Check your network for any issues and resolve them if possible.
- Resource limitations: If The Dude is running on a machine with limited resources, such as CPU, RAM, or disk space, it may struggle to complete the discovery process. Check the resource usage on the machine and consider upgrading if necessary.
- Unsupported devices/Service Probes: The Dude may have difficulty discovering devices that are not supported, such as devices with non-standard SNMP implementations or custom protocols. Make sure that your devices are compatible with The Dude's discovery process.
- Firewall settings: If there are firewall settings that block The Dude's discovery process, it may not be able to complete. Make sure that your firewall is configured to allow The Dude's discovery process to pass through.
ADDITIONAL TROUBLESHOOTING:
If the previous solutions did not resolve the issue, here are a few additional troubleshooting steps you can try:
- Check the Dude logs: The Dude logs can provide valuable information about any issues or errors that may be preventing the discovery process from completing. You can access the logs by going to
"File" > "Settings" > "Logs"
in The Dude client.
- Verify the SNMP settings: The Dude uses SNMP to discover and monitor devices on the network. Ensure that your devices are configured to respond to SNMP requests and that the SNMP community string is correctly configured in The Dude.
- Check for network loops: Network loops can cause discovery processes to hang or time out. Ensure your network is configured correctly to avoid loops and other common network issues.
- Test the SNMP connection: You can test the SNMP connection to a device by using the "Tools" > "SNMP Walk" feature in The Dude. This will allow you to verify that the device is responding to SNMP requests and that The Dude can retrieve information from the device.
- Check for duplicate IP addresses: Duplicate IP addresses on the network can cause The Dude to hang or time out during the discovery process. Make sure that all devices on the network have unique IP addresses.
If none of these solutions fix the issue, it may be helpful to contact MikroTik support for more help.