Causes of an LED 666 During a Sysback Network Boot

Contents

This document gives a summary of the causes and recovery procedures of an LED 666 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.

An LED 666 occurs when Phase 2 of the cfgmgr command fails during a Sysback network boot.

An LED 666 occurs during a network boot when the /usr file system has not been exported on the server with root permissions for the client.

SOLUTION

Edit the /etc/exports file and change the line starting with /usr to provide root permission to all hosts performing a network boot. If the text access= appears on the line, all hosts after that text are exported without root permission.

EXAMPLE

For instance, to export node4 with root permission do the following:

    cd /etc 
    cp filesystems filesystems.old 
    vi filesystems 

Change:

    /usr -ro, root=node1,node2:access=node3,node4 

to:

    /usr -ro, root=node1,node2,node4:access=node3 

    exportfs -u 
    exportfs -a 
    exportfs   (to verify the change took place) 

If you followed all of the preceding steps and the system still stops at an LED 666 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 preceding avenues for assistance may be billable.

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

[ Doc Ref: 90605189814762     Publish Date: Mar. 06, 2001]