Highlighted

What is the VDID

VOM uses the VDID obtained from VxVM to identify the array as so has identifed an Hitachi USP-V (actually the USP is rebadged as StorageTek 9990V) as:

HITACHI_R600_SerialNo

This is not useful as I don't know what R600 means, so I am trying to understand what the VDID is.  I have looked in:

SF admin
VOM users
VOM Install
VOM Add-ons User

But I can't find any definitions in these.

I could only find an old VOM windows guide reference to it - http://sfdoccentral.symantec.com/vom/4.0/win_unix/html/vom_winadm_addon_users/SFW_VOM40/ch04s03s13.h...

which says:

The Veritas Disk ID (VDID) is a string that contains information that can identify the array that a disk is contained in. The VDID string is shown in the GUI as a part of the display of information for disks. The VDID string is also shown as a result of the vxdisk diskinfo and the vxdisk list CLI commands.

The format of the VDID string varies by array manufacturer and array model. The details of how to interpret the VDID string for a particular array are in an appendix.

 

and the next page gives a table for format of VDID Strings for Various Arrays including

Hitachi    9960, 9970, 9980, 9200, 9500,7700,USP    HITACHI_{Model}_{EnclosureID}_{CU}_{ LogicalDeviceID }
Hitachi    other models                                        WWWN+LUNID

 

vxdisk list does not give VDID (and vxdisk diskinfo is Windows syntax), but I can get VDID from vxlist which shows:

Enclosure:  hitachi_usp-v0
Status:             connected
Model:              HITACHI
Revision:           6008
Array Type:         A/A
Serial Number:      SerialNo
ASL:                name=libvxhdsusp.so version=vm-6.1-rev-1
I/O Policy:         default=MinimumQ current=MinimumQ
Partition Size:     default=512 current=512
Recovery Option:    Throttle cur=Nothrottle[0] def=Nothrottle[0] Error-Retry  cur=Timebound[300] def=Timebound[300]
Failover Policy:    default=Global current=Global
Redundancy:         default=0 current=0
Disk Count:         241
Path Count:         482
VDID:               HITACHI_R600_SerialNo
Target Ports:       5,5,6,6

 

As I understand, in vxdmpadm, the enclosure name is the enclosure type appended with a number (0, 1, 2 etc) so the enclosue is unqiue within the host, but not between hosts, so I understand the need to a unique identifier, but it would seem sensible to just append the serial number to the enclosure name.

So where can I find a recent definition for VDID on UNIX so I can find out what R600 means - perhaps this is the Enclosure_id - are there any vxvm commands I can run to obtain Enclosure_id

Thanks

Mike

 

 

1 Solution

Accepted Solutions
Accepted Solution!

Hi Mike,   The R600 is the

Hi Mike,

 

The R600 is the internal (code) name of the arrays

Hitachi TagmaStore USP-V(R600)

Hitachi TagmaStore USP-VM(R601)

 

Its better explained in this windows note https://sort.symantec.com/public/documents/sfha/6.1/windows/productguides/html/sf_admin/apbs01.htm

 

Note:       For the disks that are discovered by the ddlprov provider, the VDID string format for its array is "VID_PID_CabinetSerialNumber_LUNSerialNumber". For the disks that are not discovered by the ddlprov provider, the VDID string format for its array is "VID_PID_DISKS_LUNSerialNumber". Note that the following is not a complete list of such arrays.

 

So you're looking at the PID there.

 

Here is the document showing the extended attributes discovered.

https://www.symantec.com/business/support/resources/sites/BUSINESS/content/live/TECHNICAL_SOLUTION/77000/TECH77831/en_US/338446.pdf

View solution in original post

3 Replies
Accepted Solution!

Hi Mike,   The R600 is the

Hi Mike,

 

The R600 is the internal (code) name of the arrays

Hitachi TagmaStore USP-V(R600)

Hitachi TagmaStore USP-VM(R601)

 

Its better explained in this windows note https://sort.symantec.com/public/documents/sfha/6.1/windows/productguides/html/sf_admin/apbs01.htm

 

Note:       For the disks that are discovered by the ddlprov provider, the VDID string format for its array is "VID_PID_CabinetSerialNumber_LUNSerialNumber". For the disks that are not discovered by the ddlprov provider, the VDID string format for its array is "VID_PID_DISKS_LUNSerialNumber". Note that the following is not a complete list of such arrays.

 

So you're looking at the PID there.

 

Here is the document showing the extended attributes discovered.

https://www.symantec.com/business/support/resources/sites/BUSINESS/content/live/TECHNICAL_SOLUTION/77000/TECH77831/en_US/338446.pdf

View solution in original post

Thanks Riann. Do know of a

Thanks Riann.

Do know of a VxVM command other than vxlist which shows the VDID.  It is my understanding that vxlist consolidates info from VxVM and vxfs, but I can't see the VDID in commands like vxdisk and vxdmpadm.

Mike

Dont laugh but..... vxdisk

Dont laugh but.....

vxdisk list and vxprivutil will show it. Here is the kicker, on Unix its the UDID, not VDID

http://www.symantec.com/docs/TECH128957

 

There is also a tool to check for mismatch

http://www.symantec.com/docs/HOWTO84985