vPar Monitor?

[Hanry Zhou]

I have two quesionts.

As I understand, each vPar has their own Monitor and it is stored on their local boot disks. My first questions is, are these monitor all same, same contents?

2nd question. If you reboot the hard partition, you should boot the monitor from the boot disk of a virtual partition that was running during your most recent partition configuration change. My 2nd question is, How do you know which one is more recent partition?


Thanks,
zhou

[James Murtagh]

Hi,

Each Vpar has its monitor (/stand/vpmon) but per hard partition (npar) there is only one monitor. Think of it located between the kernel and firmware. Even if one Vpar is inactive any changes are written to other Vpars. I will find out exactly how this works for you tomorrow but I suspect even after a Vpar is shut down, the memory resident portion (taken from a small chunk within that partitions memory allocation) is still active, hence still writeable. So in answer to your second question, it shouldn't matter.

Regards,

James.

[Massimo Bianchi]

Hi,
I worked with Vpar last year.

As far as i can remember, of you want to shut down the harda partition you MUST first shut down all your vpar.

Then, from console, you got access to the monitor of the partition and you rebbot it. So it's of no importance from which partition you do the reboot.

HTH,
Massimo

[Jean-Louis Phelix]

Hi,

Yes, each vpar has its own /stand/vpmon copy and all should be identical because delivered by the vpar product which must have the same release on all vpars, but only one is running at a time in the system.

Yes you are right, you have to boot from a vpar aware of the last config change (most recent vpdb), but I'm very sorry, I think there is no way to know which one is the most recent. You would need an access to all /stand/vpdb on all vpars to know this.

Regards.

[Hanry Zhou]

thank you all for the kind response.

ok, if each vpar has its own /stand/vpmon, and they are all identical, but where is npar's vpmon located, is it located on one of boot disk in one of vpar?

[harry d brown jr]

When you boot vpars you do so by in the isl by

hpux /stand/vpmon

Only one vpmon is started - ever.

Each partition has its own boot disk and therefore a copy of vpmon. This means that you can start your partitions from ANY vpar enabled boot disk.

vpmon will be the same if each partition has the same level of vpars installed.

If you had five vpar enabled boot disks, you can start the vpmon from anyone of those disk locations. Then from the vpmon you can start your vpar partitions using (I think - it's been a while since I rebooted) vpload -p partitionname


live free or die
harry

[Hanry Zhou]

Also,

1. Are all /stand/vpdb's identical on different vpar's

2. If I can't find out the time stamp on /stand/vpdb and /stand/vpmon before I boot up a vpar, how do I figure out which one is most recent?

Thanks,

[harry d brown jr]

1. Are all /stand/vpdb's identical on different vpar's

They will be identical, providing you ONLY make changes to vpdb when ALL partitions of that GROUP are running (vpard - is the SYNC daemon).

If you make changes and a partition(s) is not UP (running), then you have to manually copy the vpdb file over to the partition(s) that is NOT running - once you start it up.

2. If I can't find out the time stamp on /stand/vpdb and /stand/vpmon before I boot up a vpar, how do I figure out which one is most recent?

You just need to know beforehand. Sorry :-(

**** With a system that is capable of running virtual partitions, say an N-class, you could have thousands of boot disks (really no limits other than system stuff) and hundreds (really no limits) of GROUPS of "partitions".

For example, lets say you have an N-class server and it has access to 15 18-GB disks. You could have one vpdb boot 6 of them under one configuration. Another vpdb could have a configuration for 3 partitions, and a third for 6 other partitions. Now you can only run 6 (7 if you are creative) on an N-class at any one time.

What I do when I want different configurations is to have differently named vpdb's. You do this by booting the vpmon like this:

hpux /stand/vpmon -D MYcrazyConfig

and then later shutdown and reboot with a different configuration set:

hpux /stand/vpmon -D mySANEvpdb

or just

hpux /stand/vpmon -D vpdb


I really think that anyone that wants to or IS running vpars MUST have Marty Poniatowski's "hp-ux virtual partitions" book.

http://www.hp.com/hpbooks/prentice/ptr_0130352128.html



live free or die
harry

[Hanry Zhou]

So, where is the npar's monitor exactly located, or it is just one of monitors on vpar's?