vPar is booting very slow after adding a cell board and memory

[Atindra Ghosh]

I am faceing issue after adding one cell board and 64GB memory in exting nPar. vPar are very slow while booting and after booting also. Also note that this system has icap cpu. Please help if you have any solution.

[Steven E. Protter]

Shalom,

If possible, let the vpar boot and take a look at /etc/rc.log to see where the hang up was.

Then run hardware diagnostics, cstm or mstm or xstm

You've given us very little to work with here.

You might do better reporting this issue to HP hardware and having them dispatch a tech.

SEP

[Torsten.]

We don't even know what server and vPars version you have, nor what "slow" means or what your configuration looks like.

To shorten this, consider to contact HP support directly.

[Atindra Ghosh]

System is HP Intrigity(ia64 SD32B) Superdome, and vPar version is A.04.04.04.

[Steven E. Protter]

Thanks for the additional information.

Please post

parstatus
vparstatus -A

Take a look at those logs and post what you think is relevant.

I'm assuming 11.31 HP-UX but please clarify that.

vpar is at version 5.04 or 5.05 for 11.31

SEP

[Atindra Ghosh]

vparstatus -A is showing only the resources which are available for vPar. I know that I need to change the ILM and CLM value becuse granularity cearts the issue to vPar boot slow. need to know how we are calclulating granularity to set the ILM and CLM. Please sahre information if you have on this.

[Turgay Cavdar]

Hi,
Checkout the doc:
http://docs.hp.com/en/T1335-90073/T1335-90073.pdf
page 211,255

Memory: Choosing a Granularity Value and Boot Time (Integrity)
During the boot process of HP-UX on Integrity vPars, the time it takes to obtain the memory layout
information for the nPartition is relative to the number of memory granules configured for the nPartition.
The number of granules is dependent upon the granularity value:
number_of_granules = total_physical_memory_in_nPartition / granularity_value
If the granularity value is too small, the number of granules will be too high and processing all the granules
during boot up may take a long time.
On Integrity systems, it is important to chose an appropriate granularity value that does not cause slow boot
times because changing a granularity value requires rebooting the entire nPartition as well as recreating the
vPars database.

The Goal
The goal to avoid slow boot times is to have the number of granules to be close to 50. Any quantity up to 100
will show reasonable boot times, but HP recommends a value close to 50.

[Olivier Masse]

Indeed, granularity can have an effect on boot time but I think you can't change it once your vPars are set. One thing you can check, if you happen to be running an older version of 11.23 in your vPar, is the patch database: there was a patch released sometime in 2006 that adresses an issue with long boot times on vPars. After applying it at my site, it resolved the problem without needing to change the granularity.

Olivier.