@BubbaBubba 1. Is there any VLAN settings you've done on the core switch? Or access Control rules? On the switch web interafce you can go to System Tools, and try Ping the controller IP.

Reset the switch if possible.

The controller will cover all existing settings on the core switch anyway.

2. I feel like it is related to the Ethernet LAN settings on your controller. Again you may check is tehre any VLANs/networks you created on the Wired Network-LAN?

The last time I saw similar issue, I gigure out that the LAN settings changed the router LAN IP and the switch did not obtain correct IP address. Sometimes the controller shows the switch IP but actually the controller is not able to communicate with the switch.

I solved the issue via reset my whole system(so no configurations on controller anymore) but not sure if you can do that. You may backup the config file first before changing any thing on the controller.

  @Somnus 

Thanks a ton for your suggestions.

#1

All of the TP Link devices correctly receive IP addresses from the DHCP server on the Linux Host Router. I can ping all of the TP Link hardware from the Omada Controller host and I can ping the Omada Controller from the "core" switch, as you suggested I try. There are no ACLs, but I have configured some VLANs (IOT, Guest), but the Omada traffic isn't VLAN tagged. It's VLAN1 on the switch which is untagged on the network. This seems to be the default switch behavior and correct me if I'm wrong, but I think this is all good. Again, DHCP and ping both work fine, so I think there's no problem with connectivity between the "core" switch and the router.

The problem that I'm experiencing is that the Omada Controller doesn't reply to the L2 discovery broadcast. All of the other TP Link devices send the discovery broadcast and get responses, but the "core" switch just doesn't get a response. I'm capturing packets on the Omada Controller host and the "core" switch is repeatedly sending the discovery broadcasts but never gets a response.

It might be worth noting that all of the devices that the Omada Controller discovers correctly are going through the "core" switch, so nothing wrong with the basic switching functionality of the "core" switch on either the uplink or downlink sides.

#2

As stated above, no problems with connectivity, pings between devices all work fine.

I've completely reset my Omada Controller (stopped, wiped data dirs, start) and I've factory reset the both of the misbehaving switches a few times, but still no luck.

  @BubbaBubba 

I re-hosted my controller and updated from 4.4.8 to 5.3.1. All of my devices are adopted and configured now. I can't explain why it wasn't working on the previous host/sw-version and the new host isn't where I'd like the controller to be located, but at least I have a working configuration now and I can work to try to find the differences between the non-working and working setups.

Thanks again for your attention.