[Fixed in 1.8.3] HPE Aruba 3800 24G 2SFP+ Switch (J9575A)

Unimus support forum
Post Reply
rescar
Posts: 2
Joined: Fri Jul 13, 2018 2:17 pm

Fri Jul 13, 2018 2:21 pm

I can't seem to get this device added, and I think it's because with PKI authentication it's set to auto-enable. Any hints?

Code: Select all

2018-07-13 09:05:13.937  INFO 19232 --- [nio-8085-exec-8] n.u.service.DeviceCredentialService      : Saving new device credentials 'DeviceCredential{username='manager', SSH key = 1675 character(s)}'
2018-07-13 09:05:13.960  INFO 19232 --- [nio-8085-exec-8] net.unimus.business.core.CoreClientImpl  : Discovering 1 devices
2018-07-13 09:05:48.148  WARN 19232 --- [    discovery-7] n.u.c.d.v.juniper.JunosDiscoveryDriver   : Output recognition timeout reached while trying to talk to 'dev100asw002.devices.corp.rescar.com'!
2018-07-13 09:05:48.732  WARN 19232 --- [    discovery-7] n.u.c.d.v.m.MlnxosDiscoveryDriver        : Discovery error on 'dev100asw002.devices.corp.rescar.com' - 'Command not supported by device'!
2018-07-13 09:05:49.883  INFO 19232 --- [    discovery-7] n.u.c.s.cli.CliDiscoveryServiceImpl      : Discovery reports an unsupported device on 'dev100asw002.devices.corp.rescar.com'
2018-07-13 09:05:50.147  INFO 19232 --- [nio-8085-exec-8] net.unimus.service.DeviceService         : Attempt to run 1 discover(y/ies)
2018-07-13 09:05:50.744  INFO 19232 --- [    discovery-7] n.u.c.s.cli.telnet.TelnetConnector       : Not using SSH_KEY based credentials for dev100asw002.devices.corp.rescar.com:23 - not supported by Telnet
2018-07-13 09:05:51.552  INFO 19232 --- [    discovery-7] n.u.c.s.cli.telnet.TelnetConnector       : Not using SSH_KEY based credentials for dev100asw002.devices.corp.rescar.com:23 - not supported by Telnet
2018-07-13 09:06:16.387  INFO 19232 --- [nio-8085-exec-1] net.unimus.service.DeviceService         : Updating device dev100asw002.devices.corp.rescar.com
2018-07-13 09:06:16.398  INFO 19232 --- [nio-8085-exec-1] net.unimus.service.DeviceService         : Updating bound device credential to DeviceCredential{username='manager', SSH key = 1675 character(s)}
2018-07-13 09:06:16.399  INFO 19232 --- [nio-8085-exec-1] net.unimus.business.core.CoreClientImpl  : Discovering 1 devices
2018-07-13 09:06:46.826  WARN 19232 --- [    discovery-8] n.u.c.d.v.juniper.JunosDiscoveryDriver   : Output recognition timeout reached while trying to talk to 'dev100asw002.devices.corp.rescar.com'!
2018-07-13 09:06:47.420  WARN 19232 --- [    discovery-8] n.u.c.d.v.m.MlnxosDiscoveryDriver        : Discovery error on 'dev100asw002.devices.corp.rescar.com' - 'Command not supported by device'!
2018-07-13 09:06:48.534  INFO 19232 --- [    discovery-8] n.u.c.s.cli.CliDiscoveryServiceImpl      : Discovery reports an unsupported device on 'dev100asw002.devices.corp.rescar.com'
2018-07-13 09:06:49.394  INFO 19232 --- [    discovery-8] n.u.c.s.cli.telnet.TelnetConnector       : Not using SSH_KEY based credentials for dev100asw002.devices.corp.rescar.com:23 - not supported by Telnet
Last edited by rescar on Fri Jul 13, 2018 2:28 pm, edited 1 time in total.
User avatar
Tomas
Posts: 607
Joined: Sat Jun 25, 2016 12:33 pm

Fri Jul 13, 2018 2:26 pm

Hi,

What is the discovery job fail reason?
(Dashboard > Last Failed Job > Show log)
rescar
Posts: 2
Joined: Fri Jul 13, 2018 2:17 pm

Fri Jul 13, 2018 2:29 pm

unsupported_device
telnet_known_credentials_refused
User avatar
Tomas
Posts: 607
Joined: Sat Jun 25, 2016 12:33 pm

Fri Jul 13, 2018 2:45 pm

This will be an issue in our ProCurve / ArubaOS driver.
We are very sorry you ran into this.

Could you please run Unimus in debug mode, and send me a log of the failed discovery attempt from debug mode?
(feel free to send it over a PM)

Thanks!

On Linux:

Code: Select all

sudo su
service unimus stop
cd /opt/unimus
java -jar Unimus.jar \
--logging.level.net.unimus.core=TRACE \
--unimus.core.echo-ssh=TRUE \
--unimus.core.echo-telnet=TRUE
On Windows:

Code: Select all

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
bone
Posts: 1
Joined: Fri Aug 17, 2018 8:44 am

Fri Aug 17, 2018 8:50 am

Any news about this type?
We get the unsupported error while trying via SSH (We have 5 stacked switches, 2 fiber and 3 48G switches)
20180817 - Unimus.png
20180817 - Unimus.png (7.76 KiB) Viewed 359 times
2018-08-17 10:20:50.398 WARN 6244 --- [discovery-3] n.u.c.d.v.juniper.JunosDiscoveryDriver : Output recognition timeout reached while trying to talk to '*.*.*.*'!
2018-08-17 10:20:50.985 WARN 6244 --- [discovery-3] n.u.c.d.v.m.MlnxosDiscoveryDriver : Discovery error on '*.*.*.*' - 'Command not supported by device'!
2018-08-17 10:20:54.657 INFO 6244 --- [discovery-3] n.u.c.s.d.CliDiscoveryServiceImpl : Discovery reports an unsupported device on '*.*.*.*'
User avatar
Tomas
Posts: 607
Joined: Sat Jun 25, 2016 12:33 pm

Fri Aug 17, 2018 11:11 am

bone wrote:
Fri Aug 17, 2018 8:50 am
Any news about this type?
We get the unsupported error while trying via SSH (We have 5 stacked switches, 2 fiber and 3 48G switches)
Sadly, the person with the original problem newer got back to us with a debug log.

If you could please send us a debug log of a discovery run that presents the issue, we would be very glad to fix it.
(please find instructions in the above post)

Thanks!
User avatar
Tomas
Posts: 607
Joined: Sat Jun 25, 2016 12:33 pm

Fri Aug 24, 2018 5:09 pm

Thanks to @bone we managed to track down the issues and fix it.

The fix is available in 1.8.3 Beta builds, and will also be a part of 1.8.3 when it releases.
Post Reply