[Fixed in 1.8.3] RBwAPG-60ad Not discovering

[sbrconsulting]

I have a network with 2 of these. If I log in and watch the log, I can see Unimus successfully logging in, but Discovery fails.
Running 6.42.6 with board firmware 6.42.6.
If you need anything else to try to debug, let me know.

[Tomas]

We have a couple of these in the office here, and they are working properly.
Could you please run Unimus in debug mode, and send us a log of a discovery attempt?

Thanks!

[sbrconsulting]

I would be happy to.
Where do I find instructions for doing that?

[Tomas]

On Linux:

Code: Select all

sudo su
service unimus stop
cd /opt/unimus
java -jar Unimus.jar \
--logging.level.net.unimus.core=TRACE \
--unimus.core.echo-ssh=TRUE \
--unimus.core.echo-telnet=TRUE

On Windows:

Code: Select all

1) Download .jar distribution:
   https://unimus.net/download.html
2) Stop Unimus service
   If you are running the Portable version, skip this
3) Open an admin command prompt
4) change to folder where Unimus.jar was downloaded
5) Run "java -jar Unimus.jar --logging.level.net.unimus.core=TRACE --unimus.core.echo-ssh=TRUE --unimus.core.echo-telnet=TRUE"
6) Logs should be in the command prompt window

[sbrconsulting]

On both of the units when I opened a terminal window, it prompted, "Do you want to see the license (y/n)? or something similar, so it never responded to the request. Once I answered the question, it is not asked again. The 2 devices are now discovered in Unimus.

Thanks Tomas for quick responses

[Tomas]

Thanks for the update.
We will add handling for this to our RouterOS driver, so Unimus can deal with this without the need for user interaction.

[Tomas]

Update:
This is now implemented, will be a part of 1.8.3 release.