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 to 2 exclusive ports each (untagged). All GS108(P)E v3 switches are setup with manual IP address and gateway settings.
All switches do what they're supposed to do. I can connect a device to the LAN by pushing the plug into the corresponding port and it will get an IP address from the DHCP server of that LAN. However, about 30% of the GS108(P)E v3 switches cannot be pinged from the backbone. They only respond when I plug my notebook into one of the untagged ports.
I want to reconfigure my switches centrally over the LAN, so this is nasty since not all switches in my network show up. The matter is depending on the GS108(P)E v3, not on the backbone switch. The firmware is identical (V2.06.03EN). I checked all other settings, they seem to be identical.
Any thoughts or hints about this ?
Thanks - 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.
12 Replies
Most of these Web configurable switches are not built on a managed switch core with a management VLAN and a management core handled by an untagged management CPU connected to an internal untagged port. There is a small microcontroller listening on all frames passing the switch, taking care on e.g. ICMP multicast or the managment IP stack. No management VLAN, the controller does not deal with tagged frames.
Technically, it does not matter over which VLAN the untagged management frames are going in and out of the microcontroller, relevant is just the IP subnet and IP adddress.
For simplicity, run the management VLAN for these "Plus" switches untagged on the wired backhaul all over your network, keep all other VLANs tragged.
Few newer 10 GbE and Multigig Plus switrches (xxnnnEx) are implemented on a management core - there is a proper management CPU on a management VLAN. These behave more like a managed switch - something these Web managed Plus switches were never intended for.
Regards
-Kurt
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!
