Serial Console Issue on CRS226-24G-2S+

RouterOS General
1

Hi all,

Goal
To be able to paste configuration into Serial Console, to configure a CRS226 the same as I do for a CRS125, when modifying and testing VLAN configuration.
I’d much prefer to use Serial Console, as without it I would lose communication with the CRS after configuring the following, if I have the VLANs set incorrectly:

/interface ethernet switch drop-if-no-vlan-assignment-on-ports
/interface ethernet switch drop-if-invalid-or-src-port-not-member-of-vlan-on-ports

Situation
I’m encountering an issue when connecting to a CRS226-24G-2S+ using Serial Console. When I do the exact same test with a CRS125-24G-1S, Serial Console works perfectly.
The CRS125 and CRS226 are running the latest RouterOS version available in the current branch, and RouterBOOT is up to date as well.
I’m using a Windows 10 PC, with PuTTY.

Detail
I’m encountering one way communication from PuTTY to the CRS. The CRS sees data from PuTTY, but PuTTY doesn’t see data from the CRS.
I know this because I used Terminal in Winbox for Serial Terminal. When I type into PuTTY, I see the text in Serial Terminal in Winbox. When I type into Serial Terminal in Winbox, I don’t see the text in PuTTY on Windows.

Settings
I’ve connected to the CRS using a Cisco console cable, and USB to Serial adapter.
I’ve used the following settings in PuTTY:
Baud Rate: 115200
Data bits: 8
Stop bits: 1
Parity: None
Flow control: None

I’ve also tried using Winbox to set Flow Control to XON/XOFF, and I’ve set the same option in PuTTY, with no change.

Thanks in advance,

Matthew McTague
Vetta Technologies

2

Try 9600 baud. It’s very rare to find a serial connection that runs at 115200.

3

Hi there,

Setting baud rate to 9600 causes the communication to not even work one way, I just get spaces in the output rather than letters and numbers.
Setting baud rate back to 115200 caused one way communication to work properly again, but it’s still not two way communication - as previously explained.

4

Good to know. I haven’t used the serial console. I typically do most of my config via SSH or WinBox. You might want to try WinBox, as it can connect at layer 2, so even if you screw something up in the config and lock yourself out of the WebFig or SSH, you usually can still connect with WinBox.

5

Hi there,

As I said above, with the following set, I lose communication over any method except Console:

/interface ethernet switch drop-if-no-vlan-assignment-on-ports
/interface ethernet switch drop-if-invalid-or-src-port-not-member-of-vlan-on-ports

I need to be able to troubleshoot issues, rather than having to reset the CRS if the configuration isn’t quite perfected before I enable those rules.
I need those rules in place on all ports to ensure that client nodes can’t set a different VLAN and have their traffic accepted.