v1.3.6 FINAL bug reports and comments

[sirhc]

This could be an issue we chase for a long time.

There are over 6000 switches out there and only a few people report this issue and it would appear that turning the power off (not just a reset) appears to clear the Error and resolve the issue and we can not recreate it, at least not yet.

I guess the best thing for now is when people do experience this issue to gather as much information as they can such as look in the log and report exactly what they see and did when it occurs and eventually we will figure it out.

[sirhc]

I have been trying to recreate this all day and no luck.

[LRL]

I did indeed power cycle the unit while I was on site today. For a brief while it was fine. But as I said this is a new second switch for one of our main DC sites. Durring the process of changing port descriptions, applying power, changing STP, and VLANs it went back to the error state. The first message I seen while on site was something to the affect of "i2c timeout". Unfortunately at that time I was more concerned with cable errors and programming new gear.

I tried to downgrade the switch to 1.3.3 while on site when I noticed the error came back, but the UI told me I couldn't downgrade below 1.3.4 :/ The site is currently easy to access, but that's going to change in the not fare future. I have a spare ws-12-DC and could swap it out and send it your way if that would assist in resolving this?

Below is part of the currentl log on the device. It's all pretty much that repeating over and over. If so desired I can allow remote access into it for anyone as well.

Code: Select all

Jan 1 02:36:35 system: starting ntpclientJan 1 02:36:37 switch[767]: i2c_read failed after 5 tries: addr 49: Failed writing command to slaveJan 1 02:36:40 switch[767]: i2c_read failed after 5 tries: addr 49: Failed writing command to slaveJan 1 02:36:40 switch[767]: i2c error: excessive arbitration lost start errors (0x51)Jan 1 02:36:47 system: starting ntpclientJan 1 02:36:51 switch[767]: retrying i2cJan 1 02:36:54 switch[767]: i2c_read failed after 5 tries: addr 49: Failed writing command to slaveJan 1 02:36:57 switch[767]: i2c_read failed after 5 tries: addr 49: Failed writing command to slaveJan 1 02:36:57 switch[767]: i2c error: excessive arbitration lost start errors (0x51)Jan 1 02:36:58 system: starting ntpclientJan 1 02:37:08 switch[767]: retrying i2cJan 1 02:37:08 switch[767]: i2c error: excessive arbitration lost start errors (0x51)Jan 1 02:37:10 system: starting ntpclientJan 1 02:37:19 switch[767]: retrying i2cJan 1 02:37:19 switch[767]: i2c error: excessive arbitration lost start errors (0x51)Jan 1 02:37:21 system: starting ntpclientJan 1 02:37:30 switch[767]: retrying i2cJan 1 02:37:30 switch[767]: i2c error: excessive arbitration lost start errors (0x51)Jan 1 02:37:33 system: starting ntpclientJan 1 02:37:41 switch[767]: retrying i2cJan 1 02:37:41 switch[767]: i2c error: excessive arbitration lost start errors (0x51)Jan 1 02:37:44 system: starting ntpclient

[LRL]

I should add, somewhere between changing poe on a port and stp is when I noticed the issue back.