Page 1 of 1
[Solved] Discovery fails on Mikrotik devices
Posted: Sat Jul 01, 2017 4:16 pm
by acs_user
Hello All,
New to Unimus. I've got Unimus version 0.3.3 installed on a Raspberry Pi 3 using the Debian install and I can't get any devices discovered. I've added both a RB3011 and a UBNT Cloudkey as well as the creds for each. I keep getting discovery fail. What am I missing? I can reach each device through ssh from the Pi.
Thanks
Re: Diccovery fails on devices
Posted: Sat Jul 01, 2017 4:35 pm
by Tomas
Hi,
What does it say for the discovery fail reason on the failed job log on the dashboard?
Re: Diccovery fails on devices
Posted: Sat Jul 01, 2017 4:44 pm
by acs_user
Hey Tomas,
It says:
ssh_unable_to_identify_device
Re: Diccovery fails on devices
Posted: Sat Jul 01, 2017 4:50 pm
by Tomas
UBNT CloudKey is not supported, but just about any other UBNT device is.
MikroTik is also fully supported, so that should work.
Please do the following as root:
Code: Select all
cd /opt/unimus
service unimus stop
rm Unimus.jar
wget unimus.net/download/1.0.0-rc-debug/Unimus.jar
java -jar Unimus.jar
This will run Unimus in foreground in full debugging mode.
Please note it will take a few minutes to start up on the Pi (due to its processing power).
Run a discovery on the MKT after it starts, and please send me the logs that will be output to stdout.
(strip any sensitive information)
Re: Diccovery fails on devices
Posted: Thu Jul 06, 2017 2:23 pm
by acs_user
After working with Tomas, I was able to discover my RB3011 in Unimus. I had enabled strong-crypto and by default JRE doesn't support anything over AES-128.
See this forum thread. The fix was quick and painless.
Here's the site I referenced.