NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
JosLaan
Feb 28, 2017Aspirant
M4300-28G ip management port fails after restart in a stacked configuration.
Hello, we have a stacked configuration from 6 times a M4300-28G switch (firmware version 12.0.2.9), the stack up and running. The ip management port (IP4) is set to vlan 1 and via the web inter...
- Mar 16, 2017
Hi Jos,
We have received the TechSupport file just you sent to us.
This error may cause by serviceport enhancement in 12.0.2.x which add a new default IP address 192.168.0.239/24.
We also find a similar issue just like yours which will only appear on slave stack unit.
Maybe this issue have same root cause with yours.(default serviceport IP address)
So We will share the new firmware to you when the similar issue fix.
Please use a workaround method to avoid the error for now if possible:
Set the an another IP address on management VLAN.
Such as:
192.168.1.x/24
192.168.10.x/24
Thanks for your understanding and patience.
LaurentMa
Feb 28, 2017NETGEAR Expert
Hi JosLaan
Welcome to the community!
One possible reason would be: configuration lives in non-volatile memory, when it's saved. Until it is saved, it is applied in RAM only.
When you configure the switch, it is not saved automatically. Are you using Web Interface (GUI)? A Save button should do it.
I believe you had configured the Management VLAN IP address and clicked on "Apply" button on that GUI page.
By Applying the configuration, you save it in RAM and make it work in running config.
But the startup config remains untouched as this point: you should go to Maintenance -> Save Config and click SAVE button to write the running config into the startup config. Only the startup config in non-volatile memory is getting used after a reboot.
Let us know if this helps!
Regards,
- JosLaanFeb 28, 2017Aspirant
Hello Laurent,
thank you for your explanation, I checked the settings for ip manangement after reboot and they seems ok:
(M4300-28G) (Config)#show ip management
IPv4 Interface Status.......................... Down
IPv4 Management Interface...................... vlan 1
IP Address..................................... 192.168.4.1
Subnet Mask.................................... 255.255.0.0
Method......................................... Manual
Routing Mode................................... Enable
Default Gateway................................ 0.0.0.0Source Interface............................... vlan 1
Burned In MAC Address.......................... B0:7F:B9:42:C6:A4
Locally Administered MAC address............... 00:00:00:00:00:00
MAC Address Type............................... Burned InWhen I change the ip-address (see below) to another address and back again to the original value then the Web Interface will working again.
(M4300-28G) (Config)#ip management vlan 1 192.168.4.2 255.255.0.0
(M4300-28G) (Config)#ip management vlan 1 192.168.4.1 255.255.0.0
Or disconnecting the ethernet cable from the switch and plug it in again, then also de Web Interface will working again.
Very strang!
When logging (via CLI USB port) on the master switch a few message appear (see below) but the stacking configuration looks working well after full startup:
U-Boot 2012.10-00216-g55eda36 (May 25 2016 - 15:31:45)VerNo=1.0.0.8
+ + Checking for application
Extracting application from .stk file...done.
Loading Operational code...done.
Uncompressing apps.lzma
DMA pool size: 8388608started!
(Unit 1)>
Applying Global configuration, please wait ...
Applying Interface configuration, please wait ...
Trying to attach more units.....
Trying to attach more units.....Trying to attach more units.....
Trying to attach more units.....
Trying to attach more units.....
disc ERR: Timeout occurred
ATP: TX timeout, seq 164. c6:d0 cli 778. to 4 tx cnt 21.
RPC - Timeout to CPU: b0:7f:b9:42:c6:fc.
RPC - Timeout to CPU: b0:7f:b9:42:c6:d0.
User:After first installing the switches in a stack configuration and connected to our existing network we had a BPDU error message (every 10 sec.), after a firmware update (from 12.0.0.11 to 12.0.2.9) this message was fixed.
Have you any suggestions what we can do?
best regards,
Jos Laan
Protonic Holland
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!