You may want to use the bosboot command while performing certain tasks. For example, many software installations require running the bosboot command at the end of installation. The bosboot command may fail when the DMP device controls the physical volume IDs (PVIDs). You must temporarily release the PVIDs from DMP to enable the bosboot command to perform correctly. After the bosboot command completes, enable DMP to reclaim the PVIDs.
To run bosboot command on the rootvg
# vxdmpadm native list PATH DMPNODENAME ============================================== hdisk168 emc0_0039 hdisk172 emc0_0039 hdisk184 emc0_0039 hdisk188 emc0_0039
# lsvg -p rootvg rootvg: PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION emc0_0039 active 73 0 00..00..00..00..00
# lspv | grep -w rootvg emc0_0039 00c398edf9fae077 rootvg active
# vxdmpadm native release
The output of the following command shows that DMP has released the PVIDs of the paths.
# lspv | grep -w rootvg hdisk168 00c398edf9fae077 rootvg active hdisk172 00c398edf9fae077 rootvg active hdisk184 00c398edf9fae077 rootvg active hdisk188 00c398edf9fae077 rootvg active
# bosboot -ad /dev/ipldevice bosboot: Boot image is 56863 512 byte blocks.
If the bosboot command fails on /dev/ipldevice
, then retry the command on the paths of current boot disk until it succeeds.
# vxdmpadm native acquire
# lspv | grep -w rootvg emc0_0039 00c398edf9fae077 rootvg active