I also thought this to be true, but found out the the sync process was not working

What Firmware version is currently loaded?

Is Firmware same version on all RBS as on the RBR? 

If the RBS wirelessly connected and synced fully and then connecting ethernet to your switch and doesn't work and only shows factory SSID name, then we can presume either LAN cabling in between the RBR and RBS and your switch or the switch itself is cause of what your experiencing. Your model switch is a managed switch. Orbi and managed switches have had a long history of being problematic. Check to see if you can disable any and all IGMP protocols and any Green Ethernet features on this switch. If no, try one of the following non managed switches:

NG GS-105/108v4 and GS308v3, D-Link DGS-105/108 and HP ProCurve 1400/1800 series switches work for Orbi systems.

Also be sure your using good quality LAN cable. CAT6 is recommended between the RBR and RBS.

Furrye38,

Thanks for your interest.

Re: Firmware - The router and satellite out of the box had firmware version 3.6.x - where x is some collection of dots and numbers I did not write down. I ran the update firmware menu option for both router and satellite, and it installed a firmware version 4.6.x. It said that was the latest firmware available. I ran the menu option 2 more times, and it insisted that was the latest version available. Checked NG website and found firmware versions 7.6.x for router and satellite (separate files). Downloaded those and used manual installation menu option to install both. So, router and satellite are running firmware versions 7.6.x.

Re: Syncing - The blue light appears to be less about syncing, and more about connecting. After updating both router and satellite to firmware version 7.6.x, I changed the SSID on the router to ABC123. I also turned-off the IoT SSID. The router and satellite came with SSID set at ORBI23. I then connected the WAN port on the router to a port on the NG GS724T, and a LAN port on the satellite to another port on the GS724T. I am using the Orbi as an access port, not the network router as I have and need a dual WAN (with auto-failover) router. Following boot-up of both, I initiated a sync, and noted a blue light on the satellite. On checking the wifi sites available at my location, I found both the ABC123 SSID and the ORBI23 SSIDs were being broadcast. I thought, perhaps, that a neighbor might have an ORBI, but that was unlikely since I live in a very sparsely occupied 2nd home community. So, I unplugged the satellite, and ORBI23 went away. I then disconnected the satellite from  the GS724T port and moved it to sit physically alongside the router. I then initiated a sync wirelessly, and noted a blue light on the satellite. At that point, there was no ORBI23 being broadcast. I then powered-down the satellite, moved it back to its intended location, reconnected it to the GS724T port, and powered it back up. While it was booting-up (white light flashing) the ORBI23 IoT SSID was briefly broadcast (even though it had been turned-off on the router before the wireless sync), and then it disappeared. On completion of the boot-up, the satellite showed a blue light, and the only SSID being broadcast was the ABC123. So far, the units have worked successfully since that last boot-up.

Re: The GS724T switch - As configured, it is operating essentially as an unmanaged switch. There are no green or power-saving features activated. there are no port-forwarding, port-blocking, special protocols, VPN, etc being used. While I really do not need a managed switch, I bought it new for less than an unmanaged switch of the same size. It is a rugged, industrial quality product that has functioned very well for over 8 years now. Quite frankly, if Orbi cannot function with a wired backhaul through that switch, then the switch stays, and Orbi gets returned.

Re: LAN cables - The house is amply wired with certified CAT-6 cable (as a retired PE/EE, I personally installed it during new construction of the house) and I use only Fluke-tested and certified CAT-6 patch cables.

Aside from some apparent flaws in the firmware (incorrect info on latest firmware version, and brief broadcast of the turned-off ORBI23 IoT SSID), the problem I encountered appears to have been an unsuccessful sync via a wired backhaul through a switch. The blue light that concluded that sync would lead you to believe it was a successful sync, but it appears that all it meant was that the two units had communicated. The units clearly were not in sync. Syncing the units wirelessly solved the problem.