I can not get the console cable to work with this switch. I have a CRS317 and Crs328-24p on the same rack and the same console cable works just fine. I tried updating the ROS on the problematic switch and the boot up on the screen works perfecfly but when the switch loads up. I can work on it from the WINBOX but I can not use the console. Im trying to do some quick paste configs and without the console it proves to be tricky. Has anyone seen this before. It stays stuck like in the image im attaching.

if for some reason on RouterOS terminal on serial port is disabled, or the serial is used by another service, you see nothing after RouterOS end loading...

try this:

<REMOVED>

EDIT: see updated script
viewtopic.php?p=939889#p939836

This is what I get, Im not at the office I just vpn'd in to try this and hope it would work by the time I get back to the office but just wanted to post the output after adding the commands.

terminal code

[admin@Mikro-24PortCore] <SAFE> /system console remove [find]
[admin@Mikro-24PortCore] <SAFE> /system routerboard settings set baud-rate=115200
[admin@Mikro-24PortCore] <SAFE> /port set 0 baud-rate=auto data-bits=8 flow-control=none name=serial0 parity=none stop-bits=1
failure: Cannot change port while in use!
[admin@Mikro-24PortCore] <SAFE> /system console add channel=0 disabled=no port=serial0 term=vt102
[/code]

something is using the serial port....


try without safe mode, the commands do not involve any network functionality, as you see.


results of this?

Looking Better.. mannn I wish I was at the office to test this out lol

terminal code

[admin@Mikro-24PortCore] > /system console remove [find]
[admin@Mikro-24PortCore] > :delay 4s
[admin@Mikro-24PortCore] > :put [/port get serial0 used-by]
remote-access
[admin@Mikro-24PortCore] > /system console add channel=0 disabled=no port=serial0 term=vt102
[admin@Mikro-24PortCore] >  
[admin@Mikro-24PortCore] > 
[admin@Mikro-24PortCore] > 
[admin@Mikro-24PortCore] >

"remote-access" on serial port????

remote-access is for "remotize" a serial port.....

you (or previous owner) never use that board to conect remotely a plugged serial device?

Ok, updated script for that... unexpected....

Took it nicely..

terminal code

[admin@Mikro-24PortCore] > /system console remove [find]
[admin@Mikro-24PortCore] > :delay 1s
[admin@Mikro-24PortCore] > /system routerboard settings set baud-rate=115200
[admin@Mikro-24PortCore] > :delay 1s
[admin@Mikro-24PortCore] > /port remote-access remove [find]
[admin@Mikro-24PortCore] > :delay 1s
[admin@Mikro-24PortCore] > /port set 0 baud-rate=auto data-bits=8 flow-control=none name=serial0 parity=none stop-bits=1
[admin@Mikro-24PortCore] > :delay 1s
[admin@Mikro-24PortCore] > /system console add channel=0 disabled=no port=serial0 term=vt102
[admin@Mikro-24PortCore] > 
[admin@Mikro-24PortCore] > 

Ill update the post when I get to the office to test it .. THANK YOU!!!

Thanks.

I'm almost sure that it work certainly...

Please also report info for other users that come on same problem.

Thank you so much that worked like a charm

Yes, but the interesting part would be if we knew what was the reason it didn't work...
For example by a configuration export...

Already identified:

terminal code

[admin@Mikro-24PortCore] > :put [/port get serial0 used-by]
remote-access

you (or previous owner) never use that board to conect remotely a plugged serial device?

someone set the serial port (inadvertitely or on purpose) to be used by remote via TCP,
and when RouterOS start, the control of serial, pass from os loader to service, than use that as remote serial port

to be paranoid, someone did it on purpose so that they could remotely control that device via virtual serial ...

someone did it on purpose so that they could remotely control that device via virtual serial ...

Could that be indeed possible ?

yesss.....

And voilà, everyone on the Internet can use the RouterBOARD serial... if have one (active) by RFC2217 (or RAW)
https://datatracker.ietf.org/doc/html/rfc2217