Hi All
I just bought two CRS326-24S+2Q+ for my company.
But I found something strange that the health info are total different.
I’ve done “reset configurations” on both switches.
Still get the same result as below.
Anyone know why?
Thanks!

Hi All
I just bought two CRS326-24S+2Q+ for my company.
But I found something strange that the health info are total different.
I’ve done “reset configurations” on both switches.
Still get the same result as below.
Anyone know why?
Thanks!

Ckeck system → routerboard firmware version and upgrade…
Thanks for your suggestion.
I’ve done that as you can see the firmware version 6.45.6 on the winbox window title.
No, what you see there is the RouterOS version, not the firmware version.
Firmware is like the BIOS of the device. It can be upgraded in System->Routerboard.
If an issue still occurs after a firmware upgrade, write to support@mikrotik.com, providing supout.rif files from both devices.
Oh…my fault.
I got it and will upgrade the routerboard fimware later.
Update status to you ASAP.
Thanks for Zacharias & pe1ch1’s great help.
Got it. Thanks.
You can upgrade it at any time (just click that upgrade button) but you will see the result only after the next reboot.
Reboot is not mandatory after upgrade so you can just upgrade it and then wait for an opportunity for a reboot.

Bad news. Got the same issue.
I’m going to write to support@mikrotik.com !!
Thanks, everyone!
Try to check system health from terminal and see if again the results are the same…
/system health print
Try to check system health from terminal and see if again the results are the same…
/system health print
Here you are.
Output are different on the 2 switches.Even got zero RPM info for fan speed.

Contact support…
Contact support…
Support will be useless with: return the product or “it still does its job”
Had the same issue with two RB1100AHx4 Dude Edition, one of which was missing temperature readout.
My advice: just forget about it and don’t expect too much from Mikrotik.
I got reply form support team last night.
This issue is already fixed in the upcoming RouterOS version.
Please use upgrade your devices when it will be published.
I will update you if new ROS version applied.
Thanks.
Update: The issue still stays in ROS v6.45.7. Sad…