Problem with Auto-Discovery

[ditlevw]

Hi

I can't find anyone else who has the same problem as me, so here you have a thread about my problem with Auto-Discovery.

I've setup Auto-Discovery to scan a subnet on my network. On this subnet, I have both network-devices and the IP of my own PC. Even though I leave Auto-Discovery to search a small part of the network, perhaps just a /27 (ex 10.0.0.0 255.255.255.224), It doesn't find anything. The Auto-Discovery doesn't seem to end the search even if I leave it for hours. One could think, that it could have something to do with access-lists or firewalls, but it isn't that. If I run a normal "manual" Monitoring Wizard, it finds my device in a second.

I've tried to capture the trafic from Nagios XI to my computer and I can see that Nagios does try to check on a lot of open ports, but I still don't get why the Auto-Discovery doesn't finish.

Does anyone else have the same problem?

I'm running Nagios XI 2011R1.5 on a virtual server in an ESX-environment. The license is just "trial" with the ability to monitor up to 7 devices.

I'm wondering if it might have something to do with the devices that doesn't disapear from "Host Detail", even if they have been deleted from the "Hosts" -list in Nagios Core Config Manager.

I'm really in doubt if Nagios is the right thing for a Linux-newbie like me. If you have to be a Linux-expert to fix problems like this, it might be difficult to get customers.

[ditlevw]

Oh.... I forgot to mension that, the installation is from a 32-bit VM-ware image.

[siju.doniston]

Hi

I am also facing this same issue.When i run the network scan ex 191.168.1.0/24 , it detect nothing
Any help would be appreciated.

thanks
Siju

[ditlevw]

...

I'm running Nagios XI 2011R1.5 on a virtual server in an ESX-environment. The license is just "trial" with the ability to monitor up to 7 devices.

I'm wondering if it might have something to do with the devices that doesn't disapear from "Host Detail", even if they have been deleted from the "Hosts" -list in Nagios Core Config Manager.

I'm really in doubt if Nagios is the right thing for a Linux-newbie like me. If you have to be a Linux-expert to fix problems like this, it might be difficult to get customers.

As for the devices that still appear in my "Host Detail", I can add that I currently have 6 hosts, according to the License Information.

[ditlevw]

Is everyone on vacation?

[lmiltchev]

Try to run fping manually, for example (plug in your IP/subnet):

# fping -a -A -d -g 191.168.1.0/24

[ditlevw]

Try to run fping manually, for example (plug in your IP/subnet):

# fping -a -A -d -g 191.168.1.0/24

Done. I got replys from the devices I expected.

Could it have something to do with what I mentioned earlier about the devices that doesn't disapear from "Host Detail", but are deleted from the "Hosts"-list in the Core Config Manager?

[ditlevw]

[nscott]

I'm currently doing some testing on this component/wizard. There was a bug in this component/wizard several weeks ago. There is phantom bug where the wheel will keep spinning and all you'll need to do is hit the refresh job list.

If you have some sort of IDS and packet sniffer that could be in issue as well, since fping and then the corresponding port check would definitely raise some IDS alarms.

[ditlevw]

I'm currently doing some testing on this component/wizard. There was a bug in this component/wizard several weeks ago. There is phantom bug where the wheel will keep spinning and all you'll need to do is hit the refresh job list.

If you have some sort of IDS and packet sniffer that could be in issue as well, since fping and then the corresponding port check would definitely raise some IDS alarms.

I don't have any IDS ...yet.