I am having similar issues.
We have built a new Windows Server 2012 Std server as a Virtual Machine.
We then installed SIM 7.3 onto this new clean build. After the initial install was completed I noticed there were a number of "sshd" "error" events in the Application Event Log. The event detail is below:
"Event ID = 0
Source = sshd
Level = Error
The description for Event ID 0 from source sshd cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
sshd: PID 4580: error: Could not load host key: /etc/ssh_host_ecdsa_key"
I noted that If I uninstalled OpenSSH the events stopped. I tried re-installing from the 7.3 install files but the errors came back.
When I checked the OpenSSH\etc folder I noted that there was a key for rsa & dsa but no key or pub file for "ecdsa". Hence why there is a problem loading it. It's not there.
After quite a bit of time searching the internet I could not seem to locate anything specifically relating to HP SIM and this error with OpenSSH. We checked through the SIM docs, including the release notes.
What we did:
What we have done now though is to generate an ecdsa key using the command line. A "ssh_host_ecdsa_key" file now exists in the etc folder and the error event has now gone away.
The command we used to generate the key was similar to the one below:
ssh-keygen -t ecdsa -f /etc/ssh_host_ecdsa_key -N ""
We are not sure if this is the correct action but it has resolved it, at this time.
I'm not sure why with a clean build of Windows and a fresh install of HP SIM 7.3 this issue has arisen.
Any feedback on this would be much appreciated.
Is there an issue with the SIM 7.3 install which means it does not create the "ecdsa" key? Should it?
Is the action we took correct or should we have done something else?
Thanks,
John