Business Community > All Threads > Tagged VLANs not working on JetStream switches?
< All Threads

Tagged VLANs not working on JetStream switches?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Tagged VLANs not working on JetStream switches?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Tagged VLANs not working on JetStream switches?
Tagged VLANs not working on JetStream switches?
2020-11-19 22:10:42 - last edited 2020-11-24 16:40:58
Model: T1700X-16TS  
Hardware Version: V2
Firmware Version: 2.0.0 Build 20160922

I have a problem where JetStream switches (T1700X-16TS and T1700G-28TQ) are not properly passing traffic when using ports with tagged 802.1Q VLANs. When using untagged VLANs, there are no problems.

 

With the following setup:

Switch A: T1700X-16TS (ports 13-16 are using SFP+ copper and fiber)

Switch B: T1700G-28TQ (ports 25-28 are using SFP+ copper and fiber)

Switch C: T1700X-16TS (ports 13-16 are using SFP+ copper and fiber)

 

For example, this works:

Workstation 1 (Windows 10) 1gig -> Port B2 (Untagged VLAN 1, PVID 1) -> Port B25 (Untagged VLAN 1, PVID 1) -> Port A13 (Untagged VLAN 1, PVID 1) -> Port A11 (Untagged VLAN 1, PVID 1) -> Server 1 (Linux) 10gig

Workstation 2 (MacOS) 1gig -> Port B3 (Untagged VLAN 1, PVID 1) -> Port B25 (Untagged VLAN 1, PVID 1) -> Port A13 (Untagged VLAN 1, PVID 1) -> Port A11 (Untagged VLAN 1, PVID 1) -> Server 1 (Linux) 10gig

 

But this doesn’t work:

Workstation 1 (Windows 10) 1gig -> Port B2 (Untagged VLAN 111, PVID 111) -> Port B25 (Tagged VLAN 111, PVID 111) -> Port A13 (Tagged VLAN 111, PVID 111) -> Port A11 (Tagged VLAN 111, PVID 111) -> Server 1 (Linux, VLAN setup using networkd) 10gig

Workstation 1 can ping Server 1, and vice versa, but copying a file (scp) or simply running the “top” command from a ssh session will both hang.

Same problem when trying workstation 2; can ping, but traffic doesn’t seem to pass for more than a second.

 

This also doesn’t work:

Workstation 1 (Windows 10) 1gig -> Port B2 (Untagged VLAN 111, PVID 111) -> Port B25 (Tagged VLAN 111, Untagged VLAN 1, PVID 1) -> Port A13 (Tagged VLAN 111, Untagged VLAN 1, PVID 1) -> Port A11 (Untagged VLAN 111, PVID 111) -> Server 1 (Linux) 10gig

 

Has anyone else successfully used tagged VLANs with these switches?

  0      
 
  0      
 
#1
Options
3 Reply
Re:Tagged VLANs not working on JetStream switches?
2020-11-24 16:57:17

So I did some further testing, and it appears the problem is not just with "trunk" ports between the two switches. Even tagged VLANs between ports on the same switch are having the problem.

 

See the above post for how the switches are setup. I then connected two servers to swith A as follows.

 

Server 1 (Linux) 10gig -> Port A10 (Untagged VLAN 1, PVID 1, tagged VLAN 111) ->  Port A11 (Untagged VLAN 1, PVID 1, tagged VLAN 111) -> Server 2 (Linux) 10gig

 

VLANs configured on the Linux servers using networkd.

 

If I ping from server 1 to server 2 on the untagged interface I have no problems. 

 

PING 192.168.192.27 (192.168.192.27) 56(84) bytes of data.
64 bytes from 192.168.192.27: icmp_seq=1 ttl=64 time=0.191 ms
etc.

--- 192.168.192.27 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9214ms
rtt min/avg/max/mdev = 0.129/0.147/0.191/0.022 ms

 

When I run a bandwidth test on the untagged interface, no problems:

 

Connecting to host 192.168.192.27, port 5201
[  4] local 192.168.192.17 port 51850 connected to 192.168.192.27 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  1.08 GBytes  9.27 Gbits/sec    0    550 KBytes       
[  4]   1.00-2.00   sec  1.09 GBytes  9.34 Gbits/sec    0    605 KBytes       
[  4]   2.00-3.00   sec  1.09 GBytes  9.34 Gbits/sec    0    635 KBytes       
[  4]   3.00-4.00   sec  1.09 GBytes  9.34 Gbits/sec    0    665 KBytes       
[  4]   4.00-5.00   sec  1.09 GBytes  9.34 Gbits/sec    0    697 KBytes       
[  4]   5.00-6.00   sec  1.09 GBytes  9.34 Gbits/sec    0    732 KBytes       
[  4]   6.00-7.00   sec  1.09 GBytes  9.35 Gbits/sec    0    766 KBytes       
[  4]   7.00-8.00   sec  1.09 GBytes  9.35 Gbits/sec    0    803 KBytes       
[  4]   8.00-9.00   sec  1.09 GBytes  9.35 Gbits/sec    0    843 KBytes       
[  4]   9.00-10.00  sec  1.09 GBytes  9.35 Gbits/sec    0    882 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  10.9 GBytes  9.34 Gbits/sec    0             sender
[  4]   0.00-10.00  sec  10.9 GBytes  9.33 Gbits/sec                  receiver

iperf Done.

 

 

If I ping from server 1 to server 2 on the tagged interface I have no problems:

 

PING 192.168.75.27 (192.168.75.27) 56(84) bytes of data.
64 bytes from 192.168.75.27: icmp_seq=1 ttl=64 time=0.287 ms
etc.

--- 192.168.75.27 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9214ms
rtt min/avg/max/mdev = 0.127/0.163/0.287/0.043 ms

 

When I run a bandwidth test on the tagged interface, it appears data is being throttled:

 

Connecting to host 192.168.75.27, port 5201
[  4] local 192.168.75.17 port 49420 connected to 192.168.75.27 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec  84.8 KBytes   694 Kbits/sec    2   1.41 KBytes       
[  4]   1.00-2.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  4]   2.00-3.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  4]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  4]   4.00-5.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  4]   5.00-6.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  4]   6.00-7.00   sec  0.00 Bytes  0.00 bits/sec    1   1.41 KBytes       
[  4]   7.00-8.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  4]   8.00-9.00   sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
[  4]   9.00-10.00  sec  0.00 Bytes  0.00 bits/sec    0   1.41 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  84.8 KBytes  69.5 Kbits/sec    5             sender
[  4]   0.00-10.00  sec  0.00 Bytes  0.00 bits/sec                  receiver

iperf Done.

 

Has anyone else observed this? Are Jetstream switches actually capable of using tagged VLANs? I ask becuase my IT folks laugh at me for not getting Cisco or Arista :-)

  0  
  0  
#2
Options
Re:Tagged VLANs not working on JetStream switches?
2020-11-26 09:42:11

Dear @jhusker,

 

We haven't received such feedback before. Could you please provide more info for further analysis?

 

With the following setup:

Switch A: T1700X-16TS (ports 13-16 are using SFP+ copper and fiber)

Switch B: T1700G-28TQ (ports 25-28 are using SFP+ copper and fiber)

Switch C: T1700X-16TS (ports 13-16 are using SFP+ copper and fiber)

 

How are the 3 switches connected? Can you draw a simple network topology?

Do you configure any advanced functions such as ACL on the switches?

 

But this doesn’t work:

Workstation 1 (Windows 10) 1gig -> Port B2 (Untagged VLAN 111, PVID 111) -> Port B25 (Tagged VLAN 111, PVID 111) -> Port A13 (Tagged VLAN 111, PVID 111) -> Port A11 (Tagged VLAN 111, PVID 111) -> Server 1 (Linux, VLAN setup using networkd) 10gig

Workstation 1 can ping Server 1, and vice versa, but copying a file (scp) or simply running the “top” command from a ssh session will both hang.

Same problem when trying workstation 2; can ping, but traffic doesn’t seem to pass for more than a second.

 

If the ping works, then the tagged VLAN works between the switches, otherwise, the ping won't work at all. There should be something we overlooked. If you connect Workstation 1(Windows 10) to Port A10 (Tagged VLAN111, PVID111), would the problem still exist?

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#3
Options
Re:Tagged VLANs not working on JetStream switches?
2020-11-26 10:01:15

Dear @jhusker,

 

See the above post for how the switches are setup. I then connected two servers to swith A as follows.

Server 1 (Linux) 10gig -> Port A10 (Untagged VLAN 1, PVID 1, tagged VLAN 111) ->  Port A11 (Untagged VLAN 1, PVID 1, tagged VLAN 111) -> Server 2 (Linux) 10gig

 

When I run a bandwidth test on the untagged interface, no problems:

 

Connecting to host 192.168.192.27, port 5201
[  4] local 192.168.192.17 port 51850 connected to 192.168.192.27 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
 

When I run a bandwidth test on the tagged interface, it appears data is being throttled:

 

Connecting to host 192.168.75.27, port 5201
[  4] local 192.168.75.17 port 49420 connected to 192.168.75.27 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd

iperf Done.

 

How did you run the bandwidth test on the Tagged interface?

Did you just set VLAN111 on both Server 1 and Server 2 before you run the bandwidth test?

Could you use the same port on the client to run the Iperf test for checking?

 

I don't think it is the VLAN configuration issue since the ping test works, so the VLAN tagged traffic can be forwarded properly in Layer 2.

For the current problem you posted, it could have something to do with Layer 3 settings, and you may check the firewall settings.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 1125

Replies: 3

Related Articles
JetStream switches and DHCP server
613 0
VLAN Configuration - Jetstream Switches
251 0
Vlans not being tagged
911 0
How to use JetStream switches in a distributed environment
477 0
OMADA Controller & JetStream switches
2073 0
Australian Daylight Saving adjustment not working on JetStream switches
1351 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.