broadcast issues 2026.3
I connected to four devices and then ran one command on one. Started broadcast and then hit enter several times and it worked. Up arrowed to bring up the command and it ran but only on the active session.
All Comments (5)
When i typed the command it broadcasted to all
Well, maybe because i ran the command pre broadcast. I did it on another set of switches and it worked. but I did broadcast first. IDK
Hello,
Thank you for reaching out!
What you are seeing is expected rather than a bug. Broadcast forwards your keystrokes to every session in the group, as described in broadcast actions in SSH sessions, but what it cannot do is share history. Shell history lives on each remote host, not inside RDM. Pressing up recalls whatever that particular switch last ran, so only the one you had already run the command on had anything to pull back. The other three sat at an empty prompt, and the enter that followed did nothing.
That also explains your second set of switches. You turned broadcast on first, so the command landed in every session's history, and recall then found it everywhere. Even in the general case, four hosts will often have four different last commands, which is rarely what you want when the whole point is to run one thing everywhere.
The cleaner way to repeat a command across the group is a typing macro on the SSH entry. With broadcast on, firing the macro replays the string as typed input to every session, so it behaves exactly like typing it fresh, at the press of a button.
One thing worth checking so we can rule out anything else: with broadcast on and every session at a clean prompt, type a few characters and press the left and right arrow keys, and let us know whether the cursor moves in all sessions or only the active one. Cursor movement does not depend on history, so it tells us straight away that the keys themselves are reaching every session.
Looking forward to your reply!
Best regards,
i think it was related to a "history command", let's disregard. I think I had it in a very specific situation where this happened and not a bug.
Hello,
Thanks for circling back and confirming.
Glad it turned out to be tied to that specific history-command scenario rather than a broadcast issue on RDM's side.
Reach out anytime if something else pops up!
Best regards,