NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Management vLAN on PLUS switch
Hi All,
I have four Netgear Plus Managed switches around my home, not from a capacity need but more just ease of placement Vs having a larger switch in a central location and having to cable everything back there. These are; GS116Ev2, GS108PEv3, GS108Ev3 and GS110EMX. Each switch is on the current firmware release.
I’m changing from a flat network (192.168.0.x) to implementing 802.1Q vLAN’s along the lines of (vLAN 1 – set but not routed anywhere), vLAN2 – endpoints / 192.168.102.x, vLAN3 – IoT devices / 192.168.103.x, vLAN4 – infrastructure / 192.168.104.x and vLAN8 – guest / 192.168.108.x. I’ve got each of these vLAN’s configured on the switches with untagged PVID set as required on the device ports and port trunking / vLAN membership on the appropriate interconnecting, WAP & router ports. All appears to be working properly.
My question – in the switch management software there isn’t a way to set a vLAN ID for the management IP on these switches and I’m reluctant to just change the IP to a vLAN4 subnet in case I then find I can’t get into the management interface again. The management IPs are still in the 192.168.0.x subnet currently. Does anyone know the correct way to set the vLAN / IP info to set the management IP on my vLAN4?
Thanks,
Colin
In case the VLAN carrying the Plus switch admin traffic is coming as [T]agged to the Plus switch, the Plus switch config Web UI (and the NSDP protocol) won't be able to discover and manage the Plus switch.
The workaround is simple: Keep the traffic you intend to use for the Plus switches management Subnet VLAN as untagged - so avoiding the IP subnet traffic does come over tagged frames to the Plus switches.
Sorry if this is to brief, I'm about on giving up my free unpaid support to the community here, because Netgear is unwilling to valuate and compensate (time, effort, network resources, power, ...) what we are doing here. The model of providing some free NFR (unsellable) Netgear devices does not compensate for out private investment in time and resources.
4 Replies
Here again, most o the Plus switches are not built on managed cores. Thetiny uC will see all IP traffic on untagged frames, nothing you can do to change. In its heart it's an unmanaged switch with some configuration options.
You can change the Plus switch admin IP address to any IP subnet you prefer. Any system connecting needs to hav an IP address in that very same subnet. Limitations exist in the MTU because most of the Plus switches don't support any PMTUD and can't be reached in nonstandard Ethernet MTUs, eg. via VPN routers.
The admin IP can be any address like on a connected host - because this is what the uC is... Just it does not understand any tagged VLANs or nonstandard MTUs.
Thanks schumaku for your replies and sorry if I've asked something that has been asked elsewhere - I had tried to search the forum but not found anything under either the switch models or "Plus management vLAN", probably just not searched for the correct terms. I'd also read the user manuals for the switches and couldn't find a clear answer there either.
Anyway, just to clarify, if I have a fully utilised switch with all untagged endpoint ports on vLAN's & subnets different to the switch management IP and with an uplink port tagged with all vLAN's, including the switch IP subnet, does this mean the management IP would not be accessible from the rest of the network as the uplink port is tagged traffic only?
If so, would I need to have an untagged port on the vLAN with the correct subnet for the switch IP, even if I don't have anything connected to that port? Or, can I just have an untagged port that is a member of two vLAN's (one with the management subnet) and rely upon the PVID to tag the port connected client data to its intended vLAN? If it makes a difference, I'm using 802.1Q vLAN's
It all seemed so easy when I set off on this.
Thanks again,
Colin
In case the VLAN carrying the Plus switch admin traffic is coming as [T]agged to the Plus switch, the Plus switch config Web UI (and the NSDP protocol) won't be able to discover and manage the Plus switch.
The workaround is simple: Keep the traffic you intend to use for the Plus switches management Subnet VLAN as untagged - so avoiding the IP subnet traffic does come over tagged frames to the Plus switches.
Sorry if this is to brief, I'm about on giving up my free unpaid support to the community here, because Netgear is unwilling to valuate and compensate (time, effort, network resources, power, ...) what we are doing here. The model of providing some free NFR (unsellable) Netgear devices does not compensate for out private investment in time and resources.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
