Subject: bootp & the DEC alpha as1200
To: None <tech-net@netbsd.org>
From: Stephen M Jones <smj@cirr.com>
List: tech-net
Date: 03/14/2002 20:03:04
Hi there -

I've got a DEC Alpha AS1200 that I'm trying to netboot off another
AS1200.  I'm running into some problems, I've read the netboot document
many times on the netbsd.org site, but I think I might be running into 
a problem that may not have been addressed.

firstly, let me state my goal.  I want to be able to boot an AS1200 with 
the basic install kernel for disaster recovery, et cetera.

Here is the scenario:  bjork wants to boot off of otaku.  Here is what
happens:

otaku's /etc/bootptab:

bjork:\
        :ht=ether:\
        :ha=08002BC3C532:\
        :sm=255.255.255.240:\
        :lg=207.202.214.131:\
        :ip=207.202.214.137:\
        :hn:\
        :bf=netboot:\
        :bs=auto:\
        :hd=/tftpboot:\
        :vm=rfc1048:

(note, I'm using hd instead of rp, hd is where my netbsd.gz file is)

what /tftpboot looks like on otaku:

drwxr-xr-x  2 root  wheel      512 Mar 13 02:56 mop
-r--r--r--  1 root  wheel    61392 Mar 11 21:49 netboot
-rw-r--r--  1 root  wheel  2538549 Aug 18  2001 netbsd.gz
lrwxr-xr-x  1 root  wheel        1 Mar 14 06:33 tftpboot -> .

bjork's boot command:

P00>>>boot ewa0 -p bootp -fi netbsd.gz
(boot ewa0.0.0.2.1 -file netbsd.gz -flags -a)

Trying BOOTP boot.

Broadcasting BOOTP Request...
..file open failed for bootp/ewa0.0.0.2.1

otaku's server log:

# bootpd -s -d9
bootpd: info(6):   bootptab mtime: Fri Mar 15 01:45:45 2002
bootpd: info(6):   reading "/etc/bootptab"
bootpd: info(6):   read 1 entries (1 hosts) from "/etc/bootptab"
bootpd: info(6):   recvd pkt from IP addr 0.0.0.0
bootpd: info(6):   bootptab mtime: Fri Mar 15 01:45:45 2002
bootpd: info(6):   request from Ethernet address 08:00:2B:C3:C5:32
bootpd: info(6):   found 207.202.214.137 (bjork)
bootpd: info(6):   bootfile="/tftpboot/netboot"
bootpd: info(6):   vendor magic field is 0.0.0.0
bootpd: info(6):   sending reply (with RFC1048 options)
bootpd: info(6):   setarp 207.202.214.137 - 08:00:2B:C3:C5:32
bootpd: info(6):   arp -d 207.202.214.137; arp -s 207.202.214.137 08:00:2B:C3:C5:32 temp

and thats it .. no log message concerning a tftp transfer, yet tftp 
appears to work just fine when bjork is running from a local disk:

bjork$ tftp otaku
tftp> get netboot
Received 61801 bytes in 0.2 seconds
tftp> get netbsd.gz
Received 2554599 bytes in 4.0 seconds
tftp>

If I change the name of the file or path (bf) in the bootptab, I do
get an error saying that the file couldn't be found.

So, I gave dhcpd a shot .. and I had basically the same results ..

netboot has a few strings in it:

knetbsd.alpha.gz
netbsd.alpha
onetbsd.gz
onetbsd
netbsd.old.gz
netbsd.old
netbsd.bak.gz
netbsd.bak
netbsd.gz
netbsd

So, I sort of assumed that mopd might be able to be used to grab 'netboot',
so I tried it:

bjork:

P00>>>boot ewa0 -p mop -fi netboot
(boot ewa0.0.0.2.1 -file netboot -flags -a)
Trying MOP boot.
..

Network load complete.
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 0
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
configuring I/O adapters...
  ncr0, hose 1, bus 0, slot 1
  tulip0, hose 1, bus 0, slot 2
  floppy0, hose 0, bus 1, slot 0
  isp0, hose 0, bus 0, slot 3
jumping to bootstrap code

halted CPU 0

halt code = 2
kernel stack not valid halt
PC = fffffc000050aac0
P00>>>

otaku:

# mopd -a -d -f
MOP DL 802.3 8:0:2b:c3:c5:32   > ab:0:0:1:0:0      len   54 code 08 RPR 
MOP DL 802.3 0:60:97:d1:61:b1  > 8:0:2b:c3:c5:32   len    9 code 03 ASV 
MOP DL 802.3 8:0:2b:c3:c5:32   > 0:60:97:d1:61:b1  len   54 code 08 RPR 
MOP DL 802.3 0:60:97:d1:61:b1  > 8:0:2b:c3:c5:32   len   14 code 02 MLD

So I suppose thats not possible (maybe there is a boot.mop for the 
alpha as there is for the VAX?).

I'm sorry if this topic has been exhausted, but doing a quick search 
on the archive I couldn't find anything specific to the AS1200.  Thank you.