uncontrolled vpar shutdown

[masood bt]

Hello

As a part of testing, I need to shutdown a vPar in an uncontrolled way.

I understand hpvmstop shuts down the vm guest in an uncontrolled way.

For vpar, what is the command.
Is it
#vparreset -p ?

Also, I think I need to consider that this vpar which should be shutdown in uncontrolled way should NOT be a base vpar in that npar.

Please suggest.

There are total six vPars in this nPar

model:ia64 hp superdome server SD32B

[Torsten.]

What do you mean by "uncontrolled"?

Something like a reset / power off?

In this case the vparreset may work for you.

(I wonder why you want to do this).

[masood bt]

Hi..
Yes, uncontrolled means ungraceful.....or reset etc. I need to shutdown the vpar in this way... this is as a part of testing as I said earlier....

How do I know that a particular vpar is a base vpar or not?

thank you

[masood bt]

what does this mean

On Superdome, when there is a pending Reboot for Reconfiguration, the target virtual partition
will not be rebooted until all the virtual partitions within the nPartition are shut down and the
virtual partition Monitor is rebooted.

[Vishu]

Hi masood,

1)*****Yes, uncontrolled means ungraceful.....or reset etc. I need to shutdown the vpar in this way... this is as a part of testing as I said earlier....**********

so you wanna do ungraceful shutdown. then vparreset will definitely work for you. you can use as

vparreset -p -h

-h for hard reset or -t for soft reset.


2) **********what does this mean

On Superdome, when there is a pending Reboot for Reconfiguration, the target virtual partition
will not be rebooted until all the virtual partitions within the nPartition are shut down and the
virtual partition Monitor is rebooted. ***************

This means that some change is pending to be implemented to SCCD of the npar. So, it need a reboot of the npar to implement that change, which requires all Vpar in that npar to be down.

[Bill Costigan]

There is no 'base vPar' on the nPar. All vPars are equal.

A chunk of software called vpmon runs directly on the nPar and that hosts all the vPars equally. You can kill any or all vPars you wish and vpmon keeps running.

[Steven E. Protter]

Shalom,

#vparreset -p

That is ugly, but its still a controlled crash.

I froze up an npar on Tuesday by violating hot swap hardware replacement rules. Thats uncontrolled and was not expected.

I use vparreset when building a vpar if I let it out of the door too early and its got bad parameters and I need to bring it up in single user mode.

No real harm though. System recovers though every filesystem requires fsck.

Even freezing up an npar and having to do an RS (reset power) didn't impact any of the systems in it. They recovered as expected.

SEP

[masood bt]

thank you all for your replies.
I did completed this on my vpar.these are my observations:

vparreset -p (server reboots)
vparreset -p -t (server reboots)



vparreset -p -h (server is shut down)
i.e., in MON prompt, vparinfo...server status is (down)

I did vparreset -p -h

from another vpar, ofcourse.

After the testers are happy that databases switched to another vpar...then i did vparload.

you can add your comments...else I will close this thread on monday

[masood bt]

as explained in my earlier reply