How to tell if Npar or Vpar?

[Michael Steele_2]

The way I've been doing it is by running either 'vparstatus' or 'parstatus'. If 'vparstatus' doesn't exist then its an Npar. This seems a little unreliable. How do others make the distinction? Note: I'm working on 5 old superdomes and much of the GSP partition information is unreliable.

[melvyn burnard]

are there any vp* processses running?
Is there less hardware than you would expect?

[Michael Steele_2]

I guess I can elaborate. Some of my partitions are unbootable from the bch. The AUTO file has been made incorrectly with the 'mkboot' command. For Npars 'hpux' is usually entered. For Vpars 'hpux /stand/vpmon -a' is usually entered. So it looks like the unbootable partitions are Vpars with 'hpux' in the AUTO file instead of 'hpux /stand/vpmon -a'.

[Michael Steele_2]

Looks 90% of them are running vpard and vphbd daemons. But, I think Vpar software has been installed on Npars anyway.

[melvyn burnard]

Well the only difference between an Npar and a Vpar is whether the Vpar software is installed, and is then used.
The usual methodology is to install Vpars onto the Npar boot disc, and then create the frst Vpar using that boot disc, as you say, by changing the mkboot auto file string.


If indeed there are Vpars in an Npar, then ANY instance of HP-UX OS in that Npar has ot be on a Vpar.

[Michael Steele_2]

Ok, that's also where I'm coming from. Lets say you boot a Vpar with 'hpux' now, then the state of some of the resources would be displayed as bad or n/a or something in 'vparstatus'. So what about from the GSP?

[sujit kumar singh]

Hi Michael,


On an SD if you have even one VPAR in the NPAR as UP then the VFP for that NPAR shall show you the OS is up or running.

regards
sujit

[Jozef_Novak]

Hi Michael,

one alternative way how to find out whether you're on a vpar on npar is to check the AUTO file.

vpars always boot monitor before hpux kernel, so the AUTO file should read:

boot /stand/vpmon

instead of the usual "boot vmunix".

Jozef

[Mounaam]

Hi,

you can use vecheck(1):
DESCRIPTION
The vecheck command uses its exit status to report whether or not the
command has been run in a virtual partition (vPars) environment. The
result can be used to alter command flow in a script.
...
RETURN VALUE
The vecheck command exits with one of the following values:

0 The command is run in a vPars environment.
255 The command is run in a non-vPars environment.

Regards.

[Michael Steele_2]

Jozef and Sujit, you did not read the question properly.

Mounaan:

That's nice. And /sbin/vecheck exists on my PA-Risc box. I don't have an Itegrity dome so I can't check there. I'd have given 10 but there is no man page for vecheck and very little on the internet.

Do you have a procedure for running it?

[Mounaam]

Hi,

the man page for this command isn't provided by vPar 3.X (11.11) but is available in vPar 4.X (11.23) and 5.X (11.31).

You'll find an example of its usage in startup script /sbin/init.d/icod (or /sbin/init.d/vparinit).

Regards.

[VK2COT]

Hello,

vecheck(1M) is one of many tests run in my
Perl script for HP-UX servers:

http://www.circlingcycle.com.au/Unix-sources/HP-UX-check-OAT.pl.txt

Basically, here is the summary for vecheck
with Perl code how to use it:

my $ret = system "vecheck 2>/dev/null";
my $RCVALUE = ( $ret >> 8 ) && 0xff;
chomp($RCVALUE);
if ( "$RCVALUE" == 0 ) {
print
"\nINFO vecheck(1m) confirms server running in virtual partition (vPars) environment\n";
}
else {
if ( "$RCVALUE" == 255 ) {
print
"\nINFO vecheck(1m) confirms server NOT running in virtual partition (vPars) environment\n";
}
}

Cheers,

VK2COT

[Michael Steele_2]

.