Page 1 of 1

Auto Discovery - all port ranges not discovered

Posted: Mon Aug 21, 2017 10:16 pm
by jonny@jdtay
Hiya,

Subject is partly self explanatory :).

I'm trialling Nagios XI in the 60 day trial period, alot of the virtual machines that we're running are running in excess of 500+ ports all in private\dynamic ranges that I'd rather not have to define manually, one by one. The Auto-Discovery tool isn't finding the port ranges when I use the 'All' drop down for Default Services.

I've found documentation on the CCM tool and how you can explicitly define each of the ports that are monitored but, this is a little more painful than I'd like.

Is it possible to instead change the port ranges that the Auto-Discovery tool scans using NMAP so I can include ranges of ports instead?

1) Running CentOS6 (installed from the Nagios OVA)
2) 64 bit
3) VMware Image
4) No special configs at the moment, almost stock install beside using a proxy for HTTP connections (including WGET and YUM)

5) No installation issues, just config and reporting.

Thanks :)

JT

Re: Auto Discovery - all port ranges not discovered

Posted: Tue Aug 22, 2017 1:21 pm
by scottwilkerson
This is currently not available as the Auto Discovery uses the -F (fast mode) of nmap to operate.

That said, I agree that this would be an excellent addition and am submitting a feature request for the development team to add this in the future.

Re: Auto Discovery - all port ranges not discovered

Posted: Tue Aug 29, 2017 11:54 pm
by JDTAY
It's reasons like this that give me faith that building my business case to drop my Network monitoring appliance in favour of Nagios XI when my trial expires.

This all makes it all the easier for me to develop my business case to implement Nagios over PAServMon. Thank you!

Re: Auto Discovery - all port ranges not discovered

Posted: Wed Aug 30, 2017 8:50 am
by scottwilkerson
JDTAY wrote:It's reasons like this that give me faith that building my business case to drop my Network monitoring appliance in favour of Nagios XI when my trial expires.

This all makes it all the easier for me to develop my business case to implement Nagios over PAServMon. Thank you!
Thank you JT for laying out a good use case.

I don't want to give the illusion that every feature request gets implemented, but if a solid use case is presented, that our team can see could be used by many people, they usually get added in time.