SSH problem on ESXi host before performing upgrade

[jiarongsu71647]

I have install hyperflex  4.5(2e),and esxi is  version 6.7

now I want to upgrade esxi form 6.7 to 7.0,but it error with "Failed to establish SSH connection to host: Host is not reachable, or in lockdown mode"

I tried to add  below config in the esxi host and restart ssh,but it not work

echo "KexAlgorithms +diffie-hellman-group14-sha1" >> /etc/ssh/sshd_config

what can I do next to fixed this problem?

also I want to know what user is the HXPlatform to control esxi host ?    root? or other user?   if not the root ,what is the other user password?

thanks

[marce1000]

   - @jiarongsu71647         FYI : https://www.cisco.com/c/en/us/support/docs/hyperconverged-infrastructure/hyperflex-hx-data-platform/216554-ssh-incompatibility-with-esxi-6-7p04-bu.html

  M.

[jiarongsu71647]

 I  saw this article and I already try ,but It not work,  upgrade  fail with error "Failed to establish SSH connection to host: Host is not reachable, or in lockdown mode"

[marce1000]

  - @jiarongsu71647        What exactly did you try ?   

  M.

[jiarongsu71647]

I tried to echo "KexAlgorithms +diffie-hellman-group14-sha1" >> /etc/ssh/sshd_config   to  the esxi host and reboot ssh  but not work 

[marce1000]

  - @jiarongsu71647     Check if the particular cipher (diffie-hellman-group14-sha1)  is listed (after the changes you made) 
                                     by using the command :  nmap -p 22 --script ssh2-enum-ciphers esxi-host
                                                                           (esxi-host can be the hostname of the esxi server or it's ip address)

 M.

[jiarongsu71647]

thanks marce

i will tried your suggestions 

[jiarongsu71647]

hi marco

   I have tried this command,and I saw the particular cipher  (diffie-hellman-group14-sha1)  is listed in the output

  but I retry the upgrade processes in hyperflex,it also error with "Failed to establish SSH connection to host: Host is not reachable, or in lockdown mode"

what can i do next to fix this problem?

[marce1000]

 - @jiarongsu71647   Contact Cisco TAC , describe what you have done and ask why that workaround didn't help.

  M.