How to setup Integrity network boot
Abstract
This article shows you how to configure Ignite-UX server to boot Integrity Clients from the network. The Ignite-UX server zx6000 (192.168.2.10) and the Ignite-UX client tifa (192.168.2.17) hosts are used. Both server and client are running HP-UX 11i v3.
The installed Ignite-UX product version is C.7.7.98. Remember that Ignite-UX network booting requires that the client boot network card and one of the servers cards share the same subnet. Use Two-Step Recovery or setup a Boot-helper if this is not possible.
This example assumes that the Ignite-UX server is the only DHCP server accessible from the client boot network interface. Additional configuration may be required if additional DHCP services are running on the same Subnet.
Registered Client
The following assumes that Ignite-UX is already installed with the required bundles to support the releases.
1. Check current Ignite-UX defaults. By default, network boot assumes that installation will be handle on the client console.
If client control from the Ignite-UX server needs after network boot, add the run_ui=false and control_from_server=true entries to the [ I | V | W ]INSTALL file systems using the instl_adm command using the following procedure:
# instl_adm -d > /tmp/defaults # cat /tmp/defaults # instl_adm defaults: # NOTE: Manual additions between the lines containing "instl_adm defaults" # and "end instl_adm defaults" will not be preserved. server="192.168.2.10" netmask[]="255.255.255.0" route_gateway[0]="192.168.2.1" route_destination[0]="default" # end instl_adm defaults.
Append the following lines at the end of /tmp/defaults file:
run_ui=false control_from_server=true
Update the configuration file to all INSTALL file systems.
# instl_adm -f /tmp/defaults
2. Modify /etc/bootptab (DHCP control file) entries to ensure that required network information is delivered to the Ignite-UX client during the hardware and kernel booting. Note the IADEF and tifa tag define the default option for all the clients and the specific IP Address for the host identified by the MAC Address (Hardware Address).
IADEF:\
ht=ethernet:\
hn:\
dn=americas.local:\ # Domain Name (optional)
gw=192.168.2.1:\ # Gateway
sm=255.255.255.0:\ # Subnet Mask
ds=208.133.206.44 200.91.75.5:\ # DNS Server(s)
vm=rfc1048:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48:
tifa:tc=IADEF:ip=192.168.2.17:ha=CA65FD9224B9 # IP Address & Hardware (MAC) Address
3. Uncomment the bootps entry in the /etc/inetd.conf file and verify that the Ignite-UX tftp and instl_boots entries are in place.
...
tftp dgram udp wait root /usr/lbin/tftpd tftpd \
/opt/ignite \
/var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd
...
Test Register Client Network Boot
Scsi(Pun0,Lun0) HP Virtual FileDVD 0.04 ( 80 MBytes/sec)
Scsi(Pun1,Lun0) HP Virtual FileDVD 0.04 ( 80 MBytes/sec)
EFI version 1.10 [14.62] Build flags: EFI64 Running on Intel(R) Itanium Processor EFI_DEBUG
EFI IA-64 SDV/FDK (BIOS CallBacks) [Tue Jun 17 09:30:56 2008] - HP
Cache Enabled. This image MainEntry is at address 0000000000102000
HP AVIO Stor Driver v1.0
HP AVIO LAN UNDI Driver v1.0
FPSWA.EFI preload successful.
FPSWA.EFI start successful.
Scsi(Pun0,Lun0) HP Virtual FileDVD 0.04 ( 80 MBytes/sec)
Scsi(Pun1,Lun0) HP Virtual FileDVD 0.04 ( 80 MBytes/sec)
EFI Boot Manager ver 1.10 [14.62] [Build: Tue Jun 17 09:30:56 2008]
Loading device drivers
Select "EFI Shell [Built-in]" option in the Boot Menu.
EFI Boot Manager ver 1.10 [14.62] [Build: Tue Jun 17 09:30:56 2008]
Please select a boot option
HP-UX Primary Boot: 0/0/0/0.0.0
HP-UX HA Alternate Boot: 0/0/0/0.1.0
HP-UX Alternate Boot: 0/0/0/0.1.0
EFI Shell [Built-in]
Lan Boot
Boot option maintenance menu
Use ^ and v to change option(s). Use Enter to select an optionUse the lanboot select command to start the network booting, select the proper lan card (01) and choose the desired HP-UX Release (2).
Shell> lanboot select
01 Acpi(PNP0A03,0)/Pci(1|0)/Mac(CA65FD9224B9)
Select Desired LAN: 01
Selected Acpi(PNP0A03,0)/Pci(1|0)/Mac(CA65FD9224B9)
Client MAC Address: CA 65 FD 92 24 B9 ..
Client IP Address: 192.168.2.17
Subnet Mask: 255.255.255.0
BOOTP Server IP Address: 192.168.2.10
DHCP Server IP Address: 192.168.2.10
Boot file name: /opt/ignite/boot/nbp.efi
Retrieving File Size.
Retrieving File (TFTP).
@(#) HP-UX IA64 Network Bootstrap Program Revision 1.0
Downloading HPUX bootloader
Starting HPUX bootloader
Obtaining size of fpswa.efi (328192 bytes)
Downloading file fpswa.efi (328192 bytes)
(C) Copyright 1999-2008 Hewlett-Packard Development Company, L.P.
All rights reserved
HP-UX Boot Loader for IPF -- Revision 2.036
Booting from Lan
Obtaining size of AUTO (226 bytes)
Downloading file AUTO (226 bytes)
Obtaining size of AUTO (226 bytes)
Downloading file AUTO (226 bytes)
Obtaining size of AUTO (226 bytes)
Downloading file AUTO (226 bytes)
1. target OS is B.11.23 IA
2. target OS is B.11.31 IA
3. Exit Boot Loader
Choose an operating system to install that your hardware supports:2
Monitor the kernel booting. In this example, Ignite-UX server control is been enable, so a DHCP request will be issue and a menu will be displayed in the console when the system ready to initiate control from the Ignite-UX server. From the Ignite-UX server, X server support and access from the client needs to be enable.
Obtaining size of AUTO (226 bytes)
Downloading file AUTO (226 bytes)
Obtaining size of Rel_B.11.31/IINSTALL (51055320 bytes)
Downloading file Rel_B.11.31/IINSTALL (51055320 bytes)
> System Memory = 4090 MB
loading section 0
.................................................................................................... (complete)
loading section 1
................. (complete)
loading symbol table
Obtaining size of Rel_B.11.31/IINSTALLFS (61341696 bytes)
Downloading file Rel_B.11.31/IINSTALLFS (61341696 bytes)
loading ram disk file (Rel_B.11.31/IINSTALLFS).
.....................................................................................................................
(complete)
Launching Rel_B.11.31/IINSTALL
SIZE: Text:50892K + Data:8336K + BSS:23776K = Total:83006K
Console is on Serial COM1
Booting kernel...
Disabling 8259s
krs_read_mfs: Error 5 opening MFS.
Loaded ACPI revision 2.0 tables.
krs_read_mfs: Error 5 opening MFS.
Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 3891 MB 3891 MB 3891 MB
Kernel : 3891 MB 3891 MB 3891 MB
User : 3286 MB 2913 MB 2925 MB
-------------------------------------------------------------------------
ktracer is off until requested.
NOTE: nm_devvp_lock not a power of 2 or is outside of allowed range: (16)
NOTE: setting nm_devvp_lock to 32
Installing Socket Protocol families AF_INET and AF_INET6
Kernel EVM initialized
sec_init(): kernel RPC authentication/security initialization.
secgss_init(): kernel RPCSEC_GSS security initialization.
rpc_init(): kernel RPC initialization.
rpcmod_install(): kernel RPC STREAMS module "rpcmod" installation. ...(driver_install)
NOTICE: nfs_client_pv3_install(): nfs3 File system was registered at index 11.
NOTICE: nfs_client_pv4_install(): nfs4 File system was registered at index 12.
iether0: INITIALIZING HP PCI/PCI-X 1000Base-T at hardware path 0/0/1/0
System Console is on the Built-In Serial Interface
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: No swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
AF_INET socket/streams output daemon running, pid 31
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B.11.31_LR FLAVOR=perf nfsauth: lookupname: 2
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4188736 Kbytes, lockable: 2879776 Kbytes, available: 3283572 Kbytes
* Preparing to execute init...
======= 02/12/09 00:43:59 EST HP-UX Installation Initialization. (Thu Feb 12
00:43:59 EST 2009)
@(#)Ignite-UX Revision C.7.7.98
@(#)ignite/launch (opt) Revision:
/branches/IUX_RA0809/ignite/src@75250 Last Modified: 2008-08-25
11:39:14 -0600 (Mon, 25 Aug 2008)
* Configuring RAM filesystems...
* Scanning system for IO devices...
* Boot device is: 0/0/1/0
* Searching the network for a DHCP server to supply default networking
information....
This could take up to 30 seconds if a DHCP server cannot be found. If
you wish to cancel the DHCP server search, you may press CTRL-C now.
* Bringing up Network (lan0)
add net default: gateway 192.168.2.1
* Reading configuration information from server...
* NFS mounting clients directory.
* Using client directory: /var/opt/ignite/clients/0xCA65FD9224B9
Anonymous Client
Work in Progress
Control Ignite-UX Client from the Server
This is the output in the client console when local control is disable.
Select Client -> Install Client -> New Install to start the Ignite-UX client installation.
Add any install control information and click [ OK ].
Select the desired configuration or Network archive to install or restore in the Ignite-UX client.
Reference
- Configuring the Ignite-UX Server for Itanium-Based Clients http://www.docs.hp.com/en/5992-5309/ch03s02.html
- Configuring an Ignite Server to Boot Anonymous Itanium-Based Clients http://www.docs.hp.com/en/5992-5309/ch04s03.html
- WFM Case: 3604793115
