Reconfiguring kernel under vPars!

[Abdul Salam H S_2]

Hi,

I would like to clarify my doubt regarding kernel tuning under vPars. After changing the parameters and rebuilding in Vpars mode, when it reboots, it is crashing the other virtual partition also.Or is it needed to be booted in normal non-vPar mode for reconfiguring the kernel? I feel that as the kernels are independent of the partitions, it shouldn't behave this way.

Although, I was able to reboot one partition while the other one was still up and running earlier, my system has suddenly started giving a new problem. Now, its crashing the other partition, whenever I issue a shutdown or reboot command.

Is there any latest patches to be loaded for this issue?


Thanks and Best Regards,

Abdul Salam

[Michael Steele_2]

What syntax with the shutdown command are you using? Use shutdown -r now, not -R or -H/h.

What model server is this, RP8400?

What version of vpars, 2.1?

In rc.log are on either node are there any complaints or error messages from the /stand/vpmon?

[Michael Steele_2]

Isn't it necessary for you to update all vpars when re-making a kernel?

"...Keep in mind that this procedure needs to be performed for all HP-UX 11i operating systems that will run a Virtual Partition. Kernel creation and modification can also be done in SAM, as described in Chapter 11...."

Why don't you try SAM?

[Abdul Salam H S_2]

Thank you Frederick,

The system is rp5470 with the following config:

There are 2 vpars.

2 * CPUs / 4GB RAM for each partiton.

The vpar version is :

T1335AC A.02.01.00 HP-UX Virtual Partitions

VPARMGR B.11.11.01.01

I'm doing the kernel parameters tuning through SAM only.But after rebuilding the kernel after making the modifications, it will obviously ask for a reboot.And while rebooting, it is causing the other partition also to crash.

Both partitons are working normally.But I'm facing problem only while rebooting.

The command I'm using for reboot is either
shutdown -h 0 or
shutdown -r 0

The details of the config are attached


Thanks and Best Regards,

Abdul Salam

[KCS_1]

hi, Abdul Salam

Check your configuration and look at my attached file ,again.

you may some crue from my attached file.

have a good job!!

[Michael Steele_2]

Note to Patrick: Couldn't read your attachement.

Abdul:

Let's bypass SAM since it probably needs to be patched up.

Can you list out the kernel parameters you want to change? For example:

cd /stand/build

kmtune -q dbc_max_pct -l
-or-
kmtune -q dbc_max_ptc
-or-
kmtune -l

Here's how you change the kernel parameter values:

kmtune -s dbc_max_pct=35 -S /stand/build/system

Then it's:

mk_kernel -s /stand/build/system

kmupdate

Repeat procedure on other node before:

shutdown -r now

[Victor M. Gomez Hornill]

We are also suffering a similar problem.
We have 3 vPars sharing just one physical server.
When we start one of the virtual partition, the others seem hang (they dont respond to ping during 5-7 minutes).
After that, the partition finish to start and the rest begin to respond (the ping).
In the case of an vPar TOC, all the rest hang 50-60 minutes. After that time (one hour), they start to work as normal.

It seems to be a vPar A.02.01 software bug, as our HP Support at Spain has told us.
He has recommeded us upgrade it to vPart to A.02.02 and then apply the patch PHSS_28764.

Kind regards,

Victor

[Victor M. Gomez Hornill]

You will probably obtain the same behaviour in any case of "rebooting", not only after rebuilding the kernel.

F.Y.I.
We have six physicals server, sharing 3 vPars, all of them..

And this behaviour (vPars hanging when one of them is restarting) only happens in ONE of the server, and only in one of the vPars.

Best regards,
Victor