This issue has been solved.

Luns exported format from storage box

Created: 18 May 2012 | Updated: 29 May 2012
Login to vote
0 0 Votes

Hi People,

I have a doubt. In veritas storage foundation ,is there a way to know if a exported lun from storage , is stripe or concat ?

 

Thanks in advance

Alejandro

Quick Look Solution

"vxdisk -e" may work - see

"vxdisk -e" may work - see extract from manual:

If the -e option is specified, an additional two columns are displayed. The first column shows the OS-based disk access name. This option is useful if you have enabled enclosure-based naming. The second column shows the device-specific extended attributes. These attributes are specific to the device, like type of hardware mirroring on the disk, type of dynamic provisioning on disk, mediatype of the disk, etc

Mike

Filed Under

Comments

Marianne van den Berg
Trusted Advisor
Accredited
Certified
18
May
2012
Votes
0

Luns from hardware array is

Luns from hardware array is presented to the OS as a physical disk. We then use these 'disks' to create VxVM volumes.

You will need to use array tools to view physical layout.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mikebounds
Trusted Advisor
Accredited
21
May
2012
Votes
0
SOLUTION

"vxdisk -e" may work - see

"vxdisk -e" may work - see extract from manual:

If the -e option is specified, an additional two columns are displayed. The first column shows the OS-based disk access name. This option is useful if you have enabled enclosure-based naming. The second column shows the device-specific extended attributes. These attributes are specific to the device, like type of hardware mirroring on the disk, type of dynamic provisioning on disk, mediatype of the disk, etc

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has helped you, please vote or mark as solution

TonyGriffiths
Symantec Employee
Accredited
Certified
21
May
2012
Votes
0

Hi Some array vendors include

Hi

Some array vendors include such metadata coded in the SCSI inquiry data of the LUN. If it data is exposed AND the ASL has the ability to intepret it, then these extended attributes can be displayed as Mike mentioned.

Below is an extract from the admin guide

 

https://sort.symantec.com/public/documents/sfha/6....

cheers

tony

jdangelo_symc
Symantec Employee
21
May
2012
Votes
0

VXDISK Extended Attributes

Alejandro,

To determine what the avaiable extened atrributes are, you can run the following comamnds:

#> vxdisk -x  (SF 6.0)

#> vxdisk -x list (SF 5.1)

There are nearly 70 differents attributes that we report on.  That said, not all array vendors publish the same attribute info.

Joe D

 

 

28
May
2012
Votes
0

Thank you very much everyone

Thank you very much everyone for your answers

 

Ale

mikebounds
Trusted Advisor
Accredited
29
May
2012
Votes
0

Just to clarify, as in my

Just to clarify, as in my first post, "vxdisk -e list" MAY work and this depends, as Tony says if array vendors include such metadata coded in the SCSI inquiry data of the LUN.

As Joe says you can use vxdisk -x to see what extended attributes are available, although on 5.1, syntax is not "vxdisk -x list", it is just "vxdisk -x" and this does not give values of extended attributes, just available attributes, as Joe says.  Example output on a Solaris system I tried:

# vxdisk -x
 
The Supported Attributes :
DISKID              DGID                VID                 PID
ANAME               ATYPE               TPD_SUPPRESSED      NR_DEVICE
CAB_SERIAL_NO       LUN_SERIAL_NO       PORT_SERIAL_NO      CUR_OWNER
LIBNAME             LUN_OWNER           LUN_TYPE            SCSI_VERSION
REVISION            TPD_META_DEVNO      TPD_META_NAME       TPD_LOGI_CTLR
TPD_PHY_CTLR        TPD_SUBPATH         TPD_DEVICES         ASL_CACHE
ASL_VERSION         UDID                ECOPY_DISK          ECOPY_TARGET_ID
ECOPY_OPER_PARM     DEVICE_TYPE         DYNAMIC             TPD_HIDDEN_DEVS
LOG_CTLR_NAME       PHYS_CTLR_NAME      DISK_GEOMETRY       MT_SAFE
FC_PORT_WWN         FC_LUN_NO           HARDWARE_MIRROR     TPD_CONTROLLED
TPD_PARTITION_MAP   DMP_SINGLE_PATH     DMP_VMDISK_IOPOLICY  TRANSPORT          
IO_POLICY           PATH_ATTR           ARRAY_CTLR_ID       ARRAY_PORT_PWWN
DDL_DEVICE_ATTR     DDL_THIN_DISK       MEDIA_TYPE          NON_SCSI_ASL
 

 

Running vxdisk -e list gives:

# vxdisk -e list

DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
disk_0       auto:ZFS       -            -           ZFS                  c1t0d0           -
emc_clariion0_0 auto:cdsdisk   -            -           online               c3t5d0 lun RAID 6

So this gives the raid type - "RAID 6".  You can get hardware mirroring type from "vxdisk -x <attr> -p list", but I tried several attributes HARDWARE_MIRROR, ATYPE, LUN_TYPE and MEDIA_TYPE before I stumbled on correct (non-obvious attibute):

# vxdisk -x DDL_DEVICE_ATTR -p list
DEVICE       DDL_DEVICE_ATTR
disk_0       NULL
emc_clariion0_0 lun RAID 6

 

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has helped you, please vote or mark as solution