Custom SSH

Execute commands on network devices via SSH with configurable ciphers

Actions5

Execute Multiple Commands

AI-generated

Overview

This node connects to a remote device via SSH and executes multiple commands sequentially. It is designed for network device management, allowing users to run a series of commands with configurable wait times between each. This is useful for automating device configuration, monitoring, or troubleshooting tasks on devices such as switches, routers, and other network equipment.

Use Case Examples

  1. Run multiple diagnostic commands on a Cisco router to gather status information.
  2. Execute a batch of configuration commands on an Aruba switch to update settings.
  3. Send a series of commands to a Juniper device for routine maintenance.

Properties

Name Meaning
Host The IPv4/IPv6 address or hostname of the remote device to connect to via SSH.
Port The SSH port number on the remote device, defaulting to 22.
Cipher Selection Selects the specific cipher or group of ciphers to use for the SSH connection, balancing security and compatibility.
Commands A collection of commands to execute on the remote device, each with an optional wait time after execution before sending the next command.
Advanced Security Options Settings to configure compatibility level, security level, and allowance of legacy algorithms for the SSH connection.
Connection Options Various options to control connection behavior, timeouts, prompts, retries, logging, terminal type, and device-specific settings.

Output

JSON

  • success - Indicates if the command execution was successful.
  • host - The hostname or IP address of the device where commands were executed.
  • results - An array of results for each executed command, including command text and output.
  • commandCount - The total number of commands executed.
  • cipher - The cipher used for the SSH connection.

Dependencies

  • An API key credential for SSH authentication (username and password).

Troubleshooting

  • Connection failures due to incorrect host, port, or network issues. Verify device accessibility and SSH service availability.
  • Authentication errors if credentials are missing or incorrect. Ensure valid SSH username and password are provided.
  • Command execution errors if commands are invalid or not supported by the device. Validate commands before execution.
  • Timeouts if device prompts or responses are slower than configured timeouts. Adjust connection and prompt timeout settings.
  • Cipher negotiation failures if selected ciphers are not supported by the device. Use fallback ciphers or adjust cipher selection.
  • Issues with device-specific prompts or pagination. Configure device type and prompt regex appropriately.

Discussion