[Fixed in 1.4.0] Unable to add ProCurve 2824

[smccloud]

After using Unimus at home I decided I'd like to use it at work for the few devices we have here that can be backed up by it. The main one we have is a HP ProCurve 2824. I can connect to it via telnet without issue, but Unimus is saying it cannot create a telnet or ssh session to it. Are there any logs I can provide to help troubleshoot this?

[Tomas]

Hi,

Logs are in:
Linux - /var/log/unimus/unimus.log
Win - C:\ProgramData\Unimus\log\unimus.log

Unimus can also be run in debug mode if the standard logs do not show sufficient data.

Please let me know what OS and what distribution you are running.

Thanks!

[smccloud]

I'm currently running the croc/unimus Docker image, however if needed I can switch to a standard install on a Windows machine. The logs in the container currently just show

Code: Select all

2017-10-17 14:51:28.302  INFO 7 --- [http-nio-8085-exec-1] net.unimus.service.DeviceService         : Adding new device 192.168.25.254

[Tomas]

In 'start.sh', add at the end ' --logging.level.net.unimus.core=TRACE'.
Restart Unimus/container.

That will set debugging mode, and much more debugging output should be present.

[smccloud]

In 'start.sh', add at the end ' --logging.level.net.unimus.core=TRACE'.
Restart Unimus/container.

That will set debugging mode, and much more debugging output should be present.

Actually, just after I posted that the container crashed (seems to be an issue with Docker on Synology devices) so its now running on a Ubuntu 16.04 install.

Running with java -jar /opt/unimus/Unimus.jar --logging.level.net.unimus.core=TRACE shows the following.

Code: Select all

2017-10-17 10:22:54.959 DEBUG 17430 --- [    discovery-2] n.u.c.service.cli.CliDiscoveryService    : Discovering available SSH port on '192.168.25.254'.
2017-10-17 10:22:54.959 TRACE 17430 --- [    discovery-2] n.u.core.service.cli.ssh.SshConnector    : Checking ssh availability on 192.168.25.254:22 within timeout 10000s
2017-10-17 10:22:54.960 DEBUG 17430 --- [    discovery-2] n.u.core.service.cli.ssh.SshConnector    : Failed to connect SSH to 192.168.25.254:22 reason 'Connection refused (Connection refused)'.
2017-10-17 10:22:54.961 DEBUG 17430 --- [    discovery-2] n.u.c.service.cli.CliDiscoveryService    : SSH on '192.168.25.254' did not respond on any of configured connector ports.
2017-10-17 10:22:54.961 DEBUG 17430 --- [    discovery-2] n.u.c.service.cli.CliDiscoveryService    : Discovering available TELNET port on '192.168.25.254'.
2017-10-17 10:22:54.961 TRACE 17430 --- [    discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Checking telnet availability on 192.168.25.254:23 within timeout 10000s
2017-10-17 10:23:04.971 TRACE 17430 --- [    discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Telnet presence check on '192.168.25.254' failed within timeout 10000ms
2017-10-17 10:23:04.971 TRACE 17430 --- [    discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing expect session
2017-10-17 10:23:04.971 TRACE 17430 --- [    discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing telnet session
2017-10-17 10:23:04.972 DEBUG 17430 --- [    discovery-2] n.u.c.service.cli.CliDiscoveryService    : TELNET on '192.168.25.254' did not respond on any of configured connector ports.

[Tomas]

Can you please paste a copy of how the login procedure to the device over Telnet looks like?

Thanks!

[smccloud]

ProCurve J4903A Switch 2824
Software revision I.10.77

Copyright (C) 1991-2009 Hewlett-Packard Co. All Rights Reserved.

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the Government is subject to restrictions
as set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and
Computer Software clause at 52.227-7013.

HEWLETT-PACKARD COMPANY, 3000 Hanover St., Palo Alto, CA 94303

We'd like to keep you up to date about:
* Software feature updates
* New product announcements
* Special events

Please register your products now at: www.ProCurve.com




Press any key to continue

Username:
Password:

[Tomas]

That looks correct... we will need to do some more debug.

Can you please run Unimus like this:

Code: Select all

java -jar Unimus.jar \
--logging.level.net.unimus.core=TRACE \
--unimus.core.echo-ssh=TRUE \
--unimus.core.echo-telnet=TRUE

This will output debugging data and device communications to the console.
Please run a discovery and send me the output.

Feel free to PM me the log, and please strip any sensitive info.

Thanks!

[smccloud]

PM Sent

[Tomas]

Just an update for anyone watching this thread - issue has been fixed, fix will be released in 1.4.0.

The issue affected ProCurve only over Telnet.
ProCurves over SSH work in all current releases.

All thanks go to smccloud for working through this issue with me!