Error Message

vxconfigd debug can display

VxVM vxio V-5-0-74 Cannot open disk <>:kernel erro 6

#vxdisk -e list  can display two dmpnode name pointing to the same OS Native name

DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
ams_wms0_12  auto:none      -            -           online invalid       sdb              std fc   <  2 entries for sdb
sdb          auto:cdsdisk   -            -           online               sdb             std fc   < 2 entries for sdb

vxdg import will fail with the following:

VxVM vxio V-5-0-1138 new disk sdb has a non-unique UDID<4>VxVM vxio V-5-0-1205 UDID and GUID for new disk sdb conflicts with disk sdb
 

The file dmpnames.info does the following:
It associated the lun serial number with the name that is desired as the dmpnode name.

Refer to technical document TECH72109 for information on dmpnames.info

In the example below:

Drive device sdb is associated with the lun serial number (0004) and the device sda is associated with the lun serial number (0002)

--dmpnames.info

HITACHI%5FDF600F%5F77014349%5F0004 sdb
HITACHI%5FDF600F%5F77014349%5F0002 sda

If the lun serial number should change the file dmpnames.info will be invalid.

For example:

 Device sda will have new lun serial number (0004).  VxVM will still assigned dmpnode name sdb.

Example of lun serial number 

        Device                                 : /dev/sda
        Vendor Identification                  : HITACHI
        Product Identification                 : DF600F
        Revision                               : 0000
        Serial Number                          : 770143490004  <<< Cabinet Serial (77014349) and Lun Serial Number(0004)

When changing from enclosure base naming to Operating System(OS) base naming the drive in question could go into error state or point to the wrong dmpnode

The example below show two dmpnodes pointing to the same OS device node. 
ams_wms0_12 auto:none - - online invalid sdb std fc
sdb auto:cdsdisk - - online sdb std fc

This is due to the migration from enclosure base naming to OS base naming and back to enclosure base naming. VxVM attempt to associate the dmpnode name to enclosure name ends up getting messed up due to the restrictions done by the dmpnames.info file.

We can determine this through command vxdmpadm print_property_list. It will display the following output

HITACHI%5FDF600F%5F77014349%5F0004 : has 4 associate value pairs

associate : USER_DEFINE_NAME value : sdb <<<<<<<<<<<<<<<<<<

associate : DMP_DEVICE value : sdb

associate : DISK value : /dev/sdg

associate : DISK value : /dev/sda

The entry "USER_DEFINE_NAME" mean the file dmpnames.info has a name you would like vxvm to assign as a dmpnode name, like: 

sda === dmpnode name sdb

Remove the file /etc/vx/dmpnames.info

run vxdctl enable