7318 TCP/IP Broadcast Boot Configuration

Contents

About this document

This document provides information for configuring an IBM 7318 model P10 or model S20 to boot using a TCP/IP broadcast load configuration. This document was designed for AIX system administrators with a knowledge of AIX administration and the 7318. Using these instructions, a TCP/IP broadcast boot configuration takes about 20 minutes.

In a broadcast load configuration, the 7318 broadcasts a boot request to every host on the network. Hosts that are configured to send the 7318 its load image and configuration file reply to the broadcast. This document contains modules that configure the host for the broadcast load.

This document does NOT contain detailed explanations about the modules and steps used in the configuration methods.

The information contained in this document is valid for AIX 4.x.

The product documentation library is also available:
http://www.rs6000.ibm.com/resource/aix_resource/Pubs/index.html

Remote booting

Assumptions

Requirements

Checking the interface

The host communicates with the network through an interface (tr0, en0, et0, fi0). To configure an interface for TCP/IP, the interface must be active (the words <UP, RUNNING> appear in the flags when the ifconfig command is run).

NOTES:

1. A communication interface is configured on a communication adapter. This means the tr0 interface is configured on the tok0 adapter card, the en0 (or et0) interfaces are configured on the ent0 adapter card).
2. A communication adapter can have multiple interfaces. TCP/IP networks can be configured based on the following adapters:

   ent0     Available 00-02     Ethernet High-Performance LAN Adapter (8ef5) 
   fddi0    Available 00-03     FDDI Primary Car, Single Ring Fiber 
   tok0     Available 00-04     Token-Ring High-Performance Adapter  (8fc8) 
   

For a standard Ethernet interface configured on ent0, enter:

    ifconfig en0 

Sample output:

en0:  flags=8080863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>, 
        inet 9.3.6.32 netmask 0xffffffc0 broadcast 9.3.6.63 

        ifconfig tr0 

tr0:  flags=80a0043<UP,BROADCAST,RUNNING,ALLCAST,MULTICAST>, 
        inet 9.3.6.68 netmask 0xffffffc0 broadcast 9.3.6.127 

If the interface is active (the words <UP, RUNNING> appear in the flags list), continue to the next section, "Checking the tftp daemon".

If the words <UP, RUNNING> do NOT appear in the flags list, configure the interface through SMIT. Enter:

    smit inet 

Checking the tftp daemon

1. Verify that tftp is active. Enter:

       lssrc -ls inetd | grep tftp 
   

   Sample output:

     tftp    /usr/sbin/tftpd       tftpd -n        active 
   

   If the process is active, proceed to the next section, "Checking the tftp file access permissions".

   If the process is inactive or is not listed, continue to start the process by activating the tftp daemon.

2. To activate the tftp daemon, open the /etc/inetd.conf file with a text editor, and search on tftp.

3. If the entry is commented out, uncomment the entry (remove the # sign). Sample tftp entries are shown below:

   For AIX 4.2.x and lower:

      tftp     dgram  udp     wait     nobody   /usr/sbin/tftpd      tftpd -n
   

   For AIX 4.3.x and higher:

     tftp     dgram  udp6    SRC     nobody  /usr/sbin/tftpd         tftpd -n
   

4. Save any modifications and exit the file.

5. Open the /etc/services file with your favorite text editor, and search on tftp.

6. An uncommented, sample tftp entry is shown below:

       tftp 69/udp 
   

7. Save any modifications and exit the file.

8. Refresh the inetd daemon to implement file modifications, enter:

       refresh -s inetd 
   

9. Refer to Step 1 (above) to check for an active tftp process once more.

   If the process is active, continue to the next section, "Checking the tftp file access permissions".

   If you are unable to start tftp, please contact an IBM AIX Technical Specialist.

Checking the tftp file access permissions

1. Open the /etc/tftpaccess.ctl file with an editor.

   NOTE: If the /etc/tftpaccess.ctl file does not exist, either create the file (and allow tftp access to the directories in which the files reside) or continue to the section, "Boot the 7318". If the /etc/tftpaccess.ctl file does not exist, then tftp is allowed access to all directories.

2. Specify the directories to which tftp is allowed access (uncomment or add allow:/usr/lib/cns directory).

   The following is a sample /etc/tftpaccess.ctl file entry with tftp allowed access to the /usr/lib/cns directory:

   ######################################################### 
   #       The following example, when uncommented, only 
   #       allows access to the Diskless Client boot files. 
   ######################################################### 
   allow:/tftpboot allow:/usr/lib/cns 
   

3. Save any modifications and exit this file.

4. Change to the directory in which the load image and configuration file reside.

5. Verify that the permissions for the files are world-readable, enter:

       ls -1 | more 
   

   Correct sample file permissions are as follows:

   -r--r--r--     1 root     system     442532 Jul 25 01:56 cns-p10 
   -r--r--r--     1 root     system    1240228 Jul 24 01:56 cns-s20e 
   -rw-r--r--     1 root     system      17539 Sep 09 1995 p10.cfg 
   -rw-r--r--     1 root     system      43120 Jul 24 01:56 s20.cfg 
   

6. If the file is not world-readable, change the permissions. Enter:

       chmod 444 <filename> 
   

7. Continue to the next section, "Adding the 7318 Entry in the /etc/bootptab File"

Adding the 7318 entry in the /etc/bootptab file

1. Open the /etc/bootptab file with an editor.

2. Add an entry for the 7318 at the end of the file.

   NOTE: Device parameters are listed at the beginning of the file. All entries must be on one line (lines may wrap to the next line), must contain no spaces, and must be separated by a colon. The entry must end with a colon.

   Sample entry:

       cns.ibm.com:ht=ethernet:bf=/usr/lib/cns/cns-s20:ha=00406 
       e000999:ip=1.1.1.2: 
   

   NOTE: The ht=ethernet is mandatory and indicates the format of the hardware address, which will always be Ethernet. This can be an issue for those who are booting across a bridge to Token Ring.

3. Save the modifications and exit the file.

4. Continue to the next section, "Checking for active bootp services".

Checking for active bootp services

1. Verify the bootp daemon is active. Enter:

       lssrc -ls inetd | grep bootps 
   

   Sample output:

       bootps        /usr/sbin/bootpd bootpd /etc/bootptab     active 
   

   If the bootp is active, continue to the next section, "Boot the 7318".

   If the process is inactive or is not listed, continue to start the process.

2. Open the /etc/inetd.conf file with your favorite editor, and search on bootps.

3. If the entry is commented out, uncomment the entry. (remove the # sign).

   An uncommented sample entry from the /etc/inetd.conf file is shown below:

   bootps  dgram   udp   wait  root  /usr/sbin/bootpd   bootpd /etc/bootptab 
   

4. Save any modifications and exit the file.
5. Open the /etc/services file with your favorite editor, and search on bootps.

6. If the entry is commented out, uncomment the entry (remove the # sign).

   An uncommented sample entry from /etc/services is shown below:

       bootps          67/udp                  # bootp server port 
   

7. Save any modifications and exit the file.

8. Refresh the inetd daemon with the file modifications, enter:

       refresh -s inetd 
   

9. Refer to Step 1 (above) to check for an active bootp process. If you are unable to start bootp, please contact an IBM AIX technical specialist.

10. When the process is active, continue to the next section, "Boot the 7318".

Boot the 7318