remove the first vpar (holding the npar mode and runing the vpmon for the npar)

[kenken_3]

Hi All,

I have 3 vpars in the same npar and they are vpar1, vpar2 and vpar3. vpar1 is the first vpar (holding the npar boot disks, vpmon for whole npar, the vpmon is A.04.xx. and it's os version is 11.23). vpar2 and vpar3 are the same. they have vpmon version A.03.xx and it's os is hpux11.11.

I need to remove vpar1 to free up some resources. the difficult part is it owns the npar mode, different version of vpmon).

Here are my plans. please advise if you have better one or I miss any important steps:

1) collect all the outputs on cpu, memory, IO of vparstatus for each vpar; backup all the vpdb;
2) shutdown all the vpars;
3) boot to vpar2 or vpar3 (npar mode);
4) change the npar bootpath;
5) remove all the vpars, re-create vpar2 and pvar3 with the information collected;
6) reboot npar mode;
7) go to vpar mode and load the 2 created vpars;

Please suggest. Thanks.

[Torsten.]

If you have a mixed vPar installation with 11.11 and 11.23 you must have a PA-RISC system.

IMHO it must be enough to reboot the server and load a version A.03.xx vpmon, that's it.

Now you can remove vpar1.


Or even better:

Shutdown vpar1 and vparremove it.




All depends on if this is a sx1000 or sx2000 based system - what is it?

[kenken_3]

HI Torsten,

Yes, it is Pa-risc server. How can I check whether it is s1000 or S2000?

thanks

[Torsten.]

Please use "model" command.

[kenken_3]

it is 9000/800/rp8440.

my question is if I go to the npar mode of the vpar2 or vpar3(hpux11.11 and vpmon A.03.xx), when I remove the first vpar1(hpux11.23 and vpmon A.04.xx), whether the vpdb can keep the change and not corrupted.

If it is safe to do that, I can just remove the vpar1 there without regenerate others.

thanks,

[Torsten.]

You have a sx2000 chipset based system, so you don't need to have any physical console device included in the first vPar - this makes things easier.

I'm not sure if there are differences in the vpdb, but I don't think so.

Make sure to record all the configuration details.

I would try this:

Restart the system from a version 3 vpmon. The version 4 vPar will not start and complain, but this shouldn't be a problem.

If the version 3 vPars come up, remove the first vPar.

This should be everything to do.

Don't forget to adjust the bootpath to the vpmon, this can be done from the BCH directly.

[kenken_3]

Hi Torsten.,

Thanks. Your suggestion will be the easist way for me if it works well.

Currently the Npar's primary and alternate booting path are the same as the first vpar vpar1's boothing paths.

Once I removed the vpar1 in npar, I should use parmodify -b to change the npar primary boothing path.

Can I do it in vpar mode or in npar mode?

thanks

[Torsten.]

I would simply record the hardware path for one of the 11.11 boot disks and use this to set pathes in BCH directly.

Example:

Main Menu: Enter command or menu > co

...

Configuration Menu: Enter command > pa pri 0/1/1/0.0.0

...

Main Menu: Enter command or menu > bo pri