HERA-B Bologna

Online Computing

How does vmehb1 bootstrap
The boot process of the CETIA Lynx-OS VME cpu

In the CETIA board ROM are implemented the protocols: BOOTP, TFTP, UDP and IP, and a device driver for the local network.
As you can see from the output at the bottom of this page, the bootstrap starts (line 1) with the broadcast (ethernet ff:ff:ff:ff:ff:ff, IP 255.255.255.255) of a bootp request from the client port (bootpc = 68) of the CETIA cpu (ethernet 00:00:de:49:04:c4) to the server bootp port (bootps = 67) of all the IP addresses.
In line 2 pchb3 replay to the broadcast, sending to vmehb1: the client name (Y), the server name (S) and the gateway name (G).
In the line 3 starts the download of the boot files by vmehb1 using tftp. vmehb1 sends a tftp read request (RRQ) for the file: "/home/Lynx/bootpfiles/vm", from an ephemeral port (in this case 2048) to the UDP port 69: this starts the tftp transfert from an ephemeral port (in this case 1387) of pchb3 to an ephemeral port (2048) of vmehb1 (line 4, 5, ...).
After the completion of the loading of "/home/Lynx/bootpfiles/vm", vmehb1 build a RAM-disk of 4.6 MByte, and install the root file system (/) on such RAM-disk.
In line 26706 vmehb1 sends an arp broadcast (ethernet ff:ff:ff:ff:ff:ff) to get th ethernet address of pchb3. In line 26707 pchb3 replies with its ethernet address 0:0:c0:e8:b6:ce

Starting from line 26714, vmehb1 mounts in NFS some directory of pchb3:

pchb3.bo.infn.it:/home/Lynx/C601/Nodes/vmehb1/Root             on /server
pchb3.bo.infn.it:/home/Lynx/C601/Nodes/vmehb1/Home             on /home
pchb3.bo.infn.it:/home/Lynx/C601/Nodes/vmehb1/Home/Temp/vmehb1 on /tmp

Starting from line 26737, vmehb1 loads some programs from the NFS-mounted disks.

Starting from line 28356, vmehb1 mounts in NFS some directory of hp8hb1:

hp8hb1:/home    on /hp8hb1/home
hp8hb1:/monthly on /hp8hb1/monthly
hp8hb1:/weekly  on /hp8hb1/weekly

At the and of the bootstrap the root directory "/" look like:

lrwxrwxrwx   1 root    512 May 13 15:46 X11 -> /server/X11  NFS-disk on pchb3
lr--------   1 root     12 Jul  5 11:46 bin -> /server/bin  NFS-disk on pchb3
drwxr-xr-x   2 root    512 Jul  5 11:46 bin.local           RAM-disk
drwxr-xr-x   2 root   3072 Jul  5 11:46 dev                 RAM-disk
lr--------   1 root     12 Jul  5 11:46 etc -> /server/etc  NFS-disk on pchb3
drwxr-xr-x   2 root    512 Jul  5 11:46 etc.local           RAM-disk
drwxr-xr-x   8 root   1024 Jun 24 15:28 home                NFS-disk on pchb3
drwxr-xr-x   5 root    512 Jul  5 11:46 hp8hb1              NFS-disk on hp8hb1
-rwxr-xr-x   1 root  59031 Sep 16  1994 init                RAM-disk
drwxr-xr-x   3 root   1024 Dec 29  1994 lib                 RAM-disk
lrwxrwxrwx   1 root    512 May 13 15:46 net -> /server/net  NFS-disk on pchb3
drwxr-xr-x  14 root   1024 Jan 13  1995 server              NFS-disk on pchb3
lrwxrwxrwx   1 root    512 May 13 15:46 sys -> /server/sys  NFS-disk on pchb3
drwxrwxrwt   2 root   1024 Jul  1 16:51 tmp                 NFS-disk on pchb3
drwxr-xr-t   2 root    512 Dec  3  1994 tmp.local           RAM-disk
lrwxrwxrwx   1 root    512 May 13 15:46 usr -> /server/usr  NFS-disk on pchb3

Output of the command:

tcpdump -e ether host 0:0:de:49:4:c4  > vmehb1_boot.dump

during the boot process of the Lynx-OS cpu (the tcpdump utility is written by: Van Jacobson, Craig Leres and Steve McCanne, all of Lawrence Berkeley Laboratory).

    1  0:0:de:49:4:c4  ff:ff:ff:ff:ff:ff ip 342:  255.255.255.255.bootpc     > 255.255.255.255.bootps:     xid:0x1cf2 [|bootp] (DF) [tos 0xb6]
    2  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 342:  pchb3.bo.infn.it.bootps    > vmehb1.bo.infn.it.bootpc:   xid:0x1cf2 Y:vmehb1.bo.infn.it S:pchb3.bo.infn.it G:pchb3.bo.infn.it ether 0:0:de:49:4:c4 [|bootp]
    3  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 1070: vmehb1.bo.infn.it.2048     > pchb3.bo.infn.it.tftp: 1028 RRQ "/home/Lynx/bootpfiles/vm"[|tftp] (DF) [tos 0xb6]
    4  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 558:  pchb3.bo.infn.it.1387      > vmehb1.bo.infn.it.2048:     udp 516
    5  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 64:   vmehb1.bo.infn.it.2048     > pchb3.bo.infn.it.1387:      udp 6 (DF) [tos 0xb6]
.....................................
26703  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 558:  pchb3.bo.infn.it.1387      > vmehb1.bo.infn.it.2048:     udp 516
26704  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 558:  pchb3.bo.infn.it.1387      > vmehb1.bo.infn.it.2048:     udp 516
26705  0:0:de:49:4:c4  ff:ff:ff:ff:ff:ff arp 60:  arp who-has vmehb1.bo.infn.it tell vmehb1.bo.infn.it
26706  0:0:de:49:4:c4  ff:ff:ff:ff:ff:ff arp 60:  arp who-has pchb3.bo.infn.it tell vmehb1.bo.infn.it
26707  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    arp 42:  arp reply pchb3.bo.infn.it is-at 0:0:c0:e8:b6:ce
26708  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 98:   vmehb1.bo.infn.it.609      > pchb3.bo.infn.it.sunrpc:    udp 56
26709  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 70:   pchb3.bo.infn.it.sunrpc    > vmehb1.bo.infn.it.609:      udp 28
26710  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 150:  vmehb1.bo.infn.it.610      > pchb3.bo.infn.it.676:       udp 108
26711  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 102:  pchb3.bo.infn.it.676       > vmehb1.bo.infn.it.610:      udp 60
26712  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 98:   vmehb1.bo.infn.it.611      > pchb3.bo.infn.it.sunrpc:    udp 56
26713  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 70:   pchb3.bo.infn.it.sunrpc    > vmehb1.bo.infn.it.611:      udp 28
26714  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 142:  vmehb1.bo.infn.it.31d988e3 > pchb3.bo.infn.it.nfs:       100 getattr [|nfs]
26715  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 138:  pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31d988e3: reply ok 96 getattr [|nfs]
26716  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 98:   vmehb1.bo.infn.it.610      > pchb3.bo.infn.it.sunrpc:    udp 56
26717  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 70:   pchb3.bo.infn.it.sunrpc    > vmehb1.bo.infn.it.610:      udp 28
26718  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 150:  vmehb1.bo.infn.it.611      > pchb3.bo.infn.it.676:       udp 108
26719  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 102:  pchb3.bo.infn.it.676       > vmehb1.bo.infn.it.611:      udp 60
....................................
26729  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 142:  vmehb1.bo.infn.it.31db88e3 > pchb3.bo.infn.it.nfs:       100 getattr [|nfs]
26730  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 138:  pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31db88e3: reply ok 96 getattr [|nfs]
26731  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 150:  vmehb1.bo.infn.it.31dc88e3 > pchb3.bo.infn.it.nfs:       108 lookup [|nfs]
26732  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 170:  pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31dc88e3: reply ok 128 lookup [|nfs]
26733  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 150:  vmehb1.bo.infn.it.31dd88e3 > pchb3.bo.infn.it.nfs:       108 lookup [|nfs]
26734  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 170:  pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31dd88e3: reply ok 128 lookup [|nfs]
26735  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 142:  vmehb1.bo.infn.it.31de88e3 > pchb3.bo.infn.it.nfs:       100 statfs [|nfs]
26736  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 90:   pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31de88e3: reply ok 48 statfs [|nfs]
26737  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 154:  vmehb1.bo.infn.it.31df88e3 > pchb3.bo.infn.it.nfs:       112 read [|nfs]
26738  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 146:  pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31df88e3: reply ok 104 read [|nfs]
26739  0:0:de:49:4:c4  0:0:c0:e8:b6:ce   ip 154:  vmehb1.bo.infn.it.31e088e3 > pchb3.bo.infn.it.nfs:       112 read [|nfs]
26740  0:0:c0:e8:b6:ce 0:0:de:49:4:c4    ip 146:  pchb3.bo.infn.it.nfs       > vmehb1.bo.infn.it.31e088e3: reply ok 104 read [|nfs]
....................................
28356  0:0:de:49:4:c4  ff:ff:ff:ff:ff:ff arp 60:  arp who-has hp8hb1.bo.infn.it tell vmehb1.bo.infn.it
28357  8:0:9:b1:ab:ec  0:0:de:49:4:c4    arp 60:  arp reply hp8hb1.bo.infn.it is-at 8:0:9:b1:ab:ec
28358  0:0:de:49:4:c4  8:0:9:b1:ab:ec    ip 98:   vmehb1.bo.infn.it.631      > hp8hb1.bo.infn.it.sunrpc:   udp 56
28359  8:0:9:b1:ab:ec  0:0:de:49:4:c4    ip 70:   hp8hb1.bo.infn.it.sunrpc   > vmehb1.bo.infn.it.631:      udp 28
28360  0:0:de:49:4:c4  8:0:9:b1:ab:ec    ip 122:  vmehb1.bo.infn.it.632      > hp8hb1.bo.infn.it.712:      udp 80
28361  8:0:9:b1:ab:ec  0:0:de:49:4:c4    ip 102:  hp8hb1.bo.infn.it.712      > vmehb1.bo.infn.it.632:      udp 60
28362  0:0:de:49:4:c4  8:0:9:b1:ab:ec    ip 98:   vmehb1.bo.infn.it.633      > hp8hb1.bo.infn.it.sunrpc:   udp 56
28363  8:0:9:b1:ab:ec  0:0:de:49:4:c4    ip 70:   hp8hb1.bo.infn.it.sunrpc   > vmehb1.bo.infn.it.633:      udp 28
28364  0:0:de:49:4:c4  8:0:9:b1:ab:ec    ip 142:  vmehb1.bo.infn.it.344f88e3 > hp8hb1.bo.infn.it.nfs:      100 getattr [|nfs]
28365  8:0:9:b1:ab:ec  0:0:de:49:4:c4    ip 138:  hp8hb1.bo.infn.it.nfs      > vmehb1.bo.infn.it.344f88e3: reply ok 96 getattr [|nfs]
....................................

HERA-B Bologna Home Page

July 5, 1996 Domenico Galli

HERA-B Bologna

Online Computing

How does vmehb1 bootstrap The boot process of the CETIA Lynx-OS VME cpu

How does vmehb1 bootstrap
The boot process of the CETIA Lynx-OS VME cpu