NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi AC3000 with Cisco SG112-24 Switch
Using a Cisco unmanaged sg112-24 switch with Orbi AC-3000 and with one satellite connected via ethernet backhaul to same switch. V2.2.1.210 firmware on both Orbi devices. Orbi router cpu at 17%. A...
I happened to have a Linksys 1GB switch without any Green stuff or Loop detection. It works OK. I will keep an eye on the network to see is anything changes. The Orbi CPU utilization is about the same at 17%. I might be chasing shadows with the Cisco - it likely is thinking it is detecting a loop when none is actually there.
- What other wired devices do you have connected to Orbi? Any mesh speakers (e.g. Sonos)?
- Since you have wired backhaul, please make sure Daisy Chain is disabled in Orbi advanced wireless settings.
1. As far as other things on the LAN - Mostly Windows 10 PCs, a couple of network printers, a couple of Buffalo NAS devices, a couple of smart TVs/DVD. Wifi has 6 Leviton wall light switches. I have 3 Netgear 1G 8 port unmanaged switches that star off of the Cisco - mostly to handle additional devices at didstance. Everything terminates to the Cisco, including the 3 NetGear switches, so only 2 "layers" of switches. Nothing out of the ordinary. The Orbi and Orbi satellite are connected via 2 ports on the Cisco as well but have nothing else connected to their LAN ports.
2. I did try the Daisy Chain settings both on and off. No difference.
I also have switched physical cables and port locations on the Cisco and the Orbi Router. When you plug into a different port on the Cisco, it starts ok with Green link on the right LED and green flickering (traffic) on the left LED (indicates 1GB connection) for about 10 seconds, then it goes to error indication state, (flashing amber on the left) but everything is still operational. The Cisco is detecting something it doesn't like from the Orbi, but I'm not convinced one way or the other if it is causing harm (slowness, packet storms). I could put WireShark on the wired LAN to see if it would pick if anything.