Perhaps it is expecting the replies to come back via the untagged VLAN instead and they wouldn't because Ubiquiti discovery is not a layer 2 protocol like CDP and LLDP.
#Ubiquiti device discovery tool. software
the UniFi Controller software conducts device discovery, provisioning.
#Ubiquiti device discovery tool. android
Android is the number 1 (by numbers) operating system. In the Unifi dashboard go to Devices -> Select the Switch -> Config. Ubiquiti are known for their Unifi range WiFi access points and easy management. Ive tried it but like the format of the Ubiquiti DDT much better. For Ubiquiti Discovery Protocol, it should be sending the discovery broadcast on VLAN101 in our case and getting the replies back tagged from that VLAN. Configure wireless devices that you want to connect to the wireless. CDP frames do not normally have a VLAN tag, so perhaps this is why the Netonix is not finding those. You can filter those devices by type (UniFi, airMAX, EdgeMAX) or by using search. the CDP frame sent by the device passes through the Netonix and to our router. Ubiquiti Device Discovery Tool is an app allowing you to discover and see Ubiquiti devices on your local network. The Netonix actually forwards these CDP frames to our router and so the neighbors list populates there - i.e. One thing I notice is that our APs send CDP with a tag of VLAN 101, it seems it is a strange behaviour of Ubiquiti. The Ubiquiti Device Discovery Tool will search for the UniFi Cloud Key.
![ubiquiti device discovery tool. ubiquiti device discovery tool.](https://i.ytimg.com/vi/0oDhws4CD5k/maxresdefault.jpg)
For those that don’t know, Ubiquiti put business-class networking firmly in the consumer price bracket. If the tool is not installed, you will be prompted to add it. Its with a (slightly) heavy heart I write this as I’m a fan boy of Ubiquiti‘s networking gear. If the Ubiquiti Device Discovery Tool is already installed, proceed to step 7. Our Ubiquiti APs have both CDP and Ubiquiti discovery protocol enabled, so there are two different ways that the Netonix should be able to use to discover them and both are failing. Enable the Discover Cloud Key option at the top right. Ubiquiti Discovery tool release notes v2.5.1 - added IPv6 link-local access with recovery UI and recovery IP address - quick access to Rescue WebUI using SSH tunnel - display link-local Rescue address v2.4.1 - added MD5, SHA512 passwords challanges - updated product recognition v2.3. Go to the website and you will be presented with a window like below. Yes, there are a few things that could potentially be causing issues. Configuring the Ubiquiti Discovery Tool and Controller Once you have the controller software installed on whatever server you are using the setting will be the same.
![ubiquiti device discovery tool. ubiquiti device discovery tool.](https://img.crx4chrome.com/8f/aa/26/hmpigflbjeapnknladcfphgkemopofig-screenshot-1.jpg)
I will setup a test later on and verify if I am able to prevent discovery from populating by playing with VLAN ID's and tagged ports. Stephen wrote:The only thing I can think that it might be is that potentially the tagged ports could be related.