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

Step 7: Set the system identity on the clone for boot on the target

This step is ordinarily needed for both the “move” and “clone” scenarios, since the MAC address(es)

on the target will differ from those on the source. (The exception to this is the case where your MAC

addresses have been virtualized through Virtual Connect, and you are moving the VC profile to the

new system.)

To set the identity of the target (hostname, mapping of IP addresses to network interfaces, language,

time zone, etc.) perform the following while logged onto the source system as root:

1. Create a sysinfo file modeled on the template supplied in

/etc/opt/drd/default_sysinfo_file. This file contains hostname, IP addresses or DHCP

information, and other customizing information.

If you prefer to wait until the target system boots to supply this information, leave the parameter

SYSINFO_INTERACTIVE set to ALWAYS. Otherwise, comment out this variable and set the

values for other variables in the sysinfo file.

Additional information regarding the content and syntax of the sysinfo file is available in the

sysinfo(4) manpage, packaged in PHCO_39064 or any superseding patch.

A sample sysinfo file, including the required parameter SYSINFO_HOSTNAME, appears below.

SYSINFO_HOSTNAME=myhost

SYSINFO_DHCP_ENABLE[0]=0

SYSINFO_MAC_ADDRESS[0]=0x0017A451E718

SYSINFO_IP_ADDRESS[0]=192.2.3.4

SYSINFO_SUBNET_MASK[0]=255.255.255.0

SYSINFO_ROUTE_GATEWAY=192.2.3.75

SYSINFO_ROUTE_DESTINATION[0]=default

SYSINFO_ROUTE_COUNT[0]=1

SYSINFO_DNS_DOMAIN=ours

SYSINFO_DNS_SERVER=192.2.3.50

2. Issue the command:

drd rehost –f <sysinfo_file_location>

For additional information about the drd rehost command, see the chapter “Rehosting and

unrehosting systems” in the Dynamic Root Disk Administrator’s Guide, available at

http://www.hp.com/go/drd-docs

, and in the drd-rehost(1M) manpage.

Step 8: Mark the clone LUN for identification from the target EFI

It can be challenging to identify the clone LUN after it is moved to the target system. Since the LUN is

partitioned, it is displayed with “fs” entries. However, if multiple partitioned disks are visible from

the EFI menus of the target, an extra “marker” can help to identify the LUN.

To create the marker, issue the following on the source system:

# touch /tmp/move_to_new_hw

# efi_mkdir -d <dsf of EFI partition of clone> EFI/HPUX/DRD

# efi_cp -d <dsf of EFI partition of clone> /tmp/move_to_new_hw \

EFI/HPUX/DRD/move_to_new_hw

Step 9: Move scenario: Disable the source system

If you are moving the system (keeping the same hostname and network identity) to a location on the

same network, shutdown the source system or remove it from the network.