...
- Enter the node into the 'NODES' data base.
- Enter the node into the 'MONHOST' data base.
- On iepm-bw.slac.stanford.edu, make a tar file including all the code.
Code Block cd /afs/slac/package/netmon/bandwidth-tests/v3src tar -cvf dist.tar -T dist.scripts.list scp dist.tar iepm@<fully qualified monitoring host name>:/home/iepm/dist.tar
- Log onto the new monitoring host node under the 'iepm' account.
- Execute the following to install the source code
Code Block mkdir v3src cd v3src tar -xvf ../dist.tar
- Now configure the 'config' directory. The following files may need configuration:
- The 'config' directory contains a sample .cshrc. Modify this to match the node being installed and copy it to '/home/iepm/.cshrc'. This will defined where java is located, and two environment variables "$bandsrc" which points to the v3src directory and "$banddata" which points to the directory where the data and reports are stored. Note that there is a link from '/var/www/html' to this directory.
- 'cleanup-list' - should be configured correctly. If there are processes which are known to hang, they should go in this file. 'bw-cleanup' uses this file to clean processes known to hang (now or in the past). If the process with the name in this list exists longer than the number of minutes indicated on its line, it will be killed.
An example is: Code Block # cleanup process list # Connie Logg 5/18/06 cal@slac.stanford.edu post-test,120 gnuplot,5 triganal,120 runperiod,120 pathload_rcv,3 pathchirp_rcv,3 /bin/ping,3 /bin/owping,3 /bin/iperf,3 /bin/tlaytcp,3 /bin/bw-iperf-client,3
- 'owampd.conf.template', 'owampd.limits', and 'owampd.keys' are configuration files for owamp. 'owampd.limits' and 'owampd.keys' should be ok. Look at owampd.conf.template. 'datadir' and 'vardir' are defined to be '/home/iepm/owamp/data' and '/home/iepm/owamp/run' respectively. If this is ok (recommended default), save 'owampd.conf.template' as 'owampd.conf'. Then create the directories:
Code Block mkdir /home/iepm/owamp mkdir /home/iepm/owamp/data mkdir /home/iepm/owamp/run
- 'servers.alive' may need to be configured. This is the file that has the information for starting the servers. It is used by 'keep-servers-alive' to start, and if necessary, restart the servers. For a standard monitoring host, this file should be:
The first field is the name of the script. The second field is the directory in $iepmSrcDir where the script resides. The third is a list of parameters to start it with.Code Block bw-iperf-server,bin,-s -p 5000 -w 20M thrulayd,bin, pathload_snd,bin, -q -i map-updated,, pathchirp_snd,bin, owampd,bin, -c /home/iepm/v3src/config -Z >& /tmp/owampd.log &
- Make copies of /etc/my.cnf and /etc/iepm.cnf in the config directory. They are used to provide configuration information to the CGI scripts.
Code Block cp /etc/my.cnf /home/iepm/v3src/config cp /etc/iepm.cnf /home/iepm/v3src.config/iepm.cnf.<aliasname>
- Install JAVA, if required. If it must be installed, the recommended installation directory is '/home/iepm'. To install it, copy the 'JDK...bin' in 'home/iepm/iepmtools' to '/home/iepm' and execute it.
- Configure Geoplot.
- Load the NODES and NODESPECS tables, MONHOST table, TOOLSPECS table, PLOTSPECS table, and ther GROUPS and NODEGROUPS tables if you want to use their functionality.
- Once the tables are loaded, run the various reports for them. 'report-nodes' should be run first. If MONHOST is not set up correctly, none of the reports will run. You must fix MONHOST first.
- Once all the reports run, you are ready to try the probes. 'schedule-load' will force the probes to be scheduled and run. Look in $mysqldb/data and check the data files that are output from the probes running. If they look ok, you can execute the various 'load-<type>data' scripts to load them into the data base. Do not start 'load-datad' until you have verified that the individual 'load<type>-data' scripts are working correctly. The biggest issue here is making sure MySQL is properly configured.