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).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
