Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > User Device Tracker (UDT) > All nodes and ports being automatically added to UDT

All nodes and ports being automatically added to UDT

Created by Matthew Lamb, last modified by Matthew Lamb on Nov 17, 2017

Views: 276 Votes: 2 Revisions: 12

Updated 23rd Oct 2017

Overview

This article pertains to an issue that can occur with the upgrade of UDT to version 3.3. In this issue, any node that is not within UDT already is automatically added within UDT. This includes all the nodes ports if they are SNMP and even includes WMI based nodes that are not capable of being polled by UDT for port and endpoint information.

 

This problem can occur with existing nodes and any nodes added in after this point.
Attempts to remove the nodes will result in the nodes being added back into UDT shortly thereafter.


You might also see files filling up in the following folder. It's safe to clear these out until a fix is in place.

Environment

  • UDT 3.3

 

Cause 

Incorrect handling of polling jobs on nodes on startup.
It starts the jobs on all listed nodeids, causing them to be added into UDT in the process.

 

Resolution

This issue was resolved with UDT 3.3 Hotfix 1.


Once applied all should be fine going forward.

But if you were on UDT without Hotfix 1 for some time, then additional steps maybe needed.
Do check your UDT Configuration as it is possible you may need to fix some UDT Configuration if Hotfix 1 wasn't applied at the time of UDT 3.3 deployment. 


For resolving the issue please do the following:

1. Please apply UDT 3.3 HF1, simply run the Orion Installer or download it from https://customerportal.solarwinds.com/HotFixes# (Install HotFix on all servers [primary poller, APEs, AWSs])

2. From the Orion web console go to the Port Management (../Orion/UDT/Ports/Default.aspx) page.

3. Chose Show: Nodes and Filter to: UDT Monitored Nodes.

4. Check nodes you don't need to monitor with UDT.

5. Click "Delete" button.

6. Make sure only "Delete node and data from UDT only" checked and click "Delete" button.

7. Repeat steps 4-6 for all node pages if needed.

 

Steps 2-7 should not be needed for any customers that installed UDT 3.3 after the time UDT Hotfix 1 was released, as the hotfix now auto installs with UDT 3.3.

 

If you did require the hotfix to correct the issue, then we recommend the next steps as well:

  • 1) Stop All Orion services (on all pollers if there are multiple pollers)
  • 2) Execute these two SQL queries in the following order: 
    • L2\L3 polling isn't needed for Windows devices, as such, run the following SQL query in database Manager:
      delete from udt_nodecapability where nodeid in (select nodeid from nodesdata where objectsubtype = 'WMI') and Capability != 8
    • Next to clean up the UDT Tables after running above query, to remove unwanted UDT jobs.
    • DELETE FROM udt_job WHERE nodeid NOT IN (SELECT nodeid FROM udt_nodecapability)
  • 3) Clean up Collector 'sdf' data and JobEngine 'sdf' data *** on all Pollers *** .
    • JobEngine data: *C:\ProgramData\Solarwinds\JobEngine.v2\Data\*
    • Collector data: *C:\ProgramData\SolarWinds\Collector\Data\*

For clean up data file do the next:

  • - stop all SolarWinds services (on all pollers if there are multiple pollers);
  • - navigate to 'Data' folders above;
  • - prepare a backup copy of 'JobEngine35.sdf' or 'PollingController.sdf' file;
  • - delete 'JobEngine35.sdf' or 'PollingController.sdf' ;
  • - copy 'JobEngine35 - Blank.sdf' or 'PollingController-Blank.sdf' to the same folder and rename it to 'JobEngine35.sdf' or 'PollingController.sdf';
  • - remove the "Read-only" attribute from that files;
  • - start all SolarWinds services.

 

Support members: if a customer reports on this issue, please submit this issue to development and link Jira CUST-35968 as the master issue for now. The issue is corrected via buddy drop, so development needs to confirm the issue and can provide BD if it's the same problem. DO NOT SUPPLY BUDDY DROP WITHOUT DEVELOPMENT APPROVAL.

 

UPDATE BD is not needed now that HF1 is now out.

 

 

Suggested Tags:  <g class="gr_ gr_79 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling ins-del multiReplace" data-gr-id="79" id="79">udt</g>, node, auto, automatically, <g class="gr_ gr_78 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del" data-gr-id="78" id="78">add</g>, added, all nodes, <g class="gr_ gr_80 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling" data-gr-id="80" id="80">wmi</g>, ports

 

A reason for rework or Feedback from Technical Content Review:

 

 

Last modified

Tags

Classifications

Public