Dear all,
Let me please update you with info what is our Dev team working on right now for UDT 3.1. The main focus of this release is the stability and performance of UDT in bigger environments.
To achieve the improvements, we have to rebuild our discovery process first, so it can serve well also when adding 1000+ switches at once. Idea is to do the discovery of nodes first, to save the results, then to poll the interfaces and have results saved again, and only then to ask user which ports will be tracked by UDT.
Also, if you already have done the discovery using NPM, we will be able to continue from there, without forcing the new users to do the same discovery again.
Apart these major changes to the discovery, we will be implementing also a number of fixes to the known bugs (the Node ID and port ID to be displayed in the New MAC alert, no DNS/IP info polled from various devices, count of endpoints per SSID, some out of memory exceptions will be fixed etc..)
From the UI perspective, the biggest change will be the implementation of Vendor identification based on MAC address feature request from thwack ideation page (thanks for your votes, “Vox populi” really helps us with prioritization!)
Vendor name and respective icon will be displayed in several resources: Endpoint Details resource, in MAC endpoint popup on Node details page, in Rogue devices resource… Naturally, you will be allowed to report this value too. In addition to these, a new Vendor resource (pie chart) will be created:
This pie chart will take you to the search result page with all endpoints from the specific vendor listed. In addition, you will be able to setup new Alert triggered by a new vendor connecting to your network (so next time somebody brings Nintendo Wii to the office, you will be first to know about it )
Speaking of Alerts: we’ve decided to implement another popular request – New MAC alert improvement by adding IP, DNS, Device ID and port ID in to the emails sent.
Last but not least, with UDT 3.1, we aim to support Motorola and Ruckus wireless devices, allowing you to track endpoints on wider variety of networks.
Looking forward your feedback
Peter Ksenzsigh