Temperature readings across multiple AP9631 stuck until reboot

[Anonymous user]

I have 6 temperature probes spread across 4 SU6000RMXL with AP9631 management cards. Over the holiday break, I got an email alert about high temperatures, but only 1 of the 4 showed a problem. One of the ones that didn't show a problem has a probe within a few feet of the probes showing high temperatures, and we were pulling our hair out trying to understand the circumstances that would fit the data. After I got back to the office, I realized that the temperature readings on the other probes were all stuck at a value, and were no longer tracking changes in the environment. After rebooting the management cards on the affected units, they started responding again to variations in the temperatures.

The image below is a screenshot of my monitoring dashboard. On the upper 2 graphs, you can see a lengthy flat spot from mid-December until early January when I restarted the interfaces, that completely missed the temperature spike on December 29th seen in the lower 2 graphs. It concerns me that this would happen at all, but especially given that 3 out of 4 cards got into this state within a few days of each other. At the time it happened, all 4 units were running v6.2.0. I have since updated them all to v6.4.6. Is this a known issue that has been addressed between those versions? I read the release notes but didn't see it mentioned, and now I'm worried I can't trust them to issue an alert when something happens.

[BillP]

Hi Novice,

May I know what named of your monitoring temperature graph? I have used cacti and prtg but no template for that.

Thanks, Huan

[Anonymous user]

I'm using a Centreon front end on top of Nagios.

[BillP · Accepted solution]

Tks Drew.

Today I just configured my prtg with monitoring specific counters of APC UPS that making good status.