03.06.2019 16:40, Claudio Jeker пишет:
On Mon, Jun 03, 2019 at 04:19:13PM +0300, Belous Victor wrote:
Thanks, Claudio Jeker

03.06.2019 15:39, Claudio Jeker пишет:
On Mon, Jun 03, 2019 at 03:15:07PM +0300, Belous Victor wrote:
Hi!

I can't boot the sparc t1000 server.

I have openbsd installed on virtualbox, the config openbsd server it is


openbsd# uname -a
OpenBSD openbsd.centerinform. 6.5 GENERIC#3 amd64

openbsd# cat /etc/ethers
00:14:4f:c4:7d:d6    sparc

openbsd# cat /etc/hosts
127.0.0.1    localhost
::1        localhost
192.168.215.130    sparc
192.168.215.131    openbsd

openbsd# cat /etc/rc.conf.local
bootparamd_flags=
mountd_flags=
nfsd_flags=
ntpd_flags-"NO"
pf=NO
portmap_flags=
rarpd_flags="-al"
tftpd_flags="/tftpboot"

openbsd# cat /etc/bootparams
sparc    root=192.168.215.231:/bsd.rd

This is not correct. bootparams points to a directory that acts as the
root directory on the sparc system.
You can set it to /home/bvictor/install/sparc64 or some other place where
bsd.rd is located.
Now

openbsd# cat /etc/bootparams
sparc    root=192.168.215.231:/home/bvictor/install/sparc64
openbsd#



{0} ok boot net
You may want to use boot net bsd.rd (so that the bsd.rd kernel is loaded).
{0} ok boot net bsd.rd

SC Alert: Host System has Reset
ChassisSerialNumber NNL0812010



Atlas, Shpalernaya, 28 Sun T1000




Boot device: /pci@7c0/pci@0/network@4  File and args: bsd.rd
1000 Mbps full duplex  Link up
OpenBSD BOOT 1.12
1000 Mbps full duplex  Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/etc/random.seed: No such file or directory
1000 Mbps full duplex  Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/bsd.rd: No such file or directory

Boot:


SC Alert: Host System has Reset
ChassisSerialNumber NNL0812010



Atlas, Shpalernaya, 28 Sun T1000




Boot device: /pci@7c0/pci@0/network@4  File and args:
1000 Mbps full duplex  Link up
OpenBSD BOOT 1.12
Trying bsd...
1000 Mbps full duplex  Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/etc/random.seed: No such file or directory
1000 Mbps full duplex  Link up
No response for RARP request
open /pci@7c0/pci@0/network@4/bsd: No such file or directory

Not sure what is up with 'No response for RARP request'. In the end you
already got ofwboot.net loaded via tftp. It is possile that the T1000 is
using dhcp for this and so the RARP is not fully working (at least the
tcpdump output had no RARP packets in it).
I thinks, OpenBSD BOOT uses RARP, but with errors. Tcpdump show, it don't
sent ARP request correct

16:13:20.544694 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:2 [|bootp]
   0000: 4500 0148 0000 0000 0411 b5a6 0000 0000  E..H............
   0010: ffff ffff 0044 0043 0134 7168 0101 0600  .....D.C.4qh....
   0020: 0000 0000 0002 0000 0000 0000 0000 0000  ................
   0030: 0000 0000 0000 0000 0014 4fc4 7dd6 0000  ..........O.}...
   0040: 0000 0000 0000 0000 0000 0000 0000 0000  ................
   0050: 0000 0000 0000 0000 0000 0000 0000 0000  ................
   0060: 0000 0000 0000                           ......

This is not a RARP packet. So it seems your system is not receiving the
RARP packets sent by ofwboot.net on the T1000. Since you mentioned that
this is a virtual system it could be that the host is filtering the
requests out. The bootloader will fall back to bootp if rarpd/bootparams
fails.
You may be able to setup dhcpd to load the kernel by setting a host entry
for the sparc system with the full path to your NFS reachable bsd.rd as
bootfile.

I stop firewall service on the host and no change.

I installed dhcp server on openbsd with the config

openbsd# cat /etc/dhcpd.conf
authoritative;
subnet 192.168.215.0 netmask 255.255.255.0 {
    range                 192.168.215.121 192.168.215.129;
    option routers            192.168.215.100;
    option broadcast-address    192.168.215.255;
    option domain-name-servers    192.168.215.100;
    option domain-name        "centerinform";
}
host sparc {
    hardware ethernet 00:14:4f:c4:7d:d6;
    option host-name "sparc";
    fixed-address 192.168.215.130;
    option root-path "192.168.215.130:/home/bvictor/install/root";
    server-name "openbsd";
    filename "ofwboot.net";
    allow bootp;
    next-server openbsd; }

openbsd#

and issue the next boot command

{0} ok boot net:dhcp bsd.rd

SC Alert: Host System has Reset
ChassisSerialNumber NNL0812010



Atlas, Shpalernaya, 28 Sun T1000




Boot device: /pci@7c0/pci@0/network@4:dhcp  File and args: bsd.rd
1000 Mbps full duplex  Link up
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for BOOTP/DHCP reply
>> OpenBSD BOOT 1.12
1000 Mbps full duplex  Link up
No response for RARP request
Using BOOTP protocol: ip address: 192.168.215.130, hostname: sparc, netmask: 255.255.255.0, gateway: 192.168.215.100
root addr=192.168.215.131 path=/
open /pci@7c0/pci@0/network@4:dhcp/etc/random.seed: Unknown error: code 13
1000 Mbps full duplex  Link up
No response for RARP request
Using BOOTP protocol: ip address: 192.168.215.130, hostname: sparc, netmask: 255.255.255.0, gateway: 192.168.215.100
root addr=192.168.215.131 path=/
open /pci@7c0/pci@0/network@4:dhcp/bsd.rd: Unknown error: code 13

Boot: ares> break

Then I run next command


{0} ok boot net bsd.rd

SC Alert: Host System has Reset
ChassisSerialNumber NNL0812010



Atlas, Shpalernaya, 28 Sun T1000




Boot device: /pci@7c0/pci@0/network@4  File and args: bsd.rd
1000 Mbps full duplex  Link up
>> OpenBSD BOOT 1.12
1000 Mbps full duplex  Link up
No response for RARP request
Using BOOTP protocol: ip address: 192.168.215.130, hostname: sparc, netmask: 255.255.255.0, gateway: 192.168.215.100
root addr=192.168.215.131 path=/
open /pci@7c0/pci@0/network@4/etc/random.seed: Unknown error: code 13
1000 Mbps full duplex  Link up
No response for RARP request
Using BOOTP protocol: ip address: 192.168.215.130, hostname: sparc, netmask: 255.255.255.0, gateway: 192.168.215.100
root addr=192.168.215.131 path=/
open /pci@7c0/pci@0/network@4/bsd.rd: Unknown error: code 13

Boot:


On openbsd

openbsd# tcpdump  -s 1024 ether host 00:14:4f:c4:7d:d6
tcpdump: listening on em0, link-type EN10MB
14:45:56.463418 arp who-has openbsd (Broadcast) tell sparc
14:45:56.463486 arp reply openbsd is-at 08:00:27:40:f1:e2
14:45:56.464143 sparc.32768 > openbsd.tftp: 20 RRQ "ofwboot.net"
14:45:56.464536 openbsd.15993 > sparc.32768: udp 516

..... (boot ofwboot.net)


14:46:30.933771 0.0.0.0.bootpc > 255.255.255.255.bootps: vend-rfc1048
14:46:30.934324 openbsd.bootps > sparc.bootpc:  Y:sparc S:openbsd sname "openbsd" file "ofwboot.net" vend-rfc1048 SM:255.255.255.0 DG:192.168.215.100 NS:192.168.215.100 HN:"sparc" DN:"centerinform" BR:192.168.215.255 [tos 0x10]
14:46:30.938928 arp who-has openbsd tell sparc
14:46:30.939026 arp reply openbsd is-at 08:00:27:40:f1:e2
14:46:30.939692 sparc.1023 > openbsd.sunrpc: udp 76
14:46:30.939867 openbsd.sunrpc > sparc.1023: udp 28
14:46:30.940560 sparc.1023 > openbsd.1008: udp 68
14:46:30.940784 openbsd.1008 > sparc.1023: udp 28
14:47:07.400305 sparc.bootpc > 255.255.255.255.bootps:  secs:36 vend-rfc1048
14:47:07.400706 openbsd.bootps > sparc.bootpc:  secs:36 Y:sparc S:openbsd sname "openbsd" file "ofwboot.net" vend-rfc1048 SM:255.255.255.0 DG:192.168.215.100 NS:192.168.215.100 HN:"sparc" DN:"centerinform" BR:192.168.215.255 [tos 0x10]
14:47:07.406739 sparc.1022 > openbsd.1008: udp 68
14:47:07.406922 openbsd.1008 > sparc.1022: udp 28


On the host computer, where run virtualbox openbsd I switch off the firewoll and have the next packets

[root@tpm ~]# tcpdump -s 1024 -i enp4s0f0 ether host 00:14:4f:c4:7d:d6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp4s0f0, link-type EN10MB (Ethernet), capture size 1024 bytes
14:45:56.467016 ARP, Request who-has openbsd (Broadcast) tell sparc, length 50 14:45:56.467347 ARP, Reply openbsd is-at 08:00:27:40:f1:e2 (oui Unknown), length 50 14:45:56.467793 IP sparc.filenet-tms > openbsd.tftp:  20 RRQ "ofwboot.net" octet
14:45:56.468408 IP openbsd.15993 > sparc.filenet-tms: UDP, length 516
14:45:56.468916 IP sparc.filenet-tms > openbsd.15993: UDP, length 4


... (boot the ofwboot.net)

14:45:56.557471 IP sparc.filenet-tms > openbsd.15993: UDP, length 4
14:46:30.938023 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:14:4f:c4:7d:d6 (oui Unknown), length 300 14:46:30.938830 IP openbsd.bootps > sparc.bootpc: BOOTP/DHCP, Reply, length 300
14:46:30.943206 ARP, Request who-has openbsd tell sparc, length 50
14:46:30.943519 ARP, Reply openbsd is-at 08:00:27:40:f1:e2 (oui Unknown), length 50
14:46:30.944047 IP sparc.1023 > openbsd.sunrpc: UDP, length 76
14:46:30.944383 IP openbsd.sunrpc > sparc.1023: UDP, length 28
14:46:30.944825 IP sparc.1023 > openbsd.1008: UDP, length 68
14:46:30.945301 IP openbsd.1008 > sparc.1023: UDP, length 28
14:47:07.404672 IP sparc.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:14:4f:c4:7d:d6 (oui Unknown), length 300 14:47:07.405298 IP openbsd.bootps > sparc.bootpc: BOOTP/DHCP, Reply, length 300
14:47:07.410320 IP sparc.exp2 > openbsd.1008: UDP, length 68
14:47:07.410851 IP openbsd.1008 > sparc.exp2: UDP, length 28

I have no ideas who don't work rarp.




--
С уважением,
Виктор Антонович Белоус

Reply via email to