Multi-host run

What it does: runs the same command (one line or several) on many devices at once over SSH and shows the results side by side, so you can compare a whole group in one pass instead of logging into each box in turn. Differences between devices are flagged so an odd one out stands out.

What you need: the devices to target — add them from your Inventory, your saved Hosts (SSH hosts only; Telnet hosts are skipped and named), or type them in manually — plus SSH credentials (one login for the run; a device picked from Saved hosts uses that host's own login). Then enter the command(s) and run.

Safe to run: yes by default — commands are checked against the read-only policy and anything that would change a device is blocked unless you explicitly allow it. Runs happen in parallel; press Stop to cancel a run in progress.

Quick commands: a checklist — tick one to add it as the next line of the command box, untick to take it out, so you can build a batch of several commands (lines you type stay). Each is tagged read-only or changes config by the same read-only gate the run uses. The 12 presets — show version, show ip int br, show cdp neigh, show lldp neigh, show inventory, show int status, show run, copy tftp://TFTP-SERVER/{hostname}.cfg → running-config (replace TFTP-SERVER with your TFTP server's address), {enter}, write memory, uname -a and uptime. {hostname} becomes each device's name when it's a plain host name, otherwise its address. {enter} sends a bare Return to answer a device prompt (like "Destination filename?"); it counts as a change, so Read-only blocks it.

What to expect / reading results: each device gets its own column/panel with its output; the diff flag highlights where a device's result differs from the others — a fast way to catch the one switch with the wrong VLAN, a stale config line, or a host that didn't answer. If a device's prompt doesn't come back in time after a command, that device's result says "⚠ Output may be truncated" and names the command — re-run it, or page the output on the device. Nothing leaves your machine; the SSH sessions go straight to the devices.