GS308E becomes unreachable

[Sciao]

Hello,

i have a strange problem. I have a couple of GS308E manaed switch in my home, i configured both of them with VLAN (802.1Q) since i have a separate vlan for iot/smart devices and everything works.

But one of the switches (the first connected to the router) after some time becomes unreachable (no admin page, no ping, nothing), until i restart it. I tried the discovery app of netgear and it sees the switch, but with a wrong ip (that is neither in my subnet so not reachable anyway)

I know the router can't get an ip on a vlan, so the main port gets also untagged packets and, as i said, as soon as the switch is restarted, it works and i can access the config page / ping the router.

On the other side, the second switch (that is connected to the first) is always correctly accessible.

Any idea?

Thanks

[schumaku]

---

@Sciao wrote:

I tried the discovery app of netgear and it sees the switch, but with a wrong ip (that is neither in my subnet so not reachable anyway)

---

What IP address? Does it fall-back to the default IP (because of the switch is up before the router DHCP server)? Does it pick up an config from another network - what is possible because of the management isn't hard locked into a defined VLAN?

[SBMeijer]

Hi @schumaku and @Sciao 

I am running into the same issue. I have 2 of these switches with multiple VLANS.

Here is some ping-output (both of them are acting the same):

Reply from 172.16.99.55: bytes=32 time=11ms TTL=126
Reply from 172.16.99.55: bytes=32 time=7ms TTL=126
Request timed out.
Reply from 172.16.99.55: bytes=32 time=5ms TTL=126
Reply from 172.16.99.55: bytes=32 time=5ms TTL=126
Reply from 172.16.99.55: bytes=32 time=13ms TTL=126
Reply from 172.16.99.55: bytes=32 time=7ms TTL=126
Reply from 172.16.99.55: bytes=32 time=7ms TTL=126
Reply from 172.16.99.55: bytes=32 time=14ms TTL=126
Request timed out.
Reply from 172.16.99.55: bytes=32 time=4ms TTL=126
Reply from 172.16.99.55: bytes=32 time=7ms TTL=126
Reply from 172.16.99.55: bytes=32 time=6ms TTL=126
Request timed out.
Request timed out.
Reply from 172.16.99.55: bytes=32 time=9ms TTL=126
Reply from 172.16.99.55: bytes=32 time=7ms TTL=126
Reply from 172.16.99.55: bytes=32 time=6ms TTL=126
Reply from 172.16.99.55: bytes=32 time=8ms TTL=126

The IP-address is static on boh of the switches.

I tried multiple versions and none are working correctly. Also, the ping is quite stable until i try to login into the GUI.

I have one multicast VLAN and a lot of traffic over them. Would it be possible they are being overloaded?

[schumaku]

---

@SBMeijer wrote:

I am running into the same issue.

---

The OP talked about "after some time becomes unreachable (no admin page, no ping, nothing), until i restart it. I tried the discovery app of netgear and it sees the switch, but with a wrong ip", That much about "the same".

---

@SBMeijer wrote:

I tried multiple versions and none are working correctly. Also, the ping is quite stable until i try to login into the GUI.

I have one multicast VLAN and a lot of traffic over them. Would it be possible they are being overloaded?

---

Along with the IP stack, the Web UI, the tiny embedded controller on this switch design does also handle certain functionally, like handling IGMP Multicast. All this requires that the controller is "sniffing" all the traffic flowing the switch. I could imagine that a very high number of frames could make it hit its limits. Certainly, the least prio job is handling pings - the same applies to enterprise and carrier grade switching-ruters by the way, too. Looks like a problem to look into by Netgear switch engineering.

[Bergro]

I have also the ping problem.

I discovered it is caused by my camera software on the PC

If I close the software, then al works fine.