ALKSupport,
We definitely recognize this issue. I posted a blog about it with steps to correct this problem. That blog can be found here:
We are also working on a service release (1.0.1) that includes a much easier way to limit which ifTypes are used. The service release is currently in RC and I will send you the download link offline. The default it types will be a much better list in future releases.
Thanks,
Mav
Dear Mav
Thank you for the reply, I managed to get hold of RC 1.0.1 and got it installed today, it solved the issue with capacity planing by de-selecting the port type propVirtual under advanced settings. While it did solve the initial problem it did create a new one else where.
From a capacity planing perspective its naturally only the physical ports thats interesting, but from a inventory / tracking perspective its relevant to follow the MAC and IP information across VLAN's and partically on port groups, it seems that by removing propVirtual type interfaces UDT lost the ability to track this kind of information on bundled trunks in particular.
But for now the first problem is solved, I'll see if there is some working around for the other part.
Regards
René
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.