i2c errors

[jbaird]

Ok - so, it's probably safe to assume that there is no permanent damage since the sensors have been reporting properly?
One odd thing is that we had to disable STP on a backhaul interface after the cold reboot/recovery, otherwise it was stuck in 'discarding':
Dec 31 19:20:35 STP: set port 1 to learning
Dec 31 19:20:35 STP: set port 1 to forwarding
Dec 31 19:20:52 STP: set port 1 to discarding
We have always had STP enabled on all interfaces, so I'm not quite sure what is causing this yet.
(You can also see that NTP was not working correctly, but a disable/enable of ntpclient fixed this)
Other than that, the switch appears to be functioning as expected.

[jbaird]

I am thinking there was more likely a sag than a surge and that the sag left the switch in an indeterminate state that a hard power cycle cleared.

I don't care for standby type of UPS that transfer from line to inverter. If not running a DC system with batteries, I prefer to use a true online UPS that always run from the inverter.

Since you use a switch that can take unregulated DC, your best bet would be to convert over to a battery banked DC plant that avoids transfer lag.

Our typical setup is a Traco TSP+BCM PSU/UPS combo which has a seamless transfer. We already had invested money in this APC XL/battery combo at these sites, and once the APC dies (or batteries) we will convert this to our standard config.

[sirhc]

Ok - so, it's probably safe to assume that there is no permanent damage since the sensors have been reporting properly?
One odd thing is that we had to disable STP on a backhaul interface after the cold reboot/recovery, otherwise it was stuck in 'discarding':
Dec 31 19:20:35 STP: set port 1 to learning
Dec 31 19:20:35 STP: set port 1 to forwarding
Dec 31 19:20:52 STP: set port 1 to discarding
We have always had STP enabled on all interfaces, so I'm not quite sure what is causing this yet.
(You can also see that NTP was not working correctly, but a disable/enable of ntpclient fixed this)
Other than that, the switch appears to be functioning as expected.

I agree there is probably no damage and the reboot resolved your issue.

I am at a loss here, no idea but I am pretty sure this is not due to any damage but rather something else.

If you are using RSTP on other switches around your network RSTP communicates to its neighbors so maybe a state of another port on another switch has changed (from discarding to forwarding) possibly which would tell this switch to act differently now in regard to that ports state?