NC_Net Official Site

NC_Net is a windows service that is also a drop in replacement program for NS_Client.
NC_Net has been designed to take the same inputs and produce the same outputs as NS_Client
from the Nagios check_nt plugin.http://www.nagios.org/
For NC_Net Support Contact us at: mailto:amontibello@shatterit.com?subject=NC_Net
or feel free to post into the Nagios mail lists.

Current install package - NC_Net_setup.msi NC_Net 2.28 07/16/05

All most updated Documentation can be accessed at this link NC_Net other files use this link to download the newest documentation without reinstalling NC_Net
Older versions of NC_Net are saved as zip files here. Just change the extension back to zip or open with a tool like WinZip.

NEW

Please remember to notify us of unexpected errors that way we can validate if NC_Net needs to be updated with a fix or workaround.
Feel free to notify us about modification to Documentation or Suggestions for NC_Net

NC_Net 2.26 04/19/05 -

Added 04/19/05 -- Removed \\ from output of UsedDiskSpace due to some compatibility issues reported by users

Added 04/19/05 -- BUG FIX -- MODIFIED WMI checks to use ^ as delimiter instead of ;

For a list of older enhancements view history.htm

NC_Net is currently still under development,
- It currently implements ALL checks that NS_Client implements as well as passive checks.
- NC_Net has been tested on:
--Windows XP Professional SP2
--Windows Server 2003 Enterprise
--Windows 2000 Server SP4
--Windows 2000 Professional SP4

Enhancements

Documentation has been rewritten. (Feb 2005)

ENUMCONFIG command prints out NC_Net's current configuration. (One parameter per line)

Event Log Checking - now can use -w and -c. these are compared to the number of entries found.
New lines removed from Event log and WMICHECK.

Can now install NC_Net into any directory during the install.

Backup copies of installed configuration files are in the start menu folder of NC_Net.

CONFIG command can be used to send a configuration change dynamically to NC_Net.
Passive and active checks can now be started dynamically without restarting of NC_Net service. Passive checks are now implemented.
Event Log Checking - check For any event log entry in any windows Event log (including Custom logs).(uses Reg Exp for message checks)
WMI Query - Responds with the string result of the query or an error. (Results truncate on endofbuffer)
Service State - can use both Descriptive names (From Service Manager) and internal names (from Registry).
Instance - will return a list of instances for a performance counter, accepts multiple instances.

Downloads and links

Current install package - NC_Net_setup.msi NC_Net 2.28 07/16/05
Check_nt source with NC_Net enhancements (modified from official plug-ins v1.4Beta1 Jan 2005) check_nt.c
Passive Check Configuration- Passive Checks Simplified.htm
Older versions of NC_Net -(WinZip Format) Older Versions
Current Documentation - readme.html
TO DO List - todo.txt
Version History - version.txt
Source to extra tools programs - Tools Source Zip
Zip of just the extra tools - Tools only Zip

Installing - NC_Net_setup.msi NC_Net 2.28 07/16/05 With Passive checks

NC_Net re-install Overview
a) Uninstall older version first (If problems see uninstall.txt)
b) Install new version by opening the .msi program.
c) Open Services Console in windows and Start The NC_Net Service.
Make sure no other programs like NS_Client are running on same port first.
Currently a Reboot is NOT required to install and run NC_Net.

Install Process
Preparing for install:
Make sure to uninstall existing copies of NC_Net.
This is done through Control Panel -> Add or Remove Programs.
If uninstall fails review Manual Uninstall txt

Install Process:
Download the install package, then run it.

Post Install:
Make sure to turn off NS_Client before starting NC_Net.
(This is because by default they will try to use the same port.)
You may also want to change the properties of NS_Client to Startup Type: Manual
Do not configure both NS_Client and NC_Net Startup Types set to Automatic.
Turn on the NC_Net Windows Service.
Start sending active checks to the server via check_nt.

Install Details:
The install package will copy all files and documentation to:
[Program files]/shatter it/NC_Net/
It will also setup some start menu links.
Some of the utility programs created to test NC_Net can be accessed through the start menu.

Uninstall:
Remove NC_Net by choosing remove from: Control Panel -> Add or Remove Programs.

Contact Us

http://www.shatterit.com/
NC_Net Programmer: mailto:amontibello@shatterit.com?subject=NC_Net

Memory usage of NC_Net

Memory usage is very dynamically dependent on what checks are being done, the frequency of the checks as well as the details of the Host machine.  NC_Net has been designed to dynamically poll resources via the Dot Net Framework.  When doing this some of the data may be large, for example the event logs checks.  A second example is doing a general WMI query. 

Memory usage typically starts out a bit larger than the steady state after the service has been running for a few days.  This is not easily controllable.  The Dot Net framework is similar to Java in that it does run a virtual Machine called CRL in DOT Net.  NC_Net does use explicit calls to Garbage collection to try and assist in freeing memory.  However there is no inline assembly.

Memory usage during initial configuration will always be higher than typical due to error handling code and extra processing on some checks to validate the non-ok results.

Memory usage is typically about 5-9 Megs when using Active checks only. (About 7 checks - disks, CPU, Memory, Processes and Service States ).

Memory usage is typically about 12-19 Megs when running both Active checks and Passive checks.  (One test server is running at 13 Megs running 15 assorted service checks)

Memory Usage on one test server was about 15Megs for active check enabled (not used but running) and 35 passive checks run each minute. (at least one of each type)

Technical Notes

(This section needs updating 1/20/05) See readme.html for updated information.
NC_Net was developed in C# using the Dot Net Framework.
Framework References - usage:
System.Managment - Access to WMI for USEDDISKSPACE check and Process State Check.
System.ServiceProces - Access to Services for adding itself, and for running SERVICESTATE checks.
System.Diagnostics - Access to Performance Counters, Processes, and event Viewer.
System.Configuration.Install - Access to installer Class for installation as a service.

The uninstall process leaves the C# source code in the Start menu. This was done on purpose. Currently the only release of the source code is through the installation process. After uninstalling NC_Net, Delete the NC_Net folder in the start menu if you no longer want a copy of the source code.

NC_Net is designed to work with check_nt plug-in. The tool 'NS_Client Test Console' bug has been fixed and it has been expanded to be able to test remote NC_Net or NS_Client instead of just the local host.