Make your own free website on
Fast Links

Summary of features

Detailed description


Sample screens

Change log


Todo List

Mailing List


Site map

Admin Guide


Man pages




Mirror Sites


Tripod UK

Lineone UK

Main bcnu site

Hosted by

Updated: 9th November 1999
Version 1.22

Summary of Features

bcnu is a web based system management tool which delivers information on the status of networked systems in a simple and easy to use manner. Have a look at the sample screens to see how easy it is. It uses a web browser to display information about hosts in a tabular form. Coloured icons show the status of monitored conditions and clicking on these will bring up detail about the state of the system. Historical information can be held indefinitely and there is a powerful query tool available to interrogate it. More details can be found here.

bcnu can be managed from a central unix system, with all agents, scripts and config files distributed from one point using the supplied shell scripts. It will soon be possible to configure agents from a web browser.

bcnu has a very open architecture. The agents are currently bourne shell scripts, but can be any program. There are a set of standard shell functions available to make interfacing with bcnu very easy. It is a simple matter to modify existing scripts to talk to bcnu. These will have all the benefits of bcnu agents, e.g. logging, resending, proxy etc. I would be happy to receive your agents to include with the distribution

bcnu has been designed to be very simple to implement. By default it is configured to make very little impact on the managed system. Logging levels can be set for each agent separately. It is possible to set an agent only to log in the event of an error.

Monitoring of network devices can be spread over multiple machines, all may have different checking and logging intervals. e.g. you may wish to check all web servers every 5 minutes, application servers every 10 minutes, but mail or print servers only every 30 minutes. This is easy with bcnu due to the flexible agent architecture.

Its main features:

  • easy to use
  • simple agent based monitoring with flexible thresholds
  • multiple views of the same information
  • includes agent scheduler for total flexibility
  • automatic logging and resend of messages
  • discover agent to build a picture of your system automatically
  • built in web server for static pages
  • powerful cgi access to data including multiple views and historical queries
  • free!! (Distributed under the terms of the Artistic licence)
Standard agents include:
  • network monitor, ping, http, ftp , mail, lpd, oracle etc
  • intelligent log file scanning for messages and warnings
  • checking for required processes to be running
  • filesystem mount status and space usage
  • processor/memory usage and system up time
Special agents include:
  • volume management checks for solaris,aix and hpux
  • system availibility
Admin agents include:
  • logging and resending of agent data
  • agent proxy
  • alerts sent by mail, pager, win32popup, web, Perl/TK window or custom program
  • report of all errors and warnings
  • self monitoring and alerting agent (runs on another system)
  • discovery of systems to be managed
  • optional static web page built to show status of all systems
Contributed agents include:
  • Critical file checker - checks to see if important files have been changed
  • oracle table space monitor
  • check oracle backup log agent
bcnu is a system which I developed for a number of different reasons. I manage a large number of different unix systems and had been investigating systems management tools. It appeared to me that most tools fell into two different categories:

  • Network management tools which covered some unix management issues, but were mainly designed to provide a graphical network view of network objects.
  • in depth system management tools which forced a change in the way systems were run and were difficult to set up and use.

Both types of system were expensive to set up in financial and training/maintenance costs.

I then came across the Big Brother network monitor by Sean Hughes - which inspired me to write bcnu. Big Brother is a simple web based monitoring package which uses shell scripts and a couple of c programs to provide basic management facilities.

The only problem I had with BB is that it is a bit complicated to install and maintain, and there is no real control over the scheduling of agents.

I also came across spong by Ed Hill, which was an execellent tool, but again still a bit inflexible and required perl5 on all systems.

I hope bcnu addresses all of the above issues.

bcnu is designed to run as a client on any unix system. The master requires perl and a web server for the full functionailty, but the alert mechanism will work without these.

The prebuilt binaries allow bcnu to be deployed within minutes, with only the agent thresholds to be configured.
What is bcnu?
bcnu is a client-server monitoring system. It consists of a server daemon running on each system to be managed. The daemon schedules the running of agents on the system. The agents can be used to check the health of the system or to run periodic bcnu admin tasks.

One central system is designated as the "master". This is where all data is logged to and where remote management can be carried out from.

A web browser is used to display the status of the systems under its control.

bcnu's main features are:

  • web browser based monitoring
  • multiple views of systems supported
  • easy to understand configuration file
  • cgi not required for basic monitoring
  • simple web server for static pages built into daemon
  • remote management of bcnu agents
  • separate agents for different functions
  • allows scheduling/enabling/disabling of each agent independently
  • each agent is completely configurable
  • proxy data gathering
  • discovery agent to find systems automatically
  • powerful queries on current or historical data
  • blackout mode for switching off agent activity
  • automatic logging and resending of agent information
  • alerts by mail,pager,web or custom program
  • files may be attached to agent data
  • historical data kept
  • flat file or mysql database support for data
  • runs on many unix platforms, prebuilt binaries available
  • free!!
What do I need to run it?
In addition to Unix systems, any IP connected device can be monitored by bcnu i.e routers, Netware/NT servers, gateways etc. It will use a ping to test whether the system is alive or not.

It is also possible to check for IP services on any system, i.e. ftp, http etc

To check other internal services on Unix systems requires a bcnu daemon and agents to be loaded.

Currently the supported Unix platforms for the daemon are:

  • Solaris 2
  • HPUX 9,10
  • AIX 4
  • Linux 1 and 2
  • FreeBSD 3
  • ICL DRS NX (deprecated)

As these are the only systems I have access to, these are the only ones I can test on, but I am hoping that others will contribute ports to other systems.

The software is distributed in source and with pre-built executables for the above platforms.

A C compiler will be required (gcc is fine) to rebuild.

For managed systems, that is all that is required as all the agents are bourne shell scripts and don't do anything very complicated.

For the master system perl is required to build the web pages. Perl 4 is fine.( but see below)

Currently a web server is required for the cgi scripts where these are used. I use Apache.

The web browser should preferably be Explorer 3+ or Navigator 3+, but it will still work on older browsers. The use of background colours in tables makes these browsers better.

(Optional) Kermit 6 is required for pager support.

(Optional) If you are using the Perl/TK alert script then Perl5 and the TK module is required.
Download bcnu 1.22 for Unix
You can download the full bcnu distribution here (625942 bytes). The package contains all source and binaries for bcnu version 1.22.
Binaries are for: solaris(sparc), hpux, aix, freebsd, drsnx, linux(Redhat 5.2)

The source only distribution is here (424822 bytes). This should build on a lot of Unix platforms, although it has only been tested on those listed above.

These distributions are gzipped tar archives.

Html, text and some pod and man documentation is also provided in the package.

Download BETA snapshot of bcnu 1.23 for Unix
If you like excitement and don't expect things to work first time every time, you can download the source only bcnu distribution here ( bytes). The package contains source only - no binaries, all the latest agents, scripts etc which are in development. It will be pretty stable - but no guarantees (are there ever any?)

The documentation will not be updated until the full release - so use the mailing list if you need any assistance

Quick Install of bcnu for Unix
To install the package for the impatient:

cd /usr/local (preferred location)
gzip -dc bcnu-1.22.tgz | tar xvf -
cd /usr/local/bcnu
/usr/local/bcnu/etc/bcnud_server start

This will start a basic bcnu configuration on this system. See the README document and the admin guide for further instructions.

Feedback welcome!

Download/Install win32 bcnualert program
You can download the latest version (1.12) of the win32 alert program here

This has been tested on Windows 95, but should work on any win32 system

Because of the size of some of the Microsoft system files, I've split it into two packages. If you don't have the files mscomctl.ocx and msvbvm60.dll installed already then you need to download them here (1201552 bytes) or from any windows driver site and place the files in your windows system directory.

If you already have those files then you only need the setup package for bcnualert 1.12 (516517 bytes)

To install this, you just need to unpack it and run the setup program. When you run it for the first time, it will pop up a settings page which will ask for:

  • master host name - the pc registers itself with the master host
  • bcnu port number - port number of bcnud, normally 6666
  • check interval - how often the pc will check that the master is still alive
  • This PC's id - How this pc is identified (should be valid unix filename format)
The settings will be saved to the registry and bcnualert will then wait for any alerts to be sent to it and checking that all is well with the master host. See the sample pages for an example of the program in use.
Sample pages

These pages are designed to show how the web monitoring pages of bcnu look.

The pages which are displayed have been generated from a live system but the data has been changed to show examples of bcnu output.

The pages here show a variety of systems from full unix servers with all agents, nt servers with web/ftp services, win9n pc's acting as alert agents and routers. We also monitor a host on the internet to check our connection with the outside world is ok

There is also a non-working example of the query page which is available when using the perl cgi scripts

It is possible to drill down within each page and get more detail where available by clicking on the hyperlinks. Although there is a login button, this is disabled as the features provided are only available using the cgi scripts.

  • Show the summary status of all the systems being monitored
  • Show only abnormal conditions for all systems
  • Show hosts split into platforms for all systems
  • Non-working example of the query selection screen available using cgi and the history files

The dynamic cgi pages look the same except that there are some very important extra options:

  • the query tool allows searching all of the data files which are available.
  • a history of unacknowledged alerts is shown to ensure that you don't miss any
  • You can only ignore hosts(switch off alerts) by logging in
Win32 Alerts

Here is a sample of the win32 alert program showing some alerts, please imagine that you can hear a siren or some other sound file while looking at this to get the full effect!



Version 1.23 - (Under development - BETA version not available from downloads yet)

  • Logs agent allows actions (Wulf Dietrich)

Version 1.22 - 8/4/2000

  • New win32 alert program - send alerts to a windows PC, popup a window and sound alarm (separate download)
  • Changes to bcnud, alert agent and hostinfo to support win32alerts
  • Improved vmgt, fs and procs agents from Wulf Dietrich
  • Improved client_install script to better handle SUSE Linux and AIX from Wulf Dietrich
  • Improved bcnud_server startup/shutdown
  • Fixed bugs in client_install
  • Fixed problem with empty agent fields
  • Contributed key.cgi to display key in browser and various minor fixes and enhancements from Charles Howes
  • Contributed agents for mailq checking and running commands from Wulf Dietrich
  • More customization possible thru bcnulocal script
  • Javascript countdown clock/refresh - Charles Howes
  • C Sources tidied up by Kevin Koch
  • Makefile is now more intelligent
  • Bug in Linux ping identified - version of ping from Redhat 5.2 is OK, or alternative perl version is supplied in the distribution

Version 1.21 - 6/3/2000

  • NEW web based acknowledgement of errors - alerts will stay on screen until they are acknowledged even if the condition clears itself
  • NEW cookie controlled login controls access to admin functions
  • NEW fix_perms script to fix bcnu permissions
  • NEW linux support for LVM added to vmgt - Thanks to Volker Pense
  • Updated cgi scripts to log acknowledgement/ignores
  • Setup script will generate sample alerts on master
  • Fixed bug in proxy - not setting hosttype
  • Fixed bug on HPUX - PATH not set properly on reboot
  • Fixed bug where bcnud_server sometimes hangs when started via rsh
  • Fixed bug SHELL not recognized! on Linux
  • Fixed problem with web access to index.htm, create symbolic link to index.html
I've had quite a few bug fixes and suggestions from Wulf Dietrich, thanks to him for all of these
  • NEW customized log agent
  • Improved logs agent
  • NEW Oracle table space monitor
  • Updated debugging options and error handling in agent_head
  • Fixed bug in AIX errpt logs agent
  • Fixed bug in ALTHOST handling
  • Restart option for bcnud_server
  • Limit on number of alerts per host per day

Version 1.20 - 18/1/2000

This release has a new setup script to make it much easier to install bcnu for the first time. It will prompt for all of the important settings and hopefully leave you with a working configuration which can be tested immediately.
  • NEW agent to check oracle database availability
  • NEW agent to check files for changes - contributed by Doug Bakewell
  • Added an option to specify different local hostname in bcnulocal
  • Added some support scripts to set perl location, and fix sound on linux
  • Added system type of APPLIANCE for web cameras etc
  • Improved error logging for agents to help in debugging
  • Fixed a problem in the proxy function of the alert agent
  • Fixed a problem in bcnuinfo to show all email alert recipients
  • Fixed a problem with spurious quotes in Slackware - Thanks Scott
  • Fixed a problem with linux startup scripts not being set correctly
  • Fixed a problem with the fs script not displaying disk space correctly

Version 1.19 - 15/12/99

  • Added AIX errpt checking to log agent
  • Added -ad flags to buildweb in alert agent
  • Changed default action for bcnud. It will now only log the hostname of incoming reports and not the full domain name. An option (-q) has been added to bcnud to log the FQDN if required.
  • Added new option on browser to show hosts sorted by platforms, also added the platform to the agent details screen.

Version 1.18 - 18/11/1999

  • Fixed problems with bcnu sending too many fields with a message
  • Added code to decode messages on agent details screen
  • Added code to send host type for all agents
  • Fixed some per host settings, all local variables now configured via bcnulocal
  • Fixed a bug with the query cgi form not highlighting default log
  • Fixed a bug in bcnuenv.linux - no MAIL defined - Thanks Christoph
  • Fixed the install and upgrade scripts, they now retain all previous data, logs and config info when upgrading. Auto upgrade now works much better
  • BCNUHOME wasn't set in bcnud_server, oversight from previous change

Version 1.17a - 21/10/1999

  • Fixed problems with install script not setting up defaults correctly

Version 1.17 - 15/10/1999

  • Fixed y2k compliance code, and tested with dates set to 2000+
  • Fixed a bug with service number handling in bcnu.c causes the http test to fail on linux/freebsd

Version 1.16 - 10/9/1999

  • Updated log.c to add support for ignoring individual agents
  • Added freebsd 3.3 support and fixed a bug with CHILD processes
  • Modified Web graphics
  • Added snmp trap logfile capture script (UCD snmp)

You can email me at or subscribe to the low volume mailing list
© 1999,2000 John Phillips All rights reserved

Site Stats

Translate this page from  
powered by SYSTRAN Translation Software