First you will need the iepm-bw source code. Typically this is obtained from SLAC by an email request to cottrell@slac.stanford.edu. He will tar up the entire v3src directory:
Code Block |
---|
>cd $bandsrc
45cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>tar -cvf v3src .tar47cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>gzip -c v3src.tar /tmp/v3src.tar.gzls -l /tmp/v356cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>ls -l /tmp/v3src.tar.gz
-rw-r--r-- 1 cottrell sf 125632972 May 17 12:34 /tmp/v3src.tar.gz57cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>rm v3src.tarcp /tmp/v358cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>mv /tmp/v3src.tar.gz ./59cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>ls -l v3src.tar.gz
-rw-r--r-- 1 cottrell sf 125632972 May 17 12:34 v3src.tar.gz60cottrell@pinger:/afs/slac/package/netmon/bandwidth-tests/v3src>cd /afs/slac/public/users/cottrell70cottrell@pinger:/afs/slac/public/users/cottrell>cp $bandsrc/v3src.tar.gz ./
|
This will require a lot of disk space (e.g. v3src.tar is ~ 180MBytes). It creates a file $bandsrc/v3src.tar.gz which is probably too big to email so it is made vailable by anonymous ftp. To access it use:
Wiki Markup |
---|
73cottrell@pinger:/afs/slac/public/users/cottrell>ftp ftp.slac.stanford.edu
Connected to ftp.slac.stanford.edu (134.79.18.30).
220-====================================================================
220-By using this system you expressly consent to the terms and
220-conditions in: http://www.slac.stanford.edu/comp/policy/use.html
220\-
220-Connection from pinger.slac.stanford.edu logged
220-====================================================================
220 FTP server ready.
Name (ftp.slac.stanford.edu:cottrell): anonymous
331 Anonymous login ok, send your complete email address as your password.
Password:
230-====================================================================
230\-
230-Stanford Linear Accelerator Center Anonymous FTP Server
230\-
230-====================================================================
230\-
230-This server is for anonymous read access to public information
230-made available at SLAC, and provides an anonymous incoming 'drop
230-box' directory for files that is readable only by individuals
230-who have SLAC accounts. If you are looking for the SLAC anonymous
230-ftp server for the dissemination of experimental data, the server
230-name is ftp-\[experiment\].slac.stanford.edu (where \[experiment\] is
230-currently glast, babar, iepm, lcd, e162, and e157).
230\-
230-All incoming files should be placed in the incoming directory.
230-Files placed in the incoming directory may not be read back via
230-anonymous ftp.
230\-
230-Any questions about this service should be sent via email to
230-unix-admin@slac.stanford.edu
230\-
230-====================================================================
230-Anonymous access granted, restrictions apply.
230-Please read the file README
230- it was last modified on Tue Nov 26 18:12:42 2002 - 1632 days ago
230-Please read the file README.LC02
230- it was last modified on Mon Jan 28 14:48:21 2002 - 1935 days ago
230-Please read the file README.incoming
230- it was last modified on Thu Nov 14 11:38:30 2002 - 1645 days ago
230-Please read the file README.outgoing
230- it was last modified on Mon Mar 10 12:52:44 2003 - 1529 days ago
230-Please read the file README.tip_inbox
230 it was last modified on Fri Jul 6 15:09:28 2001 - 2141 days ago
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd users/cottrell
250 CWD command successful
ftp> ls
227 Entering Passive Mode (134,79,18,30,187,254).
150 Opening ASCII mode data connection for file list
dr-xr-xr-x 2 ftp ftp 4096 May 17 19:45 .
dr-xr-xr-x 2 ftp ftp 4096 May 14 18:21 ..
\-r--r--r-- 1 ftp ftp 335 Oct 5 2001 identity.pub
\-r--r--r-- 1 ftp ftp 304 Feb 9 1996 pgp.publickey
\-r--r--r-- 1 ftp ftp 125632972 May 17 19:45 v3src.tar.gz
226 Transfer complete.
ftp> binary
200 Type set to I
ftp> |
You will need to unzip and detar the file using: tar -xzvf v3src.tar.gz
Log onto the monitoring host node under the 'iepm' account.
...
- 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
, andowampd.keys
are configuration files for owamp.owampd.limits
andowampd.keys
should be ok. Look atowampd.conf.template
.datadir
andvardir
are defined to be/home/iepm/owamp/data
and/home/iepm/owamp/run
respectively. If this is ok (recommended default), saveowampd.conf.template
asowampd.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 bykeep-servers-alive
to start, and if necessary, restart the servers. For a standard monitoring host, this file should be: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' inhome/iepm/iepmtools
to/home/iepm
and execute it. - Configure Geoplot.
http://www.slac.stanford.edu/comp/net/bw-html/v3plm.html#geoplot
- Now assuming that database tables are loaded, run the various reports for them.
report-nodes
should be run first. IfMONHOST
is not set up correctly, none of the reports will run. You must fixMONHOST
first. - Other reports to run are:
Code Block report-monhost report-nodegroups report-nodespecs report-plotspecs report-table-structure report-toolspecs
- 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 data loading scripts called by
load-datad
. These include:
If all of the above tests work, and the data base is loaded with all probes, nodes, plotspecs, etc. then you can load the crontab. Crontab files are located in v3src/crontabs. You should use the one with nameCode Block load-ping-data load-trace-data load-iperf-data load-tlayctp-data load-trace-data load-pathchirp-data load-pathload-data
crontab.iepm
.
crontab -l will give you the listing of cronjobs for the logged in account.Code Block Crontab -u username crontab.iepmbw
This should start the system up. If there are problems, be sure to check the/home/iepm/mysql/logs
directory for the output from the cronjobs.