Successful System Cloning using Ignite-UX

13
• Does Ignite-UX run on the system?
•
Upgraded systems and older versions of Ignite-UX
•
Does the recovery archive or golden image support the system?
•
Am I going to clone a system that has the same hardware model string?
•
Do I have a high enough firmware revision to run the version of HP-UX that is in the Ignite-UX
installation kernel?
•
Do I have any HP-UX applications loaded that are known to have problems after being loaded
onto cloned systems?
The sections that follow describe these additional issues for your consideration.
Does Ignite-UX run on the system?
Previously, support for new systems and how to determine what OE and Ignite-UX version are
required was described. By way of the following example, this section presents the symptoms that
you may encounter when Ignite-UX does not support a given system at all.
Example
You have the 11i v1 OE media from March 2004 in a depot and want to install it onto an rp3440
with Ignite-UX version B.3.3.x. The boot disk is on a SAN device via an A6795A (2GB XL2-based
FC HBA). What potential problems might you encounter?
In this case the installation kernel panics upon boot with panic messages similar to the following:
Stored message buffer up to panic:
PDC_MODEL_CPU_ID returned 0x14
System Panic:
linkstamp: Wed Jul 11 16:30:57 MDT 2001
_release_version: @(#) $Revision: vmunix: vw: -proj
selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' --
cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: set_machine_parameters_64: Unidentified cpu type returned from
PDC_MODEL
PC-Offset Stack Trace (read across, top of stack is 1st):
0x00210590 0x002640c8 0x00263ee8
0x004a1e2c 0x00205ae4 0x002008b4
End Of Stack
In this case, the installation kernel does not support the system being installed or recovered. You
need to upgrade the version of Ignite-UX you are using, in this case to version B.5.3.x.