NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS108E not accessible over tagged VLAN
Hi all, I have a backbone switch which is connected to several GS108(P)E v3 switches. The uplink port contains 3 VLANS (30,31,32) which are tagged on that port. These switches distribut the 3 VLANs ...
Thanks Kurt,
I re-thought everything after reading your post and concluded it could not be something on the GS108E v3 which were setup identically. So it had to be something on the backbone. I finally noticed that accessible GS108E v3 were connected to a port which had the PVID of the VLAN I want to contact the GS108E v3 over. I never expected this PVID to be of any influence on the tagged ports. After I set the PVID on the tagged ports on the backbone switch correctly I was able to manage the GS108E v3 centrally over the backbone / WLAN.
Thanks again - M.
Thanks Kurt,
I re-thought everything after reading your post and concluded it could not be something on the GS108E v3 which were setup identically. So it had to be something on the backbone. I finally noticed that accessible GS108E v3 were connected to a port which had the PVID of the VLAN I want to contact the GS108E v3 over. I never expected this PVID to be of any influence on the tagged ports. After I set the PVID on the tagged ports on the backbone switch correctly I was able to manage the GS108E v3 centrally over the backbone / WLAN.
Thanks again - M.
In brief, the way I understand the implementation:
The IP stack on the device does "listen" to all the traffic on the network. Only untagged frames are ending on the IP stack, tagged frames are not untagged and never taken as IP packets.
From this is my conclusion that the VLAN network for the config handling must be run untagged, (VLAN nnn [U], PVID nnn).
Well, see here the VLAN setup of my backbone XS716T:
If I understood it correctly I only have tagged VLANs here since VLAN Member and VLAN Tag and Tagged VLANs are the same for each port. However the PVID entry must be 31 if I want to access the config page of the connected GS108E v3 (connected to xg7 ... xg12). Does the PVID make the respective VLAN untagged ?
Thank you for your insights ... M.
The PVID does define the VLAN where untaggged frames will be associated to. There should by a related setting per port defining VLAN 31 [U], too to make it correct.
Yeah, that's what I thought, too. However, I told you what I observed, and you can see the settings of the XS716T which I used to connect to the GUI of the GS108E v3.
While this fits to my observations, too ...
If for whatever reason untagged frames are coming from the GS108E and we define these going to the VLAN 31 using the PVID 31 setting, while the other direction seems workable tagged seems workable (what fits to my observations), I suggest to rethink the implementation. The most logical way would be to run the VLAN 31 untagged on the links to these switches. so it's a clean implementation.
I don't like the idea that one frame direction is tagged, while frames in the other direction are untagged.
This leads me to the question for Netgear YeZ if this isn't a (systematic?) issue by the Plus switch design and implementation, at least on models without a managed core, that the IP management frames are not tagged properly, ignoring the VLAN config in fact.
That’s a hidden gem! It looks like there is NATIVE VLAN on those switches after all and PVID tells you which one it is 😉
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
