v1.4.2 Bug Reports and Comments

[Hightech]

Just got a new WS-10-250-AC firmware 1.4.2 final don't pass management vlan on tagget trunk ports on the switch if the port is untagget on management vlan it pass the trafic.

We have had this error before on some very old firmware versions.

We use STP on this ports that don't pass management vlan.

firmware 1.4.2rc6 work just fine, so you have changed some thing on the final version!

We have 1.4.2 final running on a WS-12-250A with same configuration working just fine, so it is me by related to the ws-10-250-AC switch

Br.
Carsten

I think you'll need to double check this is accurate. The STP code was not changed between rc6 and final. Furthermore there is no reason it would operate differently on different models.

If you can come up with a simple configuration that reproduces the problem I'll look into it further.

It cout be related to hardware fail on this switch port 5 and 6 are broken not passing traffic and PoE is some how burning off PoE equipment when we turn on PoE on this ports!

I can send you our config file from the switch, we dont change anything else than the firmware and it stop passing management vlan on tagget ports.

Br.
Carsten

[AlexC]

Discovery is finally working again for me now with v.1.4.2.

[vnce]

i upgraded 1 site and everything worked perfectly except for a mikrotik ap we have there,, it showed connected at a gig but it would not pass traffic, troubleshot everything even went and plugged straight in, nothing wrong with mikrotik, but it wouldn't pass traffic.. rolled firmware back to 1.4.1 and mikrotik worked perfectly,, any thoughts?
all ap's on their own vlans, 24 port 400watt switch

[sirhc]

i upgraded 1 site and everything worked perfectly except for a mikrotik ap we have there,, it showed connected at a gig but it would not pass traffic, troubleshot everything even went and plugged straight in, nothing wrong with mikrotik, but it wouldn't pass traffic.. rolled firmware back to 1.4.1 and mikrotik worked perfectly,, any thoughts?
all ap's on their own vlans, 24 port 400watt switch

Not with the provided information but there was no change between v1.4.1 and v1.4.2 to anything that would affect this in anyway that I can think of?

I would wait until a weekend or off peak time and upgrade it again and poke around?

I am sure that is not what you want to hear though, wish I had a better solution!!!

[6gnet]

Regarding SFP counters on WS-12-250AC, they do work now, thanks! but they don't reset, when clicking "Reset Counters" button, they remain as they were before.

-G

[sirhc]

Regarding SFP counters on WS-12-250AC, they do work now, thanks! but they don't reset, when clicking "Reset Counters" button, they remain as they were before.

-G

I thought the bug on SFP stats was only boken with the WS-10-250-AC? And I heard that was fixed?

I will confirm that you are correct and that when you attempt to clear just the port stats on a WS-12-250-XX they do not clear but if you clear all the port stats with the top gear it does cleat that.

I will note that bug in the release notes and open a ticket to fix it.

[6gnet]

Sorry I meant WS-10-250-AC

-G

[sirhc]

Sorry I meant WS-10-250-AC

-G

Well I was told the stats were fixed on the WS-10 SFP ports but it appears the individual port stat clear for SFP ports is broken on WS-10-250-AC and WS-12-250-XX

[Torolan]

Hi we have tried this on 6 or 7 switches seemed to be no issue however on 1 switch WS-400B we have 2 rocket m titanium's locked to 100MF at radio and switch do to the gigabit lock up bug. Once we deployed 1.42 these locked up and stopped responding. We tried to make a change on switch to reboot them switch locks up. Says applying config will revert if changes fail etc. never comes back. Switch works just cant log in etc. Reboot switch it is back up. By now starting to really piss off our PtP customers off this tower. Finally moved ports in switch for the titanium sectors got them to come and work. So we are thinking bad switch. Roll out at 6:30am this morning with new WS 400b switch with 1.42 firmware and config for switch, we are replacing on it. shut old switch down move cables over 1 by 1 and power up new switch boots up fine except Rocket titanium's not working again make a change on switch locks up. No matter what we do, reboot, switch is up make a change locks up. Couldn't bring Titaniums back.

Installing 3rd switch this morning on 1.39 firmware to try and bring the Rocket Titanium's back. We will use manual config this time.

We have titanium's on other switches that have been flashed to 1.42 firmware. Question are they ticking time bombs ? Meaning if we make a change on thoses switches are they going to lock up. Maybe it has nothing to do with the titanium's at all ?

Note we had no problems with original switch on 1.39 firmware, with make changes, and the 1.42 flash went ok, but at this location minute you make a change on switch with the 1.42 firmare on it. The switch locks up.

Any help would be greatly appreciated

[sirhc]

Hi we have tried this on 6 or 7 switches seemed to be no issue however on 1 switch WS-400B we have 2 rocket m titanium's locked to 100MF at radio and switch do to the gigabit lock up bug. Once we deployed 1.42 these locked up and stopped responding. We tried to make a change on switch to reboot them switch locks up. Says applying config will revert if changes fail etc. never comes back. Switch works just cant log in etc. Reboot switch it is back up. By now starting to really piss off our PtP customers off this tower. Finally moved ports in switch for the titanium sectors got them to come and work. So we are thinking bad switch. Roll out at 6:30am this morning with new WS 400b switch with 1.42 firmware and config for switch, we are replacing on it. shut old switch down move cables over 1 by 1 and power up new switch boots up fine except Rocket titanium's not working again make a change on switch locks up. No matter what we do, reboot, switch is up make a change locks up. Couldn't bring Titaniums back.

Installing 3rd switch this morning on 1.39 firmware to try and bring the Rocket Titanium's back. We will use manual config this time.

We have titanium's on other switches that have been flashed to 1.42 firmware. Question are they ticking time bombs ? Meaning if we make a change on thoses switches are they going to lock up. Maybe it has nothing to do with the titanium's at all ?

Note we had no problems with original switch on 1.39 firmware, with make changes, and the 1.42 flash went ok, but at this location minute you make a change on switch with the 1.42 firmare on it. The switch locks up.

Any help would be greatly appreciated

Try holding in the default button for 20 seconds while powering up the switch.
Then let stand for 3 minutes or so while the switch re-formats the JFFS file system on the flash.
My guess is the original config file was corrupted and when you exported it and imported it to the next switch the problem followed the corrupted config file?

When you downgraded to v1.3.9 it re-wrote the config file fixing the corruption?

If you have the original corrupted config file please email it to me chris@netonix.com