Dynamic Root Disk Frequently Asked Questions (766143-001, March 2014)

At this point, the bootpath for vpmon on the nPar points to an inactive (original) image

even though vpmon is still up and running. The running vpmon maintains the master

copy of the vPar database in memory. This data is synchronized with each running

vPars local copy of /stand/vpdb. When vpmon is booted, the local /stand/vpdb is

loaded into memory and serves as the master copy. If a vPar is down while changes are

made that affect the vPar database, subsequent booting of vpmon from that vPar results

in the loss of those changes because the local copy of the vPars database is stale when

loaded by vpmon.

NOTE: HP recommendeds that the vpmon bootpath is modified to point to the clone

once it is activated, though there is no need to actually reboot the nPar unless the vpmon

executable has been changed.

If running vPars release A.05.06 or later on Integrity, the default bootpath for vpmon

can be set from the monitor prompt. This first EFI boot manager menu entry can be

changed without rebooting the nPar. The following monitor command sets the bootpath

for the active clone image corresponding to the vPar previously used to boot vpmon:

MON> mon_bootpath -p [new_bootpath]

From vPars release A.04.05 up to vPars release A.05.06 on Integrity, the mon_bootpath

command only allows you to add additional bootpaths to the nPar EFI boot manager

menu. For these releases, you need to change the default boot entry from the EFI menu

during a reboot in nPar mode. Prior to vPars release A.04.05, you need to change the

default boot entry from the EFI menu during a reboot in nPar mode. In all cases, if the

alternate or HA bootpaths need to be updated, they need to be updated from the EFI

menu during a reboot in nPar mode.

On PA systems, changes to vpmon bootpaths can be made from a running vPar: #

parmodify -p [partition_number] -b [bootpath] -P [partition_name]

Note that individual bootpath settings for setboot are lost if the disk at the specific

path is re-created with any of the following:

 The drd clone command

 Ignite cold install

 Ignite recovery

top

1-13. Q:

If swconfig is not supported by DRD, and swinstall runs swconfig, will it work

properly?

DRD defers the configuration part of an install operation, which remains inactive until

the system image is booted. (This behavior is similar to what happens when kernel

software is installed.)

top