jokerfest · Systems Engineer · ✭✭✭✭✭

That is weird. There was a new version released yesterday, maybe the online installer has a glitch?

I can help you fix your All Nodes. Chose "All Nodes - Tree" instead. Then you can group by vendor. Then Filter Nodes with [yourCustomProperty='UPS']

I think I've gotten that error before when I tried to upload from a network share. Is your diagnostics file on your local machine?

Most all Cisco devices return a useful value for this OID, but sadly- the Cisco wireless controllers in my environment do not

thanks for the info, it took some research to find a workable alternative

I have created a UnDP for snmpEngineTime (1.3.6.1.6.3.10.2.1.3), which in most cases matches the number we are looking for. I also created a Transform for snmpEngineTimeDays ({snmpEngineTime} / 86400) to help display on reports.

I don't have an answer for the database but I have another option for you. Go to User Device Tracker Settings > Port Management - Manage Ports From there you can Show: Nodes and Filter to: UDT Unmonitored nodes It may take some toying with the settings but that should get you what you are looking for. You can also monitor…

mine is also empty

Drive-by stealing your syntax. Thanks!

This is the way

haha BUMP

thanks for helping to update an old thread - I do mean that, it's normally great to see that and much appreciated in this case - all of the links I can find are dead, even the newer ones

Under Settings, All Settings - here are some of mine You can make free-form fields, yes/no, dropdown boxes, etc.

I will post here for anybody who is interested. As @"rschroeder" mentioned, but is hard to find anywhere: The UNLIMITED APEs for NAM is really 20. While most people will not need more than that, it is quite misleading. TLDR; NAM comes with licensing for 20 additional polling engines.

That sounds like the kind of thing I would use a Custom Property for. I think they are amazing and have so many uses. One of the versatile parts of I've had to explain to others in my organization is that they are completely independent from one another. It can be a managed, tier 2, low priority, and also have a completely…

Thanks for this list. This is exactly what I was hoping to find.

Sad to say, in 2019, running UDT 3.3.2, I am currently having the same issue described here. 

If I make a small test job of a few routers/switches, it will run fine and say "Downloaded and discarded Running Config - no change" I overstated when I said it was doing it for every one though. With my larger jobs in the hundreds, there seem to be some that do and some that don't. I have yet to find a correlation. I will…

I re-created the jobs and they appear to be working properly now. Not an ideal resolution, but a happy outcome nonetheless. Now I can set my cleanup to keep x number of configurations instead of keeping x months and having a whole collection of identical configs.

Thank you wluther, I downloaded your report. This exactly what I was looking for! 

This is perfect. Thank you!

Hi guys, I have been using the "only save configs that have changed" for about a month or so now. Checking my backup files, it is saving a new copy every time, even when they are exactly the same. Is there something that I am missing here? Thanks!

Thank you lynchnigel - I now have a nice one on my node details page:

Thanks silverbacksays for pointing me in the right direction. "none of your devices have been correctly configured" is really what got me looking at the problem from the outside in.

Hey, thanks for checking up on me. I had spaced it. So I just made a custom query and I get the info but it looks kinda clunky. Could I make a custom report so I can change column widths, or is there another better way?

I will be moving site to a new web services server/license. I will also upgrade to the newest release at that time.

No, but I'm in the works to upgrade orion and npm to the newest releases. I was hoping to know if it was a bug other people had experienced or if it was a performance issue. My server is very taxed until I can update/upgrade.

Node is set up with auto determine. I changed, put back, and tried again with no luck...

Thanks for the reminder! I haven't been back to that screen in a while.

are you saying the function is broken? do I need to get out the pitchforks?