Why
do you separate the DHCP range from your latest BOSS? It should be in the same
subnet so that tftp can work, under your latest boss control subnet.
Best
Regards,
Cheng
Cui
•
Frey Computing Services Center • Baton Rouge, LA 70803
From:
testbed.twisc@gmail.com [mailto:testbed.twisc@gmail.com] On Behalf Of Chang
Shiau-Han
Sent: Thursday, March 18, 2010 11:09 PM
To: testbed-admins@flux.utah.edu
Cc: ccui1@tigers.lsu.edu
Subject: Re: [Testbed-admins] Question of add new node and tftpboot
That right, our latest boss's
ip is the 192.168.32.70, and dhcp range is 192.168.36.150 to 250.
i had checked dhcpd.conf.template, it's steup the same with old boss dhcp
setup.
Or, have other way to add new nodes, ex. by hand?
shiauhan
2010/3/19 Cheng Cui <ccui1@tigers.lsu.edu>
I am not quite sure. But I am curious about your DHCP
server’s ip is not in the same network of others. Is the latest
boss’s ip the 192.168.32.70? Looks like ip confliction.
Best Regards,
Cheng Cui
• Frey Computing Services Center • Baton
Rouge, LA 70803
Hi,
We have 2 version emulab in our machines, old version and latest version, and
on-line server is the latest version, off-line server is the old version.
We want to add new nodes to the machine latest version. But when we using
tftpboot in latest version to add a new node, node will coutinuously reboot as
in figure 2.
If we copy tftpboot from machine old version to machine latest version, we can
get the login in screen as in figure 1.But still we can not add a new node.
Can we copy the tftpboot directory from machine old version to machine latest
version directly? or we should using 'tftpboot-latest.tar' in machine latest
version and execute the "prepare" script in three MFSes??
And where shall we copy? Shall we maintain the same file to /tftpboot/ and
/usr/testbed/tftpboot ?
In
tftpd.log, some file's path had problem, example,
"/tftpboot/freebsd.newnode/kernel.ko.gz"
and "/tftpboot/freebsd.newnode/boot/kernel.ko.gz", the path is
right?
We
have no idea how to add the node in this situation.Would you please give us a
hand to handle this problem?
===================================bootinfo.log=====================================
Mar 18 16:51:19 boss bootinfo[1130]: 192.168.36.250: REQUEST (vers 1)
Mar 18 16:51:19 boss bootinfo[1130]: iptonodeid: No such nodeid: 192.168.36.250
Mar 18 16:51:19 boss bootinfo[1130]: Unable to convert IP to nodeid for
192.168.36.250!
Mar 18 16:51:19 boss bootinfo[1130]: 192.168.36.250: nonexistent IP, booting
'emulab-ops,NEWNODE-MFS'
Mar 18 16:51:19 boss bootinfo[1130]: iptonodeid: No such nodeid: 192.168.36.250
Mar 18 16:51:19 boss bootinfo[1130]: Unable to convert IP to nodeid for
192.168.36.250!
Mar 18 16:51:19 boss bootinfo[1130]: 192.168.36.250: REPLY: boot from mfs
192.168.32.70:/tftpboot/freebsd.newnode
===================================tftpd.log=====================================
Mar 18 16:51:13 boss tftpd[79813]: 192.168.36.250/2070: RRQ for /tftpboot/pxeboot.emu
(remapped to /pxeboot.emu)
Mar 18 16:51:13 boss tftpd[79813]: tftp: client does not accept options
Mar 18 16:51:13 boss tftpd[79813]: 192.168.36.250/2070: RRQ done
Mar 18 16:51:13 boss tftpd[1196]: pid 79813 exits, numchildren=0
Mar 18 16:51:13 boss tftpd[79814]: 192.168.36.250/2071: RRQ for /tftpboot/pxeboot.emu
(remapped to /pxeboot.emu)
Mar 18 16:51:13 boss tftpd[79814]: 192.168.36.250/2071: RRQ done
Mar 18 16:51:13 boss tftpd[1196]: pid 79814 exits, numchildren=0
Mar 18 16:51:19 boss tftpd[79825]: 192.168.36.250/2229: RRQ for
/tftpboot/freebsd.newnode/boot/boot.4th.gz (remapped to
/freebsd.newnode/boot/boot.4th.gz)
Mar 18 16:51:19 boss tftpd[79825]: 192.168.36.250/2229: NAK (1, File not found) sent
Mar 18 16:51:19 boss tftpd[1196]: pid 79825 exits, numchildren=1
Mar 18 16:51:19 boss tftpd[79826]: 192.168.36.250/2230: RRQ for
/tftpboot/freebsd.newnode/boot/boot.4th (remapped to
/freebsd.newnode/boot/boot.4th)
Mar 18 16:51:19 boss tftpd[79826]: 192.168.36.250/2230: NAK (1, File not found) sent
Mar 18 16:51:19 boss tftpd[1196]: pid 79826 exits, numchildren=0
Mar 18 16:51:19 boss tftpd[79827]: 192.168.36.250/2231: RRQ for
/tftpboot/freebsd.newnode/boot/loader.rc.gz (remapped to
/freebsd.newnode/boot/loader.rc.gz)
Mar 18 16:51:19 boss tftpd[79827]: 192.168.36.250/2231: RRQ done
Mar 18 16:51:19 boss tftpd[1196]: pid 79827 exits, numchildren=0
Mar 18 16:51:19 boss tftpd[79828]: 192.168.36.250/2232: RRQ for /tftpboot/freebsd.newnodeej.gz
(remapped to /freebsd.newnodeej.gz)
Mar 18 16:51:19 boss tftpd[79828]: 192.168.36.250/2232: NAK (1, File not found) sent
Mar 18 16:51:19 boss tftpd[1196]: pid 79828 exits, numchildren=1
Mar 18 16:51:19 boss tftpd[79829]: 192.168.36.250/2233: RRQ for /tftpboot/freebsd.newnodeej
(remapped to /freebsd.newnodeej)
Mar 18 16:51:19 boss tftpd[79829]: 192.168.36.250/2233: NAK (1, File not found) sent
Mar 18 16:51:19 boss tftpd[1196]: pid 79829 exits, numchildren=0
Mar 18 16:51:20 boss tftpd[79831]: 192.168.36.112/2070: RRQ for /tftpboot/pxeboot.emu
(remapped to /pxeboot.emu)
Mar 18 16:51:20 boss tftpd[79831]: tftp: client does not accept options
Mar 18 16:51:20 boss tftpd[79831]: 192.168.36.112/2070: RRQ done
Mar 18 16:51:20 boss tftpd[1196]: pid 79831 exits, numchildren=0
Mar 18 16:51:20 boss tftpd[79832]: 192.168.36.112/2071: RRQ for /tftpboot/pxeboot.emu
(remapped to /pxeboot.emu)
Mar 18 16:51:20 boss tftpd[79832]: 192.168.36.112/2071: RRQ done
Mar 18 16:51:20 boss tftpd[1196]: pid 79832 exits, numchildren=0
Mar 18 16:51:29 boss tftpd[79842]: 192.168.36.250/2239: RRQ for
/tftpboot/freebsd.newnode/kernel.ko.gz (remapped to /freebsd.newnode/kernel.ko.gz)
Mar 18 16:51:29 boss tftpd[79842]: 192.168.36.250/2239: NAK (1, File not found) sent
Mar 18 16:51:29 boss tftpd[1196]: pid 79842 exits, numchildren=1
Mar 18 16:51:29 boss tftpd[79843]: 192.168.36.250/2240: RRQ for
/tftpboot/freebsd.newnode/kernel.ko (remapped to /freebsd.newnode/kernel.ko)
Mar 18 16:51:29 boss tftpd[79843]: 192.168.36.250/2240: NAK (1, File not found) sent
Mar 18 16:51:29 boss tftpd[1196]: pid 79843 exits, numchildren=0
Mar 18 16:51:29 boss tftpd[79844]: 192.168.36.250/2241: RRQ for /tftpboot/freebsd.newnode/boot/kernel.ko.gz
(remapped to /freebsd.newnode/boot/kernel.ko.gz)
Mar 18 16:51:29 boss tftpd[79844]: 192.168.36.250/2241: RRQ done
Mar 18 16:51:29 boss tftpd[1196]: pid 79844 exits, numchildren=0
Mar 18 16:51:29 boss tftpd[79845]: 192.168.36.250/2242: RRQ for
/tftpboot/freebsd.newnode/boot/kernel.ko.gz (remapped to
/freebsd.newnode/boot/kernel.ko.gz)
Mar 18 16:51:30 boss tftpd[79845]: 192.168.36.250/2242: RRQ done
Mar 18 16:51:30 boss tftpd[1196]: pid 79845 exits, numchildren=0
Mar 18 16:51:30 boss tftpd[79846]: 192.168.36.250/2243: RRQ for
/tftpboot/freebsd.newnode/etc/fstab.gz (remapped to
/freebsd.newnode/etc/fstab.gz)
Mar 18 16:51:30 boss tftpd[79846]: 192.168.36.250/2243: NAK (1, File not found) sent
Mar 18 16:51:30 boss tftpd[1196]: pid 79846 exits, numchildren=1
Mar 18 16:51:30 boss tftpd[79847]: 192.168.36.250/2244: RRQ for
/tftpboot/freebsd.newnode/etc/fstab (remapped to /freebsd.newnode/etc/fstab)
Mar 18 16:51:30 boss tftpd[79847]: 192.168.36.250/2244: NAK (1, File not found) sent
|