Netgear M4100-D12G - IPV4 Net Interface

Sometime switches offers device IP and management IP separately so that you keep the access to the router/switch away from the other users.

Makes sense. Can anyone confirm that ?

I set the management IP to 192.168.4.X
It is on the 192.168.4.0 sub net and works fine. I don't understand why though I can't set the Logical Net IPV4 Interface though of the switch to another spare / free IP on the same 192.168.4.0. If I try to it generates a very generic unhelpful error (unable to set or something like that).

If I where you setup management IP to 192.168.5.x while keeping rest of switch setting using 192.168.4.x

Likely to be refusing because of security issues that you do not want both to be on same subnet if above works

Hi,

I have exactly the same question and issue.

In the installation guide the book tells you to use the web to setup the LAN interface. The LAN interface it shows is the management IP address setup, as per the guide. However, it also says you can use the CLI and ezconfig to set the management/LAN interface. When you use ezyconfig, the value displayed on the web interface remains at the default. If you change it via the web interface, you can now access the web interface both from the IP address you created on the ezconfig AND via the value you just entered via the web gui.

It is extremely confusing and concerning as the programmed value from the CLI is different to that on the web GUI.

Here is the clarification regarding both.

The switches have network parameters (network parms)
this is ip address, subnet and gateway assigned to management interface. This value you see in the web gui under network interface.

The switch also support static routing which allow you to bind ip address to the vlan or port.

By default when you use ezconfig, on previously version netgear did the following

network parameters   

OR

network parms   

On newer firmware, when you use ezconfig, they do the following

vlan database
vlan routing 1
exit
config
interface vlan 1
ip adddress  
exit
ip routing
ip route default 
exit

The different is that first is tied to management vlan. which can be changed using

network mgmt_vlan 

and second is tied to vlan 1 interface. Since the default vlan on the switch is vlan 1, it seems better to have vlan 1 routing interface take the IP address since poeple who buy the switches will sooner or later want to do vlan routing. Since the GUI and other services are accessible by routing interface, it makes it easy to allow use of the switch. If people would consider security then they would plan out ACL and access configuration to limit exposure to the switch.

Another reason is that good admin will not use vlan 1 for management and will reconfigure the management vlan to different vlan. If you configure vlan 1 routing then when you try to configure the IP on network interface in the GUI, it won't let you use the same subnet since it is already existing interface assigned to it on vlan 1. If configure a different address then it sort becomes like multi homed address concept on vlan 1.

I hope that makes more sense.

Hi, please can I bump in here? I cannot follow the above but I am having real problems setting a fixed IP for management purposes. The default setting for the management interface is to have DHCP enabled and this is working fine. My problem is that I want to turn off the DHCP and assign a fixed IP. ie from addresses not available on DHCP but on the same subnet. If I turn off the network configuration protocol I am then able to edit the IP address but whatever I do I cannot make it stick. As soon as I apply the address I lose access to the device and cannot then save the configuration. If I try and access the web interface at this point I cannot access using either the new "applied" IP address or the original one issued by the DHCP server. How may I set a fixed IP for the management address of the device please?