Air Cleaner User Manual
Chapter 13. Network Boot/Installation Configuration
The Sysback Network Boot/Install Configuration options create and configure a
host to provide boot and optional installation services to a client host over the
network.
The SysBack Network Boot functions use the BOOTP protocol to enable a client to
communicate with the boot server. The client sends a BOOTP request across the
network to a server. Then, the server, if configured, responds with the information
that the client needs to contact that server and, subsequently, access the network
boot image.
Once the client has successfully transferred the network boot image, the client uses
this image to boot into maintenance mode and display the System Backup &
Recovery for AIX Installation & Maintenance Main Menu.
Classic Network Boot and NIM Resource Boot
This section explains the differences between the Classic Network Boot and the
NIM Resource Boot.
Classic Boot
The SysBack Classic Network Boot method used in versions earlier than 5,
continues in Version 5 for environments that do not use AIX NIM (Network
Installation Manager) resources.
The Classic Network Boot method relies on the / and /usr filesystems of the boot
server for creating the network boot image. The boot server also fulfills other
processing requirements for the client during the boot/installation process.
Therefore, the boot server must meet certain requirements in order for the boot
client to successfully utilize the boot server’s resources. Specifically:
1. The operating system level of the boot server must be the same level as the
boot client when using SysBack only to boot into maintenance mode. (The
client must boot from the same level as what is currently installed.)
2. The operating system level of the boot server must be the same level as the
installation/restore image used to reinstall the client machine when booting
and installing the client. (The client must boot from the same level as the image
to be installed.)
3. The boot server must have installed any AIX filesets required for the client to
support attached hardware.
Note: If filesets are installed specifically to support a boot client, the server
must be rebooted, and the network boot image updated and recreated
before the client will successfully boot from the boot server.
4. The boot server must have installed kernel filesets to support the processor
type (uniprocessor or multiprocessor) of the boot client regardless of whether
or not the boot server is of the same processor type.
Note: If filesets are installed specifically to support a boot client, the server
must be rebooted and the network boot image updated or recreated
before the client can successfully boot from the boot server.
© Copyright IBM Corp. 2002,2003 13-1