Troubleshooting
Device discovery fails regardless of the devices selected.
Solution
These are the paths to resolving this issue:
n 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 (try ping etc.),
n Make sure the SNMP requests/responses are not blocked by a firewall.
n Verify that job engine services (JobEngine v2, Collector Polling Controller,
Collector Data Processor, Collector Management Agent) are running.
n Check the UDT.Jobs log to see if the discovery job finished successfully or
shows an error.
n Check the UDT.BusinessLayer log to see if the discovery job's results were
processed successfully or shows an error,
Node Discovery Fails for Some Devices
Issue
Device discovery fails if done for specific devices.
Solution
These are the paths to resolving this issue:
n 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 (try ping
etc.)
n Run UDT Compatibility Checker (discovery target ) from machine with the right
polling engine against the device and check the results
n Increase Port/Layer3 Discovery Job Timeout (Advanced Settings page)
n Increase SNMP Timeout (Advanced Settings page)
UDT Missing User Data
Issue
350
To Next Page