10.0.0.1:/var/opt/ignite/clients /var/opt/ignite/clients"

NOTE: Retrying: "/usr/sbin/mount -orw 10.0.0.1:/var/opt/ignite/clients /var/opt/ignite/clients"

NOTE: Retrying: "/usr/sbin/mount -orw 10.0.0.1:/var/opt/ignite/clients /var/opt/ignite/clients"

...

The messages continue until either the amount of retries given in _hp_nfs_mount_retries is exceeded or the NFS file system mounts successfully.

_hp_tftp_cmds

The _hp_tftp_cmds string variable can be specified in the INSTALLFS file to supply additional instructions to the tftp commands that are used to transfer data during an installation. The commands supplied with this variable are passed as input to the tftp command along with the usual commands supplied by Ignite-UX. The most likely use of this would be to modify the retransmission-timeout (rexmt) and overall timeout (timeout) values. The default values that Ignite-UX uses are rexmt=2 timeout=25. (Refer to tftp(1) for more details). The string assigned to this variable should contain one tftp command statement per line. For example:

init _hp_tftp_cmds="rexmt 5 timeout 40"

Setting this variable can increase the number of retransmissions and the timeout. You may want to increase these values if the system being installed is a long way (network-wise) from the Ignite-UX server or if you have a fairly unreliable or overloaded network.

_hp_hide_other_disks

The _hp_hide_other_disks string variable can be set to one or more space-separated hardware paths of disks that should be "hidden" from being configured or otherwise modified during the install. It allows more disks to be hidden than what is provided by the hide_boot_disk keyword.

This variable is not especially useful for installation purposes, as you need to know all of the disk hardware paths that need to be hidden, which is difficult at installation time unless you know exactly what is in the system beforehand and what it looks like.

This is more useful during recoveries as Ignite-UX currently does them, as you can ensure that some disks cannot be accessed or modified during a recovery session.

_hp_saved_detail_level

The _hp_save_detail_level internal string variable is used in configuration files that have been created by a Save-Asoperation in the Ignite-UX GUI. Like _hp_cfg_detail_level, it contains a list of option characters that represent which aspects of the configuration file have been modified. The format is identical to the _hp_cfg_detail_level variable.

You should not use this variable in custom configurations. If you are using itool or other Ignite- UX internal commands to create configuration files that place this variable into a configuration file, you should remove any reference to this variable.

100