blog:netboot_solaris

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
blog:netboot_solaris [2018/11/28 09:26] – [Detailed Instructions] johnblog:netboot_solaris [2019/02/17 16:45] (current) – john
Line 22: Line 22:
  
 <code> <code>
-echo "00:01:02:03:04:ef sparky" >> /etc/ethers+echo "00:80:42:0b:17:dd sparky" >> /etc/ethers
 echo "192.168.1.15 sparky" >> /etc/hosts echo "192.168.1.15 sparky" >> /etc/hosts
 </code> </code>
  
-Run the rarp daemon in verbose mode (rarpd -v) and monitor syslog/messages for queries from the Sparc machine as it powers on. You should see a request for "00:01:02:03:04:ef" being answered by "192.168.1.15".+Run the rarp daemon in verbose mode (rarpd -v -d) and monitor syslog/messages for queries from the Sparc machine as it powers on. You should see a request for "00:80:42:0b:17:dd" being answered by "192.168.1.15", if you don't have a matching entry yet, you'll see the following:
  
-The next step is supplying a kernel image to the booting Sparc machine.+<code> 
 +~# rarpd -d -v 
 +rarpd[2326]: Building list of addresses per interface. 
 +rarpd[2326]: link lo 
 +rarpd[2326]:   addr 127.0.0.1/8 on lo 
 +rarpd[2326]: link eth0 
 +rarpd[2326]:   addr 192.168.1.111/24 on eth0 
 +rarpd[2326]: RARP request from 00:80:42:0b:17:dd on eth0 
 +rarpd[2326]: not found in /etc/ethers 
 +rarpd[2326]: RARP request from 00:80:42:0b:17:dd on eth0 
 +rarpd[2326]: not found in /etc/ethers 
 +rarpd[2326]: RARP request from 00:80:42:0b:17:dd on eth0 
 +rarpd[2326]: not found in /etc/ethers 
 +rarpd[2326]: RARP request from 00:80:42:0b:17:dd on eth0 
 +rarpd[2326]: not found in /etc/ethers 
 +rarpd[2326]: RARP request from 00:80:42:0b:17:dd on eth0 
 +rarpd[2326]: not found in /etc/ethers 
 +</code> 
 + 
 +Once you have the right ethernet address for the Sparc, rarpd will respond as such: 
 + 
 +<code> 
 +rarpd[3578]: RARP request from 00:80:42:0b:17:dd on eth0 
 +rarpd[3578]: RARP response to 00:80:42:0b:17:dd 192.168.1.15 on eth0 
 +</code> 
 + 
 +The next step is supplying a kernel image to the booting Sparc machine. Note that modern versions of rarpd on Linux will also try to find a Sun kernel image, if you already have a working tftp server elsewhere ignore that feature of rarpd by running it with the //-e// flag: rarpd -d -v -e.
  
 === tftp === === tftp ===
  
 As the machine starts to boot it will make a request via TFTP, to the same server that it received a rarp request from, for a kernel image. As the machine starts to boot it will make a request via TFTP, to the same server that it received a rarp request from, for a kernel image.
 +
 +In my case:
 +
 +<code>
 +Feb 17 16:43:56 curse tftpd[4446]: tftpd: serving file from /export/tftp
 +Feb 17 16:44:05 curse tftpd[4478]: tftpd: trying to get file: C0A8010F.SUN4M
 +</code>
  
 The name of the kernel image will depend on the IP address that you have assigned to the Sparc machine. Unfortunately it's in hexadecimal format. In the case of assigning 192.168.1.15, as above, you can calculate the filename as follows: The name of the kernel image will depend on the IP address that you have assigned to the Sparc machine. Unfortunately it's in hexadecimal format. In the case of assigning 192.168.1.15, as above, you can calculate the filename as follows:
Line 72: Line 105:
         boottype=:in          boottype=:in 
 </code> </code>
 +
 +Obviously **sparky** must match the hostname you're assigning to the Solaris host, and the **root** and **install** paths should mirror where you have unpacked the Solaris installation CD images.
  
 === NFS === === NFS ===
  • blog/netboot_solaris.1543397216.txt.gz
  • Last modified: 2018/11/28 09:26
  • by john