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
Hi Carl_z,
Yes, it is strange. But hey, I'm used to face strange problems... ;) Thanks for the link!
I can assure that the workstation's IP settings are fine. In fact even DHCP works after the stack becomes inaccessible but of course I double checked it.
Right now I'm in the process of cleaning out older VLAN settings through out the different interfaces at the stack -> Trunk allowed VLANs settings, asf. After that I will wait a couple of hours up to a day and then check if that changes something. I will let you know as soon as possible. If this doesn't help, I will prepare and send the configs to you. I hope that's fine for you.
Best,
dialsc
Hi Carl_z,
I just wanted to let you know that I found how to avoid the problem. Right now I'm still trying to reproduce the problem but I wasn't lucky so far. I will keep you informed about what ever I find.
Best,
Dirk
Hi,Dirk
OK, thanks for your effort.
Best Regards
Carl
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
Hi dialsc,
Congratulations! It nice to hear you out of touble .
If you there problems later，dont hesitate to let us known~
Thanks&Bestregards
Carl
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
