Skip to main content
NetApp Knowledge Base

SSH connection refused to SP or BMC after newly introduced controller

Views:
3,265
Visibility:
Public
Votes:
1
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • AFF Models
  • FAS Models
  • ONTAP 9
  • Service Processor (SP)
  • Baseboard Management Controller (BMC)
  • BIOS

Issue

Scenarios
  • Newly installed system prior to booting into ONTAP
  • Replaced motherboard prior to booting into ONTAP
  • Wipeclean performed on SP or BMC
Symptoms
Attempting to SSH into the SP/BMC IP address of a controller under the scenarios list results in the following:
 
ssh -l admin 10.10.10.10
ssh: connect to host 10.10.10.10 port 22: Connection refused
 
If connected to the serial console of the controller at the same time of the SSH attempt, similar errors to the following will be seen in the output:
 
[200912345678][123:456:easyinitd][WARN][easyinitd_wdt.c:monitor_service:119]sshd is not started yet, might still generate keys
sh: can't kill pid 11111: No such process
network: Secure Port is enabled for [ssh] with 22
Unable to load host key "/etc/ssh/ssh_host_rsa_key": invalid format
Unable to load host key "/etc/ssh/ssh_host_rsa_key": invalid format
Unable to load host key: /etc/ssh/ssh_host_rsa_key
Unable to load host key "/etc/ssh/ssh_host_dsa_key": invalid format
Unable to load host key "/etc/ssh/ssh_host_dsa_key": invalid format
Unable to load host key: /etc/ssh/ssh_host_dsa_key
Unable to load host key "/etc/ssh/ssh_host_ecdsa_256_key": invalid format
Unable to load host key "/etc/ssh/ssh_host_ecdsa_256_key": invalid format
Unable to load host key: /etc/ssh/ssh_host_ecdsa_256_key
Unable to load host key "/etc/ssh/ssh_host_ecdsa_384_key": invalid format
Unable to load host key "/etc/ssh/ssh_host_ecdsa_384_key": invalid format
Unable to load host key: /etc/ssh/ssh_host_ecdsa_384_key
Unable to load host key "/etc/ssh/ssh_host_ecdsa_521_key": invalid format
Unable to load host key "/etc/ssh/ssh_host_ecdsa_521_key": invalid format
Unable to load host key: /etc/ssh/ssh_host_ecdsa_521_key
sshd: no hostkeys available -- exiting.
 
Applications such as SecureCRT might report the following during the connection attempt: 
[LOCAL] : RECV: SERVICE_ACCEPT[ssh-userauth] -- OK
[LOCAL] : SENT : USERAUTH_REQUEST [none]
[LOCAL] : 
[LOCAL] : RECV: TCP/IP close
[LOCAL] : Changing state from STATE_CONNECTION to STATE_CLOSED
[LOCAL] : Connected for 5 seconds, 1586 bytes sent, 1079 bytes received
[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : The operation completed successfully.

 

 

 

 
 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.