Hi all,

i need for my costumized report the LastSeen from the UDT Search.

The LastSeen from sql-tables udt_ipadress udt_endpoint is different of the UDT Search.

From which sql-table is the LastSeen of the UDT Search.

Thanks in advanced

Hi There,

We recently installed UDT v3.2.0 and applied hotfix 1. When I add nodes to UDT, I cannot view them in NPM to get normal stats - error message appears on the website, however, the nodes that are not added to UDT display normal

Anyone had similar issues?

Would really appreciate the help/advice!

Hi Guys,

We have UDT in our infrastructure and it is not capturing the user details. We have 14 Dc's being Polled to capture that information.

When i check the UDT compatibility Checker. It gives User details for 1 DC and for the rest 13 DC's it says "Eventing6 didnt find any matching log entries"

Kindly let me know what is missing from our end.

Thanks,

Reuben

After researching through existing reports, UDT settings, knowledgebase, DB schema and thwack, I am posting this request to identify:what is the port usage per poller?

I have created a report that helps me find the # of individual elements per poller but am unable to see a place to find details on the ports being monitored by each poller. The idea is to know how to distribute the load of UDT port monitoring per poller.

Can someone assist or point in the right direction?

Thanks

I have edited a report I found here.  Simply put, it lists interfaces that are currently down on a node, but was up earlier, or so I thought.  I have stripped everything away in this report to just show interfaces Operational Status as Down.  In limited instances, Device Tracker shows that certain Operational Status for interfaces are up for example Gi1/0/3 is up.  I run the report and the report shows the "Operational Status is Down" for this interface.   I log into the switch and I see that Gi1/0/3 has been up for 4 hours.  This happens only on 1 or 2 interfaces of a node, and not always.  The report option that I am using is: Operational Status       is not equal to      UP.

I tried the other options of equal to, contains, etc, of Up and Down.  No matter what combination I try, I get the results of the report thinking that the Operational Status is Down.  It seems that Operational Status is not real time?  Is this correct?  If it's not real time, how would I "refresh" this variable?

Does anybody know how this works?

We have a fairly large deployment of Juniper access layer switching that until about a year ago was mostly the EX2200 series. Over the last year and a half we've started using the EX2300 series and unfortunately cannot get UDT working. As we continue to lifecycle devices our population of the 2300 series switches has increased greatly and not being able to use UDT on these devices is frustrating.

Last year we contacted both Solarwinds support and Juniper about this and what we found is that Juniper changed OIDs somewhere between the EX2200 series we have running OS 12.x to the EX233 series we are now getting running OS 15.x. This is also causing issues with vlan polling.

Has anybody else ran into this issue and if so what are you doing about it? Solarwinds asked us to submit a feature request for this which we did, but that was a year ago and Juniper has also not been able to help. Within another year or two we'll have refreshed all of our devices and if this is still not working UDT will become completely useless to us.

Forgot to mention that this will not work with on any Juniper ELS devices. With everything in their product line heading this way I would hope something will change to get this working in the near future.

We have recently implemented Rogue alerts in UDT. This is notifying us of items showing up as Rogue devices, those that are not in our approved MAC address white list.

The only problem is it seems like we keep getting Rogue Alerts for devices that are already in our whitelist. For example, we've been installing new printers at several locations. This morning when I installed a new one a few hours later we got a rogue alert for that device (working as designed) but then we also got 5 additional alerts for printers that we had already installed. We had already acknowledged those printer's rogue alerts, and those printers were already in the white list. I thought for a few weeks this was just a fluke but that has occurred numerous time to the point where my staff is spending more time searching for invalid alerts than valid alerts.

Is anyone using Rogue alerts? Have you seen similar problems to this?

The potential for this feature in UDT, especially as far the the SANS controls go, is great. However barriers to getting this to work seem great as well.

We have an issue where if a particular switch goes offline (usually due to an ISP at a remote site, from a power outage, or sometimes even with the switch rebooting) the UDT system automatically marks those ports on that device as unmonitored.  When the device is polling again UDT doesn't automatically restore those ports as monitored.  Usually I will come across a switch and notice that the port information isn't appearing like it should and I will check the ports and they went unmonitored again.  Its easy enough to re-activate the monitoring.  It would be nice though if it didn't do this.  Is there a setting that manages this?  Is it based on a time frame of being offline?  Is there a way to send an alert when the UDT automatically unmonitors a port?

I have installed UDT eval - looks VERY interesting so far; experiencing a couple of router issues and such that other folks are commenting on and have an open case.

One odd thing I have noticed that started virtually the minute UDT became active is SNMP authentication failures - we capture these in NPM via traps.  What is interesting is that they appear to be coming from my orion server and attempt to communicate via SNMP to any device in the network; whether or not they are in UDT (they are in NPM).  Even more interesting is the extra IP address contained in the trap - see bold below:

snmpTrapEnterprise = RAPID-CITY-MIB:snmpTraps 
experimental.1057.1 = [*local switch address*]
cExtSnmpTargetAuthInetAddr = 49.48.46.49 
cExtSnmpTargetAuthInetType = 1 
authAddr = [*local Orion server address*] 
snmpTrapOID = SNMPv2-MIB:authenticationFailure 
sysUpTime = 3618379348 

Has anyone else seen this or know what it could be coming from?  Again, this started immediately after UDT was installed.

Thanks,

Dave

UDT displays information about devices connected to switches and routers on specific ports. Based on the bridge tables, ARP, CDP, and possibly other data, we collect information about what MAC addresses and IP addresses are on each port, and whether they are connected directly or not.

Some customers have issues with making UDT work with Cisco Nexus 5k and 7k. We mostly find out that some MIBs we need are not accessible, or not supported. We do not know whether this is due to an incorrect configuration of the devices, or the MIBs are really not supported. We found out that NX-OS version 5.2 and later should support the required MIBs, but there are still customers for whom UDT just simply does not work with Nexus.

Recently, we have got access to Cisco lab with two Nexus devices; none of them worked at the first attempt. After some config changes in both of them, they started to work. So what we would really appreciate is someone who could help us analyzing what the minimum version of NX-OS working with UDT is (we can send a list of MIBs we need), and how to configure the devices so the MIBs are available and contain the data we need. SNMP access is not necessarily required, we might be fine with getting the data via console.

If you are interested, please reply to this post or send me a message directly.

Regards,

Jiri

I installed UDT V2.0 RC and I reached a point where I entered the AD credentials that I thought might work, but they failed.

 Exactly what rights, privileges, or access does this account need to have in order for UDT to pull the user information?

I tried to use the embedded link on the page that should have taken me to the answer, but it took me of a generic page of marketing material.

 Can we get the link fixed or even better, can someone tell me what we need.? The download didn’t contain any documentation.

Rick

Hi There,

We recently installed UDT v3.2.0 and applied hotfix 1. When I add nodes to UDT, I cannot view them in NPM to get normal stats - error message appears on the website, however, the nodes that are not added to UDT display normal

Anyone had similar issues?

Would really appreciate the help/advice!

On day 2 of our UDT trial and am a little disappointed. It seems such a powerful tool but seems to display information in a poor way, if it all.

Ive gone into Endpoint Vendors and chosen one of our printer manufactures and am, well, a little underwhelmed by the lack of information available, and am hooping it is configurable but suspect it probably isnt.  All the information is there in a DB somewhere, so Id like to be able to view it.

I was expecting the search results to yield the printer, name, mac, ip, switch name, port number, all in one big easy to see list.  Instead its just showing me the MAC and the Match Type Vendor and no obvious place to add more columns.  I have to then select the MAC to reveal the info for that single device.  Why cant all of this info be presented within the search results as a big list.  We could then easily see all of our printers (or other vendors) ans where they are connected.

Is this possible at all?

Hello,

Has anyone ever had this kind of discards on a device? The first one is a regular old HP Printer plugged into a stacked switch and the second is a port on a catalyst 9300 that goes to a SAN fileserver.

I have installed UDT eval - looks VERY interesting so far; experiencing a couple of router issues and such that other folks are commenting on and have an open case.

One odd thing I have noticed that started virtually the minute UDT became active is SNMP authentication failures - we capture these in NPM via traps.  What is interesting is that they appear to be coming from my orion server and attempt to communicate via SNMP to any device in the network; whether or not they are in UDT (they are in NPM).  Even more interesting is the extra IP address contained in the trap - see bold below:

snmpTrapEnterprise = RAPID-CITY-MIB:snmpTraps 
experimental.1057.1 = [*local switch address*]
cExtSnmpTargetAuthInetAddr = 49.48.46.49 
cExtSnmpTargetAuthInetType = 1 
authAddr = [*local Orion server address*] 
snmpTrapOID = SNMPv2-MIB:authenticationFailure 
sysUpTime = 3618379348 

Has anyone else seen this or know what it could be coming from?  Again, this started immediately after UDT was installed.

Thanks,

Dave

This knowledge base article(and UDT documentation)

SolarWinds Knowledge Base :: User Device Tracker Compatibility Checker

states;

"Layer 3 Job Statistics

Consult these objects about endpoints (IP addresses) and their mapping to corresponding MAC addresses to find what the device whose IP address UDT cannot see is returning for the IP-MAC.

ipNetToMediaTable

ipNetToPhysicalTable

Note: If the device does not support those objects UDT cannot get any layer3 information."

UDT Compatibility Checker shows that some switches on our network are only successful polling ipNetToMediaTable, but fail on ipNetToPhysicalTable.

Running an SNMP get table on the OID for ipNetToMediaTable on these switches does produce results that include MAC addresses and IP addresses.

Should I expect to see Layer 3 results in UDT, or does UDT require both ipNetToMediaTable and ipNetToPhysicalTable?

UDT polling of an Arista router using VRFs is not working for me.  I've tried using snmpv3 and v2 with no success.  The only results UDT gets are for the default VRF.  I've gone through the posts here with no success.  Here is my config on the switch:

snmp-server view v1default iso included

snmp-server community v2test ro

snmp-server group groupv3 v3 auth read v1default

snmp-server user snmpv3 groupv3 v3 auth md5 *****

no snmp-server vrf default

snmp-server vrf THEVRF

Polling from a linux box using v3 and the context THEVRF works fine. I get results I expect.  Polling with v2 is the same from a linux box.  However from UDT I get nothing but the default VRF arp tables. Even using UDT Compatibility Checker fails to see the vrfs.

Has anyone had success with UDT and Arista VRFs?  Any, suggestions?

This may not be the right category, but UDT often deals with endpoints and endpoint names so I assume it will be a good place to ask.

After running the Active Diagnostic tool to resolve some unrelated issues (now solved), I'm having a difficult time identifying what endpoints are being referred to in the issue outlined below. Is there anyway to determine what those UID's are representing? (ie: a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4)

TITLE: Ping all plugins on agents (Agent Infrastructure)

DISCOVERED: 7/25/2016 10:32:35 AM

RESOLUTION: Ensure that the recipient 'Discovery' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' is running.

Ensure that the recipient 'Discovery' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' is running.

Ensure that the recipient 'NetPath' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' is running.

Ensure that the recipient 'NetPath' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' is running.

Ensure that the recipient 'Discovery' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' is running.

Ensure that the recipient 'NetPath' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' is running.

Ensure that the recipient 'NetPath' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' is running.

Ensure that the recipient 'Discovery' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' is running.

DESCRIPTION: Pinging the service has failed: Object reference not set to an instance of an object.

Pinging the service has failed: Object reference not set to an instance of an object.

Pinging recipient 'NetPath' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging recipient 'DPIProbe' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' succeeded with response status 'up'. Version: '2.1.0.174'

Pinging recipient 'JobEngine' on endpoint 'a7b8ceef-cb20-44e8-a6f8-cd3e3f6ee3d4' succeeded with response status 'up'. Version: '2.11.0.223'

Pinging recipient 'JobEngine' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' succeeded with response status 'up'. Version: '2.11.0.223'

Pinging recipient 'NetPath' on endpoint '3cfe3c75-eebb-4c44-8f66-93bd022db524' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging the service has failed: Object reference not set to an instance of an object.

Pinging recipient 'JobEngine' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' succeeded with response status 'up'. Version: '2.11.0.223'

Pinging recipient 'NetPath' on endpoint '7c56b704-f426-46ce-b541-c8e44fa32a8e' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging recipient 'DPIProbe' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' succeeded with response status 'up'. Version: '2.1.0.174'

Pinging recipient 'NetPath' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' has failed because of the error: DeliveryFailedPing message received:{"errorCode":87,"errorMessage":"AgentTaskHandlerBase::execute: ewException caught: Error [0x57], [WorkerProcessController::GetWorkerProcessProxy - invalid plugin usage: pluginId [NetPath], path [C:\\Program Files (x86)\\SolarWinds\\Agent\\Plugins\\NetPath], process type []], File: AgentTaskHandlerBase.cpp, Line: 116"}

Pinging recipient 'Discovery' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' has failed because no response was received in the defined timeout 5000 ms.

Pinging recipient 'JobEngine' on endpoint 'd9b80b3c-fc16-4e18-b8ea-279f369ac779' succeeded with response status 'up'. Version: '2.11.0.223'

Hi everyone,

I just installed UDT 3.3 (30 days test license) on our environment (NPM 12.2, NCM 7.7, IPAM 4.5.2)

I added 2 switches to our UDT for testing. 1 core switch and 1 access switch.

Did a port discovery for those devices and they are now showing on UDT.

BUT... I can't see the VLAN or MAC Address that are on the ports.

I then added a device to the watch-list and I can see that it get's the correct VLAN and Subnet but it tracks it to the Layer 3 interface on the Core switch and not on the interface on the access switch.

Does anyone have the same issue?

BTW my access switch is a Cisco Catalyst 2960-X.

on the Discovery I marked it to get Layer 2 and Layer 3 Topology.

Thanks!

Rafa.

I've done this before, but it's quite a time since I've done it last time.

So, I'm noticing that I'm monitoring two switch ports with NPM (uplinks only) and UDT is monitoring those ports too, but not anything else on that switch. With other switches there is same situation, just some of the ports are monitored by NPM, but I still get every ports monitored with UDT.  So it obviously should be possible but I don't know how. If I open a list view of UDT nodes, I can only see those two ports, and status is "monitored" but nothing else. Other switches I see other ports too, not just the ones that are monitored with NPM.

This must be some really simple thing, that I just cannot find in settings... so can you help...?