CSR1000v not connected via ssh

[yennym3]

I have built the image of csr1000v-universalk9.17.04.03-serial.qcow2 ,but when I try to access by ssh I get the following error:

The address 172.18.0.64 is the exposed address to access, it makes the connection but closes it.
ssh [email protected]
kex_exchange_identification: Connection closed by remote host

ssh -vvvv [email protected]
OpenSSH_8.2p1 Ubuntu-4ubuntu0.5, OpenSSL 1.1.1f 31 Mar 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname 172.18.0.64 is address
debug2: ssh_connect_direct
debug1: Connecting to 172.18.0.64 [172.18.0.64] port 22.
debug1: Connection established.
debug1: identity file /home/mw/.ssh/id_rsa type -1
debug1: identity file /home/mw/.ssh/id_rsa-cert type -1
debug1: identity file /home/mw/.ssh/id_dsa type -1
debug1: identity file /home/mw/.ssh/id_dsa-cert type -1
debug1: identity file /home/mw/.ssh/id_ecdsa type -1
debug1: identity file /home/mw/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/mw/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/mw/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/mw/.ssh/id_ed25519 type -1
debug1: identity file /home/mw/.ssh/id_ed25519-cert type -1
debug1: identity file /home/mw/.ssh/id_ed25519_sk type -1
debug1: identity file /home/mw/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/mw/.ssh/id_xmss type -1
debug1: identity file /home/mw/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5
kex_exchange_identification: Connection closed by remote host

I have tried #300 but the ssh connection still does not work and the CPU usage decreases very little.

Am I making a mistake?, how can I fix it?

[mzagozen]

@yennym3 can you provide the full command you use to start the container? Try including --trace as an argument (docker run --privileged -it ... vr-csr... --trace) and you should get more debug output. I am particularly interested in the last section where the bootstrap config is applied.

[yennym3]

@yennym3 can you provide the full command you use to start the container? Try including --trace as an argument (docker run --privileged -it ... vr-csr... --trace) and you should get more debug output. I am particularly interested in the last section where the bootstrap config is applied.

Hi,

Sorry, the error was related to hellt/vrnetlab. This is related to hellt#130, thank you!!