TL-SX3016F Setup Issues with vLANs etc
TL-SX3016F Setup Issues with vLANs etc
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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @AusDread,
If the Port 1 (1/0/1) is the uplink port that connects other switches, you may set the Port1 to TAGGED all VLANs (Trunk port), and no need to set the PVID for a trunk port. Besides, terminal devices like computers, NVRs usually do not support VLAN tags, so you may set the port that connects terminal devices to UNTAGGED port for the corresponding VLANs and specify the PVID.
For example, if your network topology is like the following setup
PCs (VLAN100 or VLAN10) --- Main Switch (VLAN10, VLAN100) ---- (Trunk) Switch1 (Trunk) ---- (Port 1) TP-Link SX3016F (Port16 - VLAN10 to NVR1, Port 15 - VLAN100 to NVR2)
To make the PCs from Main Switch side talk to NVRs connected to SX3016F switch from corresponding VLANs (vlan10 or vlan100), you may configure the VLAN setup on the SX3016F as the following.
Port 1: Tagged port with VLAN10 and VLAN100
Port 16: Untagged port with VLAN10, PVID as 10
Port 15: Untagged port with VLAN100, PVID as 100.
Hope that helps!
Related Configuration Guide: Configuring 802.1Q VLAN
- Copy Link
- Report Inappropriate Content
Looks like that has fixed it! Cheers Fae!
Will do a bit more testing a few more reboots to make sure there is nothing 'hinky' going on but final working config was to:
All Layer 3 Routing turned OFF/DISABLED
vLAN 1 Interface
No ip address
vLAN 100 Interface
ip address 10.0.100.20 255.255.255.0
*This is to set my switch into my Management vLAN which is 100 across my network
Port 1, my 'Trunk' port
Re-set PVID to 1
Set vLANs 10 and 100 to TAGGED
Port 16, Ubiquiti NVR plugged in
Set PVID to 100
Set vLAN 100 Untagged
Traffic from vLANS 10 and 100 appears to now be traversing the 10G 'trunk' between my ES-48's switches (tested in 3 switches, so all good there now) and I can get a vLAN 10 or vLAN 100 IP from my Windows DHCP server depending on wether or not I put port 16 into vLAN 10 or vLAN 100, set it to UNTAGGED and change the PVID to that vLAN.
Awesome. All working as it should now ;)
So tomorrow we start with LAG's. If all goes fine I'll grab another of these switches to put over in Building 2 and link two fibre runs back to this one ;)
Cheers for all the help, tips and advice from ALL contributors. It's greatly appreciated ;)
- Copy Link
- Report Inappropriate Content
Dear @AusDread,
Thanks for sharing the results, I'm glad to hear that it works now!
Here is a LAG configuration guide you may refer to. Configuring LAG
I'd also like to add a kind note to others who may see this thread,
If you're configuring your JetStream switches in Standalone mode, please always remember to Save Config once you complete the configuration, otherwise, the settings would be lost after a reboot.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2093
Replies: 13
Voters 0
No one has voted for it yet.