Hi all.
I am having problems with a network installation
of the Tru64 UNIX v5.0 using the RIS server.
The workstation AS600 on which I would like
to install the OS has firmware v7.0.
I have set the joind flags to -d9 -l2 in order
to turn on debug logging.
I have also set $JOINLOG to point at /tmp/join.log
# /sbin/init.d/dhcp stop
# rcmgr set JOIND_FLAGS -d9 -l2
# JOINLOG=/tmp/join.log; /sbin/init.d/dhcp start
Then I said at the srm console prompt
>>> boot -fl "" ewa
Then nothing happened.
Well, hardly anything - the firmware said it was
broadcasting BOOTP request, and that it was not
successful at it.
The /tmp/join.log contained several instances of the following:
============================================================
975063678.563152 Packet arrived on Friday November 24 12:01:18
received on address 161.53.65.255
packed payload:
0000: 01 01 06 00 00 00 00 00 0a 00 80 00 a1 35 41 46 5AF
0016: 00...
0224: 00 00 00 00 00 00 00 00 00 00 00 00 63 82 53 63 c Sc
0240: 35 01 08 2b 02 5e 00 ff 5 + ^
from (ip_address,port#)=(161.53.65.70,68) to=(255.255.255.255,67) received on interface tu0
xid=0000000000 secs=2560 flags=0x8000 chaddr=00:00:00:00:00:00
received short packet length 248 bytes from 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00: discarded
Then I found somehow (URL
http://www.join.com/doc/server.b.html) that the
diagnostics is obtained on some early BOOTP clients and that the server
can be forced to accept these requests by editing its configuration file
/etc/join/server.pcy.
After I did it and restarted joind, the firmware still complained
that it couldn't find a BOOTP server, but the /tmp/join.log contained
an iteration of the following:
============================================================
974994512.663680 Packet arrived on Thursday November 23 16:48:32
received on address 161.53.65.255
packed payload:
0000: 01 01 06 00 78 e8 de 7e 00 00 00 00 00 00 00 00 x ~
0016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f8 22 "
0032: 59 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Y
0048: 00...
0288: 00 00 00 00 00 00 00 00 00 00 00 00
from (ip_address,port#)=(0.0.0.0,68) to=(255.255.255.255,67) received on interface tu0
xid=0x78e8de7e secs=0 flags=000000 chaddr=00:00:f8:22:59:04
unpacked payload:
ht=1:ha=00.00.f8.22.59.04:ci=0.0.0.0:gi=0.0.0.0:sa=0.0.0.0:yi=0.0.0.0:
BOOTP packet from HW 00:00:f8:22:59:04 configured with IP 161.53.65.164
Reply Host structure:
ht=1:ha=00.00.f8.22.59.04:ci=0.0.0.0:gi=161.53.65.160:sa=161.53.65.160:yi=161.53.65.1
64:vm=rfc1048:sm=255.255.255.0:ho=toporko:bs=16693:rp=kosjenka:/ris/r0p1:sn=kosjenka:
bf=/ris/r0k1:
outgoing bootp packet:
0000: 02 01 06 00 78 e8 de 7e 00 00 00 00 00 00 00 00 x ~
0016: a1 35 41 a4 a1 35 41 a0 a1 35 41 a0 00 00 f8 22 5A 5A 5A "
0032: 59 04 00 00 00 00 00 00 00 00 00 00 6b 6f 73 6a Y kosj
0048: 65 6e 6b 61 00 00 00 00 00 00 00 00 00 00 00 00 enka
0064: 00...
0096: 00 00 00 00 00 00 00 00 00 00 00 00 2f 72 69 73 /ris
0112: 2f 72 30 6b 31 00 00 00 00 00 00 00 00 00 00 00 /r0k1
0128: 00...
0224: 00 00 00 00 00 00 00 00 00 00 00 00 63 82 53 63 c Sc
0240: 01 04 ff ff ff 00 0c 07 74 6f 70 6f 72 6b 6f 0d toporko
0256: 02 41 35 11 12 6b 6f 73 6a 65 6e 6b 61 3a 2f 72 A5 kosjenka:/r
0272: 69 73 2f 72 30 70 31 ff 00 00 00 00 00 00 00 00 is/r0p1
0288: 00 00 00 00 00 00 00 00 00 00 00 00
setting ARP entry to IP 161.53.65.164 as HW 00:00:f8:22:59:04
removing ARP entry to 161.53.65.164
============================================================
It seems that the firmware does not understand the answer of
the joind daemon, but I can't think of a reason why it happens.
Thank you for your consideration.
Sinisa Segvic
Received on Fri Nov 24 2000 - 11:36:41 NZDT