2026.3.15 multiple ssh session with broadcast

This is something repeatable that I would like to show so this can be resolved. Very odd behavior. Please reach out to me.

Anyone?

Hello Grant,

We would like to schedule a remote session with you, if possible, so we can look into your issue.

Please use the online appointment booking system to schedule a session at your convenience.

I sent you the link via DM.

Best regards,

See you tomorrow.

Hi Grant,

Thanks again for taking the time to meet with us today! Here's a quick summary of what we covered and the next steps.

SSH Broadcast Truncation Bug

During the session, you demonstrated that when opening multiple Cisco switch sessions simultaneously and using the "Broadcast All" feature to run a command across all of them at once, the terminal output gets truncated to approximately 5 lines instead of the expected 24-line default. Running the same command on a single session in isolation works correctly, which points to RDM's broadcast session handling as the likely cause.

We were able to reproduce the issue on our end and have already reported it to the development team for investigation. We will keep you posted as we get more information.

In the meantime, here is a workaround you can use: on the affected entry, go to Terminal settings, set Terminal size to Fixed size, and configure the Columns and Rows values (tested with 120x40, Standard). With this configuration, all tabs should connect with the correct size.

Network Scan Feature Request

Regarding the two Network Scan improvements you mentioned (disabling auto-scan on launch and supporting multiple IP ranges in a single session) — after consulting with our team, the best way to move this forward is to submit a formal feature request on our forum. This allows the dev team to track community interest and helps prioritize the request accordingly.

You can submit it here: https://forum.devolutions.net/forums/17/remote-desktop-manager--feature-request

Don't hesitate to reach out if you have any questions!

Best regards,

What i don't understand is how RDM only displayed X lines when this should have come from the switch. Is RDM somehow in this scenario doing a terminal length 10 when connecting? I don't understand how RDM could limit the response of the switch. The switch is outputting based on it's settings.

Hello Grant,

That is a fair question, and you are right: RDM does not send "terminal length" or any other command to the switch, and it cannot limit what the switch outputs. The paging (the --More-- prompt) is done by the switch itself.

What RDM does control is the terminal size it reports to the switch when the SSH session starts (the number of rows and columns of the terminal window). Cisco switches use that number as the page length for the session. In your recording, when you opened a single switch, it paged after about a full screen of lines, which is the height of the window, not a fixed 24 lines.

What we found in our tests with 2026.3.15.0 is this: when several SSH sessions are opened at once, only the first tab, the one in front, starts with the real size of the window. The other tabs are connected in the background with a very small terminal size (13 rows in our lab). RDM sends the correct size to the switch when you bring each tab to the front, but some switches only read the size when you log in. That is what we believe happened with the IT_OFFICE switch (the one with the older IOS 12.2) in your recording: its second "sh run" still stopped after about 11 lines even after the tab was in front. The Broadcast feature is not involved: we reproduced it without Broadcast, and the same sessions opened one at a time or with the previous 2026.2 version behave correctly in our tests.

We have reported this to our development team. I cannot give you a date for a fix yet, so here are the ways to avoid it in the meantime:

1. Set a fixed terminal size on the entries. In the entry properties, in the Terminal section, Display tab, set "Terminal size" to "Fixed size" and enter the columns and rows (for example 120 columns and 40 rows). With this, every tab starts with that size, even when it is opened in the background. We tested it with seven sessions opened at once and all of them started with the size we configured.

2. Run your "Terminal Length" macro (terminal length 0) in all the tabs once they are connected. It works on every switch regardless of the terminal size.

3. Open the switches one at a time, or open them and bring each tab to the front before sending commands, if the switch accepts the size change (the newer switches may).

If you would like to confirm it on your side, run "show terminal | include Length" in one of the tabs opened in the batch (not the first one) and in a switch opened alone. You should see a much smaller number in the first case.

Let me know if the fixed size works for you or if you would like me to look at anything else.

Best regards,

Any update on this one?

Hello Grant,

Thanks for checking in. Here is where things stand.

The paging problem you reported (the --More-- prompt appearing after only a few lines in the tabs opened in the background) is logged with our development team and is still open. It is not fixed in version 2026.3.16.0, which was released on October 27, so updating will not change it. The cause is that the background tabs are connected before they have a real window size, so they report a very small terminal to the switch. A proper fix depends on the terminal rework that is in progress, and I cannot give you a date yet.

Until then, the most reliable way to avoid it is the fixed size on the entries:

1. Open the entry properties, go to the Terminal section, Display tab, and set "Terminal size" to "Fixed size". Enter the columns and rows (for example 120 columns and 40 rows). Every tab then starts with that size, even when it is opened in the background. We tested it with seven sessions opened at once and all of them started with the configured size.

2. Alternatively, run your "Terminal Length" macro (terminal length 0) in all the tabs once they are connected. It works on every switch regardless of the terminal size.

If you try the fixed size, please let me know whether it solves it on your switches, including the older IOS 12.2 one.

Best regards,