Successful System Cloning using Ignite-UX

PHSS_30180 OpenGL 1.1 Run (PA2.0 only)

PHSS_30183 DDA Run (PA2.0 only)

PHSS_30184 PEX 5.1 Dev (PA2.0 only)

PHSS_30185 PEX 5.1 Run (PA2.0 only)

If these products are needed on a PA-RISC 1.1 system as well, they would no longer work because

the patches are newer.

A good general guideline is to create golden images on the lowest common denominator

hardware, for example, PA-RISC 1.1 systems if you have a mixture of PA-RISC 1.1 and 2.0

hardware. With very different architecture types, for instance nPars capable systems vs. non-nPars

capable systems, some software might not be configured correctly if the golden images or recovery

archives used for cloning were created on non-nPars capable systems; the reverse is true also.

Example 3

Consider the following issue that relates to golden images and cloning from a non-partitionable

system to a partitionable one.

HP Instant Capacity (iCAP) versions 6.x and 7.x only install onto partitionable systems. If you create

a recovery archive for cloning or a golden image for installation on a non-partitionable system and

clone or install it, the system will not have any iCAP software loaded.

This will cause problems for partitionable systems because the iCAP WBEM provider will not be

installed.

This WBEM provider is responsible for authorizing certain activities performed by the various nPar

commands, such as parcreate(1M), parmodify(1M), and parremove(1M) on iCAP systems.

The iCAP WBEM provider must be present, or it cannot be determined whether the system is an

iCAP system or not. The nPar commands may refuse to work without the presence of the iCAP

software (specifically, the iCAP WBEM provider).

The lack of iCAP software on partitionable vPars systems is likely to cause problems, as well.

Note that this problem is not an issue with iCAP versions 8.x and onward.

Do I have kernel tunables set such that cloning cannot work?

Ignite-UX will recover or clone a system using the kernel tunables that were set in the recovery

archive. You can set kernel tunables to consume a large amount of physical memory. If you're

cloning a system and the target system has less memory, it is possible that you may not be

successful in cloning the system.

Let us look at the buffer cache as an example. If you have nbufs and bufpages set to zero, the

dynamic buffer cache will be used. If either or both nbufs and bufpages are set, you will have

a static buffer cache. This buffer cache will occupy real memory and needs to be allocated during

the system startup.

For example, if you have an rp8420 with 16GB of memory and bufpages has been set to

260000 in the system file then the buffer cache is static and is just over 1GB in size. If you attempt

to clone this system to an N series system with 1GB of memory the following occurs on first boot:

panic: Insufficient buffer cache memory

The system panics on first boot because there is not enough memory to allocate the buffer cache so

the cloning attempt fails.