Our Network Operations team currently relies on the SSH functionality available under Node Management in SolarWinds. While this feature provides connectivity through the SolarWinds poller, it has several operational limitations that impact efficiency during day-to-day troubleshooting and device administration:
- Limited support for pasting multiple commands.
- No option to export or save session logs.
- Slower and less responsive compared to standard SSH clients such as PuTTY, MobaXterm, or SecureCRT.
SolarWinds also provides an SSH launch option from the top-right menu that offers a more traditional terminal experience. However, this connection is established from the engineer's local workstation rather than through the SolarWinds poller.
In our environment, network devices are configured to accept SSH connections only from the SolarWinds polling infrastructure. As a result, the alternative SSH option cannot be effectively utilized by the network team.