Vpar 1.3 to 3.03 upgrade

[Richard Murden]

We have a RP8420 with an expansion cabinet. The RP8420 and the cabinet both have two nPars each with the expansion cabinet's second npar made into vpars. We are currently running two vpars there. We are running 11i. If i run an swlist i see that A.03.03 is loaded but if i run a vparstatus -V on one of the vpars i get Version 1.3. I assume the software was just loaded using swinstall without going through the proper procedures.
My question is;
1. Can i upgrade from 1.3 to 3.03?
2. Do i need to remove the 3.03 version first since i am still on 1.03?
3. Do i need to apply the 3.03 to my other npars? I dont have any plans to vpar those out
4. I f my vpars are on the expansion cabinet, will the entire cabinet have to be brought down?
Thanks,
Richard
Points to be awarded!

[Pete Randall]

Richard,

I don't think you need to do anything - it's just a different number being presented for the same software.

In my case, I get:

# vparstatus -V
Version 1.1

- and -

t# swlist |grep -i vparsbase
VPARSBASE A.02.02.00 HP-UX Virtual Partitions
- Base Version


And I know that no more recent version was installed, so they are the same!


Pete

[Richard Murden]

Thanks for the reply but i need a little more hard evidence. Is there some other command i can run? I have attached a swlist output.

[Torsten. · Accepted solution]

Richard, you are running version A.03.03.

the vparstatus -V gives you "the version number of the vparstatus output format" - not the software version. Confusing, I know.

see man vparstatus.

[Richard Murden]

Seems reasonable. I can buy that. I did a man on vparstatus and ran this command.
vparstatus -m -M
3.0.0.0.1.0.0.0.0.0.0:3.0.0.2.0.6.0.0.0.0.0:/stand/vpmon:/stand/vpdb:A.03.03

Is the vpar database A.03.03? Or is this what i am looking for?

I assume when the version 03.03 was apllied it was just with swinstall, thats it. So i assume i am safe. How did it get applied if the proper procedures werent followed? The MP, servers have all been powered down and boot since that software install. Did this trigger it?
Thanks,
Richard

[Torsten.]

man vpastatus again:

-m Displays the console path, hardware path from which the monitor was booted, the file system path of the monitor, the vPars database file system path that is being used by the monitor and


the vPars release version information.

[Torsten.]

example:

#vparstatus -m
Console path: 0.0.2.0
Monitor Boot disk path: 0.0.1.0
Monitor Boot filename: /stand/vpmon
Database filename: /stand/vpdb
vPars release version: A.03.03

[Richard Murden]

This is what I got with the -m.
#vparstatus -m
Console path: 3.0.0.0.1.0.0.0.0.0.0
Monitor Boot disk path: 3.0.0.2.0.6.0.0.0.0.0
Monitor Boot filename: /stand/vpmon
Database filename: /stand/vpdb
vPars release version: A.03.03

That good, i was getting worried when i used the -V option.

I also looked on our RP8400 running 11i. I dont get the same output like i do on the RP8420.
vparstatus -m
Console path: 1.0.0.0.1.0.0.0.0.0.0
Monitor Boot disk path: 1.0.0.2.0.6.0.0.0.0.0
Monitor Boot filename: /stand/vpmon
Database filename: /stand/vpdb
[sdc9017:/]# vparstatus -m -M
1.0.0.0.1.0.0.0.0.0.0:1.0.0.2.0.6.0.0.0.0.0:/stand/vpmon:/stand/vpdb
[sdc9017:/]# vparstatus -M
shmtest:Up:Dynamic,Autoboot,Nosearch:/stand/vmunix::2/5;;1.10,1.11;;:1.0.1.0.0.4.0.0.0.0.0.0.0 BOOT,1.0.1,1.0.6:;4096:N
hcisec:Up:Dynamic,Autoboot,Nosearch:/stand/vmunix::1/6;;1.12;;:1.0.0.2.0.6.0.0.0.0.0 BOOT,1.0.8,1.0.10,1.0.12,1.0.14,1.0.0.3.0.6.0 ALTBOOT:;8192:N
sdc9018_dp55:Up:Dynamic,Autoboot,Nosearch:/stand/vmunix::1/2;;1.13;;:1.0.4.0.0.25.8.0.0.2.3 BOOT,1.0.4,1.0.2,3.0.12:;1024:N

Cant find a version numer using -M or -m. I have attached a swlist.

Thanks,
Richard

[Torsten.]

Perhaps the output came with version 3.03.

Your second system has version A.03.02.

See the (short) list of changes from 3.02 to 3.03:

http://docs.hp.com/en/7041/T1335-90042.pdf

[Richard Murden]

Thanks all for the help and clarification. I am closing the thread.
Thanks,
Richard