v1.4.2 Bug Reports and Comments

[givemesam]

last night I upgraded a WS-12_DC D model from 1.3.9 to 1.4.2 and did not notice till this morning that there were tons of CRC errors exactly since I did the UG. was there a stack change for the Ethernet ports?

Any thoughts?

I just rolled back to 1.3.9 and all the CRCs stopped!

John

No, "we do not have anything to do with the switch core code itself. The switch core itself is a self contained chip and we have nothing to do with the code that runs it.

All we do is write the UI/CLI/STATS and control the Daemons that control things like STP/LACP and then we only have a limited affect on them such as steering a car, all the steering mechanisms are already built into the car.

I would say if anything it was when the device re-negotiated the link the link was poor sort of like when you call someone and the line is crappy so you hang up and call back.

I would have tried rebooting the device or disabling and enabling the port.

But once again "we have nothing to do with the switch core code and packet handling per say, this is all done in the switch core chip and it has it's own firmware which we do not write."

we see errors on the port of an AF24 when something is rebooting, my take on it is that there are thousands of TCP packets resending from somewhere, and nothing replying. something along those lines. clear the counters one minute after everything is stable and see it is only related to the downtime / initial min

[mike99]

Had a strange bug. Brand new WS-10-150-AC. Was configuring it on my desk. No PoE output on this switch.

I was testing configuration on each port, check if every port was pinging the router. Port 1 and 2 worked fine. 3 didn't come up and after that, 1-6 ports didn't come up. Try to reboot it several time or access config via console but was not able to do anything.

On boot, I was seeing the following error message if I pressed [Enter] before the switch finish booting:
No kernel interface: open(/dev/switch): No such file or directory
But it still seem to do the same even after fixing it via reset.

After boot, the switch constantly return a "Segmentation fault" error, maybe every second.

Seem like the're were no way to get the config back. I've done a factory reset at boot and now the switch is fine.

I updated it to 1.4.2 yesterday (didn't check firmware version before update) but the switch was up all night and I was able to work on it this morning until I plugged port 3. I had a backup I had done with just few modification before the switch crash so restored it and now, seem to work fine. Made some config change, tested again all port, rebooted it 2 times, didn't see the problem again.

[sirhc]

PERSONALLY I WOULD NOT USE v1.4.2 I WOULD USE v1.4.3rc7 AS THERE WERE SOME NASTY BUGS FOUND AND FIXED

READ RELEASE NOTES.