If is useful for someone...
dx3230L-7.19.6.fwf.zip (38.1 KB)
Count me in as the now sad owner of a bricked switch after trying to upgrade SwOS from 2.17 to 2.18.
Exactly same symptoms as others reported.
RMA is not an option in my case as well, and switch is barely over a year old anyway. That's an expensive piece of e-waste, with fully functional hardware.
I will not be risking upgrading the 4 other similar switches I have.
Unless MikroTik prepare a remote solution for this, it would be useful if we would known does the router anything on UART when it logs BootROM: Trying UART. Does it send any signal, or just waiting input. And if the latter what it is waiting for.
I hope you'll understand if this time I don't sacrifice one to try...
It doesn't necessary to making brix. I mean, if it search something on UART, it would be informative for reverse engineering, if there is no official help.
Would you mind: why it is no option?
The switch was purchased online and shipped internationally. The local distributor charges ~$120 just to diagnose, and then will add the cost of repairs. I am not sure it's worth it to repair at this point, I just bought a $200 TP-link switch to get stuff back online.
My main worry now is what should I do with my 4 other similar switches, and how risky it is to upgrade the firmware.
At this point, I don't see the point of live to update the devices (any) before waiting for the problem to be resolved...
Also never put last version. Leave the other to do that and see if someone that lives to update, encounters some problems...
Do you have any specific reason to using SwitchOS instead of RouterOS on those metals? We operating this switches with RouterOS, fortunately without any problem.
You could try it this way, it worked for me:
@k6ccc did you ever update your CRS326-24G-2S with swos 2.18? Just curious if anyone was able to update without problems (or going through hoops). Not that I am recommending that you upgrade, I wouldn't until more info from Mikrotik emerges as @rextended advised here
@Buckeye To be honest, I had to check. No, my one CRS326 is still 2.17 and all my CSS326 are 2.18.
Just to confirm, I have now updated 3 CRS328-24P-4S+ to 2.18 using the method described above, i.e. first upgrade ROS, update SWOS from within ROS and finally updating SWOS from within SWOS. This seems to work reliably. Although the first boot after the initial upgrade of ROS seems to take ages. But it comes online eventually.
It wasn’t an option for me because the switch was purchased more than a year ago, and my distributor was unable to open a support ticket with MikroTik because the purchase date is older than the warranty window. Even though I provided all the e-mails from MikroTik stating that they would repair the switch free of charge, the distributor was unable to open the support ticket on their end. According to the distributor rep, there is a web page they use to start the RMA process with MikroTik, and a valid purchase date is required to start the process.
Distributor does not know valid purchase date?
Well, the distributor rep is either lying to you or does not know what he/she is doing, unless Mikrotik is different from any other vendor/manufacturer, that page is nothing but a tool to make easy "normal" RMA's . There is ALWAYS another (more complex, manual) procedure to deal with "exceptional" cases.
When Mikrotik support really written such a commitment it is at your distributors turn. As @jaclaz already said, there is always an alternative way (where you won't fail entering a "valid purchase date").
Precisely my point. When I provided that information to them, they said there was nothing they will do.
I’m not quite sure I understand the difficulty here. I gave the distributor everything they needed to start the RMA. Distributor said, “go pound sand.” MikroTik said, “yeah can’t help you there. Go talk to the distributor again.”
Perhaps I don’t know the magic, but how exactly do I make the distributor do something they don’t want to do?
A valid date is a date that is within the 1 year warranty period. The purchase date of the switch is 15 months ago and is considered invalid for warranty.
Okay. So they are lying. How does that help me exactly? It’s not like I can send the item back to MikroTik directly. If that were the case, I would have done that. MikroTik instructed me to send the item back to the distributor. The distributor told me that there was nothing they will/can do about it. What other option do I have here?