Issue:
After upgrade to 5.0MP3, server fails to bootwith the following error message:

VxVM sysboot INFO V-5-2-3409 startingin boot mode...
Jul 18 05:49:03 vxvm:vxconfigd: V-5-1-11538 volboot:Upgrading protocol version (70) in volboot file to the
Jul 18 05:49:03vxvm:vxconfigd:   highest version (80) automatically. Might be result of anupgrade.
Jul 18 05:49:04 vxvm:vxconfigd: V-5-1-1589 enable failed:Configuration daemon error 14
Jul 18 05:49:04vxvm:vxconfigd:         Bad address; aborting
VxVMsysboot WARNING V-5-0-4817 Error starting vxconfigd
VxVM sysboot WARNINGV-5-0-0


Other messages were as follows:
Warning: The followingfiles in / differ from the boot archive:

   stale//kernel/drv/vxapm/sparcv9/dmphpalua.SunOS_5.10.1
   changed/kernel/drv/sparcv9/vxdmp.SunOS_5.10
volboot was still at protocol version70.
# more volboot
volboot 3.1 0.6 70
hostid cbmccusldap3p
hostguid{f81e2eec-1dd1-11b2-b066-00144f2ca03a}
defaultdg rootdg
bootdgrootdg
end
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
###############################################################
####



Solution:
Therecommended action was to reboot to the failsafe archive to correct the aboveinconsistency.

Unencapsulated boot disk
Used Solaris "boot -Ffailsafe" to update the boot archive.
Server came up successfully and volbootprotocol version was 80.
Encapsulated boot disks successfullyagain.