Hi Mark,
Community here, not formal Netgear tech support. 8-)
@MarkChristy wrote:
However, the help documents dictate configuring this puppy over a web interface. When you try and configure the uplink port, it breaks your current connection to the management IP address.
Not very different from whatever expensive different brand switch while doing in-band config, regardless of whatever access protocol you are using, isn't it?
Unfortunately, you don't tell us much about the uplink config on the other side (VLANs, IP subnet, DHCP), and on how you initially access it. These switches are very simple configurable devices. As such, we must understand the limitations of the microcontroller serving various purposes.
First, be aware the microcontroller does access all VLANs concurrently, means there is no management VLAN, the switches can pick up an IP config from any VLAN DHCP address. Second, due to the microcontroller simplicity IP stack, the DHCP server can time-out and fall back to the default IP - it will not retry even if the device is set to be a DHCP client.
This should give you an idea what might happen while doing your config.
The most simple way is keep the VLAN you intend to use on the uplink port untagged, initial access the switch on it's default IP or the DHCP assigned IP, then set the IP to a local static config. In case it tends to pick an IP config from a different upstream VLAN DHCP already (the NETGEAR Switch Discovery Tool (NSDT) is your friend), disable these for a moment (and power reboot due to the DHCP client shortcoming). Now configure the ports, including the uplink as required.
To avoid another small hurdle, don't forget about the need for setting the PVID to the single VLAN ID you run [U]ntgged to the device. The PVID does define the VLAN ID where untagged frames flowing into the switch port will be assigned to.
It's nothing difficult, it isn't overly complex - when keeping these points in mind.
Regards,
-Kurt
