@celsius233 

do you have any of the relatively basic "easy smart" switch anywhere?  Even with careful per-port vlan assignment on them, they often sow up on my omada controller as connected to different omada switch ports and entirely incorrect VLANs than what they are actually connected to and set as.  After much diagnosing, i simply started to ignore it.  For the most part, i think that omada switch device recognition and reporting to controller is largely guesswork under the hood, and it often goes whacko.

I have devices on my core switch, on a defined port, that are reported by omada as connected to my Uplink LAG ports....which. of course they arent, the uplink lag ports are exactly that - uplink lag - they are just going to another switch.

Again, i ignore it.

When its got really confised when ive been experimenting, i often find a hard reset and reprovision fixes it until my next round of crazy fiddling.

  @GRL 

Thanks for the info.  It would really suck for me to set all this up again and that would be really unfortunate.  I have to switches in my network:   SG2008P v3.20 and SG2218P v1.20.  I would expect those to be fairly robust.  I remember seeing an "Easy..." tickbox somewhere on a Controller page, but I don't recall where right now.

Actually, the page wasn't false reporting.  I could get to the 192.168.50.100 landing page which was workstations BMC management port.  So it was assigning and routing to that port, i.e. it wasn't a false reporting.  I couldn't get to the 192.168.50.3 IP which was the internal NIC of the workstation.  Having removed the BMC port connection from the network, I still can't get tothe 192.168.50.3 from any subnet except the admin subnet that the gateway is on and the subnet the workstation is on.  It's like the routing is all messed up.  But I can get to other devices on the 192.168.50 subnet from all other subnets; just not the one device at 192.168.50.3.  I also tried assigning a different IP to the workstation:  192.168.50.101.  It shows up and is assigned, but again I can't get to it; even with a different assigned.  It's just stuck for that particular machine.  To make it even more strange, I plugged the second NIC in that box (different MAC) and I STILL can't get to it.  I can't see how that's possible.  It's like there is a global ACL set which is blocking the traffic, but there isn't because other devices in that subnet are reachable and I change the IP multiple times and still stuck.

  @celsius233 

Funnily enough - I too have had to completely rebuild my omada network from scratch including factory reset of all devices including controller.  While doing so, i discovered what, at least on my network, was causing the wrong devices to be reported as connected to the wrong ports.

Known Devices.

In my case, while i was changing interlink ports etc and using temporary links while i set port profiles on my switches, i discovered that the hardware controller, once it "learns" a device on a port, regardless if that devices changes port in the future, its somewhat "sticky" and doesn't always recognize the port change, and will continue to report the old port in the connected devices list.

All i had to do was go to known devices and "forget" all of them (tricky as the list repopulates as you are deleting so have to keep at it) and voila - no more port/device confusion.