[Fixed in 1.0.0] HPE 1920 Not Recognised

Unimus support forum
Post Reply
CSFIT
Posts: 2
Joined: Thu Jun 15, 2017 12:55 pm

Thu Jun 15, 2017 1:05 pm

Hi,

We have a HPE 1920-24G-PoE+ (370W) Switch Software Version Release 1115

Latest Firmware (Dec 2016). Unimus will not identify or back this device up. The logs show that it manages to log on ok via telnet but then it cannot find a provider to do the backup. I downloaded the debug version of Unimus and here is the log :

Code: Select all

[size=85]2017-06-15 13:10:17.894 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Discovering available SSH port on '192.168.2.48'.
2017-06-15 13:10:17.895 TRACE 4080 --- [discovery-2] n.u.core.service.cli.ssh.SshConnector    : Checking ssh availability on 192.168.2.48:22 within timeout 20000s
2017-06-15 13:10:18.919 DEBUG 4080 --- [discovery-2] n.u.core.service.cli.ssh.SshConnector    : Failed to connect SSH to 192.168.2.48:22 reason 'Connection refused: connect'.
2017-06-15 13:10:18.920 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : SSH on '192.168.2.48' did not respond on any of configured connector ports.
2017-06-15 13:10:18.921 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Discovering available TELNET port on '192.168.2.48'.
2017-06-15 13:10:18.922 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Checking telnet availability on 192.168.2.48:23 within timeout 20000s
2017-06-15 13:10:19.036 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing expect session
2017-06-15 13:10:19.037 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing telnet session
2017-06-15 13:10:19.039 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Telnet available on '192.168.2.48'
2017-06-15 13:10:19.040 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : TELNET on '192.168.2.48' discovered on port 'Port{id='1', createTime='1497526949', port='23'}'.
2017-06-15 13:10:19.042 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Discovering usable credentials on '192.168.2.48'.
2017-06-15 13:10:19.043 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Trying credentials 'DeviceCredential{username='XXXXX', password = X character(s)}' on '192.168.2.48'
2017-06-15 13:10:19.044 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Connecting Telnet to 192.168.2.48:23 with 'DeviceCredential{username='XXXXX', password = XX character(s)}', connectTimeout 20000
2017-06-15 13:10:19.171 DEBUG 4080 --- [discovery-2] n.u.core.service.cli.CliAuthenticator    : Failed to authenticate to 192.168.2.48:23 - invalid credentials.
2017-06-15 13:10:19.171 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing expect session
2017-06-15 13:10:19.172 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing telnet session
2017-06-15 13:10:19.173 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Trying credentials 'DeviceCredential{username='XXXXX', password = X character(s)}' on '192.168.2.48'
2017-06-15 13:10:19.174 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Connecting Telnet to 192.168.2.48:23 with 'DeviceCredential{username='XXXXX', password = XX character(s)}', connectTimeout 20000
2017-06-15 13:10:19.302 DEBUG 4080 --- [discovery-2] n.u.core.service.cli.CliAuthenticator    : Failed to authenticate to 192.168.2.48:23 - invalid credentials.
2017-06-15 13:10:19.302 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing expect session
2017-06-15 13:10:19.303 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing telnet session
2017-06-15 13:10:19.305 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Trying credentials 'DeviceCredential{username='XXXXX', password = X character(s)}' on '192.168.2.48'
2017-06-15 13:10:19.306 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Connecting Telnet to 192.168.2.48:23 with 'DeviceCredential{username='XXXXX', password = XX character(s)}', connectTimeout 20000
2017-06-15 13:10:19.432 DEBUG 4080 --- [discovery-2] n.u.core.service.cli.CliAuthenticator    : Failed to authenticate to 192.168.2.48:23 - invalid credentials.
2017-06-15 13:10:19.432 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing expect session
2017-06-15 13:10:19.435 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing telnet session
2017-06-15 13:10:19.436 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Trying credentials 'DeviceCredential{username='XXXXX', password = X character(s)}' on '192.168.2.48'
2017-06-15 13:10:19.436 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Connecting Telnet to 192.168.2.48:23 with 'DeviceCredential{username='XXXXX', password = XX character(s)}', connectTimeout 20000
2017-06-15 13:10:24.574 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Discovered usable credentials to TELNET on '192.168.2.48'. Credentials = 'DeviceCredential{username='XXXXX', password = XX character(s)}'.
2017-06-15 13:10:24.576 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : TELNET discovery phase 1 starting on '192.168.2.48'.
2017-06-15 13:10:28.581 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CiscoDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.582 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Driver 'CiscoDiscoveryDriver' returned partial potential for '192.168.2.48'
2017-06-15 13:10:28.582 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'DcnSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.583 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'EdgecoreSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.583 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'HpComwareDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.584 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'HpLockedComwareDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.584 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'MikrotikRosDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.585 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'NetonixSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.585 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'UbntEdgerouterDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.586 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'UbntEdgeswitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.586 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'UbntAirosDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.586 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'HpProcurveDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.587 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'TplinkSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.587 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Driver 'TplinkSwitchDiscoveryDriver' returned partial potential for '192.168.2.48'
2017-06-15 13:10:28.588 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver '_3comDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.588 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'DellSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.589 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Driver 'DellSwitchDiscoveryDriver' returned partial potential for '192.168.2.48'
2017-06-15 13:10:28.589 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'HalonSecurityrouterDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.589 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'RuckusZonedirectorDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.589 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'Pfsense2xxDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.590 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'UbntAirfiberDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.591 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ScreenosDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.592 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'UbntToughswitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.592 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'UbntUnifiSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.594 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'FortigateDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.595 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'FortiadcDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.595 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ZteZxr10DiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.595 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Driver 'ZteZxr10DiscoveryDriver' returned partial potential for '192.168.2.48'
2017-06-15 13:10:28.596 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CiscoSmbDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.596 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Driver 'CiscoSmbDiscoveryDriver' returned partial potential for '192.168.2.48'
2017-06-15 13:10:28.597 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'WatchguardFirewareDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.597 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ExtremeXosDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.598 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ExtremewareDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.599 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'BrocadeDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.599 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CiscoNexusDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.599 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'QuantaDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.600 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'FusionswitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.601 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'PaloaltoFirewallDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.601 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'SophosUtmDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.601 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'JunosDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.602 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CambiumEpmpDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.603 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ExaltExtendairDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.603 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CumulusLinuxDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.604 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ZyxelSwitchDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.605 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CalixE7DiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.606 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Driver 'CalixE7DiscoveryDriver' returned partial potential for '192.168.2.48'
2017-06-15 13:10:28.607 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'NokiaTimosDiscoveryDriver' for initial data analysis on '192.168.2.48'
2017-06-15 13:10:28.607 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : TELNET discovery phase 2 starting on '192.168.2.48'.
2017-06-15 13:10:28.608 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling high potential drivers for discovery phase 2 on '192.168.2.48'
2017-06-15 13:10:28.608 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling partial potential drivers for discovery phase 2 on '192.168.2.48'
2017-06-15 13:10:28.609 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CiscoDiscoveryDriver' for interactive analysis on '192.168.2.48'
2017-06-15 13:10:28.612 DEBUG 4080 --- [discovery-2] n.u.c.d.cisco.CiscoDiscoveryDriver       : Got device prompt on '192.168.2.48'.
2017-06-15 13:10:33.662 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'TplinkSwitchDiscoveryDriver' for interactive analysis on '192.168.2.48'
2017-06-15 13:10:33.666 DEBUG 4080 --- [discovery-2] n.u.c.d.t.TplinkSwitchDiscoveryDriver    : Got device prompt on '192.168.2.48'.
2017-06-15 13:10:33.692 TRACE 4080 --- [discovery-2] n.unimus.core.drivers.util.EnableHelper  : Device '192.168.2.48' in enabled mode
2017-06-15 13:10:38.738 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'DellSwitchDiscoveryDriver' for interactive analysis on '192.168.2.48'
2017-06-15 13:10:38.741 DEBUG 4080 --- [discovery-2] n.u.c.d.dell.DellSwitchDiscoveryDriver   : Got device prompt on '192.168.2.48'.
2017-06-15 13:10:43.774 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'ZteZxr10DiscoveryDriver' for interactive analysis on '192.168.2.48'
2017-06-15 13:10:43.780 DEBUG 4080 --- [discovery-2] n.u.c.d.zte.ZteZxr10DiscoveryDriver      : Got device prompt on '192.168.2.48'.
2017-06-15 13:10:43.814 TRACE 4080 --- [discovery-2] n.unimus.core.drivers.util.EnableHelper  : Device '192.168.2.48' in enabled mode
2017-06-15 13:10:48.865 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CiscoSmbDiscoveryDriver' for interactive analysis on '192.168.2.48'
2017-06-15 13:10:48.870 DEBUG 4080 --- [discovery-2] n.u.c.d.cisco.CiscoSmbDiscoveryDriver    : Got device prompt on '192.168.2.48'.
2017-06-15 13:10:53.942 TRACE 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Calling driver 'CalixE7DiscoveryDriver' for interactive analysis on '192.168.2.48'
2017-06-15 13:10:53.946 DEBUG 4080 --- [discovery-2] n.u.c.d.calix.CalixE7DiscoveryDriver     : Got device prompt on '192.168.2.48'.
2017-06-15 13:10:58.987 DEBUG 4080 --- [discovery-2] n.u.c.service.cli.CliDiscoveryService    : Device '192.168.2.48' was not discovered by any driver in discovery phase 2
2017-06-15 13:10:58.988 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing expect session
2017-06-15 13:10:58.989 TRACE 4080 --- [discovery-2] n.u.c.s.cli.telnet.TelnetConnector       : Closing telnet session[/size]
This is stopping us purchasing the product as we're about to roll out the HPEs throughout our organisation.
Thank-you
User avatar
Tomas
Posts: 1206
Joined: Sat Jun 25, 2016 12:33 pm

Thu Jun 15, 2017 1:12 pm

Hi, I will be glad to help.

Can you please run Unimus directly with

Code: Select all

java -jar Unimus.jar
Or just run Unimus.exe directly on Windows.

It will output device communication into the command-line (it is not output into the log file for security reasons).
Please run a discovery on the 1920 and PM me a full log (everything from the command-line).

Thanks!
CSFIT
Posts: 2
Joined: Thu Jun 15, 2017 12:55 pm

Thu Jun 29, 2017 9:35 am

For anyone reading the thread, Tomas fixed this the same day and it's available in the latest release candidate / V1.0.0 as per the edited title.
Post Reply