instl_bootd.1m (2012 03)

i
instl_bootd(1M) instl_bootd(1M)
port +1 becomes the client port (
instl_bootc). This option is useful if more than
one daemon is in use, or if the default ports conflict with another service. Some
clients may only specify a limited set of port numbers. When using a non-default
port , ensure it is set to a value that may be matched by the client hardware.
-b boot_file Change the boot file path from the default
/opt/ignite/boot/boot_lif
to
boot_file. boot_file is a Logical Interchange Format (LIF) volume that the client
uses to access other boot utilities (see lif (4), hpux (1M) and isl(1M)). boot_file must
be accessible using the
tftp service (see tftp (1)).
instl_boottab Use the file instl_boottab instead of the default file
/etc/opt/ignite/instl_boottab
as the source of available IP addresses to
allocate to clients. See below for a description of this file.
-? Displays the help screen.
instl_boottab Description
The instl_boottab file contains the list of temporary IP addresses used by clients during the initial phase
of their boot process. A permanent IP address for the client is prompted for and used when the boot pro-
cess is complete, at which time the temporary IP address may be reused to service other boot requests.
The instl_boottab file may contain one or more IP addresses. If it contains no addresses, the server will
not accept boot requests.
The following is a sample instl_boottab file:
# This is a comment line
1.23.45.67 # A single entry.
1.23.45.68:::reserve # Reserve when allocated.
1.23.45.69:080009123456:19930225100240:reserve # Reserved
1.23.45.70:080009123457:19930225111433
Comments are denoted by the # character and may be used anywhere except between fields. Blank lines
are also allowed. A template instl_boottab is provided in
/etc/opt/ignite/instl_boottab
and
contains a header comment explaining the syntax and sample entries, which are commented out.
Each non-comment line of the instl_boottab file contains one IP address entry with the IP address
specified in "dot" notation (for example, 12.34.123.89). In addition to the IP address, each entry may con-
tain three additional fields, each separated by the
: (colon) character. The additional fields may be
empty or absent. All four fields are defined as follows:
Field 1 Defines the IP address of the entry in "dot" notation. This field cannot be empty and must
begin in the first column of the line.
Field 2 Indicates the LAN card station address of the last client to use the entry. It is added
automatically by
instl_bootd, but may be added manually and is useful when field 4
is set to reserve.
Field 3 Indicates the date and time (in YYYYMMDDhhmmss format) when the entry was last
allocated. This field is updated by
instl_bootd.
Field 4 May be set manually to the keyword
reserve, to indicate that the entry may be allo-
cated only to the client with a station address matching field 2. If field 2 is empty, the
entry may be allocated to any host. After allocation, field 2 is updated to indicate the
client to which it is allocated. Once field 2 is set, the entry cannot be allocated to any
other client.
When
instl_bootd receives a boot request, it searches instl_boottab for an IP address issued to the
client during a prior boot request. If the search is unsuccessful, instl_bootd searches for the IP
address with the oldest time stamp.
An IP address may be marked with a
reserve keyword, which causes instl_bootd to allocate the
address to the client specified in field 2. Once a reserve address is allocated to a client, it cannot be
allocated to a different client unless instl_boottab is manually edited to change the reserved status.
Once an IP address is allocated to a client,
instl_bootd updates fields 2 and 3 of instl_boottab. Field
2 identifies the client by its LAN card station address; field 3 indicates the date and time the allocation
occurred.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: March 2012