Edit the testbox registration using ttreg -e ttXX
and replace
ipaddr:
, gateway:
, netmask:
and
dnsserv:
with their new values.
If ipaddr:
is to be overwritten with a new value, backup the
current value in a old-ipaddr:
record. Multiple
old-ipaddr:
are allowed.
Logon to ginkgo and go to /ncc/ttpro/files/ttXX_specific/etc
and
record the same set of changes in changes in rc.conf.local
and
resolv.conf
If applicable, files in
/ncc/ttpro/files/ttXX_specific/usr/home/ttraffic/config/
have to be altered to to reflect the new network identity
Do this as root
On ginkgo, ttsync
your changes using tt_sync -v -E -b ttXX -f /etc/
Do this as root
Logon to the testbox in question, and in coordination with the hosting site
(see ttreg
for contact details), schedule a shutdowntime. This can
be done remotely with shutdown(8)
Example:
shutdown -h 1500 "Halt machine because of relocation"
As testboxes are configured for GMT this will initiate a shutdown at 16:00 PM Central European Time and 10:00 AM Eastern Standard Time. Add one hour for Daylight Savings Time.
Just when the box is about to go down, lets say one hour before or less, edit
the box its status with ttreg
and make it status: OFF
.
This ensures that other testboxes in the TTM network won't try to exchange
testdata with the unreachable testbox.
Logon to ginkgo and go to /ncc/ttpro/config
and execute the following command:
cfengine.conf -DChainUpdate
. This will push the new configuration to all testboxes
You may do this as root, but ttraffic is sufficient enough for this purpose.
Don't forget the change the box its status back to ON again, after it has been successfully relocated and follow the remaining steps in "Installing a new testbox" "section 5, when the box comes online at the site", if applicable.