Page 1 of 3

Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 12:20 pm
by cloudcom
Hi,
I created an auto discovery job for anip range with /24 subnet like 10.10.96.0/24

almost one day later, I checked the wizard and saw that it is still running, no detected devices.

İf I create a job with /26 subnet, it works. (gives results even if it takes very long time).

Is it normal that it takes long time?
And do you have a solution that works the "job with /24" ?

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 12:47 pm
by tmcdonald
A /26 network will have 62 hosts at most, whereas a /24 can have up to 254 hosts. It's possible that, due to your network layout, the nmap scan running in the backend is getting hung up on some host that would be visible in the /24 but would not be visible in the /26 network.

Try running the following from the command line:

Code: Select all

time nmap -vv 10.10.96.0/24 | tee /tmp/nmap.out
then send the /tmp/nmap.out file to me in a PM. If the command seems to hang on a certain step for more than 5 minutes, take a screenshot of where it is hanging and send it over. Otherwise let it run its course and send the file when it is done.

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 2:46 pm
by cloudcom
I run the command.
İt has finished succesfully and takes 31 minutes.
Does it mean that auto discovery works fine? I tried many times from GUI but it never works!
What should be problem then? What is the point that I missed?

I sent nmap.out file to you by PM.

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 2:48 pm
by abrist
What version of the autodiscovery component and configwizard are you using? (go to admin --> manage components/manage configwizards)

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 2:54 pm
by cloudcom
abrist wrote:What version of the autodiscovery component and configwizard are you using? (go to admin --> manage components/manage configwizards)
Auto-Discovery
Provides device and service auto-discovery.
Version: 2.04 Author: Nagios Enterprises, LLC

Auto-Discovery
Monitor devices and services found by auto-discovery jobs.
Version: 1.3

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 3:11 pm
by tmcdonald
You should be on version 1.3.2 of the Wizard. It looks like in your other thread you had tried to install it? http://support.nagios.com/forum/viewtop ... 16&t=27310

Can you provide a screenshot of the Admin -> Manage Config Wizards page? It should be v1.3.2 if you installed the wizard linked in that post.

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 3:36 pm
by cloudcom
Yes, it was 1.3.2

under the topic http://support.nagios.com/forum/viewtop ... 16&t=27310
cloudcom wrote:Hi slansing,

This is the last version of the auto discovery wizard.
I run "check for update" and it showed "uptodate".

I can not set all devices' commands by hand. I must fix the problem.
Can re-installing the Nagios-XI be a solution?

but I have re-installed the nagiosXI so it is 1.3 now

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 3:40 pm
by tmcdonald
It needs to be 1.3.2 now. Upload the wizard and it should work fine, especially after the reinstall.

Re: Auto discovery does not work with /24 subnet

Posted: Mon Jun 02, 2014 5:07 pm
by cloudcom
I have installed the updated wizard again, and it did not work again :(

I prepared some screen shots in order to show the problem more clearly:
auto discovery screen shots.docx
Version 1.3.2 solves niether the topic http://support.nagios.com/forum/viewtop ... 16&t=27310 nor the topic http://support.nagios.com/forum/viewtop ... 16&t=27444

The problems persist.

Re: Auto discovery does not work with /24 subnet

Posted: Tue Jun 03, 2014 1:50 am
by cloudcom
I checked the progress of auto discovery a short time ago.
It is still running but "Lust Run" field have been changed.
As you see from above screenshots, I run the auto discover job at 23:51 yesterday.

But now, it shows the time as 09:34
Last Run.png
I guess It has time limit and after a particular time, it re-runs the job. Right?