Patch-ID# 112392-07
Keywords: vrtsvxvm 3.5mp3: security vxio, vxplex, vxconfigd, vxsync, vxclust
Synopsis: VxVM 3.5: general patch for Solaris 7, 8, and 9
Date: May/19/2004


Install Requirements: Reboot after installation                      
                      
Solaris Release: 7 8 9

SunOS Release: 5.7 5.8 5.9

Unbundled Product: Veritas VxVM

Unbundled Release: 3.5

Xref: 

Topic: 

Relevant Architectures: sparc

BugId's fixed with this patch: 4228190 4233507 4295380 4368933 4421145 4479302 4479879 4486602 4487591 4490375 4490646 4491048 4491997 4494006 4501921 4504662 4628999 4629246 4629303 4630477 4648109 4655082 4656592 4666269 4685297 4693346 4711196 4712376 4719356 4723639 4724737 4749183 4753143 4754257 4757423 4769704 4771018 4775892 4780047 4788268 4794938 4800160 4800446 4806363 4817095 4819716 4819736 4820436 4822685 4836017 4846600 4849123 4869501 4875401 4881620 4882902 4884319 4886517 4887356 4892045 4896990 4900508 4903611 4908473 4911443 4925410 4928807 4930738 4937259 4957502 4962757 4970610 4975602 4975998 4983404 4990011 4991788

Changes incorporated in this version: 4479879 4719356 4794938 4836017 4869501 4875401 4881620 4884319 4887356 4892045 4896990 4900508 4903611 4908473 4911443 4925410 4928807 4930738 4937259 4957502 4962757 4970610 4975602 4975998 4983404 4990011 4991788 4846600

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

/etc/init.d/vras-vradmind.sh
/etc/init.d/vxnm-vxnetd
/etc/init.d/vxrsyncd.sh
/etc/init.d/vxvm-reconfig
/etc/init.d/vxvm-recover
/etc/init.d/vxvm-shutdown
/etc/init.d/vxvm-startup1
/etc/init.d/vxvm-startup2
/etc/init.d/vxvm-sysboot
/etc/rc0.d/K99vxvm-shutdown
/etc/rc2.d/S94vxnm-vxnetd
/etc/rc2.d/S95vxvm-recover
/etc/rc2.d/S96vradmind
/etc/rc2.d/S96vxrsyncd
/etc/rcS.d/S25vxvm-sysboot
/etc/rcS.d/S35vxvm-startup1
/etc/rcS.d/S85vxvm-startup2
/etc/rcS.d/S86vxvm-reconfig
/etc/vx/aslkey.d/libvxap.key
/etc/vx/aslkey.d/libvxatf.key
/etc/vx/aslkey.d/libvxeccs.key
/etc/vx/aslkey.d/libvxemc.key
/etc/vx/aslkey.d/libvxfujitsu.key
/etc/vx/aslkey.d/libvxhds.key
/etc/vx/aslkey.d/libvxhitachi.key
/etc/vx/aslkey.d/libvxlsiinf.key
/etc/vx/aslkey.d/libvxnec.key
/etc/vx/aslkey.d/libvxpurple.key
/etc/vx/aslkey.d/libvxrdac.key
/etc/vx/aslkey.d/libvxsena.key
/etc/vx/aslkey.d/libvxshark.key
/etc/vx/aslkey.d/libvxssa.key
/etc/vx/aslkey.d/libvxstorcomp.key
/etc/vx/aslkey.d/libvxveritas.key
/etc/vx/aslkey.d/libvxvpath.key
/etc/vx/aslkey.d/libvxxp256.key
/etc/vx/lib/discovery.d/libvxap.so
/etc/vx/lib/discovery.d/libvxatf.so
/etc/vx/lib/discovery.d/libvxeccs.so
/etc/vx/lib/discovery.d/libvxemc.so
/etc/vx/lib/discovery.d/libvxfujitsu.so
/etc/vx/lib/discovery.d/libvxhds.so
/etc/vx/lib/discovery.d/libvxhitachi.so
/etc/vx/lib/discovery.d/libvxlsiinf.so
/etc/vx/lib/discovery.d/libvxnec.so
/etc/vx/lib/discovery.d/libvxpurple.so
/etc/vx/lib/discovery.d/libvxrdac.so
/etc/vx/lib/discovery.d/libvxsena.so
/etc/vx/lib/discovery.d/libvxshark.so
/etc/vx/lib/discovery.d/libvxssa.so
/etc/vx/lib/discovery.d/libvxstorcomp.so
/etc/vx/lib/discovery.d/libvxveritas.so
/etc/vx/lib/discovery.d/libvxvpath.so
/etc/vx/lib/discovery.d/libvxxp256.so
/etc/vx/slib/liba5k.so.2
/etc/vx/slib/libg_fc.so.2
/etc/vx/slib/libvxdiscovery.so
/etc/vx/vras/msg/vras.msg
/etc/vx/vras/templates/addsec.tem
/etc/vx/vras/templates/addvol.tem
/etc/vx/vras/templates/changeip.tem
/etc/vx/vras/templates/changeip_resume
/etc/vx/vras/templates/chk_connect_state
/etc/vx/vras/templates/chk_status
/etc/vx/vras/templates/createpri.tem
/etc/vx/vras/templates/delpri.tem
/etc/vx/vras/templates/delsec.tem
/etc/vx/vras/templates/delvol.tem
/etc/vx/vras/templates/fbsync.tem
/etc/vx/vras/templates/fbsync_chk_status
/etc/vx/vras/templates/ibc.tem
/etc/vx/vras/templates/makesec.tem
/etc/vx/vras/templates/makesec80.tem
/etc/vx/vras/templates/migrate.tem
/etc/vx/vras/templates/migrate80.tem
/etc/vx/vras/templates/pauserep.tem
/etc/vx/vras/templates/resizevol.tem
/etc/vx/vras/templates/resizevol_chk_maxgrow
/etc/vx/vras/templates/resumerep.tem
/etc/vx/vras/templates/resync.tem
/etc/vx/vras/templates/set.tem
/etc/vx/vras/templates/startrep.tem
/etc/vx/vras/templates/stoprep.tem
/etc/vx/vras/templates/syncrvg.tem
/etc/vx/vras/templates/syncvol.tem
/etc/vx/vras/templates/takeover.tem
/etc/vx/vras/templates/takeover80.tem
/etc/vx/vras/templates/vxedit.tem
/etc/vx/vras/templates/vxrlink.tem
/etc/vx/vras/templates/vxrvg.tem
/etc/vx/vras/templates/vxvol.tem
/etc/vx/vras/vras_env
/etc/vx/vvr/ibc_scripts/sample_db_snapshot/README
/etc/vx/vvr/ibc_scripts/sample_db_snapshot/onfreeze
/etc/vx/vvr/ibc_scripts/sample_db_snapshot/prefreeze
/etc/vx/vvr/ibc_scripts/sample_db_snapshot/quiesce
/etc/vx/vvr/ibc_scripts/sample_db_snapshot/unquiesce
/etc/vx/vvr/ibc_scripts/sample_vxfs_snapshot/README
/etc/vx/vvr/ibc_scripts/sample_vxfs_snapshot/onfreeze
/etc/vx/vvr/ibc_scripts/sample_vxfs_snapshot/prefreeze
/etc/vx/vvr/ibc_scripts/sample_vxfs_snapshot/quiesce
/etc/vx/vvr/ibc_scripts/sample_vxfs_snapshot/unquiesce
/etc/vx/vvrports.template
/kernel/drv/sparcv9/vxdmp.SunOS_5.7
/kernel/drv/sparcv9/vxdmp.SunOS_5.8
/kernel/drv/sparcv9/vxdmp.SunOS_5.9
/kernel/drv/sparcv9/vxio.SunOS_5.7
/kernel/drv/sparcv9/vxio.SunOS_5.8
/kernel/drv/sparcv9/vxio.SunOS_5.9
/kernel/drv/sparcv9/vxspec.SunOS_5.7
/kernel/drv/sparcv9/vxspec.SunOS_5.8
/kernel/drv/sparcv9/vxspec.SunOS_5.9
/kernel/drv/vxdmp.SunOS_5.6
/kernel/drv/vxdmp.SunOS_5.7
/kernel/drv/vxdmp.SunOS_5.8
/kernel/drv/vxdmp.SunOS_5.9
/kernel/drv/vxdmp.conf
/kernel/drv/vxio.SunOS_5.6
/kernel/drv/vxio.SunOS_5.7
/kernel/drv/vxio.SunOS_5.8
/kernel/drv/vxio.SunOS_5.9
/kernel/drv/vxio.conf
/kernel/drv/vxspec.SunOS_5.6
/kernel/drv/vxspec.SunOS_5.7
/kernel/drv/vxspec.SunOS_5.8
/kernel/drv/vxspec.SunOS_5.9
/kernel/drv/vxspec.conf
/opt/VRTS/bin/vxclustadm
/opt/VRTS/man/fr/man1m/vradmin.1m
/opt/VRTS/man/fr/man1m/vrnotify.1m
/opt/VRTS/man/fr/man1m/vrport.1m
/opt/VRTS/man/fr/man1m/vxapslice.1m
/opt/VRTS/man/fr/man1m/vxassist.1m
/opt/VRTS/man/fr/man1m/vxbootsetup.1m
/opt/VRTS/man/fr/man1m/vxclustadm.1m
/opt/VRTS/man/fr/man1m/vxconfigd.1m
/opt/VRTS/man/fr/man1m/vxdarestore.1m
/opt/VRTS/man/fr/man1m/vxdco.1m
/opt/VRTS/man/fr/man1m/vxdctl.1m
/opt/VRTS/man/fr/man1m/vxddladm.1m
/opt/VRTS/man/fr/man1m/vxdg.1m
/opt/VRTS/man/fr/man1m/vxdisk.1m
/opt/VRTS/man/fr/man1m/vxdiskadd.1m
/opt/VRTS/man/fr/man1m/vxdiskadm.1m
/opt/VRTS/man/fr/man1m/vxdiskconfig.1m
/opt/VRTS/man/fr/man1m/vxdisksetup.1m
/opt/VRTS/man/fr/man1m/vxdiskunsetup.1m
/opt/VRTS/man/fr/man1m/vxdmpadm.1m
/opt/VRTS/man/fr/man1m/vxedit.1m
/opt/VRTS/man/fr/man1m/vxencap.1m
/opt/VRTS/man/fr/man1m/vxevac.1m
/opt/VRTS/man/fr/man1m/vxibc.1m
/opt/VRTS/man/fr/man1m/vxinfo.1m
/opt/VRTS/man/fr/man1m/vxintro.1m
/opt/VRTS/man/fr/man1m/vxiod.1m
/opt/VRTS/man/fr/man1m/vxlicense.1m
/opt/VRTS/man/fr/man1m/vxmake.1m
/opt/VRTS/man/fr/man1m/vxmemstat.1m
/opt/VRTS/man/fr/man1m/vxmend.1m
/opt/VRTS/man/fr/man1m/vxmirror.1m
/opt/VRTS/man/fr/man1m/vxnotify.1m
/opt/VRTS/man/fr/man1m/vxplex.1m
/opt/VRTS/man/fr/man1m/vxprint.1m
/opt/VRTS/man/fr/man1m/vxr5check.1m
/opt/VRTS/man/fr/man1m/vxreattach.1m
/opt/VRTS/man/fr/man1m/vxrecover.1m
/opt/VRTS/man/fr/man1m/vxrelayout.1m
/opt/VRTS/man/fr/man1m/vxrelocd.1m
/opt/VRTS/man/fr/man1m/vxresize.1m
/opt/VRTS/man/fr/man1m/vxrlink.1m
/opt/VRTS/man/fr/man1m/vxrootmir.1m
/opt/VRTS/man/fr/man1m/vxrvg.1m
/opt/VRTS/man/fr/man1m/vxsd.1m
/opt/VRTS/man/fr/man1m/vxserial.1m
/opt/VRTS/man/fr/man1m/vxsparecheck.1m
/opt/VRTS/man/fr/man1m/vxspcshow.1m
/opt/VRTS/man/fr/man1m/vxstat.1m
/opt/VRTS/man/fr/man1m/vxtask.1m
/opt/VRTS/man/fr/man1m/vxtrace.1m
/opt/VRTS/man/fr/man1m/vxunreloc.1m
/opt/VRTS/man/fr/man1m/vxunroot.1m
/opt/VRTS/man/fr/man1m/vxvol.1m
/opt/VRTS/man/fr/man4/vol_pattern.4
/opt/VRTS/man/fr/man4/vxmake.4
/opt/VRTS/man/fr/man7/vxconfig.7
/opt/VRTS/man/fr/man7/vxdmp.7
/opt/VRTS/man/fr/man7/vxinfo.7
/opt/VRTS/man/fr/man7/vxio.7
/opt/VRTS/man/fr/man7/vxiod.7
/opt/VRTS/man/fr/man7/vxtrace.7
/opt/VRTS/man/ja/man1m/vradmin.1m
/opt/VRTS/man/ja/man1m/vrnotify.1m
/opt/VRTS/man/ja/man1m/vrport.1m
/opt/VRTS/man/ja/man1m/vxapslice.1m
/opt/VRTS/man/ja/man1m/vxassist.1m
/opt/VRTS/man/ja/man1m/vxbootsetup.1m
/opt/VRTS/man/ja/man1m/vxclustadm.1m
/opt/VRTS/man/ja/man1m/vxconfigd.1m
/opt/VRTS/man/ja/man1m/vxdarestore.1m
/opt/VRTS/man/ja/man1m/vxdco.1m
/opt/VRTS/man/ja/man1m/vxdctl.1m
/opt/VRTS/man/ja/man1m/vxddladm.1m
/opt/VRTS/man/ja/man1m/vxdg.1m
/opt/VRTS/man/ja/man1m/vxdisk.1m
/opt/VRTS/man/ja/man1m/vxdiskadd.1m
/opt/VRTS/man/ja/man1m/vxdiskadm.1m
/opt/VRTS/man/ja/man1m/vxdiskconfig.1m
/opt/VRTS/man/ja/man1m/vxdisksetup.1m
/opt/VRTS/man/ja/man1m/vxdiskunsetup.1m
/opt/VRTS/man/ja/man1m/vxdmpadm.1m
/opt/VRTS/man/ja/man1m/vxedit.1m
/opt/VRTS/man/ja/man1m/vxencap.1m
/opt/VRTS/man/ja/man1m/vxevac.1m
/opt/VRTS/man/ja/man1m/vxibc.1m
/opt/VRTS/man/ja/man1m/vxinfo.1m
/opt/VRTS/man/ja/man1m/vxintro.1m
/opt/VRTS/man/ja/man1m/vxiod.1m
/opt/VRTS/man/ja/man1m/vxlicense.1m
/opt/VRTS/man/ja/man1m/vxmake.1m
/opt/VRTS/man/ja/man1m/vxmemstat.1m
/opt/VRTS/man/ja/man1m/vxmend.1m
/opt/VRTS/man/ja/man1m/vxmirror.1m
/opt/VRTS/man/ja/man1m/vxnotify.1m
/opt/VRTS/man/ja/man1m/vxplex.1m
/opt/VRTS/man/ja/man1m/vxprint.1m
/opt/VRTS/man/ja/man1m/vxr5check.1m
/opt/VRTS/man/ja/man1m/vxreattach.1m
/opt/VRTS/man/ja/man1m/vxrecover.1m
/opt/VRTS/man/ja/man1m/vxrelayout.1m
/opt/VRTS/man/ja/man1m/vxrelocd.1m
/opt/VRTS/man/ja/man1m/vxresize.1m
/opt/VRTS/man/ja/man1m/vxrlink.1m
/opt/VRTS/man/ja/man1m/vxrootmir.1m
/opt/VRTS/man/ja/man1m/vxrvg.1m
/opt/VRTS/man/ja/man1m/vxsd.1m
/opt/VRTS/man/ja/man1m/vxserial.1m
/opt/VRTS/man/ja/man1m/vxsparecheck.1m
/opt/VRTS/man/ja/man1m/vxspcshow.1m
/opt/VRTS/man/ja/man1m/vxstat.1m
/opt/VRTS/man/ja/man1m/vxtask.1m
/opt/VRTS/man/ja/man1m/vxtrace.1m
/opt/VRTS/man/ja/man1m/vxunreloc.1m
/opt/VRTS/man/ja/man1m/vxunroot.1m
/opt/VRTS/man/ja/man1m/vxvol.1m
/opt/VRTS/man/ja/man4/vol_pattern.4
/opt/VRTS/man/ja/man4/vxmake.4
/opt/VRTS/man/ja/man7/vxconfig.7
/opt/VRTS/man/ja/man7/vxdmp.7
/opt/VRTS/man/ja/man7/vxinfo.7
/opt/VRTS/man/ja/man7/vxio.7
/opt/VRTS/man/ja/man7/vxiod.7
/opt/VRTS/man/ja/man7/vxtrace.7
/opt/VRTS/man/man1m/vradmin.1m
/opt/VRTS/man/man1m/vrnotify.1m
/opt/VRTS/man/man1m/vrport.1m
/opt/VRTS/man/man1m/vxapslice.1m
/opt/VRTS/man/man1m/vxassist.1m
/opt/VRTS/man/man1m/vxbootsetup.1m
/opt/VRTS/man/man1m/vxclustadm.1m
/opt/VRTS/man/man1m/vxconfigbackupd.1m
/opt/VRTS/man/man1m/vxconfigd.1m
/opt/VRTS/man/man1m/vxdarestore.1m
/opt/VRTS/man/man1m/vxdco.1m
/opt/VRTS/man/man1m/vxdctl.1m
/opt/VRTS/man/man1m/vxddladm.1m
/opt/VRTS/man/man1m/vxdg.1m
/opt/VRTS/man/man1m/vxdisk.1m
/opt/VRTS/man/man1m/vxdiskadd.1m
/opt/VRTS/man/man1m/vxdiskadm.1m
/opt/VRTS/man/man1m/vxdiskconfig.1m
/opt/VRTS/man/man1m/vxdisksetup.1m
/opt/VRTS/man/man1m/vxdiskunsetup.1m
/opt/VRTS/man/man1m/vxdmpadm.1m
/opt/VRTS/man/man1m/vxedit.1m
/opt/VRTS/man/man1m/vxencap.1m
/opt/VRTS/man/man1m/vxevac.1m
/opt/VRTS/man/man1m/vxibc.1m
/opt/VRTS/man/man1m/vxinfo.1m
/opt/VRTS/man/man1m/vxintro.1m
/opt/VRTS/man/man1m/vxiod.1m
/opt/VRTS/man/man1m/vxmake.1m
/opt/VRTS/man/man1m/vxmemstat.1m
/opt/VRTS/man/man1m/vxmend.1m
/opt/VRTS/man/man1m/vxmirror.1m
/opt/VRTS/man/man1m/vxnotify.1m
/opt/VRTS/man/man1m/vxplex.1m
/opt/VRTS/man/man1m/vxprint.1m
/opt/VRTS/man/man1m/vxr5check.1m
/opt/VRTS/man/man1m/vxreattach.1m
/opt/VRTS/man/man1m/vxrecover.1m
/opt/VRTS/man/man1m/vxrelayout.1m
/opt/VRTS/man/man1m/vxrelocd.1m
/opt/VRTS/man/man1m/vxresize.1m
/opt/VRTS/man/man1m/vxrlink.1m
/opt/VRTS/man/man1m/vxrootmir.1m
/opt/VRTS/man/man1m/vxrvg.1m
/opt/VRTS/man/man1m/vxsd.1m
/opt/VRTS/man/man1m/vxsparecheck.1m
/opt/VRTS/man/man1m/vxspcshow.1m
/opt/VRTS/man/man1m/vxstat.1m
/opt/VRTS/man/man1m/vxtask.1m
/opt/VRTS/man/man1m/vxtrace.1m
/opt/VRTS/man/man1m/vxunreloc.1m
/opt/VRTS/man/man1m/vxunroot.1m
/opt/VRTS/man/man1m/vxvol.1m
/opt/VRTS/man/man4/vol_pattern.4
/opt/VRTS/man/man4/vxmake.4
/opt/VRTS/man/man7/vxconfig.7
/opt/VRTS/man/man7/vxdmp.7
/opt/VRTS/man/man7/vxinfo.7
/opt/VRTS/man/man7/vxio.7
/opt/VRTS/man/man7/vxiod.7
/opt/VRTS/man/man7/vxtrace.7
/opt/VRTS/man/zh/man1m/vradmin.1m
/opt/VRTS/man/zh/man1m/vrnotify.1m
/opt/VRTS/man/zh/man1m/vrport.1m
/opt/VRTS/man/zh/man1m/vxapslice.1m
/opt/VRTS/man/zh/man1m/vxassist.1m
/opt/VRTS/man/zh/man1m/vxbootsetup.1m
/opt/VRTS/man/zh/man1m/vxclustadm.1m
/opt/VRTS/man/zh/man1m/vxconfigd.1m
/opt/VRTS/man/zh/man1m/vxdarestore.1m
/opt/VRTS/man/zh/man1m/vxdco.1m
/opt/VRTS/man/zh/man1m/vxdctl.1m
/opt/VRTS/man/zh/man1m/vxddladm.1m
/opt/VRTS/man/zh/man1m/vxdg.1m
/opt/VRTS/man/zh/man1m/vxdisk.1m
/opt/VRTS/man/zh/man1m/vxdiskadd.1m
/opt/VRTS/man/zh/man1m/vxdiskadm.1m
/opt/VRTS/man/zh/man1m/vxdiskconfig.1m
/opt/VRTS/man/zh/man1m/vxdisksetup.1m
/opt/VRTS/man/zh/man1m/vxdiskunsetup.1m
/opt/VRTS/man/zh/man1m/vxdmpadm.1m
/opt/VRTS/man/zh/man1m/vxedit.1m
/opt/VRTS/man/zh/man1m/vxencap.1m
/opt/VRTS/man/zh/man1m/vxevac.1m
/opt/VRTS/man/zh/man1m/vxibc.1m
/opt/VRTS/man/zh/man1m/vxinfo.1m
/opt/VRTS/man/zh/man1m/vxintro.1m
/opt/VRTS/man/zh/man1m/vxiod.1m
/opt/VRTS/man/zh/man1m/vxlicense.1m
/opt/VRTS/man/zh/man1m/vxmake.1m
/opt/VRTS/man/zh/man1m/vxmemstat.1m
/opt/VRTS/man/zh/man1m/vxmend.1m
/opt/VRTS/man/zh/man1m/vxmirror.1m
/opt/VRTS/man/zh/man1m/vxnotify.1m
/opt/VRTS/man/zh/man1m/vxplex.1m
/opt/VRTS/man/zh/man1m/vxprint.1m
/opt/VRTS/man/zh/man1m/vxr5check.1m
/opt/VRTS/man/zh/man1m/vxreattach.1m
/opt/VRTS/man/zh/man1m/vxrecover.1m
/opt/VRTS/man/zh/man1m/vxrelayout.1m
/opt/VRTS/man/zh/man1m/vxrelocd.1m
/opt/VRTS/man/zh/man1m/vxresize.1m
/opt/VRTS/man/zh/man1m/vxrlink.1m
/opt/VRTS/man/zh/man1m/vxrootmir.1m
/opt/VRTS/man/zh/man1m/vxrvg.1m
/opt/VRTS/man/zh/man1m/vxsd.1m
/opt/VRTS/man/zh/man1m/vxserial.1m
/opt/VRTS/man/zh/man1m/vxsparecheck.1m
/opt/VRTS/man/zh/man1m/vxspcshow.1m
/opt/VRTS/man/zh/man1m/vxstat.1m
/opt/VRTS/man/zh/man1m/vxtask.1m
/opt/VRTS/man/zh/man1m/vxtrace.1m
/opt/VRTS/man/zh/man1m/vxunreloc.1m
/opt/VRTS/man/zh/man1m/vxunroot.1m
/opt/VRTS/man/zh/man1m/vxvol.1m
/opt/VRTS/man/zh/man4/vol_pattern.4
/opt/VRTS/man/zh/man4/vxmake.4
/opt/VRTS/man/zh/man7/vxconfig.7
/opt/VRTS/man/zh/man7/vxdmp.7
/opt/VRTS/man/zh/man7/vxinfo.7
/opt/VRTS/man/zh/man7/vxio.7
/opt/VRTS/man/zh/man7/vxiod.7
/opt/VRTS/man/zh/man7/vxtrace.7
/opt/VRTSvxms/lib/map/libvxdmp.so
/opt/VRTSvxms/lib/map/libvxvm.so
/opt/VRTSvxvm/include/libvxvmsc.h
/opt/VRTSvxvm/lib/libvxvmsc.so
/sbin/vxconfigd.SunOS_5.6
/sbin/vxconfigd.SunOS_5.7
/sbin/vxconfigd.SunOS_5.8
/sbin/vxconfigd.SunOS_5.9
/sbin/vxdg
/sbin/vxdmpadm
/usr/lib/devfsadm/linkmod/VRTS_vxvm_link.so.SunOS_5.6
/usr/lib/devfsadm/linkmod/VRTS_vxvm_link.so.SunOS_5.7
/usr/lib/devfsadm/linkmod/VRTS_vxvm_link.so.SunOS_5.8
/usr/lib/devfsadm/linkmod/VRTS_vxvm_link.so.SunOS_5.9
/usr/lib/libarray.so
/usr/lib/libvrascmd.so
/usr/lib/locale/fr/LC_MESSAGES/vxvm.mesg
/usr/lib/locale/fr/LC_MESSAGES/vxvmshm
/usr/lib/locale/ja/LC_MESSAGES/vxvm.mesg
/usr/lib/locale/ja/LC_MESSAGES/vxvmshm
/usr/lib/locale/zh/LC_MESSAGES/vxvm.mesg
/usr/lib/locale/zh/LC_MESSAGES/vxvmshm
/usr/lib/vxvm/bin/egettxt
/usr/lib/vxvm/bin/i18n_echo
/usr/lib/vxvm/bin/strtovoff
/usr/lib/vxvm/bin/vxa5kchk
/usr/lib/vxvm/bin/vxapslice
/usr/lib/vxvm/bin/vxbadcxcld
/usr/lib/vxvm/bin/vxbaddxcld
/usr/lib/vxvm/bin/vxbootsetup
/usr/lib/vxvm/bin/vxcap-part
/usr/lib/vxvm/bin/vxcap-vol
/usr/lib/vxvm/bin/vxcheckda
/usr/lib/vxvm/bin/vxchksundev
/usr/lib/vxvm/bin/vxckdiskrm
/usr/lib/vxvm/bin/vxclustadm
/usr/lib/vxvm/bin/vxcntrllist
/usr/lib/vxvm/bin/vxconfigbackupd
/usr/lib/vxvm/bin/vxconvarrayinfo
/usr/lib/vxvm/bin/vxcxcld
/usr/lib/vxvm/bin/vxdarestore
/usr/lib/vxvm/bin/vxdevlist
/usr/lib/vxvm/bin/vxdevpromnm
/usr/lib/vxvm/bin/vxdisksetup
/usr/lib/vxvm/bin/vxdiskunsetup
/usr/lib/vxvm/bin/vxdxcld
/usr/lib/vxvm/bin/vxedvtoc
/usr/lib/vxvm/bin/vxeeprom
/usr/lib/vxvm/bin/vxencap
/usr/lib/vxvm/bin/vxevac
/usr/lib/vxvm/bin/vxmirror
/usr/lib/vxvm/bin/vxmkboot
/usr/lib/vxvm/bin/vxmksdpart
/usr/lib/vxvm/bin/vxnewdmname
/usr/lib/vxvm/bin/vxparms
/usr/lib/vxvm/bin/vxpartadd
/usr/lib/vxvm/bin/vxpartinfo
/usr/lib/vxvm/bin/vxpartrm
/usr/lib/vxvm/bin/vxpartrmall
/usr/lib/vxvm/bin/vxprtvtoc
/usr/lib/vxvm/bin/vxr5check
/usr/lib/vxvm/bin/vxr5vrfy
/usr/lib/vxvm/bin/vxreattach
/usr/lib/vxvm/bin/vxrelocd
/usr/lib/vxvm/bin/vxresize
/usr/lib/vxvm/bin/vxroot
/usr/lib/vxvm/bin/vxrootmir
/usr/lib/vxvm/bin/vxslicer
/usr/lib/vxvm/bin/vxspare
/usr/lib/vxvm/bin/vxsparecheck
/usr/lib/vxvm/bin/vxswapctl
/usr/lib/vxvm/bin/vxswapreloc
/usr/lib/vxvm/bin/vxtaginfo
/usr/lib/vxvm/bin/vxunreloc
/usr/lib/vxvm/bin/vxunroot
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxautoconfig.SunOS_5.6
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxautoconfig.SunOS_5.7
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxautoconfig.SunOS_5.8
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxautoconfig.SunOS_5.9
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxdevwalk.SunOS_5.6
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxdevwalk.SunOS_5.7
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxdevwalk.SunOS_5.8
/usr/lib/vxvm/diag.d/config.d/sparcv7/vxdevwalk.SunOS_5.9
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxautoconfig.SunOS_5.6
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxautoconfig.SunOS_5.7
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxautoconfig.SunOS_5.8
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxautoconfig.SunOS_5.9
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxdevwalk.SunOS_5.6
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxdevwalk.SunOS_5.7
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxdevwalk.SunOS_5.8
/usr/lib/vxvm/diag.d/config.d/sparcv9/vxdevwalk.SunOS_5.9
/usr/lib/vxvm/diag.d/kmsgdump
/usr/lib/vxvm/diag.d/kmsgdump32
/usr/lib/vxvm/diag.d/kmsgdump64
/usr/lib/vxvm/diag.d/macros.d/dmp
/usr/lib/vxvm/diag.d/macros.d/dmp_cpuiocount
/usr/lib/vxvm/diag.d/macros.d/dmp_cpuiocount_next
/usr/lib/vxvm/diag.d/macros.d/dmp_cpuiocount_zero
/usr/lib/vxvm/diag.d/macros.d/dmp_ctlr
/usr/lib/vxvm/diag.d/macros.d/dmp_ctlr_list_next
/usr/lib/vxvm/diag.d/macros.d/dmp_ctlr_path_next
/usr/lib/vxvm/diag.d/macros.d/dmp_dev_list
/usr/lib/vxvm/diag.d/macros.d/dmp_dev_list_next_dmpnode
/usr/lib/vxvm/diag.d/macros.d/dmp_dmpnode
/usr/lib/vxvm/diag.d/macros.d/dmp_dmpnode_next
/usr/lib/vxvm/diag.d/macros.d/dmp_dmpnode_next_ptr
/usr/lib/vxvm/diag.d/macros.d/dmp_dmpnode_path_next
/usr/lib/vxvm/diag.d/macros.d/dmp_dmpopencount
/usr/lib/vxvm/diag.d/macros.d/dmp_end_dev_list_ctlrs
/usr/lib/vxvm/diag.d/macros.d/dmp_end_dev_list_dmpnodes
/usr/lib/vxvm/diag.d/macros.d/dmp_end_dmp_nodes
/usr/lib/vxvm/diag.d/macros.d/dmp_errq_buf
/usr/lib/vxvm/diag.d/macros.d/dmp_opath_next
/usr/lib/vxvm/diag.d/macros.d/dmp_opaths
/usr/lib/vxvm/diag.d/macros.d/dmp_path
/usr/lib/vxvm/diag.d/macros.d/dmp_print_dev_list_ctlrs
/usr/lib/vxvm/diag.d/macros.d/dmp_print_dev_list_dmpnodes
/usr/lib/vxvm/diag.d/macros.d/dmp_print_errq
/usr/lib/vxvm/diag.d/macros.d/dmp_print_errq_next
/usr/lib/vxvm/diag.d/macros.d/dmp_print_errq_null
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_cpuiocount
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_cpuiocount_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_cpuiocount_zero
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_ctlr
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_ctlr_list_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_ctlr_path_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dev_list
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dev_list_next_dmpnode
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dmpnode
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dmpnode_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dmpnode_next_ptr
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dmpnode_path_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_dmpopencount
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_end_dev_list_ctlrs
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_end_dev_list_dmpnodes
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_end_dmp_nodes
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_errq_buf
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_opath_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_opaths
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_path
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_print_dev_list_ctlrs
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_print_dev_list_dmpnodes
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_print_errq
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_print_errq_next
/usr/lib/vxvm/diag.d/macros.d/sparcv9/dmp_print_errq_null
/usr/lib/vxvm/diag.d/vxasldebug
/usr/lib/vxvm/diag.d/vxaslkey
/usr/lib/vxvm/diag.d/vxautoconfig
/usr/lib/vxvm/diag.d/vxcheckasl
/usr/lib/vxvm/diag.d/vxconfigdump
/usr/lib/vxvm/diag.d/vxdevwalk
/usr/lib/vxvm/diag.d/vxdmpdbprint
/usr/lib/vxvm/diag.d/vxdmpdebug
/usr/lib/vxvm/diag.d/vxdmpinq
/usr/lib/vxvm/diag.d/vxdmpmod
/usr/lib/vxvm/diag.d/vxdmptp
/usr/lib/vxvm/diag.d/vxkprint
/usr/lib/vxvm/diag.d/vxprivutil
/usr/lib/vxvm/lib/vxcommon
/usr/lib/vxvm/lib/vxroot.files
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxap.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxatf.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxeccs.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxemc.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxfujitsu.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxhds.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxhitachi.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxlsiinf.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxnec.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxpurple.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxrdac.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxsena.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxshark.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxssa.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxstorcomp.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxveritas.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxvpath.so
/usr/lib/vxvm/root/etc/vx/lib/discovery.d/libvxxp256.so
/usr/lib/vxvm/root/etc/vx/slib/liba5k.so.2
/usr/lib/vxvm/root/etc/vx/slib/libg_fc.so.2
/usr/lib/vxvm/root/etc/vx/slib/libvxdiscovery.so
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxdmp.SunOS_5.7
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxdmp.SunOS_5.8
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxdmp.SunOS_5.9
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxio.SunOS_5.7
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxio.SunOS_5.8
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxio.SunOS_5.9
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxspec.SunOS_5.7
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxspec.SunOS_5.8
/usr/lib/vxvm/root/kernel/drv/sparcv9/vxspec.SunOS_5.9
/usr/lib/vxvm/root/kernel/drv/vxdmp.SunOS_5.6
/usr/lib/vxvm/root/kernel/drv/vxdmp.SunOS_5.7
/usr/lib/vxvm/root/kernel/drv/vxdmp.SunOS_5.8
/usr/lib/vxvm/root/kernel/drv/vxdmp.SunOS_5.9
/usr/lib/vxvm/root/kernel/drv/vxdmp.conf
/usr/lib/vxvm/root/kernel/drv/vxio.SunOS_5.6
/usr/lib/vxvm/root/kernel/drv/vxio.SunOS_5.7
/usr/lib/vxvm/root/kernel/drv/vxio.SunOS_5.8
/usr/lib/vxvm/root/kernel/drv/vxio.SunOS_5.9
/usr/lib/vxvm/root/kernel/drv/vxio.conf
/usr/lib/vxvm/root/kernel/drv/vxspec.SunOS_5.6
/usr/lib/vxvm/root/kernel/drv/vxspec.SunOS_5.7
/usr/lib/vxvm/root/kernel/drv/vxspec.SunOS_5.8
/usr/lib/vxvm/root/kernel/drv/vxspec.SunOS_5.9
/usr/lib/vxvm/root/kernel/drv/vxspec.conf
/usr/lib/vxvm/root/sbin/vxconfigd.SunOS_5.6
/usr/lib/vxvm/root/sbin/vxconfigd.SunOS_5.7
/usr/lib/vxvm/root/sbin/vxconfigd.SunOS_5.8
/usr/lib/vxvm/root/sbin/vxconfigd.SunOS_5.9
/usr/lib/vxvm/type/fsgen/fs.d/vxfs/vxsync
/usr/lib/vxvm/type/fsgen/vxplex
/usr/lib/vxvm/type/gen/vxinfo
/usr/lib/vxvm/type/gen/vxmake
/usr/lib/vxvm/type/gen/vxmend
/usr/lib/vxvm/type/gen/vxplex
/usr/lib/vxvm/type/gen/vxsd
/usr/lib/vxvm/type/gen/vxvol
/usr/lib/vxvm/type/raid5/vxmake
/usr/lib/vxvm/type/raid5/vxmend
/usr/lib/vxvm/type/raid5/vxplex
/usr/lib/vxvm/type/raid5/vxsd
/usr/lib/vxvm/type/raid5/vxvol
/usr/lib/vxvm/voladm.d/bin/disk.ckinit
/usr/lib/vxvm/voladm.d/bin/disk.config
/usr/lib/vxvm/voladm.d/bin/disk.deport
/usr/lib/vxvm/voladm.d/bin/disk.doinit
/usr/lib/vxvm/voladm.d/bin/disk.encap
/usr/lib/vxvm/voladm.d/bin/disk.hot-off
/usr/lib/vxvm/voladm.d/bin/disk.hot-on
/usr/lib/vxvm/voladm.d/bin/disk.import
/usr/lib/vxvm/voladm.d/bin/disk.init
/usr/lib/vxvm/voladm.d/bin/disk.k-rm
/usr/lib/vxvm/voladm.d/bin/disk.list
/usr/lib/vxvm/voladm.d/bin/disk.menu
/usr/lib/vxvm/voladm.d/bin/disk.mirror
/usr/lib/vxvm/voladm.d/bin/disk.name_scheme
/usr/lib/vxvm/voladm.d/bin/disk.nohotuse-off
/usr/lib/vxvm/voladm.d/bin/disk.nohotuse-on
/usr/lib/vxvm/voladm.d/bin/disk.offline
/usr/lib/vxvm/voladm.d/bin/disk.online
/usr/lib/vxvm/voladm.d/bin/disk.repl
/usr/lib/vxvm/voladm.d/bin/disk.rm
/usr/lib/vxvm/voladm.d/bin/disk.unreloc
/usr/lib/vxvm/voladm.d/bin/disk.vmove
/usr/lib/vxvm/voladm.d/bin/exclude.do
/usr/lib/vxvm/voladm.d/bin/exclude.list
/usr/lib/vxvm/voladm.d/bin/exclude.top
/usr/lib/vxvm/voladm.d/bin/include.do
/usr/lib/vxvm/voladm.d/bin/include.top
/usr/lib/vxvm/voladm.d/bin/inst.allcap
/usr/lib/vxvm/voladm.d/bin/inst.allinit
/usr/lib/vxvm/voladm.d/bin/inst.custom
/usr/lib/vxvm/voladm.d/bin/inst.enclr
/usr/lib/vxvm/voladm.d/bin/inst.one
/usr/lib/vxvm/voladm.d/bin/inst.quick
/usr/lib/vxvm/voladm.d/bin/inst.show_prog
/usr/lib/vxvm/voladm.d/bin/inst.top
/usr/lib/vxvm/voladm.d/help/fr/disk.config.help
/usr/lib/vxvm/voladm.d/help/fr/disk.deport.help
/usr/lib/vxvm/voladm.d/help/fr/disk.encap.help
/usr/lib/vxvm/voladm.d/help/fr/disk.hot-off.help
/usr/lib/vxvm/voladm.d/help/fr/disk.hot-on.help
/usr/lib/vxvm/voladm.d/help/fr/disk.hotadd.help
/usr/lib/vxvm/voladm.d/help/fr/disk.import.help
/usr/lib/vxvm/voladm.d/help/fr/disk.init.help
/usr/lib/vxvm/voladm.d/help/fr/disk.k-rm.help
/usr/lib/vxvm/voladm.d/help/fr/disk.list.help
/usr/lib/vxvm/voladm.d/help/fr/disk.menu.help
/usr/lib/vxvm/voladm.d/help/fr/disk.mirror.help
/usr/lib/vxvm/voladm.d/help/fr/disk.name_scheme.help
/usr/lib/vxvm/voladm.d/help/fr/disk.nameadd.help
/usr/lib/vxvm/voladm.d/help/fr/disk.nohotuse-off.help
/usr/lib/vxvm/voladm.d/help/fr/disk.nohotuse-on.help
/usr/lib/vxvm/voladm.d/help/fr/disk.nohotuseadd.help
/usr/lib/vxvm/voladm.d/help/fr/disk.offline.help
/usr/lib/vxvm/voladm.d/help/fr/disk.online.help
/usr/lib/vxvm/voladm.d/help/fr/disk.privlen.help
/usr/lib/vxvm/voladm.d/help/fr/disk.refresh.help
/usr/lib/vxvm/voladm.d/help/fr/disk.repl.help
/usr/lib/vxvm/voladm.d/help/fr/disk.rm.help
/usr/lib/vxvm/voladm.d/help/fr/disk.unreloc.help
/usr/lib/vxvm/voladm.d/help/fr/disk.vmove.help
/usr/lib/vxvm/voladm.d/help/fr/exclude.shut.help
/usr/lib/vxvm/voladm.d/help/fr/exclude.top.help
/usr/lib/vxvm/voladm.d/help/fr/include.top.help
/usr/lib/vxvm/voladm.d/help/fr/inst.boot.help
/usr/lib/vxvm/voladm.d/help/fr/inst.custom.help
/usr/lib/vxvm/voladm.d/help/fr/inst.dmname.help
/usr/lib/vxvm/voladm.d/help/fr/inst.enclr.help
/usr/lib/vxvm/voladm.d/help/fr/inst.inst.help
/usr/lib/vxvm/voladm.d/help/fr/inst.one.help
/usr/lib/vxvm/voladm.d/help/fr/inst.pend.help
/usr/lib/vxvm/voladm.d/help/fr/inst.quick.help
/usr/lib/vxvm/voladm.d/help/fr/inst.shut.help
/usr/lib/vxvm/voladm.d/help/fr/inst.top.help
/usr/lib/vxvm/voladm.d/help/fr/vxadm.info
/usr/lib/vxvm/voladm.d/help/fr/yorn.help
/usr/lib/vxvm/voladm.d/help/fr/yorn_batch_elem.help
/usr/lib/vxvm/voladm.d/help/fr/yorn_batch_list.help
/usr/lib/vxvm/voladm.d/help/fr/yorn_batch_single.help
/usr/lib/vxvm/voladm.d/help/ja/disk.deport.help
/usr/lib/vxvm/voladm.d/help/ja/disk.encap.help
/usr/lib/vxvm/voladm.d/help/ja/disk.hot-off.help
/usr/lib/vxvm/voladm.d/help/ja/disk.hot-on.help
/usr/lib/vxvm/voladm.d/help/ja/disk.hotadd.help
/usr/lib/vxvm/voladm.d/help/ja/disk.import.help
/usr/lib/vxvm/voladm.d/help/ja/disk.init.help
/usr/lib/vxvm/voladm.d/help/ja/disk.k-rm.help
/usr/lib/vxvm/voladm.d/help/ja/disk.list.help
/usr/lib/vxvm/voladm.d/help/ja/disk.menu.help
/usr/lib/vxvm/voladm.d/help/ja/disk.mirror.help
/usr/lib/vxvm/voladm.d/help/ja/disk.nameadd.help
/usr/lib/vxvm/voladm.d/help/ja/disk.nohotuse-off.help
/usr/lib/vxvm/voladm.d/help/ja/disk.nohotuse-on.help
/usr/lib/vxvm/voladm.d/help/ja/disk.nohotuseadd.help
/usr/lib/vxvm/voladm.d/help/ja/disk.offline.help
/usr/lib/vxvm/voladm.d/help/ja/disk.online.help
/usr/lib/vxvm/voladm.d/help/ja/disk.refresh.help
/usr/lib/vxvm/voladm.d/help/ja/disk.repl.help
/usr/lib/vxvm/voladm.d/help/ja/disk.rm.help
/usr/lib/vxvm/voladm.d/help/ja/disk.unreloc.help
/usr/lib/vxvm/voladm.d/help/ja/disk.vmove.help
/usr/lib/vxvm/voladm.d/help/ja/exclude.shut.help
/usr/lib/vxvm/voladm.d/help/ja/exclude.top.help
/usr/lib/vxvm/voladm.d/help/ja/include.top.help
/usr/lib/vxvm/voladm.d/help/ja/inst.boot.help
/usr/lib/vxvm/voladm.d/help/ja/inst.custom.help
/usr/lib/vxvm/voladm.d/help/ja/inst.dmname.help
/usr/lib/vxvm/voladm.d/help/ja/inst.inst.help
/usr/lib/vxvm/voladm.d/help/ja/inst.one.help
/usr/lib/vxvm/voladm.d/help/ja/inst.pend.help
/usr/lib/vxvm/voladm.d/help/ja/inst.quick.help
/usr/lib/vxvm/voladm.d/help/ja/inst.shut.help
/usr/lib/vxvm/voladm.d/help/ja/inst.top.help
/usr/lib/vxvm/voladm.d/help/ja/vxadm.info
/usr/lib/vxvm/voladm.d/help/ja/yorn.help
/usr/lib/vxvm/voladm.d/help/ja/yorn_batch_elem.help
/usr/lib/vxvm/voladm.d/help/ja/yorn_batch_list.help
/usr/lib/vxvm/voladm.d/help/ja/yorn_batch_single.help
/usr/lib/vxvm/voladm.d/help/zh/disk.deport.help
/usr/lib/vxvm/voladm.d/help/zh/disk.encap.help
/usr/lib/vxvm/voladm.d/help/zh/disk.hot-off.help
/usr/lib/vxvm/voladm.d/help/zh/disk.hot-on.help
/usr/lib/vxvm/voladm.d/help/zh/disk.hotadd.help
/usr/lib/vxvm/voladm.d/help/zh/disk.import.help
/usr/lib/vxvm/voladm.d/help/zh/disk.init.help
/usr/lib/vxvm/voladm.d/help/zh/disk.k-rm.help
/usr/lib/vxvm/voladm.d/help/zh/disk.list.help
/usr/lib/vxvm/voladm.d/help/zh/disk.menu.help
/usr/lib/vxvm/voladm.d/help/zh/disk.mirror.help
/usr/lib/vxvm/voladm.d/help/zh/disk.nameadd.help
/usr/lib/vxvm/voladm.d/help/zh/disk.nohotuse-off.help
/usr/lib/vxvm/voladm.d/help/zh/disk.nohotuse-on.help
/usr/lib/vxvm/voladm.d/help/zh/disk.nohotuseadd.help
/usr/lib/vxvm/voladm.d/help/zh/disk.offline.help
/usr/lib/vxvm/voladm.d/help/zh/disk.online.help
/usr/lib/vxvm/voladm.d/help/zh/disk.refresh.help
/usr/lib/vxvm/voladm.d/help/zh/disk.repl.help
/usr/lib/vxvm/voladm.d/help/zh/disk.rm.help
/usr/lib/vxvm/voladm.d/help/zh/disk.unreloc.help
/usr/lib/vxvm/voladm.d/help/zh/disk.vmove.help
/usr/lib/vxvm/voladm.d/help/zh/exclude.shut.help
/usr/lib/vxvm/voladm.d/help/zh/exclude.top.help
/usr/lib/vxvm/voladm.d/help/zh/include.top.help
/usr/lib/vxvm/voladm.d/help/zh/inst.boot.help
/usr/lib/vxvm/voladm.d/help/zh/inst.custom.help
/usr/lib/vxvm/voladm.d/help/zh/inst.dmname.help
/usr/lib/vxvm/voladm.d/help/zh/inst.inst.help
/usr/lib/vxvm/voladm.d/help/zh/inst.one.help
/usr/lib/vxvm/voladm.d/help/zh/inst.pend.help
/usr/lib/vxvm/voladm.d/help/zh/inst.quick.help
/usr/lib/vxvm/voladm.d/help/zh/inst.shut.help
/usr/lib/vxvm/voladm.d/help/zh/inst.top.help
/usr/lib/vxvm/voladm.d/help/zh/vxadm.info
/usr/lib/vxvm/voladm.d/help/zh/yorn.help
/usr/lib/vxvm/voladm.d/help/zh/yorn_batch_elem.help
/usr/lib/vxvm/voladm.d/help/zh/yorn_batch_list.help
/usr/lib/vxvm/voladm.d/help/zh/yorn_batch_single.help
/usr/lib/vxvm/voladm.d/lib/vxadm_lib.sh
/usr/lib/vxvm/voladm.d/lib/vxadm_syslib.sh
/usr/sbin/in.vxrsyncd
/usr/sbin/vradmin
/usr/sbin/vradmind
/usr/sbin/vrnotify
/usr/sbin/vrport
/usr/sbin/vxassist
/usr/sbin/vxclust
/usr/sbin/vxdco
/usr/sbin/vxdctl
/usr/sbin/vxddladm
/usr/sbin/vxdg
/usr/sbin/vxdisk
/usr/sbin/vxdiskadd
/usr/sbin/vxdiskadm
/usr/sbin/vxdiskconfig
/usr/sbin/vxedit
/usr/sbin/vxibc
/usr/sbin/vxinfo
/usr/sbin/vxinstall
/usr/sbin/vxiod
/usr/sbin/vxmake
/usr/sbin/vxmemstat
/usr/sbin/vxmend
/usr/sbin/vxnetd
/usr/sbin/vxnotify
/usr/sbin/vxplex
/usr/sbin/vxprint
/usr/sbin/vxrecover
/usr/sbin/vxrecover.wrap
/usr/sbin/vxrelayout
/usr/sbin/vxrlink
/usr/sbin/vxrsync
/usr/sbin/vxrvg
/usr/sbin/vxsd
/usr/sbin/vxspcshow
/usr/sbin/vxstart_vvr
/usr/sbin/vxstat
/usr/sbin/vxtask
/usr/sbin/vxtrace
/usr/sbin/vxvol

Problem Description:

Note: VERITAS Incident Numbers are included in parenthesis.
 
(24329) vxconfig help message incorrect
(97351) porting upgrade_start, upgrade_finish, vxunroot, with some enhancement
(97525) Cannot open file /etc/vx/lib/discovery.d/libvxssa.so during boot
(100379) VxVM: Diskgroup creation is failing if two vxdg commands are given simultaniously
(101657) Replacing a disk can violate a photon array license
(103065) minor formatting bug vxdiskadm (reported by Japan)
(103403) VVR:Description for vxrlink stats not correct in man page.
(105230) SOLARIS 9: pkgrm VRTSvxvm panics the system
(106051) VVR:Changing the SRL Protection from autodcm to off during resync, does not stop resync 
(106277) vxassist maxsize|make takes more time to complete (15Hr sometimes)
(110031) VxVM: having install-db, trying to encapsulate disk will re-create rootdg.
(110917) vxassist snapstart with nmirror= > 2 does not work
(113044) .../fmr2/import/import.tc does not test correctly
4719356 (113777) Document fix: Customized Table Header location is confusing and not intuitive
(114693) Various issues with vxdmpadm usage messages and man page
(115493) VVR: SRVM TC ru_chk_nm_version_dbg.tc hits assert
(116286) VVR:Optimize check message waitq function to accumulate all ready sios and call I/O deamon queue to avoid acquire/release of spinlock multiple times
(116613) VxVMCert : DMP Test Addition of Path gets into a continous loop
4479879 (116784) vxdiskadm option 20 (yes) will change drives STATUS from "error" to "offline"
4930738 (118641) vxconfigd coredumps when running "vxdg -g <group> -k rmdisk diskname"
4962757 (119531) CVM: DRL : panic in voldrl_moveto_mru
4794938 (119541) VxVM doesn't correctly support volumes of greater than 1 terabyte
(120124) VRAS: repstatus should display most up-to-date information
(120435) Change modinfo and pstamp for VM 4.0 builds
(120669) VVR:vxedit set command should not allow role transfer if rlinks are connected
(120900) VRAS: after delsec, printrvg still shows the deleted Secondary.
(121757) VxVM: make syslogging default in vxvm-sysboot file.
(121782) VRAS: vradmind can generate duplidate RDSIds, which can cause coredumps
(122218) VRAS: vradmind hangs forever while executing a series of consecutive vradmin startrep/stoprep commands
(122391) ../scripts/admin/volassist/convert/concat.tc panics the system
4836017 (122984) Patch 112392-04 does not list required patches
(123806) FMR2: multiple snapshots of a volume taken in the same command are not tracked correctly
(123974) T3 support: DMP need to use FNDELAY to allow sense data to be captured
(124733) VVR:Optimize the update queue search operation that finds and returns the first update that hasn't been sent to the given replica
(124991) vxconfigd dumps core during zrelayout/crash_dbg.tc
(124998) FMR:snapshot with readonly option creates ss and is 100% dirty
(125234) vxconfigd hang after 117 vxstat processes running in the machine
(125640) VVR:System panics if a volume under RVG is dissociated while DCM bits are being marked.
(125975) VRAS: after running a sequense of consecutive vxvol assoc/dis commands, running a vradmin command can fail unexpectedly.
(126066) VVR:If a disconnect happens during DCM replay of multiple volumes at a point when updateq has updates from more than 1 volume, then we end up comparing the current update's block number with replay_addr of another volume
(126244) VVR:Converting Primary to Secondary does not clear the dcm_logging flag
(126701) Production cluster had various filesystems hang
(126965) VRAS: A vradmin command can hang if a binary executed internally by the vradmin command does not exist.
(127515) CVM fmr/fmrlogsz.tc fails occasionally with master message
(127728) VRAS: vradmin syncrvg doesn't use appropriate network
(127894) VRAS: Data status value is incorrect in repstatus output
(127936) VRAS: vradmind dumps core when run syncrvg command with wrong Secondary hostname
(127937) VRAS: syncrvg/syncvol commands only perform the sync to 1 host when the command is run to sync to multiple hosts.
(127966) VRAS: after migrate command, new repstatus values are not sent to the Secondary
(128159) VRAS:vradmin repstatus doesn't always give correct output for "Logging to :" field.
(128216) vxrecover core dumps if given non-existent object as input.
(128378) GLM slave node stuck in vxg_api_deinitlock via volcvm_gab_joindone
(128434) rem_drv exit status may not be reliable
(128450) VVR:"Cannot find any free port to bind" message is displayed when rlinks try to connect
(128503) I18N: Need to remove man.cf under /opt/VRTS/man/zh, or it won't display correct localized language under man page.
(128591) vxdg -o ejectkey gets errors on A/A JBOD but still expels
(129060) VRAS: vradmind dumps core when a vradmin command is killed by hitting ^C twice.
(129295) Sol: encapsulation does not check for rootvol in the group
4846600 (129377) NODE_EXPLICIT and DMPNODE_EXPLICIT do not get reset after migration
(129462) FMR-CVM - Map manipulations are not properly interlocked with I/Os on slave
(129629) VxVM is not starting with VE_LOG_BAD error on second reboot after 3rd mirror break off from rootvol.
(129927) VRAS: vradmind dumped core due to a dereference of a null pointer.
(130494) VRAS: vradmind dumped core in vrcache due to incorrect use of erase() and pointer iterator.
(130774) FUJITSU claim_device: fjget_path_mode failure
(131170) creating snapshot causes segmentation coredump
(131175) VVR:vradmind log reports a lot of vxtrace dropped event messages
4975602 (131297) recursive mutex_enter in dmp_get_shared_lock, CVM on Clariion using only DMP without PowerPath
4869501 (131368) CVM: VOLOBJ_MV_FIRSTW flag incorrectly remains set causing close to hang
(131508) VVR:Data corruption occurs because start update message is not sent to the Secondary after Primary reboots
(131595) Cannot set spare flag via vxdiskadm.  dmname "d1" matches daname of c#t#d1ds2"
(131596) vxdisksetup fails with "expr: syntax error" and "test: argument expected" if disk geometry cannot be read
(131823) VxVM: VM is recognising disks from other ( V880, 3510 etc) enclosure as SENA disks
(131928) VVR: VRAS: stoprep after takeover hangs in multi secondary config
(132254) VRAS: vradmind dumped core due to invalid address alignment
(132267) A/P array Failback does not work in CVM DMP
4892045 (132680) 113210-02 postpatch scripts test live partiton instead of alternate partition
(132808) VRAS: vradmind hit assert in IpmHandle::unregHandle()
(132857) VRAS: syncvol fails with error of Primary dg not authenticated even when the Primary dg is indeed authenticated on the Secondary host
(132895) Sol: disk init lists all partitions instead of entire disk
(133070) The Fujitsu-Siemens Primepower arrays no longer have the eeprom set properly when encapsulating
(133350) CVM/GAB panic in vol_reservegab_recv via gab_deliver_loop during join
(133481) vxvol core dumps in common_start_resync
4881620 (133579) V880 is unbootable after attempting to dual-path (multipath) internal disk
4900508 (133579) Consider updating VxVM JBOD info to include non-Seagate JBOD FC disks
(133623) VRAS: vradmin hangs if the request is unknown on the remote side.
4903611 (134055) Unwanted console messages for plexes/volumes on CVM Master node
(134234) TRANS_MAX_TIMEOUT needs to be increased or should be made tunable
(134236) vxassist relayout not handling VE_RESTART at all places
(134383) VVR:System panics during recovery, if an rlink is dcm active and there are no data volumes associated.
(134510) CVM: neighbor field not set properly after a reconfiguration in certain conditions
(134637) Read Capacity I/O Fencing Solaris 9 failure
4925410 (134661) Missing documentation on allowing non-root users to run VEA gui
(134811) VVR: VRAS: vradmin addvol command is not allowed when there is no datavolumes in the RVG.
(134883) SxRT 4.0 CVM 4.0F deadlock between transaction code and reconfig code, resulting is hung reconfig
(134946) Sol: SENA is not recognised when MPxIO is enabled on the machine
(135098) VVR:Panic occurs while atempting to attach an rlink if RVG is in FAIL state due to SRL header error
(135214) VVR:Rlinks do not connect after takeover because the acting_secondary flag does not get cleared when rlink is detached
(135228) VVR: VRAS: vradmin ibc fails to rollback resulting in frozen sec rlink
(135270) VVR:Copying a resent packet over a packet that had been correctly received earlier can lead to data corruption.
(135454) vxsync: /etc/mnttab: Too many open files
(135582) VxVM: IBM's SAN.VC support for Solaris as TPD device.
(135652) Attempt to unregister SCSI-3 PR keys for unfenced dg's
(135682) Data corruption with DRL if system crashes before klogging plex detach
(135698) VRAS:Session doesn't get closed after hitting ^C for vradmin -wait resync command.
(135728) VRAS: in RU testing, after some vradmin command, the Secondary can remain frozen, preventing further updates to be applied on the Secondary
(135744) VRAS: in multi-secondaries RDS, startrep with autosync to one Secondary reports the others as "resync in progress"
(135786) Termination of 'layered volume' OR 'volume with DRL' creation (SIGTERM signal) leaves the volume in SYNC state
(135906) CVM miscellaneous kmsgdump changes
(135917) VxVM : kmsgdump should not RESET kernel messages once it was run
(136128) Hitting dmp_io_failed_threshold should log a console message
(136166) VVR:Data corruption occurs because the process data ack function does not check both catchupq and main updateq to find the first pending update
(136224) dmp_io_failed_threshold default of 600 seconds is dangerous
(136307) Update modinfo and pstamp
(136319) VVR: VRAS: vradmin resizevol fails even when there is enough space
(136404) No primary path failback  happens with A/PG arrays.
(136506) DMP: vxconfigd core dump after 'vxdmpadm getsubpaths dmpnodename=vpath20c'
(136610) VRAS: after delsec, re-addsec to the same secondary hangs
4884319 (136641) S85vxvm-startup2 will copy new shared libraries while vxconfigd is running
(136824) vxstat reports impossibly large avg write times
4928807 (136853) VxVM - After installation of patch - some libraries cannot be linked
(136989) SOL VxVM: vxconfigd is dumping core if /dev/cfg has invalid entries
(137025) hung during vxdisk -f init <newdisk> via vxdiskadm.
(137139) VRAS: Hit assert in vradmind due to VRASCache reinit happened during Session
(137157) VVR:System panics during deport of disk group when MODS enabled
(137176) TED assert when doing an IO from a slave in vol_open_device
(137311) DDL: Panic running ddl/foreign.tc#5 on IBM Shark array w/ VPATH driver
(137452) Snapshot of multiple volumes with ufs and vxfs atop yields error msgs
(137641) vxconfigd core dumps in dmp_get_exclude_info() due to NULL pointer reference
(137670) TED_ASSERT in vol_open_device and vol_close_device are not needed
(138098) VRAS: repstatus shows Data Status as "consistent" on secondary when secondary RLink is detached
(138205) CVM: slave join fails due to unexpected change in errno value
(138249) vxdisksetup -i works on "bootdisk" while it is MOUNTED, making system unusable
(138285) IBM SANVC luns with VPATH behaving unpredictably on Solaris VM3.5 and VM 3.2
(138389) performance degradation while running a volume sync
4970610 (138553) CVM/SC30: Moving of quiesce ioctl to step1 to modify the join behaviour
4887356 (138553) 2 slave nodes in endless reconfiguration loop after power down interconnect
(138688) VVR:Rlinks do not connect when EAGAIN returns a +ve value due to resource shortage.
(138740) copystr() should handle errno == EAGAIN and ENOMEM from xcopy().
(138822) VXDCTL enable takes long time on host with JNI FCE2 - 6412 HBA
4911443 (138877) Sol 10-  VxVM postinstall script should remove pathname when invoking add_drv
(139210) path closed even if not open due to a bug in gendmpclose
(139484) VVR:On a 32-bit machine if the system is up for more than 248 days then due to a bug in the code, the rlink connection code does not complete and the rlink does not connect
4957502 (139765) when replacing a bootdisk, vxbootsetup is not getting called
(139796) vxcheckasl giving Error opening shared library libvxsena.so
(139915) CVM: vold_getrequest waits even when client still has more to send
(140345) readme file update
(140396) README file update
(140451) FFDC: Need ot preserve symbol tables in vxconfigd and all user-level utility binaries
(140484) snapback can be slow in CVM with many snapbacks together
(140726) VVR: VRAS: 'vradmin printrvg' shows incorrect output after migrating an application using GCM
(140743) system panics if vxdctl enable issued with one path disabled
(140965) CVM performance of join times and master takeovers
(141004) VVR: VRAS: many simultaneous startrep's (with autosync) can result in vradmind temporarily losing heartbeat to its peers and causing further startrep commands to fail
(141076) VxVM: exec_sync() should check for exit codes also from 'vxsync'
(141244) I18N/L10N: Wrong error message displayed for invalid VM CDS operation
(141578) snapprint doesn't report snapshot vol len
4896990 (141650) postinstall script in patch 113595-04 fails when -R option is given to patch
(141657) ASL's for IBM SANVC don't report in "vxddladm listsupport" after install
(141844) panic when multiple snapprints are run in parallel
4983404 (142002) After installing 112392-04 DRL plexes fail to recover upon disk replacement
4975998 (142245) VxVM: DMP path failover does not work on importing dg with T4 ( StorEdge 6120 )
(142285) vxeeprom doesn't correct Fujitsu disk string
(142420) Change modinfo and pstamp for VM 3.5MP3
4991788 (142751) VxDMP assigns primary role to both of SE6120-PP's paths and does not failback to the original path after the failed path has been reset
(142957) DMP config test #10 "I/O Failover/Failback test" needs to be reviewed. 
(143003) VXVM: value for voliomem_maxpool_sz in /etc/system is ignored
(143020) VXVM: PHOTON LICENSE was not generated when all SENA devices excluded from DMP
(143302) Sol: System panics during dmp testing
(143362) CVM: Hang in kmsg sender ( vol_kmsg_sender )
(143536) FMR: vxplex dis/att not working properly on fmr volumes
(143597) VXVM: DMP is having trouble to failover ( from VM 3.5mp2 ) in some configurations
4990011 (143602) VxDMP fails to failover on SE6120 controller failure
(143661) Data corruption due to vxdisksetup being run on online disk
(143700) CVM: deadlock as vol_kmsg_respond_common drop messages in quiesced state
(143812) gen_update_status paniced deu to NULL list_of_paths
(143858) publen wrongly calculates greater than disklen in sliced_init_internal
(144052) VVR: Panic in vol_ru_start_replica while accessing multiupdate in ATOMIC_SENDING phase
(144080) SOL - 35p3 upgrade_finish fails with segmentation fault core dumped
(144085) VVR: Autosync of volumes over 1TB size has problems in 3.5
(144221) T3 Storedge 6120 LUN ownership incorrect
 
(from 112392-06)
 
(130134) "vxdisksetup -ie" overlap the private and public region
 
 
(from 112392-05)
 
4771018 VxVM 3.5 Hardware Notes doc should reflect the non support of mp_support=std
(24412) subvolume SIO's not being freed
4295380 (28606) VxVM does not correctly set dump device
4228190 (34523) vxmake -d command cannot handle large description file.
4648109 (43033) SOL: dmp_per_cpu_stats_t should be 128 bytes long
(64898) 3.2e ap config test 2. VxVM basic functionality Test.
(65002) 3.2e ap config test 6. Path restoration test for devices under AP cntrl
(66749) pkgchk VRTSvxvm error; vxserial not properly linked to vxlicense
4233507 (73476)  Utility required to save VxVM configuration information for disaster recovery
4487591 (76135)  vxddladm man page corrections
4491997 (76135)  vxddladm man page corrections
4490375 (82309)  vxddladm excludearray vid/pid shouldn't indicate entire
                 library has been excluded
4494006 (77815) vxvol help out of sync with the man pages
4501921 (113692) vxunroot does not work as documented
(80615) mirrored volume is not disabled when it lost the last ACTIVE plex during resync
(84616) Add new TC's for ddl
(85455) vold_dm_as_da wrongly assumes that all danames correspond to dmp devices
(88421) I18N - Check in 3.5 I18N changes.
(90710) replacing a disk when we have multiple DRL's does not clear FAIL state
(90840) vxrelayout dumps core with Segmentation Fault when striping column
(93840) the requirement of stopping and starting the whole layered volume
(93946) creating a shared disk group does not register keys. Need to deport and import the diskgroup.
4628999 (94225) Excluded pathnames were displayed contiguously in single line
4655082 (98658)  vxmirror using Sun StorEdge S1 drives create incorrect root
                 devaliases (vx-rootdisk and vx-disk01)
(96107) VVR: resyncfromreplica.tc#7 fails occasionally
(98779) RFE: Request to handle I/O to write-disabled EMC devices in dmp
(99233) Refine Solaris VxVM package scripts
4685297 (100354) world writable files in /var/vx and /etc/vx
(100598) vxvm VOL_DFLT_IOSIZE should be increased
4630477 (101371) bogus device in `vxdisk list` output after replacing a disk drive
(101842) vxdmpadm include dumps core
(102266) VVR: ted_assert in  vol_rv_service_update:protocol error (1)
(102350) If relayout of a volume fails due to lack of temp space the error message printed does not reflect the problem.
4775892 (102494) '/usr/sbin/prtconf: getexecname() failed' on system boo
(102509) upgrade_start doesn't handle enclosure name on rootdisk.
(102655) VxVM: IBM SDD (VPATH) support/co-existence on Solaris.
(102755) VM 3.5s - upgrade_finish runs with a complain "Incorrect protocol version" when upgrading from 3.1.1 to 3.5s
(102799) relayout fails with
(102817) various vxvm errors during boot-up on Japanese solaris  system
(102913) subcmds "mirror" and "move" and others in vxassist hit VE_NOTRANS sometimes
(103439) Minor error in vxdg syntax message
(103649) Volume badlog flag set to 'on' , with valid log subdisk available
(103800) vold cores due to NULL point access.
(104205) vxresize runs w/ERROR on resizing concat-pro and stripe-pro of volume.
(104218) VVR: rvg_snapshot.tc#10 Failed
(114280) vxdg init hang with I/O fencing upon SCSI-3 PR operation failure
(105230) pkgrm VRTSvxvm sometimes fails to remove the pkg and it panics the system
(105234) drl: vxassist -o ordered make requires logdisk arg too, contrary to sag doc
(105598) vxdisk list fails if disk media name is similar to a non-existant CTD device
(105659) FMR2 - Do not allow the resize of DCO volume
(106045) increase VOLDIPC_MAX_FD to avoid VxVM commands hang
(107261) I/O stops after a drive was pulled on RAID5 volume
(108389) i/o hang on volumes with drl
(108422) vm is trying to create volume even if fmr licence is not there
(108441) vxprint taking a very long time to complete
(108818) FMR: whether to use FMR or not in vxplex and vxrecover should be allowed to be specified in file.
(108867) vxconfigd dumps core during 'vxdctl enable' after pulling out a cable from a SENA AA array
(108888) I18N: untranslated string in vxinstall(vxadm_lib.sh)
(109062) I18N - finish I18N'ize sdscvt for 3.5
(109231) plexes with SNAPDONE state are not detached on i/o error
(109486) Copyright stamps need to be updated in all VM scripts
(109851) vxassist convert applying wrong trigger pt and not checking for simple volume
(110021) FAULT:when panic during vxdg split in vcs cluster; the split operation does not roll backward
(111037) Hit ted_assert in uw_copy_packet
(110508) VVR: Panic in nmcom_server_start due to NULL msgb returned by kmsg_sys_rcvudata
(111143) VVR : changing packet_size during replication leads to data corruption and/or panic
(111793) VRAS: makesec should provide a -f option and not change state of RVG
(111288) postinstall script does not update library file list for pkgchk
(111304) VVR: Do not include SRL write time in data vol avg write time stats
(111894) ROUND read policy not used anymore when a plex is detached (3-plex volumes)
4749183 (112049) VXVM with photon Lic allow RAID5 log outside of photon to be added
(112278) VRAS: repstatus gives incorrect information if Primary is unreachable
(112279) Problems with enclosure based naming after replacing physical disks.
(124957) VRAS: vradmind gives core the 4.0 build on 05/12/03
(112517) vxsync errors needs to be changed to a warning
(112554) vs_pl_cnt (vol_summary's field for plex count) gets negative values on SLAVE when using vxmake to create sd/plex/vol and then deleting the volume
4780047 (112593) Incorrect devalias boot path on Jasper HBA
(125625) Disabling taking snapshots for raid5 volumes using vxassist snapstart
(112686) VVR : replication hangs if packet_size > 65504 is set and an io of size >= 64K is given
(112770) SCSI version for SENA disks does not come correctly
(113023) 3.5 MP1 vxconfigd hung (from vxdctl enable) in dmp_reconfig_update_cur_pri
(113054) vxrecover error while replacing a removed disk with vxdiskadm option#5
(113157) FMR: dgsj/reconf.tc causes vxconfigd to core dump
4629303 (113193) Cannot change log types from DRLSEQ back to Region (DRL)
(113516) update modinfo and pstamp for Point Patch on top of VM 3.5 Patch 1.7
(113606) I18N: EUC-JP locale alias name under Solaris 9
(113693) VRTSvmcvt package should restrict Solaris version to sol8
4491048 (114033) man pages for vxbootsetup refer to wrong command names
4629246 (114060) man pages are not correct for vxplex cp section
4711196 (114288) Encapsulation creates a public region which overlaps private
                 region
4769704 (114479) vxdiskadm opt#5 fails due to vxdisksetup asking for cCtTdD when cCtTdD used!
(114516) Incident to check-in HCL CVM DMP TC's
(114633) vxrelocd fails after switching to enclosure based naming
(114669) Need to modify mb.sh to prune out "CVS" directory in order to build sandbox properly
4490646 (114693) vxdmpadm usage statement is incorrect
(114760) (cvmtc) admin/fmr2/basetest/dcoupdate.tc hangs
4819716 (118003) man page for vxdisksetup needs to be updated with information
                 about 'old_layout' option
(114957) VVR:     Can remove DCM from volume while srlprot=autodcm. System panics when DCM required
(114988) VVR:VRAS: fail to send heartbeat to control CPU usage during autosync
4800160 (115323) vxinstall taking an enormous amount of time on hosts accessing maserati devices
(115325) VVR: vxrlink att fails displaying negative number for volumes over 1TB
4800446 (115328) Vxinstall fails to partition few disks sometimes (document work-around only)
(115520) vxconfigd dumps core in dmp_get_events () for DMP_DA_ADD_EVENT if the enclr is not present in the attr_list
(115607) VVR: Panic in vol_dcm_set_region during DR testing.
4757423 (115645) vxassist fails with  ERROR: Incorrect usage for" vxassist -H" option in vxvm 3.5
(115771) vxdg deport hangup after dg disable
(116105) scripts/admin/fmr/raid5.tc causes panic on TOT
(116454) VVR : Optimize vol_ru_delete_updates update search loop
(116587) VVR: DCM does not deactivate after failover/failback
(116705) VM40 (alpha) - vxunroot fails to recognize root vols when enclosure naming is in used.
(117013) Inappropriate error message with vxdisksetup on an invalid device
(117248) vxinstall/custom_install makes menu empty
(117388) Panic and filessytem corruption after doing "rm *" during a raid5 sd move operation
(117568) will use this incident to detect and fix mem leaks in vxconfigd (using MLScanner)
(117733) VVR: changes in 3.5 srvmtc to test replication between 3.5 and 4.0
(117858) DDL/SENA Testing: Could not open file /etc/vx/array.info for writing
4819736 (118003) manpage of vxdisksetup does not mention the option old_layout
4486602 (118007) vxinstall doesn't display "excluded disks" message for disks in enclosures
4712376 (118011) VM3.5GA: Strange notification message on console from vxvm:vxconfigd when enabling MPXIO
4806363 (118013) Prepatch[44]: test: argument expected during VxVM3.5 MP1 patch 113211-02 install
4822685 (118015) vxdisk list output shows failed disk was spare when it is not
(118064) FMR3: ted assert _vol_syncwait:1a in voldco_reset_state
4817095 (118065) Loss of storage connectivity to CVM master causes all nodes
                 to get I/O errors
(118089) VVR:RU:secondary(4.0) panic due to Memory Overrun error while running efb_dcmactive.tc
(118129) VVR: TCL test 3.3.19 hangs - rv_ackdone_limit = 0
(118172) relayout fails with VE_DG_VERSION even though dg version is at 80
(118186) vxtrace help does not explain all options of the command.
(118243) Change LUN ownership support for Fujitsu GR710, GR720, and GR730 arrays
(118272) Allow non-mirror layouts for vxassist convert operation
(118304) Shadow Image support for DF600 HDS9500 Hitachi Array
(118609) vxbootsetup prints error message test: argument expected
(118770) panic in scsi module during pkgadd of nightly 4.0 package
4723639 (118678) coredump opportunities in vxddladm
(118876) vxresize dumps core while running VRAS TC resizevol/3host-maxsize-resizevol
(119565) DMPNODE not migrated when array type changes
(119864) panic in dmp_dev_t_to_nodep()
(119998) relayout (in 3.2p3 and 3.5mp1) can exhaust dg config space
(120163) DDL: Performance improvement of SENA discovery on Solaris
(120377) memory leak in (vxconfigd) priv_scan () during diskgroup import if an LVM disk is present
(120414) vxdisksetup fails because dogi_darecs_on_device matches wrong devices
(120808) VxVM 3.2p3 vxvm-startup2/vxreattach performance degradation on boot for large configurations
(120830) Generic support of A/P arrays in CVM/DMP
(120903) VRAS: changeip displays error messages partly to stdout and stderr
(120922) assumption about page_length in get_cabinet_id() seems wrong
(121174) DMP Cannot suppress/prevent  EMC array by specifying VID and PID
(121198) VRAS: vradmind dumps core while running efb_mkpri_rpstate.tc
(121651) vxdisksetup doesnot clean the files created in /tmp
(121663) DMP failover/failback does not work for A/P arrays with DBED/AC
(121957) vxconfigd core dumps while doing bascii_copy() in a5k_get_da_sno with SunAP 2.3.1
4886517 (121962) Symbol strfind not referenced in libvxap.so for VxVM 3.5
(122376) VRAS: rolling upgrade between vras 3.5 and vras 4.0
(122471) DMP config test runs w/many errors when array in enclosure based name
(122716) VRAS: secondary should not handle timeout after connected with primary
(122982) users do not see why patchadd of 35mp1 fails because of a typo
(122984) preinstall fails in 35mp1 as required SUN patch is superseded
(123003) volume stuck in SYNC with no sync action
(123102) Race condition may lead to 'vxdmpadm disable ctlr' hangs due to missing signal from 'gendmpiodone()'
(123234) /scripts/kernel/except/ir58257_dbg.tc#2 FAILS on 3.2 and 3.5
(123311) VM: vxconfigd -m disable gives core on 04/29/03 ga3.5_maint nightly build
(123380) Change modinfo for VM 3.5 MP2 patches
(123674) VVR: Increase array sizes in rv_test.h
(123818) dmprestore daemon should not restore failed path of shared A/P array
(123885) ap config TCs still refer to AP_PURPLE
(123907) VVR TCL tedassert in volkiomem_seek
4368933 (123974) T3 support: DMP need to use FNDELAY to allow sense data to be captured
(124214) VVR: rv_ibc_send needs to handle the case in case garbage value is returned
(124315) inst.top.sh refers incorrectly to JBOD and OTHER.
4788268 (124695) CVM: disk group autoimport flag is turned off after Master takeover
4849123 (124864) vxconfigd enabled failed after upgrading to vxvm 3.5
(125217) vxdisksetup: should give Disk puboffset value as specified by user in error message
(125223) "vxvol stopall" should not stop lowerlevel volumes while upper layer volume is mounted and active with IO's
(125599) VRAS: RDS has multiple primary error after changeip
(125906) ../kernel/vxdmp/ap/vol_disable_dbg.tc fails on T3 array.
(125951) VM re-encapsulate root fails silently and system unbootable if vtoc already has private slices
(126184) VVR: panic due to inconsistent srl header entries
(126223) vxassist mirror fails to mirror vlumes of size >1TB
4875401 (126492) vxedit rename can degrade performance of VM
(127241) Solaris: vxwatch missing from VRTSvxvm package.
(127768) vxconfigd hangs in volsiowait during array removal test
(127876) Miscellaneous changes for CVM DMP test suite
(127957) Reoccurance of i71594 in vxvm 3.5
(128048) SOL: Encapsulation fails with enclusure based names
4882902 (128502) Vxconfigd coredumps when photon enclosure is replaced.
(128503) I18N: Need to remove man.cf under /opt/VRTS/man/zh, or it won't display correct localized language under man page.
(128571) potential deadlock in vxdmpadm enable path
4820436 (128610) VM/licensing functionality is not fully enabled in leadville configurations
4937259 (128878) Oracle processes hanging on vol_mv_req_recov_mode
4908473 (128878) CVM: Oracle Resilvering: Need to not duplicate effort in setting MR mode
(128983) vxdisksetup is giving "UNKNOWN ERROR WHILE WRITTING VTOC" when publen and privlen specified
(129080) memory not unmapped after a mmap in crc_file()
(129174) According to Sun, VxVM 3.2p4 can not depend on Solaris patch 108827-XX
(129660) CVM: Hang in kmsg sender
(129694) Some memory leaks in libvxvm
(129776) apauto_set_pgr() clears SCSI-3 PR keys during import
 
 
(from 112392-04)
 
(94225) Excluded pathnames were displayed contiguously in single line
(112129) CORE: master vxconfigd coredump during slaver join
(112380) 3.5 MP1 vxsync core in vol_freeze_cluster; also log update failure caus
es filesystem to be disabled
(108888) I18N: untranslated string in vxinstall(vxadm_lib.sh)
(107756) update modinfo and pstamp for VM 3.5 patch 1
 
(from 112392-03)
 
(28606) VxVM does not correctly set dump device
4421145 (61755) typo in vxdmpadm help output for option getsubpaths
(79959) I18N checkin of help files, and adding disk.refresh.help to prototype file SOL.
(85455) vold_dm_as_da wrongly assumes that all danames correspond to dmp devices
(87807) I/Os stuck in VxVM I/O mempool waitq
(88421) I18N - Check in 3.5 I18N changes.
(89108) vxdiskadm option 4 will remove the only good plex without warning
(90840) vxrelayout dumps core with Segmentation Fault when striping column
(91698) vxdisksetup -i uses -f option of vxdisk
(92524) CVM: DCO update protocol does not handle cluster reconfiguration properly
4504662 (93080) vxdisk list reports disk status incorrectly
(94326) vxresize outputs mkfs output to stdout
(94361) VxVM: Please update vmcert's prototype file for any new tcs.
4479302 (95151) slave node joining of the cluster may cause the master node to crash
(97253) scripts/admin/volassist/make/interrupt.tc faling
(97568) panic attempting to do I/O to an upopened device.
(98069) CVM: not calling volcvm_join_complete even after join is complete
(99216) Initiator hang when disable the primary controller
(99394) vol_alloc() is returning NULL even with VOLMEM_SLEEP flag causing panics
4666269 (99652) Why Volume Manager needs to forceload SUNW,isptwo?
4693346 (99652) vxvm tries to forceload non-needed drivers on 2nd reboot of boot encapsulat.
(99731) CVM: slaves can not join to the new master after master_takeover
(100581) Add CVM support for Hitachi A/P arrays
(100598) vxvm VOL_DFLT_IOSIZE should be increased
(101343) vxinstall could cause mismatch between publen and partition table
(101597) add suppoort for rootability with DMP enabled
(101612) CVM: unloading vxio driver without releasing port v
(101637) memory corruption in vol_dump_disks
(101709) Support scripts should give meaningful msg when encountering a bad disk
4754257 (102047) erroneous complaint that mountpoint is not in rootdg
(102081) rootdisk fails to re-encapsulate after VXVM package remove and reinstall
(102132) Data corruption problem in FMR during snapback.
(102372) some small DMP changes
(102638) upgrade_finish script is looking for vxlicense in /sbin instead of /usr/sbin
(102667) I18N - use of LANG shel variable should be replaced with LC_MESSAGES
(102668) VM 3.5s - array.info file is set @ 555 permissions
(102727) vxmake tag name error
(102962) SxRT3.5 CVM vxvol (recoveries) get stuck in vol_object_ioctl after master takeover
(103005) vxassist mirror sometimes fails silently
(103135) CVM: gab returns EAGAIN during a cluster reconfig, causing master takeover to hang
(103206) Data coruption in FMR (102132)
(103454) In vxdiskadm (option 5) cannot replace a failed pre-3.2 disk with new 3.2 or 3.5 disk layout (CDS), because of smaller publen.
(103590) update modinfo and pstamp for VM 3.5 Point Patch 1
(103745) Node in cluster at OK prompt, causes other system to panic.
(103807) vxassist dumps core.
(103917) "vxassist make" fails with VEX_TIMEOUT
(103927) takeover.tc hung one of the nodes in the cluster during test #4 run
(104091) VM: Quick Install in vxinstall does not exit properly if no disk were selected.
(104177) ASL: ASL packages are modifying /etc/vx/aslkey.d and  /etc/vx/lib/discovery.d directories from 755 to 775,
(104246) DMP issues with VM 3.1.1 and SAN appliance
(104384) diskgroup import is slow for configuration with large number of disks
(104438) vxplex fails to use FMR to resync offline plex
(104469) SPFS/CVM 3.5 b14 - there is no link in /opt/VRTS/bin for vxclustadm
(104541) CVM/FMR vxsync never worked in a cluster
(104656) Group failover failure due to determining incorrect  num_luns   on a controller
(104673) ASL: vxasldebug command fails with "cannot create" error message, DATE is incorrect.
(104742) vxasldebug uses absolute pathnames to tar up /etc/vx/lib/discovery.d/*
(104916) VxVM on Solaris: Timeouts using lbolt can be too short
(105116) VXVM 3.x hotspare of rootdisk fails if disk failure is after a controller failure
(105121) vxrelayout fails with error: record already exists
4724737 (105185) libvxvmsc.h header file missing from VRTSvxvm package
(105372) I18N - prompts in Shell files are not always localized.
(105448) ADD PGR support for active/passive arrays
(105680) VAIL:VVS: Add the VVS Array Config policy feature bit in VM license
(105796) vxms: File permission related problem in vxvm_map_open_id
(105859) update modinfo and pstamp for VM 3.5 Point Patch 2
(106379) vxdg adddisk allows duplicate diskid in DG
(106396) System panics during SPFS array cable pull testing
(106597) check in Solaris SDS to VxVM converter
(106688) ../admin/volnotify/volnotify.tc#2 failing on TOT
(106793) vxdisk list gives wrong info on ATF/4700 array
(106907) VxVM doesn't sync the whole plex after replacing disk
(106908) I18N: upgrade_start and upgrade_finish script
(106910) I18N:VRTSvlic package command in the vxinstall script
(107284) Possible wrong I/O count on objects because of not handling dg_objcpulist correctly
(107301) VAIL:VVS: vxassist fails with -o verify option if license for VVS Features is enabled
(107382) FMR2: a system crash after a disk is replaced by some other disk may result in data corruption.
(107473) SNAPDONE plexes are not resync'd after a crash
(107656) vxinstall should remove install-db if just using old configuration
(107662) I18N: vxdctl mode / vxdctl -c mode
(107756) update modinfo and pstamp for VM 3.5 patch 1
(108138) FMR doesn't resync properly after disk replacement
(108162) vxassist dumps core during relayout
(108615) Mode sense command fails on hitachi 9200 array with presistent reservation (fencing)
(108757) do_tur will loop forever
(108867) vxconfigd dumps core during 'vxdctl enable' after pulling out a cable from a SENA AA array
(108949) 3.5 MP1 vxdiskadm disk replacement says vols mirrored/no data loss when vols not mirrored
(109062) I18N - finish I18N'ize sdscvt for 3.5
(109402) vxdisk list shows Duplicate entries of AP metanodes
(109631) I18N: Update pstamp and release level of localized document packages
(109704) SDS2VxVM conversion not recognizing licensing(sig)
4753143 (109148) VxVM 3.5 does not generate photon license with mpxio enabled
(55730) rootability error msg with vxunroot
(84185) Bug in VOLUIO_ALIGNED() macro
(88005) CVM-TC: layered.tc fails on TOT
(90814) ../kernel/vxdmp/misc/rmdmp.tc#1and _dbg fail on ga3.5_maint
(94296) SxRT3.5 vxinstall appends disk names to Menu line
(99539) SIGLicense : Memory leak in SIGLicense library
(99993) vxconfigd - "remove_dir" function is not releasing the file resources
(104042) VxVM: I/O operation is returning success even it failed in vxio driver
(104444) mirroring of root disk failed
(104926) vxassist make logtype=drlseq silently fails to make DRL
(106277) vxassist maxsize|make takes more time to complete (15Hr sometimes)
(106454) ../coverage/coverage_L_dbg.tc#1 fails on TOT
(108192) output from modinfo in 32p3.2 and 35p1.1 contains a "d" letter.
4656592 (108677) CVM volumes disabled after scshutdown and boot up on all cluster nodes
(109231) plexes with SNAPDONE state are not detached on i/o error
(109462) All VxVM Solaris patches need to always check for required Sun patches
(109656) Panic in hitachi_failback_lungroup for HDS A/P 9200 Array with 3.1 VxVM
(109746) SDS2VxVM conversion getting errors when trans metadevices exist
(109778) CVM support for Hitachi 9500 DF600 APG
(109578) FSQA 3.5MP d4 cfs stress hits BAD TRAP: type=31 in vxglm due to NULL pointer dereference
(110021) FAULT:when panic during vxdg split in vcs cluster; the split operation does not roll backward
(110031) VxVM: having install-db, trying to encapsulate disk will re-create rootdg.
(110267) vxunroot fails to find volumes in rootdisk if bootdisk got replaced
(110341) CVM: SUNW wants vxclust to not start vxconfigd with logging
(110421) SDS2VxVM conversion encountering problems in preconvert1
(110545) Problem unecapsulating after using SDS2VxVM conversion
(110671) preconvert error message to vague in SDS2VxVM procedure
(110702) i18n changes broke message in sdscvt S61vxvmconv
(110758) ted assert in dmp_select_path due to cur_pri_path pointing to unquiesced disabled node
(111011) vxdg or vx commands relocation error
(108174) EMC request dmp to use inqury 83 for Symmetrix arrays LUn serial number
(108573) CVM:TOT: fmr/snapopen.tcs fail.
(110022) FAULT: No share dg imported on one SLAVER node at a 4 node vcs cluster
(111018) vmcvt runs commands in native locale, then interprets output
(55725) VVR: vradmind core dumps when used with large number of volumes
(94274) VVR: vxrlink updates does not give the correct information on secondary
(96061) VVR: Update timestamp for VRTSvrdoc package
(96364) VVR: vxrlink pause hangs for Secondary rlink
(99729) VVR: config status pending flag not getting cleared when slave is paused
(100516) VVR: vxrlink updates command gives spurious value
(100852) VVR: rlink disconnect due to ack timeout on update message
(100901) VVR: SRL full messages not sent to console in case of autodcm
(101271) VVR: pause hang on secondary due to start_update message from primary and pause from secondary do not allow each other to complete
(102642) VVR: hdr/dcm-header does not flush after srl overflow
(103127) VVR: data corruption due to primary assuming to have sent data when it has not
(103714) VVR: VRAS startup scripts should not display No VVR license message
(103326) VVR: Data corruption when secondary rvg is ibc frozen and primary goes in DCM mode
(103389) VVR: problem when two RLINKs try to do srl flush
(103491) VVR: vxconfigd dumps core due to mistake in "msg"
(103845) VVR: panic due to holding of two locks in vol_rvdcm_unlog_update
(104030) VVR: VRAS logs become too large due to unnecessary debug messages
(104428) VVR: Panic in uw_copy_packet() when replication from 32->64
(104482) VVR: license error during upgrade from 3.2 to 3.5
(104617) VVR: vxrsyncd core dumped due to problems with license check string
(105498) VVR: RVG avg write size stat incorrectly includes reads if in passthru
(105930) VVR: vradmin delvol command should not delete an SRL volume
(105946) VVR: rlink disconnects while doing autosync.
(106812) VVR: panic while unloading module during autosync.
(107028) VVR: hang due to deadlock among active, restartq and serial sio
(106822) VVR: vradmind core dumps when ibc scripts pathname is long
(107227) VVR: VRAS: Do not check remote OS during configuration validation
(107559) VVR: Garbled error msg displayed when running multiple vradmin commands
(107746) VVR: vxrvg recover takes long time since SRL header is not flushed.
(108200) VVR: vradmin gives error messages in mixed languages for non-english locale
(108743) VVR: SRL recovery takes very long time because of resyncing of plexes
(109054) VVR: vrnotify sends incorrect notifications for certain events
(110265) VVR: associating a volume after role-reversal leads to config error
(110319) VVR: Remnant config info on secondary after primary rvg is deleted can cause data corruption
(110536) VVR: Data loss in autosync of vol w/regsz > 512 blks & rlink discon/connects
 
 
(from 112392-02)
 
(95151) slave node joining of the cluster may cause the master node
         to crash
(105859) update modinfo and pstamp for VM 3.5 Point Patch 2
 
(from 112392-01)
 
(103206) Data coruption in FMR (102132)
(103745) Node in cluster at OK prompt, causes other system to panic.
(103590) update modinfo and pstamp for VM 3.5 Point Patch 1
(104251) SxRT3.5 i/o's hang on cfs filesystems with dco log volumes and
         snapshots
(104541) CVM/FMR vxsync never worked in a cluster

Patch Installation Instructions:
==================================================================
Table of Contents
------------------------------------------------------------------
Section 1: Installing VxVM 3.5 Patch 3
  1.1 Localized VxVM 3.5
  1.2 Installing Required Sun Patches 
  1.3 JBOD Array Considerations
  1.4 Removing VxVM 3.5 Patch 3
  1.5 Partitioning Disks on SE6120/SE6320 Arrays
 
Section 2: upgrade_start/finish
 
Section 3: Converting from SDS to VxVM
 
Section 4: Using the DRL Sequential Logging Feature
 
Section 5: Using A/P Arrays
 
Section 6: Full Disk Mirroring and Replacement Considerations
 
Section 7: Duplicate Disk ID's
 
Section 8: vxddladm listsupport Considerations (Solaris 9 only)
 
Section 9: vxassist relayout Considerations
 
Section 10: Using vxunroot to Unencapsulate the Rootdisk
 
Section 11: Using devfs to replace a disk
 
Section 12: Suppressing a path from DMP and VxVM in a Multipath 
            Array (Solaris 9 only)
 
Section 13: Error Message when Booting off a Target Driver
 
Section 14: Using Hitachi Arrays
 
Section 15: T3B Firmware Upgrade on Solaris 9
 
Section 16: Replacing a Failed Boot Disk
 
Section 17: Support for Chinese GB18030 encoding
 
Section 18: Recovering from Master Node Failure During a Snapback 
            Operation
 
Section 19: Suppressing Unwanted vxassist Authentication messages When 
            Accessing SAL
 
Section 20: SCSI-3 Fencing on Solaris 9
 
Section 21: Do Not Use Solaris 2.8 Patch 110934-10 or 
            Solaris 2.9 Patch 113713-01
 
Section 22: Troubleshooting a Duplicate Device Entry in vxdisk list
 
Section 23: Issues with vxlictest
  23.1 May Generate Core Dump on Inputting an Incorrect Licensing Key
  23.2 vxlictest -l Should Not Require Key or Feature Name
 
Section 24: Support for IBM-SDD
 
Section 25: Documentation Errata
  25.1 Volume Manager 3.5 Troubleshooting Guide Changes
  25.2 Volume Manager 3.5 Hardware Notes Changes
  25.3 Volume Manager 3.5 User's Guide Changes
  25.4 Volume Manager 3.5 Release Notes Changes
  25.5 Volume Manager 3.5 Administration Guide Changes
  25.6 Volume Manager 3.5 Installation Guide Changes
 
Section 26: Disk Connectivity Policy
  26.1 Global Disk Detach Policy
  26.2 Local Disk Detach Policy
 
Section 27: Backing up VxVM Configuration Data
 
Section 28: Known Issues with JNI HBAs
 
Section 29: Problem When Removing VxVM Package
 
Section 30: Support for Hitachi Arrays
 
Section 31: Localized Man Pages Show Incorrect Text
 
Section 32: Known Issue with the VVR vradmind Daemon
 
Section 33: DMP Tunable: dmp_failed_io_threshold consideration.
  IMPORTANT: Wrong dmp_failed_io_threshold setting can lead to data loss
 
Section 34: Updating jbod.info file on a V880 internal disk enclosure configuration
 
Section 35: Moving a disk device from one physical array slot to another
 
Section 36: Join and Master Failover Times
 
Section 37: cvm Timeout for SunCluster
 
Section 38: Localization Issues
 
Section 39: vxdmp.conf and vxio.conf files overwritten during patch installation
 
------------------------------------------------------------------
 
For late breaking information regarding this patch, please go to the VERITAS 
Support Web Site Content Notice page at the following URL:
 
http://seer.support.veritas.com/docs/267192.htm.
 
===============================
Section 1
Installing the VxVM 3.5 Patch 3
===============================
 
1.1 Localized VxVM 3.5
 
This patch also supports localized releases of VxVM 3.5. When you install
this patch, if previous 3.5 language packages are already installed, it will
replace all the necessary localized packages (language packages and 
messages).
 
1.2 Required Sun Patches
Please make sure that the following Sun patches are present in your system
before installing this patch.
 
If the patches shown in the required list are not already installed, go to
http://sunsolve.Sun.com to download the patch.
 
For solaris 8:
111413 (-06 or higher)
108993 (-18 or higher)
108528 (-14 or higher)
 
For solaris 7:
107473 (-07 or higher)
106541 (-19 or higher)
 
 
For Solaris 6:
105181 (-31 or higher)
 
1.3 JBOD Array Considerations
If you have an array which was previously claimed as jbod,
you may get the following warning message during reboot after the upgrade:
   NOTICE: vxvm:vxdmp: added disk array <disk-array-serial-no>
   vxvm:vxconfigd: WARNING: File /etc/vx/array.info not in proper
   format.
   Regenerating file /etc/vx/array.info.
   All attributes will be set to default values.
   The system is coming up.  Please wait.
 
This message informs you that your array configuration has 
changed and that VxVM is recreating the file for you.
 
1.4 Removing the VxVM 3.5 Patch 3
If you back out this patch, you may get the following warning
message when you reboot:
   vxvm:vxconfigd: WARNING: Incomplete serial no in file 
/etc/vx/array.info
   Attributes will be set to default values for these records.
 
Note:
   The above warning message may be repeated many times. 
It can safely be ignored.
 
1.5 Partitioning Disks on SE6120/SE6320 Arrays (Ref. incident 115328)
Unless the correct installation command sequence is followed, partitioning
of disks on SE6120/SE6320 arrays may fail. (You may see error messages of the form:
 
"Volume Manager: Partitioning T40_27 as a new disk.
vxvm:vxdisk: ERROR: Device T40_27: online failed:
        Device path not valid
  The partitioning of T40_27 failed.")
 
 
This can be avoided by ensuring that you install the VxVM and SE6120/SE6320 Array Support 
Library packages, VxVM 3.5 MP3 patches, and run vxinstall in the following sequence:
 
1. Install VxVM - using pkgadd
2. Install VxVM 3.5 P3 patches (using patchadd)
3. Install VRTSt4 (ASL pkg) - using pkgadd
4. Run vxinstall
 
Note: You can obtain the latest VRTSt4 ASL from http://support.veritas.com/
- under "Knowledge Base Search" type "VRTSt4" and click Search.
 
(VRTSt4 ASL is available from TechFile ID: 254419, 
(http://seer.support.veritas.com/docs/254419.htm))
 
 
------------------------------------------------------------------
 
================================
Section 2
Upgrade_start/finish
====================
 
If you are going to upgrade Solaris, follow the instructions in the
Installation Guide, but you will need to use the new upgrade_start and
upgrade_finish scripts (refer to TechFile: 251521, 
http://seer.support.veritas.com/docs/251521.htm).
 
The upgrade_start and upgrade_finish scripts for this release will
help you to upgrade to version 3.5 of VxVM from a previous version 
of VxVM.
 
Note: The scripts for this release (VxVM 3.5) will NOT help 
you to upgrade from VxVM 3.5 to a higher version of VxVM. If you need to 
upgrade from a lower version of VxVM to a higher version, then you always 
need to use the upgrade_start and upgrade_finish scripts for 
the higher version of VxVM, not the scripts for the lower version.
 
Patch Requirements for OS Upgrade
 
The following patches are required for proper VxVM functioning:
 
OS upgraded to   Crucial patches required before running upgrade_finish
==============   =====================================================
Solaris 2.8      111413-06, 108827-19, 108528-14
Solaris 2.7      107473-07, 106541-19
Solaris 2.6      105181-31
 
 
 
--------------------------------------------------------------------
============================
Section 3
Converting from SDS to VxVM
===========================
For information on the SDS to VxVM Conversion package
(vxvmconvert) please refer to
TechNote: 251080, http://seer.support.veritas.com/docs/251080.htm.
------------------------------------------------------------------
 
========================================
Section 4
Using the DRL Sequential Logging Feature 
(Ref. incident 106385)
========================================
When the DRL Sequential Logging feature is used, it is recommended that the 
'voldrl_min_regionsz' tunable value be set to at least half the 'vol_maxio' 
tunable value. I/O to a volume with drl sequential logging may hang if the 
'vol_maxio' tunable setting is increased without adjusting the 
'voldrl_min_regionsz' tunable setting.
--------------------------------------------------------------------
 
================
Section 5
Using A/P Arrays
================
 
It should be noted that, in the case of A/P arrays, LUN ownership is
set by the DDL ASL library (using hardware configuration information
determined by scsi inq and the LUN mode sense details). This means,
for example, that if your system is configured so that:
The host machine has four HBAs, and each HBA is connected to an A/P
array - such as an HDS9200 - with primary and secondary controllers
Then, the DMP LUN is connected to the host via four paths - two primary
and two secondary paths of the HDS9200 array.
 
The effect of this, as far as VxVM DMP is concerned, is that:
1. There will be redundancy, since DMP has four paths to choose from
if a failure occurs.
a) If one of the controllers goes down, all I/O goes through the other
controller.
b) This leaves two spare paths that will be used only if one of the
other paths fails; providing redundancy at the switch level (but, not
for the array controller).
 
2. There is no load balancing, since DMP will select one of the two
primary paths to use as the current active primary path, which means
that there will be active I/O going through only one of the four paths.
------------------------------------------------------------------
 
 
==================================================
Section 6
Full Disk Mirroring and Replacement Encapsulated Root Disk Considerations
=========================================================================
 
If you are mirroring or replacing an encapsulated root disk, then it is
strongly recommended that you use vxdiskadm option #6 for mirroring and
option #5 for replacing.
 
However, if you choose to use vxassist to mirror your encapsulated
root disk, or if you wish to manually replace the disk, then you will
need to make sure that your target disk is setup correctly first.
 
To allow for future forwards and backwards compatibility,  a 1-cylinder 
gap was introduced between the private and public regions 
of the disk in VxVM 3.5; effectively reducing the public region by one
cylinder. Manual instruction is now needed to create a disk layout on
the target disk first. 
 
Consider these two scenarios :   
1. Mirroring a full disk created using an earlier version of VxVM 
   to a target disk which is exactly the same size as the 
   source disk. (A "full disk" is a disk that has no free cylinders.)   
   Note: You only need to use this step if disk mirroring/replacement
   using vxdiskadm fails. For details, see vxdiskadm(1M).   
2. Replacing a failed disk created using an earlier version of 
    VxVM to a target disk which is exactly the same size as the 
    source disk.
 
Note: 
   In the following examples, the traditional c#t#d# naming
   scheme is used. If you are using enclosure-based naming scheme,
   use the enclosure name instead. 
 
1. Determine the size of the source disk's private region, 
   using either of the following methods:   
   a. Get the private region length of the source disk using:
	#vxdisk list diskname
    where diskname is the disk media name of the source/failed disk. 
    In the displayed output, note the len(length) value for 
    the private field.
    In this example, the value of this field is 3071: 
	private: slice=4 offset=1 len=3071 
   b. For failed disk, if this information is not be available, 
    you must decide what the private region is. 
    (One option is to use the same private region size of another 
    identical disk in the disk group.)  
 
2. Use the vxdisksetup program to initialize the target disk: 
    # /usr/lib/vxvm/bin/vxdisksetup -i c#t#d# privlen=XXXX old_layout
   where XXXX is the size of the source disk's private region. 
 
3. Add the newly initialized target disk to the source disk group: 
	# vxdg  -k -g diskgroup adddisk medianame=c#t#d# 
 
------------------------------------------------------------------
 
===================
Section 7
Duplicate Disk Id's
===================
When VxVM detects disks with duplicate disk IDs, VxVM attempts to 
select the appropriate disk (using array vendor-specific logic). If a 
disk cannot be selected, VxVM does not import any of the duplicated 
disks into a disk group. 
In the rare case when VxVM cannot make the selection, you must choose 
which duplicate disk to use. (An array with hardware mirroring capability 
is particularly susceptible to data corruption, if the wrong disk were to
be selected.)
The following examples describe situations where user intervention is 
needed.
 
Example 1:
When DMP is disabled to an array that has multiple paths, then each path 
to the array is claimed as a unique disk. VxVM detects duplicate disks 
whenever an array is configured as a unique disk for each accessible 
path and gives the following message:
vxvm:vxconfigd: NOTICE: Unable to resolve duplicate diskid.
When DMP is suppressed, VxVM can not know which path to select as the 
true path. You must decide which path to use. Decide which path to exclude
 and then either edit the file /etc/vx/vxvm.exclude or, if vxconfigd is 
running, use the vxdiskadm option 17 selection 1 (suppress all paths 
through a controller from VxVM view) or selection 2 (suppress a path 
from VxVM view).
The following example shows a vxvm.exclude file with paths c6t0d0s2, 
c6t0d1s2, and c6t0d2s2 excluded from VxVM:
exclude_all 0
paths
c6t0d0s2 /pci@1f,4000/SUNW,ifp@2/ssd@w50060e8003275705,0
c6t0d1s2 /pci@1f,4000/SUNW,ifp@2/ssd@w50060e8003275705,1
c6t0d2s2 /pci@1f,4000/SUNW,ifp@2/ssd@w50060e8003275705,2
#
controllers
#
product
#
pathgroups
 
Example 2:
Some arrays such as EMC, HDS, and so on provide hardware mirroring.
When a lun pair is split, depending on how the process is performed, 
you may get two disks with the same diskid. With duplicate disk IDs, 
VxVM gives the following message:
vxvm:vxconfigd: NOTICE: Unable to resolve duplicate diskid.
Check with your array vendor to make sure that your site uses the 
proper split procedure. If you know which luns to use, decide which 
path to exclude and then either edit the file /etc/vx/vxvm.exclude or,
 if vxconfigd is running, use the vxdiskadm option 17 selection 1 
(suppress all paths through a controller from VxVM view) or 
selection 2 (suppress a path from VxVM view).
 
Example 3:
When you have disks duplicated using dd or any other disk copying 
utility, VxVM gives the following message:
vxvm:vxconfigd: NOTICE: Unable to resolve duplicate diskid.
Choose which set of duplicated disks that you want to exclude, and 
either edit the file /etc/vx/vxvm.exclude or, if vxconfigd is running,
 use the vxdiskadm option 17 selection 1 (suppress all paths through 
a controller from VxVM view) or selection 2 (suppress a path from 
VxVM view).
 
------------------------------------------------------------------
 
===================================
Section 8 
vxddladm listsupport Considerations
===================================
(This applies only when running on Solaris 9.)
After installing your patch, you may not see all the supported arrays 
when using the vxddladm listsupport command.
If you do not see the correct information, enter:
   # vxddladm addsupport all
   # vxddladm listsupport
 
to see updated results.
 
Note: A core dump may occur when using the vxddladm addsupport all command
(refer to Sun BugID 4642144). Until this problem is fixed, a temporary 
work-around is to set the LD_LIBRARY_PATH environment variable to /usr/lib 
before running vxddladm addsupport all.
 
------------------------------------------------------------------
 
===================================
Section 9
vxassist relayout Considerations
===================================
 
The vxassist relayout operation requires all mirrors in the volume
to have the same layout. If the volume contains mirrors with
different layouts, then you need to relayout the mirror plexes
to the same layout before performing the volume relayout operation.
------------------------------------------------------------------
 
============================================
Section 10
Using vxunroot to unencapsulate the root disk
=============================================
Only those encapsulated volumes that were derived from the pre-encapsulated 
root disk partitions can be unrooted. All other volumes created on the root 
disk after encapsulation must be either removed or moved to another disk
before using vxunroot.
 
------------------------------------------------------------------
 
========================================
Section 11
Using devfs to replace a disk
========================================
 
Before using devfs to replace a disk, you should ensure that the dev_t
entry for the old disk is removed from the OS device tree. Use the following
command to remove the dev_t entry:
 
luxadm -e offline <device_path>
----------------------------------------------------------------------------
=========================================================
Section 12
Suppressing a Path from DMP and VxVM in a Multipath Array
(Ref. incident 108881)
=========================================================
(This applies only when running on Solaris 9.)
 
Problem: If  you have an array with multiple paths, and after suppressing 
one path from DMP, suppress that path from VxVM using the vxdiskadm 
option 17 and option 1. Then, if all rootdg disks are from that array 
you will receive errors of the following form, and vxconfigd will not start,
so VxVM will not run:
 
 vxvm:vxconfigd: NOTICE: Unable to resolve duplicate diskid
 Please refer to release notes and admin guide for possible action/solution.
 Following are the disks with duplicate diskid:
 Vendor: SUN Product: T300 - c1t1d2s2, c4t2d2s2
 ...
 Following are the disks with duplicate diskid:
 Vendor: SUN Product: T300 - c1t1d3s2, c4t2d3s2
 WARNING: vxvm:vxio: cannot log commit record for Diskgroup rootdg: error 28
 vxvm:vxconfigd: ERROR: enable failed: Error in disk group configuration
 copies
 Unexpected kernel error in configuration update; transactions are disabled.
 vxvm:vxconfigd: FATAL ERROR: Rootdg cannot be imported during boot
 
Workaround:
 
A. If only one array is connected to one controller, perform the following
two steps:
   1. Suppress path from DMP, using vxdiskadm option 17, then option 5
   2. Suppress path from VxVM, using vxdiskadm option 17, then option 1
 
B. If more than one array is connected to one controller, perform the
following two steps:
   1. Suppress path from DMP, using vxdiskadm option 17, then option 5
   2. Suppress every path from VxVM belonging to the array, using
      vxdiskadm option 17, then option  2
 
-----------------------------------------------------------------------
 
==============================================
Section 13
Error Message when Booting off a Target Driver
(Ref. incident 109019)
==============================================
 
When any target driver, such as an ATF, coexists with VxVM,
and if the target driver happens to claim the boot disk, then the
following message may be displayed at the console:
WARNING: vxvm:vxdmp: Cannot find device number for </pci@1e,2000/lpfc@2/sd@0,7:a> 
where the path </pci@1e,2000/lpfc@2/sd@0,7:a> corresponds to the bootdisk,
obtained from EEPROM.
This message can safely be ignored.
 
----------------------------------------------------------------------
======================
Section 14
Using Hitachi Arrays
(Ref. incident 100458)
======================
If you are considering having your boot disk residing on an Hitachi array
you should first contact Hitachi Data Systems for the latest information
on supported boot disk configurations with Hitachi arrays.
------------------------------------------------------------------
 
=================================
Section 15
T3B Firmware Upgrade on Solaris 9
=================================
On Solaris 9 only, a T3B upgrade to firmware version 2.1 must follow
the procedure below. Not using the procedure leads to disabled disk
groups or an inability to mount file systems. The procedure is a result
of VERITAS incident number 95877.
Use the mount command to unmount related filesystems.
 
Stop all VxVM volumes:
# vxvol stop <vol_name>
 
Stop VxVM:
# vxdctl stop
#vxiod -f set 0
 
Upgrade T3B firmware to version 2.1.
 
Start VxVM:
# vxiod set 10
# vxconfigd -m disable
# vxdctl enable
Start the VxVM volumes:
 
# vxvol -g <dg_name> start <vol_name>
Use the mount command to remount the file system.
----------------------------------------------------------------
 
============================
Section 16
Replacing a Failed Boot Disk
(Ref. incident 109757)
============================
When using the vxdiskadm option #5 to replace a failed bootdisk 
(rootdisk) which is under VxVM control, you need to select "yes"
when the following message appears. Failure to do so will result 
in an unbootable system, even though the mirrors are complete. 
	The disk c0t0d0s2 was a previously encapsulated root disk. 
	Due to the disk layout that results from root disk 
	encapsulation, the preferred action is to reinitialize and 	
	reorganize this disk. However, if you have any non-redundant 
	data on this disk you should not reorganize this disk, as the 
	data will be lost. 
	Reorganize the disk [y,n,q,?] (default: n)
You must now select "y." 
-------------------------------------------------------------------
=======================================
Section 17
Support for Chinese GB18030 encoding
=======================================
GB18030 for the zh_CN locale is not supported
on Solaris 2.6 and 2.7.
GB18030 for zh_CN locale is supported on Solaris 8 and 9, provided
that you have installed patches 113203-03 and 113595-04.
------------------------------------------------------------------
 
===============================================================
Section 18
Recovering from Master Node Failure During a Snapback Operation
===============================================================
If the master node crashes when executing a command of the form:
# vxassist -o resyncfromreplica snapback ...
to execute a default snapback operation (resynchronizing from 
a replica on an FMR (DCO) volume), you will find, when the system 
comes back up and the volumes are restarted, that recovery is not
complete, and the snapshot plexes are not associated with any volume. 
To recover from this situation, you should use the following 
procedure:
1. Use the following commands to discover the original volume name of 
   each snapshot plex:
 # volrid='vxprint -g <diskgroup> -p -F "%snap_rid" <plexname>
  # volprint -g <diskgroup> -n -v -e v_rid=$volrid
2. Using the information discovered in step 1, identify the volumes 
   to which the snapshot plexes originally belonged, and reattach 
   them to those original volume as in the following command:
# volplex att <original_volume> <plex1> [<plex2> ...]
 
To return to the original state; you now need to perform the following
two steps:
 
3. Remove the dangling snapshot volume (the volume without any snap and 
   plexes)
 
4. Recreate the SNAPDONE plexes.
 
-----------------------------------------------------------------------
========================================================================
Section 19
Suppressing Unwanted vxassist Authentication messages When Accessing SAL
========================================================================
In this release of Volume Manager, if SAL is installed on a host on which 
vxassist is run, warning messages may be output when vxassist tries to 
contact SAL. See situations 1 and 2, below. In both cases, you can suppress
communication between vxassist and SAL by adding the following line to 
the vxassist defaults file:
 
salcontact=no
 
(The vxassist defaults file is usually "/etc/defaults/vxassist." See 
the vxassist(1m) man page for more information.)
 
Situation 1
vxassist shows the warning messages, "WARNING: SAL authentication failed" 
This warning message occurs because SAL rejects the credentials supplied 
by vxassist. For example:
 
# vxassist make voltest 100m
vxvm:vxassist: WARNING: SAL authentication failed. Username "root" not found
in password file
 
If connection to SAL is desired then you need to set valid username 
and password, using the command vxspcshow. Please refer to the vxspcshow man 
page for more information).
 
Situation 2
If vxassist does recognize the version of SAL being used, or detects an 
error in the SAL output, the following message may be appear: 
"WARNING: Error while retrieving information from SAL".
 
 
===========================
Section 20
SCSI-3 (vxfen) on Solaris 9
(Ref. incident 111620)
===========================
 
You must have Solaris patch 113277-08 (or higher) installed if you intend to
employ SCSI-3 fencing (vxfen) on Solaris 9. 
 
Failure to install this patch may cause the master node to fail due
to being fenced out, then the other nodes will not take over as master
node. Shared disk groups will be inaccessible, and the CFS filesystems may
be dismounted.
 
=====================================================================
Section 21
Do Not Use Solaris 2.8 Patch 110934-10 or Solaris 2.9 Patch 113713-01
=====================================================================
 
Solaris 2.8 patch 110934-10 and Solaris 2.9 patch 113713-01 prevent
the installation of VCS, VxVM, and GLM patches.
 
By using the showrev -p command, you can display the currently installed patches 
and their levels. For example, to check for patch 110934-10,
enter:
 
# showrev -p | grep 110934
 
If you have patch 110934-10 (Solaris 2.8) or patch 113713-01 (Solaris
2.9) installed, you must either upgrade them or remove them.
 
The following patch levels have been verified with VxVM 4.0:
     110934-14
     113713-11
 
To install the latest revision of a patch, use the patchadd command.
For example:
# patchadd 110934-14
 
To remove a patch, use the patchrm command.  For example:
# patchrm 110934-10
 
Note: The patch might not be removable, in which case a message
similar to the following will be displayed:
 
     "Patch 110934-10 was installed without backing up the original files.
     It cannot be backed out.
 
     Patchrm is terminating."
 
For Solaris 2.8, patch 110934-10, refer to TechNote 252441:
http://seer.support.veritas.com/docs/252441.htm.
 
For Solaris 2.9 patch 113713-01, the workaround is to rename the space file
before running patchadd, as follows:
 
# mv /var/sadm/pkg/VRTSvxvm/install/space \
  /var/sadm/pkg/VRTSvxvm/install/space.org
 
then:
 
# patchadd <THIS_PATCH_ID>
 
 
For Solaris 2.8, you can use patch 110934-08 or lower. If you do not
have or cannot obtain patch 110934-08, do not install patch 110934-10.
 
You can successfully install the VERITAS package without either patch.
 
The latest status of patches 110934-10 and 113713-01 for use with specific
VERITAS products is available at http://support.veritas.com.
 
 
=======================================================
Section 22
Troubleshooting a Duplicate Device Entry in vxdisk list
(Ref. incidents 114479 and 101371)
=======================================================
 
Please follow this procedure if you encounter duplicate entry in
"vxdisk list" or vxdisksetup gives "Duplicate DA" error as
specified in Incident:101371 SunBug:4630477 and Incident:114479
SunBug:4769704.
 
# vxdisksetup -i c1t5d0
vxdisksetup: c1t5d0: Duplicate DA records encountered for this device.
                     Refer to the troubleshooting guide to clear them
 
# vxdisk list
<snip>
c0t8d0s2     sliced    -            -            online
c1t2d0s2     sliced    c1t2d0s2     rootdg       online
c1t3d0s2     sliced    c1t3d0s2     ttdg         online
c1t5d0s2     sliced    c1t5d0s2     -         error
c1t5d0s2     sliced    c1t5d0s2     -         online/error <<<-- any
state is ok.
<snip>
 
1. Remove c1t5d0s2 entries from vxvm control.
 
   Do "vxdisk rm <da-name>" for all the duplicate entries
 
   [since you don't know which one is the valid one, so do
   it for all ...there can be more than 2 duplicate entries
   also ...]
 
 vxdisk rm c1t5d0s2
 vxdisk rm c1t5d0s2 <-- do it again to remove all the entries.
 
 
2. Remove the disk c1t5d0s2 using luxadm ( solaris command ).
 
   Get A5K Array name and Slot number of the disk using luxadm
 
   #luxadm disp /dev/rdsk/c1t5d0s2
 
 
   Remove device c1t5d0s2 using "luxadm remove_device" command.
   [luxadm remove_device enclr,slot-number]
 
   #luxadm remove_device SAHYADRI,f5
 
 
   Pull the disk out as per luxadm instructions.
 
 
3. Run command  "devfsadm -C"
 
4. Run command  "vxdctl enable"
 
 
  [Till this point, we have removed the dev_t corresponding to the
   physical disk. Now we will remove all the stale dev_t's]
 
  Please loop ac per below instructions.
 
LOOP :
 
  [you will see one entry less, since we can have more than 2 duplicate
   entries]
 
  #vxdisk list
 <snip>
 c0t8d0s2     sliced    -            -            online
 c1t2d0s2     sliced    c1t2d0s2     rootdg       online
 c1t3d0s2     sliced    c1t3d0s2     ttdg         online
 c1t5d0s2     sliced    c1t5d0s2     -         error
 <snip>
 
5. Again remove *ALL* duplicate c1t5d0s2 entries from vxvm control.
 
 vxdisk rm c1t5d0s2
 
6. Run command "luxadm -e offline <path to disk>" on *ALL THE PATHS*
   to the disk [this removes the stale dev_t]
 
   Our test machine is having 2 paths to the disk through
    controllers c1 and c2
 
 #luxadm -e offline /dev/dsk/c1t5d0s2
 #luxadm -e offline /dev/dsk/c2t5d0s2
 
7. Run command "devfsadm -C"
 
8. Run command  "vxdctl enable"
 
goto LOOP:
 
[Continue this process until there are no more entries in vxdisk list
 of corresponding disk c1t5d0s2 ]
 
Result:
 
# vxdisk list
<snip>
c0t8d0s2     sliced    -            -            online
c1t2d0s2     sliced    c1t2d0s2     rootdg       online
c1t3d0s2     sliced    c1t3d0s2     ttdg         online
<snip>
 
 
Now both OS device tree and VxVM are in a clean state corresponding
to disk c1t5d0s2.
 
Please follow the procedure to replace the failed disk or removed disk
as described in the Volume Manager Administration Guide (replace a new disk in
place of device c1t5d0s2).
 
=====================
Section 23
Issues with vxlictest
=====================
 
-----------------------------------------------------------------------------
23.1 vxlictest May Generate Core Dump on Inputting an Incorrect Licensing Key
(Ref. Incident 122091)
-----------------------------------------------------------------------------
 
A core dump may be generated if you input an incorrect license key when using 
the vxlictest command on a v1280, SUNW,Netra-T12 system. (Sun BugID 4810189)
 
Workaround: 
There is no work-around. However, the core dump indicates only that an incorrect 
license key was used. It can be ignored. 
 
If the correct key is used, vxlictest will not core dump.
 
This is fixed in the next major release.
 
----------------------------------------------------------------------------
23.2 vxlictest -l Should Not Require Key or Feature Name (Sun BugID 4818865)
----------------------------------------------------------------------------
 
According to the synopsis, vxlictest -l should not require a key or a feature 
name. This is incorrect.
 
Workaround: The "-l" option must be followed by a key value:
 
vxlictest -l <key>  
 
(If you want to list all license features, use "vxlicrep" command.)
 
 
======================
Section 24
Support for IBM-SDD
(Ref. Incident 102655)
======================
 
VxVM now supports the co-existence of IBM-SDD (VPATH), version 1.4.0.7, on 
Solaris. (SDD is IBM's multipath driver. It does not provide path suppressing.) 
 
Support is provided by means of the new ASL libvxvpath.so.
 
vpath devices/metanodes are represented as vpathN; for example: 
 
    /dev/rdsk/vpath12[a-h] 
 
where a-h represents partition number or slices.
 
Problem: Although Volume Manager can create a new volumes under vpath partitions,
there is a known problem where it can not encapsulate existing filesystem
data that is already under vpath control.
 
Workaround: If you wish to put vpath partition disks under Volume Manager
control, you first need to backup your filesystem data, and then restore the
filesystem contents after creating new volumes on it.
 
 
==================================
Section 25
Documentation Errata for VxVM 3.5
==================================
 
Please note the following changes to the documentation 
for VxVM 3.5 for Solaris.
 
-------------------------------------------------
25.1 VERITAS Volume Manager Troubleshooting Guide
-------------------------------------------------
 
[1] On page 48
specify the option -x syslog to vxconfigd:
 
[should be]
specify the option -x syslog to vxconfigd under C locale:
 
-------------------------------------------------
25.2 VERITAS Volume Manager Hardware Notes
-------------------------------------------------
 
[1] On page 2
HDS9950
 
[should be]
HDS9960
 
[2] On page 6
... create an entry for it in the /kernel/drv/vxdmp.conf file, 
such as the following:
dmp_pathswitch_blks_shift=16
 
[should be]
... create an entry for it in the /kernel/drv/vxdmp.conf file, 
such as the following:
dmp_pathswitch_blks_shift=16; 
 
[3] On page 8
NEC arrays: DS1200, DS1200F, DS3000SL, DS3000SM, DS3001, DS3002, DS1000,
DS1000F, DS1100, DS1100F, DS3011, DS1230, DS450, DS450F, iStorage 1000,
iStorage 2000, and iStorage 4000.
 
[should be]
NEC arrays: DS1200, DS1200F, DS3000SL, DS3000SM, DS3001, DS3002, DS1000,
DS1000F, DS1100, DS1100F, DS3011, DS1230, DS450, DS450F, iStorage 1000,
iStorage 2000, iStorage 3000, and iStorage 4000.
 
[4] On pages 21 and 22
In the "DMP and JBOD Disk Array Support," section, on pages 21-22, 
the instructions for adding JBOD disk arrays to the JBOD category
of DMP by editing vxdmp.conf are no longer supported, and should 
be ignored. You must use the vxddladm addjbod command to add disks 
to the JBOD category.
Please refer to the vxddladm(1M) man page for details.
 
[5] on page 38
 
(The following instructions for correcting the VERITAS Volume Manager
Hardware Notes resolve Sun BUGID#: 4771018 (mode mp_support=std is 
not supported).)
 
Replace the complete section under "Sun StorEdge T3 Support in A 
Multi-host Environment"
 
[should be]
In multi-host configurations, the Sun StorEdge T3 must be configured 
to the MPxIO mode (explicit failover or nonauto_trespass). In this 
mode, the Sun StorEdge Traffic Manager Software (STMS) driver on the 
host handles multipathing. VERITAS Volume Manager (VxVM) will not 
see multiple paths to any device on the array.
 
You need to upgrade the Sun StorEdge T3 firmware to 1.17B. The patch 
for this upgrade is 109115-09. The latest firmware for StorEdge 
T3 and T3+ Arrays is available in patches 109115-xx and 112276-xx.
 
The /kernel/drv/scsi_vhci.conf file must have the MPxIO mode enabled 
(mpxio-disable="no"). Use the command "sys mp_support mpxio" on the 
Sun StorEdge T3 array to enable the MPxIO mode.
 
Note: All hosts in the clustered environment must use the MPxIO mode.
 
----------------------------------------
25.3 VERITAS Volume Manager User's Guide
(Ref. Incident 113777)
----------------------------------------
 
[1] on page 4
Add the following Note under "Tools"
Customizing the Table Header when a particular disk group is selected
(select disk group, then Tools -> Customize Table Header) will have the 
effect of changing the Table Header tabs for the top-level disk group,
not for the selected disk group.
 
[2] on page 66
Destroy a dynamic disk group only if you are sure that you no longer
need the volumes and data in the dynamic disk group. Since the last 
disk in a dynamic disk group cannot be removed, destroying a dynamic 
disk group is useful for freeing the last disk in a dynamic disk group for reuse.
 
[should be]
Destroy a dynamic disk group only if you are sure that you no longer
need the volumes and data in the dynamic disk group. 
 
[3] on page 66
Replace the text beginning "To destroy a dynamic disk group" with
the following:
 
To destroy a dynamic disk group
 
Right-click on the disk group to be destroyed
 
Choose Destroy Dynamic Disk Group
 
When the warning prompt appears; select Yes to confirm that you want
all volumes and disks removed from the dynamic disk group.
The dynamic disk group is then destroyed.
 
[4] on page 131
Under Step 3 - Complete the Set Usage Threshold box as follows:
 
Remove the last row of the table: "Alert Interval (vxfs systems 
only)."
 
-------------------------------------
25.4 Volume Manager 3.5 Release Notes
-------------------------------------
[1] on page 15 below last bullet of section "New Features"
 
Add the following bullet:
 
o 32-Terabyte File System Support
The 3.5 release is the first major VxFS release to support a new disk 
layout (version 5) that enables the creation of file system up to 32
terabytes in size. File systems created on VxFS 3.5 will by default use 
the new disk layout, but files created on Version 5 can still only be a 
maximum of two terabytes. File systems larger than 1TB can be created 
only on 64-bit kernels and must be created on a VERITAS Volume Manager? 
volume. An eight terabyte file system requires a 2K block size, a 16 TB 
file system requires a 4K block size, and a 32 TB file system requires 
an 8K block size. An online conversion utility, vxupgrade, is provided 
to upgrade existing disk layouts to Version 5 on mounted file systems. 
 
------------------------------------------------
25.5 VERITAS Volume Manager Administration Guide
------------------------------------------------
[1] on page 311
Replace the complete section under "voldrl_max_drtregs."
 
[should be]
voldrl_max_drtregs
 
This tunable specifies the maximum number of dirty regions that can exist
on the system at any time. This is a global value applied to the entire
system, regardless of how many active volumes the system has.
 
The default value for this tunable is 2048.
 
The tunable voldrl_max_drtregs can be used to regulate the worse-case
recovery time for the system following a failure.  A larger value may
result in improved system performance at the expense of recovery time.
 
----------------------------------------------
25.6 VERITAS Volume Manager Installation Guide
(Ref. Incident 134661)
----------------------------------------------
[1] on page 49
Add the following after the sub-section "Windows"
 
Modifying Connection Access (optional)
 
To allow users other than root to access VEA, set up a group called vrtsadm 
in /etc/group, and add the users to this group. For example, adding the 
following entry will allow the two users, root and ed, to access VEA:
 
vrtsadm::600:root,ed
 
To specify a group other than vrtsadm, you should add the group to /etc/group, 
modify the Security key and restart the VEA server daemon, as in the 
following example.
 
1. Add a new group:
 
# groupadd -g gid veagrp
 
2. Edit /etc/group to add users to the group.
 
3. Modify the Security key in the registry:
 
# /opt/VRTSob/bin/vxregctl /etc/vx/isis/Registry setvalue \
Software/VERITAS/VxSvc/CurrentVersion/Security AccessGroups REG_SZ veagrp
 
4. Restart the VEA server daemon:
 
# /opt/VRTSob/bin/vxsvcctrl restart
 
========================
Section 26
Disk Connectivity Policy
(Ref incident 118065)
========================
 
With VERITAS Volume Manager (VxVM), it is possible to create a shared
disk group on the master node of a cluster. This provides all nodes
in the cluster with concurrent read and write access to the volumes within 
the shared disk group.
 
Only the master node can create a shared disk group. This has the following
advantages and implications:
 
* All the nodes in the cluster see exactly the same configuration. 
* Only the master node can change the configuration. 
* Any changes on the master node are coordinated and propagated to the other 
(slave) nodes in the cluster. 
* Any failures requiring a configuration change must be sent to the master 
so that they can be correctly resolved. 
* As the master node resolves any failure, all the slave nodes are correctly 
updated; ensuring that all nodes have the same view of the configuration. 
 
The practical implication of this approach is that any IO failure on any
node results in the configuration of all nodes being changed. 
 
However, in some cases, it is not desirable to have all nodes reacting in this 
way to an IO failure (this is known as the global disk detach policy). 
To address these cases, an alternative way of responding to IO failures was 
added for shared disk groups. Starting with VxVM 3.2 the local disk detach 
policy (more formally known as the connectivity policy) became available for 
disk groups version 70 and above. 
 
Note: When the master causes an IO failure on a disk, the disk is marked as
failed and removed from the disk group. This is the same for both local detach 
policy and global detach policy. On all the nodes, the volumes on that disk 
will be unable to perform IO to an underlying physical device. When a slave 
causes an IO failure the disk is not removed from the disk group.
 
26.1 Global Disk Detach Policy
 
The global disk detach policy is the traditional and default policy for all 
nodes on the configuration. 
 
In this case, if there is an IO failure on one node, the master node
performs the normal IO recovery work to repair the failure, and the plex
is detached cluster wide. All nodes in the cluster continue to perform 
IO functions.  
 
Note: The global detach policy must be used when Disk MultiPathing (DMP) is 
managing multi-pathing on Active/Passive arrays, This ensures that all nodes 
correctly coordinate use of the active path.
 
26.2 Local Disk Detach Policy
 
The local disk detach policy was first designed for failover applications in 
large clusters.  If an application is affected by IO failures, the cluster 
framework is then able to move the application to a node that still had access 
to the volume.  
The local disk detach policy is used particularly with mirrored volumes.  (For
Unmirrored (or hardware mirrored) volumes there is no difference between
the local and global detach policies.)
 
In the case of local disk detach policy, if there is a write failure on a node, 
the master node performs the normal IO recovery work to repair the failure; but 
in addition, all the nodes are contacted to see if the disk is still acceptable. 
If the failure is not seen by all nodes, the local detach policy 
stops IO only from the node that had the failure. 
 
Note: For private disk groups, the local disk detach policy does not change the
behavior of the disk group. 
 
==================================
Section 27
Backing up VxVM Configuration Data
==================================
 
A new feature, the vxconfigbackupd daemon, is now available for backing up VxVM 
configuration data. 
 
vxconfigbackupd monitors changes to disk group configuration in VxVM. Whenever a 
configuration change occurs, the daemon backs up the changed disk group configuration 
to a file using the vxmake description format.
 
The vxconfigbackupd daemon is started from the /etc/rc2.d/S95vxvm-recover startup 
script. Changes that you make in this script for the invocation of vxconfigbackupd
do not take effect until VxVM is next started from the script.
 
Error and warning messages for the daemon are written with a timestamp to the
console device. The daemon exits on receiving a TERM signal.
 
By default, configuration backup files are stored in the /etc/vx/dgcfg directory in 
compressed form (using gzip or compress), and are maintained in a cyclical manner.
An alternate configuration backup directory can be specified using the -d option.
The files are stored uncompressed if the compression utilities are not available on 
the system. The gzip utility is preferred over compress when both utilities are 
available.
 
The configuration copy files are named dgname.N, where N is a number ranging from 
1 for the most recent copy to 5 for the oldest copy.
The number of copies that are maintained can be changed by using the
-n option.
 
When a disk group is deported or destroyed, the default behavior is to move
the configuration files for the disk group from the backup directory to
the deport subdirectory.
If the -R option is specified, the configuration files are deleted instead of moved.
 
By default, the daemon logs the configurations of all disk groups that are currently 
imported on the system.
If a list of one or more disk group names is specified as an argument,
this restricts the daemon to logging the configurations of only these disk
groups.
 
Please refer to the configbackupd(1M) manual page for further information.
 
==========================
Section 28
Known Issues with JNI HBAs
==========================
 
If your JNI card has Model numbers FCE-1063, FCE2-1063, FCE-6410, FCE2-6410, or 
FCE2-6412, then you may experience error messages of the form:
 
"Oct 22 00:16:16 ds13un jnic: [ID 847178 kern.notice] jnic1: Memory port parity 
error detected
Oct 22 00:16:16 ds13un jnic: [ID 229844 kern.notice] jnic1: Link Down
Oct 22 00:16:16 ds13un jnic: [ID 744007 kern.notice] jnic1: Target0: Port
0000EF (WWN 500060E802778702:500060E802778702) offline.
Oct 22 00:16:18 ds13un jnic: [ID 709123 kern.notice] jnic1: Link Up
Oct 22 00:16:18 ds13un jnic: [ID 236572 kern.notice] jnic1: Target0: Port
0000EF (WWN 500060E802778702:500060E802778702) online.
Oct 22 00:16:18 ds13un jnic: [ID 229844 kern.notice] jni
 
Contact JNI support for more information."
 
Workaround: 
 
Add the following parameter to the JNI configuration file (jnic.conf):
FcEnableContextSwitch = 1;
 
==================================
Section 29
Problem When Removing VxVM Package
(Ref incident 105230)
==================================
 
A panic may occur when removing the VxVM package (VRTSvxvm) using pkgrm on Solaris 9.
 
(Note: This problem is isolated to Solaris 9 only.) 
 
Work-around: The problem can be avoided by running "devfsadm stop" before the pkgrm command:
 
/etc/init.d/devfsadm stop
pkgrm VRTSvxvm
 
==========================
Section 30
Support for Hitachi Arrays
(Ref incident 129438)
==========================
 
It should be noted that only A/P mode is supported for the Hitachi arrays DF400/HDS5800
and DF500/HDS9200. If you have installed any of these arrays, you need to verify that they 
are configured for A/P mode.
 
Please contact VERITAS Support if you need assistance in determining your Hitachi array
mode.
 
If you need assistance in reconfiguring these arrays to A/P mode, you should contact 
your Hitachi Field Engineer.
 
Note: VxVM does not support SCSI3/PGR on HDS9200 in A/P mode on Solaris 2.9.
 
=======================================
Section 31
Localized Man Pages Show Incorrect Text
(Ref incident 128077)
=======================================
 
Problem: Localized man pages do not display - they are obscured by the
English versions.
 
Work-around: Remove the "man.cf" file under /opt/VRTS/man/<lang>, where
<lang> is "ja" (Japanese), "zh" (Chinese), or "fr" (French), depending on the language 
you are using.
 
========================================
Section 32
Known Issue with the VVR vradmind Daemon
========================================
 
Problem: The vradmind daemon reports a large number of messages
in the log files located in /var/vx/vras/log directory. 
 
These messages have the form: "Dropped <number> events from Trace"
 
When these messages appear in the log, the vradmind daemon might:
 
 * terminate abnormally
 * cause an increase in cpu usage
 
Work-around: There is no work-around for this problem.
 
VERITAS plans to develop a point-patch to address this problem.
(See also TechNote: 261293 at 
URL http://seer.support.veritas.com/docs/261293.htm)
 
 
===================================================
Section 33
DMP Tunable: dmp_failed_io_threshold consideration.
(Ref incident 136128)
===================================================
 
SYMPTOM:
Possible data loss after failure of a single path in a multipathed 
environment can occur due to interactions between an Application or 
File System and Volume Manager.
 
This issue only applies to configurations where all the following
apply:
 
1)  Volume Manager version 3.5 is installed.
2)  Volume Manager Volumes are NOT mirrored.
3)  There are multiple paths to the disk.
4)  Some portion of the I/O path below DMP fails in such a way that 
the error is not returned to DMP before 10 minutes have elapsed. 
Examples of situations that have been seen to cause this include: Bad 
hardware (HBA, FCOT, GBIC, Switch Port, Array Controller), and HBA 
configured to retry endlessly.
 
NOTE:  It is the failure condition in 4) that triggers the problem.  
These failures are rare and are not seen during normal operation of a 
healthy SAN.
 
BACKGROUND:
The dmp_failed_io_threshold tunable allows DMP to explicitly mark a 
device as "insane" whenever a specific time period is reached. Normally, 
DMP would retry on all available DMP paths before it concludes that a 
disk is "insane." With this parameter, it can make this conclusion even 
before it had a chance to retry all paths. This tunable sets a threshold 
value of 600 seconds (10 minutes) for an I/O error to be returned from 
the device. If the I/O takes longer than 10 minutes to return with an 
error, then DMP assumes that the device is insane and passes the error 
to Volume Manager without retrying. This allows Volume Manager to use 
a mirror of the data to satisfy the request without further delay.
 
NOTE: This is not a timeout. No DMP activity will occur after the 10 
minutes passes. DMP only checks the elapsed time of the I/O after it 
is returned by the lower layer. If the elapsed time is greater than 
dmp_failed_io_threshold seconds (default 600) then the error will be 
returned to Volume Manager without retries. DMP will wait as long as 
it takes for the I/O to be returned.
 
However, if the delay in returning the I/O is caused by something in 
the I/O path to the device rather than the device itself, DMP will 
incorrectly return the error to the Volume Manager layer rather than 
retrying the I/O on another path. If the Volume is not mirrored, then 
the error will be passed to the File System or Application layer. 
This can result in the File system marking inodes for deletion when 
they are still valid. If raw volumes are in use, then the application 
could believe that the data on disk is corrupted when it is not.
 
If the Volume is mirrored, Volume Manager will satisfy the I/O from 
the other plex and detach the plex that failed, preventing the volume 
from becoming hung.
 
SOLUTION:
To prevent this possibility in situations where mirrored volumes are 
not used, the threshold should be tuned to a sufficiently high value 
so that it will not be reached (16 hours in this example).
 
To change dmp_failed_io_threshold value, you need to add (or modify) 
the value in /kernel/drv/vxdmp.conf: 
 
    dmp_failed_io_threshold=57600
 
Then reboot.
 
In situations where mirrored volumes are in use and an application 
timeout is being hit when there is still a valid plex with the data, 
the dmp_failed_io_threshold can be tuned to a smaller value to allow 
the I/O to succeed on the mirror without triggering an application 
failure.
 
 
=======================================================================
Section 34
Updating jbod.info file on a V880 internal disk enclosure configuration
(Ref incident 133579, Sun BugID 4900508 )
=======================================================================
 
There is a new procedure for supporting multipathed JBOD (Just a Bunch
of Disks) drives with VERITAS Volume Manager (VxVM) 3.5 and later. This
new procedure is needed for multipathed internal disk drives on
Enterprise 3x00 and Sun Fire V880 systems.  Customers with internal
drives with VxVM 3.5 cannot enable Dynamic Multipathing (DMP)
support without this procedure, which will lead to serviceability
issues.   
 
This procedure only affects multipathed disk drives that are not
supported under VERITAS Device Discovery Libraries (DDL) in VxVM 3.5.
 
The following is an example of failing configuration:
 
  VERITAS Volume Manager (VxVM)
 
  . VERITAS Volume Manager 3.5 and later
 
  Sun Workstation/Server with internal multipathed disks, example:
 
  . Sun Enterprise Server 3x00
  . Sun Fire V880
 
Sun StorEdge Arrays are supported with VxVM 3.5 DDL and do not need this
procedure for DMP to work. Specifically, Photon (A5x00), Purple I/II
(T3/T3+/T3B), and Sonoma (A3500) are supported with storage specific DDL
and are not affected.
 
The following example shows a configuration which will experience this 
problem.
 
If a multipathed disk is connected to two different HBAs such as c0 and 
c1, 'vxdisk' will list it as two separate disks:
 
  # vxdisk list
 
    --------------------------------------------------
   | DEVICE    | TYPE    | DISK    | GROUP   | STATUS |
   |===========+=========+=========+=========+========|
   | c0t0d0s2  | sliced  | disk0   | rootdg  | online |
   | c1t0d0s2  | sliced  | disk1   | rootdg  | online |
    --------------------------------------------------
 
Here two disks showed up instead of one. Any internal JBOD disk that 
has multiple paths to it is subject to this problem.
 
Another example occurs when the vxdmpadm command shows a multipathed 
disk having only one path to it.
 
  # vxdmpadm getdmpnode nodename=c0t0d0s2
 
    -----------------------------------------------------------------------
  | NAME     | STATE    | ENCLR-TYPE  | PATHS  | ENBL | DSBL | ENCLR-NAME |
  |==========+==========+=============+========+======+======+============|
  | c0t0d0s2 | ENABLED  | OTHER_DISKS | 1      | 1    | 0    | OTHER_DISKS|
  | c0t1d0s2 | ENABLED  | OTHER_DISKS | 1      | 1    | 0    | OTHER_DISKS|
   -----------------------------------------------------------------------
 
This is a change of behavior compared to earlier releases.
VxVM 3.5 moved to a new device discovery library (DDL) architecture in
which specific device support (Hitachi, Photon, T3, Sonoma) is moved
from kernel driver to user libraries (under /etc/vx/lib/discovery.d).
The benefit is that new device support and bug fixes can now be done
with minimal disruption to the system.
 
The solution to this problem for VxVM 3.5 and later is to specify JBOD
support with the 'vxddladm' command.  This command needs to be executed
once and the information is persistent across reboots.  Preferably, the
command should be run *before* running 'vxinstall' for the first time.
Details for this procedure can be found in the VxVM 3.5
Administrator's Guide, and are repeated below.
 
 
CORRECTIVE ACTION:
 
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above
problem. 
 
This procedure can also be used to support Vicom Storage Virtualization 
Engine. It is also used in the StorEdge 6xx0 solution. 
 
New service procedure and documentation change are required to address
this VxVM multipathing issue. VERITAS has documented the 'vxddladm'
JBOD support in the VxVM 3.5 Administrator's Guide, page 57,
under the section:
 
     Administering Disks
     --> Discovering and Configuring Newly Added Disk Devices
     ----> Administering the Device Discovery Layer
     ------> Adding Support for Disks in the JBOD Category
 
Note that "vxdmp.conf" is not the right fix for this case as 
"vxddladm" will eventually take over the functionality.
 
  For completeness, please adhere to the following procedure:
 
  1. Find Disk Vendor ID
 
     Execute the following command to correctly identify the vendor
     ID of the internal disk: (must run as root)
 
     /etc/vx/diag.d/vxdmpinq <VxVM device name in /dev/vx/rdmp/>
 
     For example:
 
       # /etc/vx/diag.d/vxdmpinq /dev/rdsk/c0t1d0s2
       Vendor id (VID)  : SEAGATE 
       Product id (PID) : ST318404LSUN18G 
       Revision         : 8507
       Serial Number    : 0025T0LA3H
 
     In the example above, the vendor id is "SEAGATE".
 
 
  2. Add VERITAS Device Discovery Layer support for JBOD.
     (must run as root)
 
       # /usr/sbin/vxddladm addjbod vid=SEAGATE pid=ST31840LSUN18G
       # vxdctl enable
 
     NOTE: If the device is FUJITSU, you must include the length.
           For example, 
      # /usr/sbin/vxddladm addjbod vid=FUJITSU pid=MAG3091LSUN9.0G
           length=10
 
     Use vxddladm command to verify the JBOD disk is now supported:
 
       # /usr/sbin/vxddladm listjbod
 
 
--------------------------------------------------------------------
       | VID     | PID      | Opcode | Page Code | Page Offset | SNO length
|
 
|=========+==========+========+===========+=============+============|
       | SEAGATE | ALL PIDs | 18     | -1        | 36          | 12
|
 
--------------------------------------------------------------------
 
  3. Reboot the system
 
  4. Verify devices are now multipathed.  
 
       # /usr/sbin/vxdmpadm listenclosure all
 
         ---------------------------------------------------------
        | ENCLR_NAME    | ENCLR_TYPE   | ENCLR_SNO    | STATUS    |
        |===============+==============+==============+===========|
        | OTHER_DISKS   | OTHER_DISKS  | OTHER_DISKS  | CONNECTED |
        | Disk          | Disk         | DISKS        | CONNECTED |
         ---------------------------------------------------------
 
  5. Verify disk and DMP paths are recognized.  
 
       # /usr/sbin/vxdisk list
 
         Devices under Disk_0 are multipathed disks.
 
         ------------------------------------------------
        | DEVICE  | TYPE    | DISK     | GROUP  | STATUS |
        |=========+==========+==========+=======+========|
        | Disk_0  | sliced  | disk01   | rootdg | online |
         ------------------------------------------------   
 
       # /usr/sbin/vxdmpadm getdmpnode enclosure=Disk
 
         ------------------------------------------------------------------
       | NAME   | STATE   | ENCLR-TYPE | PATHS | ENBL | DSBL | ENCLR-NAME |
       |========+=========+============+=======+======+======+============|
       | Disk_0 | ENABLED | Disk       | 2     | 2    | 0    | Disk       |
        ------------------------------------------------------------------
 
 
 
------------------------------------------------------------------
 
 
=======================================================================
Section 35
Moving a disk device from one physical array slot to another
(Ref incident 137607)
=======================================================================
 
PROBLEM:
 
If a disk device is moved (or swapped) from one physical array slot to another, then it is 
possible for two different devices to be incorrectly merged into a single DMP node 
- ultimately leading to possible data corruption.
 
Note: This situation can occur even after the disks have been re-discovered (for example,
 by means of the devfsadm -C command) and re-scanned (for example, by using the vxdctl enable 
command).
 
For example; suppose the disk at slot 2 is powered off. The host will not then see any device 
in slot 2. Then:
 
# vxdisk list
DEVICE       TYPE      DISK         GROUP        STATUS
c1t1d0s2     sliced    -            -            error
c1t1d0s4     simple    c1t1d0s4     rootdg       online
c3t1d0s2     sliced    -            -            online
c3t3d0s2     sliced    -            -            online
c3t4d0s2     sliced    -            -            online
c3t5d0s2     sliced    -            -            online
c3t6d0s2     sliced    -            -            online
 
Note that c3t2d0 is missing. Also notice that DMP device c3t5d0 has only one entry.
 
Then:
# vxdmpadm getsubpaths dmpnodename=c3t5d0s2
NAME         STATE     PATH-TYPE  CTLR-NAME  ENCLR-TYPE   ENCLR-NAME
====================================================================
c3t5d0s2     ENABLED     -        c3         Disk         Disk
 
 
Suppose, now:
disk c3t5d0 at slot 5 is powered off and removed from slot 5
disk c3t2d0 at slot 2 is removed from slot 2
The two disks are swapped (so that the disk that was in slot 5 is now in slot 2,
and the disk that was in slot 2 is now in slot 5
Both disks are powered on.
 
If rediscover and rescan are now performed, in an attempt to get DMP and the OS see the 
new disk arrangement, it is possible that DMP node c3t5d0s2 has become "confused," 
and has incorrectly multi-path'ed BOTH the old device (c3t2d0s2) as well as the new device 
(c3t5d0s2) as the same device. Since these two disks are physically different, and should 
never be multi-path'ed into the same DMP node, data corruption will occur if I/O goes 
through this DMP path.
 
# devfsadm -C
# vxdctl enable
# vxdisk list
DEVICE       TYPE      DISK         GROUP        STATUS
c1t1d0s2     sliced    -            -            error
c1t1d0s4     simple    c1t1d0s4     rootdg       online
c3t1d0s2     sliced    -            -            online
c3t3d0s2     sliced    -            -            online
c3t4d0s2     sliced    -            -            online
c3t5d0s2     sliced    -            -            onlin
c3t6d0s2     sliced    -            -            online
 
# vxdmpadm getsubpaths dmpnodename=c3t5d0s2
NAME         STATE     PATH-TYPE  CTLR-NAME  ENCLR-TYPE   ENCLR-NAME
====================================================================
c3t5d0s2     ENABLED     -        c3         Disk         Disk
c3t2d0s2     ENABLED     -        c3         Disk         Disk
# dd if=/dev/zero of=/dev/vx/rdmp/c3t5d0s4 bs=128k count=1000
1000+0 records in
1000+0 records out
# iostat
  device    bps     sps    msps
 
....
  c3t5d0   4076    15.9     1.0
....
  c3t2d0   4076    15.9     1.0
 
Notice that I/O is going through both devices, which is incorrect, and will lead to unexpected 
data corruption.
 
WORK AROUND:
 
Just before changing (swapping) the disk slots, the multipathing should be disabled. 
That is, the library definition and/or the jbod definitions should be removed.  
The disks will then be added as single-pathed disks, and existing multi-pathing will 
be lost as a result of dmpnodes being split. Multipathing can be later re-enabled, 
and vxdctl enable will merge the correct dmpnodes.
 
The steps are:
 
(a) Exclude the library or remove the JBOD definition:
         # vxddladm excludearray libname=<> or # vxddladm rmjbod vid=<>
(b) Scan the disks for vxvm:
         # vxdisk scandisks or vxdctl enable
 
    (The main purpose of steps (a) & (b) is to force all the dmpnodes from the array to 
    be single-path'ed.)
 
(c) Include the library or JBOD definition.  
         # vxddladm includearray libname=<> or # vxddladm addjbod vid=<>
(d) Scan the disks for vxvm:
         #vxdisk scandisks or vxdctl enable.
 
   (The main purpose of steps (c) & (d) is to re-group the paths from scratch to again 
   form multi-path'ed dmpnodes for the luns.)
 
Note: The above steps will also fix the problem, if it has already occurred.
 
For example:
If you have physically moved a particular XP1024 disk (corresponding DDL library libvxxp256.so) 
to a different array slot, then you need to carry out the following steps:
 
# vxddladm excludearray libname=libvxxp256.so
# vxdctl enable  (or vxdisk scandisks)
# vxddladm includearray libname=libvxxp256.so
# vxdctl enable  (or vxdisk scandisks)
 
----
Caution: Once multi-pathing is disabled, the same disk is exposed as two different
disks with the potential of the disk being initialised through the other path.
Therefore, this state should not be continued for long. Also, the system should
not be rebooted because the DG import would then fail due to duplicate disk ids.
 
==============================
Section 36
Join and Master Failover Times
(Ref incident 140965)
==============================
 
PROBLEM: 
 
In some cases customers may experience long join times or long master failover times.
Customers are notified by a message like this example:
 
	"cluster_establish: timed out"
 
To enable VERITAS support to diagnose the cause, it may be necessary to
turn on additional diagnostic information (see below) on nodes
experiencing this problem. This information should then be provided to
your VERITAS support engineer, or to VERITAS Customer Support.
 
To turn on debug messages:
 
In /opt/VRTSvcs/bin/CVMCluster/online
 
Change line:
VXCLUSTADM=/etc/vx/bin/vxclustadm
 to
VXCLUSTADM="/etc/vx/bin/vxclustadm -T"
 
Once the messages are turned on, you must offline the node and then onlined
for the changes to take affect.
 
For more help contact your VERITAS support engineer or VERITAS Customer Support. 
 
=================================
Section 37
cvm Timeout for SunCluster
(Ref incident 142776) Sun 5003523
=================================
 
Instantaneous timeouts for SunCluster may be caused by setting cvm timeout values too high.
The maximum value for these timeouts must not be more than 2147.
 
The path to the file holding the timeout values is:
 
/opt/SUNWcvm/etc/cvm.conf
 
The timeout values for the following actions must not exceed 2147 seconds:
 
cvm.start_timeout
cvm.stop_timeout
cvm.abort_timeout
cvm.return_timeout
cvm.step1_timeout
cvm.step2_timeout
cvm.step3_timeout
cvm.step4_timeout
 
For more help contact your Sun support engineer or Sun Customer Support. 
 
====================
Section 38
Localization Issues  
====================
 
In the Japanese localized VEA in some circumstances the system messages may be incomplete or missing and
interpreted as follows:
 
Incident 144279
In SxRT 3.5 MP3 Japanese version, using EMC FAS or VxTF Toolkit "OVERRIDE_ID" is displayed 
instead of the text "Do you want to override array policies?".
 
Incident 144723
VxVmCommon_NOTASCII should be translated to say:
"Volume Manager takes ASCII characters to set the comment. 
Please enter ASCII characters for the comment."
 
Incident 144081
The resource string "VxVmCommon_COMMENTTOOLONG" is not included in localized resource file.
The string gives the message "Value too long for comment field. The maximum length for comment is 20."
 
Incident 144258
In the Japanese localized VEA graphical user interface, when a user selects a disk group and right clicks to 
rename the group, the users does not see a mnemonic character inside. The user also sees a message
"Mnemonic identified by key" 'DISK_GROUP_ID' not found in 'vrts.resource.ja.VmResourceBundle_ja.properties'.
 
Incident 144271
In the Japanese localized version of VEA, the word COMMA is displayed instead of the "," 
in the VmDisableControllerDialog.
 
Incident 144274
The Japanese localized VEA shows  "VmRecoverDisk_Confirm" instead of the text "Are you sure you want to recover
the disk <0>?"
 
Incident 144277
The Japanese localized VEA shows "VmDisableControllerDialog_LASTPATH_WARNING" instead of the text 
"Device(s) {0} can be accessed only through this controller. Are you sure you want to disable this controller<1>?
 
Incident 144781
In the French VEA, users may not see the disk name(s) when selecting a list of disks to create a new 
disk group in the New Dynamic Disk Group Wizard because the text area in the Add Disk page is very small.
If a disk containing the file system is initialized, the data on that disk will be overwritten. 
This issue also appears in the Add Disk to Disk Group Wizard.
 
====================================================================
Section 39
vxdmp.conf and vxio.conf files overwritten during patch installation
Ref Incident 145266
====================================================================
 
Tunables for VERITAS Volume Manager (VxVM) 3.5 are stored in the /kernel/drv/vxdmp.conf 
file and the /kernel/drv/vxio.conf files. These files are overwritten during the installation of VxVM 3.5 MP2 
(Sun Patch ID 112392-06) or 3.5 MP3 (Sun Patch ID patch 112392-07).  
 
If you have modified vxdmp.conf or vxio.conf, make a copy of them before installing MP2 or MP3 so you 
can restore them afterwards.  
 
If you did not make a copy these files, you can still recover them as they are saved by patchadd(1M) 
during installation. For example, to recover the files saved during the installation of MP2, 
run the following commands:
 
# cp /var/sadm/pkg/VRTSvxvm/save/112392-06/undo.Z /tmp
# cd /tmp
# uncompress undo.Z
# pkgadd -d ./undo -s /tmp
# cp /tmp/VRTSvxvm/reloc/kernel/drv/vxio.conf /kernel/drv 
# cp /tmp/VRTSvxvm/reloc/kernel/drv/vxdmp.conf /kernel/drv
 
Then, reboot the system.
 
-------------------------------------------------------------------------------------------
 
Patch Installation and Uninstallation Instructions:
-------------------------------------------------- 
For Solaris 7, 8, and 9 releases, refer to the man pages for instructions on
using 'patchadd' and 'patchrm' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions.  The following example
installs a patch to a standalone machine:
 
        example# patchadd 112385-07
 
The following example removes a patch from a standalone system:
 
        example# patchrm 112385-07
 
For additional examples please see the appropriate man pages.

Special Install Instructions:
--------------------------------------- 
Do not use Solaris 8 patch 110934-10 or Solaris 9 patch 113713-01.
They contain bugs that prevent the installation of VM patches.
Refer to Section 21 above for details.
 
You need to use the shutdown command to reboot the system after patch 
installation or de-installation:
 
    shutdown -g0 -y -i6

README -- Last modified date:  Wednesday, May 19, 2004

