vpar Monitor upgrade.

[fizan]

Vivek,

4.****Re-create of 11:23 v-pars? what should i perform here again after booting up the new A.5.0.1 monitor after start the 11:31 v-par, ???next is should build from scratch the other all 3-v-pars of 11:23 do you advice this one???

am bit worried bcoz the app owner's are informed only for server shutdown i.e 3 -vpar's will be down for 5 hrs, how can i re-create it?

[Vivek_Pendse]

No need to worry :)
Before doing this activity, you have to take backup of all vpar paths i.e. hw paths, cpu, memory whichever are assigned. i.e. with the command # vparstatus -v
Or, you can get a script from HP; called vpars-collect.sh

Once you install 11.31 on npar (on new disk), then you have to just re-create existing 11.23 vpars. So, the hw paths will be remained same & it (11.23 os) would boot as was before.

Re-creating vpar means, just we are creating the vpar with same hw path & cpu, memory resources.

Thanks,
Vivek

[Torsten.]

You have several ways to reach the goal.

The problem is, you need to boot from the version 5 vpmon (11.31) and once this is done, you can only do modifications from the version 5 vPar.


You can do what I wrote earlier or even really consider to re-create the other vPars.


Re-create here means you create the vPars definition, not the OS - the OS remains.



The problem is you need to put the new vpmon on a new disk and merge the existing configuration into. Since vpmon resides in /stand, you need a valid LVM structure on the new disk.


So you can
- create the 4th vpar, then install 11.31 in npar mode.
or
- install 11.31 in npar mode, bring the "old" vpdb in place, then create the 4th vpar the reboot in vPars mode
or
- install 11.31 in npar mode, create the 4th vPar (this is the only vPar now). Re-create the other vPars and boot in vPars mode.




You may minimize the downtime by installing 11.23 in the 4th vPar, the update to 11.31. So you need a single reboot from the new vpmon only - but this update may or may not produce other problems with the OS itself.

[fizan]

@ Vivek:

Thanks:
1.Now i got it, after booting up according to your steps i need to just use vparcreate cmd with old HW paths for all existing 3 v-pars.

**In this after vpar creation it comes to:MON
then as follows am i correct plz?

MON> vparload -p vpar1 -B oldpath
MON> vparload -p vpar2 -B oldpath
MON> vparload -p vpar3 -B oldpath
MON> vparload -p newvpar4 -B TAPE 11:31 OS

@ Tortsen:

Thanks
as i prefer to go with 1st one::
1. creation of the 4th vpar,
2. Then install 11.31 in npar mode new disk
3. boot in v-par mode
===========================================

One common question is my BASE OS now is 11:23 in n-par0, after the V-pmon upgrade
my n-par0 BASE OS will change as 11:31 with A.5.0.1 v-par sw correct?

Thanks

[Vivek_Pendse]

Hi,

When you have installed 11.31 on new disk in npar. Then you will re-create old 3 vpars with their existing hard paths.

After that, you will reboot the npar & you will boot it from 11.31 vpar & will come to
MON> --> of 11.31

From here:
just do --> vparboot -p

No need to mention, the -B old path --> as you have already mentioned, while re-creation of vpar.

Also, I didnot understand, why did you mentioned:

MON> vparload -p newvpar4 -B TAPE 11:31 OS

Thanks,
Vivek

[fizan]

>>Also, I didnot understand, why did you mentioned:

MON> vparload -p newvpar4 -B TAPE 11:31 OS<<<<

Bit confused:
After the chnages:
1. n-par0 will be run on 11:31 OS
2.At the
n-par0# vparcreate -p with old paths,
correct or wrong ?
3. After boot in v-par mode
4. now all the 4-vpars will be up in A.5.1 sw
=====================================
>>Also, I didnot understand, why did you mentioned:

MON> vparload -p newvpar4 -B TAPE 11:31 OS<<

Vivek:will vparload cm wil work in MON> promt?

=========================================

>>From here:
just do --> vparboot -p <<<<

from here states on the login of vpar1# right?

[Vivek_Pendse]

Yes, exactly.
No need to boot from the tape again. As you will be installing 11.31 os with it's vpar on new disk & re-creating old vpars.
So, just boot from the new 11.31 vpar os & monitor & just boot all the vpars e.g. vparload -all

[fizan]

Thanks vivek -San:

very much thanks will summarize the activity & update you by EOD

[fizan]

Summ::

1. shutdown all the running 3 v-par's
2. from MON> reboot
3. ISL> hpux --- n-par0 logged in.
4. nparo# Delete the A.4.5.7 v-par SW.
5. Install the 11:31 on the new hard disk {tape or dvd is best for 11:31 restoration?}
6. Install the A.5.0.1 v-par SW on new HDD
7. set the primary boot path for the new vp-MON:
8. vparcreate -p with old path : just allocating the HW resources to v-pars.
9. nparo# vparstatus --- now should show N/A on all patitions
8. npar0# shutdown -ry 0
9. Interpt at ISL > hpux/stand/vpmon -a or /hpux/stand/vpmon
10 **first need to boot 11:31 v-par**then other 3v-pars 11:23 will be booted up. mixed


11. whether i need to take the /stand/vpdb copy before shut the v-pars on A.4.5.7 version ?
12. Are it will re-create automatically when i boot up the v-pars on A.5.0.1. ?

Any other or Any steps missed out?

[Vivek_Pendse]

These steps are not required.
3. ISL> hpux --- n-par0 logged in.
4. nparo# Delete the A.4.5.7 v-par SW.

No need to worry, this is tested solution.
Go ahead & install the os & vpars software on new disk. Just ensure the ignite backup of all vpars beofre acitivity.

Thanks,
Vivek