1. SYMANTEC VxVM UDID OVERVIEW
SCOTT N DUMMER
Symantec UK Support
Symantec – Introduction into how VxVM handles UDID content - rev6.0

2. INTRODUCTION
UDID OVERVIEW

3. UNIQUE DISK IDENTIFIER (UDID) INTRODUCTION
VxVM UDID DETAILS
VxVM uses two UDID values, kernel UDID (DDL) and on-disk UDID to potentially identify a CLONE/REPLICATED device differently to a standard data disk.
The Device Discover Layer (DDL) kernel UDID is the true UDID of the disk.
The on-disk UDID is the UDID written on the disk, however, this is not necessarily the “true” UDID of the disk discovered by the DDL (Device Discovery Layer). The on-disk UDID may come from another source.
DDL UDID (DDL UNIQUE TO DISK)
Private Region
ON-DISK UDID (DO NOT TRUST)

4. Private Region Contains the UDID attribute
UDID WRITTEN TO DISK
UDID CONCEPT INTRODUCED in 5.0
From VxVM 5.0, a unique disk identifier (UDID) attribute is added to the disk’s private region
(on-disk) when the disk is initialized or when the disk is imported into a disk group (if this identifier does not already exist).
In releases prior to 5.0, if VxVM could not determine which disks are the originals and clones, VxVM would not import any of the disks.
Traditionally, duplicated (clones/replicated) disks would have to be re-initialized (made unique) before they could be imported. This would normally have involved rebuilding the diskgroup to make it unique to the source disks (changing the diskid and dgid).
Disk
Private Region Contains the UDID attribute

5. UNIQUE DISK IDENTIFIER (UDID)
FORMAT
The Unique Disk Identifier (UDID) format consists of the following attributes:
Vendor ID
Product Id
Cabinet Serial Number
Lun Serial (LSN)
Each value proceeds with a HEX value of “5F” which equates to an ASCII value of “_”
LAYOUT: vid, '_', pid, '_', cab_serial_no, '_', lun_serial_no
Forms the UDID
Stored in the Private Region (on-disk)
VENDOR ID
PRODUCT ID
CAB_SERIAL_NO
LUN_SERIAL_NO

6. PRIVATE REGION CONTENTS DUPLICATED
ON-DISK
Advanced disk arrays provide hardware tools to create clones and replicated images of disks.
As a result, the VxVM private region (on-disk) contents are duplicated from the source disk to target devices such as CLONED / REPLICATED disks.
When the disk group containing the original disk is to be imported, VxVM can detect multiple disks having the same disk identifier due to the attributes defined in the private region (on-disk).
UDID (DDL UNIQUE)
Veritas diskid
Veritas dgid
ON-DISK UDID
- Source disk
Private Region

7. UDID COMPARSION UDID_MISMATCH
Whenever a disk is brought online, the current UDID value that is known to the Device Discovery Layer (DDL) is compared with the UDID that is set in the disk’s private region (on-disk).
If the UDID values do not match, the udid_mismatch flag is set on the disk.
NOTE: The “udid_mismatch” flag can be viewed with various “vxdisk” CLI command options.
DDL UDID (DDL UNIQUE TO DISK)
UDID
Private Region
CHECK
DIFFER
UDID_MISMATCH
UDID
ON-DISK UDID (DO NOT TRUST)

8. BACKGROUND INFORMATION
HISTORY
The disk content on the source disk can be copied by creating a hardware snapshot, clone or replicated image.
This can also be achieved by using dd or a similar command to clone/replicate the source disk content to a target device.
SOURCE LUN
Data transferred...
To avoid the legacy duplicate disk ID condition, the default action of VxVM is to prevent such duplicated disks from being imported.
TARGET LUN
Private Region Updated from source disk
Veritas diskid
Veritas dgid
ON-DISK UDID
Private Region

9. VXVM CLI COMMANDS UPDATING UDID CONTENT
The on-disk UDID content can be updated using the “vxdisk updateudid <da-name>” command.
This CLI operation takes the UDID value from the DDL and overwrites the UDID on-disk.
DDL UDID (DDL UNIQUE TO DISK)
UDID
UDID
Private Region
# vxdisk updateudid <da-name>
clone_disk flag set
UDID
ON-DISK UDID
UPDATED

10. UDID_MISMATCH FLAG VxVM VERSION DIFFERENCES
If a disk is a clone or a replicated copy of another disk, the on-disk UDID will differ to the UDID discovered by the Device Discovery Layer (DDL), thus triggering a udid_mismatch flag.
DDL UDID
ON-DISK UDID
UDID
UDID
Private Region
Private Region
Data transferred...
SOURCE LUN
TARGET LUN
UDID
UDID
UDID
udid_mismatch

11. Suppressed visibility of the UDID_MISMATCH flag
5.0 MP3 to 5.1 SP1 RP3/
Suppressed visibility of the UDID_MISMATCH flag

12. UDID_MISMATCH FLAG VxVM VERSION DIFFERENCES
The udid_mismatch flag visibility criteria behaviour changed as of 5.0 MP3.
Since 5.0 MP3, the VxVM udid_mismatch disk flag is not shown to the user (vxdisk list) unless the source and target (clone/replicated)disks are presented to the same physical server.

13. udid_mismatch NOT VISIBLE to USER udid_mismatch DETECTED
UDID_MISMATCH FLAG
SOURCE + TARGET ON DIFFERENT SERVERS
ORIGINAL DESIGN
udid_mismatch NOT VISIBLE to USER
UDID
UDID
PRODUCTION SERVER
OFF-HOST SERVER
UDID
UDID
UDID
udid_mismatch DETECTED
SOURCE DISK
CLONE DISK

14. udid_mismatch VISIBLE to USER udid_mismatch DETECTED
UDID_MISMATCH FLAG
SOURCE + TARGET ON SAME SERVER
ORIGINAL DESIGN
udid_mismatch VISIBLE to USER
PRODUCTION SERVER
UDID
UDID
UDID
UDID
UDID
udid_mismatch DETECTED
SOURCE DISK
CLONE DISK

15. New visibility of the UDID_MISMATCH flag
5.1 SP1 RP4/ /6.1
New visibility of the UDID_MISMATCH flag

16. udid_mismatch NOT VISIBLE to USER
VxVM DESIGN REVIEW
In 5.1.x and 6.0.x, VxVM may not prevent against incorrect LUN selection during the import process.
Scenario: Replicated and corresponding clone disks are presented to the same server.
All replicated devices are reporting a udid_mismatch for Diskgroup “srdfdg”.
- A single replicated (source) disk fails.
- This results in the corresponding clone image losing its udid_mismatch flag.
INCORRECT LUN SELECTION
udid_mismatch NOT VISIBLE to USER
SOURCE DISK
CLONE DISK
Not all the clone devices are now reporting a udid_mismatch for Diskgroup “srdfdg”.
This is because the udid_mismatch flag is not always visible, so by making it visible at all times, both Diskgroup images are treated as clones.

17. UDID_MISMATCH FLAG DESIGN CHANGE
SUMMARY: Where VxVM finds a matching disk (Clone) related to the Diskgroup image, and where the diskid also matches, the import selection criteria incorrectly assumes it is the source disk image.
The udid_mismatch flag visibility criteria behaviour changed as a result in 5.1 SP1 RP4 and to prevent incorrect disk selection data corruption scenarios.
Regardless if the source and target disks are presented to the same server, if a udid_mismatch state exists the udid_mismatch FLAG will always be visible to the user (vxdisk list).

18. udid_mismatch VISIBLE to USER udid_mismatch DETECTED
UDID_MISMATCH FLAG
SOURCE + TARGET ON DIFFERENT SERVERS
ENHANCED DESIGN
udid_mismatch VISIBLE to USER
UDID
UDID
PRODUCTION SERVER
OFF-HOST SERVER
UDID
UDID
UDID
udid_mismatch DETECTED
SOURCE DISK
CLONE DISK

19. udid_mismatch VISIBLE to USER udid_mismatch DETECTED
UDID_MISMATCH FLAG
SOURCE + TARGET ON SAME SERVER
ENHANCED DESIGN
udid_mismatch VISIBLE to USER
PRODUCTION SERVER
UDID
UDID
UDID
UDID
UDID
udid_mismatch DETECTED
SOURCE DISK
CLONE DISK

20. COMPARING UDID VALUES DISAGREE SOURCE (STD) AND CLONE DEVICES
The UDID values for source (STD) luns will agree, however, the clones luns will have a different UDID.
STD LUNs : # vxdisk -v list emc0_00ea emc0_00e7 emc0_00e8 emc0_00e9 | egrep 'Device|udid'
Device: emc0_00ea
udid: EMC%5FSYMMETRIX%5F %5F22000EA000
tag udid_asl=EMC%5FSYMMETRIX%5F %5F22000EA000
Device: emc0_00e7
udid: EMC%5FSYMMETRIX%5F %5F22000E7000
tag udid_asl=EMC%5FSYMMETRIX%5F %5F22000E7000
Device: emc0_00e8
udid: EMC%5FSYMMETRIX%5F %5F22000E8000
tag udid_asl=EMC%5FSYMMETRIX%5F %5F22000E8000
Device: emc0_00e9
udid: EMC%5FSYMMETRIX%5F %5F22000E9000
tag udid_asl=EMC%5FSYMMETRIX%5F %5F22000E9000
CLONE LUNs: # vxdisk -v list emc0_00eb emc0_0033 emc0_0034 emc0_0035 | egrep 'Device|udid'
Device: emc0_00eb
flags: online ready private autoconfig udid_mismatch autoimport
udid: EMC%5FSYMMETRIX%5F %5F22000EB000
Device: emc0_0033
udid: EMC%5FSYMMETRIX%5F %5F
Device: emc0_0034
udid: EMC%5FSYMMETRIX%5F %5F
Device: emc0_0035
udid: EMC%5FSYMMETRIX%5F %5F
DISAGREE

21. VxVM CODE CHANGE PREVENT INCORRECT LUN SELECTION
With the VxVM code changes we now safeguard against incorrect LUN selection during the import process where all LUNCLASSES report a udid_mismatch state for the same Diskgroup image.
- Replicated devices are all reporting a udid_mismatch for Diskgroup “srdfdg”
- Clone devices are all reporting a udid_mismatch for Diskgroup “srdfdg”
# vxdg import srdfdg
VxVM vxdg ERROR V Disk group srdfdg: import failed:
DG import duplicate clone detected.
Please refer to system log for details.
SUMMARY: VxVM does not know which Diskgroup image should be treated as the production (source) image.
Until one of the Diskgroup images has the udid_mismatch state updated for all of its related disks (LUNCLASS), neither Diskgroup will be permitted to be imported.
PREVENT INCORRECT LUN SELECTION

22. LUN SERIAL LUN (LSN) CHANGE
How LSN changes can impact UDID_MISMATCH events

23. UNIQUE DISK IDENTIFIER (UDID)
FORMAT
The Unique Disk Identifier (UDID) format consists of the following attributes:
Vendor ID
Product Id
Cabinet Serial Number
Lun Serial (LSN)
Each value proceeds with a HEX value of “5F” which equates to an ASCII value of “_”
LAYOUT: vid, '_', pid, '_', cab_serial_no, '_', lun_serial_no
Forms the UDID
Stored in the Private Region (on-disk)
VENDOR ID
PRODUCT ID
CAB_SERIAL_NO
LUN_SERIAL_NO

24. LUN SERIAL NUMBER (LSN) CHANGE
Changing the LUN Serial Number (LSN) content will directly modify the UDID make-up, thus, potentially triggering a FAKE (false clone) udid_mismatch event. This tricks VxVM into thinking that a standard LUN is a CLONE, which is not the case.
PRE 5.1 DESIGN POST 5.1 DESIGN
(LONG LSN) (SHORT LSN)
SUMMARY: The EMC LSN lookup location on disk obtained by the EMC ASL changes from 5.1, so the LSN is shortened when upgrading to VxVM 5.1 onwards, if the disk was initialized in a previous VxVM release.
SUMMARY

25. HARDWARE CLONE OVERVIEW
How CLONE devices can impact UDID_MISMATCH events

26. VXVM CLONE DISK CONTENT
The Veritas Volume Manager (VxVM) managed device content (such as the diskid,dgid and on-disk UDID) is transferred from the source (primary) replicated device to its corresponding target (CLONE) device. This results in an intentional udid_mismatch state on the target devices.
NOTE: The UDID value stored in the DDL will remain unique for both the source and target devices.
OVERVIEW
Cloned VxVM content
UDID (DDL UNIQUE)
Synchronization Direction
- Replicated device (Source)
- Clone device (Target)
Veritas diskid transferred to clone disk Veritas diskid updated
Veritas dgid transferred to clone disk Veritas dgid updated
ON-DISK UDID transferred to clone disk ON-DISK UDID updated

27. EMC SRDF-R2 TO BCV LUN PAIRINGS
SRDF-R2 LUNS
BCV LUNS
SOURCE
SRDF-R2 LUNS: EMC SID:
BCV LUNS: EMC SID:
CLONE
emc1_01de (AVID) : 01DE
emc1_030d (AVID) : 030D
emc1_01df (AVID) : 01DF
emc1_030e (AVID) : 030E
emc1_01e0 (AVID) : 01E0
emc1_030f (AVID) : 030F
emc1_01ef (AVID) : 01EF
emc1_0310 (AVID) : 0310
SYNCHRONIZED (READY TO SPLIT)
SYNCHRONIZING…..
emc1_01e1 (AVID) : 01E1
emc1_0311 (AVID) : 0311
emc1_01f0 (AVID) : 01F0
emc1_0312 (AVID) : 0312
DAFFY:
DAFFY:

28. HARDWARE REPLICATION OVERVIEW
How REPLICATED devices can impact UDID_MISMATCH events

29. VXVM REPLICATED DISK CONTENT
The Veritas Volume Manager (VxVM) managed device content (such as the diskid,dgid and on-disk UDID) is replicated from the source (primary) to the target (secondary) replicated device. This results in an intentional udid_mismatch state on the target devices.
NOTE: The UDID value stored in the DDL will remain unique for both the primary and secondary disk types.
OVERVIEW
Replicating VxVM content
UDID (DDL UNIQUE)
- Primary srdf-r1 Disks (RW) (Source Primary disks)
- Secondary srdf-r2 Disks (WD) (Replicated Secondary disks)
Veritas diskid replicated to secondary Veritas diskid updated
Veritas dgid replicated to secondary Veritas dgid updated
ON-DISK UDID replicated to secondary ON-DISK UDID updated

30. Secondary (R2) Site (WD) Storage-Based Replication
EMC SRDF EXAMPLE
Primary (R1) Site (RW)
Secondary (R2) Site (WD)
APP
APP
UDID (DDL - UNIQUE)
UDID (ON-DISK)
UDID (ON-DISK FROM PRIMARY)
Storage-Based Replication
EMC SRDF

31. EMC SRDF LUN OVERVIEW ACROSS SITES
Primary Site (RW)
Secondary Site (WD)
SRDF-R1 LUNS: EMC SID:
SRDF-R2 LUNS: EMC SID:
emc0_002b (AVID) : 002B
emc1_01de (AVID) : 01DE
emc0_002c (AVID) : 002C
emc1_01df (AVID) : 01DF
emc0_002d (AVID) : 002D
emc1_01e0 (AVID) : 01E0
emc0_002e (AVID) : 002E
emc1_01ef (AVID) : 01EF
REPLICATING…..
emc0_002f (AVID) : 002F
emc1_01e1 (AVID) : 01E1
emc0_0030 (AVID) : 0030
emc1_01f0 (AVID) : 01F0
DONALD:
DAFFY:

32. DMP can display CLONE and REPLICATED device attributes
DMP VALUE ADD
DMP can display CLONE and REPLICATED device attributes

33. Symantec™ DMP Extended Attributes
For EMC DMX/VMAX LUN States
DEFAULT nr WD
READY (RW)
NOT-READY (NR)
WRITE-DISABLED (WD)
NOTE: Apply the latest VRTSaslapm for 5.1.x and 6.0.x from

34. EMC SRDF ROLE STATE DETECTION
PRIMARY (R1) SERVER: RW (Read-Write LUNs)
Donald # vxdisk -eo alldgs list | grep -i linux_srdfdg | grep -i srdf-r1
emc0_002b auto:cdsdisk emc0_002b linux_srdfdg online sdcc lun srdf-r1 Mirror
emc0_002c auto:cdsdisk emc0_002c linux_srdfdg online sdce lun srdf-r1 Mirror
emc0_002d auto:cdsdisk emc0_002d linux_srdfdg online sdex lun srdf-r1 Mirror
emc0_002e auto:cdsdisk emc0_002e linux_srdfdg online sdcz lun srdf-r1 Mirror
emc0_002f auto:cdsdisk emc0_002f linux_srdfdg online sdfu lun srdf-r1 RAID
emc0_ auto:cdsdisk emc0_ linux_srdfdg online sdkx lun srdf-r1 RAID
SECONDARY (R2) SERVER: WD (Write-Disabled LUNs)
Daffy # vxdisk -eo alldgs list | grep -w linux_srdfdg | grep -i srdf-r2
emc1_01de auto:cdsdisk (linux_srdfdg) online udid_mismatch sdr lun WD srdf-r2 RAID
emc1_01df auto:cdsdisk (linux_srdfdg) online udid_mismatch sdai lun WD srdf-r2 RAID
emc1_01e0 auto:cdsdisk (linux_srdfdg) online udid_mismatch sdaj lun WD srdf-r2 RAID
emc1_01ef auto:cdsdisk (linux_srdfdg) online udid_mismatch sdy lun WD srdf-r2 Mirror
emc1_01e1 auto:cdsdisk (linux_srdfdg) online udid_mismatch sdak lun WD srdf-r2 RAID
emc1_01f0 auto:cdsdisk (linux_srdfdg) online udid_mismatch sdap lun WD srdf-r2 Mirror
VxVM SRDF LUN OVERVIEW

35. VCS PREONLINE TRIGGER
To update the on-disk UDID content for replicated devices managed by VCS

36. VCS HANDLING OF REPLICATED LUNS
UDID CONTENT
When replicating a source replicated LUN to a remote/target device, the UDID content on the target device will differ on-disk to the UDID discovered by the DDL (Device Discovery Layer, this is the true UDID value).
It may not be possible to assign newly initialized disks to a VxVM diskgroup when the replicated ROLES have been migrated due to conflicting UDID states.
A diskgroup cannot be imported using a mix of STANDARD and CLONE disks.
PROBLEM
SOLUTION
VCS PREONLINE trigger
Prior to importing the replicated VxVM managed diskgroup, the UDID content from the DDL is written on-disk, aligning the UDID values for the applicable disks for that LUNCLASS.
The PREONLINE trigger will capture the required disk list content when DMP is used without any Third Party Driver:
By aligning the UDID content prior to importing the diskgroup, newly presented storage can be allocated as required to the diskgroup that have a rw (read-write) state.
vxdisk –eo alldgs list | grep –w <dg-name> | grep –i <LUNCLASS>
wwwwwww

37. HOW TO IMPLEMENT VCS PREONLINE TRIGGER
IMPLEMENTATION STEPS:
1.] Obtain the VCS Preonline script from Symantec Support.
2.] The Preonline script may require modification depending on the environment.  
The %rep_lun hash may need modification to cater for the replication solution configured, i.e. EMC SRDF. This hash consists of the pairing between the replication agent and the lunclass for the hardware replication technology shown by VxVM/DMP.
The %rep_lun informs VCS of the replication vendor and lunclass in relation to the VCS replication agent.
  For example, the following "%rep_lun" Preonline entry states that EMC SRDF is the replication solution, and the corresponding on-disk UDID relates to srdf-r1 devices associated with the VCS managed diskgroup are to be updated.
                        my %rep_lun = ( "SRDF", "srdf-r1" );  
The Preonline script needs to be copied to the directory "/opt/VRTSvcs/bin/triggers" with the name of "preonline".
VCS SRDF AGENT – PART 1

38. HOW TO IMPLEMENT VCS PREONLINE TRIGGER
3.)   The VCS Preonline attribute needs to be set for all groups which have a replication resource.
PreOnline attribute can be set in one of two ways:
a) In VCS configuration (/etc/VRTSvcs/conf/config/main.cf) file, define
       PreOnline=1
       in the ServiceGroup (SG) definition within the main.cf to enable the PreOnline trigger for that SG.
b) While the cluster is running and is in writable state, do      # haconf -makerw
     # hagrp -display <SG> | grep -i Preonline
     # hagrp -modify <SG> PreOnline 1
      to enable the PreOnline trigger for required ServiceGroup <SG>.
    # hagrp -display <SG> | grep -i Preonline
    # haconf -dump -makero
VCS SRDF AGENT – PART 2

39. USEFUL VCS PREONLINE RELATED ARTICLES
Veritas Cluster Server (VCS) preonline trigger available to update UDID based content for replicated devices with 5.1 SP1 RP3 and onwards TECH208802
How to display the Veritas Volume Manager (vxVM) UDID related content for VxVM managed luns (vxudidlist.sh)
HOWTO84985
How to implement the Veritas Cluster Server (VCS) preonline trigger to handle the UDID update for EMC SRDF devices
HOWTO84987
How to implement the Veritas Cluster Server (VCS) preonline trigger to handle the UDID update for HDS TrueCopy (HTC) devices
HOWTO84986
How to implement the Veritas Cluster Server (VCS) preonline trigger to handle the UDID update for IBM GlobalMirror/MetroMirror devices
HOWTO85021
How to implement the Veritas Cluster Server (VCS) preonline trigger to handle the UDID update for EMC RecoverPoint devices
HOWTO85020
SYMANTEC ARTICLES

40. FURTHER PRODUCT DESIGN IMPROVEMENT
6.1 and Enhancements

41. NEW VXDG OPTION vxdg –c import <dg-name>
With Veritas Volume Manager (VxVM) 6.1 (and 6.0.5) it is now possible to update the on-disk UDID related content for a specific DiskGroup.
Previously:
# vxdisk updateudid <da-name>
# vxdisk set <da-name> clone=off
Replaced with:
# vxdg –c import <dg-name>
The “-c" is a new option provided by VxVM.
It enables the user to update the UDID related content, clearing udid_mismatch and subsequent clone_disk flags from the disks associated with the specified Diskgroup (DG).
NOTE: This option is mainly used to handle UDID alignment for replicated devices at a DG level.
vxdg –c import <dg-name>

42. NEW VXDISK OPTION vxdisk –c updateudid <da-name>
With Veritas Volume Manager (VxVM) 6.1 (and 6.0.5) it is now possible to update the on-disk UDID related content for a specific disk and clear the clone_disk flag in a single operation
Previously:
# vxdisk updateudid <da-name>
# vxdisk set <da-name> clone=off
Replaced with:
# vxdisk –c updateudid <da-name>
It enables the user to update the UDID related content, clearing udid_mismatch and subsequent clone_disk flags from the specified disk(s).
NOTE: This option is mainly used to handle UDID updates at a disk level.
vxdisk –c updateudid <da-name>

43. NEW VCS DISKGROUP ATTRIBUTE
With Veritas Cluster Server (VCS) 6.1 (and 6.0.5) it is now possible for VCS to call the VxVM command “vxdg –c import <dg-name>”.
VCS configuration:
        DiskGroup srdfdg (
                DiskGroup = srdfdg
                ClearClone = 1  <<<<< NEW 6.1 enhancement for VCS (default is 0)
                )
The VCS ClearClone attribute is mainly used to handle UDID updates for VxVM replicated devices.
ClearClone = 1
Etrack: [VCS][Product Backport] Backport VCS 6.1 DiskGroup agent "ClearClone" attribute to 6.0.x - to update the on-disk UDID content and reset the clone_disk flag to enable a VxVM dg to be imported in certain co...

44. NEW VCS SRDF CONFIGURATION
The EMC SRDF resource could be defined in the VCS ServiceGroup “srdfgrp” as follows:
group srdfgrp (
SystemList = { goofy = 0, pluto = 1 }
AutoStartList = { goofy, pluto }
SystemZones = { goofy = 0, pluto = 1 } )
DiskGroup plutodg (
DiskGroup = plutodg
ClearClone = 1  <<<<< NEW 6.1 enhancement for VCS (default is 0)
Mount srdfmnt (
MountPoint = "/srdfvol"
BlockDevice = "/dev/vx/dsk/plutodg/srdfvol"
FSType = vxfs
FsckOpt = "-n"
SRDF SRDF-PlutoDg (
SymHome = "/opt/emc/SYMCLI"
GrpName = PlutoDg
SplitTakeover = 1
plutodg requires SRDF-PlutoDg
srdfmnt requires plutodg
SAMPLE MAIN.CF LAYOUT

45. UDID SCRIPT CHECK SCRIPT: vxudidlist.sh
For those customers who can’t upgrade to 6.x and benefit from the “vxdisk –o udid list” command, the following script will report the required UDID content. #!/bin/ksh
# vxudidlist.sh - Compare UDID values until upgrading to 6.x which has the "vxdisk -o udid list" command
echo "Check excludes disks reported in online invalid|error|LVM|ZFS states"
echo "DA_NAME DGNAME DDL_UID PRIV_UDID CHECK"
for disk in `vxdisk -q list | egrep -v 'online invalid|error|LVM|ZFS' | awk '{ print $1 }'` do
content=`vxdisk -v list $disk |egrep '(Device|group|udid)' |awk '{ print $2 }' |sed "s/name=/dgname:/g" |sed "s/udid_asl=//g" |tr -s "\n" " "`
echo "$content" | awk '{ if ($3==$4) print $0,"match" ; else print $0,"mismatch" }'
done
# END OF SCRIPT - S.N.Dummer - Jan 2013
SCRIPT: vxudidlist.sh

46. Scott N Dummer scott_dummer@symantec.com Symantec UK Support