Hello!
I have an issue with a temp sensor in my new CCR1009-7G-1C-1S+.
I am collecting values over SNMP every 1 minute, and almost every time received value is correct (28-31C)
But sometimes i can see a spikes over 80C, every few hours.
That spikes occur in random times, not related to CPU load.
Does somebody here have similar issue?
Is it issue of CCR1009? or maybe caused by firmware (6.44.5)?
or just my device has a some hardware defect?
We also have noticed this behaviour on a couple of CCR1009s.
On which exact CCR1009 model you have noticed such CPU behavior (if possible, provide SN)? We will try to reproduce it locally.
+1 from me also.
First i bought ccr1009PC and everything was fine with temp log. Then i moved to 1009+PC and temp checking script from time to time alarms about high temp but in health status everything was normal (i had a little script to check temp and sends email if it is getting too hot).
After months of sporadically false alarms i stoped the script.
Model: CCR1009-7G-1C-1S+
S/n: 914F0A7AC1B0
some data collected from device:
We are also experiencing the same issue with CCR1009-7G-1C-1S+ S/N 94C10A2586B8
Looks like S+ version have this issue with device temp, because Processor Temp is OK, I have 2 of them:
@SNITE @littledpurple what aplications do you use for SNMP Monitoring?
@ingdaka We use Zabbix with this template https://share.zabbix.com/network_devices/mikrotik/template-net-mikrotik-snmpv2
Hello, I have the same issue, using zabbix monitoring CCR-1009 too…
Same here: CCR1009-7G-1C-1S+
One week done by Observium
-faxxe
Same problem: CCR1009-7G-1C-1S+
S/N 914F0B7F5297
Something decided?
Same here.
CCR1009-7G-1C-1S+
S/N: 914F0A7D0752, 7AEC0624C572, 7AEC069DC199
This is not shown only in SNMP data, but also in Winbox - System - Health, when you look at counters long enough.
You’re right. I watched for about an hour, my jumps were up to 108 degrees Celsius.
Hate to drag up an old post, but I’m seeing this on various CCR1036s and CCR1072s as well.
Various RouterOS versions (all “long-term” branch):
6.45.8
6.45.9
6.45.3
6.46.8
6.47.9 (this one is a CCR1009-7G-1C-1S+)
6.44.6 (I know that one is old and possibly insecure, not my position to update it unfortunately)
So it isn’t limited to CCR1009s… I’m polling with LibreNMS at 300sec (5 min) intervals.
I am seeing this issue as well. I am curious if any kind of resolution or official response from MT has been made?