NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300-24x: spontaneous reboots dispite latest firmware
Hi *, we're running a (until today) single M4300-24x 10G switch, with latest firmware (M4300-24X ProSAFE 20-port 10GBASE-T and 4-port 10G combo, 12.0.2.20, 1.0.0.9). Both with earlierer and current ...
I suggest you to open a chat or online support ticket with NETGEAR Support then describe your concern and include the logs you have posted for it to be analyzed. If ever the switch has been declared faulty, be ready to submit a .doc or .pdf copy of the Proof of Purchase or Sales Invoice of it for warranty verification. Then, if the hardware warranty is still valid, an online replacement will follow.
Regards,
DaneA
NETGEAR Community Team
Hi jmozdzen,
we're running a (until today) single M4300-24x 10G switch, with latest firmware (M4300-24X ProSAFE 20-port 10GBASE-T and 4-port 10G combo, 12.0.2.20, 1.0.0.9). Both with earlierer and current firmware, we have experienced unexpected reboots every few weeks (typically there are about 4 weeks uptime, but I've seen this after two weeks, too).
The remote syslog does not report anything special, i.e. the recent reboot (approx Mar 22 15:34):
--- cut here ---
Mar 22 12:57:26 s-22455-02-05 TRAPMGR[trapTask]: traputil.c(721) 56609 %% Link Up: lag 10
Jan 1 00:01:11 s-22455-02-05 TRAPMGR[dot1s_task]: traputil.c(763) 416 %% Spanning Tree Topology Change Received: MSTID: 0 lag 1
Jan 1 00:01:12 s-22455-02-05 TRAPMGR[dot1s_task]: traputil.c(763) 417 %% Spanning Tree Topology Change Received: MSTID: 0 lag 1
Jan 1 00:01:14 s-22455-02-05 TRAPMGR[dot1s_task]: traputil.c(763) 418 %% Spanning Tree Topology Change Received: MSTID: 0 lag 1
Jan 1 00:01:15 s-22455-02-05 TRAPMGR[dot1s_task]: traputil.c(763) 419 %% Spanning Tree Topology Change Received: MSTID: 0 lag 1
Jan 1 00:01:16 s-22455-02-05 TRAPMGR[dot1s_task]: traputil.c(763) 420 %% Spanning Tree Topology Change Received: MSTID: 0 lag 1
Jan 1 00:01:18 s-22455-02-05 TRAPMGR[dot1s_task]: traputil.c(763) 421 %% Spanning Tree Topology Change Received: MSTID: 0 lag 1
Jan 1 00:01:46 s-22455-02-05 TRAPMGR[SNMPCfgTask]: traputil.c(763) 422 %% Cold Start: Unit: 0
Mar 23 06:38:36 s-22455-02-05 CLI_WEB[emWeb]: emweb_common_custom.c(162) 467 %% HTTP Session 11 started for user admin connected from 192.168.103.12---- cut here ---
So no pointer either before or after the reboot.
There has been no special (network / system) activity around the reboots, nor a pattern we could detect. Nobody was logged on to the switch at the time of reboot.
From the logs you have posted, there might be a loop within the existing network where the M4300-24x switch is connected since there are changes in the Spanning Tree Topology that occured.
Let us isolate the problem. Kindly answer the questions below:
a. How is everything connected? It would be best that you post an image or screenshot of your detailed network diagram.
b. On the web-GUI of the M4300-24xz switch, go to Switching > STP > Basic > STP Configuration and check the Force Protocol Version selected. On the STP Configuration, what is the Force Protocol Version selected?
The release notes from 12.0.2.20 suggested that somebody reported similar behaviour: "M4300-12X12F (XSM4324S) - device rebooted itself without any reason, customer wants to know the root cause."
This is one of the fix that should take effect after upgrading the firmware of the M4300-12X12F(XSM4324S) switch to v12.0.2.20.
Regards,
DaneA
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
