TSW212 1.7: untagged VLAN membership required for each port

[jan.tomandl]

I have updated my TSW212 to FW 1.7 right now. I found that there is a new feature (?) that each port MUST be a member of one untagged VLAN.

Previously I had following config:

VLAN1     P1 untagged, P3,8 tagged
VLAN2     P2 untagged, P3,8 tagged
VLAN3     P4,5,6,7 untagged.

Now it does not allow me to have this config. I had to add a “dummy” VLAN4 so the config is as follows:

VLAN1     P1 untagged, P3,8 tagged
VLAN2     P2 untagged, P3,8 tagged
VLAN3     P4,5,6,7 untagged.
VLAN4     P3,8 untagged  

Note: in my case there is not any untagged traffic at port 3,8.

Can anyone explain me reason for this change?

Is it for defining explicit rule what the switch shall do if it receives an untagged packet the respective port? Ok, but then what the switch did in such situation in previous FW? Was this a bug?

Thx

Jan

[anon65719490]

Hello,

Thank you for your inquiry and interest.

This change is currently under review. Once we have gathered more relevant information from our internal sources regarding why this implementation was introduced, I will update you here with further details.

Best regards,

[anon65719490]

Hello,

After further digging and investigation, this VLAN behavior seems unusual. Here to assist and troubleshoot this specific situation, we’ll need to continue this process privately, because sensitive/publicly unshareable information, such as the troubleshoot file, public IP addresses, serial numbers, etc., needs to be collected.

You should find a support request form in the inbox of the email address you used for your forum registration. Kindly fill out the form, and please reference Ticket ID: 15573 when submitting it. Once the form is completed, we’ll contact you directly via email to investigate the issue in depth.

Best regards,