Sparc/Netboot/ko

이 글은 젠투/SPARC netboot 설치 이미지 활용을 위해 네트워크 부팅 서버 설정을 안내합니다.

도입부
이 문서는 썬 마이크로 시스템즈 SPARC 또는 울트라 스팍 기반 컴퓨터용 네트워크 부팅 환경 설정 방법을 설명합니다. 이 문서는 여러분이 네트워크 부팅 서버로 가동할 젠투 리눅스 컴퓨터를 이미 갖추고 있다고 가정합니다.

넷부트 서버와 클라이언트는 동일한 서브넷에 있어야 하는데 ARP 프로토콜이 보통 다른 네트워크 서브넷으로 전달하지 못하기 때문입니다.

네트워크 부팅 과정에서 일어나는 일의 대략적인 내용은 다음과 같습니다:


 * 1) 클라이언트 머신은 IP 주소를 요청하기 위해 역방향 ARP(RARP) 요청을 보냅니다.
 * 2) 서버 머신은 IP 주소를 클라이언트에 응답으로 반환합니다.
 * 3) 클라이언트에서 TFTP 프로토콜을 이용하여 RARP 서버에서 부팅 이미지 다운로드를 시도합니다.
 * 4) 이미지를 다운로드하고 나면 네트워크 부팅 클라이언트에서 이미지로 부팅합니다.

이 개요 내용에 따라 역방향 ARP 데몬과 TFTP 데몬 프로그램을 설치해야합니다.

역방향 ARP 데몬
역방향 ARP 데몬은 이미 시스템에 설치되어 있습니다. 꾸러미의 일부입니다.

rarpd 일반 요소 설정 :

파일을 설정해야합니다. 이 파일에는 어떤 호스트가 요청했을 경우 에서 응답해야 하는지, 어떤 주소로 응답해야 하는지 나타냅니다.

형식읜 NIC의 MAC 주소이며 머신은 네트워크 부팅을 수행하고 이 언급한 호스트 이름을 부여받습니다. 공백은 MAC 주소를 호스트 이름과 구분하며 각 항목은 한 줄에 기입합니다. 다음은 sparc-netboot.gentoo.org 이름을 가진 호스트에 대한 예제입니다:

에 호스트를 추가하려 한다면, 요청을 받을 때마다 파일을 점검하므로 서비스를 다시 시작할 필요가 없습니다.

호스트 이름 해석 :

에 있는 각 항목에 호스트 이름이 붙어있다면 네트워크 부팅 서버에서는 각 호스트 이름을 IP 주소로 해석할 수 있어야합니다. 두가지 방법으로 해결할 수 있는데, 파일을 쓰거나 네트워크 부팅 서버에서 사용하는 이름 서버를 활용하는 방법입니다.

호스트 이름을 해석하는 항목은 네트워크 부팅 서버에 젠투를 설치했을때 이미 본 것과 매우 유사해보입니다. 우리 예제에서는 sparc-netboot.gentoo.org 호스트의 IP 주소가 10.0.1.15라고 가정하며 항목의 모습은 다음과 같습니다:

If you use a nameserver, then the DNS server administrator will need to add a record for the hostname, in our example sparc-netboot.gentoo.org, to point to the appropriate IP address. Please consult your DNS server administrator and/or the documentation for the DNS server's DNS software for how to add the entry.

rarpd 설정

First, we will need to determine the options to use for. While there are more options than we'll cover here, these options should get you started As there is currently no script for, an entry will need to be added to  if you want to enable  services at boot time. A sample entry is as follows:

An explanation of the above options (as taken from the man page):


 * Be verbose.
 * Do not check for the presence of a boot image, reply if MAC address resolves to a valid IP address using database and DNS.
 * eth0 represents the interface which should bind to.

더 많은 옵션은 를 참고하십시오.

tftpd 데몬
Here there are two options for a TFTP daemon, and. You only need to install one of the TFTP daemons for proper operation.

tftpd 일반 요소 설정

Each TFTP daemon will need a directory from which to serve files to tftp clients. The directory we will use for this howto will be. This will appear as the root directory to the clients when requests are received. Additionally, we'll setup the system to run the TFTP daemon with the user and group nobody.

If the directory you have chosen does not currently exist, it will need to be created with the command. The command for the example is:

Then we will need to change the owner of so that it is owned by user nobody and group nobody:

atftp 데몬
First, install the package as follows;

After the atftp has been installed, it will need to be configured. If tftpd services are desired at boot time, an entry to will need to be added as  has no, , or  scripts of its own. If you want to use or  for controlling the tftpd service, please see their respective man pages.

Below is an example entry for atftpd in.

An explanation of the above options (as taken from the man page);


 * Increase or set the logging level. No args will increase by one the current value. Default is LOG_NOTICE, see syslog(3) for log level. Current value range from 0 (LOG_EMERG) to 7 (LOG_DEBUG).
 * Run as a daemon. Do not use this option if atftpd is started by inetd.

더 많은 옵션은 를 참고하십시오.

tftp-hpa 데몬
First, install the package:

tftp-hpa comes with an and the accompanying  configuration file. Check to make sure that INTFTPD_PATH and INTFTP_OPTS variables in match the values below:

The TFTP daemon can then be started via the script:

For more options, consult.

클라이언트에서 활용할 tftpboot 이미지 준비
Make sure you have an image you want to use for netbooting. Please check the local Gentoo distfiles mirror for the appropriate image. We'll assume you are planning to boot using the image.

Once you have an image, copy the image into :

Now, when the netboot client makes a TFTP request, it looks for a file that is the hexadecimal number of its current IP address, and on some platforms an suffix. The hexadecimal number should use capital characters.

So for our example IP address, 10.0.1.15, let's look at its hexadecimal equivalent:

So for the example netboot client, it would look for a file named when it tftpboots.

Iif you are really, really lazy (like me), you can netboot the host to get the filename the client is looking for from the netboot server logs.

Make sure that both the and TFTP daemon you've chosen are currently running, then boot the host as described below in.

The client will appear to hang after the boot net command is issued. Then on the netboot server, check the system logs for an entry for.

An example entry from a netboot server running and  looks like:

The filename is shown above after "filename" in the log entry, which in this case is.

As a way to keep track of what netboot image you are using, and to allow multiple machines to use the same netboot image, you can use a soft link to create the file with the hexadecimal value. To create this using our sample sparc64 host and the, use the following command:

Now everything should be set for netbooting!

클라이언트 넷부팅
From OpenBoot PROM (OBP) on the SPARC, enter the command;

Other methods for certain machines are:

This will initiate the networking booting process. A constantly changing string of hexadecimal digits should appear. When the image has finished loading, the kernel will take over and start the OS booting process. In the case of our sparc64 install image, you will be left at a shell prompt from which you can begin the install process.

문제 해결
Building the prerequisite software

If the netboot server is a Gentoo Linux system and experiences problems after installing the rarpd and tftpd packages, please search the Gentoo Forums and Gentoo Bugzilla to see if this problem has been encountered by anyone else. If it has not, or the solutions found do not work, then please open a new bug.

I've issued the boot net command but it appears to hang.

This is presumably because the file your system is trying to load from the tftpboot server is not available. On a SPARC system, you would probably see the following:

Double check that the file the client needs does exist in. You can confirm the filename it is requesting by looking in the system logs. Also, once this file exists, the client will try to load it. Sometimes, when the file is missing originally, it will freeze downloading the file once it appears. To resolve this, just get back to an OBP prompt, and issue the "boot net" command again. The host should then start downloading the tftpboot image and boot the OS.

I'm trying to netboot, but all I see are "Timeout waiting for ARP/RARP packet" messages.

This could be due to a few different problems:


 * 1) Make sure the entry in  exists for the client in question. If the MAC address is incorrect and/or the netboot server cannot resolve the hostname for the client, it cannot respond with the needed information.
 * 2) Verify that the network hub or switch the netboot server and client are connected to allow RARP traffic to flow freely. If the client's request cannot reach the server, or vice versa, the host will be unable to continue.
 * 3) No one is responding to the RARPD request because no services are listening. Verify that the  service is up and running.
 * 4) The client does not think its NIC has a link to the network hub/switch it is plugged into. Check to see if the NIC and the port on the network hub or switch has a link light. If the link light is on, check to see what the setting of tpe-link-test? is in OBP with the command;  . You should receive something like . The first column represents the parameter name, the second column shows the current value for the the parameter, and the third column shows the default value for the parameter. In the example above, we can see that the current value is false, which means that the client is not checking to see if the client and network hub or switch can establish a link before issuing its RARP request. Often times this can cause the problem.

To change the value of tpe-link-test? from an OBP prompt, issue the following command:

This shows the value of tpe-link-test? is now true. Try netbooting the client again.