NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port Isolation and replication between two switches
Hello All, I am attempting a thought experiment to save myself from having to run new cable drop, and not sure if what I’m thinking about is possible without creating loopbacks. I know enough abo...
Orbi AX or Orbi Pro AX in this case. And I assume you talk of Access Point Mode for the flat network.
I don't know anything about the newer Orbi AX systems. In general, Orbi makes use of STP (why ever...). On both switches, enable STP (no RSTP, no MSTP, ...) and put the Configuration Revision Level (AKA as Priority or ID) to 32768.
What you designate as a wireless controller is (in access point mode) just yet any other Orbi wireless satellite, additionally holding the management for the Orbi satellites. There is no WAN port in this access point config: All ports are LAN.
Do not add any additional cabling - this will create additional duplicate links, so certainly a network loop.
Do not add any additional VLAN, especially none like the VLAN 2 on the drawing, do not configure the ports where the Orbi satellite is connected as an access port to VLAN 2, keep it untagged on VLAN 1 - as everything will happen on the same flat network. And do not add any VLAN "LAN"s on the Orbi Pro AX...
Just in case, forget the idea that all the traffic is passing the Orbi AX or Orbi Pro AX router - the router and each satellite will act as individual access points in AP mode.
If you have done all this, please tell us exactly what Orbi devices we're facing here. Then we might be able to help (or bring in Netgear for assistance) why the Orbi "router" can't discover the wired satellite. At the end of the day, this is a whatever Orbi issue, not a switch problem...
Last but not least: This is just plain L2 networking - no "isolation" or "replication" (whatever the later is).
Sorry, it didn’t occur to me to add some details about the wireless setup. To answer your question, yes the wireless clients connect to the same LAN and IP subnet as the primary [V]LAN. It's a very flat network, and one IP subnet that everything communicate on.
I'm running the Orbi Wifi system, so from the router I’m looking to connect an Orbi satellite across the network.
From what I understand about the Orbi Wifi system, all ports are members of VLAN 1. Now, I think where I am confused is does it really matter what device is plugged in through the switch? As another example, if I had a camera system setup, and I wanted to ethernet connect a camera clear across the network through the switches (GS110EMX and XS708T). How could I setup switch routing so where it was mimicking one long cable stretched across a building? I was thinking, regarless of the device, even if I had non-VLAN aware devices, was there a way to force the ports to route in such a way where it could act like a eithernet cable spliced together?
This example is what I am trying to accomplish with this wireless mesh setup, if that makes sense.
As for your question/comment on “why one does buy "Mesh" wireless systems - where we never know what games they do with STP” I don’t really understand what you mean by that? But I was asked to setup the network this way, to have LAN ethernet and WIFI 6 available.
Orbi AX or Orbi Pro AX in this case. And I assume you talk of Access Point Mode for the flat network.
I don't know anything about the newer Orbi AX systems. In general, Orbi makes use of STP (why ever...). On both switches, enable STP (no RSTP, no MSTP, ...) and put the Configuration Revision Level (AKA as Priority or ID) to 32768.
What you designate as a wireless controller is (in access point mode) just yet any other Orbi wireless satellite, additionally holding the management for the Orbi satellites. There is no WAN port in this access point config: All ports are LAN.
Do not add any additional cabling - this will create additional duplicate links, so certainly a network loop.
Do not add any additional VLAN, especially none like the VLAN 2 on the drawing, do not configure the ports where the Orbi satellite is connected as an access port to VLAN 2, keep it untagged on VLAN 1 - as everything will happen on the same flat network. And do not add any VLAN "LAN"s on the Orbi Pro AX...
Just in case, forget the idea that all the traffic is passing the Orbi AX or Orbi Pro AX router - the router and each satellite will act as individual access points in AP mode.
If you have done all this, please tell us exactly what Orbi devices we're facing here. Then we might be able to help (or bring in Netgear for assistance) why the Orbi "router" can't discover the wired satellite. At the end of the day, this is a whatever Orbi issue, not a switch problem...
Last but not least: This is just plain L2 networking - no "isolation" or "replication" (whatever the later is).
Hi Schumaku,
Thanks for the reply, we are using the Orbi System AX6000, not the pro. The information you provided seems to have worked, and I can now see the satellite device from the mesh router.
As you advised, I setup the XS708T for STP (it was set for RSTP) and set the Priority to 32768 (default was 0). I could not find any STP settings on the GS110EMX, and nothing in the manual that talked about where those settings could be. However, that didn’t seem to matter that much, later on as I continued in the setup.
I removed all the unnecessary VALNs form the switches and removed the unneeded cabling from the GS110EMX switch.
With that setup it looks like the Ethernet backhaul between the Orbi devices is able to communicate with each other.
Thanks again for your input and advise, I believe the issue has been resolved.
Oh sorry my ignorance, the Smart Managed Plus like the GSxxxE[xx] of course don't offer any STP.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
