[Solved] Discovery fails on Mikrotik devices

Unimus support forum
Post Reply
acs_user
Posts: 12
Joined: Sat Jul 01, 2017 3:56 pm
Location: USA

Sat Jul 01, 2017 4:16 pm

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
Last edited by acs_user on Thu Jul 06, 2017 2:26 pm, edited 2 times in total.
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Sat Jul 01, 2017 4:35 pm

Hi,

What does it say for the discovery fail reason on the failed job log on the dashboard?
acs_user
Posts: 12
Joined: Sat Jul 01, 2017 3:56 pm
Location: USA

Sat Jul 01, 2017 4:44 pm

Hey Tomas,
It says:
ssh_unable_to_identify_device
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Sat Jul 01, 2017 4:50 pm

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)
acs_user
Posts: 12
Joined: Sat Jul 01, 2017 3:56 pm
Location: USA

Thu Jul 06, 2017 2:23 pm

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.
Post Reply