Unimus forum

In this case, echoing log messages into the CLI session is what is causing Unimus not to discover the device. You will have to configure the device not to echo logs to CLI. (Unimus can not properly identify the prompt when "random" data are coming into the CLI session) On Cisco this would ...

The particular issue in the original post has also been addressed in 1.10.0 Beta and newer. Link to a Beta build with a fix: https://drive.google.com/drive/folders/1alqDTUohBa5evPXQmHwlPcZa7JmcLzOg (if you are seeing this after 1.10.0 has been released, this is already fixed in stable Unimus releases)

Not sure what is going on then, sorry.
The group is active and we have people in it - there was a new person who joined it a few weeks ago.

PM me your Telegram name / number, and I can invite you to the group directly.

It seems you are looking for a user instead of the group.

If you click the link in the original post, and "View group", it should open the group in Telegram.
You should be able to join it there.

The support group is active and people are chatting it in.

What error did you receive from Telegram when you tried to join?

Greetings,

Could you please enable Device output logging under "Zones > Default > Debug mode"?
After this, run a discovery on this Juniper.

Please open a support ticket on our Portal, and attach the device output log file to the ticket.

Thanks!

Hi,

Would it be possible to setup a Webex session to see how this device is different from other similar Cisco devices?
If so, please create a ticket on the Portal, and we will get back to you to work out the details.

Thanks!

Hi,

Unimus automatically tries all enabled connectors during discovery, and uses the safest one available on the device.

What is the discovery job fail reasons?
Dashboard > Latest failed job > select job > Show log

Thanks for the update, happy to hear it's solved!

Is the server Windows or Linux.

Can you reach https://licensing.unimus.net/status ?