File transfer (SFTP / SCP / TFTP)

What it does: pushes a file to a device or pulls one back. Pick a protocol, a direction (send/receive), the local file, and the remote path. Common jobs: back up a running/startup config, drop a new IOS/firmware image onto flash, or restore a saved config.

Which protocol?

• SFTP — file transfer over SSH. Authenticated and encrypted; the safe default when the device supports it.
• SCP — also over SSH; older but still common on network gear. Use it when SFTP isn't available.
• TFTP — tiny, unauthenticated, unencrypted UDP transfer (port 69). Still the standard for IOS images and quick config moves, but it has NO password and NO encryption — only use it on a trusted management network, never across the internet.

Safe to run: the transfer itself is safe, but overwriting a device's config or image is consequential — double-check the remote path and filename, and keep a backup of what's already there before you replace it.

Reading results: a success line reports the byte count and the source→destination; the progress bar tracks SFTP/SCP and TFTP uploads. Failures (auth, path not found, permission) are shown verbatim. Every transfer is written to the Activity log.