Operating System - HP-UX
1834484 Members
3901 Online
110067 Solutions
New Discussion

Ignite-Cloning a System Changes Kernel Params?

 
SOLVED
Go to solution
Alzhy
Honored Contributor

Ignite-Cloning a System Changes Kernel Params?

Is this supposedly the normal behaviour? We're at the latest C release.

Just noticed a clone I made, SHMMAX was set on the orginal machine at 32GB. The cloned machine now shows only 128MB... (0x8000000 bytes)

Hakuna Matata.
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: Ignite-Cloning a System Changes Kernel Params?

Shalom Nelson,

No that is not normal behavior.

Kernel parameters are preserved unless the target system can't meet the settings.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Alzhy
Honored Contributor

Re: Ignite-Cloning a System Changes Kernel Params?

Peace too SEP.

I just tried. It does appear it changes certain kernel params.

Anyone else?
Hakuna Matata.
Aussan
Respected Contributor
Solution

Re: Ignite-Cloning a System Changes Kernel Params?

are you cloning to a similar system?
if so ignite assumes it's the same system and does not rebuild the kernel, to change that you have to set the _CLONING_HP to true
in the additional tab in itool you'll see it
The tongue weighs practically nothing, but so few people can hold it
Alzhy
Honored Contributor

Re: Ignite-Cloning a System Changes Kernel Params?

Aussan,
Thanks for the tip...

Our reference system (where we make clones from) is a SuperDome vPar (128GB of Memory). The 2 clones I've done to rp8420 vPars (16GB and 4GB of memory).

So there is such an ignite param... Wil try it..

Thanks!
Hakuna Matata.