Running a 5-story deployment with ~45 APs. A random Omada EAP showed up in the controller for adoption. It has power but likely a bad LAN cable, since it strictly demands Mesh to adopt.
Physical inspection of the building (2 full walkthroughs) yielded nothing. If I temporarily enable Mesh and adopt it, will the controller topology map accurately point to its uplink buddy? Looking for a way to triangulate its physical location.
Adopting it over Mesh will give you an uplink connection topology (it will show which nearby AP it connected to). That will narrow it down to a specific floor or wing, but won’t give you the exact ceiling tile.
If you can to use your iPhone, grab the NetSpot app from the App Store and use their Device Discovery tool. Click adopt over the mesh uplink first. Once it’s actually authorized and on your local subnet,It scans the local network and lists everything with an active IP, MAC, and vendor tag. You can filter the list by your AP’s brand (or its MAC address) to find it.From there, just tap the AP in the list and use the built-in Device Ping tool. Keep a continuous ping running to it while you walk around the building. If you start pulling high latency or packet loss, you’re moving away from the mesh node it’s uplinked to. If the ping drops to 1-2ms, you’re getting close to its general area. It’s much faster than playing detective in the ceilings completely blind.
@Ok-Cantaloupe-90 Oh wow, I didn’t know the mobile version of NetSpot could do real-time tracking like that without a pre-loaded map. Downloading it now, going to hunt it down on the 3rd floor. Thanks!