This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I am having a problem with my network randomly going offline.
I am trying to identify the culprit. Every time this happens, it's purely only affecting connected devices. WiFi devices are not affected. And if I only reset my switch, this seems to correct it (usually). I lose both access to internet as well as my local devices (see below, all are connected to this switch).
I have a Netgear CM 600 Cable modem, this is connected to a Netgear R8500 Router, and then this is connected to a Netgear GS748T v5 Managed Switch.
All LAN devices are connected to this 48 port switch. There are 2 NAS servers, 2 Windows Servers, 5 PCs, and various home audio, video, automation, and security devices. There are two GS116NA switches connected with further AV stuff and a couple PCs.
I turned off Link Aggregation on all devices. That was about the only thing I had set up on this switch beyond the system defaults. Though as I'm writing this, I am thinking I should probably do a factory reset to be sure and see this fixes things.
Firmware is 6.3.1.11
I have been trying to watch logs around the time of these events. I think I need to learn more about how to work with logs, however, as it seems to delete the log whenever I reset it. However, this one seems to have some 'issues'. I was wondering if anyone has any ideas on this?
<14> Jan 1 00:02:42 192.168.1.21-1 General[56170932]: main_login.c(219) 278 %% HTTP Session 5 initiated for connection from 192.168.1.13
<14> Jan 1 00:02:42 192.168.1.21-1 CLI_WEB[56170932]: emweb_common_custom.c(162) 277 %% HTTP Session 5 started for user admin connected from 192.168.1.13
<13> Jan 1 00:02:08 192.168.0.239-1 TRAPMGR[56136692]: traputil.c(739) 276 %% Cold Start: Unit: 0
<13> Jan 1 00:01:49 192.168.0.239-1 TRAPMGR[56125068]: traputil.c(739) 275 %% Spanning Tree Topology Change Initiated: 0, Interface: g48
<13> Jan 1 00:01:49 192.168.0.239-1 TRAPMGR[56125068]: traputil.c(739) 274 %% Spanning Tree Topology Change: 0, Unit: 1
<13> Jan 1 00:01:28 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 273 %% Link Up: g40
<13> Jan 1 00:01:16 192.168.0.239-1 TRAPMGR[55921268]: traputil.c(739) 272 %% LLDP-MED Topology Change Detected: ChassisIDSubtype: 4, ChassisID: 74:D4:35:85:5B:A2, DeviceClass: 1, Interface: g43
<13> Jan 1 00:01:16 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 271 %% Entity Database: Configuration Changed
<13> Jan 1 00:01:15 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 270 %% Link Up: g43
<13> Jan 1 00:01:15 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 269 %% Link Up: g44
<13> Jan 1 00:01:14 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 268 %% Link Up: g36
<13> Jan 1 00:01:14 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 267 %% Link Up: g32
<13> Jan 1 00:01:14 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 266 %% Link Up: g3
<13> Jan 1 00:01:14 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 265 %% Link Up: g48
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 264 %% Link Up: g38
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 263 %% Link Up: g37
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 262 %% Link Up: g35
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 261 %% Link Up: g34
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 260 %% Link Up: g30
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 259 %% Link Up: g19
<13> Jan 1 00:01:13 192.168.0.239-1 TRAPMGR[55995772]: traputil.c(696) 258 %% Link Up: g13
<11> Jan 1 00:01:13 192.168.0.239-1 General[55922508]: nsdp_control.c(1667) 257 %% NSDP could not create the socket - No such file or directory
<13> Jan 1 00:01:13 192.168.0.239-1 OSAPI[55922508]: osapi_net.c(446) 256 %% Failed to add route to 0.0.0.0 0.0.0.0 via 192.168.0.254 to the IP stack routing table.
<14> Jan 1 00:01:10 192.168.0.239-1 CLI_WEB[56170932]: sysapi.c(2693) 246 %% Configuration file <startup-config> read from flash!
<14> Jan 1 00:01:09 192.168.0.239-1 CLI_WEB[56170932]: cli_txtcfg.c(482) 86 %% Configuration applied from file <startup-config>
<14> Jan 1 00:01:09 192.168.0.239-1 CLI_WEB[56170932]: sysapi.c(2693) 85 %% Configuration file <startup-config> read from flash!
<14> Jan 1 00:01:08 0.0.0.0-1 CLI_WEB[54859612]: cli_web_api.c(648) 84 %% Failed to open the CLI banner file cli.bnr.
<14> Jan 1 00:01:08 0.0.0.0-1 DOT1Q[54859612]: dot1q_cfg.c(1218) 82 %% Error accessing DOT1Q config data for VLAN 1 in dot1qVlanIsConfigurable
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 81 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 80 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 79 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 78 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 77 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 76 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 75 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 74 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 73 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 72 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 71 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 70 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 69 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 68 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 67 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 66 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 65 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 64 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 63 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 62 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 61 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 60 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 59 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 58 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 57 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 56 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 55 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 54 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 53 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 52 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 51 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 50 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 49 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 48 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 47 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 46 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 45 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 44 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 43 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 42 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 41 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 40 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 39 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 38 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 37 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 36 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 35 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 34 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 33 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 32 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 31 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 30 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 29 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 28 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 27 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 26 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 25 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 24 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 23 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 22 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 21 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 20 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 19 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 18 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 17 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 16 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 15 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 14 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 13 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 12 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 11 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 10 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 9 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 8 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 7 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 6 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 5 %% NIM: incorrect phase 152 for operation
<14> Jan 1 00:01:08 0.0.0.0-1 NIM[55880788]: nim_intf_api.c(95) 4 %% NIM: incorrect phase 152 for operation
<10> Jan 1 00:01:07 0.0.0.0-1 General[50375364]: bootos.c(179) 3 %% Event(0xaaaaaaaa)
<13> Jan 1 00:01:07 0.0.0.0-1 BSP[50375364]: bootos.c(163) 2 %% Starting code... BSP initialization complete, starting FastPath application.
<13> Jan 1 00:00:48 0.0.0.0-1 General[50375364]: sdm_template_mgr.c(357) 1 %% Booting with default SDM template IPv4-routing Default.
Something I've noticed, my switch is not accurately setting the date and time. I wonder if this causes a problem? Trying to figure out how to set this...
I noticed on a different log that my router was being blocked due to DOS attacks. And I had turned on Auto-DOS-Control. I turned that off. Things seem more stable. So, maybe that was part of the problem. I will have to rely on the router and server firewalls.
I still have some problems with some devices, so, trying to take things one step at a time, I did a factory default on the switch, will see if that fixes anything.
I'm still researching on how to set the time automatically. I've had problems before with a different network device that didn't have a correct time, so just want to rule that out.
Next step will be to plug those problem devices directly to the router to see if they still go offline.
I noticed on a different log that my router was being blocked due to DOS attacks. And I had turned on Auto-DOS-Control. I turned that off. Things seem more stable. So, maybe that was part of the problem. I will have to rely on the router and server firewalls.
I still have some problems with some devices, so, trying to take things one step at a time, I did a factory default on the switch, will see if that fixes anything.
I'm still researching on how to set the time automatically. I've had problems before with a different network device that didn't have a correct time, so just want to rule that out.
Next step will be to plug those problem devices directly to the router to see if they still go offline.
