Showing results for 
Search instead for 
Did you mean: 
Create Post

What we are working on for UDT (Updated August 10, 2020)


The latest release of User Device Tracker (UDT) is available on and in your customer portal. We hope you're enjoying the features of our current UDT 2020.2 release! 2020.2 delivered support for Viptela devices and a host of bug fixes.


With another successful release under our belt, it's time to start working on new features for the next release. Here are just a few items we have in the works for you:

  • SD-WAN vEdge Visibility - discover and display directly connected devices for the most popular SD-WAN vendors.
  • Juniper ELS Support - discover VLAN information from Juniper ELS capable devices.
  • Usability Improvements - database performance and scalability; highly requested interface tweaks.
  • Device View Integration - an overlay of UDT information on one of NPM's newest features.

Learn more about the Orion Platform improvements here: The Orion Platform.


You ask, we listen. Many of the top features developed for UDT are generated through your participation in user sessions and your votes in the Feature Requests forum. Thank you for your valuable feedback.


Tags (1)

The discovery idea is very bad. It also conflicts with running UDT in large environments.

Richard, why do you please think it conflicts with running in large environments?

When can we expect the new version to be out for RC?

Because we don't run discovery

What we do in reality is add the nodes to our own CMDB

Import those nodes and interfaces into NPM using SWIS

Add them to NCM using SWIS

periodically run the 'discovery' process in UDT to re-add nodes to UDT

What we like to do is add manged nodes to NCM, run inventory collection on them, flag the interfaces (or ports) for monitoring by NPM (or UDT).


we don't have any firm dates yet, will keep you updated.


Not everyone is going this way Richard - we have even bigger customers using discovery. However I can imagine that for some organizations, it's easier to get data from one source - CMDB.

I am glad to see that you guys are adding the IP to the New MAC alert improvement. Have you considered adding the MAC to the IP alert? or to combine both alerts and let the user select within multiple trigger conditions and/or multiple variables for the Trigger Actions.

One thing that is seriously lacking is importing items to a watch list. For example: PCI requires that you must watch your network to see if Rogue APs are connected to the wired network. With my Cisco WLC managed, I can run a report in Orion to show me all rogues and their MACs, however, I can't just have them automatically added to the UDT watch list. I have to manually enter each MAC and then compare that list to the new report list periodically and true up. With 350+ locations in retail areas, this is a huge burden.


We use unlimited UDT on top of unlimited NPM and NCM to monitor our environment.

UDT is such a great product but I think it is missing integration with NPM or Orion Core.

For example I found that UDT use PortID instead of NPM InterfaceID although using the same NodeID.

I think this is why I cant have UDT Port Detail resource in my Interface Detail page which will be very helpful.

In my mind, with integration we can also avoid separate discovery process.

If license is the concern, we can just unmonitor it like it is now.

This will be great breakthrough for UDT if can happen.

Look forward to it.

Peter -

Will 3.1 support Windows Server 2012 R2 as a platform?



Hi John,

yes, 2012 R2 will be supported.


None of these features are nearly as important to our Enterprise as ARP entries from Cisco ASAs and Bulk imports into the device watchlist. We have 70% of our devices behind store firewalls and it has made UDT useless. Also, we need to track rogue APs for PCI and could easily import all of them via a CSV from the NPM Wireless Rogue AP report. Today, there are nearly 1000 Rogues that have to be manually keyed in to the watchlist.

Yes it needs to be integrated into Orion npm.

we have not bought it because of lack of integration. We are awaiting this to occur. Please treat this as a priority

peter.ksenzsigh will UDT 3.1 support HuaWei devices?

Not in this release. However, CLI parser (which would simplify enablement of any vendor support) is a high priority feature planned in some of our near vNexts..


Do you have a roadmap for UDT 3.2 / 4.x?

I'd like to know what your planned feature list is for future releases so I can do some planning. I understand that plans change and that these would not be solid commitments, but with other products we had some kind of future roadmap.

e.g. NPM had web-based reporting, web-based alerting, and generally 'moving tools to the web UI' as a long-term view.

NCM had 'merging databases' and again, moving the server-based tools to the webUI.

I have no idea what the long-term strategy is for UDT (or IPAM)

Hi Richard,

so the long term goals for UDT are:

1, to improve vendor support - more devices supported (by implementing CLI parsing)

2, to redesign the whitelisting so its more flexible and usefull also in big networks (with a condition builder, mass import/export functions, automated port shut features etc..)

3, to improve wireless capabilities

4, to continously invest into scalability and performance (ideally with each release) as the number of endpoints connected to networks is growing really fast..

and lot more



Was wondering if you are working on the below also.

1.     Port Description added as a column.

2.     UDT Custom MAP ToolTip Support.

3.     Ability to reset an Error Disabled Port after a security Violation

Please add Err-disable reporting:



Please, update the WWWO list for UDT. The list still contains plans for UDT v3.1, which was released a year ago.  We're already on 3.2.1. Thanks! 


I really like seeing err-disabled status but what about adding unplugged if the interface in NPM is set to unpluggable?

I think many are confused when they add interfaces to UDT which create red dots on their node status icons for port is down child status when the same ports are not down in NPM.

I have set the value for UDT to false for dbo.nodechildstatusparticipation but that shouldn't be needed.


Thanks for pointing out, tha last year has passed somehow faster than usually...


Hi Christian,

We received couple of requests for more options available in parent-child status configuration however it still doesn't compete with any of the above features. Thanks for feedback anyway as every "vote" counts and as soon as we get all top-priorities off the list we can start working on the next ones.


Can you share some screenshots about new features? Especially about NTA Integration and VRF Information.

Hi Rams,

not yet, as Dev is still in a phase of investigating tech. feasibility. I will update the post once we are further with the research.


"Following recent UDT 3.2.2 Service release"

Was this released? I saw that 3.2.1 had been released, and then was almost immediately pulled back (with almost no news about why, something about waiting until 3.2.2).  My portal still shows 3.2.0 as the latest release.

We took it down as decided to use next version of core to leverage new Orion feature like web-alerting etc.. Please bear with us as you will be really soon notified about 3.2.2 availability.


I concur with the integration piece of NPM.

Thanks guys for the constructive feedback! any other integration points you would like to see in a future?


I would like to see the ability to view if a port is in an err-disabled state or not, and see the port description column. Also, the ability to use in the map tooltips under ports "${PortDescription}"

Yes err-disabled and unplugged(based on NPM setting)

I would like to pull reports based off custom setting i.e. Datacenter and campus LAN. It would be nice to have a total port count just only for the datacenter side and campus LAN side. I have had request and worked with your techs on this. We haven't been too successful yet on the reporting piece.

Any plans to add additional reporting capabilities for different media types?

Use Case example, Cisco 3750-X Switches containing mixture of 10/100/1000BaseTE fixed RJ-45, and SFP Slots contained in uplink modules. You can get a total port count and avaialbility pretty easily, but it's not easy to distinguish between the physical media types of the actual interface.

It'd be useful for capacity planning to have a report that gave a breakdown of physical port type availability by switch.

What is the projected time frame 3.3 will be out?

Can we have a new thread for new releases -- it is very confusing to reach comments asking when 3.2 is coming out on a thread relevant to a post 3.2 release.

Aside: if you want me to alpha/beta/test the VRF support let me know and we'll get it installed on our test server.

Hi Richard, we have changed the system to keep updating existing threads to simplify the maintenance of the main WWO page of all products. I will raise your point however to other colleagues to reconsider this.



Hi RichardLetts‌,

Please see this announcement for more details on the changes that were made to the WWWO guides. We are aware of the irrelevancy of some of the comments on these threads and we are exploring our options as our platform vendor doesn't offer an easy way to archive comments. In the meantime, we hope the ability to bookmark a single post will prove to be helpful since now you will always have the latest and greatest information as soon as an update is available. 


Is there an update as to when UDT will be updated for the 2017.x Orion Platform?

Is UDT going away, or going to be replaced?  Is it still being worked on?

Its long do we have to wait for Cisco nexus support?

Any future plans with this product?  Been a while since any updates, and calling support for the UDT line usually goes past the 1 hour queue time and boots me out. 

I could see in the portal 3.3.1 RC2 but nothing about that here or in RC web page, what is include on it ?



I have recently purchased UDT to monitor all ports in our data centre.  Our Information Security team dictates that no passwords should be sent in clear text for this reason we are not able to use SNMP v2 and have to use SNMP v3 on all network devices.

I am shocked to 'discover' that User Device Tracker does not support SNMP v3 full stop.....

Is it on the road map to enable SNMP v3 with UDT??

I have found the 'feature' request at the following link   which is open for voting.  I don't really consider this to be a feature however it's just basic security for devices on the network!?!?

Why does NPM support SNMP v3 when UDT does not?  What's the rationale here?

ashleyhames​, thanks - this is excellent feedback and we'll consider this feature.

Historically, the discovery and polling mechanisms for NPM and UDT were developed independently; while the functionality overlaps significantly, the data collected is used very differently. The behavior and the configuration of the discovery and polling currently differ significantly. We've heard very clearly that users would like to see consistent behavior, and have a unified configuration experience. Thanks for your clear and direct expectations here. As the product evolves, we'll reach out to you for feedback on the features and behaviors in the tool.


One big HUGE thing that needs to be fixed is multi-VRF support for devices like the Nexus 7K, which isolates each VRF's ARP table into a separate context. 

Right now I can only poll a Nexus 7K within Orion on a single context, thus I can only poll for a single VRF.    We should be able to associate multiple SNMP contexts with a single box so the different ARP/Routing tables can get polled.

It appears that the last bullet "Discover and monitor network equipment requiring a command-line interface, like Cisco Nexus gear" should accomplish this.  There are many networks using Nexus and it's VRF functionality. I could see this being a deal breaker for some people.

Is UDT to the point where it can:

  1. Get the ARP info for MAC addresses from Cisco ASA's?
  2. Use snmp-v3 instead of v3?

If so, would you kindly paste in a link I can follow to read the process for making both of these items work for us?

I'd be curious how large organizations are doing discovery and managing which ports are monitored. I don't need an alert every time one of our 30k Windows PCs reboots, so we manually add and only monitor trunk interfaces.

We don't monitor down to switch port level. Trunk only. 

Version history
Revision #:
5 of 5
Last update:
‎08-11-2020 09:21 AM
Updated by: