I have a Cisco ASR9k running IOS-XR 5.3.4. Discovery fails when using the correct credentials. Log says ssh_connection_error. But I can SSH from the server that Unimus is running on just fine. Here's part of the log file:
-09 15:16:45.005 INFO 5947 --- [http-nio-8085-exec-10] n.u.s.p.v.i.VaadinSettingsServiceImpl : User 'hanson' enabling device output logging
2019-10-09 15:16:45.006 INFO 5947 --- [http-nio-8085-exec-10] n.u.s.p.impl.PrivateSettingsServiceImpl : User hanson enabling device output logging
2019-10-09 15:16:45.007 WARN 5947 --- [http-nio-8085-exec-10] net.unimus.core.api.CoreImpl : Enabling device output logging
2019-10-09 15:16:54.743 INFO 5947 --- [SimpleAsyncTaskExecutor-15] n.u.s.p.v.impl.VaadinDeviceServiceImpl : User 'hanson' trigger discovery operation with '1' device(s)
2019-10-09 15:16:54.743 INFO 5947 --- [SimpleAsyncTaskExecutor-15] n.u.s.p.impl.PrivateDeviceServiceImpl : Attempt to run '1' discover(y/ies)
2019-10-09 15:16:54.746 INFO 5947 --- [SimpleAsyncTaskExecutor-15] net.unimus.business.core.CoreClientImpl : Discovering 1 devices
2019-10-09 15:16:59.204 INFO 5947 --- [mailTaskScheduler-1] n.u.c.service.mail.QueuedMailSenderImpl : Sending 'RichMailMessage{from='unimus@hansoninfosys.com', replyTo='unimus@hansoninfosys.com', to=[unimus@hansoninfosys.com], subject='Unimus - job report}'
2019-10-09 15:17:06.469 DEBUG 5947 --- [http-nio-8085-exec-9] n.u.s.p.impl.PrivateSettingsServiceImpl : User hanson getting debug mode
2019-10-09 15:17:06.469 DEBUG 5947 --- [http-nio-8085-exec-9] n.u.s.p.impl.PrivateSettingsServiceImpl : Returning false
2019-10-09 15:17:06.469 DEBUG 5947 --- [http-nio-8085-exec-9] n.u.s.p.impl.PrivateSettingsServiceImpl : User hanson getting device output logging state
2019-10-09 15:17:06.469 DEBUG 5947 --- [http-nio-8085-exec-9] n.u.s.p.impl.PrivateSettingsServiceImpl : Returning true
2019-10-09 15:17:11.674 INFO 5947 --- [http-nio-8085-exec-2] n.u.s.p.v.i.VaadinSettingsServiceImpl : User 'hanson' getting log file
[Solved] Failing to discover IOS-XR
For anyone finding this in the future, adjusting the timeout settings fixed the issue.
We often see similar issues on older / slower / heavily loaded Cisco devices.
This can be fixed by adjusting the "unimus.core.inter-connection-delay" timeout option.
We have a Wiki article that explains how to adjust this:
https://wiki.unimus.net/display/UNPUB/C ... t+timeouts
Setting "unimus.core.inter-connection-delay" to around 1000 should fix this.
We often see similar issues on older / slower / heavily loaded Cisco devices.
This can be fixed by adjusting the "unimus.core.inter-connection-delay" timeout option.
We have a Wiki article that explains how to adjust this:
https://wiki.unimus.net/display/UNPUB/C ... t+timeouts
Setting "unimus.core.inter-connection-delay" to around 1000 should fix this.