For some reason this forum wouldn't let me post my whole detailed experience - kept saying 'Illegal Content in Title or Links' even though I had no Links and the title was: Setup Issues with vLANS on TL-SX3016F ... what PITA.

Long story short - the ONLY way I could get this new TLSX3016F to work on my network was to give EVERY SINGLE vLAN I have in the entire domain/network its own Interface AND IP address in the appropriate subnet, even though I have turned off ALL Layer 3 services ( I have another Layer 3 switch that does all my inter-vlan routing etc). If the vLAN interface does not have an IP - you cannot ping the switch, at all, and NO DATA will flow through the 'Trunk' back to the rest of my network. I only wanted an IP address in my Mangement vLAN - 10.0.100.20. With only this Ip address setup - I could ping from my laptop on vLAN100, but could not ping from a Server on vLAN10. I had to add an IP to teh vlan 10 vlan interface on the switch. As soon as that was added I could ping BOTH IP addresses the switch had - 10.0.100.20 and 10.0.10.99.

I set Port 1 (1/0/1) like:

Any othe rcombination of PVIDs, Tagged or Untagged would not work. And if I did not specify an IP for each vLAN Interface it also would not ping.

Is this by design? I've never seen a decent Enterprise or Business switch that does vLANs ever do this. On every other switch I've deployed (Dells, Cisco's, Edgeswitches, Netgears etc) I basically set the port to Trunk and Tag thje vLANs I want to traverse through it - job done. This seems kinda wasteful and tedious.