With the proper authorization, you can set configuration parameters to be used by the PROM during a WAN boot. If set, these parameters take precedence over any default configuration values from the DHCP server for those parameter.
At a minimum, you must provide the following information to the OpenBoot PROM:
IP address of the booting client
Name of the boot file
IP address of the system that is providing the boot file image
The subnet mask and IP address of the default router might also be required.
You specify network parameter settings to PROM through the network-boot-arguments variable. The variable supports the following parameters:
IP address of the TFTP server
DHCP client identifier: this can be set to any unique value that the DHCP server allows. For AI clients, this value should be set to the hexadecimal hardware address of the client, preceded by the string 01 to indicate an ethernet network. For example, an Oracle Solaris client with the hexadecimal Ethernet address 8:0:20:94:12:1e uses the client ID 0108002094121E.
Maximum number of DHCP retries
File to download by using TFTP or URL for WAN boot
IP address of the boot client (in dotted-decimal notation)
Host name to use in the DHCP transaction
HTTP proxy server specification (IPADDR[:PORT])
IP address of the default router (in dotted-decimal notation)
Subnet mask (in dotted-decimal notation)
Maximum number of TFTP retries
To set network-boot-arguments parameters, use the following syntax:
$ eeprom network-boot-arguments="protocol,parameters"
Address discovery protocol to be used.
Any number of comma-separated parameters from the previous table. Each parameter must be in key=value format.
For example, for a system with the host name mysystem.example.com and where you allow only 3 DHCP retries, you would type the following:
$ eeprom network-boot-arguments="dhcp,hostname=mysystem.example.com,dhcp-retries=3"
If you supply network boot settings to PROM, then do not use any arguments when issuing the command to boot the system. Otherwise, depending on the arguments you use, some or all of those boot settings you defined would be ignored. From the previous example, if you specify dhcp when booting, the process will use DHCP, but will ignore the settings for host name and DHCP retries.