v1.3.0 & v1.3.1 & v1.3.2 FINAL bug reports and comments

[mike99]

WS-12-250A: MAC table don't work on SFP with 1.3.2.

It work fine on WS-24-400A. Didn't try yet on WS-12-250AC.

[sirhc]

Eric is looking at releasing v1.3.3rcX Wednesday evening.

Fixes:
300+ VLANs will not bog down the UI or go out to lunch for a long time saving the config
2000+ MAC entries will not slow down UI

Enhancements:
POE port time conditions on the Power Tab for SMART DC switches so you can have the DC Switch auto shut down a POE port based on time conditions say late at night when a heavy link like AF24 would not be needed. THat way it can run off the lower power consumption backup link.

On the action list:
Investigate the aforementioned MAC table with SFP ports issue

[sakita]

Didn't see a thread for 1.3.2 firmware, so I'm posting it here.

WS-12-250-AC switch log includes the following curious messages...

Dec 31 19:07:24 kernel: link state changed to 'down' on port 25
Dec 31 19:07:27 kernel: link state changed to 'up' on port 25
Dec 31 19:07:46 kernel: link state changed to 'up' on port 25
Dec 31 19:07:46 kernel: link state changed to 'up' on port 25

...is port 25 something internal?

[sirhc]

Didn't see a thread for 1.3.2 firmware, so I'm posting it here.

WS-12-250-AC switch log includes the following curious messages...

Dec 31 19:07:24 kernel: link state changed to 'down' on port 25
Dec 31 19:07:27 kernel: link state changed to 'up' on port 25
Dec 31 19:07:46 kernel: link state changed to 'up' on port 25
Dec 31 19:07:46 kernel: link state changed to 'up' on port 25

...is port 25 something internal?

Since we use the same switch core / chipset / firmware for all switches the SFP ports rather they are 12 ports or 24 ports the switch core internally sees them as ports 25 and 26.

We talked about changing this but believe it or nor it is in a lot of different modules.

So in the LOG on a 12 port switch port 25 is port 13 and port 26 is port 14 - ehh, it is on a long list of things to address someday

[cbl]

I upgraded a couple of switches this morning from 1.2.0rcX to 1.3.2. After it finished I was unable to access the IP of the switch as well as devices on the same VLAN. I narrowed it down to the MGMT VLAN that is tagged on a Trunk port. If I change the Cisco that the Trunk port plugs into to use a native VLAN on the MGMT VLAN Id, then I can reach the devices on that MGMT VLAN on the Netonix. Downgrading from 1.3.2 to 1.2.4 fixes this issue as it appears to pass the MGMT tagged correctly. I am using SFP fiber ports for my Trunk on these two cases.

[Magician]

I was setting of my first ( I Know I Know) WS-6-MINI last friday and ran into a bug. When installing new sites I place all radio ports off vlan access and test and power them. Then port by port I place on management vlan to configure the radios and then place on its designated vlan. Well on this unit it tested cables and the LED's show 24V passive is on but the radios are not powered. By placing the radio as a member of any vlan the unit powers.

To test this I dropped a live radio to exclude on all vlans and the radio lost power. Is there a reason you guys disable POE due to vlan config?

Thanks

[sirhc]

Yes this was already discussed in a previous post, I am moving this post to the proper thread.

viewtopic.php?f=17&t=930&start=20#p7338


We are correcting this in the next release

[mgthump]

hello,

we use a router at each site and I normally would put the public ip range at ETH2 on the router and a 2nd range ETH2.100 for management.

I've added and tagged vlan 100 on all the ports and marked them trunk hoping to get the native vlan to pass without any luck. DHCP messages and site access work for the vlan100 but I can't get native traffic to pass. I marked them all as trunk ports and I'm on software 1.3.2. little confused by this issue. I'm sure its something simple but not sure what I'm missing here.


I also tried to add VLAN 1 and marked all ports untagged to see if it would pass without any luck.

[sirhc]

hello,

we use a router at each site and I normally would put the public ip range at ETH2 on the router and a 2nd range ETH2.100 for management.

I've added and tagged vlan 100 on all the ports and marked them trunk hoping to get the native vlan to pass without any luck. DHCP messages and site access work for the vlan100 but I can't get native traffic to pass. I marked them all as trunk ports and I'm on software 1.3.2. little confused by this issue. I'm sure its something simple but not sure what I'm missing here.


I also tried to add VLAN 1 and marked all ports untagged to see if it would pass without any luck.

Try v1.3.3rc5 viewtopic.php?f=17&t=994

If that does not help please post your VLAN Tab

[mgthump]

1.3.3rc5 did the trick, everythings flowing well after the upgrade, Thanks!!