NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS510TLP Port flapping
So had a similar issue with a GS108T where the ports would flap down then up repeatedly causing internet to break. The GS510TLP has been updated to latest 6.6.2.9 firmware and RESET to DEFAULTS (whi...
Since the bad cable was found I have not seen anymore port flapping. Strange that it affected several ports
| <13> Jun 24 11:51:10 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 826 %% Link Down: g5 |
| <15> Jun 24 11:51:10 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 825 %% HAPI LS callback, u 0. p 6 |
| <15> Jun 24 11:43:36 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 824 %% SNTP: system clock synchronized on Sun Jun 24 11:43:36 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (185.186.77.153). |
| <15> Jun 24 11:42:31 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 823 %% SNTP: system clock synchronized on Sun Jun 24 11:42:31 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (185.186.77.153). |
| <15> Jun 24 11:41:25 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 822 %% SNTP: system clock synchronized on Sun Jun 24 11:41:25 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (129.250.35.251). |
| <15> Jun 24 11:40:19 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 821 %% SNTP: system clock synchronized on Sun Jun 24 11:40:19 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (95.215.175.2). |
| <13> Jun 24 11:21:44 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 820 %% Link Up: g5 |
| <15> Jun 24 11:21:44 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 819 %% HAPI LS callback, u 0. p 6 |
| <13> Jun 24 11:21:40 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 818 %% Link Down: g5 |
| <15> Jun 24 11:21:40 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 817 %% HAPI LS callback, u 0. p 6 |
| <13> Jun 24 11:21:00 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 816 %% Link Up: g5 |
| <15> Jun 24 11:21:00 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 815 %% HAPI LS callback, u 0. p 6 |
| <13> Jun 24 11:20:56 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 814 %% Link Down: g5 |
| <15> Jun 24 11:20:56 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 813 %% HAPI LS callback, u 0. p 6 |
| <13> Jun 24 11:20:35 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 812 %% Link Up: g5 |
| <15> Jun 24 11:20:35 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 811 %% HAPI LS callback, u 0. p 6 |
| <13> Jun 24 11:19:40 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 810 %% Link Up: g4 |
| <15> Jun 24 11:19:40 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 809 %% HAPI LS callback, u 0. p 5 |
| <13> Jun 24 11:19:37 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 808 %% Link Down: g5 |
| <15> Jun 24 11:19:37 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 807 %% HAPI LS callback, u 0. p 6 |
| <13> Jun 24 11:19:35 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 806 %% Link Up: g5 |
| <15> Jun 24 11:19:35 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 805 %% HAPI LS callback, u 0. p 6 |
Please tell me what those broadcom drivers errors mean - bad firmware?
Why is SNTP going baserk?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
