Netonix Forums

Hi guys does anyone know what could be causing this issue, I have upgraded the firmware to 1.4.6 but we still have the same issue.
The switch is also rebooting itself every half hour or so.



Logs say


Jan 1 00:00:09 netonix: 1.4.6 on WS-12-250-DC
Jan 1 00:00:13 system: Setting MAC address from flash configuration: EC:13:B2:81:83:F6
Jan 1 00:00:16 admin: adding lan (eth0) to firewall zone lan
Jan 1 00:00:27 admin: Unable to query power supply
Jan 1 00:00:33 admin: removing lan (eth0) from firewall zone lan
Jan 1 00:00:36 admin: adding lan (eth0) to firewall zone lan
Jan 1 00:00:44 admin: adding lan (eth0) to firewall zone lan
Jan 1 00:00:45 STP: set port 1 to discarding
Jan 1 00:00:45 STP: set port 3 to discarding
Jan 1 00:00:45 STP: set port 5 to discarding
Jan 1 00:00:45 STP: set port 7 to discarding
Jan 1 00:00:45 STP: set port 11 to discarding
Jan 1 00:00:45 STP: set port 12 to discarding
Jan 1 00:00:45 STP: set port 1 to learning
Jan 1 00:00:45 STP: set port 1 to forwarding
Jan 1 00:00:45 STP: set port 3 to learning
Jan 1 00:00:45 STP: set port 3 to forwarding
Jan 1 00:00:45 STP: set port 5 to learning
Jan 1 00:00:45 STP: set port 5 to forwarding
Jan 1 00:00:45 STP: set port 7 to learning
Jan 1 00:00:45 STP: set port 7 to forwarding
Jan 1 00:00:47 STP: set port 12 to learning
Jan 1 00:00:48 STP: set port 12 to forwarding
Jan 1 00:00:48 STP: set port 11 to learning
Jan 1 00:00:48 STP: set port 11 to forwarding
Jan 1 00:00:50 STP: set port 5 to discarding
Jan 1 00:00:50 STP: set port 5 to learning
Jan 1 00:00:50 STP: set port 5 to forwarding
Jan 1 00:00:51 STP: set port 3 to discarding
Jan 1 00:00:51 STP: set port 3 to learning
Jan 1 00:00:51 STP: set port 3 to forwarding
Jan 1 00:00:56 STP: set port 5 to discarding
Jan 1 00:00:57 STP: set port 5 to learning
Jan 1 00:00:57 STP: set port 5 to forwarding
Jan 1 00:01:05 UI: i2c error setting 0x47 12 110
Jan 1 00:01:26 UI: i2c error setting 0x47 14 122
Jan 1 00:01:27 system: starting ntpclient
Jan 1 00:01:30 dropbear[1496]: Running in background
Jan 1 00:01:33 switch[1523]: Detected warm boot
Jan 1 00:01:36 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:37 system: starting ntpclient
Jan 1 00:01:40 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:43 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:43 switch[1521]: i2c link down to power supply (0)
Jan 1 00:01:46 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:48 system: starting ntpclient
Jan 1 00:01:49 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:52 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:55 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:58 switch[1521]: retrying i2c link to power supply
Jan 1 00:01:59 system: starting ntpclient
Jan 1 00:02:01 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:04 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:08 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:10 system: starting ntpclient
Jan 1 00:02:11 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:14 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:17 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:20 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:20 switch[1521]: i2c link down, in recovery mode
Jan 1 00:02:21 system: starting ntpclient
Jan 1 00:02:23 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:26 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:29 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:32 system: starting ntpclient
Jan 1 00:02:32 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:36 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:39 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:42 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:44 system: starting ntpclient
Jan 1 00:02:45 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:48 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:51 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:54 switch[1521]: retrying i2c link to power supply
Jan 1 00:02:56 system: starting ntpclient
Jan 1 00:02:57 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:00 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:04 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:07 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:07 system: starting ntpclient
Jan 1 00:03:10 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:13 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:16 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:18 system: starting ntpclient
Jan 1 00:03:19 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:22 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:25 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:28 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:29 system: starting ntpclient
Jan 1 00:03:32 switch[1521]: retrying i2c link to power supply
Jan 1 00:03:35 switch[1521]: retrying i2c link to power supply

Well, our forum doesn't allow external images, so please edit accordingly, but I'd guess! that you're probably seeing abnormally high wattage on a port or two which is sourcing power; That's a hardware failure related to overcurrent, From the equipment we have deployed at our WISP, it generally tends to follow a storm or other ground potential shift event.

I haven't personally witnessed a failure on i2c comms yet, but i'm aware that it can happen with older hardware revisions in an RF heavy environment, such as FM colocated equipment; No way for me to be sure without physically laying eyes on everything, though.

Long post short: Please RMA, your switch has been damaged, and will need to be repaired. The RMA procedure can be found here: http://forum.netonix.com/viewtopic.php?f=6&t=1259

Thanks!