Bad CRS328-24P-4S+RM out of the box?

Hardware MikroTik hardware general
1

I just received my CRS328-24P-4S+RM…got it to replace 2 ubiquiti switches plus a 3rd mikrotik (combine poe + 1G + 10G into one switch). Anyway, the switch got installed in my rack yesterday evening. I came home today and went to go look at it (because I do weird stuff like that when I’m bored), and noticed what sounded like the fans ramping up and down, plus a “FAN” fault on the front of the unit. Everything is working fine, the health seems good :

CPU Temperature	28C
Board Temperature	22C
FAN1	0 RPM
FAN2	0 RPM
PSU1	118mA @ 26.43V
PSU2	433mA @ 52.64V

but the fans are saying 0 RPM. I’m on the latest 2.9FW, so I’m wondering if this is DOA…ish?

2

Same problem here with a brand new CRS328-24P-4S+RM. I restated the switch but the problem came back after few hours.

3

Same problem for me. Brand new switch the fan goes on and off and the fan failure led is on. I reboot the switch and it came back after a couple of hours.
It’s the third time I reboot the switch and now the uptime is one day without the problem.

4

Seem that the unit is defective. The fan failure came back this morning after 3 days uptime. Reset, reboot and reinstalling the FW didn’t work.

5

I RMA’d the unit with Baltic Networks. I had to pay return shipping which sucked. I got the new unit two days ago, plugged it in, loaded my old config backup, and let it run. Exactly 23 hours later, fan warning light is on and fans are ramping up and down. I repeated the same process, unbox switch, immediately update to 2.9, move cables..wait.

IT seems that either mikrotik makes SH%@ty hardware, or theres a problem in firmware 2.9. My garage stays cool enough that I don’t think heat will be an issue, but I’m not about to RMA a second switch.

The second thing I noticed, is that even after downloading the latest, the switch still tells me that there is a firmware update available (the dates are off by like 5 days). coming from Ubiquiti this seems like a step backwards.

6

I had the exact same issue with the same model. I have a thread on it here somewhere.

Turned out there was nothing wrong with the unit. It was SwOS.

I changed over to RouterOS and it’s been running fine since. SwOS 2.9 has been released since but unfortunately mine is in production now so I can’t make any changes.

SwOS isn’t terribly reliable and I also had an issue with buffer overruns. Since switching to RouterOS I haven’t had a single issue.