Air Cleaner User Manual

604 Configuring the boot network
605 Invalid network boot device provided
The boot server is likely missing device support for either the token-ring,
ethernet, or FDDI adapter. You need to install the appropriate device
support on the server system, reboot the server, and remake the network
boot image for the client.
606 Configuring the boot network.
608 Copying network boot information file from boot server
609 Failed to copy network boot information from boot server
The tftp command failed to tftp the file /tftp/Client Hostname.sbinfo from
the boot server. One of the following usually apply:
1. The file does not have read permissions for all users.
2. The file does not exist.
3. An /etc/tftpaccess.ctl file exists on the boot server but does not provide
access to the /usr/lpp/sysback/netinst/boot directory.
4. On a PCI-based system, you cannot use the leading zero’s for any of
the IP address in the SMS Menu. Even though the first tftp command
works, the second one run will fail.
Rebuild the network boot image on the server and add the network boot
client, making sure all values are correct.
610 NFS mount of /usr fleshiest from the server is hanging
The /etc/exports file does not have permissions for the client to mount
/usr. Type exportfs on the server and look for the line starting with
“/usr”. Make sure the client hostname is included on the line and that
/usr is exported with root permission.
Example of output:
/usr -ro,root=node1,node2
In the above example, only node1 and node2 are exported. Add the
network boot client again and verify that all the values are correct for the
server’s IP address, the gateway, and the subnet mask for the client.
611 NFS mount of /usr fleshiest from the server failed
This often means that /usr fleshiest was not exported to the client (see
LED 610). There are known problems in AIX Version 4.1 that will affect
SysBack network boots. These problems are fixed in the following file set
levels:
v bos.adt.prof 4.1.4.5
v bos.rte.libc 4.1.4.5
v bos.net.nfs.client 4.1.4.4
v bos.sysmgt.quota 4.1.3.1
v bos.net.tcp.client 4.1.4.4
Make sure the above filesets are at this level or later. If updating the
filesets, reboot the server, then remake the network boot image on the
server.
613 Configuration of gateway failed during network configuration
Appendix C. LEDS C-3