installing on differend hardware

[Verlinden]

I made an Golden image (make_sys_image) of an C3600 system. I would like to use it to install a J5600 system.
Is this possible?
In the documentation they say you can if the hardware is similar. Where can I check which machines are similar?

[Cheryl Griffin]

Similar hardware usually refers to staying within a machine class, meaning that you could clone a C3600 to another C3600 and potentially C3700s, etc.

The source and the target should use the same install kernels: Crossing hardware platforms, such as going from a C3600 to an J5600 may work if the install kernel is the same, but may fail if other drivers, libraries or patches are required.

Ignite uses the following kernels:
INSTALL - for systems that are 32/64 capable; K,D,R,T,E,F,G,H and I class machines
VINSTALL - Vclass systems only
WINSTALL - 64 bit systems only; Superdome, RP,N,L,A, new workstations
IINSTALL - Itanium

The source must have any required HWE enablement patches needed to build a kernel on the target. You can find these requirements by looking at the Release Notes for the OS and the Support Plus CD and/or HW manuals.

Since a C3600 anda J5600 are both 64 bit only workstations of the same PA8600 level using the same kernel, cloning has a good chance of working (baring no other patch related issues.)
Cheryl

[Pete Randall]

From the Ignite-UX Administrator's Guide (see:
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90750/B2355-90750_top.html&con=/hpux/onlinedocs/B2355-90750/00/00/7-con.html&toc=/hpux/onlinedocs/B2355-90750/00/00/7-toc.html&searchterms=Ignite-UX&queryid=20030228-060720
)

In the "Notes on Cloning Systems" section:


Using make_net_recovery and make_tape_recovery

The make_tape_recovery and make_net_recovery tools are designed to reproduce a system exactly the way it was at the time the snapshot was taken. These tools try to accommodate for cloning in various ways:

* You can change hostname/networking information.


* You can make changes to disks and file systems during the recovery.


* Detect hardware model changes and rebuild the kernel.

However, their attempt to reproduce a system exactly may be undesirable:

* The disk layout is saved "as-is" from the original system and does not have flexible logic to accommodate disks of varying sizes or locations.


* Hardware instance numbers for devices that exist at the same paths between systems have the instance numbers preserved from the original system. This can cause non-contiguous assignments in instance numbers. Which is usually only a cosmetic problem.


* Many files that are specific to the system the recovery image was taken from, are preserved. This includes many log files, etc.


* When the kernel is rebuilt (in the "cloning" situation), drivers may be added as needed by the hardware, but unused drivers will not be removed.



Pete