vparboot & vparmodify commands

[kzqqql]

Hi Gurus,

I created a mirror of primay boot disk on a vPar (within same VG00)  and changed the boot paths accordingly,  however the mirror boot disk could not boot up the server, possibly I forgot to replicate the LIFS. Now I want to rollback to reinstate the original primary boot device, these are the steps I plan to do:

(1) Logon a vPar (aaa) sharing same nPar with the affected vPar (e.g. bbb)

(2) as 'root', halt the affected vPar bbb

# vparreset -f -p bbb -h

# vparstatus

(3)  Boot up the affected vPar via the original boot paths

# vparboot -p bbb -B <orig-pri-boot-path>

I am not sure what will be the syntax of the argument <orig-pri-boot-path> to use in above command. Below are the original boot paths I saved before making the change, do I enter the whole Hex string or do I use the decimla format?

Let say if I can run 'vparmodify' command on another vPar to change back the boot path, then I don't have to specify the <orig-pri-boot-path> argument,  but I don't find sucvh options in 'parmodify' 

# setboot -v

Primary bootpath : 6/0/6/1/0/4/0.0x2042000b5d6a11aa.0x4000000000000000 (/dev/rdisk/disk1)

HA Alternate bootpath :

Alternate bootpath : 6/0/14/1/0/4/0.0x2043000b5d6a11aa.0x4000000000000000 (/dev/rdisk/disk1)

NB:  nPar --- PA-RISC in Superdome

         O/S   --- HPUX 11.31

Thank you in advance.

[Torsten.]

Superdome or Superdome 2?
vPars 5.x or vPArs 6.x?

PA-RISC Superdome, so it is either vPars 3.x or 4.x, right?

Both paths point to disk1, so it looks like you just pointed to an alternate path, not to the other disk.

[kzqqql]

Thanks Torsten.

Regarding vPar version, I guess you asked for this:

# swlist | grep -i part
  DynamicNPars                      B.11.31.0709   Dynamic nPartitions enablement
  NParCmds                          B.11.31.1009   NPartition Commands
  ParMgr                            B.31.02.04.04  Partition Manager - HP-UX
  T1335DC                           A.05.07          HP-UX Virtual Partitions for 11.31

And let me rephrase my question:

1) My orginal (prmary) boot disk is /dev/rdisk/disk1, and there are2 boot paths set up: primary & alternate

2) I then created a mirror boot disk, say, /dev/disk/diskM, then I changed both boot paths using the mirror disk's lunpaths, with 'setboot' command

3) I rebooted the server, but could not boot up, looks like I made some mistakes when replicating the primary boot disk's LIFS to the mirror disk, so I have to rollback to the primary disk

4) I logged on another vPar (within same nPar), run these commands to halt the probematic vPar and boot it up via the primary disk

# vparreset -f -p <my-vpar> -h

# vparstatus

# vparboot -p <my-vpar> -B <orig-pri-boot-path>

Now I am not sure what syntax to use in the argument <orig-pri-boot-path>, Hex LUNpath or hardware path in Decimal?

And is there a way to modify the boot paths using the vparmodify command?

[Torsten.]

Could you please post

# vparstatus -v

after mirroring?


There must be an entri with "ALTBOOT" listed like this:

[IO Details]
2.0.8
2.0.13
0.0.8
0.0.0
2.0.8.1.0.4.0.13.0.0.0.0.1 BOOT
0.0.8.1.0.4.0.15.4.0.0.0.1
0.0.8.1.0.4.0.14.4.0.0.0.1,ALTBOOT

[kzqqql]

Spoiler

Hi Torsten, below are the [IO Details] section of 'vparstatus -v' display BEFORE I created the mirror. So to boot up the vPar via the original boot disk, I have to run:

# vparboot -p <my-vpar> -B  6.0.5.1.0.4.0.10.2.0.0.0.0

[IO Details]

6.0.13.1

6.0.5.1

6.8.1

6.0.5.1.0.4.0.0x50060e8005900f00.0x4000000000000000.0.0.0.0

6.0.5.1.0.4.0.10.2.0.0.0.0 BOOT

6.0.2

6.0.13.1.0.4.0.11.6.0.0.0.0,ALTBOOT

6.0.5.1.0.4.0.201.62.0.0.0.0

6.0.13.1.0.4.0.201.4.0.0.0.0

6.0.5.1.0.4.0.101.4.0.0.0.0

6.0.5.1.0.4.0.101.15.0.0.0.0

6.0.13.1.0.4.0.201.15.0.0.0.0

6.0.5.1.0.4.0.201.48.0.0.0.0

6.0.13.1.0.4.0.0x50060e8005900f10.0x4000000000000000.0.0.0.0