We are trying to get our UDT to actually display IP:MAC and tell us where the enduser is connected. We have monitored the ports via discovery wizard, and have AD tied to the platform. What are we missing?
There's a great post by @mesverrum. Kindly check the link below.
https://thwack.solarwinds.com/discussion/102868/solar-winds-device-tracker-doesnt-make-sense#latest
So, UDT is actually quite simple and basic if you break it down into its components. The first part that needs to work right is getting the MAC addresses. For this, the device needs to be monitoring the right "Ports" from a discovery, as opposed to "Interfaces". If you added devices manually and didn't get the ports discovered right, just rediscover them using a discovery, much easier. There 2 places in discovery where it asks you about what ports or interfaces you want. Interfaces is NPM performance monitoring, Ports is UDT where it gets the MAC address. You >should< be monitoring all access ports, whether they're currently active or not. You don't need to do trunks as they have LOTS of mac addresses on them, but it won't affect it working or not, it will just give you a bunch of "indirect" ports where the MAC isn't monitored.
These MAC addresses get connected to their IP addresses by monitoring routers for those VLANs / networks. Make sure you're monitoring all the ports on your LAN side at least. You might have problems if you're doing VRF's as SW doesn't really like to scan all the VRF's. When you're done, if its associating mac with IP's, then this is done right.
The active directory part is the hardest. You need the right permissions to access the logs in AD where it will parse them for what userID logs into what IP address. If you aren't getting usernames associated with the IP/MAC, its almost always a credential or permissions issue. SW will access this frequently, so make sure your creds don't get locked out. Here is a snipped on the creds, I don't recommend giving SW administrator credentials!
"
HTH!
