GMT
(Amsterdam time -1 in the winter, -2 in the
summer)ttdell
"Limited
"Disabled
"Disabled
" (to have a more consistent memory check. Feel
free to enable this during setup phase)Enabled
"COM2
"9600
"CTS/RTS
" (set by default)
Read the "BOOT IMAGES NOTE" below. Boot the TB using the install floppy. If you don't have it, the latest image is in
/ncc/ttpro/files/install_floppies/ttminstall.bin
and you can create the boot floppy being root
on a unix
pc with a floppy drive (e.g. oudzuid) and using either
"dd if=ttminstall.bin of=/dev/fd0
"
or
"cat filename > /dev/fd0
"
After booting, answer the questions asked:
193.0.4.22: tt-install.ripe.net
193.0.4.23: tt-install2.ripe.net
193.0.4.24: tt-install3.ripe.net
fxp0
" (for Dell boxes, if not already
set- it is the default anymore CO)BOOT IMAGES NOTE: There are two boot images.
One is the
ttminstall-host.bin
which is just in the ftp site directoryncc/ttftp/tb-image/ttminstall-host.bin
and the internal one
ttminstall.bin
which is in/ncc/ttpro/files/install_floppies
.The only difference is that the latter spawns a shell after boot, the first one does not (because we do not want a host to have
root
access to a test-box, either when in "recovery" mode)
Clean up the e-mail you got the application form in and save it to
/ncc/ttpro/application_forms/
with the corresponding testbox name (e.g. tt75). Do not over clean. Keep the original e-mail header as it shows the submission date of the form. Nothing relies on this file anymore. It is kept for purely archival purposes.
At a linux box as ttraffic
execute:
/ncc/ttpro/bin/app2ttreg (application_form_file_named_as_ttid)
If you are lucky this will fill up the ttreg entry from the application form as much as possible and pop up your configured editor for corrections. Continue accordingly and save. If it does not look good or work correctly, don't get disappointed, fill it by hand by executing:
ttreg -n ttnum
Creation of the corresponding test-box software tree only depends on this ttreg entry anymore.
Once you have the necessary ttreg entry, as
root
on ginkgo
/ncc/ttpro/bin/create_testbox -v ttnum
fxp0
"proto_test_box_4
"install_disk_4
"proto_test_box_4_exclude
"create_testbox
" script, verify that you
have:/ncc/ttpro/files/ttnum_generic
tree as
a symlink to proto_test_box_4
/ncc/ttpro/files/ttnum_specific
tree with
the test-box specific config data (/etc
and /usr/home/ttraffic
dirs)/ncc/ttpro/files/exclude_dir/ttnum_exclude
as
a symlink to proto_test_box_4_exclude
. This has a foo line and is not used
for anything special. It is there for compatibility reasons only.root
on ginkgo
, preferably looking at the
output:/ncc/ttpro/bin/install_testbox -v --address <ip_addr>
ttnum
install_testbox
operation, just wait
for it to finish looking at the DEBUG messages (the last one should be
"DEBUG: Disks unmounted successfully). It may take around half an
hour.ifconfig fxp0 <ip_address> netmask 255.255.255.192
for the RIPE
DEVEL networkroute delete default
route add default 193.0.4.1
(RIPE DEVEL network)
To sync the 2nd hard disk with the contents of the 1st one, execute (manually
for now) as root
on the test-box:
/usr/local/bin/copy_disk wd1 --reconfig
ntptime
"; normal status is 0x107
).Try to boot the TB from the 2nd hard drive by typying at the boot prompt the string:
0:wd(1,a)/kernel
where (1,a)
instead of the
default (0,a)
mean that you are booting from the slave disk on the
first ide channel (so disk 1)
rm -f /var/spool/mqueue
, since all the log
messages we would normally receive by e-mail from these ticket get lost in
case the host has not a real network connection.Since the whole create_testbox process depends on a valid ttreg entry anymore, when you reach this point, everything should be ready to execute
/ncc/ttpro/config/cfengine.conf -DUpdateDNSfile
as ttraffic
on ginkgo
, preferably looking at the output.
This will automatically generate the /ncc/domain/ripe.net-tt
file
for direct DNS resolution, then restart our internal DNS server. That file
is generated by ttconfig, which uses the ttreg database data.
(This is important, If you forget to do this, then the customer will not be able to get support from Dell.)
Do a ttreg -e ttnum
and set its state
to SETUP
otherwise the makefullmesh
and ttregconfig.pl
scripts fail
Create test box relation group:
As ttraffic on ginkgo execute:
For v4:
cd /ncc/ttpro/wwwpages
mkdir -p /ncc/ttpro/data/plots/ttnum/mini
make
Add the box to the list of machines that can be seen by the ttraffic webuser. Before doing this it is strongly recommended to shutdown your browser and start again. Because if you already have browsed a ttm page with user id other than 'ripe', webserver will treat your browser with the old id (most of the time 'ttraffic').
ripe
, passwd: riperipe
/ncc/www/src/cgi-bin/ttm/.htaccess
ttnum
to the "Require group
" list
wwwsync -p /cgi-bin/ttm/.htaccess
Change the state of the box into ON in ttreg.
To speed up propagation (use with care) do the following as ttraffic
on ginkgo
:
cd /ncc/ttpro/config
cfengine.conf -DChainUpdate
Do a:
sshtt ttnum -c grep Position /data/ttraffic/"GENE.*"
This will return lines like:
Fri Feb 1 13:00:02 2002:Position from 20020201 120000 to 130000: 59.2611 +/- 0.0000, 24.4283 +/- 0.0000.
ttreg -e ttnum
Look for the "geoloc:" and enter the coordinates behind it:
"geoloc: 59.2611 +/- 0.0000, 24.4283 +/- 0.0000
".
Note that the minus signs are important. If they are omitted a box will end up in the wrong half of the world. Some good examples to understand how this line should look can be seen by doing the same for tt75 (+,+), tt46 (+,-), tt47 (-,-). Having a look at http://www.ripe.net/ripencc/mem-services/ttm/Plots/gpsinfo.html also helps.
http://ttnum.ripe.net:10259
).
stt /ncc/stt/np/startdatataking.stt