As soon as I finished the install and was taken to Network Sonar- I knew this wasn't going to be what I was looking for. As with NCM, the problem here is that when you discover the network, UDT looks like it chews up elements like there is no tomorrow. I can't be positive, because I only run a 100 element license of NPM on my dev box, and despite assurances to the contrary, after running a small discovery with UDT I find that it wants to import 2000 more interfaces than my 100 element NPM license allows. So- so much for running this as a module within Orion. My problem with NCM, and what appears to be a problem with UDT is that while I don't want to collect data and manage every port in my network, I do need user tracking data for the entire network. Since it appears that I must monitor every single port, I would need 8-10 additional pollers over the 4 I already run to keep Orion happy with 7K elements per poller. Not going to happen.
I may back out this install and try a completely standalone installation to evaluate, but this is not what I was hoping to see after being quite vocal about the issue with NCM. I may feel differently once I run this as a standalone, but right now this is not only not a home run, but it never got off the bus into the dugout.
Steve Extrand Sr Network Analyst (1) Orion v10 SLX polling engine & Additional Web Server 35500 elements (3) Orion v10 SLX polling engine (3) NTA v3.7 775 interfaces (3) IPSLA SLAX