[Fixed in 0.2.1] Discovery failure: Provision (Procurve)

Beta release announcements and discussion around them
Post Reply
Itcoop
Posts: 32
Joined: Tue Aug 02, 2016 12:39 am

Thu Aug 11, 2016 5:27 pm

I believe the issue may be related to the login order of the settings --> credentials screen. I'm attempting to connect to a Provision 5412ZL series switch running K.16.01.0004 code.

2016-08-11 11:03:20.727 INFO 5348 --- [nio-8085-exec-2] n.u.core.util.DuplicateRequestFilter : Checking discovery request address duplicity 10.xx
2016-08-11 11:03:20.727 INFO 5348 --- [nio-8085-exec-2] n.u.core.util.DuplicateRequestFilter : Not duplicated DiscoveryRequest(context=JobContext(deviceId=5, groupId=1), address=10.xx)
2016-08-11 11:03:36.344 INFO 5348 --- [ discovery-89] n.u.core.util.DuplicateRequestFilter : Removing discovery request address 10.xx
2016-08-11 11:03:36.345 INFO 5348 --- [ discovery-89] n.u.core.util.DuplicateRequestFilter : Address removed 10.xx
2016-08-11 11:03:36.458 INFO 5348 --- [ discovery-89] net.unimus.core.util.MessageLogger : Logging message GenericMessage [payload=DiscoveryResult(context=JobContext(deviceId=5, groupId=1), address=10.xx, port=22, credentials=DeviceCredential{username='manager', password = x character(s)}, deviceVendor=null, deviceType=null, model=null, connectorType=SSH, discoveryLog={SSH=UNABLE_TO_IDENTIFY_DEVICE}, successful=false), headers={unimus-core-discovery-context=BackerContext(isDiscovered=false, sshConnectorConfig=net.unimus.schema.SshConnectorConfig@1cdd267, httpConnectorConfig=net.unimus.schema.HttpConnectorConfig@9c336e, httpsConnectorConfig=net.unimus.schema.HttpsConnectorConfig@79bbd8), id=2f55a4d0-c46d-a81d-f43b-03304d08eb4b, unimus-request-processing-duration=PT15.615S, timestamp=1470935016457}]
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Thu Aug 11, 2016 7:38 pm

Error is {SSH=UNABLE_TO_IDENTIFY_DEVICE}.
This means Unimus was able to log into the device correctly, but the ProCurve driver was no able to discover the device.

I based ProCurve support on J4904A - 2800 series.
It must be that the 5400 series is different enough that the current ProCurve driver implementation is not able to handle it.

I will gladly fix the driver, but I would need SSH access to the device, is that possible?
If so please PM me here on the forums, and we can discuss how to proceed.
Itcoop
Posts: 32
Joined: Tue Aug 02, 2016 12:39 am

Sat Aug 13, 2016 2:42 pm

Sure. I have many procurve series in my lab ( microwaves, comware, brocade, and Ruggedcom) if you would like access to them as well. I'll pm you the address to my lab.
Thank you.
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Sat Aug 13, 2016 11:25 pm

SSH access to those would be very much appreciated, so I can implement proper support.

Thanks in advance!
Post Reply