Causes of an LED 611 During a sysback Network Boot

About This Document

This document gives a summary of the causes and recovery procedures for a LED 611 during a sysback network boot. The information in this document has been verified for AIX Versions 3.2, 4.1, 4.2 and 4.3. It has also been verified for sysback.obj 3.3.3 and sysback.rte 4.1.x.x.

Causes of an LED 611

An LED 611 occurs when the NFS mount of the /usr filesystem from the server fails during a sysback network boot.

Causes and Recovery Procedures

When the following conditions result in an LED 611, perform the solutions shown:

1. The /etc/exports file does not have the correct permissions for the client to mount /usr.

   SOLUTION

   Execute the following command:

    
       exportfs 
   

   Look for the line starting with /usr. Make sure the client hostname is included on the line.

   EXAMPLE

       /usr -ro, root=node1,node2 
   

   In the above, only node1 and node2 are exported to NFS mount /usr. If your client's hostname is not included on that line, add the network boot client as follows:

   1. Enter:

          smitty sysback 
      

   2. Choose one of the following:

          Configuration Options 
          Network Boot Configuration 
          Add or Change a Network Boot Client 
      

   3. Make sure each entry is filled in correctly, as shown:

      Client network adapter type             [token-ring] 
      Client platform/kernel type             [rspc] 
      Client hostname                         [mars.aix.dfw.ibm.com] 
      Server IP address                       [9.19.129.186] 
      Client gateway address (optional)       [9.19.141.241] 
      Client subnet mask (optional)           [255.255.240.0] 
      Client adapter hardware address (optional)    [] 
      

   4. Verify by entering the following command:

          exportfs 
      

      Look for the line starting with /usr. Make sure the client hostname is included on the line.

2. The /etc/exports file does not have an entry for /usr.

   SOLUTION

   Enter the following command:

       exportfs 
   

   If there is no entry for /usr in the /etc/exports file, follow the steps in the "Solution" section of Step 1.

   If you get the following error message when adding the network boot client:

   Configuring network boot for client... thumper.aix.dfw.ibm.com

       /usr ro,root=thumper.aix.dfw.ibm.com 
   

   Starting NFS and BOOTP services...

       exportfs: /usr: sub-directory (/usr/lpp) already exported 
       /usr not found in /etc/exports 
   

   The above messages indicate that the client has been configured, but you must correct the problem with the export function before booting the client.

   1. Enter:

          exportfs 
      

      If a subdirectory for /usr that is not a filesystem is already in the /etc/exports file, then you cannot export the parent directory /usr.

      Example output from the exportfs command is shown below:

          /usr/sys/inst.images -rw 
          /usr/lpp             -root=mars,access=mars 
      

      In this example, /usr/sys/inst.images is its own filesystem, but /usr/lpp is still part of /usr filesystem. You cannot export /usr until you remove /usr/lpp from the /etc/exports file (see Step b).

   2. Execute the following command to remove /usr/lpp from the /etc/exports file.

          /usr/sbin/rmnfsexp -d /usr/lpp  -B 
      

   3. Re-add the network boot client as described in Step 1.

   4. Verify by entering the following command:

          exportfs 
      

      Look for the line starting with /usr. Make sure the client hostname is included on the line.

3. This could be a defect that existed in sysback.obj 3.3.1.x - 3.3.3.5. It is fixed with sysback.obj 3.3.3.17.

   In the U.S., you can order an update of sysback by calling 800-225-5249. Ask to speak with the Sysback Marketing Team. Outside the U.S., contact your AIX sales representative.

   Install the new version of sysback, and rebuild your boot image:

   1. Enter:

          smitty sysback 
      

   2. Choose:

          Configuration Options 
          Network Boot Configuration 
          Configure/Update a Network Boot Image 
      

4. There is a known defect in AIX 4.1.4 that affects NIM as well as sysback network boots. This defect is fixed in the fileset levels:

   APAR: IX54851

        FileSet Name         Level 
       --------------       ------- 
       bos.adt.prof         4.1.4.5 
       bos.rte.libc         4.1.4.5 
       bos.net.nfs.client   4.1.4.4 
       bos.sysmgt.quota     4.1.3.1 
       bos.net.tcp.client   4.1.4.4 
   

If you followed all of the above steps and the system still hangs at an LED 611 during a network boot to Service mode, you may want to pursue further system recovery assistance from one of the following:

• Local branch office
• Your point of sale
• Your AIX support center

All of the above avenues for assistance may be billable.

For reasons of time commitment and the integrity of your AIX operating system, the best alternative at this point may be to reinstall AIX.