How UDT polls Wireless Endpoints

Support for polling wireless controllers (and their access points/clients) has been built into UDT since UDT 2.5. 

Because NPM already had wireless polling, that code was extracted into a shared package now used by both NPM and UDT, so UDT supports the exact same set of wireless devices/vendors as NPM (Cisco, Aruba, Ruckus, Meru, Motorola, HP, Meraki, Aruba Central, RUCKUS One, etc.).

Integration behavior when both products are installed: If NPM and UDT are installed together, NPM takes priority and handles the wireless polling while UDT is suspended for that function — but UDT still has full access to the wireless data NPM collects (stored in the shared Wireless_* tables).

NA

Wired endpoints: UDT_AllEndpoints is populated by UDT via SNMP polling of switches and their interfaces (MAC/IP/port data), not from the AP .

Wireless endpoints: UDT relies on the shared Wireless module (originally built for NPM, extracted into a package both products use) which polls the Wireless LAN Controller (WLC), not the access point directly . "Wireless polling is done by [the] collector, there are no UDT jobs" for this — the AP data (clients, SSIDs, connections) comes from polling the controller that manages the thin APs .

What UDT shows from that data: From the Device Tracker views you can drill into a wireless controller node, open an SSID under "All Access Points and SSIDs," and see Current/All Endpoint Connections for clients connected through that controller/SSID, along with last-login user information correlated from Active Directory .

Once you open the Access Points, you should see the Current Endpoints Connections.