Net Devices icon

Net Devices

Manage network devices via SSH

Save Config

AI-generated

Overview

This node operation "Save Config" is designed to save the current configuration of a network device via SSH. It is useful in network management workflows where administrators need to ensure that the running configuration on devices is saved persistently, preventing loss of changes after reboots or failures. For example, after making configuration changes to a router or switch, this operation can be used to save those changes to the device's startup configuration.

Use Case Examples

  1. After updating VLAN settings on a switch, use the Save Config operation to save the changes.
  2. Automate nightly backups of device configurations by saving the running config of multiple devices.

Properties

Name Meaning
Advanced Options Collection of advanced settings to control connection and command execution behavior, including retry counts, timeouts, auto disconnect, and connection pooling.

Output

JSON

  • success - Indicates if the save config command was successful
  • command - The operation command executed, here it will be 'saveConfig'
  • output - Output message or response from the device after saving the config
  • deviceType - Type of the network device
  • host - Host address of the network device
  • timestamp - Timestamp when the operation was executed
  • executionTime - Time taken to execute the save config command in milliseconds
  • connectionRetries - Number of connection retry attempts made
  • commandRetries - Number of command retry attempts made
  • error - Error message if the command failed

Dependencies

  • Requires credentials for network device access including host, username, authentication method, and optionally password or private key.

Troubleshooting

  • Connection failures may occur if device credentials or network settings are incorrect; verify host, port, and authentication details.
  • Command execution may time out if the device is slow to respond; adjust commandTimeout and retry settings accordingly.
  • If the node fails on error, check the 'Fail on Error' advanced option to control workflow failure behavior.
  • Ensure the device supports the save config command; unsupported devices will cause errors.

Discussion