[Fixed in 2.3.0] Cisco SG300 no longer being discovered

Unimus support forum
Post Reply
SpotTheCat
Posts: 1
Joined: Sat Jan 07, 2023 7:39 pm

Sat Jan 07, 2023 7:53 pm

Hi,

Since I upgraded to 2.2.4 it appears my Cisco SG300's have stopped being backed up and discovered.

I've updated the firmware on the switches in the hope that they would upgrade the cipher suite but no joy.

I changed all passwords and checked that nothing else has changed.

Debug log extract is below but it doesn't explain why they've stopped being discovered - just "AuthenticationError: 'CONNECTION_ERROR'".

Any idea why this has stopped working and if it can be fixed?

Thanks

Spot

2023-01-07 19:34:53.981 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Task execution started, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290'
2023-01-07 19:34:53.981 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Sending task execution started message to the server, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290'
2023-01-07 19:34:53.981 TRACE 6940 --- [discovery-32] n.u.core.api.ForwardingResponseSender : Sending 'JobStartedMessage(opId=d5270c82-dfb4-406c-aea9-0f16c62110ea, zoneId=Z-8af3c1fa-cb66-46ab-900d-223d9bf73487, jobId=D-fbe29743-4df8-4dbd-a783-8faec1068290)'
2023-01-07 19:34:53.981 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Calling service, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290'
2023-01-07 19:34:53.981 DEBUG 6940 --- [discovery-32] n.u.c.s.d.p.PortDiscoveryProcessor : Discovering available 'SSH' port on 'xxx.xxx.xxx.44'
2023-01-07 19:34:53.981 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Checking ssh availability on 'xxx.xxx.xxx.44':'22' within timeout '10000'ms
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Closing device CLI session
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Closing SSH raw socket
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Ssh available on 'xxx.xxx.xxx.44':'22'
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] n.u.c.s.d.p.PortDiscoveryProcessor : 'SSH' on 'xxx.xxx.xxx.44' discovered on port '22'
2023-01-07 19:34:54.030 DEBUG 6940 --- [discovery-32] u.c.s.d.p.c.CredentialDiscoveryProcessor : Discovering usable credentials on 'xxx.xxx.xxx.44'
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] u.c.s.d.p.c.CredentialDiscoveryProcessor : Testing '1' credentials through 'SSH' on 'xxx.xxx.xxx.44'
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] u.c.s.d.p.c.CredentialDiscoveryProcessor : Trying credentials 'Credential{id=0, username='cisco', password = 5 character(s)}' on 'xxx.xxx.xxx.44'
2023-01-07 19:34:54.030 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Creating SSH session to 'xxx.xxx.xxx.44':'22' with 'Credential{id=0, username='cisco', password = 5 character(s)}', connectTimeout '10000'ms
2023-01-07 19:34:54.030 DEBUG 6940 --- [discovery-32] n.u.c.s.connection.CliConnectionManager : Applying inter-connection delay for '500'ms
2023-01-07 19:34:55.192 DEBUG 6940 --- [discovery-32] n.u.core.cli.login.CliLoginStateMachine : CLI login process for 'xxx.xxx.xxx.44:22' starting in CONNECTED state
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] n.u.core.cli.login.CliLoginStateMachine : CLI login process for 'xxx.xxx.xxx.44:22' moving to USERNAME_REQUIRED state
2023-01-07 19:34:55.530 TRACE 6940 --- [discovery-32] n.u.c.c.l.r.UsernameRequiredResolver : Sending username to 'xxx.xxx.xxx.44:22'
2023-01-07 19:34:55.530 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Closing device CLI session
2023-01-07 19:34:55.530 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Closing SSH shell channel
2023-01-07 19:34:55.530 TRACE 6940 --- [discovery-32] n.u.c.s.connection.ssh.SshConnection : Closing SSH session
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] u.c.s.d.p.c.CredentialDiscoveryProcessor : Error during credential discovery on 'xxx.xxx.xxx.44' using 'SSH'. AuthenticationError: 'CONNECTION_ERROR'
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Removing task from registry, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290'
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Finishing task execution, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290'
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Current task state, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290', state 'RUNNING'
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Sending task response, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290'
2023-01-07 19:34:55.530 TRACE 6940 --- [discovery-32] n.u.core.api.ForwardingResponseSender : Sending 'DiscoveryJobFinishedMessage(opId=d5270c82-dfb4-406c-aea9-0f16c62110ea, zoneId=Z-8af3c1fa-cb66-46ab-900d-223d9bf73487, jobId=D-fbe29743-4df8-4dbd-a783-8faec1068290, metadata=JobMetadata(startTime=1673120093981, duration=1549), result=DiscoveryJobResult(serviceCheckResults=[ServiceCheckResult(connectorConfigId=1, type=SSH, port=Port(id=1, portNumber=22), error=null)], serviceConnectResults=[ServiceConnectResult(connectorConfigId=1, type=SSH, port=Port(id=1, portNumber=22), error=null)], authenticationResults=[AuthenticationResult(type=SSH, credentials=[], error=CONNECTION_ERROR, discoverySuccessfulCredential=null)], deviceUuid=D-fbe29743-4df8-4dbd-a783-8faec1068290, deviceInfoResult=null, deviceExtendedInfoResult=null, deviceFirmwareDataResult=null, deviceAddressesResult=null, modeSwitchResult=null, runtimeError=null))'
2023-01-07 19:34:55.530 DEBUG 6940 --- [discovery-32] net.unimus.core.api.job.DiscoveryJob : Task finished, id 'D-fbe29743-4df8-4dbd-a783-8faec1068290', state 'FINISHED'

Device log show this:

HEADER:
Address: xxx.xxx.xxx.44
Zone number: 0
Job type: DISCOVERY
Job started: 2023-01-07 19:48:30.380
Job finished: 2023-01-07 19:48:32.348
DEVICE OUTPUT START:
<<SSH connect - socket>>SSH-2.0-OpenSSH_5.9p1.RL
<<SSH disconnect - socket>>
TIMESTAMP: 2023-01-07 19:48:31.398
<<SSH connect - session>><<SSH connect - shell channel>>




User Name:<<SSH disconnect - channel & session>>
DEVICE OUTPUT END:
User avatar
Tomas
Posts: 1126
Joined: Sat Jun 25, 2016 12:33 pm

Sat Jan 07, 2023 9:13 pm

SpotTheCat wrote:
Sat Jan 07, 2023 7:53 pm
Since I upgraded to 2.2.4 it appears my Cisco SG300's have stopped being backed up and discovered.
Hi. This is a side effect of the upgrade to our SSH client library in 2.2.3. We updated our SSH crypto support with newer (more secure) protocols, but this broke compatibility with old SSH servers which do not support larger MAC segment sizes.

It was a lot of work, but we fixed this (we basically added dynamic MAC segment size based on chosen MAC) in 2.3.0. This fix is available in the latest 2.3.0-Beta, more info (and download links) here: viewtopic.php?p=3986#p3986
Post Reply