NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dialsc
May 24, 2017Guide
M5300 unaccessible after reload and/or uplink reboot
Hi, Starting with the beta firmware 11.0.0.30 there is a strange behaviour to be seen on a M5300 based stack. Here are the facts. The stack: 1 M5300-28G3 1 M5300-28GF3 Role: OSP...
- Aug 22, 2017
Hi Carl_z,
Unfortunately I have to inform you that I'm about to give up. I'm not able to reproduce the issue. Once I did a config change I thought might be the problem I was not able to get it to run into the problem again. Here's a short description.
The switch in question was originally connected to the backbone switch with one 10GB line. That line was configured to carry a couple of VLANs where VLAN 48 was one of them. This was - let's say - a leftover from when the network topology was changed/a new area introduced.
Then the setup was changed so the uplink was not just one line but a LAG with two 10GB links. This LAG was configured to also carry VLAN 48 beside a couple of others. I did miss to take away the VLAN tagging/membership settings from the first single line when the LAG was fully set up. Once the new area was introduced, I forgott to remove VLAN 48 from the LAG, as well.
So, I did remove any other VLAN setting from both, the original single line as well as the LAG thus only VLAN20 (the backbone VLAN) was active on the LAG connecting to the backbone switch. After I did that change, the problem seemed to be resolved and I was not able to force it again.
I even applied the "old" startup-config from which I know that it was running when the problem occured. No chance, I do not get the switch to run into the issue again.
So, therefore I have to give up now which - on the one hand - is something realy good... ;) On the other hand I feel sorry not being able to show you how to force this issue.
Nevertheless, I'm done now... ;)
Best,
dialsc
dialsc
Jul 05, 2017Guide
Thanks for your answer. Right now I'm running firmware version 11.0.0.31 on all the switches which is the latest, official one. Do you want me to go through this procedure anyways?
Greez,
dialsc
DaneA
Jul 05, 2017NETGEAR Employee Retired
Yes, kindly proceed with it for as long as the switches are not being used for production at the moment so that we could isolate the problem and verify if the problem is only present when using firmwares v11.0.0.30 & v11.0.0.31. Be reminded to perform a factory reset on the switches after reverting back to the previous firmware (to when it was working fine before) then reconfigure it from scratch in order to start clean using the firmware uploaded.
Keep us posted about the result.
Regards,
DaneA
NETGEAR Community Team
- dialscJul 05, 2017Guide
OK. Would it be sufficient to load a configuration backup once the switch was factory reset? It's so much to configure and error-prone doing it all manually. The switch is productive and I'm facing the risk to bring the whole area down if this does not work.
Greez,
dialsc
- DaneAJul 05, 2017NETGEAR Employee Retired
- dialscJul 05, 2017Guide
OK, will do it in the evening/night or on the next weekend... :smileyfrustrated: I will report the result once done.
Greez,
dialsc
- dialscJul 10, 2017Guide
This is to let you know the latest results. For a test: I was NOT changing the firmware but did reset the switch and loaded the configuration which I saved before back into the switch. I then did the test of restarting the uplink backbone switch and the result was, that the switch was becoming accesible again after the uplink switch was up again. So this looked like the problem was solved by resetting and reloading the switch's configuration.
Unfortunatelly this is not true. This morning - after the switch was running for about two days - I performed the same test again and now the problem reappeared. By this I can confirm that resetting the switch does not solve the problem.
I will now change the the firmware back to the former one -> 11.0.0.28. Once that was done I will wait two days and test it again. After that I will let you know the results.
Greez,
dialsc
- DaneAJul 11, 2017NETGEAR Employee Retired
I inquired your concern to the higher tier of NETGEAR Support and they recommend that you open an online case with NETGEAR Support in order for your concern to be forwarded to the engineering team for further investigation. Be reminded to upload the configuration file of the switches to the online case.
Regards,
DaneA
NETGEAR Community Team
- dialscJul 11, 2017Guide
Thank you very much for taking care about this one!
Unfortunatelly I'm not entitled to open a support case there. As a none-original purchaser of these switches they will not accept any request from my side. Any chance you or they can open a ticket. I will support them as much as I can but someone else has to open a ticket, sorry... ;(
Related Content
NETGEAR Academy

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