Unimus forum

I am new to Unimus. I am planning to deploy this software in a Linux VM...however for a quick look I installed on my local Windows workstation.

I wanted to start with see how the backup up some Ubiquiti AirFiber radios would look.

Does Unimus just try all the credentials until it finds one that works? Or is there a way to specify the credential to use?

Your forum post of supported devices listed the Ubiquiti AirFiber as supported. Is there a certain software on the AirFiber that is required to be supported?

I note the http and https connectors seem to be greyed out and not able to be enabled. Is this functionality not supported on Windows?

Is the Linux version more functional? Are certain platforms for Unimus less functional?

Thanks in advance.

Hi,

We support AirFiber (and all other devices, UBNT or others) through SSH and Telnet.
However, we highly recommend not using Telnet because of security.

HTTP and HTTPS connectors are in the GUI in preparation for IP camera (CCTV) and IP phones backup.
This will be coming in the near future, but we already implemented the GUI for connector config.
It is disabled, since those connectors are not available yet.

Windows and Linux versions are the same in all functions and features.

In short, all current devices are handled over CLI (SSH or Telnet).

Sorry for the confusion!

Ok..thanks...that makes sense.

So how do I troubleshoot why Unimus cannot backup my AirFiber radios I have added?

I can SSH from the machine running Unimus and use those credentials to login.

When I try to backup these devices I get an info message that the request was sent to discovery.

When I click "show log" all I see is: ssh_unable_to_identify_device

It seems that it is common to use the same credentials across many devices. Discovery seems to not figure out the credential to use to make the backup.

This means SSH was able to connect, but device was not discovered by any device driver.
If it's an AirFiber - it's possible UBNT changed something in the newer firmwares.

We will need to get some debugging data, and it should be an easy fix.

You can now enable debug logs by going to "Zones > Default > Debug mode".
Here, enable debug logging and device output logging.

Rerun the discovery, and after it fails, download both logs files and send them to us.

Thanks!

For future reference, the issue was in the AirFiber, it was SegFault-ing upon running 'mca-status' I implemented a fallback mechanism in Unimus, so we can handle AirOS even if this happens.

It will be released in 1.3.1.

I am getting the same error ssh_unable_to_identify_device when trying to connect to a Juniper Ex2200 running JunOS.

i have followed the fix as listed above, what should i do next?

Hi

Please follow the instructions in this post:
viewtopic.php?p=685#p685

Send me the output in a PM and I will be glad to look at the issue.

Tomas, I am having the same issue with HP 5120 Switches, should I follow the same procedure and PM you?

cgarcia7777 wrote: ↑

Wed Oct 31, 2018 9:27 pm

Tomas, I am having the same issue with HP 5120 Switches, should I follow the same procedure and PM you?

Hi,

You can now generate debug logs simply by going to "Zones > Default > Debug mode".
Here, enable debug logging and device communication logging.

After that, run a discovery on the problematic device.
Please PM or email (or create a support request on the Portal) with both log files attached.

Thanks!

I have opened a support request thanks for your help.