v1.3.9rc2 through rc14 - BETA/Release Candidate

[Eric Stern]

n case it matters, these switches were newly upgraded and the 1hr graph only has about 5 minutes of data.

I can confirm it happens only on newly powered/upgraded switches that do not have a lot of historical data. From my guess, it seems as if there is less than 1hr of full data then the javascript freaks out. I have other RC8's that are behaving properly if they have a bit of uptime.

Given this information I was able to duplicate it. It will be fixed in the next RC.

[zaltec]

Someone else reported that they fixed this problem by reflashing rc8, so you can try that.

Hi Eric,
already tried with 2 different switches, problem still there. I made some modification on snmp.conf file to exclude some oids and the issue seems to be related only to interface polling. When polling all other oids from Dude i see no problem, as soon as it starts polling interfaces (to build interface table or traffic graph) CPU spikes to 100%.

BR,
Giorgio

[Eric Stern]

Hi Eric,
already tried with 2 different switches, problem still there. I made some modification on snmp.conf file to exclude some oids and the issue seems to be related only to interface polling. When polling all other oids from Dude i see no problem, as soon as it starts polling interfaces (to build interface table or traffic graph) CPU spikes to 100%.

BR,
Giorgio

Can you describe how you are testing this? I can't duplicate it.

Which model are you using?

Does it happen when you do an snmpwalk with The Dude?

[designweb]

over 30 plus switches on rc8 all good until today a mini 6 has lost its ability to read the board voltages, it was running an AC-500, a B5 mimosa and an M5 loco.
reloaded firmware still the same error as below, the incoming AC-500 stayed online with its port showing up an ok, the mimosa and loco lost power, although still showing on port graphic green and orange, however then turned power off to both radios and have now lost access to switch even though AC-500 still accessible and showing port up at 1Gb.
I suspect hardware failure rather than rc8 but would like expert opinion




Jan 1 00:00:05 netonix: 1.3.9rc8 on WS-6-MINI

Jan 1 00:00:09 system: Setting MAC address from flash configuration: EC:13:B2:91:01:26

Jan 1 00:00:10 kernel: link state changed to 'up' on port 6

Jan 1 00:00:11 system: starting ntpclient

Jan 1 00:00:12 admin: adding lan (eth0.3800) to firewall zone lan

Jan 1 00:00:15 kernel: link state changed to 'down' on port 6

Jan 1 00:00:17 kernel: link state changed to 'up' on port 6

Jan 1 00:00:19 dropbear[750]: Running in background

Jan 1 00:00:24 system: starting ntpclient

Dec 30 16:44:55 switch[766]: Error reading temp sensor

Dec 30 16:44:57 switch[823]: Detected cold boot

Dec 30 16:44:58 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:44:59 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:00 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:01 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:02 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:03 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:04 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:05 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:06 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:07 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:08 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:09 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:10 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:11 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:12 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:13 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:14 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:15 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:16 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:17 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:18 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:19 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:20 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:22 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:23 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:24 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:25 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:26 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:27 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:28 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:29 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:30 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:31 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:32 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

Dec 30 16:45:33 switch[823]: i2c error: arbitration lost start (0x20), recovery failed

Dec 30 16:45:34 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:35 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:36 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:37 switch[823]: i2c error: arbitration lost write bit (0x20), recovery failed

Dec 30 16:45:38 switch[823]: i2c error: arbitration lost stop (0x20), recovery failed

[Eric Stern]

How long was it running rc8 before the problem started?

I would try power cycling it. If you still get the same errors it is likely hardware failure.

[designweb]

it was indeed hardware failure, when the tech got there with a spare under his arm, he found the recent severe storms in the UK had found their way into a 'waterproof ' box and one port was damp, so unrelated to rc8 and all of the other ports still working so proving again to be a great product under adversity
Happy Holidays

[sirhc]

v1.3.9rc12 - Released 1/4/2016
- Fixed per-port graphs that were broken if switch was up less than 1 hour
- Fixed condition where DC2DC power supply failed to wake up switch from hibernation mode
- Fixed where unresolvable hostname could hang syslog server
- Fixed DC power supply voltage range
- Added LLDP Discovery
- Now retains log if log daemon is restarted
- CLI no longer saves config unless something was changed

[lligetfa]

v1.3.9rc12 - Released 1/4/2016
- Now retains log if log daemon is restarted

Retains log even if manually attempt to clear. How are we supposed to clear the log now?

[sirhc]

v1.3.9rc12 - Released 1/4/2016
- Now retains log if log daemon is restarted

Retains log even if manually attempt to clear. How are we supposed to clear the log now?

SORRY, you found a bug - Will fix before next rc release.

Beat it up Les and see if you can find more

[zaltec]

Hi Eric,
first of all happy new year.
Regarding the issue it's quite simple, add the switch to dude with the correct snmp community, double-click the device you just added, go to snmp->interface and as soon you go there the cpu goes to 100% and snmp become unresponsive, same thing if you make a link (right click-new link), as soon as you select the interface to graph, cpu 100%. Snmpwalk is ok.
Actually i'm having this problem on all WS-12-250A, strange thing is the WS-12-250-DC are working fine (same fw of course).

Can you describe how you are testing this? I can't duplicate it.

Which model are you using?

Does it happen when you do an snmpwalk with The Dude?