NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
XS712T false temperature alerts?
Hello,
We have 2 XS712T's (running latest firmware) and from both, we sometimes see these type of alerts in our Syslog server:
Oct 6 15:49:42 192.168.10.239-1 TRAPMGR[55942028]: traputil.c(658) 2702 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal Oct 6 15:49:12 192.168.10.239-1 TRAPMGR[55942028]: traputil.c(658) 2701 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal
These events are a couple of seconds apart as you can see.
In general, the intervals and who sends such an alert are random. We cannot establish a pattern. It "just happens". We can get a couple of these over the course of a few days in the same week, from any one switch, or it can be totally quiet for weeks before some switch sends one out again. Totally random who and when.
The actual temperatures are really always stable and fine. The messages basically tells us "normal" so what triggers these "temperature change alarm" messages?
Any ideas?
Hi ElectricSteve,
Welcome to NETGEAR community!
We can also see the same alarm on my XS172T of LAB as blow:
And our XS712T work fine and normally just like yours.
<13> Sep 21 14:49:50 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 121 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal <13> Sep 21 14:49:20 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 120 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Above Threshold <13> Sep 20 10:26:30 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 119 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal <13> Sep 20 10:25:59 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 118 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Above Threshold
This alarm will appear when temperature rise above to threshold and back to normal temperature again.
Such as:
1)XS712T find the temperature around comes to very high;
2)He sent a alarm to syslog server with:
%% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Above Threshold
3)Then,Lab master turn on the air condition and XS712T back to normal temperature again.
4)He told to syslog server with:
%% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal
So this alarm just like a kindly remainder that:
'Hi administrator, My fever has gone':smileyhappy:
After all,
Maybe the temperature threshold for XS712T is a little low.
Because we wana XS172T could tell administrator to avoid the high temperature that may hurt switch.
So this alarm will appear with high frequency.
We are sorry about your concerns.
Regards,
Daniel.
5 Replies
Hi ElectricSteve,
Since you have mentioned that both XS712T switches are on the latest firmware version which is v6.1.0.34, i believe it should have fixed the issue where it displays unrealistic high temperature through a debug session as per the release notes here.
Have you performed a factory reset on both XS712T switches after the firmware has been upgraded to the latest version? It is recommended to do a factory reset after doing a firmware upgrade then reconfigure it from scratch.
Regards,
DaneA
NETGEAR Community Team
Hello Dane,
I unpacked the switches, upgraded the FW to v6.1.0.34 and then configured them for the first time. I did not do a factory-reset after the FW upgrade however.
You speak about factory-reset, then configure from scratch. I cincerely hope that making a backup of the current config (if the dreaded 404 error does not ruin it...) and restoring the config after the reset, is possible (because you speak about "from scratch").
I'm sorry but the GUI is so daft and sluggish, and I have so many VLAN's etc. configured, it took ages to configure everything (needing to go to every single vlan, tick all the ports/lags with either T or U etc. etc. etc. is so annoying, And that on multiple switches.
I need to be able to restore via config-file (which I never had to do so far, and hopefully it works, instead of throwing 404-like errors like when backing-up the config).
To be honest, the error that appears in syslog, going from "temperature normal -> temperature normal" sounds like a bug and unrelated to the "255 degrees" thing the release-notes mention.
Hi ElectricSteve,
Welcome to NETGEAR community!
We can also see the same alarm on my XS172T of LAB as blow:
And our XS712T work fine and normally just like yours.
<13> Sep 21 14:49:50 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 121 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal <13> Sep 21 14:49:20 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 120 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Above Threshold <13> Sep 20 10:26:30 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 119 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal <13> Sep 20 10:25:59 172.26.2.112-1 TRAPMGR[55942028]: traputil.c(658) 118 %% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Above Threshold
This alarm will appear when temperature rise above to threshold and back to normal temperature again.
Such as:
1)XS712T find the temperature around comes to very high;
2)He sent a alarm to syslog server with:
%% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Above Threshold
3)Then,Lab master turn on the air condition and XS712T back to normal temperature again.
4)He told to syslog server with:
%% Temperature change alarm: Unit: 1 Sensor ID: 2 Event: Normal
So this alarm just like a kindly remainder that:
'Hi administrator, My fever has gone':smileyhappy:
After all,
Maybe the temperature threshold for XS712T is a little low.
Because we wana XS172T could tell administrator to avoid the high temperature that may hurt switch.
So this alarm will appear with high frequency.
We are sorry about your concerns.
Regards,
Daniel.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
