I have a CRS504-RXQ-IN that I had to do a factory reset of. (See attached screenshot). I discovered the hard ware that this more or less bricks the device.
How can fix that and restore the IP address of the CRS504 back to its default of 192.168.88.1?
If I have to resort to console commands, I’ll need the exact sequence of commands.
Does Mikrotik monitor these forums, or are we on our own?
Double-click the MAC address in WinBox and login using that MAC address. Once inside, go to System -> Reset Configuration, enable only Keep Users and Do Not Backup. Click the Reset Configuration button and wait for the CRS to reboot. The switch will be back on the default configuration with the ports in a bridge bridge and bridge has 192.168.88.1/24 assigned.
You sound like you want the default configuration. You have quite a few choices:
the button-press config reset is available
netinstall has the ability to apply the default conf, you just have to select it (I think it's -r without -e on the cli)
use the MAC feature of Winbox
if you have access to the device, /system/reset-configuration is the command for restoring the default conf. If you just want an address, /ip address add interface=etherX address=192.168.88.1/24 is the command for setting it.
Lately I have found that e.g. LHG devices new out of the box, that should come with “CPE Router” configuration so you should be able to connect any device and get an IP address in the 192.168.88.0/24 network and use a browser to open http://192.168.88.1 or telnet to that address, actually come with completely empty config and a DHCP client running on the ethernet port. So you need to connect them to an existing network with DHCP server to get access via IP (of course it is possible to use winbox and MAC access).
Well, I can tell you that my “real world use-case” is to recommend people to buy an LHG and then configure it using a short manual that says to telnet to 192.168.88.1 in a connected computer and paste a config I have auto-generated for them, and in this real world it is not OK that for every new user there is a new procedure to acces their device…
Indeed. What makes it more complicated is that you receive the device with some installed RouterOS that lags behind the current version, and the online documentation almost never mentions version numbers.
So it may be that the current documentation is valid for 7.20 or 7.21, but the device was shipped with 7.18 and we do not know how the config was back then.