EmployeeEmployeeHey Chris,
Usually, if a ConfigSource has been applied for "a while" but discovered no instances, I would expect that to be down to credentials or the device refusing the SSH connection from the Collector's IP, so I would take a sample non-responsive Resource in LM and double-check the ssh.user/ssh.pass values against the device itself, and ensure the device's config isn't going to be blocking a port 22 connection from the Collector.
You can also use the "Test script" button within the ConfigSource definition page to select one of the non-responsive devices as a test (start with the Active Discovery script) to see what the Collector sees.
Also, if you run Active Discovery against a Resource, the Collector debug commands !adlist, suitably targeted to the Resource and/or ConfigSource name, and !adetail for the relevant discovery task ID, may show error message details.
Hope this helps!
Antony
