superdom shutdown or npar shutdown

[Asif_8]

Hi !

we have ia 64 superdom SD32B.which have
4 npar
everu npar have 4vpars
every npar ist vpar boot from internal disk
some npar have differnst os ( 11.23 and 11.31)
Due power souce change of workstrage (LWP 1000AP38-2) we want to shudown the superdom
1. what is the procedure of shudown superdoem
or after shutdown vpars how to shudown npars
2. how to start superdoem (npars and vpars)

thanks

[g3jza · Accepted solution]

Hi,

shutdown:

Shutdown all of your vPars first (standard #shutdown -hy 0 on every vPar).

Then after all of the vPars are shut down, confirm this by accessing the console/MP of each nPar. There should be only vpMON ([MON]) . You can confirm that the given nPar has no vPars running by entering #vparinfo on the [MON] prompt. All of them should be 'down'.

Then after you are sure that no vPars are running, just go to the command menu of your MP and enter the PE (power enable) ,select X (complex) and answer OFF.

one example:
[sd01-mp] MP> cm

Enter HE to get a list of available commands

(Use to return to main menu.)

[sd01-mp] MP:CM> pe

This command controls power enable to a hardware device.

B - Cabinet
C - Cell
X - Complex
I - IO Chassis
P - Partition
Select Device: x

The power state is ON for complex.
In what state do you want the power? (ON/OFF)

Startup:

So power up the whole complex : command menu-->PE-->X-->ON

Depending on how are the vPars configured. If there's autoboot on every vPar, then just wait for all of your vPars to start up.
If the autoboot is not enabled, then at each nPar's [MON] prompt just type #vparload -all

[Asif_8]

thanks

1. if i want to power off the one by one npar
then i choose
This command controls power enable to a hardware device.

PE-->P-->0 ---1 --2 --3

2. how i check vPars configured autoboot ?

thanks

[g3jza]

1)
yes, you can power off / on one nPar at the time, but you can also poweroff the entire complex (X) at once and by this you disable power to the whole superdome.

2)
#vparstatus from your vPar shell and look for attribute: Auto for earch vPar.

But it depends on how your nPar's boot disk is configured, I mean, what's inside the AUTO file of your nPar's boot disk. It should contain boot string "boot vpmon -a" in order to boot all of the vPars automatically.

[Asif_8]

Thanks, yes vpar set boot as below

#vparstatus
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ============ ======================= =====
xxxxxx1 Up Dyn,Auto,Asr /stand/vmunix -lq
xxxxxx2 Up Dyn,Auto,Nsr /stand/vmunix -lq
xxxxxx3 Up Dyn,Auto,Nsr /stand/vmunix -lq

[g3jza]

ok,
then for example you have nPar0:
Go to the shell of any vPar on the nPar0;

type #parstatus -Vp0|grep -i boot
and look for the HW Path of your primary boot disk (the disk which is used to boot vpMON).

Then you need to figure out which vPar is assigned the disk with that HW Path. (You can compare the '#vparstatus -v' output with the HW Path from the '#parstatus -Vp0' to match the primary boot disk).

Then if you know which vPar is assigned the primary boot disk of nPar0, associate that Hw path of the disk with device special file and extract the AUTO file:

#efi_cp -d /dev/rdisk/diskXX_p1 -u /EFI/HPUX/AUTO /tmp/AUTO
#cat /tmp/AUTO

If the AUTO file contains 'boot vpmon -a' then all of your vPars should be booted automatically.

I hope I didn't write it too complicated.