Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > User Device Tracker (UDT) > User Device Tracker (UDT) Documentation > UDT Administrator Guide > Troubleshooting > Node discovery fails for some devices

Node discovery fails for some devices

Table of contents
Created by Steven Bansil_ret, last modified by Steven Bansil_ret on Feb 02, 2017

Views: 135 Votes: 0 Revisions: 2

Issue

The device discovery fails when it's done for specific devices.

Solution

  • UDT Discovery runs on the poller the nodes are affiliated with (i.e. it respects main and additional polling engines) since UDT 2.5. Make sure the machine where appropriate poller is installed has access to the selected device.
  • Run UDT Compatibility Checker (discovery target ) from machine with the right polling engine against the device and check the results.
  • Increase Port/Layer3 Discovery Job Timeout (Advanced Settings page)
  • Increase SNMP Timeout (Advanced Settings page)
 
Last modified

Tags

Classifications

Public