Problems with Temp. on CRS328

Hardware MikroTik hardware general
1

Hello,

we have a problem with a part of our CRS-328-4C-20S-4S+ switch. Although the same firmware is active on all and the bios is the same. We can’t read the temperature of some devices.
As far as we have been able to determine so far, this partly ensures that the fans are not controlled correctly and the switch then gets too warm. Eventually stop working and need a roboot.

Does anyone have an idea why ??
crs328_temp.jpg

2

Are the blades spinning?

When was the last time you blew them out?

Are the fans stock or third-party?

I have the 24P version, so maybe your 20S differs, but mine uses 3-pin PC type fans. If you use 2-pin fans, you lose speed control. 2-pin fans should run full-speed, but that shortens their life, which brings me back to my first question.

3

Hi,

Are the blades spinning? - yes they do

When was the last time you blew them out? - the switches are all a maximum of 4 weeks old.

Are the fans stock or third-party? - the original ones

I have 4pin fans installed.

4

Are the same type of sfp/sfp+ modules installed in both devices?

The temp reading (not cpu temp) on a number of switch models comes from the sfp/sfp+ modules themselves.

5

Make sure you reference

https://wiki.mikrotik.com/wiki/MikroTik_wired_interface_compatibility

Also note that 10gbaseT sfp+ devices can generate a lot of heat

https://wiki.mikrotik.com/wiki/S%2BRJ10_general_guidance

6

I have about 50 of the switches and they all have the same 24 SFPs from Edge Optics in them. So it can’t be that.
Some show the temp. Not with others.

7

Just confirming when you said the firmware was the same, do you mean the router OS and firmware or just the OS, it can be a bit confusing as the firmware is included with the OS but not installed until you run the upgrade option form the routerboard menu then reboot :slight_smile:

8

Yes, both the same. After the update, I also brought the bios up to date.

9

Are you able to netinstall one of the units that is not behaving correctly and see if it resolves the solution at all? If that does not work I might suggest creating a supout.rif from the device and opening up a ticket with support@mikrotik.com to see if they think this is a bug or if it might be some kind of hardware issue :slight_smile: