The TOOLSPECStable contains the specifications for each and every probe for each and every target node. Many of the specifications are identical, however because some can be different depending upon the characteristics of the network connecting to the target node, each node must have its own specifications.
The following is a template for a csv file for entering the toolspecs. Note that any probe can be commented out by starting the line with 2 '#' signs ("##"). the field specifier line must all be contained on one line, as must each of the probe specifications. They are split up over multiple lines to make the example fit in the space below.
TABLENAME=TOOLSPECS ## the following 2 lines must be on one #srcNodeID,destNodeID,toolName,toolPath,toolDo,testtype,toolOpts1,toolOpts2,toolopts3, time2run,runinterval,daystoanalyze,datatoanalyze ##insert the srcnodeid and destnodeid in the first two columns # again, each probe specification must be on one line ##iperf example 113,5,iperf,/home/iepm/v3src/bin/iperf,1,background-syn,-p 5000 -t 20 -w 20M,,, 30,600,28,iperf:iperf=w p lt 6 pt 6 # miperf - multistream iperf example 113,5,miperf,/home/iepm/v3src/bin/miperf,1,background-syn,-p 5000 -P 8 -t 20 -w 2M,,, 30,600,28,miperf:miperf=w p lt 6 pt 6;miperf:thrumin=w p lt 5 pt 1;miperf:thruavg=w p lt 7 pt 1;miperf:thrumax=w p lt 3 pt 1 113,5,traceroute,/usr/sbin/traceroute,1,background,-q 1 \-w 2,,,15,600,28,traceroute:numhops=w p lt 6 pt 6 113,5,ping,/bin/ping,1,background,-s 1000 \-c 10 \-w 20,,,15,600,28,ping:max=w p lt 7 pt 5;ping:avg=w p lt 2 pt 5;ping:m in=w p lt 3 pt 113,5,pathchirp,/home/iepm/v3src/bin/pathchirp_rcv,1,background,-t 10 \-J 6 \-a 2 \-l 100 \-u 10000,,,45,1800,28,pathchirp :pathchirp=w p lt 6 pt 6;pathchirp:thrumin=w p lt 5 pt 1;pathchirp:thruavg=w p lt 7 pt 1;pathchirp:thrumax=w p lt 3 pt 1 113,5,pathload,/home/iepm/v3src/bin/pathload_rcv,1,background-syn,-t 90,,,45,1800,28,pathchirp:pathchirp=w p lt 6 pt 6 ;pathchirp:thrumin=w p lt 5 pt 1;pathchirp:thruavg=w p lt 7 pt 1;pathchirp:thrumax=w p lt 3 pt 1