Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > User Device Tracker (UDT) > UDT Administrator Guide > Troubleshooting > Node discovery completely fails

Node discovery completely fails

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

Views: 23 Votes: 0 Revisions: 2

Issue

The device discovery fails regardless of the devices selected.

Solution

  • UDT Discovery always runs on main poller even if the nodes are affiliated with additional poller. Make sure the machine where main poller is installed has access to the selected device.
  • Make sure the SNMP requests/responses are not blocked by a firewall.
  • Verify that job engine services (JobEngine v2, Collector Polling Controller, Collector Data Processor, Collector Management Agent) are running.
  • Check the UDT.Jobs log to see if the discovery job finished successfully or shows an error.
  • Check the UDT.BusinessLayer log to see if the discovery job's results were processed successfully or shows an error.
 
Last modified
22:12, 1 Feb 2017

Tags

Classifications

Public