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,
Thank you so much for jumping into this one, highly appreciated!
I did an inspection regarding the information you've provided and found out the following: The source of those packages is a Samsung TV. That TV is creating two packages like the one you mentioned during its startup. I just tested it by doing "normal" TV usage... ;)
It looks like the scenario as you tested it - creating this kind of packages with 100Mbps - is not what happens in real live. So far, after doing a couple of restarts and therefore having a couple of these packages sent through the network, the stack IP is still accassible through VLAN 48 once the uplink switch has been restarted. It looks like there is something else causing the inaccessibility after a while of continued operation of the stack.
I will further test it by:
1. restart the uplink switch after 1 hour of stack operation
2. restart the uplink switch tomorrow
3. restart the uplink switch after 24 hours of stack operation
3. continue to do so
Once the inaccessability reoccurs I'll create a TechSupport file immediately and provide the information to you.
Hth!
Greez,
dialsc
PS: For what it's worth I've just seen the following behaviour. I was - due to tests asked by your colleague - still running firmware 11.0.0.28. I change the config to make the version 11.0.0.31 the active one. Then I triggered a restart through the web UI. After the stack has rebooted, the same problem occurs. The mgmt IP is not accessible from my workstation -> VLAN48. After triggering a second reload through the command interface the mgmt IP has become available.
Hi ,dialsc
Do you have a serial connection to the M5300 ?
When the issue appeaer can you try to ping vlan 20 and vlan 48 (ping 10.0.0.3, ping 192.168.48.1)via serial .
By doing this , we want to confirm vlan 48 is normal or not.
If you can ping vlan 48 (excute ping 192.168.48.1 in M5300 ) successfully.
Suggest do the follwoing test
1. Assign a new port untag in vlan 48.
2. Set the port pvid to 48.
3. Connect a PC to the port and set PC's IP as 192.168.48.77(This ip can be any one that in same subnet with vlan 48)
4. Connect from the pc to 192.168.48.1.
Thanks&Best Regards
Carl.
Hi Carl_z,
Regarding your message before your last one. I did what you asked me to do. I connected to the stack via USB console and performed the ping tests, here's the result:
(M5300-28G3) >ping 10.0.0.3
Pinging 10.0.0.3 with 0 bytes of data
Reply From 10.0.0.3: icmp_seq = 0. time <1 msec.
Reply From 10.0.0.3: icmp_seq = 1. time <1 msec.
Reply From 10.0.0.3: icmp_seq = 2. time <1 msec.
----10.0.0.3 PING statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (msec) min/avg/max = <1/<1/<1
(M5300-28G3) >ping 192.168.48.1
Pinging 192.168.48.1 with 0 bytes of data
Reply From 192.168.48.1: icmp_seq = 0. time <1 msec.
Reply From 192.168.48.1: icmp_seq = 1. time <1 msec.
Reply From 192.168.48.1: icmp_seq = 2. time <1 msec.
----192.168.48.1 PING statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (msec) min/avg/max = <1/<1/<1Then I connected the workstation to a port configured as untagged VLAN 48 at the stack directly and the ping to the mgmt IP still fails. Furthermore pinging other IPs configured on the stack fail, too. For example pinging 192.168.48.1 (VLAN 48) also fails. It seems that none of the IP configured at the stack can be accessed from my workstation in VLAN 48.
Very interessting: EVERYTHING ELSE seems to work fine. Traffic from and to any of the VLANs connected to and routed over the stack seems to working fine. All this traffic is being routed over IPs configured at the stack.
---------------
Regarding your latest message. Sure, no problem. Can you please tell me where to send the configs to?
Best,
dialsc
Hi dialsc,
You can follow this to send the configs
How do I send my Web Managed Plus / Click switch configuration file to NETGEAR community moderators? http://kb.netgear.com/app/answers/detail/a_id/31437
It very strange that can't ping 192.168.48.1 from your workstation.
Two points to double check
1.The workstation's ip is 192.168.48.x /255.255.240.0 ?
2.The port pvid=48?
Thanks for your patience
Best Regards
Carl
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
