## $Header: /home/vikas/netmgt/nocol/src/perlnocol/RCS/README,v 1.3 1994/11/29 21:04:59 vikas Exp $
##
## Perlnocol README
#
## A few perl routines that can be used with Nocol.
#
armon		- appletalk route monitor (requires Cisco router & rcisco)
bgpmon		- check if any BGP peers down/idle on a cisco router
bpmon		- bootp monitor (requires bootpquery program)
hostmon		- client/server system for monitoring Unix system performance
mailmon		- monitor sendmail queue lengths
mkarmon		- program to build armon configuration lines
modemmon	- cisco terminal server modem line usage monitor
nocollib.pl	- perl library with nocol-oriented routines
novellmon	- IPX service monitor (requires Cisco router & rcisco)
nrmon		- Novell route monitor (like armon)
rcisco		- telnet to a Cisco and run a command (requires sockets.ph)
		  Alternately, you can use tcpf.c
snmpmon		- Monitor various SNMP variables from routers/RMON/etc.

For programs that log onto the cisco router and parse the output, you
need to code your router's  p a s s w o r d  in the 'rcisco' perl script
which introduces a security risk (this is for 'rcisco' to log into
your cisco). (An alternate to rcisco is the 'tcpf' C program).

Using the samples (mainly  armon/modemmon/novellmon) you can build
new monitors in Perl fairly easily. Your monitor just needs to call
the 'nocollib.pl'  module which has NOCOL utility routines.
Also see the man page for 'perlnocol'.

The original PERL interface to NOCOL was provided by John Wobus (9/21/93).


INSTALLATION
------------

1. Most monitors include 'nocollib.pl' so generic variables can be set
   in this file. The 'Makefile' edits the following variables automatically:
	$nocolroot  $NLOG_HOST

2. 'rcisco' (or 'tcpf') is required in the following monitors, so edit the
   location/path of this program in the following:
	armon bgpmon modemmon novellmon nrmon

3. The CMU 'snmpwalk' program and the MIB file is needed by the following
   monitors, so edit the location of these programs/files in the following:
	snmpmon-client

4. 'hostmon-client' needs to be installed on all your Unix systems that
   need to be monitored. Make sure you put the proper server hostname
   in the '@permithosts' array.


  armon:	This monitors AppleTalk routes from a cisco router.
		Can be changed to use CAP's atlook instead (see notes
		in the top of the file).

  bgpmon:	Checks cisco routers to see if the various BGP peers
		are in a connected state.

  bpmon:	Checks bootp daemon on various systems.

  hostmon:	For monitoring the health of your Unix systems (load, disks,
		memory, process tables, etc.) Consists of a client program
		that runs on all the remote machines and a server program
		'hostmon' that connects to the clients and gathers/processes
		data from the clients and writes into NOCOL.

		Edit the '@permithosts' line in the 'hostmon-client'
		program to control which hosts can have telnet access to
		the hostmon client data.

		Edit the 'ping' program location (preferably in nocollib.pl)
		and check the syntax in hostmon depending on your OS.

  mailmon:	Checks for clogged mail queues using 'mailq'.

  nrmon:	Monitors Novell routes from a cisco router (similar to
		armon).

  novellmon:	Monitors Novell *services* from a cisco router.

  modemmon:	Checks number of modem lines used on a cisco terminal server
		by doing a 'who' and counting number of users on tty
		lines.

  snmpmon:	Monitor SNMP stats on various devices such as:
		   RMON, terminal-server lines, traffic load, etc.
		The 'snmpmon' server program processes the data gathered
		by the 'snmpmon-client' program and puts it into the NOCOL
		format. The client requires the CMU-SNMP snmpwalk program 
		(supplied with NOCOL).


	-Vikas Aggarwal
	vikas@navya.com
	===============


