NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS108Tv2 port flapping
I have sky Q running on Ethernet. Using 2 netgear switches on 5.4.2.22 there is no problem. However, I installed 5.4.2.25. when both switches reboot and activate the new firmware the highly active sky...
0 1 days 21:36:23 Link Up: g7 1 1 days 16:00:48 Link Up: g8 2 1 days 16:00:45 Link Down: g8 3 1 days 16:00:36 Link Up: g8 4 1 days 16:00:33 Link Down: g8 5 1 days 16:00:27 Link Up: g8 6 1 days 13:53:42 Link Down: g8 7 0 days 21:41:28 Link Down: g7 This was from 251 which is connected directly to the Main Sky Q box port 8 (port 7 is the TV). I suspect that their is a minor issue with the Q box. Overall everything has been stable. 252 has not shown any port flapping or link changes in 24h.
Upon reset to defaults on Friday, I noted a log that stated something like 'settings not compatible with current firmware'. Sadly I didn't capture that message.
Conclusions
I started out upgrading initial fw to .18 with a reset to defaults back then, then .19 about a year ago then .22 a few months ago. Since the reset to defaults on fw .25 and the reprogramming of both switches, both have been perfectly stable. The .25 firmware appears to require a reset to default, atleast when coming from so many older baselines. I now consider the case closed.
| <14> Oct 29 10:55:33 192.168.50.252-1 SNTP[2184296428]: sntp_client.c(1806) 1 %% SNTP: system clock synchronized on Sat Oct 29 10:55:32 2016 UTC+00:00 |
| <14> Oct 29 10:59:19 192.168.50.252-1 NIM[2179216468]: usmDbIntfTypeGet(1573) 2 %% internal interface number 0 out of range |
| <14> Oct 29 10:59:19 192.168.50.252-1 NIM[2179216468]: usmDbIntfPhyCapabilityGet(1656) 3 %% internal interface number 0 out of range |
| <14> Oct 29 10:59:35 192.168.50.252-1 NIM[2179216468]: usmDbIntfTypeGet(1573) 4 %% internal interface number 0 out of range |
| <14> Oct 29 10:59:35 192.168.50.252-1 NIM[2179216468]: usmDbIntfPhyCapabilityGet(1656) 5 %% internal interface number 0 out of range |
I cleared the logs again. On the whole there was just a brief period of the port reporting as flapping however, I did NOT notice the extreme disconnections I had before. The switch has behaved fine. The minor port flapping is odd but I'd not jump to conclusions just yet.
My LAN is as follows;
Sky BB -> Mikrotik CCR1009 -> port 5 sw 251 port 1 -> port 1 sw 252 port 3 -> Edimax Pro Wifi 1750 -> old 100Mb netgear sw -> Q mini.
sw 251 port 8 -> Sky Q main box.
I'm operating VLAN 1 and VLAN4 between both smart switches. Both VLANs terminate at the Edimax Wifi which strips the VLAN1 tag and passes it to the Netgear 100mb sw. At that point to the Q mini it is Untagged. The above is not my full network plan but is sufficient for our illustration. Some port flapping is possibly due to the WiFi access point resetting itself which is possible if a config change occurs. I'll dig into it's logs to try to correllate. I must add that I did quite a bit of reconfiguring of my network yeterday and therefore would like to observe the logs over a few days now to see if it stabilises.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
