Migrating an Integrity HP-UX 11iv3 Instance to New Hardware

when the target system is deployed, either by specifying it directly on Ignite-UX menus, or by choosing

on the menus to supply the information when the system is first booted.

To remove the pre-existing network information, edit /var/opt/ignite/clients/<target

hostname>/recovery/latest/system_cfg to remove the _hp_custom_sys stanza.

Alternatively, the stanza may be commented out by inserting “#” in column 1 of the lines it contains.

Here is a sample of the _hp_custom_sys stanza that should be commented out:

# System/Networking Parameters

#_hp_custom_sys+={"HP-UX save_config custom sys"}

#init _hp_custom_sys="HP-UX save_config custom sys"

#_h p_custom_sys visible_if false

#(_hp_custom_sys=="HP-UX save_config custom sys") {

# final system_name="<source hostname>"

# final ip_addr["<source NIC hw path"]="<source address>"

# final netmask["<source NIC hw path"]="<source mask in hex>"

# final broadcast_addr["<source NIC hw path"]="<broadcast>"

# init _hp_default_final_lan_dev="<source NIC hw path>"

# final route_destination[0]="default"

# final route_gateway[0]="<source gateway>"

# final route_count[0]=1

# final nis_domain="udl"

# final wait_for_nis_server=TRUE

# final dns_domain="<DNS domain>"

# final dns_nameserver[0]="<IP address of DNS server>"

# is_net_info_temporary=FALSE

#} # end "HP-UX save_config custom sys"

Prior to deploying the target system, determine the network configuration information needed for it.

This is the same information that is needed to cold install the target system from a depot, including

whether DHCP is used to manage the interfaces, IP addresses (if DHCP is not used), subnet masks,

gateways, and optional NIS and DNS servers.

If you prefer to modify the information in the system_cfg file itself, and have multiple network

interfaces on the target system, you may need to identify the hardware path for each NIC prior to

editing system_cfg. See instl_adm(4) for further information about the syntax of the

networking parameters in the system_cfg file.

Step 6: Change a recovery-related variable in control_cfg

The config file /var/opt/ignite/clients/<target

hostname>/recovery/latest/control_cfg contains information specific to deploying a

recovery archive to the same system. In both the move and the clone scenarios, the target is a

different system.

If the target system is a different model from the source system, then the setting of _HP_CLONING

does not need to be changed. However, if the target system is the same model but is configured with

different peripheral devices, you may want to ensure that the kernel is re-built on the target system by

modifying the setting of _HP_CLONING. To do this, edit the file

/var/opt/ignite/clients/<target hostname>/recovery/latest/control_cfg on the

Ignite-UX server and make the following change:

Change:

(MODEL == "<source system model>")

{ init _HP_CLONING = "FALSE" }