NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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...
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
OK, will do it in the evening/night or on the next weekend... :smileyfrustrated: I will report the result once done.
Greez,
dialsc
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
Hi,
I think I can confirm that this is an issue which was not introduced with the latest firmware thus must have exists longer in the firmware. I just went through the following procedure:
1. Uploaded the former firmware (11.0.0.28) to the stack
2. Set this older firmware the active one and restarted the stack
3. Rest the stack to factory default
4. After a restart I loaded back the configuration saved before and restarted the stack
5. Restarted the uplink backbone switch
Result: Again the management IP address/the stack is not accassible anymore. And again network traffic is flowing fine through the stack, e.g. routing over the stack and through the backbone area (to which the stack mgmt IP belongs) works, but the mgmt IP itself is not accassible.
It becomes accasible again by either disrubting the power supply or reloading/restarting the stack through a USB console session.
I guess it's your turn now. Let me know how I can help you but please check this out. Right now it is not working reliably.
Greez,
dialsc
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
