Issue with WS-12-250X using port 13&14 in VLANS

[sirhc]

Hi guys,

Adam from cirrinity.net discovered an issue with using ports 13 & 14 with VLANS on the WS-12-250A and WS-12-250B models.

Ports 13 & 14 we NOT getting properly configured with VLANS.

This does not affect the WS-24-400A or WS-24-400B models.

We will have a firmware update available in about an hour to fix this issue.

[adairw]

I need to verify my cable configuration, but I'm pretty sure they are right.
I have a WS-12-250A with copper sfp's in ports 13 and 14. I was trunking two vlans out to a mikrotik and previous to the copper sfp's things were working. Added the SFP's and moved the trunked vlan's to port 13 (was on 11 prior) and now I can't access the devices plugged in to those untagged vlan ports.
I am running 1.0.2RC5

[Rory]

First thing's first, lets get you running a newer version of the firmware. The version you are using has some specific sfp fixes, but there were a few VLAN changes in more recent versions. Please look at the post here: http://forum.netonix.com/viewtopic.php?f=17&t=240 . There is a link at the top for the most recent version. Please let us know if the problems persist once the switches are upgraded.

[adairw]

yep, I'm already on 1.0.5rc2.
Here are a couple of screen shots showing the simple config.
I forgot to verify the cable when I was there today but I'm 99% sure they got plugged in to the right locations.

[iggy05]

Can you still access Vlan 1? I was still able to access Vlan 1 no matter what when it was broken for me but everything is now fixed after one of the new updates. I can't remember right off hand witch version I am on right now and I would have to go out there to check.

[adairw]

It appears that untagged frames are passing just fine. It's only when you tag that things don't work correctly.

[adairw]

Updated to 1.0.6rc1 and still can't passed tagged frames over ports 13 & 14. Just to troubleshoot I may default the switch and test, just to make sure it's not a borked config.

[adairw]

Defaulted the switch and no change on passing tagged frames....

however...

I also found another oddity (bug?) from a default config, I had not turned on any power to any of the ports yet my cameras are up and passing traffic???? I will start a new post on this as well.

[sirhc]

This is your second post on the same issue.

No that should not occur, this is an over sight in my count.
But I know why, I will have to have Eric fix that tomorrow.
If you remember we changed the unit so that you can reboot it and it leaves the POE ports on during the reboot or after a firmware upgrade ti limit radio down time.
I did not think about people having POE turned on or configured on then defaulting it in the UI.
If you power cycled it would turn them off to match the defaulted config.
I will have Eric make sure he turns all the POE off if you do a software UI default.
Good catch

[adairw]

This is your second post on the same issue.

Yep, because I didn't want two different problems getting wrapped up with this one.