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'

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

We have a bunch of switches added in NPM and whomever added them previously did not scan for UDT ports when adding the nodes.  Now, I'd like to have those switches scanning with UDT ports and I can't seem to find a way to additionally add that on the existing node.  The only way I've seemed to find was to delete the node, re-add it, and then click "scan for UDT" while finalizing the addition of the node.  Is this this only way, or am I simply missing something?

Hello,

Does anyone has the following issue which seems to happen on Alcatel switchsonly ?

This is an issue about the displayed VLAN numbers when I look at the UDT ports of a Alcatel switch.

Here is a real example to explain and show the issue:

First, I can check information on a connected PC:

The ipconfig shows an IP address starting by 10.20,
which means in our infra I'm clearly on VLAN 20.

Carte Ethernet Connexion au réseau local :

   Suffixe DNS propre à la connexion. . . : administration.adm
   Description. . . . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
   Adresse physique . . . . . . . . . . . : 64-00-6A-4F-AB-CD
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::91b:5520:d7dc:1c14%11(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 10.20.0.59(préféré)

I can also check on the switch (CLI) it's connected on that I see on port 27 my Mac Address on VLAN 20

JT-RDC-SW5-> showmac-address-table 1/27

Domain   Vlan/SrvcId        Mac Address            Type         Protocol     Operation          Interface

--------+--------------+---------------------+----------------+------------+--------------+------------------------

   VLAN    20             00:0c:29:cc:xx:xx     learned          ---          bridging       1/27

   VLAN    20             00:21:b7:2e:xx:xx     learned          ---          bridging       1/27

   VLAN    20             48:4d:7e:f0:xx:xx     learned          ---          bridging       1/27

  VLAN    20             64:00:6a:4f:ab:cd     learned          ---          bridging       1/27

Note: The port 27 is an access port which I see to be on VLAN 20 by the following command.

JT-RDC-SW5-> show vlan port

vlan   port     type      status

------+-------+---------+-------------

...

   20   1/27    default   forwarding

...

Everything looks consitent so far,
except, when I look at the UDT page of the switch, I see "Vlan 1" on the very right column

And the issue is that I see VLAN 1 on every ALCATEL access port (amongs hundreds switch, whatever the switch and whatever the port)

			1/27		10.20.0.x		64:00:6A:4F:AB:CD	1
					10.20.3.x		48:4D:7E:F0:xx:xx	1
					10.20.7.x		00:21:B7:2E:xx:xx	1
					10.20.0.x		EC:B1:D7:D9:xx:xx	1

Whick makes the UDT module very not usefull
What is really frustrating is that I see however "1,20" (as follow) when I move the mouse over the port number, but not 20 (or at least 1,20) at the end of the column in the UDT Table.

Solarwinds support tells me that my switchs (Alcatel 6850) might not support the OID requested... but first I don't think I have control over this OID value,

and second I can't believe that more than 100 Alcatel switchs do not follow SW MID standard...

I knew that Solarwinds was not entirely compatible Alcatel, but for such a basic function I don't believe there's no solution.

Does anyone meet the same issue ?

If anyone has their Alcatel Switch 6850 working well with UDT,
I'll be more than happy to see that's working for somebody else.

Thank you everyone for your feedback.

Jean-Thierry

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?

Hello Everyone, we wanted to remove/unmanage the ports in bulk from UDT module. We have added all the ports of the network devices into the UDT module(nearly 4k). Now i need to remove the logical, loopbak or virtula etc ports from UDT monitoring. As well as, we have reports which includes all the ports utilization, if i want to remove these specific ports then, how I can achieve this. Please provide your suggestion. Thanks in advance!

Hi,

I am seeing a notification banner for UDT polling jobs still running. I saw another thread where it was mentioned to just increase the Layer 2 and 3 job timeout value little bit.

I did that but i see the count of 300+ polling jobs running. does it take lot of time to process? Or any other things need to be checked?

Hello SolarWinds community,

Is there a way to tell what is connected to a switch using UDT? I remember there used to be port history, but I am not sure what changed because this information is no longer available. Is this a default setting for UDT? To identify and catalogue what is connected to a port on a switch? If so, what settings can I check to enable this feature again?

Hi,

I have this message very often 

New UDT polling jobs (3) are still running..

I keep extending the polling interval (I was at 120 minutes and now 500) but still get this message.

What does this message means exactly and how do I fix it ?

Second question, I have an additionnal poller, can I put the UDT charge of certain devices to this poller ?

Thank you

Hi!

Read somewhere that NPM & UDT stores LLDP information internally in its SQL DB,

1) is there a way to extract this information to show all the switches that has a LG-Ericsson device (VoIP - LLDP MED) attached to it?

2) Can the above information automatically be fed to NCM to automatically tag the VOICE VLAN on those ports? This to speedup rollout of new PBX.

I understand that item two is advanced, but perhaps the first item should be doable?

/Kaj

Long time reader, first time poster.

In an attempt to create a single pain of glass within UDT,  I am running into a problem with our router/firewall. There is no option to poll the ARP table via SNMP. I have access to the database and have looked at several tables and was wondering if anyone has used the SDK or created a homebrew solution to push IP/MAC into the UDT_EndpointIP table and if so does anyone know if the UDT_IPAddressCurrent/History tables need to be updated as well or is that information updated from within the already existing framework of the UDT product?

I'm ready to back things up and start testing but was hoping that someone has already invented the wheel and that I could stand on their shoulders.

The other option I've looked at is to take a spare device and manually populate the ARP table using Perl and API calls to the router to get the current data.

Thanks,

Rosie

P.S. If I should post this elsewhere please let me know.

Hi,

I am new to Soalrwinds. I am having an issue with UDT device connection history. If I connect a PC to a port , it detects the port and shows the time "First Seen" properly.

But when I remove the device it continues to still show it as connected, although it recognizes the port is down. SO I see "Last Seen" as "Current" instead of the actual time. I have seen this behavior at least hours after device being disconnected. 

Hi,

Can you help me configure Alert Trigger Action to block a MAC or Shutdown a switch port when a new Rogue device is detected by using VB scripting and passing the MAC address variable?

I found the below Twack article and would like to do something similar but in my case block rogue devices.

https://thwack.solarwinds.com/docs/DOC-177839

Or please let me know if there is a more optimal way to accomplish this.

Your help is greatly appreciated!

Thank you.

Hey all, I am trying to clean up our UDT database and I am wondering if any of you know of a good way to get a report on MAC addresses that have a "Last seen" date of a month or older.

Even if I could get a pointer of where that information is location in the database is, I could do a query there and that would help too.

Thanks everyone for your time.

We recently switched from Brocade to Cisco C9410R also added new DHCP scope for users. I made sure DHCP, DNS and DC are setup correctly, but we can't see any endpoints in UDT (we still have a few brocades online and they work fine).

I used the UDT compatibility checker and it showed "auth errors" for some MIBs.

but my Network Engineer tells me the switch is setup correctly it should be able to read all global MIBs. So we opened ticket with Cisco they had us do a SNMPwalk, and it was in fact able to get all the MIBs I think.

So I'm not sure why was UDT comp check throwing errors. Opened a case with SW support, no response of yet.

Some aspects of managing UDT ports still confuse me a little. Here are a couple of clarifying questions.

1. True or False - One must monitor an interface by NPM before it can be monitored as a port by UDT.

2. If #1 is False, then how does one add new ports to a node that already exists in Orion?

3. I am able to Search for and find a hostname, but when I drill down the the Endpoint Details view, no Current or Historical Connection data is present. Why is this? The node has certainly been connected for quite some time.

Thanks for any help.

A couple of months ago I upgraded NPM to 12.2, and all the other matching upgrades for NCM, NTA.  I also installed the recommended Hot Fixes.

Then I bought IPAM and UDT and installed them, along with one more APE.

They ran OK for a few weeks, but now I've got this message showing up in the Alerts part of NPM's home page:

New UDT polling jobs (388) are still running...

I searched for that message in Support & Thwack; haven't found the issue.  I was hoping it was something I could correct by changing UDT  polling timeouts, but although I've tried doubling them once, and doubling them a second time, there's been no improvement.

Might you have an idea about what's going on here?  I've had reoccurring issues where the C drives on APE have filled, and SW Support seems to think the issue is possibly:

• The C drives are sized too small (they're not, per SW recommendation)
• Anti-Virus is stopping reports from getting to the main NPM instance (AV is configured to exempt the recommended directories, but the logs say communications are failing between the APE's and NPM)
• I removed failing NetPath monitors in hopes that might fix it.  No luck.

If you have ideas on what's going on with my UDT, based on this alert, I'd love to hear from you.

It seems that after changing switch devices from SNMPV2 to  SNMPv3 UDT no longer show port information. NPM info all looks good interface , hardware monitoring etc.... all good

I've got a Dell-manufactured network. My Layer 3 core switch is fully supported by UDT, but my PowerConnect-W-series wireless APs only have Layer 2 support. As a result, when my users connect their smartphones to the guest network, I get a rogue MAC alert. There is no information about the associated DNS name or IP address (which would tell me guest or WLAN) included.

My workaround is to look up the MAC address on my wireless AP controller, figure out what it is coming from, and individually whitelist it. Now that all my colleagues' phones are pretty well checked in, UDT is not shrieking so much anymore.

My question for the community is, Is this best I can do? What other options or steps should I consider?

I know that I can use the OOB report named "UDT: All Endpoints" to see what MAC addresses and IPs are attached to what switch port at any point in time.

What I need is to have a report that will list any MAC address/IP address that has moved switch ports during whatever time period I designate.

The intention is to use this report to make sure that as we proceed with replacing old switches, we are able to plug endpoints back into the same port number as before and document it when something has moved.

Any ideas? I could do this by exporting the report into Excel and doing some sorting, but I would rather have a report.

Thanks for helping me.