OS Version: Solaris 10
Veritas Version: 4.1

Running vxdisk list gives me this:
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c1t10d0s2 auto:sliced disk01 rootdg online
c1t11d0s2 auto:sliced rootdg01 rootdg online

Running vxdisk list c0t0d0 shows 2 other disks (c0t1d0 and c0t0d1) - what caused them to be 'tied' to c0t0d0? What exactly does it mean?

Device: c0t0d0s2
devicetag: c0t0d0
type: auto
info: format=none
flags: online ready private autoconfig invalid
pubpaths: block=/dev/vx/dmp/c0t0d0s2 char=/dev/vx/rdmp/c0t0d0s2
Multipathing information:
numpaths: 3
c0t0d0s2 state=enabled
c0t0d1s2 state=enabled
c0t1d0s2 state=enabled


Why doesn't vxdisk list show the disks c0t1d0 and c0t0d1 as separate disks?
What other veritas commands may show more info on the configuration? (Note: can't run GUI interface - only command line to get info)

(Trying to figure out HOW this came about - can't make changes to server/disks. Multiple attempts at getting c0t1d0 and c0t0d1 to show up in veritas as their own disk versus being 'tied' to c0t0d0)

Found and fixed issue (just don't know HOW it got this way in the first place).

# vxdiskadm
- option 17,
(default yes to question),
Option 6 - Prevent multipathing of a disk by VxVM

Is this by any chance a V880 or V890 with 12 disks?

vxdmpadm and vxdmpinq are sometimes useful when this happens, I have seen in some cases where a StorEdge 3xxx lun will be reported by vxvm as being the same disk because of label recycling on those arrays. If there is an ASL available it will usually fix this type of problems.