Storix Software SBAdmin AIX System Recovery Guide - Manual (Page 23)

Storix System Backup Administrator 23 Version 8.2 AIX System Recovery Guide
6. Be sure that the bootpd and tftpd daemons are enabled on the boot server. Check the /etc/inetd.conf file
on the boot server to ensure that these daemons are not commented out (not preceded with a #). If so,
uncomment these lines by removing the “#”, then type “refresh –s inetd”.
7. After initiating the network boot from the client, check to see if the bootpd daemon was started on the boot
server. This daemon will usually remain running for several minutes after it is started, even if the boot fails.
Use the command “ps –ef | grep bootpd” on the server to check for the existence of this process. If
the process does not exist, the boot server did not receive a bootp request from the client. Check the
server’s IP address you entered in the BOOTP information, and try performing a “ping” from the client to
check network communication to the boot server. There is an option to “ping” the server from both the
BOOTP menu and the SMS menus.
Determining the Network Adapter Hardware Address
Some systems require that the adapter hardware address be used to network boot a client. In other cases, you
can prevent the need to enter the client and server IP addresses into the BOOTP screen if the hardware
address of the client is known to the boot server. This requires that the network adapter hardware address be
entered when
setting up the client for network installation . The steps to obtain the network adapter hardware
address of the client differ widely depending on the platform and system model. If you do not know how to
determine the adapter hardware address, you can find this information on the screen by initiating a network
boot operation (even if the boot is unsuccessful).
LED Codes
This chapter contains a list of the system LED codes that may appear when booting or installing from a System
Backup . Many of the LED codes are for information only, usually when there is no system console available,
and many indicate an error in the boot or install process.
Many of the LED codes will only appear during a no-prompt installation . This is because there may not be a
system console attached, and the LED is used to provide information to the user on the progress of the
installation, or if an error has occurred requiring user intervention.
The LED codes below are those that are provided by this application. Any other codes that appear are not part
of this product, but normally represent a system software or hardware problem. If the LED code is not listed
here, you should refer to your system software diagnostics documentation for details.
c06 Failed to identify the system type during a tape boot
The bootinfo -B command failed due to device support missing from the boot image which is required
to support the system's hardware. The problem usually is caused from missing SCSI or BUS device
support. You will need to remake the boot tape from a system containing all device support required for
the system to be installed.
c21 Could not bring up boot network
The ifconfig command failed to bring up the boot network. Check that the subnet mask is correct or
remove the subnet mask from the network boot configuration.
c31 Prompting user to select a system console
A prompt should appear on each graphical device and ASCII terminal asking the user to press a key to
select that device as the system console. If there is a graphical device and the prompt does not
appear, then the boot image does not contain the device support required to activate that device. You
must install the graphics adapter device support for the device on the server and remake the network
boot image, or recreate a bootable tape on another system containing the required device support.
c32 User selected a graphical display as a console device