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

I note that this is one of those sessions where you connect, it asks you for a username, you input, hit enter and then you're again presented with a username and then password prompt. It seems the second user/pass is the relevant one. The first one is like a throwaway of some sort. Is this maybe where the break lies?

edit-
Scratch that last bit. understanding the logs better, looks like user and pass are getting sent in the right place it's just failing auth. I'm out of idea

According to the log, it seems that Unimus is doing everything correctly, the device is however refusing the login.

What is strange is that even after the first username, it already outputs "% Authentication Failed".
As you can see in the log, Unimus does attempt to provide username and password the second time, but again gets "% Authentication Failed".

Probably the next step would be doing a Webex session to look at this more in details.
Please contact me over PM or email to work out the details.

Update:
We have finally managed to solve this issue.
Araknis switches were outputting "Press any key to continue..." but were really ignoring this and continuing with the login sequence anyway. This caused a state desync in Unimus, since it was expecting the device to wait for a key press.

Update:
We have finally managed to solve this issue.
Araknis switches were outputting "Press any key to continue..." but were really ignoring this and continuing with the login sequence anyway. This caused a state desync in Unimus, since it was expecting the device to wait for a key press.

Update:
We have finally managed to solve this issue.
Araknis switches were outputting "Press any key to continue..." but were really ignoring this and continuing with the login sequence anyway. This caused a state desync in Unimus, since it was expecting the device to wait for a key press.