Custom SSH

Execute commands on network devices via SSH with configurable ciphers

Actions5

Execute Command

AI-generated

Overview

This node executes a single SSH command on a remote network device. It is useful for network administrators or automation engineers who need to remotely run commands on devices such as switches, routers, or servers via SSH. For example, it can be used to retrieve device status, configuration details, or perform administrative tasks remotely.

Use Case Examples

  1. Run 'show version' on a Cisco router to get firmware and hardware details.
  2. Execute 'uptime' on a Linux server to check how long the system has been running.

Properties

Name Meaning
Host IPv4/IPv6 address or hostname of the device to connect to via SSH.
Port SSH port number of the device, default is 22.
Cipher Selection Select specific cipher or cipher group for the SSH connection to control encryption algorithms used.
Command The SSH command string to execute on the remote device.
Advanced Security Options Options to configure compatibility level, security level, and allowance of legacy algorithms for the SSH connection.
Connection Options Various connection parameters such as timeouts, prompt regex patterns, retry settings, logging, terminal type, and device-specific optimizations.

Output

JSON

  • success - Indicates if the command execution was successful.
  • host - The hostname or IP address of the device connected to.
  • command - The command that was executed.
  • output - The output returned from the device after executing the command.
  • cipher - The cipher used for the SSH connection.

Dependencies

  • An SSH password credential is required for authentication.

Troubleshooting

  • Common issues include connection failures due to incorrect host, port, or credentials. Verify these parameters before retrying.
  • If the selected cipher is not supported by the device, enabling fallback ciphers can help automatically try other ciphers.
  • Timeout errors may occur if the device is slow to respond or network latency is high; increasing connection and prompt timeouts can help.
  • Invalid command errors occur if the command syntax is incorrect or unsupported by the device; verify command correctness.
  • If the node throws errors about missing credentials, ensure the SSH password credential is properly configured and linked.

Links

Discussion