Doubt in Vpar

[Guna_2]

Hi Gurus,

1.) The scenario is, I have 2 Vpar’s configured on a Server. I booted the vpmon from the boot disk of the 1st Vpar(bootpath). After that, I booted the vpar2. Now vpar2 is up and vpar1 is down. In that situation if the bootpath disk of the vpmon failed or entirely detached from the server, then what will happen?

Will my Vpar2 run after the bootpath disk of vparmon failed?

2.) Can I remove the vpar1, which one I created primarily and which has the console associated with it?


Thanx & Rgds,
----MGP---

[Steven E. Protter]

Shalom MGP,

If you did everything right both vpars should be independent and run regardless of the others status.

I would suggest looking at syslog.log and shutdown logs and see if there is a clue to where the problem is.

SEP

[Duncan Edmonstone · Accepted solution]

Hi,

1) Once vpmon is running, it no longer needs to access the disk it was booted off, so if that disk failed you wouldn't have an immeidate problem in vpar2 (until you came to reboot the nPar) - of course vpar1 might have a problem - but you are Mirroring your boot disks yes? (if you can afford a system that runs the vPar software, you can afford to protect your boot disks)

2) Yes you can remove vpar1 if you wish - you will of course have to update your auto boot strings to ensure you now boot off the vpmon in /stand on vpar2 before you remove vpar1.

HTH

Duncan

[Guna_2]

Thanks Duncan,

Nice answer.

But i came up now with another doubt,

take a scenario,

I have only one VPAR on my server. I am booting the server, from the primary boot path of PDC i booted to /stand/vpmon, which gave me the MON> console. now the vpar is down state. As per your above answer,at this point of time, the VPMON don't want to access the disk, as it has already loaded the VPMON and VPDB into memeory. In this place if my entire disk failed or disk detached from server, What will happen?

Will my Monitor (VPMON) continue running?


Thanks once again,
----MGP----

[Roberto Arias]

Hi all:

Please check that you have vpmon0s database in all vpar ( in stand) and the daemon is running
regards

[Guna_2]

Hi Roberto,

Yes you are correct, all the vpar's have a vpmon and vpdb copy in /stand. But my question is when all the Vpars are down and the bootpath disk of the VPMon fails, What will happen?

Will my monitor continue running?

Thanks,
---MGP---

[Eric SAUBIGNAC]

Bonjour,

< But my question is when all the Vpars are down and the bootpath disk of the VPMon fails, What will happen? >

When vpmon start it loads in memory the database from the boot disk. As said Duncan, once vpmon is running, it no longer needs to access the disk it was booted off.

So the definitive answer to this question is : NOTHING. vpmon will still run and you will be able to load any vPar whose resources are available.

The only problem could occur if in this configuration, that is without having online the vpar wich includes the boot disk, you modify anything to the vPars. The vpdb of the boot disk will not update, and at tne next nPar rebbot you will loose all modifications, unless you boot with an updated disk.

Here is an extract of documentation. It explains how vpmon loads and how vpdb is maintened :

------
At the heart of the vPars Monitor is the partition database. The partition database contains partition configuration information. Using the partition database, the Monitor tracks which virtual partitions exist and what hardware resources and partition attributes are associated with each partition.
When the Monitor boots it reads a copy of the partition database from a file on the same disk from which the Monitor /stand/vpmon is booted. The default file is /stand/vpdb. Then, the Monitor creates a master copy of the vPars partition database in the memory reserved by the Monitor.
The operating system of each virtual partition also keeps a local copy of the partition database in a file, by default /stand/vpdb, on its local boot disk. You can create, modify, and view the database contents using vPars commands at the Unix shell level. Because the format of the database is proprietary, you must use only vPars commands to create, modify, and view the database.
Whenever you execute a vPars command from the Unix shell of a partition, the change is made first to the Monitor master copy. Then, the operating system from which you executed the command updates its local copy from the master copy. Every five seconds, the operating system of each running partition automatically updates its local copy from the master copy. This synchronization ensures that the virtual partitions and changes to the partition database are preserved when the entire hard partition is rebooted.
------

Hope this will help

Regards

Eric

[Guna_2]

Thank you!

Thanks to all of you for giving quick and perfect answer.

--MGP--