Netonix Forums

We recently had a brief power outage at a site. Everything came back fine, and then today, one of our AF11 radios rebooted twice (after previously having 2+ years of up-time).

Today I logged into the Netonix switch proving POE to the AF11 (an other equipment). Every port on the Status page reads "Error" in the Watts column and the status page displays "Error" for all of the power and temperature sensors.

Does this likely indicate a dying switch, or will a reboot probably clear things up?

I can update the firmware, but am leery of doing so without first rebooting the switch.

And since these switches have been so rock solid stable for us, I haven't had to look at them for some time... and have forgotten some of the operation details... I know that a firmware upgrade will not affect the poe output, but don't remember if a reboot will or not.

Thanks
Mark

well....it seems all sensors are reporting error, which means that either one of the sensors is holding up that communications bus, or the board has been damaged so its causing this. A power cycle might bring it back....guess ya just have to try & power cycle.

Update 8/22:

I replaced the unit with a new one we had on the shelf as a backup. The new unit came up and is working fine.

Back at the shop, I placed the old unit on the bench and powered it up. It booted fine and can read all of the temp and power sensors, granted there is no POE load on the switch. I upgrade the firmware to 1.5.8 and the sensors still report as good.

After the power outage on 8/19, the AF11 went down twice on 8/20 and again on 8/21. I only logged into the switch after the 3rd outage which is when I noticed the sensor issues, but also that the switch rebooted when the AF11 last went down. This led me to believe that the switch was likely bad and probably not the AF11 after all.

At this point I don't feel I can trust that the switch is 100% and safe to deploy again.

Any suggestions for how I can test the switch? Can I send it in for an evaluation and possible repair?

Thanks
Mark

Finally got around to checking our syslog and I found the following for the switch. At this point I really just want to know if I should put the switch out or pasture on the "bad equipment" shelf or not.

Code: Select all


2021-08-20T16:02:24-04:00 10.1.2.254 sysinit: Error: Read failed
2021-08-20T16:02:24-04:00 10.1.2.254 sysinit: Error: Write failed
2021-08-20T16:02:25-04:00 10.1.2.254 sysinit: Error: Write failed
2021-08-20T16:02:25-04:00 10.1.2.254 sysinit: Error: Read failed
2021-08-20T16:02:26-04:00 10.1.2.254 sysinit: Error: Read failed
2021-08-20T16:02:26-04:00 10.1.2.254 sysinit: Error: Read failed
2021-08-20T16:02:26-04:00 10.1.2.254 UI: i2c error setting 0x47 12 110
2021-08-20T16:02:27-04:00 10.1.2.254 sysinit: Error: Write failed
2021-08-20T16:02:27-04:00 10.1.2.254 sysinit: Error: Write failed
2021-08-20T16:02:28-04:00 10.1.2.254 sysinit: Error: Read failed
2021-08-20T16:02:28-04:00 10.1.2.254 sysinit: Error: Read failed
2021-08-20T16:02:29-04:00 10.1.2.254 sysinit: Error: Write failed
2021-08-20T16:02:29-04:00 10.1.2.254 sysinit: Error: Write failed


send in for RMA if you want to...RMA portal will tell you if it is eligible for RMA period or not.

Thanks. Will do.

Update: The RMA submission tool says the unit is too old for RMA. Checking Amazon it looks like we bought this unit in Aug 2016.

Just read the RMA Procedure for Warranty and Repair post...

Since I already reset the unit and upgraded the firmware, the unit appears OK. Haven't tested every port but then that wasn't the problem.

This unit will go on the "maybe good, maybe bad" shelf and might be redeployed for non-critical use.

After 5 years of solid use, I think this switch deserves to retire. :-)