Netgear vlan not working

[nicholab]

I am having issue getting a vlan to connect on two netgear switches the switches have LAG link with vlan's in place I am trying to add another vlan but it it not working.

 

I have added the vlan membership to the LAG but it is still not working and also the PVID but it not working?

[Boredguy]

Have you set the vLAN for the LAG to be T (Tagged) for your additional vLan id's and not U.

[nicholab]

Does it need to be tagged even if it is an end device?

[Boredguy]

If you have multiple vLANS going over the LAG, it should be Tagged at both ends so what to do with the packets.

 

If the LAG it just between switches, then Tag at both ends and it should be fine. We have around 3 vLANs on average configured on our Switch to Switch ports and all of them are Tagged with the pVID set to our default vLan.

[nicholab]

The LAG links are as tagged each end and the LAG is tagged on the up-link port and untagged on the client LAG port. The PVID is set as 10 on the LAG interface.

[Boredguy]

In your original post you said it was between 2 netgear switches.

In which case both ends need to be set as Tagged so that all packages have the vLan wrapper added (especially if you have more than 1 vLan going over it)

 

Switch 1 (LAG 1) -> Switch 2 (LAG 1) T at both ends

[nicholab]

I have this setup

 

Switch 1 (LAG 1) -> Switch 2 (LAG 1) T at both ends

Switch 2 (LAG 1) T to Device (LAG 2) U.

[Boredguy]

Why have you got LAG1 on switch 2 going to 2 seperate locations?

 

LAG1 between Switch 1 and Switch 2 is correct.

But if you want multiple ports to link to an end device, you need to use LAG2 on Switch 2 and set the vLAN for that, as LAG1 is being used to talk to Switch 1

[Davit2005]

What is the LAG2 for?????

[nicholab]

My set up I have

 

SW1 LAG10 T going to SW2 LAG1 T

 

On SW2 LAG 1 T, LAG 2 U in vlan 10

 

But these stupid things don't work how can configuring a vlan be such a pain?

[Boredguy]

For simplicity, taking the LAG out of it for now.

 

Connecting between the 2 switches so vLANS 10 & 20 can both send traffic over the connecting cable

Switch 1, Port 1 has vLan 10 & 20 Tagged

Switch 2, Port 1 has vLan 10 & 20 Tagged

 

Now on Switch 2, there is a end device that is on vLan 10 and another that is on vLan 20

Switch 2, Port 2 has vLan 10 Untagged and PVID of 10

Switch 2, Port 3 has vLan 20 Untagged and PVID of 20

[nicholab]

For simplicity, taking the LAG out of it for now.

 

Connecting between the 2 switches so vLANS 10 & 20 can both send traffic over the connecting cable

Switch 1, Port 1 has vLan 10 & 20 Tagged

Switch 2, Port 1 has vLan 10 & 20 Tagged

 

Now on Switch 2, there is a end device that is on vLan 10 and another that is on vLan 20

Switch 2, Port 2 has vLan 10 Untagged and PVID of 10

Switch 2, Port 3 has vLan 20 Untagged and PVID of 20

 

This is what I should have vlan 10 LAG 2 is U and PVID of 10 but this does not work. The PVID is as stupid additional setup to make it break.

[Boredguy]

The PVID limits the port to only that traffic. Depending on the model of the switch, it's the only way to remove vLan 1 from that port, but it's not always required