The TUI itool has the same functionality as the GUI itool that runs on the Ignite-UX server. Navigate the TUI using the Tab to move around and by pressing Enter to make selections. See “The client installation configuration interface” (page 117) for detailed information on using the client installation interface to configure a client's installation.
TIP: Shortcut keys also work in the itool TUI, but similar to the NETWORK CONFIGURATION screen, you cannot use them when positioned at an input field. Using shortcuts can significantly reduce the time required to navigate the TUI itool.
When the installation has been configured, select Go! to start the installation.
Managing speed and duplexing of LAN interfaces executing network boots
The default behavior of the kernel at boot up is to automatically negotiate the speed and duplex settings of all LAN interfaces that support this feature. This default behavior is later modified in HP-UX by startup scripts that can set any speed and duplex rather than allow the LAN interface to automatically negotiate these settings.
When you use an install kernel with Ignite-UX to install or recover a system, there are no startup scripts. If a Fast or Gigabit Ethernet LAN interface fails to autonegotiate, it defaults to 100 Half-Duplex regardless of the speed and duplex settings at the other end. Mismatched speed and duplex settings can cause serious performance and reliability issues when using Ignite-UX.
You can adjust the speed and duplex settings when using Ignite-UX with the _hp_lanadmin_args variable. The LAN interface Ignite-UX uses must be brought up before the Ignite-UX server can be contacted so this keyword serves no purpose if it is located in the normal configuration files used by Ignite-UX. In view of this, _hp_lanadmin_args must be configured in the install file system on the server that it boots from. If the client boots using a boot helper, _hp_lanadmin_args must be configured on the boot helper system not the Ignite-UX server.
NOTE: In a default setting, modern switches and hubs will autonegotiate the speed and duplex settings with your PA-RISC or Itanium-based system. However, in some cases you may want to set the speed and duplex settings to certain values for your environment. For example, the switch may always fail to autonegotiate with your system. If you do not use autonegotiation on the switch or hub that your system is connected to, you must provide the correct speed and duplex settings for Ignite-UX using _hp_lanadmin_args. Mismatched speed and duplex settings may cause significant performance issues or failures during recovery.
Almost all Fast and Gigabit Ethernet interfaces support setting the speed and duplex using the _hp_lanadmin_args variable for the -Xoption. Some old Fast Ethernet interfaces might not support full-duplex, so consult the product documentation for any network interfaces you encounter problems with to confirm the speed and duplex settings that each supports.
You can still take advantage of the other options available using the lanadmin command. For more information, see the examples in instl_adm(4) regarding setting the MTU (-M) and Duplex (-S) options of _hp_lanadmin_args.
IMPORTANT: Due to a problem in Ignite-UX in versions prior to B.5.2.x, some parts of the recovery may run with the wrong speed and/or duplex on the LAN interface when the system first reboots and until the final reboot. If this proves to be a problem in your environment, you must ensure that you have installed Ignite-UX version B.5.2.x or later.
Examples
Following are two examples of how to set the duplex in differing situations.
