Passive checks - assistance required...

[David Jacobson]

Hi There,

I have been playing with NC_Net for 3 weeks now, I’ve managed to get some of the basic passive checks working, but have two questions if you don’t mind:

1. For checks like “cputotal” I’d like to change the service name to CPU – If I make the change it appears not to return the result back, is it possible to change the name of passive service checks? 
2. I’m finding it quite hard to understand how to execute a custom batch/exe file and submit back passively? Client has a lot of unique monitoring requirements, that aren’t in your usual cpu/mem/service checks. 
3. How can I setup ICMP to be sent passively (to check host up/down?) 
4. If a passive check fails, will it keep sending forever? In Nagios we specify max_check_attempts to say 3, I just need to understand where that is set in the passive.cfg or if it just keeps sending the error.

Many thanks in advance.

-- 
Regards,

David Jacobson
Technical Director
SYNAQ (Pty) Ltd

[tony]

I already resonded to this via Direct Email, However here is a summary of the answer for Forum viewers:

1) the Passive.cfg commands are TAB delimited.  the service names are changeable but if you use spaces instead of TABS the command would fail.  Also some text editores are configured to replace Tabs with Spaces and this could induce an issue well. 
2) using runscripts - put an executable into the scripts folder of NC_NET.  then run call it using the runscripts command
./check_nc_net -v RUNSCRIPT -l "test.exe"
There are different options to this command ssee the help for more details
./check_nc_net --help=RUNSCRIPT
3)NC_NEt can send Passice Host Checks via NSCA, ICMP is a protocal that is independent of NC_NET.  but to configure  passive Host checks this is only done via the Startup.cfg located in the config directory of the install path of NC_NEt.(NOT THE START MENU that is only a copy of the original)
4)The startup config for NC_NET v4.1a has been greatly enhanced and restuctured with new comments and some new parameters that were not in prior versions to NC_NET.  make sure to read through it, for configuring NC_NET.  as stated in the startup.cfg the passice_alwayson parameter when false - passive checks will terminate if it gets a Failure during sending.  it can be restarted via a CONFIG command.   When True the passive checks still try to send once each passive interval.  however it will first rerun all the passive checks. Also on a side note, Passive checks can be configured to be sent to two different NSCA hosts each interval by configuring both the Internal and external sendNSCA. 

TOny
Please remember Donations are accepted and Appriciated via www.montitech.com

[David Jacobson]

Hi Tony,

Thank you very much for the info - just to let you know if I had downloaded the latest version from
Sourceforge none of these questions would have been asked.

I googled NC_Net - First link says "Official Site" (www.shatterit.com/NC_Net/) and I got it from there.

After using the latest version everything was easier to setup and better documented, maybe you should update
the site?

Thank you for your time.

We will continue to use this plugin for our client and if all goes well we should be placing a donation in
the next few months.

Regards,
David

[tony]

Good to hear,

Unfortunatly I am not on speaking terms with ShatterIT, who is hosting the Outdated NC_NEt site.  But hopefully others will hit them with messages about this.

Thanks.

Tony