NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AX4200 Management VLAN, Static IP incompatible?
I have a few AX4200s at home. They are configured to use 3 different static IPs for their management interface. I'm running 3 explicit vlans - 1001 for management, 1002 and 1003 for different classes...
BGalehouse wrote:
Now, when I try to make any changes to on the networking management page, I get an interstitial error: "Current IPv4 setting is set as Static, not allow user to Enable Management VLAN". I guess it thinks that I'm trying to change the management VLAN (even though it is already running on VLAN 1001, and I'm not actually trying to change that), and therefore some "safety" check means it doesn't want me to have a static IP set.
Not convinced these WAX2xx allow defining a management VLAN -and- a static LAN IP for the management.
Said that, I strongly doubt your management VLAN is already on the VLAN you expect it to be. Strongly suggest to double check your unknown magic router does correctly assign DHCP addresses in the appropriate VLAN subnet. Before moving the WAX220 management VLAN to a tagged network, first you need to configure the trunks on your switch (for both the router uplinks as well as for the WAX220. Start with an untagged management VLAN to avoid more confusion!- Configure an access port (resp. a port untagged, but assigned to the management VLAN, and set the PVID on the switch to the same VLAN) for the management VLAN. Now double check the DHCP server does assign an IP config for the management VLAN and IP subnet. If it's correct, change the switch port to tagged for the management VLAN, and change the WAX220 config to use the management VLAN. If you desire, look if it's possible to change the WAX220 LAN IP to a static IP now. But not before!
Note: All my WAX operating on VLANs are using DHCP with MAC-IP address pairs reserved - I try to avoid putting fixed LAN IPs where not required. Thus I never had the idea to put up a static LAN IP on a WAX2xx configured for a tagged management VLAN.
Regards,
-Kurt.
schumaku wrote:Not convinced these WAX2xx allow defining a management VLAN -and- a static LAN IP for the management.
Said that, I strongly doubt your management VLAN is already on the VLAN you expect it to be. Strongly suggest to double check your unknown magic router does correctly assign DHCP addresses in the appropriate VLAN subnet.
WAX220 let me set it up that way - first changing the VLAN, then to a static IP. But this put it in a state where I cannot make more wireless changes. So I guess it is effectively unsupported/broken by design. As I said though, I'll revert the static IP setting, at least from the APs viewpoint and that will probable work around it.
I'm quite certain at this point that the router is doing the right thing. Previously I used a Mikrotik with this VLAN structure, now I use an Arch box. In both cases you set up a virtual interface for each VLAN and go from there with a dhcp pool configuration for each and so on and so forth.
If you believe the router port config is correct, change the VLAN config to the tagged management port (and set the WAX220 to DHCP) - not connect the WAX20 direct to the router. Nothing that stops you from this test. Now time to configure the switch correct to use the tagged VLAN trunks.
The switch message was very clear: "Current IPv4 setting is set as Static, not allow user to Enable Management VLAN". Isn't it? So return to DHCP, re-activate the management VLAN, ... No short cuts supported. The price for deploying Business Essentials line models I guess.
Have managed to configure the VLAN trunks required on the switch accordingly in the meantime?
The message "Current IPv4 setting is set as Static, not allow user to Enable Management VLAN" is from any AP, when I try to further adjust wireless settings. It is not a message from the switch.
I'm convinced the message is a firmware bug, because the management VLAN is already set and operational on the APs. In particular, the error message arrives over the management VLAN, from the static IPs, because that is how I access the AP web interfaces. Also, the management VLAN isn't something that I'm trying to change at this point, but is pre-populated as 1001 on the wireless settings page.
BGalehouse wrote:
The message "Current IPv4 setting is set as Static, not allow user to Enable Management VLAN" is from any AP, when I try to further adjust wireless settings. It is not a message from the switch.
Yes, my bad, lack of sleep along time after midnight. Talking of the WAX220 here. Conclude, the WAX220 was never enabled for the tagged management VLAN, because it does not allow enabling the management VLAN.
BGalehouse wrote:
I'm convinced the message is a firmware bug, because the management VLAN is already set and operational on the APs. In particular, the error message arrives over the management VLAN, from the static IPs, because that is how I access the AP web interfaces. Also, the management VLAN isn't something that I'm trying to change at this point, but is pre-populated as 1001 on the wireless settings page.
Seriously think the WAX220 magically changing the VLAN, despite having a static IP configured, and under the impression you are accessing the WAX220 over the management VLAN (despite not having configured the switch accordingly). I'm about to bet on a beer you still access the WAX220 over the untagged network my new friend.
The wireless settings page defines the SSID<->VLAN relation only. Easy possible operating the same IP subnet over tagged and untagged connections.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
