Rainevar

t's time (and more) for there to be a way to administratively specify the sysObjectID -> Vendor and MachineType mappings Once this is done then we will have somewhere to also add other configuration items such as: - UnDP pollers added to discovered devices based on the sysObjectID so we do not have to add them manually…

Yes, I am aware of that. I was referring a feature to automatically mapped my UnDP custom poller (node and interface) to new device based on sysOID or interface type/speed.

I vote for more integration between UDT and NPM!!!

After spend sometime with UDT, I realize the main factor why it cant happen now UDT use PortID instead of OrionCore/NPM InterfaceID although using the same NodeID. I think this is why I they need separate discovery process and cant have UDT Port Detail resource in my Interface Detail page. This will be great breakthrough…

Hi Richard, This is a very good workaround. Thanks, R

Does this work for you? It doesn't work for me. Can you share your custom report query?

Thanks michalB. It's very unfortunate.

Hi michalB, That is not what I meant. I want the make UDT discovery process recurring everyday. Thanks, R

I didnt realize its that easy... I thought it will delete the node from NPM as well. Thanks MichalB

I am aware of that. Which is why I post in feature request thread. We already use the syslog alert action to send email notification. Both to trigger and reset condition. But in flapping event, you will easily miss track the status. If it shown in Alert window, we will know for sure if the event is still happen or not.…

Hi, 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…