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 dialsc,
Welcome to the community!
Can you kindly help to post the following message?
1.show ip interface brife.
2.show ip route.
It also helpful if you can send us your configuration files.
How do I send diagnostic files from my Managed Switch to NETGEAR community moderators? http://kb.netgear.com/app/answers/detail/a_id/31439
Thanks
Carl
Netgear Employee
Hi Carl,
Thank you very much for your answer. I will create the files needed and send them according to your instructions. If you don't mind I would prefere to send the information you asked for with the email I'm about to send to the community moderators.
Greez,
dialsc
Hi dialsc，
Thanks,have received the information from you.
You use the ip of vlan 20 (10.0.0.3) as management address,right?
When the issue appeared, can you try to ping from pc in vlan 48 to vlan 48's address.(192.168.48.1).
If it success, you can long in switch with the ip 192.168.48.1.Then check if vlan 20 is up or not (show ip interface vlan 20).
Also, since pcs in vlan 48 are in different subnet with management vlan , so it need to make sure pc in vlan 48 have a route to 10.0.0.3.
Regards
Carl.
Hi Carl,
Thanks for your answer. I was unable to come back to this one any earlier, sorry for that.
If this happens, working on a PC in VLAN 48, I cannot access any of this IPs on the switch. Neither VLAN20 nor VLAN48. Super interessting: I do still have access to all the other networks - including internet from VLAN48. This network traffic is being routed through the switch in question here.So it looks like network traffic is flowing through the switch without issues. But accessing - Mgmt UI, telnet, SSH - the switch directly is not possible. Even pings do timeout sent to one of the switch's IPs.
And yes, the routing settings on the workstation is set correctly.
Maybe the following information helps finding out the root cause. If you configure an VLAN specific IP on the switch and while the switch is running, there is no interface active on the switch participating with that VLAN, the switch considers that VLAN specific IP do be down/disabled. Example: The backbone uplink runs on VLAN 20. On the switch there is only one interface being configured to participate in that VLAN. If this interface is down, e.g. because the other side switch is being rebooted or down or unplugged, the switch reports the whole VLAN IP to be down/disabled and it is impossible to even ping the IP assigned to this VLAN on the switch from any other source through the network. This, by its own is somehow strange, as of my point of view and should/could be changed. For this case here anyways this might give an idea where the problem comes from? I don't know but I have a feeling... ;)
Greez
dialsc
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
