The paths can be disabled using vxdmpadm disable path=<pathname>, the only caveat, is if the disk is in use, Veritas will not remove the last functioning path. The previous statement regarding device tree cleanup is correct, you will have to go in to the /dev/vx/dmp and /dev/vx/rdmp and cleanup the devices, rescan and check if the paths are removed. If you need to keep persistence on, use vxddladm set namingscheme=[osn| ebn] persistence=yes
[root@server102 rdmp]# vxddladm set namingscheme=ebn persistence=yes
[root@server102 rdmp]# vxddladm get namingscheme
NAMING_SCHEME PERSISTENCE LOWERCASE USE_AVID
============================================================
Enclosure Based Yes Yes Yes
[root@server102 rdmp]# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:none - - online invalid
ibm_shark0_0 auto:cdsdisk dev1 lex online
ibm_shark0_1 auto:cdsdisk - - online
ibm_shark0_2 auto:cdsdisk - - online
ibm_shark0_3 auto:cdsdisk - - online
ibm_shark0_4 auto:cdsdisk - - online
ibm_shark0_5 auto:cdsdisk - - online
ibm_shark0_6 auto:cdsdisk dev3 lex online
ibm_shark0_7 auto:cdsdisk ibm_shark0_7 vxfendg online
ibm_shark0_8 auto:cdsdisk ibm_shark0_8 vxfendg online
ibm_shark0_9 auto:cdsdisk ibm_shark0_9 vxfendg online
[root@server102 dcli]# vxdisk rm ibm_shark0_5
[root@server102 dcli]# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:none - - online invalid
ibm_shark0_0 auto:cdsdisk dev1 lex online
ibm_shark0_1 auto:cdsdisk - - online
ibm_shark0_2 auto:cdsdisk - - online
ibm_shark0_3 auto:cdsdisk - - online
ibm_shark0_4 auto:cdsdisk - - online
ibm_shark0_6 auto:cdsdisk dev3 lex online
ibm_shark0_7 auto:cdsdisk ibm_shark0_7 vxfendg online
ibm_shark0_8 auto:cdsdisk ibm_shark0_8 vxfendg online
ibm_shark0_9 auto:cdsdisk ibm_shark0_9 vxfendg online
[root@server102 dcli]#
It is still there but removed until your next scan
[root@server102 /]# vxdmpadm getsubpaths
NAME STATE[A] PATH-TYPE[M] DMPNODENAME ENCLR-NAME CTLR ATTRS
================================================================================
c1t0d0s2 ENABLED(A) - disk_0 disk c1 -
c2t2d0s2 ENABLED(A) - ibm_shark0_0 ibm_shark0 c2 -
c2t3d0s2 ENABLED(A) - ibm_shark0_1 ibm_shark0 c2 -
c2t4d0s2 ENABLED(A) - ibm_shark0_2 ibm_shark0 c2 -
c2t5d0s2 ENABLED(A) - ibm_shark0_3 ibm_shark0 c2 -
c2t6d0s2 ENABLED(A) - ibm_shark0_4 ibm_shark0 c2 -
c2t7d0s2 ENABLED(A) - ibm_shark0_5 ibm_shark0 c2 - <<<<
c2t8d0s2 ENABLED(A) - ibm_shark0_6 ibm_shark0 c2 -
c2t9d0s2 ENABLED(A) - ibm_shark0_7 ibm_shark0 c2 -
c2t10d0s2 ENABLED(A) - ibm_shark0_8 ibm_shark0 c2 -
c2t11d0s2 ENABLED(A) - ibm_shark0_9 ibm_shark0 c2 -
[root@server102 /]#
======================
For EMC devices use powermt check, remove, dev=disk_name
For Oracle/Solaris -
# luxadm remove_device -F /dev/rdsk/ctd
# vxdiskadm, option 3
# cfgadm -f -o unusable_FCP_dev -c unconfigure c3::50060e8004274d30
# luxadm -e offline /dev/dsk/c3t50060E8004274D30d3s2
(i.e. "luxadm -e offline <device path for LUN in 'failing' state from cfgadm>)
Then re-run the previous cfgadm command (cfgadm -al -o show_FCP_dev) to check that the LUN state has changed from "failing" to "unusable".
References
luxadm - http://xteams.oit.ncsu.edu/iso/lun_removal
Oracle luxadm - http://docs.oracle.com/cd/E23824_01/html/821-1462/luxadm-1m.html
Oracle hotplug devices - http://docs.oracle.com/cd/E19683-01/816-5074-10/hotplug.html
When you are using the dmp paths, you need to remove the disk from both drectories dsk and rdmp. Once it is removed from DMP control then remove from the operating system device control.
I was not sure what your statement, "the 2 WWN has been rearranged from the array side", meant, so I added FC-AL, Fibre and hotplug.