	        Internet Rover 3.0 Installation and Setup

 1.  Create the /etc/mib_desc file - copy the one in the distribution
     etc is needed. This file contains the mib description required
     for the fast snmp api routines.

 2.  Decide where you want your data directory (herein called
     $PINGKYDIR) and edit the Makefile for your configuration.  The data
     directory will hold all of the critical rover data files and can be
     placed on a NFS-mountable partition for easy multi-workstation
     access.

 3.  Assure that the bin directory in the rover package is in your path,
     OR you have a copy of mkdep in your path somewhere.

 4.  Type make clean depend all install  ( This has worked cleanly on
     our RS6K, Sun and Ultrix machines.  If you don't have the Motif
     libraries, then you will run into problems with the graphical
     display code.  In this case, you will need to muck with the
     makefiles to avoid the building the xmap application. )

 5.  Configure the $PINGKYDIR/hostfile with a list of hosts you wish
     to monitor and tests you wish to be performed on those hosts.

 6.  Make sure that the pingd program has the setuid bit on, and is
     owned by root.  One way to do this is to become root, and type make
     root-install which does all of the right things (copies the
     binary into the bin dir, sets permissions and ownership).

 7.  Type InetRoverd & pingd &   This will start up the InternetRover
     code along with the pingd which handles all PING() tests in the
     hostfile.

 8.  For the graphical displays, you will need to create a LINKS
     file.  The LINKS file describes the links in your network and which
     nodes and interface #'s are on either end of each link.  See the
     LINKS File Format section for details...

 9.  Create a Rover Daemon for your network - use the existing
     xxxxRoverd scripts as templates.  This script will invoke the
     xxxxpoller program which, using your LINKS file, will poll the
     interface status, assign the nodes and links a state, and finally
     store this information in network status file *xxxx.STATUS ).   You
     will also need to make a symbolic link (or copy the poller)  (
     Example: cp MeritRoverd xxxxRoverd; ln -s meritpoller xxxxpoller )

 10. Start up the xxxxRoverd.  ( xxxxRoverd & )

 11. Create a symlink for the graphical map, and bring up the
     graphical map by typing your network name xxxx.  ( ln -s xmap xxxx;
     xxxx & )  Note: You will need to bring up the graphical map twice
     before it will work ; bring up the map (it will be a small
     rectangular box with no nodes) and select the file menu bar and the
     quit option under that bar.   Bring up the map a second time, and
     the nodes should appear somewhere onthe screen.  You can move the
     nodes around as you like (we'll iscuss that later ).

 12. Probably the easiest way to proceed is to now make a copy of what I
     call an executaion environment script.  We have one for each
     network we manage.  See NSFNET, CICNET, MERIT, MICHNET for
     examples.  These scripts contain all the necessary commands and
     environmental variables necessary for end users to run the
     programs, including the resources!   This has been a pain in the
     past, because user's can unknowingly override the rover
     resources, so we created a executaion environment that prevents
     this.   ( cp NSFNET XXXX )

 13. Edit your execution environment script and try it out.  You will
     notice the reference to the $PINGKYDIR/XXXX.resources file.  
     This is where you define all of your menus, actions, bitmaps for
     nodes, background bitmaps, etc.  Again, peruse the examples.  
     You can do things like assign double mouse clicks on nodes to
     execute a particular script, a different script for tripple mouse
     clicks, a script for hitting the programmable function key 1 (PF1),
     shift-F1, etc.   Basically, you can assign arbitrary actions to
     X-events on your graphical map (that's why we call it a
     programmable graphical map!)

 14. Create additional useful scripts, assign them to menus or
     function keys, and tell folks on the rover-list@merit.edu about the
     cool new scripts/programs you have assigned to your map and make
     them available to your fellow network management chums.

