This process is machine-dependent; follow the procedure
for Intel® Itanium®-based or PA-RISC-based, depending on your
system type.
Procedure
for Itanium®-based machines
Edit the /etc/bootptab file (don't
worry that it appears to be [Read-only]):
# vi /etc/bootptab
Add an entry for your client. A typical bootptab file has a generic, default client specification
defined. In this example, ignite_defaults is that entry. If your bootptab has a different
default specification, substitute it for ignite_defaults. The MAC address should be in hexadecimal,
but without the leading “0x”.
Edit the /etc/opt/ignite/instl_boottab file (don't worry that it appears to be [Read-only]):
# vi /etc/opt/ignite/instl_boottab
Add an entry for your client. If a network entry
already exists for your client, you may edit it so it looks like the
entry below. The client's MAC address should be in hexadecimal, with
a leading “0x”.
client_IP_address:client_MAC_address::reserve
Save the /etc/opt/ignite/instl_boottab file and exit vi:
:wq!
Explore
You can get the MAC address of the client by using the lanscan command. You may use any MAC address that is physically connected
to the network. Note that the lanscan command reports
the MAC address with a leading “0x”, which must be removed
before entering it in the /etc/bootptab file.
The leading “0x” is required in the /etc/opt/ignite/instl_boottab file.
The /etc/opt/ignite/instl_boottab file includes extensive descriptive comments.
Configuring an Ignite-UX server for booting clients is discussed in the section on making
configuration decisions for Ignite-UX servers in the Ignite-UX
Administration Guide found at http://www.docs.hp.com/en/IUX/infolib.html.