Troubleshooting
Problem
Establishing SSH connections between the Console and a Managed Host could return error messages that indicate issues with the network, NICs, firewall, or hosts that are down. This article provides an overview of errors like "No route to host","Connection timed out", and "Connection refused".
Symptom
Trying to establish an SSH connection from the Console to a Managed Host fails with a similar error:
ssh: connect to host 192.0.2.11 port 22: No route to hostssh: connect to host 192.0.2.11 port 22: Connection timed outssh: connect to host 192.0.2.11 port 22: Connection refusedssh: connect to host 192.0.2.11 port 22:Connection reset by peer
Document Location
Worldwide
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"Deploy","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
22 February 2024
UID
ibm10960870